Filename Preservation for EDIINT
draft-harding-ediint-filename-preservation-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Terry Harding | ||
| Last updated | 2010-04-01 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
The intent of this document is to be placed on the RFC track as an Informational RFC. The EDIINT [AS1], [AS2] and [AS3] message formats do not currently contain any provisions for preservation of the filename of a transmitted EDI business document from one Trading Partner to another. However,within certain trading communities, it is not uncommon for Trading Partners to require a specific filenames for EDI business documents to trigger specific backend processing. So it is the goal of this informational document to outline the procedures and mechanisms required to preserve filenames of EDI business documents.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)