FW: [ietf-types] Registration of media types application/xacmlpolicy+xml, application/xacmlrequest+xml, and application/xacmlresponse+xml

[<remon.sinnema@emc.com>]

All,

It looks like our options for registering XACML media types are:
1) Update the specification to include a section on media types
2) Produce a separate specification document specifically for media types
3) Go through the IETF RFC process

I would guess that option 2) is probably fastest? What do you think?

Thanks,
Ray


> -----Original Message-----
> From: Bjoern Hoehrmann [mailto:derhoermi@gmx.net]
> Sent: Saturday, December 03, 2011 6:50 PM
> To: Sinnema, Remon
> Cc: xacml@lists.oasis-open.org; ietf-types@iana.org
> Subject: Re: [ietf-types] Registration of media types
> application/xacmlpolicy+xml, application/xacmlrequest+xml, and
> application/xacmlresponse+xml
> 
> * <remon.sinnema@emc.com> wrote:
> >Section 4.10 states:
> >
> >"standards tree registrations for media types defined in documents
> >produced by other standards bodies MUST be described by a formal
> >standards specification produced by that body."
> >
> >Does that mean we first have to have a committee specification that
> >prescribes the use of a media type, before we can register said media
> >type with IANA?
> 
> The general idea is that the format specification would have a section
> that registers the media type, but you could also have a "media types
> for XACML" specification or something along that line. Without that, it
> would still be possible to register the types through the RFC process,
> like when the standards organization has a format specification but
> does
> not want to update it to include the registration information and also
> does not want to publish a separate registration specificiation. It may
> also be sufficient if there is some understanding that these things
> will
> materialize within a reasonable time frame (IETF types are registered
> when the IESG approves an Internet-Draft for publication as RFC, but it
> typically takes several months before the RFC is actually published).
> 
> If none of that sounds like an option, there is also the option to use
> different names, say `application/vnd.oasis.xacml...`.
> 
> So yeah, it would be better if you have something, but the timing and
> the procedural formalities are not overarching concerns.
> --
> Björn Höhrmann · mailto:bjoern@hoehrmann.de ·
> http://bjoern.hoehrmann.de
> Am Badedeich 7 · Telefon: +49(0)160/4415681 ·
> http://www.bjoernsworld.de
> 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/