idnits 2.17.1 draft-murata-xml-09.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3023 5 Title: XML Media Types 6 Author(s): M. Murata, S. St.Laurent, D. Kohn 7 Status: Standards Track 8 Date: January 2001 9 Mailbox: mmurata@trl.ibm.co.jp, simonstl@simonstl.com, 10 dan@dankohn.com 11 Pages: 39 12 Characters: 86011 13 Updates: 2376 15 I-D Tag: draft-murata-xml-09.txt 17 URL: ftp://ftp.isi.edu/in-notes/rfc3023.txt 19 This document standardizes five new media types -- text/xml, 20 application/xml, text/xml-external-parsed-entity, 21 application/xml-external-parsed-entity, and application/xml-dtd -- 22 for use in exchanging network entities that are related to the 23 Extensible Markup Language (XML). This document also standardizes a 24 convention (using the suffix '+xml') for naming media types outside 25 of these five types when those media types represent XML MIME 26 (Multipurpose Internet Mail Extensions) entities. XML MIME entities 27 are currently exchanged via the HyperText Transfer Protocol on the 28 World Wide Web, are an integral part of the WebDAV protocol for remote 29 web authoring, and are expected to have utility in many domains. 31 Major differences from RFC 2376 are (1) the addition of 32 text/xml-external-parsed-entity, 33 application/xml-external-parsed-entity, and application/xml-dtd, (2) 34 the '+xml' suffix convention (which also updates the RFC 2048 35 registration process), and (3) the discussion of "utf-16le" and 36 "utf-16be". 38 This is now a Proposed Standard Protocol. 40 This document specifies an Internet standards track protocol for 41 the Internet community, and requests discussion and suggestions 42 for improvements. Please refer to the current edition of the 43 "Internet Official Protocol Standards" (STD 1) for the 44 standardization state and status of this protocol. Distribution 45 of this memo is unlimited. 47 This announcement is sent to the IETF list and the RFC-DIST list. 48 Requests to be added to or deleted from the IETF distribution list 49 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 50 added to or deleted from the RFC-DIST distribution list should 51 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 53 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 54 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 55 help: ways_to_get_rfcs. For example: 57 To: rfc-info@RFC-EDITOR.ORG 58 Subject: getting rfcs 60 help: ways_to_get_rfcs 62 Requests for special distribution should be addressed to either the 63 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 64 specifically noted otherwise on the RFC itself, all RFCs are for 65 unlimited distribution.echo 66 Submissions for Requests for Comments should be sent to 67 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 68 Authors, for further information.