MIXER body mapping: FTBP with no application-reference

[David Wilson <[e-mail]>]

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                                        [e-mail]
Isode Ltd.                                       Tel: [phone]
http://www.isode.com                             Fax: [phone]