[media-types] [IANA #1456760] application/vnd.3gpp.s eal-store-forward-events-info+xml registration request
"Amanda Baber via RT" <[email protected]>
| Newsgroups | gmane.ietf.types |
|---|---|
| Message-ID | <[email protected]> |
Hi Darrel, Resending this request from July 28th. thanks, Amanda On Wed Jul 29 02:07:20 2026, david.dong wrote: > Hi Darrel, > > Can you review this new request for us by August 11th? > > Thank you. > > Best regards, > > David Dong > IANA Services Sr. Specialist > > > -- > > Name: Dongwook Kim > > Email: [email protected] > > Media type name: application > > Media subtype name: vnd.3gpp.seal-store-forward-events-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.548 "Network Resource Management - > Service Enabler Architecture Layer for Verticals (SEAL); Protocol > specification" version 19.1.0 and onwards, available via > https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3678. > > Applications which use this media: Applications supporting the SEAL > network resource management for the use of procedures for satellite > S&F events information 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): No > > 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: None > 5. Object Identifiers: None > > General Comments: > > Person to contact for further information: > > 1. Name: 3GPP specifications manager > 2. Email: [email protected] > > Intended usage: COMMON > > > > Author/Change controller: i) Author: 3GPP CT1 Working > Group/[email protected] > ii) Change controller: 3GPP Specifications Manager / > [email protected] _______________________________________________ media-types mailing list -- [email protected] To unsubscribe send an email to [email protected]