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

On Mon, Mar 9, 2026 at 4:25 PM Amanda Baber via RT <
[email protected]> wrote:

> On Thu Mar 05 14:59:38 2026, [email protected] wrote:
> > On Mon, Mar 2, 2026 at 12:28 PM Amanda Baber via RT <
> > [email protected]> wrote:
> >
> > > 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.
> > >
> >
> > Can we include a link to those?
>
> Privacy and integrity protection is solved by the transport layer by using
> HTTPS (TLS). The xml documents defined in TS 24.484 do all refer to OMA
> OMA-TS-XDM_Core-V2_1-20120403-A. In that document in clause 5.1.4 it is
> stated that TLS shall be supported according to RFC 2246.
>

Then I would change that last sentence to:

Mechanisms for privacy and integrity protection of these payloads can be
provided by HTTPS (TLS) and/or typical protections available to XML
payloads.

> > 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
> >
> > Are there any prior implementations of this, or versions of its
> > specification, that might result in interoperability problems with
> > this one?
>
> There has not been any prior implementation of this.
>

Thanks then, no additional changes needed.

Approved if the above change is accepted.

-MSK

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]