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

Approval announcement
Draft of message to be sent after approval:

From: The IESG <iesg-secretary@ietf.org>
To: RFC Editor <rfc-editor@rfc-editor.org>, rfc-ise@rfc-editor.org
Cc: The IESG <iesg@ietf.org>, <iana@iana.org>, ietf-announce@ietf.org
Subject: Re: Informational RFC to be:

The IESG has no problem with the publication of 'EDI-INT Features Header'
<draft-meadors-ediint-features-header-07.txt> as an Informational RFC.

The IESG would also like the IRSG or RFC-Editor to review the comments in
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Alexey Melnikov.

A URL of this Internet-Draft is:

The process for such documents is described at

Thank you,

The IESG Secretary

Technical Summary

   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.

Working Group Summary

   This document is not the result of any IETF Working Group,
   it is an independent submission to the RFC Editor.

Document Quality
   Alexey Melnikov has reviewed this specification for conflict with
   IETF work and for comflict with IETF processes as specified in
   RFC 5742.


   Alexey Melnikov is the Responsible Area Director.

RFC Editor Note

   The IESG believes that this work doesn't conflict with any work
   done in IETF, so it has no note to insert into this document,
   and no objection to its publication.

   Note that the document is currently waiting for new email/web
   header field approval from the designated IANA expert.