headers
Internet-Drafts | 5 May 2008 19:30
Picon
Favicon

I-D Action:draft-ietf-ediint-compression-11.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           : Compressed Data within an Internet EDI Message
	Author(s)       : T. Harding
	Filename        : draft-ietf-ediint-compression-11.txt
	Pages           : 7
	Date            : 2008-05-05

This document explains the rules and procedures for utilizing 
compression (RFC 3274) within an Internet EDI (Electronic
Data Interchange) 'AS' message, as defined in RFCs 3335, 4130,
and 4823.

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

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
Attachment (draft-ietf-ediint-compression-11.txt): message/external-body, 70 bytes
_______________________________________________
I-D-Announce mailing list
I-D-Announce <at> ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
(Continue reading)

Permalink | Reply |
headers
Alberti Antoine | 29 Mar 2004 16:43
Favicon

RE: I-D ACTION:draft-ietf-ediint-as3-02.txt


I have a few comments about this draft:

Globally: Why did you skip 2 lines after each line?

2.1: Why is it that a trading application must not embed an FTP server to work without an external one?

4.2: Once again, this chapter is essential, but does not state anything. This bullet representation is not
standardized, and does not clarify things. On the other hand, RFC 2119 defines how things should be
litteraly described without ambiguity. EDI-INT uses subsets of RFCs. For example, this draft only uses
multipart-signed for signing using S/MIME, and RFC 2634 defines a behavior about "triple wrapping". So
what is an application supposed to do with the other cases that are technically valid? What does a sender
MUST/MAY do, and what does a receiver MUST/MUST NOT support? To be a bit more technical, this draft is based
on many other high-level standards, so how can a developper do to integrate existing libraries that have
complete support of the underlying standards, and which functions does he have to restrict?
When you add "(encrypted)", does this mean that the corresponding layer encrypts, or that it may be
indirectly encrypted by an outermost layer?

6.1: This is a detail, and the choice of using this word is not technically illegal, but SFTP is an existing
and totally different protocol.
While talking about authentication, is there any link between FTP authentication, AS3-To, AS3-From, and certificates?

6.2: "Large files are handled correctly by the TCP layer". I agree (actually the TCP layer does not handle
files, so this does not sound false), but why is this sentence here? This section looks more like a
discussion about compression than about large files, doesn't it?

7.2 paragraph 2: I don't really get the diagram. What is the "[FTP Server]", for instance? From 2.1, we can
guess that trading applications only embed FTP clients, using an intermediate server. So why is it that
this diagram does not represent it?
By the way, the FTP cinematic is not described: how do partners "send" a message or an MDN? Which upload
(Continue reading)

Permalink | Reply |
headers
Alberti Antoine | 4 Feb 2004 10:54
Favicon

RE: I-D ACTION:draft-ietf-ediint-compression-03.txt


As for AS.2 and AS.3, I think section '1.2 Structure of an EDI MIME message utilizing compression' could be
enhanced with a bit of text to explain how RFCs are used.

But more important, it seems that Transfer Encoding diserves a discussion: mail infrastructures (AS.1)
require 7 bit data, so base64 encoding, while HTTP (AS.2) restricts it. This issue is raised for the cases
where the MIME layer directly containing the compressedData is not encapsulated within another layer.

Regards.

> -----Message d'origine-----
> De : owner-ietf-ediint <at> mail.imc.org
> [mailto:owner-ietf-ediint <at> mail.imc.org]De la part de
> Internet-Drafts <at> ietf.org
> Envoyé : mardi 3 février 2004 21:45
> Cc : ietf-ediint <at> imc.org
> Objet : I-D ACTION:draft-ietf-ediint-compression-03.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		: Compressed Data for EDIINT
> 	Author(s)	: T. Harding
> 	Filename	: draft-ietf-ediint-compression-03.txt
> 	Pages		: 5
> 	Date		: 2004-2-3
>
(Continue reading)

Permalink | Reply |
headers
Albin, Stephen | 6 Apr 2001 20:03
Favicon

