OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xacml message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xacml] 15-day Public Review for JSON Profile of XACML 3.0 v1.0 - ends June 12th



Hi David,

Since we're on the subject, a couple of days ago I noticed that Section 5.2.2
says that a Result object has:

•	PolicyIdentifierList: this object is optional.

PolicyIdentifierList isn't described anywhere, but there is a description of a
PolicyIdentifier object in Section 5.2.11. I assume they're the same thing
and one of these sections is using the wrong name.

More below.

On 29/05/2014 5:09 AM, David Brossard wrote:
Hi Mohammad,

Many thanks for your comments. They are very helpful. It is extremely unfortunate though that you've come with them so late especially when the profile has been 3 years in the making.

Please see my comments below.


On Wed, May 28, 2014 at 7:47 PM, Mohammad Jafari <mjafari@edmondsci.com <mailto:mjafari@edmondsci.com>> wrote:

    Hello, ____

    __ __

    I finally got a chance to review this draft. I uploaded my annotated copy to the repository here <https://www.oasis-open.org/apps/org/workgroup/xacml/download.php/53153>.____

    __ __

    There are two main issues that I noticed:____

    __ __

    - Section 4.2.3 says that there is an option to encode XML contents as Base64 or escaped XML but there is no additional property to indicate what encoding has been used. If this is meant to be left to inference, it should be stated and preferably the inference mechanism should be described.

We debated that on a XACML TC call and there wasn't really any consensus. If I recall well, Steven Legg was in favor of stating what encoding we use. I believe I was in favor of inference.

I thought the conversation was more about whether we need both alternatives.
I was of the opinion that the escaped XML was sufficient since it will be
more compact, more readable and more efficient to process than base64.


Now that we have inference (We can always change that in a v.2 I suppose), I do not believe it is the profile's role to state how to do it. That's implementation-specific. However I am already seeing that this inference will be rather expensive code-wise.

Noting that my lexical analyser passes back a string with all the JSON
character escapes taken care of, I just look for some optional leading
whitespace followed by a '<' character. A valid XML encoding has to
begin this way and a base64 encoding can never begin this way. If the
string is all whitespace, then it is empty content and it doesn't
matter what the encoding is.

Regards,
Steven


    ____

    __ __

    - Section 6 prescribes using “application/json” while later on “application/xacml+json” is prescribed. Is this a typo or is it intended (perhaps because the communication is between XACML PEP and PDP)?


As specified at https://www.iana.org/assignments/media-types/application/vnd.xacml+json (the IANA website), the type is xacml+json. Section 7 is correct. Section 6 is wrong.

    ____

    __ __

    Also I suggest including the XACML XML equivalent of the examples in Section 8.

On a previous call I mentioned I would provide the examples later. Some profiles provide the examples separately from the actual profile. I don't know whether I will do it that way but one thing I do want to do is provide the examples as separate self-contained files to avoid the copy-paste issues.

    ____

    __ __

    There are also various editorial issues:____

    - Font discrepancy: the use of fonts for the XML elements and JSON property names is not consistent throughout the document.____

    - I think tables should be captioned and referenced rather than being inline although I am not sure if OASIS has any rules about this.____

    - Referencing style to sections is not consistent; sometimes only a number is given, sometimes number is given with “section” and sometimes the entire title is included. I think using “Section” and number is more readable but even if another style is used it should be followed consistently.

Thanks, I will look into that.

    ____

    __ __

    __ __

    Regards,____

    Mohammad Jafari, Ph.D.____

    Security Architect, Edmond Scientific Company


