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] Next steps on the XACML COSs


I will try to summarize the comments and our alternatives. The comments attributed to me are as a member of the TC NOT as chair.

 

There are two proposed OS documents, the REST Profile and the JSON Profile.

 

We have comments on both from Cyril Dangerville. There were also general comments on XACML which are outside the scope of this Public Review.

 

REST - https://lists.oasis-open.org/archives/xacml-comment/201712/msg00000.html

 

Cyril inquired about behavior relating to endpoints. Steven Legg responded essentially that the wording gives implementers a lot of leeway and that Cyril’s approach is conformant.

 

I agree with Steven and therefore suggest we treat these comments as suggestions for improvement of the spec.

 

JSON - https://lists.oasis-open.org/archives/xacml-comment/201712/msg00004.html

 

Cyril reports: 2 typos, an datatype error in one example and an suggestion for security considerations.

 

 

I believe we can consider all of these changes as non-material. Clearly we can fix the typos. If the TC wants I can tackle wording of the proposed improvements.

 

Therefore I believe we can do any of the following:

 

1.       Make no changes

2.       Fix the typos and declare them to be non-material changes.

3.       Fix the typos and add text in accordance with Cyril’s other suggestions.

 

If we do other than #1, I believe we can conduct the necessary ballots electronically prior to the next call in 4 weeks.

 

We should decide today what path to take.

 

Hal

 

 

From: Hal Lockhart
Sent: Thursday, January 11, 2018 1:56 PM
To: xacml@lists.oasis-open.org
Cc: bill parducci <bill@parducci.net>
Subject: RE: [xacml] Next steps on the XACML COSs

 

I ask all the TC members to take a look at the comments and Chet’s message and decide what you think we should do. It would be particularly helpful if we could hear from our implementers, but everyone’s opinion is important. Ideally if we could get some discussion and even consensus before our next call on Feb 1.

 

This might allow editors to begin work, if any is required, on the specs.

 

Hal

 

From: Chet Ensign [mailto:chet.ensign@oasis-open.org]
Sent: Wednesday, January 10, 2018 10:58 AM
To: Hal Lockhart <hal.lockhart@oracle.com>; bill parducci <bill@parducci.net>
Cc: xacml@lists.oasis-open.org; Paul Knight <paul.knight@oasis-open.org>
Subject: [xacml] Next steps on the XACML COSs

 

Happy New Year, Bill, Hal and members of the XACML TC. 

 

I am writing regarding the next steps on your two Candidate OASIS Standards. As you know, the public review period closed on January 6th and you did receive comments. I don't include the overall negative comments from Mr. Limaye since they were directed at the main XACML specification. However,  you did have comments from Mr. Dangerville. 

 

 

First, please put together the usual comment resolution log for us to load along with the COS files. 

 

Next, if the TC does not wish to make any changes to the COSs, then please assign me to run a Special Majority Vote to get the TC's agreement to continue with the call for consent. Please just use the 'other purpose' ticket at https://www.oasis-open.org/resources/tc-admin-requests/request-a-special-majority-vote-for-other-procedural-reqest and indicate that the TC would like to vote on proceeding. 

 

If, on the other hand, the TC does wish to make some Non-Material changes in response to the comments, please let me know and we will discuss the details on how to go about doing that. 

 

Thanks & as always, let me know if you have any questions. 


/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
Mobile: +1 201-341-1393 



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