MIXER body mapping: FTBP with no application-reference
David Wilson <D.Wilson@isode.com> Fri, 04 April 1997 15:27 UTC
Received: from cnri by ietf.org id aa16081; 4 Apr 97 10:27 EST
Received: from ietf.org by CNRI.Reston.VA.US id aa10840; 4 Apr 97 10:27 EST
Received: from ietf.org by ietf.org id aa16074; 4 Apr 97 10:27 EST
Received: from woozle.isode.com by ietf.org id aa16070; 4 Apr 97 10:27 EST
Received: from isode.com (actually sirius.isode.com) by woozle.isode.com with SMTP (local); Fri, 4 Apr 1997 16:24:43 +0100
X-Mailer: exmh version 1.6.7 5/3/96
To: iesg@ietf.org, ietf-mixer@innosoft.com
cc: Harald.T.Alvestrand@uninett.no, S.Kille@isode.com, D.Wilson@isode.com
Subject: MIXER body mapping: FTBP with no application-reference
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 04 Apr 1997 16:24:42 +0100
Message-ID: <27299.860167482@isode.com>
Sender: iesg-request@ietf.org
From: David Wilson <D.Wilson@isode.com>
I have found (one) UA that generates File Transfer Bodyparts that nearly conform to the MAWG profile, but don't contain an application-reference. draft-ietf-mixer-bodymap-06.txt Section 3.3 states: "- Creating the "content-type" value by forming the string "application/x-ftp." and appending the numbers of the OID" It is not explicit that the OID in question is the OID in the FileTransferParameters.environment.application-reference.registered-identifier If the FileTransferData conforms to the MAWG profile, i.e. there is a single EXTERNAL containing unstructured-binary, and the FileTransferParameters. contents-type is unstructured-binary, then it is more useful to a potential MIME recipient to have the actual data rather than the application/x400-bp holding the encoding of the whole Ftbp, even if there is no application-reference.registered-identifier. The existing text of section 3.3 allows the such Ftbps to be mapped, but the above paragraph needs to be changed to something like: - Creating the "content-type" value by forming the string "application/x-ftbp". If the FileTransferParameters.environment. application-reference.registered-identifier has a value, then the each number in the OID is appended to the content-type, using dots as separators. This then specifies the MIME Content-type for the case when the application- reference.registered-identifier is not present. regards David Wilson D.Wilson@isode.com Isode Ltd. Tel: +44 181 332 9091 http://www.isode.com Fax: +44 181 332 9019
- MIXER body mapping: FTBP with no application-refeā¦ David Wilson