(RFC 5730 published August 2009, subtype last updated August 2009)

MIME media type name: application

MIME subtype name: epp+xml

Required parameters: none

Optional parameters: Same as the charset parameter of application/xml
as specified in [RFC3023].

Encoding considerations: Same as the encoding considerations of
application/xml as specified in [RFC3023].

Security considerations: This type has all of the security
considerations described in [RFC3023] plus the considerations
specified in the Security Considerations section of this document.

Interoperability considerations: XML has proven to be interoperable
across WWW Distributed Authoring and Versioning (WebDAV) clients and
servers, and for import and export from multiple XML authoring tools.
For maximum interoperability, validating processors are recommended.
Although non-validating processors can be more efficient, they are
not required to handle all features of XML.  For further information,
see Section 2.9, "Standalone Document Declaration", and Section 5,
"Conformance", of [W3C.REC-xml-20040204].

Published specification: This document.

Applications that use this media type: EPP is device-, platform-, and
vendor-neutral and is supported by multiple service providers.

Additional information: If used, magic numbers, fragment identifiers,
base URIs, and use of the BOM should be as specified in [RFC3023].

Magic number(s): None.

File extension(s): .xml

Macintosh file type code(s): "TEXT"

Person & email address for further information: See the "Author's
Address" section of this document.

Intended usage: COMMON

Author/Change controller: IETF