Document Action: 'Multiple Attachments for EDI-INT' to Informational RFC (draft-meadors-multiple-attachments-ediint-14.txt)
The IESG <iesg-secretary@ietf.org> Sat, 23 July 2011 15:59 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08E4621F85EE for <ietf-announce@ietfa.amsl.com>; Sat, 23 Jul 2011 08:59:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.524
X-Spam-Level:
X-Spam-Status: No, score=-102.524 tagged_above=-999 required=5 tests=[AWL=0.075, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OLJwgcuUn6i0; Sat, 23 Jul 2011 08:59:49 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 04A3D21F8A66; Sat, 23 Jul 2011 08:59:49 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Document Action: 'Multiple Attachments for EDI-INT' to Informational RFC (draft-meadors-multiple-attachments-ediint-14.txt)
X-Test-IDTracker: no
X-IETF-IDTracker: 3.56
Message-ID: <20110723155949.6809.47549.idtracker@ietfa.amsl.com>
Date: Sat, 23 Jul 2011 08:59:49 -0700
Cc: RFC Editor <rfc-editor@rfc-editor.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 Jul 2011 15:59:50 -0000
The IESG has approved the following document: - 'Multiple Attachments for EDI-INT' (draft-meadors-multiple-attachments-ediint-14.txt) as an Informational RFC This document has been reviewed in the IETF but is not the product of an IETF Working Group. The IESG contact person is Pete Resnick. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-meadors-multiple-attachments-ediint/ Technical Summary The EDI-INT AS1, AS2 and AS3 messages were designed specifically for the transport of EDI documents. Since multiple interchanges could be placed within a single EDI document, there was not a need for sending multiple EDI documents in a single message. As adoption of EDI-INT grew, other uses developed aside from single EDI document transport. Some transactions required multiple attachments to be interpreted together and stored in a single message. This informational draft describes how multiple documents, including non-EDI payloads, can be attached and transmitted in a single EDI-INT transport message. The attachments are stored within the MIME Multipart/Related structure. A minimal list of content-types to be supported as attachments is provided. Working Group Summary This is not a WG document. It was originally submitted as an Independent Submission to RFC Editor, but after a discussion between the author, sponsoring AD and ISE it was decided that it is suitable for the IETF stream. Document Quality There are at least 8 different implementations of this extension. Personnel Pete Resnick is the Responsible Area Director. RFC Editor Note In Section 2.5, please add to the end of the 1st paragraph: Existing text: Documents of the following MIME media types MAY be found in a multipart/related envelope and MUST be accepted by the user agent. However, any media type can be used depending upon industry need, and other media types MAY be accepted depending upon trading partner agreement. ADD: Please see [MIMEREG] for the definitions of the Media Types listed below. In Section 2.5 delete: DELETE: application/vnd.ms-excel, application/x-msexcel DELETE: image/bmp In Section 3, in the example: OLD: protocol="application/pkcs7-signature"; micalg=sha1; NEW: protocol="application/pkcs7-signature"; micalg=sha-1; Add the following reference to the list of Normative References: [MIMEREG] http://www.iana.org/assignments/media-types/index.html