Cheers and thanks for the very sharp eyes.

    ____

    __ __

    __ __

    __ __

    __ __

    *From:*xacml@lists.oasis-open.org <mailto:xacml@lists.oasis-open.org> [mailto:xacml@lists.oasis-open.org <mailto:xacml@lists.oasis-open.org>] *On Behalf Of *Chet Ensign
    *Sent:* Wednesday, May 28, 2014 7:42 AM
    *To:* tc-announce@lists.oasis-open.org <mailto:tc-announce@lists.oasis-open.org>; members@lists.oasis-open.org <mailto:members@lists.oasis-open.org>; xacml@lists.oasis-open.org <mailto:xacml@lists.oasis-open.org>; xacml-comment@lists.oasis-open.org <mailto:xacml-comment@lists.oasis-open.org>
    *Subject:* [xacml] 15-day Public Review for JSON Profile of XACML 3.0 v1.0 - ends June 12th____

    __ __

    OASIS members, ____

    __ __

    The OASIS eXtensible Access Control Markup Language (XACML) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review:____

    __ __

    JSON Profile of XACML 3.0 Version 1.0____

    Committee Specification Draft 03 / Public Review Draft 03____

    15 May 2014____

    __ __

    With these releases we are testing a convenience option for submitting comments to the Technical Committee. Please see the details under ‘Public Review Period’ below.____

    __ __

    Specification Overview:____

    __ __

    The aim of this profile is to propose a standardized interface between a policy enforcement point and a policy decision point using JSON. The decision request and response structure is specified in the core XACML specification. This profile leverages it. ____

    __ __

    This document was previously titled “Request / Response Interface based on JSON and HTTP for XACML 3.0 Version 1.0.” ____

    __ __

    TC Description: ____

    __ __

    The XACML Technical Committee defines a core XML schema for representing authorization and entitlement policies. ____

    __ __

    Public Review Period:____

    __ __

    The public review starts 29 May 2014 at 00:00 GMT and ends 12 June 2014 at 23:59 GMT. The specification was previously submitted for public review [2]. This 15-day review is limited in scope to changes made from the previous review. Changes are highlighted in the diff-marked PDF file [3]. ____

    __ __

    This is an open invitation to comment. OASIS solicits feedback from potential users, developers and others, whether OASIS members or not, for the sake of improving the interoperability and quality of its technical work.____

    __ __

    With this public review, we are testing a new convenience feature for sending comments to the Technical Committee. The file:____

    __ __

    http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd03/xacml-json-http-v1.0-csprd03-COMMENT-TAGS.html ____

    __ __

    contains the HTML version of the draft with a “[comment?]” link next to each section heading. Clicking on this link will launch your email application and begin a message to xacml-comment@lists.oasis-open.org <mailto:xacml-comment@lists.oasis-open.org> with the specific section number and title in the subject line. (For example, “Public review comment for xacml-json-http-v1.0-csprd03: 1.1 References”) Simply enter your comment and click send.____

    __ __

    You must be subscribed to the xacml-comment@lists.oasis-open.org <mailto:xacml-comment@lists.oasis-open.org> mailing list in order to send your comments. Instructions on how to subscribe can be found at https://www.oasis-open.org/committees/comments/index.php?wg_abbrev=xacml.____

    __ __

    Note that the Table of Contents doesn’t work in this version and other internal document links may not work in these files. That is one of the items we need fix before making this capability more broadly available. Please feel free to let us know if you find this feature helpful. We plan to refine it and make it a part of our normal public review process.____

    __ __

    URIs:____

    The prose specification document and related files are available here:____

    __ __

    Editable source (Authoritative):____

    http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd03/xacml-json-http-v1.0-csprd03.doc ____

    __ __

    HTML: ____

    http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd03/xacml-json-http-v1.0-csprd03.html ____

    __ __

    PDF:____

    http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd03/xacml-json-http-v1.0-csprd03.pdf____

    __ __

    ZIP distribution files (complete):____

    __ __

    For your convenience, OASIS provides a complete package of the prose specification and related files in a ZIP distribution file. You can download the ZIP file here:____

    __ __

    http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd03/xacml-json-http-v1.0-csprd03.zip____

    __ __

    Additional information about the specification and the OASIS eXtensible Access Control Markup Language (XACML) TC may be found at the TC's public home page located at:____

    __ __

    http://www.oasis-open.org/committees/xacml/____

    __ __

    Comments may be submitted to the TC by any person through the use of the OASIS TC Comment Facility which can be accessed via the button labeled "Send A Comment" at the top of the TC public home page, or directly at:____

    __ __

    http://www.oasis-open.org/committees/comments/form.php?wg_abbrev=xacml____

    __ __

    Feedback submitted by TC non-members for this work and for other work of this TC is publicly archived and can be viewed at:____

    __ __

    http://lists.oasis-open.org/archives/xacml-comment/____

    __ __

    All comments submitted to OASIS are subject to the OASIS Feedback License, which ensures that the feedback you provide carries the same obligations at least as the obligations of the TC members. In connection with this public review of “JSON Profile of XACML 3.0 Version 1.0,” we call your attention to the OASIS IPR Policy [4] applicable especially [5] to the work of this technical committee. All members of the TC should be familiar with this document, which may create obligations regarding the disclosure and availability of a member's patent, copyright, trademark and license rights that read on an approved OASIS specification. ____

    __ __

    OASIS invites any persons who know of any such claims to disclose these if they may be essential to the implementation of the above specification, so that notice of them may be posted to the notice page for this TC's work.____

    __ __

    ========== Additional references:____

    __ __

    [1] OASIS eXtensible Access Control Markup Language (XACML) TC____

    http://www.oasis-open.org/committees/xacml/____

    __ __

    [2] Previous public reviews: ____

    __ __

    30-day public review, 21 August 2013: https://lists.oasis-open.org/archives/members/201308/msg00014.html____

       Comment resolution log: http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd01/xacml-json-http-v1.0-csprd01-comment-log.xls____

    __ __

    15-day public review, 30 October 2014: https://lists.oasis-open.org/archives/members/201310/msg00017.html____

    - Comment resolution log: http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd02/xacml-json-http-v1.0-csprd02-comment-resolution-log.xls ____

    __ __

    [3] Redlined DIFF file: http://docs.oasis-open.org/xacml/xacml-json-http/v1.0/csprd03/xacml-json-http-v1.0-csprd03-diff.pdf____

    __ __

    [4] http://www.oasis-open.org/policies-guidelines/ipr____

    __ __

    [5] http://www.oasis-open.org/committees/xacml/ipr.php____

    http://www.oasis-open.org/who/intellectualproperty.php#s10.2.3____

    RF on Limited Terms____

    __ __

    --

    /chet
    ----------------
    Chet Ensign
    Director of Standards Development and TC Administration
    OASIS: Advancing open standards for the information society
    http://www.oasis-open.org

    Primary: +1 973-996-2298 <tel:%2B1%20973-996-2298>
    Mobile: +1 201-341-1393 <tel:%2B1%20201-341-1393> ____

    __ __

    Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html

    TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

    Follow OASIS on:
    LinkedIn: http://linkd.in/OASISopen
    Twitter: http://twitter.com/OASISopen
    Facebook: http://facebook.com/oasis.open____




--
David Brossard, M.Eng, SCEA, CSTP
VP of Customer Relations
+46(0)760 25 85 75
Axiomatics AB
Skeppsbron 40
S-111 30 Stockholm, Sweden
Support: https://support.axiomatics.com
Web: http://www.axiomatics.com <http://www.axiomatics.com/>
Axiomatics for developers: http://developers.axiomatics.com
Connect with us on LinkedIn <http://www.linkedin.com/companies/536082> | Twitter <http://twitter.com/axiomatics> | Google + <https://plus.google.com/u/1/b/101496487994084529291/> | Facebook <https://www.facebook.com/axiomatics> | YouTube <http://www.youtube.com/user/axiomaticsab>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]