Dave Crocker | 6 Dec 2004 17:31

Heads up: standards spring cleaning


Rik,

Just to make sure the IETF's EDI community knows about this.  Note that RFC1767, "MIME Encapsulation of EDI
Objects" is on the list.

d/

--- Original Message ---
>  >Date: Mon, 06 Dec 2004 11:49:54 +0100
>  >From: Eliot Lear <lear <at> cisco.com>
>  >To: drums <at> cs.utk.edu, lemonade <at> ietf.org, discuss <at> apps.ietf.org
>  >Subject: standards spring cleaning
>  >
>  >Good day,
>  >
>  >I am currently involved in an experimental process to see what it
>  >would take to hold to the notion that Proposed and Draft Standards
>  >shouldn't stay in that state forever.  There are a number of mail
>  >related standards that fall into this category, and I wonder if
>  >people can tell me whether the list of standards below (or any
>  >others on the broader list) should stay or go.  The original list
>  >was generated programmatically by looking for proposed standards
>  >below RFC 2000 that are not obsoleted (we'll do draft later).
>  >
>  >Here they are:
>  >
>  >RFC1421       Privacy Enhancement for Internet Electronic Mail: Part
>  >I: Message  Encryption and Authentication Procedures
>  >RFC1422       Privacy Enhancement for Internet Electronic Mail: Part
(Continue reading)

Rik Drummond | 7 Dec 2004 01:38

FW: Heads up: standards spring cleaning


Hi Harald, I am sure you remember this one :-)

The RFC1767, MIME Encapsulation of EDI Objects, is the basis for the EDIINT
workgroup set of standards. It is basic to rfc3335 and others. Rfc3335 is
used by over a hundred thousand business across the world to support b2b
commerce. Rate of implementation is accelerating.

Please do not make it historic.
Best regards, rik drummond - Chair EDIINT WG

Internet-Drafts | 15 Dec 2004 21:45
Picon
Favicon

I-D ACTION:draft-ietf-ediint-as2-18.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Electronic Data Interchange-Internet Integration Working Group of the IETF.

	Title		: MIME-based Secure Peer-to-Peer Business Data 
			  Interchange Using HTTP, Applicability Statement 2 (AS2)
	Author(s)	: D. Moberg, R. Drummond
	Filename	: draft-ietf-ediint-as2-18.txt
	Pages		: 42
	Date		: 2004-12-15
	
This document provides a applicability statement (RFC 2026, 3.2)
   that describes how to exchange structured business data securely
   using the HTTP transfer protocol, instead of SMTP; the
   applicability statement for SMTP is found in RFC 3335. Structured
   business data may be XML, Electronic Data Interchange
   (EDI) in either the American National Standards Committee (ANSI)
   X12 format, or in the UN Electronic Data Interchange for
   Administration, Commerce and Transport (UN/EDIFACT) format,
   or in other structured data formats. The data is packaged using
   standard MIME structures. Authentication and data confidentiality
   are obtained by using Cryptographic Message Syntax with S/MIME
   security body parts. Authenticated acknowledgements make use of
   multipart/signed Message Disposition Notification (MDN)
   responses to the original HTTP message. This applicability
   statement is informally referred to as "AS2" because it is the
   second applicability statement, produced after "AS1," RFC 3335.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-ediint-as2-18.txt

(Continue reading)


Gmane