Media Type review request for application/dialog-info+xml
Rohan Mahy
rohan at ekabal.com
Tue Jan 25 17:53:45 CET 2005
Hi,
This format is unlikely to be fetched from a web server, but if it is,
the behavior described for .xml sounds appropriate to me. Since this
format is unlikely to be stored permanently in a file system it makes
sense not to reserve a new 3-character extension.
thanks,
-rohan
On Jan 24, 2005, at 17:39, Bjoern Hoehrmann wrote:
> * Martin Duerst wrote:
>> At 04:30 05/01/25, Bjoern Hoehrmann wrote:
>>> * Allison Mankin wrote:
>>>> The Transport Area requests a Media Type review for the proposed
>>>> new type application/dialog-info+xml, intended for the IETF tree,
>>>> and specified
>>>> http://www.ietf.org/internet-drafts/draft-ietf-sipping-dialog-
>>>> package-05.txt
>>>> (Section 8.1).
>>>
>>> Why does it list .xml as file extension?
>>
>> Is there anything wrong with using a .xml extension? If yes, what?
>
> Well, e.g. RFC 3236 states:
>
> [...]
> It is not recommended that the ".xml" extension (defined in
> [XMLMIME]) be used, as web servers may be configured to
> distribute such content as type "text/xml" or
> "application/xml". [XMLMIME] discusses the unreliability of
> this approach in section 3. Of course, should the author
> desire this behaviour, then the ".xml" extension can be used.
> [...]
> --
> Björn Höhrmann · mailto:bjoern at hoehrmann.de ·
> http://bjoern.hoehrmann.de
> Weinh. Str. 22 · Telefon: +49(0)621/4309674 ·
> http://www.bjoernsworld.de
> 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
More information about the Ietf-types
mailing list