6. IANA Considerations
This specification defines two new Internet media types [RFC6838].
6.1. application/problem+json
Type name: application
Subtype name: problem+json
Required parameters: None
Optional parameters: None; unrecognized parameters should be ignored
Encoding considerations: Same as [RFC7159]
Security considerations: see Section 5 of this document
Interoperability considerations: None
Published specification: RFC 7807 (this document)
Applications that use this media type: HTTP
Fragment identifier considerations: Same as for application/json ([RFC7159])
Additional information:
- Deprecated alias names for this type: n/a
- Magic number(s): n/a
- File extension(s): n/a
- Macintosh file type code(s): n/a
Person and email address to contact for further information:
Mark Nottingham <[email protected]>
Intended usage: COMMON
Restrictions on usage: None.
Author: Mark Nottingham <[email protected]>
Change controller: IESG
6.2. application/problem+xml
Type name: application
Subtype name: problem+xml
Required parameters: None
Optional parameters: None; unrecognized parameters should be ignored
Encoding considerations: Same as [RFC7303]
Security considerations: see Section 5 of this document
Interoperability considerations: None
Published specification: RFC 7807 (this document)
Applications that use this media type: HTTP
Fragment identifier considerations: Same as for application/xml (as specified by Section 5 of [RFC7303])
Additional information:
- Deprecated alias names for this type: n/a
- Magic number(s): n/a
- File extension(s): n/a
- Macintosh file type code(s): n/a
Person and email address to contact for further information:
Mark Nottingham <[email protected]>
Intended usage: COMMON
Restrictions on usage: None.
Author: Mark Nottingham <[email protected]>
Change controller: IESG