Browse Prior Art Database

Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field (RFC6017)

IP.com Disclosure Number: IPCOM000199824D
Original Publication Date: 2010-Sep-01
Included in the Prior Art Database: 2010-Sep-17
Document File: 10 page(s) / 9K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

K. Meadors: AUTHOR [+2]

Abstract

EDIINT 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 EDIINT standards. Since these features go beyond (but do not violate) the basic premise of EDIINT, a means is needed to communicate to trading partners features that 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.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 31% of the total text.

Independent Submission                                   K. Meadors, Ed. Request for Comments: 6017                           Drummond Group Inc. Category: Informational                                   September 2010 ISSN: 2070-1721

       Electronic Data Interchange - Internet Integration (EDIINT)                          Features Header Field

Abstract

   With the maturity of the Electronic Data Interchange - Internet    Integration (EDIINT) 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    EDIINT applications and could cause potential problems with    implementations.  The EDIINT-Features header field provides a means    to resolve these problems and support new functionality.

Status of This Memo

   This document is not an Internet Standards Track specification; it is    published for informational purposes.

   This is a contribution to the RFC Series, independently of any other    RFC stream.  The RFC Editor has chosen to publish this document at    its discretion and makes no statement about its value for    implementation or deployment.  Documents approved for publication by    the RFC Editor are not a candidate for any level of Internet    Standard; see Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6017.

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.

Meadors                       Informational                     [Page 1]
 RFC 6017                                                  September 2010

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 2        1.1.  Requirements Language . . . . . . . . . . . . . . . . . . 2    2.  EDIINT-Features Header Syntax . . . . . . . . . . . . . . . . . 2    3.  Implementation and Processing . . . . . . . . . . . . . . . . . 3    4.  EDIINT Applications . . . . . . . . . . . . . . . . . . . . . . 3    5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 3    6.  Security Considerations . . . . . . . . . . . . . . . . . . . . 4    7.  Normat...