RE: profiles in AS2
"Kyle Meadors" <[email protected]> Thu, 15 Dec 2005 16:20:54 -0600
| Newsgroups | gmane.ietf.ediint |
|---|---|
| Message-ID | <[email protected]> |
This is a multi-part message in MIME format. ------=_NextPart_000_0029_01C60193.8640C5D0 Content-Type: multipart/alternative; boundary="----=_NextPart_001_002A_01C60193.8640C5D0" ------=_NextPart_001_002A_01C60193.8640C5D0 Content-Type: text/plain; charset="windows-1250" Content-Transfer-Encoding: quoted-printable Not a lot of comments on this thread. But to summarize=85 =20 3 in favor of Option 2 (Features header) and use of AS2=96Version 1.2=20 1 in favor Option 3 where filtering is done on a message =20 Still does not fully address the initial start=96up conditions as = Richard pointed out, but perhaps that just can not be done without some manual setup. =20 Since this EDIINT WG will likely be closing relatively soon, I hope we = can get some more to weigh in on this. Do others object to Option 2 (with AS2=96Version 1.2)? =20 For those AS2 vendors supporting Option 2, would this impact your = product, including those deployed in existing supply chains? Are their = significant backward compatibility problems with this choice? =20 Kyle Meadors DGI _____ =20 From: Tim McCarthy [mailto:[email protected]]=20 Sent: Wednesday, December 07, 2005 9:14 AM To: Kyle Meadors; [email protected] Subject: RE: profiles in AS2 =20 Seems to me that a combination of features 2 and 4 would provide = everything we=92d need. =20 _____ =20 From: [email protected] = [mailto:[email protected]] On Behalf Of Richard Bigelow Sent: Tuesday, December 06, 2005 5:07 PM To: Kyle Meadors; [email protected] Subject: RE: profiles in AS2 =20 These are my comments. Option 2 is preferred. This memo essentially supports John Duker's memo of Dec. 5, Features Profile in AS2. =20 1. This option requires that implementers of feature 1.n also implement = all earlier features. Is that reasonable? What if 1.5 is difficult and = many vendors don't want to do it, but many want to support 1.6? Not = recommended. =20 2. The features header allows the partner A receiving the message to = know the other partner's (B's) capabilities. So when A sends to B, A knows = what is allowed. A can also check B's AS2-version; 1.1 does not allow any of = the controlled features, but does allow compression. A should update some = state for every message received from B. B might stop supporting some = feature. Recommended. =20 A possible variant of (2) is that a partner could send some message to = all its trading partners when its capabilities change. This message would = have headers only, no content. It might be useful to send this capabilities message to partners that would rarely receive normal messages. =20 3. This option allows receivers to ignore messages they don't = understand, and to detect those messages without looking for unknown headers. But = it does not provide a mechanism for the sender to know whether a receiver = can receive the message. Suppose we had done compression this way. A could send a compressed file to B, and B could ignore it based on the feature header, but then the file is lost. B could return a new MDN code = indicating unsupported-feature, and A could then send the uncompressed file, in = this example. In other cases, A would have to use some other mechanism. A = could remember that B rejected the file and not try that feature again, but = how would A know if B upgraded and can now support the feature? The = original intent of the features header was that the sender could know in advance = if the receiver supports the feature. 3 is not recommended. =20 4. Before sending a message to B, A should ask B for B's capabilities, = and check if B supports the feature. Since B might stop supporting a = feature, A should ask each time. This is ok for rare messages, like CEM, but not = for common ones, like Multiple Attachments. Not recommended. =20 None of these protocols fully addresses the initial case. Before any messages are exchanged, how do the partners know each other's = capabilities? Each partner must assume that the other supports only the basic 1.0 AS2 protocol. Hopefully, they will be able to exchange normal messages, = which will contain at least the 1.2 version header. They can then use option = 2 to discover each other capabilities. This probably works for most = features. For CEM, either they must first exchange test messages that are = unencrypted and unsigned to establish CEM capability, or exchange initial = certificates manually. =20 Alternatively, the partners would configure each other manually the = first time. Thereafter, they would be automatically updated on each other's capabilities. =20 Richard Bigelow Inovis HYPERLINK "mailto:[email protected]"[email protected] _____ =20 From: [email protected] = [mailto:[email protected]] On Behalf Of Kyle Meadors Sent: Thursday, December 01, 2005 9:04 AM To: [email protected] Subject: profiles in AS2 =20 I am needing the opinion of the AS2 community on the use of a feature profiles within AS2. Back in 2002, compression was added as an extra feature. Using "AS2=96Version: 1.1" in a message indicated the UA could support compression even if the actual message did not contain the compressed envelope. This assisted implementers in knowing if their = trading partners could support compression.=20 =20 Moving to the present, users are requesting new features. These include = I=96Ds for Reliability (from GS1), Multiple=96Attachments (oil & gas users) and Certificate Exchange Messaging (Wal=96mart, P&G and others GS1 = companies). Given AS2's adoption, I am sure there will be others in the future.=20 =20 My question to those on this elist is how to do move forward with new features. What do we do to insure only those who support a feature = receive it (e.g., only sending CEM message to trading partners who support that profile)? Also, can anything be done to insure backward compatibility to keep new Feature Header messages from being sent to & breaking older, existing implementations (e.g. older implementation errors gracefully = when getting an unrecognized MA message).=20 =20 Here are some options. I would like to hear your thoughts on what is = best or other ideas.=20 =20 1. Use AS2=96Version header to indicate UA support of profiles (e.g. 1.2 indicates CEM, 1.3 indicates CEM, Reliability). Works like compression = (e.g. =931.2=94 indicates capability of CEM but not an actual CEM message). =20 2. Use a new header, e.g. EDIINT=96Features. The features header shows = all features supported by UA (e.g. EDIINT=96Features: CEM, = multiple=96attachment) but like AS2=96Version does not indicate every message contains profile. =20 3. Use a new header for each feature which is present ONLY in the = message using that feature. For example, =93CEM=96Profile=94 for CEM messages. = This could allow receiving UA to filter in only profiles it recognizes. =20 4. Create a =93Capability Query=94 AS2 Message which returns a = Capability MDN. MDN indicates what features receiving UA can support. =20 =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.362 / Virus Database: 267.13.10/189 - Release Date: = 11/30/2005 -- No virus found in this incoming message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.13.12/193 - Release Date: = 12/6/2005 --=20 No virus found in this outgoing message. Checked by AVG Free Edition. Version: 7.1.371 / Virus Database: 267.14.0/203 - Release Date: = 12/15/2005 =20 =20 ------=_NextPart_001_002A_01C60193.8640C5D0 Content-Type: text/html; charset="windows-1250" 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" xmlns:ns0=3D"urn:schemas-microsoft-com:office:smarttags"> <head> <META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; = charset=3Dwindows-1250"> <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;} @font-face {font-family:Verdana; 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;} p.source, li.source, div.source {margin-top:0in; margin-right:-.75in; margin-bottom:0in; margin-left:.2in; margin-bottom:.0001pt; font-size:9.0pt; font-family:"Courier New";} span.EmailStyle18 {mso-style-type:personal; font-family:Arial; color:windowtext;} span.EmailStyle19 {mso-style-type:personal; font-family:Arial; color:navy;} span.EmailStyle20 {mso-style-type:personal; font-family:Arial; color:navy;} span.EmailStyle21 {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> <!--[if gte mso 9]><xml> <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" /> </xml><![endif]--><!--[if gte mso 9]><xml> <o:shapelayout v:ext=3D"edit"> <o:idmap v:ext=3D"edit" data=3D"1" /> </o:shapelayout></xml><![endif]--> </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'>Not a lot of comments on this = thread. But to summarize…<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'>3 in favor of Option 2 (Features = header) and use of AS2–Version 1.2 <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'>1 in favor Option 3 where filtering = is done on a 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'>Still does not fully address the = initial start–up conditions as Richard pointed out, but perhaps that just = can not be done without some manual setup.<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'>Since this EDIINT WG will likely be = closing relatively soon, I hope we can get some more to weigh in on this. Do = others object to Option 2 (with AS2–Version = 1.2)?<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'>For those <span = style=3D'text-transform: uppercase'>AS2 </span>vendors supporting Option 2, would this impact = your product, including those deployed in existing supply chains? Are their significant backward compatibility problems with this = choice?<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> <p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Kyle Meadors</span></font><font color=3Dnavy><span style=3D'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'>DGI</span></font><o:p></o:p></p> </div> <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'> Tim = McCarthy [mailto:[email protected]] <br> <b><span style=3D'font-weight:bold'>Sent:</span></b> Wednesday, December = 07, 2005 9:14 AM<br> <b><span style=3D'font-weight:bold'>To:</span></b> Kyle Meadors; [email protected]<br> <b><span style=3D'font-weight:bold'>Subject:</span></b> RE: profiles in = AS2</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 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>Seems to me that a combination of = features 2 and 4 would provide everything we’d = need.<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'> [email protected] [mailto:[email protected]] = <b><span style=3D'font-weight:bold'>On Behalf Of </span></b>Richard Bigelow<br> <b><span style=3D'font-weight:bold'>Sent:</span></b> Tuesday, December = 06, 2005 5:07 PM<br> <b><span style=3D'font-weight:bold'>To:</span></b> Kyle Meadors; [email protected]<br> <b><span style=3D'font-weight:bold'>Subject:</span></b> RE: profiles in = AS2</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 color=3Dnavy face=3DArial><span = style=3D'font-size: 10.0pt;font-family:Arial;color:navy'>These are my comments. Option = 2 is preferred. This memo essentially supports John Duker's memo of = Dec. 5, Features Profile in AS2.<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'>1. This option requires that = implementers of feature 1.n also implement all earlier features. Is that reasonable? What if 1.5 is difficult and many vendors don't want = to do it, but many want to support 1.6? Not = recommended.<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'>2. The features header allows = the partner A receiving the message to know the other partner's (B's) capabilities. So when A sends to B, A knows what is allowed. = A can also check B's AS2-version; 1.1 does not allow any of the controlled = features, but does allow compression. A should update some state for every = message received from B. B might stop supporting some feature. = Recommended.<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'>A possible variant of (2) is that a partner could send some message to all its trading partners when its capabilities change. This message would have headers only, no content. It might be useful to send this capabilities message to = partners that would rarely receive normal messages.<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'>3. This option allows receivers to = ignore messages they don't understand, and to detect those messages without = looking for unknown headers. But it does not provide a mechanism for the = sender to know whether a receiver can receive the message. Suppose we had = done compression this way. A could send a compressed file to B, and B = could ignore it based on the feature header, but then the file is lost. = B could return a new MDN code indicating unsupported-feature, and A could then = send the uncompressed file, in this example. In other cases, A would have = to use some other mechanism. A could remember that B rejected the file = and not try that feature again, but how would A know if B upgraded and can now = support the feature? The original intent of the features header was that = the sender could know in advance if the receiver supports the feature. = 3 is not recommended.<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'>4. Before sending a message to B, A = should ask B for B's capabilities, and check if B supports the feature. = Since B might stop supporting a feature, A should ask each time. This is = ok for rare messages, like CEM, but not for common ones, like Multiple = Attachments. Not recommended.<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'>None of these protocols fully = addresses the initial case. Before any messages are exchanged, how do the = partners know each other's capabilities? Each partner must assume that the = other supports only the basic 1.0 AS2 protocol. Hopefully, they = will be able to exchange normal messages, which will contain at least the 1.2 = version header. They can then use option 2 to discover each other capabilities. This probably works for most features. For = CEM, either they must first exchange test messages that are unencrypted and = unsigned to establish CEM capability, or exchange initial certificates = manually.<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'>Alternatively, the partners would configure each other manually the first time. Thereafter, they = would be automatically updated on each other's = capabilities.<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> <div> <p class=3DMsoNormal = style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font size=3D1 color=3Dgray face=3DVerdana><span = style=3D'font-size:9.0pt;font-family:Verdana; color:gray'>Richard Bigelow<br> Inovis<br> <a = href=3D"mailto:[email protected]">[email protected]</a>= </span></font><font color=3Dgray><span style=3D'color:gray'><o:p></o:p></span></font></p> </div> </div> </div> <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'> [email protected] [mailto:[email protected]] = <b><span style=3D'font-weight:bold'>On Behalf Of </span></b>Kyle Meadors<br> <b><span style=3D'font-weight:bold'>Sent:</span></b> Thursday, December = 01, 2005 9:04 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> profiles in = AS2</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'>I am needing the opinion of the AS2 community on the = use of a feature profiles within AS2. Back in 2002, compression was added as an = extra feature. Using "AS2–Version: 1.1" in a message indicated = the UA could support compression even if the actual message did not contain the compressed envelope. This assisted implementers in knowing if their = trading partners could support compression.</span></font> <br> <font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'> </span></font> <br> <font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'>Moving to the present, users are requesting new features. These include = I–Ds for Reliability (from GS1), Multiple–Attachments (oil & gas users) = and Certificate Exchange Messaging (Wal–mart, P&G and others GS1 companies). Given AS2's adoption, I am sure there will be others in the = future.</span></font> <br> <font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'> </span></font> <br> <font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'>My question to those on this elist is how to do move forward with new = features. What do we do to insure only those who support a feature receive it = (e.g., only sending CEM message to trading partners who support that profile)? Also, = can anything be done to insure backward compatibility to keep new Feature = Header messages from being sent to & breaking older, existing = implementations (e.g. older implementation errors gracefully when getting an = unrecognized MA message).</span></font> <br> <font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'> </span></font> <br> <font size=3D2 face=3DArial><span = style=3D'font-size:10.0pt;font-family:Arial'>Here are some options. I would like to hear your thoughts on what is best or = other ideas.</span></font> <br> <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'>1. Use AS2–Version header to indicate UA = support of profiles (e.g. 1.2 indicates CEM, 1.3 indicates CEM, Reliability). Works = like compression (e.g. “1.2” indicates capability of CEM but not = an actual CEM message).<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'>2. Use a new header, e.g. EDIINT–Features. The features header shows all features supported by UA (e.g. = EDIINT–Features: CEM, multiple–attachment) but like AS2–Version does not = indicate every message contains profile.<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'>3. Use a new header for each feature which is present = ONLY in the message using that feature. For example, = “CEM–Profile” for CEM messages. This could allow receiving UA to filter in only = profiles it recognizes.<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'>4. Create a “Capability Query” AS2<font color=3Dnavy><span style=3D'color:navy'> </span></font>Message which = returns a Capability MDN. MDN indicates what features<font color=3Dnavy><span = style=3D'color:navy'> </span></font>receiving UA can support.<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'><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.362 / Virus Database: 267.13.10/189 - Release Date: = 11/30/2005<BR> </FONT> </P><BR> <P><FONT SIZE=3D2>--<BR> No virus found in this incoming message.<BR> Checked by AVG Free Edition.<BR> Version: 7.1.371 / Virus Database: 267.13.12/193 - Release Date: = 12/6/2005<BR> </FONT> </P><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.0/203 - Release Date: = 12/15/2005<BR> </FONT> </P> <P><FONT SIZE=3D2 FACE=3D"Arial"> </FONT> </P> ------=_NextPart_001_002A_01C60193.8640C5D0-- ------=_NextPart_000_0029_01C60193.8640C5D0 Content-Type: text/plain; name="draft-meadors-ediint-features-header-00.txt" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="draft-meadors-ediint-features-header-00.txt" Draft EDI-INT Features Header August 2005=20 =20 =20 Private K. Meadors=20 Internet-Draft Drummond Group Inc.=20 Document: draft-meadors-ediint-features- August 2005=20 header-00.txt=20 Expires: February 2006 =20 Target Category: Informational =20 =20 =20 =20 EDI-INT Features Header=20 draft-meadors-ediint-features-header-00.txt=20 =20 By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79.=20 =20 Status of this Memo=20 =20 This document is an Internet-Draft and is in full conformance with=20 all provisions of Section 10 of RFC2026. =20 =20 Internet-Drafts are working documents of the Internet Engineering=20 Task Force (IETF), its areas, and its working groups. Note that = other groups may also distribute working documents as Internet- Drafts.=20 =20 Internet-Drafts are draft documents valid for a maximum of six months = and may be updated, replaced, or obsoleted by other documents at any=20 time. It is inappropriate to use Internet-Drafts as reference=20 material or to cite them other than as "work in progress."=20 =20 The list of current Internet-Drafts can be accessed at=20 http://www.ietf.org/ietf/1id-abstracts.html=20 The list of Internet-Draft Shadow Directories can be accessed at=20 http://www.ietf.org/shadow.html.=20 =20 Any questions, comments, and reports of defects or ambiguities in=20 this specification may be sent to the mailing list for the EDIINT=20 working group of the IETF, using the address <[email protected]>.=20 Requests to subscribe to the mailing list should be addressed to=20 <[email protected]>.=20 =20 =20 Abstract=20 =20 With the maturity of the EDI-INT standard of AS1, AS2 and AS3,=20 applications and additional features are being built upon the basic=20 secure transport functionality. These features are not necessarily=20 =20 =20 Meadors Expires - February 2006 [Page 1]=20 =0CDraft EDI-INT Features Header August 2005 = =20 =20 supported by all EDI-INT applications and could cause potential=20 problems with implementations =20 =20 Conventions used in this document=20 =20 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",=20 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this = document are to be interpreted as described in RFC-2119.=20 =20 Feedback Instructions=20 =20 NOTE TO RFC EDITOR: This section should be removed by the RFC editor = prior to publication.=20 =20 If you want to provide feedback on this draft, follow these=20 guidelines:=20 =20 -Send feedback via e-mail to [email protected], with "EDIINT=20 Features Header" in the Subject field.=20 =20 -Be specific as to what section you are referring to, preferably=20 quoting the portion that needs modification, after which you state=20 your comments.=20 =20 -If you are recommending some text to be replaced with your suggested = text, again, quote the section to be replaced, and be clear on the=20 section in question.=20 =20 =20 Table of Contents=20 =20 1. Introduction...................................................2=20 2. EDIINT Features Header Syntax..................................3=20 3. Implementation and Processing..................................3=20 4. EDI-INT Applications...........................................3=20 5. Security Considerations........................................4=20 6. References.....................................................4=20 6.1 Normative References.......................................4=20 6.2 Informative References.....................................4=20 Author's Address..................................................4=20 =20 =20 1. Introduction=20 =20 EDI-INT applications provide for a secure means of payload document=20 transport. The original intent was for transport of a single EDI or=20 XML document. However, as AS1 [AS1], AS2 [AS2] and AS3 [AS3] matured, = other features and application logic were implemented upon EDI-INT=20 standards. Since these features go beyond but do not violate the=20 =20 =20 Meadors Expires - February 2006 [Page 2]=20 =0CDraft EDI-INT Features Header August 2005 = =20 =20 basic premise of EDI-INT, a means is needed to communicate to trading = partners features which are supported by the originating user agent.=20 The EDIINT Features header indicates the capability of the user agent = to support the listed feature with its trading partner without out- of-band communication and agreement.=20 =20 2. EDIINT Features Header Syntax=20 =20 The EDIINT Features header can appear in the header section of an=20 AS1, AS2 and AS3 message. Its BNF syntax is listed below.=20 =20 Feature =3D "EDIINT-Features: " Feature-Name 1*("," Feature-Name)=20 =20 Feature-Name =3D Feature-Token=20 =20 Feature-Token =3D %d48-57 / ; 0-9=20 %d65- =0D 90 / ; A-Z=20 %d97-122 / ; a-z=20 "-"=20 =20 The Feature-Token allows for feature names to be specified and can=20 only contain alphanumeric characters along with the hyphen. Feature=20 names are case-insensitive.=20 =20 3. Implementation and Processing=20 =20 The EDIINT Features header indicates the originating user agent is=20 capable of supporting the features listed. The feature header MUST be = present in all messages transmitted by the user agent and not just=20 messages which utilize the feature. Upon examination of the feature=20 header, the trading partner SHOULD assume the user agent is capable=20 of receiving messages utilizing any of the features listed.=20 =20 The features listed MUST be supported by existing IETF RFC or RFC- track Internet-draft standards. These standards MUST describe the=20 feature name which is listed in the header and the means which it=20 should be used.=20 =20 =20 4. EDI-INT Applications=20 =20 Since AS1 uses email and the EDIINT Features header is not a=20 registered header with IANA, the header MUST be preceded by a "X-" to = be used. If the receiving trading partner does not support EDIINT=20 Features, it can choose to ignore the header because of the "X-".=20 Because AS2 and AS3 utilize transports of HTTP and FTP, respectively, = which allow the application to ignore headers which it does not=20 recognize, the addition of the EDIINT Features header in AS2 and AS3=20 =20 =20 Meadors Expires - February 2006 [Page 3]=20 =0CDraft EDI-INT Features Header August 2005 = =20 =20 can be done without affecting trading partners who have not=20 implemented the header.=20 =20 AS2 and AS3 applications currently use a version header, AS2-Version=20 and AS3-Version, respectively, to indicate functional support. The=20 EDIINT Features header tremendously improves the purpose and function = of the old version header. However, to provide a connection from the=20 old version header and the EDIINT Features header, AS2 and AS3=20 applications which implement the EDIINT Features header MUST use the=20 version value of "1.2" to indicate the support of the Feature header. = Also, since version "1.1" indicates the implementation supports=20 compression [COMPRESS] and "1.2" builds upon "1.1", AS2-Version or=20 AS3-Version of "1.2" MUST support compression regardless of whether=20 it is mentioned as a feature in the EDIINT Features header.=20 =20 5. Security Considerations=20 =20 Because headers are often un-encrypted, it may be possible for the=20 feature header to be altered. Trading partners MAY consult out-of- band to confirm feature support.=20 =20 6. References=20 6.1 Normative References=20 =20 [AS1] RFC3335 =93MIME-based Secure Peer-to-Peer Business Data=20 Interchange over the Internet using SMTP=94, T. Harding, R.=20 Drummond, C. Shih, 2002.=20 =20 [AS2] RFC4130 =93MIME-based Secure Peer-to-Peer Business Data=20 Interchange over the Internet using HTTP=94, D. Moberg, R.=20 Drummond, 2005.=20 =20 [AS3] draft-ietf-ediint-as3-03.txt =93MIME-based Secure Peer-to-Peer=20 Business Data Interchange over the Internet using FTP=94, T.=20 Harding, R. Scott, 2005.=20 =20 [COMPRESS] draft-ietf-ediint-compression-04.txt =93Compressed Data = for=20 EDIINT=94, T. Harding, 2005.=20 =20 6.2 Informative References=20 =20 [RFC2828] RFC2828 =93Internet Security Glossary=94, R. Shirley, May = 2000.=20 =20 [RFC2119] RFC2119 =93Key Words for Use in RFC's to Indicate = Requirement=20 Levels=94, S.Bradner, March 1997.=20 =20 =20 Author's Address=20 =20 =20 =20 Meadors Expires - February 2006 [Page 4]=20 =0CDraft EDI-INT Features Header August 2005 = =20 =20 Kyle Meadors=20 Drummond Group Inc.=20 4700 Bryant Irvin Court, Suite 303=20 Fort Worth, TX 76107 USA=20 Email: [email protected]=20 =20 =20 Copyright Notice=20 Copyright (C) The Internet Society 2005. This document is subject=20 to the rights, licenses and restrictions contained in BCP 78, and=20 except as set forth therein, the authors retain all their rights.=20 =20 This document and the information contained herein are provided on an = "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS = OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET=20 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,=20 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE=20 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED=20 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.=20 =20 =20 =20 Meadors Expires - February 2006 [Page 5]=20 =0C ------=_NextPart_000_0029_01C60193.8640C5D0--