[media-types] [IANA #1419698] RE: IANA media type reg istrations from 3GPP (follow-up from #1379064)
"Amanda Baber via RT" <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Hi Darrel, 3GPP has one more media type for us. Can you review this by June 10th? thanks, Amanda ===== Media Type Name: Application Subtype name: vnd.3gpp.seal-data-delivery-info+xml Required parameters: None Optional parameters: "charset": the parameter has identical semantics to the charset parameter of the "application/xml" media type as specified in section 9.1 of IETF RFC 7303. Encoding considerations: binary Security considerations: Same as general security considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. In addition, this media type provides a format for exchanging information in HTTP. Hence, the security considerations from IETF RFC 2616 apply while exchanging information in HTTP. The information transported in this media type does not include active or executable content. This media type does not include provisions for directives that institute actions on a recipient's files or other resources. This media type does not include provisions for directives that institute actions that, while not directly harmful to the recipient, may result in disclosure of information that either facilitates a subsequent attack or else violates a recipient's privacy in any way. This media type does not employ compression. Interoperability considerations: Same as general interoperability considerations for application/xml media type as specified in section 9.1 of IETF RFC 7303. Any unknown XML elements and any unknown XML attributes are to be ignored by recipient of the MIME body. Published specification: 3GPP TS 24.543 "Data Delivery Management - Service Enabler Architecture Layer for Verticals (SEAL)", available via https://www.3gpp.org/ftp/Specs/archive/24_series/24.543. Applications which use this media type: Applications supporting the SEAL Data delivery management as described in the published specification. Fragment identifier considerations: The handling in section 5 of IETF RFC 7303 applies. Restrictions on usage: None Provisional registration? (standards tree only): N/A Additional information: 1. Deprecated alias names for this type: none 2. Magic number(s): none 3. File extension(s): none 4. Macintosh File Type Code(s): none 5. Object Identifier(s) or OID(s): none Intended usage: COMMON Person to contact for further information: - Name: 3GPP Specifications Manager - Email: [email protected] Author/Change controller: i) Author: 3GPP CT1 Working Group/[email protected] ii) 3GPP Specifications Manager, [email protected] _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]