RFC 6362 on Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)

rfc-editor@rfc-editor.org Fri, 26 August 2011 21:50 UTC

Return-Path: <wwwrun@rfc-editor.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 92DCC21F8C54 for <ietf-announce@ietfa.amsl.com>; Fri, 26 Aug 2011 14:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.497
X-Spam-Level:
X-Spam-Status: No, score=-102.497 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7sdIPZdwr63l for <ietf-announce@ietfa.amsl.com>; Fri, 26 Aug 2011 14:50:32 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 270C521F8A62 for <ietf-announce@ietf.org>; Fri, 26 Aug 2011 14:50:32 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 30D7998C24E; Fri, 26 Aug 2011 14:51:38 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6362 on Multiple Attachments for Electronic Data Interchange - Internet Integration (EDIINT)
From: rfc-editor@rfc-editor.org
Message-Id: <20110826215138.30D7998C24E@rfc-editor.org>
Date: Fri, 26 Aug 2011 14:51:38 -0700
Cc: 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: Fri, 26 Aug 2011 21:50:32 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 6362

        Title:      Multiple Attachments for Electronic Data 
                    Interchange - Internet Integration (EDIINT) 
        Author:     K. Meadors, Ed.
        Status:     Informational
        Stream:     IETF
        Date:       August 2011
        Mailbox:    kyle@drummondgroup.com
        Pages:      8
        Characters: 15137
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-meadors-multiple-attachments-ediint-14.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6362.txt

The Electronic Data Interchange - Internet Integration (EDIINT) 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 EDIINT 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 RFC describes how
multiple documents, including non-EDI payloads, can be attached and
transmitted in a single EDIINT 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.
This document is not an Internet Standards Track specification; it is
published for informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC