Registration of MIME media type Application/EDI-Tradacoms

[Larry Masinter]

This registration refers to RFC 1767. Now, RFC 1767 already contains 3
media type registrations, but does not mention "tradacoms". So it is
difficult to tell what is actually meant by the registration as it is
currently written.
 
Also, since RFC 1767 is a standards track document, normally the "change
controller" would be the IETF rather than a private individual/company.
 
 
 
 

     MIME media type name: Application    
 
     MIME subtype name: IETF Tree - EDI-Tradacoms
 
     Required parameters: None
 
     Optional parameters: CHARSET, as defined for MIME
 
     Encoding considerations: May need BASE64 or QUOTED-PRINTABLE
transfer encoding on transports not capable of handling 8 BIT text
 
     Security considerations: Refer to RFC 1767 Section 7
 
     Interoperability considerations: None
 
     Published specification: Refer to RFC 1767
 
     Applications which use this media type: EDI, EDIINT
 
     Additional information:
 
       Magic number(s): none
       File extension(s): none
       Macintosh File Type Code(s): none
 
     Person & email address to contact for further information:
            Name: Kyle Meadors
            Email: kyle at drummondgroup.com
 
     Intended usage: COMMON. UK EDI standard to support EDIINT AS2 in UK
 
     Author/Change controller: Drummond Group Inc.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.alvestrand.no/pipermail/ietf-types/attachments/20031118/bfb34a25/attachment.html