RE: EDIINT-Features scenarios
<[email protected]> Fri, 13 Jan 2006 12:26:31 -0500
| Newsgroups | gmane.ietf.ediint |
|---|---|
| Message-ID | <ABF4E02DA33A6F4BAC41122C7086C89903760AE7@bromail01.internal.gxs.com> |
This is a multi-part message in MIME format. ------_=_NextPart_001_01C61866.6E2B9766 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable In the Action 4, =20 Assumption: Alpha is planning to use the same certificate with Bravo and Charley for signing the message.=20 =20 With CEM, Alpha would be able to communicate with Bravo, the effective date/time of new certificate in CEM and things happen automatically. However, in the case of Charley it being manual there may be timing issue. Adding some additional scenarios that actually handles the "Certificate Change" itself would be helpful. Especially, if there is a potential need for a product to maintain two certificates at the same time until both TPs has been migrated to new certificate. =20 =20 ** This should not be an issue when Alpha maintains different certificate to sign the message when sending message to different TPs. =20 =20 ________________________________ From: Kyle Meadors [mailto:[email protected]]=20 Sent: Friday, January 13, 2006 11:01 AM To: [email protected] Subject: EDIINT-Features scenarios =20 Since there appears to be consensus in using EDIINT-Features header to announce feature support in trading partner, I have put together the following scenarios. Are these accurate? I have also included the EDIINT-Features draft which was issued last year to IETF. Does it convey all information needed for a robust implementation? =20 Actors: Company Alpha and Trading Partners Bravo and Charley Initial Condition: Alpha has trading relationship with Bravo and both are using AS2-Version: 1.1 products. TP Charley is schedule to be setup with Alpha. =20 Action 1: Alpha upgrades product to AS2-Version: 1.2 using EDIINT-Features. It supports feature CEM. Expected Outcome-1: All messages coming out of Alpha contain EDIINT-Features header and AS2-Version: 1.2. Expected Outcome-2: Bravo ignores and does NOT fail Alpha's messages and processes them "normally". Alpha does NOT send CEM messages to Bravo because it does not detect EDIINT-Features support for CEM. =20 Action 2: Bravo upgrades product to AS2-Version: 1.2 using EDIINT-Features. It supports features CEM and MA. Expected Outcome-1: All messages coming out of Bravo contain EDIINT-Features header and AS2-Version: 1.2. Expected Outcome-2: Both Alpha and Bravo recognize each other's support of CEM through EDIINT-Features header, and Bravo recognizes Alpha does NOT support MA. =20 Action 3: Alpha onramps Charley as a trading partner.=20 Expected Outcome-1: Certificates for both Alpha and Charley MUST be exchanged out-of-band Expected Outcome-2: After trading begins, Alpha recognizes Charley does NOT support CEM through its messages. =20 Action 4: Alpha issues new certificates. Expected Outcome-1: Alpha sends new certificates through CEM to Bravo. Bravo follows CEM procedure and upgrades certificates. Expected Outcome-2: Alpha exchanges new certificates with Charley out-of-band. Charley upgrades new certificates and notifies Alpha of upgrade. =20 Kyle Meadors Principal, Test Process Drummond Group Inc. 615.212.0826 =20 -- No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: 1/12/2006 ------_=_NextPart_001_01C61866.6E2B9766 Content-Type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable <html xmlns:v=3D"urn:schemas-microsoft-com:vml" = xmlns:o=3D"urn:schemas-microsoft-com:office:office" = xmlns:w=3D"urn:schemas-microsoft-com:office:word" = xmlns=3D"http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=3DContent-Type content=3D"text/html; = charset=3Dus-ascii"> <meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)"> <!--[if !mso]> <style> v\:* {behavior:url(#default#VML);} o\:* {behavior:url(#default#VML);} w\:* {behavior:url(#default#VML);} .shape {behavior:url(#default#VML);} </style> <![endif]--> <style> <!-- /* Font Definitions */ @font-face {font-family:Tahoma; panose-1:2 11 6 4 3 5 4 4 2 4;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:12.0pt; font-family:"Times New Roman";} a:link, span.MsoHyperlink {color:blue; text-decoration:underline;} a:visited, span.MsoHyperlinkFollowed {color:purple; text-decoration:underline;} span.EmailStyle17 {mso-style-type:personal; font-family:Arial; color:windowtext;} span.EmailStyle18 {mso-style-type:personal-reply; font-family:Arial; color:navy;} @page Section1 {size:8.5in 11.0in; margin:1.0in 1.25in 1.0in 1.25in;} div.Section1 {page:Section1;} --> </style> </head> <body lang=3DEN-US link=3Dblue vlink=3Dpurple> <div class=3DSection1> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>In the Action = 4,<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Assumption: Alpha is planning to = use the same certificate with Bravo and Charley for signing the message. = <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>With CEM, Alpha would be able to communicate with Bravo, the effective date/time of new certificate in = CEM and things happen automatically. However, in the case of Charley it being = manual there may be timing issue. Adding some additional scenarios that = actually handles the “Certificate Change” itself would be helpful. Especially, if there is a potential need for a product to maintain two certificates at the same time until both TPs has been migrated to new certificate.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'> <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>** This should not be an issue when = Alpha maintains different certificate to sign the message when sending message = to different TPs.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p> <div> <div class=3DMsoNormal align=3Dcenter style=3D'text-align:center'><font = size=3D3 face=3D"Times New Roman"><span style=3D'font-size:12.0pt'> <hr size=3D2 width=3D"100%" align=3Dcenter tabindex=3D-1> </span></font></div> <p class=3DMsoNormal><b><font size=3D2 face=3DTahoma><span = style=3D'font-size:10.0pt; font-family:Tahoma;font-weight:bold'>From:</span></font></b><font = size=3D2 face=3DTahoma><span style=3D'font-size:10.0pt;font-family:Tahoma'> Kyle = Meadors [mailto:[email protected]] <br> <b><span style=3D'font-weight:bold'>Sent:</span></b> Friday, January 13, = 2006 11:01 AM<br> <b><span style=3D'font-weight:bold'>To:</span></b> = [email protected]<br> <b><span style=3D'font-weight:bold'>Subject:</span></b> EDIINT-Features = scenarios</span></font><o:p></o:p></p> </div> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Since there appears to be consensus in using EDIINT–Features header to announce feature support in trading = partner, I have put together the following scenarios. Are these accurate? I have = also included the EDIINT–Features draft which was issued last year to = IETF. Does it convey all information needed for a robust = implementation?<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Actors: Company Alpha and Trading Partners Bravo and = Charley<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Initial Condition: Alpha has trading relationship = with Bravo and both are using AS2–Version: 1.1 products. TP Charley is = schedule to be setup with Alpha.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Action 1: Alpha upgrades product to = AS2–Version: 1.2 using EDIINT–Features. It supports feature = CEM.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–1: All messages coming out of = Alpha contain EDIINT–Features header and AS2–Version: = 1.2.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–2: Bravo ignores and does NOT = fail Alpha’s messages and processes them “normally”. Alpha = does NOT send CEM messages to Bravo because it does not detect = EDIINT–Features support for CEM.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Action 2: Bravo upgrades product to = AS2–Version: 1.2 using EDIINT–Features. It supports features CEM and = MA.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–1: All messages coming out of = Bravo contain EDIINT–Features header and AS2–Version: = 1.2.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–2: Both Alpha and Bravo = recognize each other’s support of CEM through EDIINT–Features header, = and Bravo recognizes Alpha does NOT support MA.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Action 3: Alpha onramps Charley as a trading partner. = <o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–1: Certificates for both Alpha = and Charley MUST be exchanged = out–of–band<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–2: After trading begins, Alpha recognizes Charley does NOT support CEM through its = messages.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Action 4: Alpha issues new = certificates.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–1: Alpha sends new = certificates through CEM to Bravo. Bravo follows CEM procedure and upgrades = certificates.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Expected Outcome–2: Alpha exchanges new = certificates with Charley out–of–band. Charley upgrades new certificates = and notifies Alpha of upgrade.<o:p></o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'><o:p> </o:p></span></font></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Kyle Meadors</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Principal, Test Process</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>Drummond Group Inc.</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt; font-family:Arial'>615.212.0826</span></font><o:p></o:p></p> <p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span = style=3D'font-size: 12.0pt'><o:p> </o:p></span></font></p> </div> </body> </html> <BR> <P><FONT SIZE=3D2>--<BR> No virus found in this outgoing message.<BR> Checked by AVG Free Edition.<BR> Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: = 1/12/2006<BR> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial"> </FONT> </P> ------_=_NextPart_001_01C61866.6E2B9766--