update on EDIINT Features
"Kyle Meadors" <[email protected]> Tue, 21 Feb 2006 17:48:20 -0600
| Newsgroups | gmane.ietf.ediint |
|---|---|
| Message-ID | <000701c63741$4c51f7c0$6901a8c0@KYLEDGILAPTOP> |
This is a multi-part message in MIME format.
------=_NextPart_000_0008_01C6370F.01B787C0
Content-Type: multipart/alternative;
boundary="----=_NextPart_001_0009_01C6370F.01B787C0"
------=_NextPart_001_0009_01C6370F.01B787C0
Content-Type: text/plain;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
Made small update on EDIINT Features on the Features Update message =
Richard
mentioned. Its paragraph is below. Will get to CEM this week.
=20
BTW, neither EDIINT Features nor CEM is officially EDI=96INT WG drafts =
but
will be personal, informational submissions. They are just being =
discussed
here because of their relation to EDIINT.
=20
=20
5. Features Update Message=20
=20
When a user agent upgrades its features, either adding or removing=20
features, it SHOULD notify its trading partners who support EDIINT=20
Features by sending a Features Update message. The Features Update=20
message has only headers does not have a body, and the EDIINT=20
Features header contains the new list of supported features. This=20
message should only go to trading partners using version "1.2" and=20
EDIINT Features header.
=20
Kyle Meadors
Principal, Test Process
Drummond Group Inc.
615.212.0826
=20
--=20
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.0.0/266 - Release Date: 2/21/2006
=20
=20
------=_NextPart_001_0009_01C6370F.01B787C0
Content-Type: text/html;
charset="windows-1250"
Content-Transfer-Encoding: quoted-printable
<html 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=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dwindows-1250">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<style>
<!--
/* 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-compose;
font-family:Arial;
color:windowtext;}
@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 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'>Made small update on EDIINT Features on the Features =
Update
message Richard mentioned. Its paragraph is below. Will get to CEM this =
week.<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'>BTW, neither EDIINT Features nor CEM is officially =
EDI–INT
WG drafts but will be personal, informational submissions. They are just =
being
discussed here because of their relation to =
EDIINT.<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'>5. Features Update 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'> When a user agent upgrades its features, =
either adding or
removing <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'> features, it SHOULD notify its trading =
partners who
support EDIINT <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'> Features by sending a Features Update =
message. The
Features Update <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'> message has only headers does not have a =
body, and the
EDIINT <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'> Features header contains the new list of =
supported
features. This <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'> message should only go to trading =
partners using version
"1.2" and <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'> EDIINT Features =
header.<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.375 / Virus Database: 268.0.0/266 - Release Date: =
2/21/2006<BR>
</FONT> </P>
<P><FONT SIZE=3D2 FACE=3D"Arial"> </FONT> </P>
------=_NextPart_001_0009_01C6370F.01B787C0--
------=_NextPart_000_0008_01C6370F.01B787C0
Content-Type: text/plain;
name="draft-meadors-ediint-features-header-01_022106.txt"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="draft-meadors-ediint-features-header-01_022106.txt"
Draft EDI-INT Features Header February 2006=20
=20
=20
Private K. Meadors=20
Internet-Draft Drummond Group Inc.=20
Document: draft-meadors-ediint-features- February 2006=20
header-01.txt=20
Expires: August 2006 =20
Target Category: Informational =20
=20
=20
=20
EDI-INT Features Header=20
draft-meadors-ediint-features-header-01.txt=20
=20
By submitting this Internet-Draft, each author represents that any=20
applicable patent or other IPR claims of which he or she is aware=20
have been disclosed, or will be disclosed, and any of which he or she =
becomes aware will be disclosed, in accordance with Section 6 of BCP=20
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
=20
=20
Meadors Expires - August 2006 [Page 1]=20
=0CDraft EDI-INT Features Header February 2006 =
=20
=20
secure transport functionality. These features are not necessarily=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. Features Update Message........................................4=20
6. Security Considerations........................................4=20
7. References.....................................................4=20
7.1 Normative References.......................................4=20
7.2 Informative References.....................................5=20
Author's Address..................................................5=20
=20
=20
1. =0D 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, =
=20
=20
Meadors Expires - August 2006 [Page 2]=20
=0CDraft EDI-INT Features Header February 2006 =
=20
=20
other features and application logic were implemented upon EDI-INT=20
standards. Since these features go beyond but do not violate the=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. =0D 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. =0D 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
4. =0D 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 - August 2006 [Page 3]=20
=0CDraft EDI-INT Features Header February 2006 =
=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. =0D Features Update Message=20
=20
When a user agent upgrades its features, either adding or removing=20
features, it SHOULD notify its trading partners who support EDIINT=20
Features by sending a Features Update message. The Features Update=20
message has only headers does not have a body, and the EDIINT=20
Features header contains the new list of supported features. This=20
message should only go to trading partners using version "1.2" and=20
EDIINT Features header.=20
=20
6. =0D 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
7. =0D References=20
7.1 =0D 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
=20
=20
Meadors Expires - August 2006 [Page 4]=20
=0CDraft EDI-INT Features Header February 2006 =
=20
=20
7.2 =0D 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
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 - August 2006 [Page 5]=20
=0C
------=_NextPart_000_0008_01C6370F.01B787C0--