[Docs] [txt|pdf] [Tracker] [Email] [Diff1] [Diff2] [Nits]
Versions: 00 01 02 03 04 05 06 07 08 09 RFC 6017
Individual Submission K. Meadors, Ed.
Internet-Draft Drummond Group Inc.
Intended status: Informational June 15, 2010
Expires: December 17, 2010
EDI-INT Features Header
draft-meadors-ediint-features-header-09
Abstract
With the maturity of the EDI-INT standards of AS1, AS2 and AS3,
applications and additional features are being built upon the basic
secure transport functionality. These features are not necessarily
supported by all EDI-INT applications and could cause potential
problems with implementations. The EDIINT Features header provides a
means to resolve these problems and support new functionality.
Status of this Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 17, 2010.
Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
Meadors Expires December 17, 2010 [Page 1]
Internet-Draft EDI-INT Features Header June 2010
described in the Simplified BSD License.
This document may contain material from IETF Documents or IETF
Contributions published or made publicly available before November
10, 2008. The person(s) controlling the copyright in some of this
material may not have granted the IETF Trust the right to allow
modifications of such material outside the IETF Standards Process.
Without obtaining an adequate license from the person(s) controlling
the copyright in such materials, this document may not be modified
outside the IETF Standards Process, and derivative works of it may
not be created outside the IETF Standards Process, except to format
it for publication as an RFC or to translate it into languages other
than English.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1. Requirements Language . . . . . . . . . . . . . . . . . . . 3
2. EDIINT Features Header Syntax . . . . . . . . . . . . . . . . . 3
3. Implementation and Processing . . . . . . . . . . . . . . . . . 3
4. EDI-INT Applications . . . . . . . . . . . . . . . . . . . . . 4
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 4
6. Security Considerations . . . . . . . . . . . . . . . . . . . . 5
7. Normative References . . . . . . . . . . . . . . . . . . . . . 5
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 5
Meadors Expires December 17, 2010 [Page 2]
Internet-Draft EDI-INT Features Header June 2010
1. Introduction
EDI-INT applications provide for a secure means of payload document
transport. The original intent was for transport of a single EDI or
XML document. However, as AS1 [RFC3335], AS2 [RFC4130] and AS3
[RFC4823] matured, other features and application logic were
implemented upon EDI-INT standards. Since these features go beyond
but do not violate the basic premise of EDI-INT, a means is needed to
communicate to trading partners features which are supported by the
originating user agent. 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.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
2. EDIINT Features Header Syntax
The EDIINT Features header can appear in the header section of an
AS1, AS2 and AS3 message. Its ABNF [RFC5234] syntax is listed below.
Feature = "EDIINT-Features:" [WSP] Feature-Name *([WSP] "," [WSP]
Feature-Name)
Feature-Name = 1*Feature-Token
Feature-Token= %d48-57 / ; 0-9
%d65-90 / ; A-Z
%d97-122 / ; a-z
"-" ; blank space " " is not allowed
The Feature-Token allows for feature names to be specified and can
only contain alphanumeric characters along with the hyphen. Feature
names are case-insensitive.
3. Implementation and Processing
The EDIINT Features header indicates the originating user agent is
capable of supporting the features listed. The EDIINT Features
header MUST be present in all messages transmitted by the user agent
and not just messages which utilize the feature. Upon examination of
the EDIINT Features header, the trading partner SHOULD assume the
user agent is capable of receiving messages utilizing any of the
Meadors Expires December 17, 2010 [Page 3]
Internet-Draft EDI-INT Features Header June 2010
features listed.
The features listed MUST be supported by IETF RFC standards. These
standards MUST describe the feature name which is listed in the
header and the means which it should be used.
4. EDI-INT Applications
AS2 and AS3 applications currently use a version header, AS2-Version
and AS3-Version, respectively, to indicate functional support. The
EDIINT Features header tremendously improves the purpose and function
of the old version header. However, to provide a connection from the
old version header and the EDIINT Features header, AS2 and AS3
applications which implement the EDIINT Features header MUST use the
version value of "1.2" to indicate the support of the EDIINT Features
header. Also, since version "1.1" indicates the implementation
supports compression [RFC5402] and "1.2" builds upon "1.1", AS2-
Version or AS3-Version of "1.2" MUST support compression regardless
of whether it is mentioned as a feature in the EDIINT Features
header.
AS1 does not use a version header and one is not required for
including the EDIINT-Features header.
The EDIINT Features header is informational and AS1, AS2 or AS3
trading partners who have not implemented it can safely ignore this
header.
5. IANA Considerations
This is a request for a provisional header registration.
Header field name: EDIINT-Features
Applicable protocol: http and mail
Status: provisional
Author/Change controller: Kyle Meadors of Drummond Group
(kyle@drummondgroup.com)
Specification document(s): https://datatracker.ietf.org/doc/
draft-meadors-ediint-features-header/
Related information: This header will be used in conjection with the
EDIINT WG specifications RFC 4130 (AS2), RFC 3335 (AS1) and RFC 4823
Meadors Expires December 17, 2010 [Page 4]
Internet-Draft EDI-INT Features Header June 2010
(AS3).
6. Security Considerations
Because headers are often un-encrypted, it may be possible for the
EDIINT Features header to be altered. Trading partners MAY consult
out-of- band to confirm feature support.
7. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3335] Harding, T., Drummond, R., and C. Shih, "MIME-based Secure
Peer-to-Peer Business Data Interchange over the Internet",
RFC 3335, September 2002.
[RFC4130] Moberg, D. and R. Drummond, "MIME-Based Secure Peer-to-
Peer Business Data Interchange Using HTTP, Applicability
Statement 2 (AS2)", RFC 4130, July 2005.
[RFC4823] Harding, T. and R. Scott, "FTP Transport for Secure Peer-
to-Peer Business Data Interchange over the Internet",
RFC 4823, April 2007.
[RFC5234] Crocker, D. and P. Overell, "Augmented BNF for Syntax
Specifications: ABNF", STD 68, RFC 5234, January 2008.
[RFC5402] Harding, T., "Compressed Data within an Internet
Electronic Data Interchange (EDI) Message", RFC 5402,
February 2010.
Author's Address
Kyle Meadors (editor)
Drummond Group Inc.
Nashville, Tennessee 37221
US
Phone: +1 (817) 709-1627
Email: kyle@drummondgroup.com
Meadors Expires December 17, 2010 [Page 5]
Html markup produced by rfcmarkup 1.129d, available from
https://tools.ietf.org/tools/rfcmarkup/