OASIS eXtensible Access Control Markup Language (XACML) TC

  • 1.  RE: Media types

    Posted 04-24-2012 14:16
    Paul, >


  • 2.  RE: Media types

    Posted 04-24-2012 14:48
    Ray, OK, thanks for the references to rfc3023. I agree with your proposed types. However, I don't think this profile is the right place to define a JSON mapping for XACML. That should be a different document. Regards, --Paul >


  • 3.  Re: [xacml] RE: Media types

    Posted 04-24-2012 15:05
    On Apr 24, 2012, at 7:47 AM, Tyson, Paul H wrote: > However, I don't think this profile is the right place to define a JSON mapping for XACML. That should be a different document. Agreed. If nothing else, the scope of work of the JSON mapping should not impede the progress of defining typing IMO. b


  • 4.  RE: [xacml] RE: Media types

    Posted 04-24-2012 15:28
    Bill, Paul, >


  • 5.  RE: [xacml] RE: Media types

    Posted 04-24-2012 15:38
    All Need to define the impact on the ITU submission I suggest that we do not choose a solution that delay the submission Regards Abbie


  • 6.  RE: [xacml] RE: Media types

    Posted 05-03-2012 17:03
    The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal >


  • 7.  Re: [xacml] RE: Media types

    Posted 05-03-2012 17:32
    Re: > The progress of this specification should be completely > independent to moving the Core to OASIS Standard. Maybe "completely independent" (?) but please note: Just a reminder (though not to contradict Hal) that there is direction from IETF/IANA (and evidence of enforcement) that if an RFC is not used to define the media/mine type(s), or maybe even if so, then the definition/description of the proposed media types must be made in a **standard** when a non-IETF SSO/SDO is making the registration request. Is the XACML TC intending to approve and publish the document "XACML Media Types Version 1.0" as an OASIS Standard? Details: ====================================================== [emph added in "**  ... **"] http://tools.ietf.org/html/rfc4288#section-4.10 4.10. Publication Requirements Proposals for media types registered in the standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required.  In all cases the IANA will retain copies of all media type proposals and "publish" them as part of the media types registration tree itself. As stated previously, 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.** Such specifications MUST contain an appropriate media type registration template taken from Section 10.  Additionally, the copyright on the registration template MUST allow the IANA to copy it into the IANA registry. [...] Proposed registrations in the standards tree by other standards bodies should be communicated to the IESG (at iesg@ietf.org ) and to the ietf-types list (at ietf-types@iana.org ).  Prior posting as an Internet Draft is not required for these registrations, but may be helpful to the IESG and is encouraged. ====================================================== Tracking: Register XACML Media Type with IANA http://tools.oasis-open.org/issues/browse/TCADMIN-844 Compare: http://tools.oasis-open.org/issues/browse/TCADMIN-613 "Media Type Specifications and Registration Procedures" Request for Comments: 4288 http://tools.ietf.org/html/rfc4288 http://tools.ietf.org/html/rfc4288#section-10 See: http://tools.ietf.org/html/rfc4288#section-5.2 Please keep me in the loop here; Ray, I have some comments/corrections for the WD 02 revision of "XACML Media Types Version 1.0" - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, May 3, 2012 at 12:03 PM, Hal Lockhart < hal.lockhart@oracle.com > wrote: The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal >


  • 8.  RE: [xacml] RE: Media types

    Posted 05-03-2012 17:45
    All, Since we've now decided to define the JSON format in a separate specification instead of in the Media Types profile, I propose the following course of action: (1) Let the JSON format specification contain the IANA media type registration details for application/xacml+json (2) Register the XML format (application/xacml+xml) through an IETF RFC (3) Skip the Media Types profile altogether What do you think? Thanks, Ray From: Robin Cover [ mailto:robin@oasis-open.org ] Sent: Thursday, May 03, 2012 7:32 PM To: xacml@lists.oasis-open.org; Hal Lockhart Cc: Barbir, Abbie; Sinnema, Remon; bill@parducci.net; ptyson@bh.com; Radhakrishnan, Rakesh; Marian, Radu; Robin Cover Subject: Re: [xacml] RE: Media types Re: > The progress of this specification should be completely > independent to moving the Core to OASIS Standard. Maybe "completely independent" (?) but please note: Just a reminder (though not to contradict Hal) that there is direction from IETF/IANA (and evidence of enforcement) that if an RFC is not used to define the media/mine type(s), or maybe even if so, then the definition/description of the proposed media types must be made in a **standard** when a non-IETF SSO/SDO is making the registration request. Is the XACML TC intending to approve and publish the document "XACML Media Types Version 1.0" as an OASIS Standard? Details: ====================================================== [emph added in "**  ... **"] http://tools.ietf.org/html/rfc4288#section-4.10 4.10. Publication Requirements Proposals for media types registered in the standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required.  In all cases the IANA will retain copies of all media type proposals and "publish" them as part of the media types registration tree itself. As stated previously, 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.** Such specifications MUST contain an appropriate media type registration template taken from Section 10.  Additionally, the copyright on the registration template MUST allow the IANA to copy it into the IANA registry. [...] Proposed registrations in the standards tree by other standards bodies should be communicated to the IESG (at iesg@ietf.org) and to the ietf-types list (at ietf-types@iana.org).  Prior posting as an Internet Draft is not required for these registrations, but may be helpful to the IESG and is encouraged. ====================================================== Tracking: Register XACML Media Type with IANA http://tools.oasis-open.org/issues/browse/TCADMIN-844 Compare: http://tools.oasis-open.org/issues/browse/TCADMIN-613 "Media Type Specifications and Registration Procedures" Request for Comments: 4288 http://tools.ietf.org/html/rfc4288 http://tools.ietf.org/html/rfc4288#section-10 See: http://tools.ietf.org/html/rfc4288#section-5.2 Please keep me in the loop here; Ray, I have some comments/corrections for the WD 02 revision of "XACML Media Types Version 1.0" - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, May 3, 2012 at 12:03 PM, Hal Lockhart <hal.lockhart@oracle.com> wrote: The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal >


  • 9.  Re: [xacml] RE: Media types

    Posted 05-04-2012 03:11
    I tend to agree with Ray. It will speed things up. @Ray, are you happy for me to use the profile i had initiated to define the JSON format? Cheers, David. On Thu, May 3, 2012 at 10:45 AM, < remon.sinnema@emc.com > wrote: All, Since we've now decided to define the JSON format in a separate specification instead of in the Media Types profile, I propose the following course of action: (1) Let the JSON format specification contain the IANA media type registration details for application/xacml+json (2) Register the XML format (application/xacml+xml) through an IETF RFC (3) Skip the Media Types profile altogether What do you think? Thanks, Ray From: Robin Cover [mailto: robin@oasis-open.org ] Sent: Thursday, May 03, 2012 7:32 PM To: xacml@lists.oasis-open.org ; Hal Lockhart Cc: Barbir, Abbie; Sinnema, Remon; bill@parducci.net ; ptyson@bh.com ; Radhakrishnan, Rakesh; Marian, Radu; Robin Cover Subject: Re: [xacml] RE: Media types Re: > The progress of this specification should be completely > independent to moving the Core to OASIS Standard. Maybe "completely independent" (?) but please note: Just a reminder (though not to contradict Hal) that there is direction from IETF/IANA (and evidence of enforcement) that if an RFC is not used to define the media/mine type(s), or maybe even if so, then the definition/description of the proposed media types must be made in a **standard** when a non-IETF SSO/SDO is making the registration request. Is the XACML TC intending to approve and publish the document "XACML Media Types Version 1.0" as an OASIS Standard? Details: ====================================================== [emph added in "**  ... **"] http://tools.ietf.org/html/rfc4288#section-4.10 4.10. Publication Requirements Proposals for media types registered in the standards tree by the IETF itself MUST be published as RFCs. RFC publication of vendor and personal media type proposals is encouraged but not required.  In all cases the IANA will retain copies of all media type proposals and "publish" them as part of the media types registration tree itself. As stated previously, 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.** Such specifications MUST contain an appropriate media type registration template taken from Section 10.  Additionally, the copyright on the registration template MUST allow the IANA to copy it into the IANA registry. [...] Proposed registrations in the standards tree by other standards bodies should be communicated to the IESG (at iesg@ietf.org ) and to the ietf-types list (at ietf-types@iana.org ).  Prior posting as an Internet Draft is not required for these registrations, but may be helpful to the IESG and is encouraged. ====================================================== Tracking: Register XACML Media Type with IANA http://tools.oasis-open.org/issues/browse/TCADMIN-844 Compare: http://tools.oasis-open.org/issues/browse/TCADMIN-613 "Media Type Specifications and Registration Procedures" Request for Comments: 4288 http://tools.ietf.org/html/rfc4288 http://tools.ietf.org/html/rfc4288#section-10 See: http://tools.ietf.org/html/rfc4288#section-5.2 Please keep me in the loop here; Ray, I have some comments/corrections for the WD 02 revision of "XACML Media Types Version 1.0" - Robin Robin Cover OASIS, Director of Information Services Editor, Cover Pages and XML Daily Newslink Email: robin@oasis-open.org Staff bio: http://www.oasis-open.org/people/staff/robin-cover Cover Pages: http://xml.coverpages.org/ Newsletter: http://xml.coverpages.org/newsletterArchive.html Tel: +1 972-296-1783 On Thu, May 3, 2012 at 12:03 PM, Hal Lockhart < hal.lockhart@oracle.com > wrote: The progress of this specification should be completely independent to moving the Core to OASIS Standard. Hal >


  • 10.  RE: [xacml] RE: Media types

    Posted 05-04-2012 06:25
    David, From: xacml@lists.oasis-open.org [ mailto:xacml@lists.oasis-open.org ] On Behalf Of David Brossard Sent: Friday, May 04, 2012 5:11 AM To: Sinnema, Remon Cc: xacml@lists.oasis-open.org; robin@oasis-open.org Subject: Re: [xacml] RE: Media types > Ray, are you happy for me to use the profile i had initiated to define the JSON format? Didn't that have "HTTP" in the title? If so, can that be changed? Thanks, Ray