RE: I-D ACTION:draft-ietf-ediint-as2-08.txt

I was able to retrieve it via FTP following the below instructions. Also try
ftp://ietf.org/internet-drafts/draft-ietf-ediint-as2-08.txt

-Steve Albin

-----Original Message-----
From: RPalermo <at> levi.com [mailto:RPalermo <at> levi.com]
Sent: Friday, April 06, 2001 9:19 AM
To: Lowerys <at> meijer.com; bpommerenke <at> hotmail.com; ietf-ediint <at> imc.org
Cc: ctoublanc <at> influe.com
Subject: RE: I-D ACTION:draft-ietf-ediint-as2-08.txt

Ditto for me as well....

-----Original Message-----
From: Steve Lowery [mailto:Lowerys <at> meijer.com]
Sent: Friday, April 06, 2001 8:03 AM
To: bpommerenke <at> hotmail.com; ietf-ediint <at> imc.org
Cc: ctoublanc <at> influe.com
Subject: Re: I-D ACTION:draft-ietf-ediint-as2-08.txt

I received the same message. I tried to get the file via email. Attached is
the response.

>>> "Benoit Pommerenke" <bpommerenke <at> hotmail.com> 04/06/01 10:21AM >>>
For :
http://www.ietf.org/internet-drafts/draft-ietf-ediint-as2-08.txt 
Got : HTTP 404 - File not found
Benoit.
(Continue reading)

Permalink | Reply |
headers
RPalermo | 6 Apr 2001 18:18
Favicon

RE: I-D ACTION:draft-ietf-ediint-as2-08.txt

Ditto for me as well....

-----Original Message-----
From: Steve Lowery [mailto:Lowerys <at> meijer.com]
Sent: Friday, April 06, 2001 8:03 AM
To: bpommerenke <at> hotmail.com; ietf-ediint <at> imc.org
Cc: ctoublanc <at> influe.com
Subject: Re: I-D ACTION:draft-ietf-ediint-as2-08.txt

I received the same message. I tried to get the file via email. Attached is
the response.

>>> "Benoit Pommerenke" <bpommerenke <at> hotmail.com> 04/06/01 10:21AM >>>
For :
http://www.ietf.org/internet-drafts/draft-ietf-ediint-as2-08.txt 
Got : HTTP 404 - File not found
Benoit.

----- Original Message -----
From: <Internet-Drafts <at> ietf.org>
To: <IETF-Announce:>
Cc: <ietf-ediint <at> imc.org>
Sent: Friday, April 06, 2001 3:50 PM
Subject: I-D ACTION:draft-ietf-ediint-as2-08.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.
>
(Continue reading)

Permalink | Reply |
headers
Steve Lowery | 6 Apr 2001 17:03
Favicon

Re: I-D ACTION:draft-ietf-ediint-as2-08.txt

I received the same message. I tried to get the file via email. Attached is the response.

>>> "Benoit Pommerenke" <bpommerenke <at> hotmail.com> 04/06/01 10:21AM >>>
For :
http://www.ietf.org/internet-drafts/draft-ietf-ediint-as2-08.txt 
Got : HTTP 404 - File not found
Benoit.

----- Original Message -----
From: <Internet-Drafts <at> ietf.org>
To: <IETF-Announce:>
Cc: <ietf-ediint <at> imc.org>
Sent: Friday, April 06, 2001 3:50 PM
Subject: I-D ACTION:draft-ietf-ediint-as2-08.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 : HTTP Transport for Secure EDI
> Author(s) : D. Moberg, D. Brooks, R. Drummond
> Filename : draft-ietf-ediint-as2-08.txt
> Pages : 25
> Date : 05-Apr-01
>
> This document describes how to exchange structured business data
> securely using HTTP transport for EDIFACT, X12, XML or other
> used for business to business data interchange. The data is packaged
> using standard MIME content-types. Authentication and privacy are
(Continue reading)

Permalink | Reply |

Gmane