[media-types] [IANA #1445348] application/vnd.vnd.3g pp.mcs-location-user-config+xml registration request

"Amanda Baber via RT" <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <[email protected]>
Hi Murray,

Would you be able to review this new 3GPP request by March 16th?

thanks,
Amanda

=====

Name: Dongwook Kim

Email: [email protected]

Media type name: application

Media subtype name: vnd.3gpp.mcs-location-user-config+xml

Required parameters: N/A

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.

The information transported in this media type does not include active or executable content.

Mechanisms for privacy and integrity protection of protocol parameters exist.

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.484 "Mission Critical Services (MCS) configuration management; Protocol specification" version 19.4.0, available via https://portal.3gpp.org/desktopmodules/Specifications/SpecificationDetails.aspx?specificationId=3138

Applications which use this media: Applications supporting the location user configuration data document 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

Person to contact for further information:

1. Name: 3GPP Specifications Manager, Dongwook Kim
2. Email: [email protected]

Intended usage: COMMON

Author: 3GPP CT1 Working Group/[email protected]

Change controller: Dongwook Kim / [email protected]

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.