OASIS eXtensible Access Control Markup Language (XACML) TC

 View Only
  • 1.  Minutes 4 January, 2024 XACML TC meeting

    Posted 01-04-2024 20:31
    Time: 2:30 PM EDT Tel: 267-807-9601 Minutes for 4 January 2024 TC Meeting I. Roll Call & Minutes Voting members Hal Lockhart (Co-Chair) Bill Parducci (Co-Chair) Steven Legg Cyril Dangerville Voting Companies: 3 of 4 (75% - quorum) Approve Minutes 9 November, 2023 TC Meeting Vote: Approved unanimously. Related and Nested Entities Profile, Version 1.0 Public Review Closed 20 December, 2023 Hal: No comments were received. The next step is to Request Chairs submit to TC Admin for Committee Specification consideration via public review and comment. Steven: I move that the Chairs submit Related and Nested Entities Profile, Version 1.0 posted at: https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/csd03/xacml-3.0-related-entities-v1.0-csd03.docx to TC-Admin for Public Review and Comment Bill: I second. Hal: Hearing no objections, the Chairs are directed to submit CSD03 to TC-Admin XACML v3.0 Separation of Duties Profile, Version 1.0 Public Review closed 4 January, 2024 Hal: No comments were received. The next step is to Request Chairs submit to TC Admin for Committee Specification consideration via public review and comment. Steven: I move that the Chairs submit Separation of Duties, Version 1.0 posted at: https://docs.oasis-open.org/xacml/xacml-3.0-duties/v1.0/csd01/xacml-3.0-duties-v1.0-csd01.docx to TC-Admin for Public Review and Comment Bill: I second. Hal: Hearing no objections, the Chairs are directed to submit CSD01 to TC-Admin. GitHub Communications Bill: I am working with TC Admin to make the TC list an Observer on the TC s github repos so that we have a single place to capture our process and decisions. Open Policy Agent doc - Comparison to XACML Cyril reviewed the changes that he submitted to correct and clarify the references to XACML on the Open Policy site. XACML TC web page Bill: I will be updating the TC web page once TC Admin has updated the backend systems to refresh the XACML page. I ll reach out for input when that process begins. New Oasis Backend Systems Hal: TC Admin has said that the process continues and will be delivered a bit later than originally scheduled. III. Issues XACML versioning Hal: Is the TC considering working on a backward compatible version of the Core Specification (v3.1) as well as a version that introduces non-backward compatible features. Steven: The issue with pursuing a v3.1 would require dragging along features that are being replaced in the v3.1 enhancement. There is general consensus that the TC consider what would be in v3.1 vs v4.0 to determine which path makes the most sense to pursue from the perspective of increased value. Open Issues The TC reviewed and discussed the open issues in GitHub, including the use case for justifying the proposed changes to variable definitions. Cyril also reviewed which issues would be suited for v3.1 and/or 4.0 The TC will begin developing a list of features for each approach to begin determining the scope of each effort. There is general consensus that JSON should be playing a larger role within the specification. There is also general consensus that the existing TC wiki page should be migrated into gitHub. Meeting adjourned. Next meeting: 29 February, 2024. Same time.


  • 2.  Minutes 4 January, 2024 XACML TC meeting - UPDATED

    Posted 01-24-2024 04:44
    Time: 2:30 PM EDT Tel: 267-807-9601 Minutes for 4 January 2024 TC Meeting I. Roll Call & Minutes Voting members Hal Lockhart (Co-Chair) Bill Parducci (Co-Chair) Steven Legg Cyril Dangerville Voting Companies: 3 of 4 (75% - quorum) Approve Minutes 9 November, 2023 TC Meeting Vote: Approved unanimously. Related and Nested Entities Profile, Version 1.0 Public Review Closed 20 December, 2023 Hal: No comments were received. The next step is to Request Chairs submit to TC Admin for Committee Specification consideration via public review and comment. Steven: I move that the TC approve the Chair requesting a Special Majority Ballot to make Related and Nested Entities Profile, Version 1.0 contained in: https://docs.oasis-open.org/xacml/xacml-3.0-related-entities/v1.0/csd03/xacml-3.0-related-entities-v1.0-csd03.docx a Committee Specification. Bill: I second. Hal: Hearing no objections, the Chairs are directed to submit CSD03 to TC-Admin for a vote on it becoming a Committee Specification. XACML v3.0 Separation of Duties Profile, Version 1.0 Public Review closed 4 January, 2024 Hal: No comments were received. The next step is to Request Chairs submit to TC Admin for Committee Specification consideration via public review and comment. Steven: I move that the TC approve the Separation of Duties, Version 1.0 posted at: https://docs.oasis-open.org/xacml/xacml-3.0-duties/v1.0/csd01/xacml-3.0-duties-v1.0-csd01.docx a Committee Specification. Bill: I second. Hal: Hearing no objections, the Chairs are directed to submit CSD01 to TC-Admin for a vote on it becoming a Committee Specification. GitHub Communications Bill: I am working with TC Admin to make the TC list an Observer on the TC s github repos so that we have a single place to capture our process and decisions. Open Policy Agent doc - Comparison to XACML Cyril reviewed the changes that he submitted to correct and clarify the references to XACML on the Open Policy site. XACML TC web page Bill: I will be updating the TC web page once TC Admin has updated the backend systems to refresh the XACML page. I ll reach out for input when that process begins. New Oasis Backend Systems Hal: TC Admin has said that the process continues and will be delivered a bit later than originally scheduled. III. Issues XACML versioning Hal: Is the TC considering working on a backward compatible version of the Core Specification (v3.1) as well as a version that introduces non-backward compatible features. Steven: The issue with pursuing a v3.1 would require dragging along features that are being replaced in the v3.1 enhancement. There is general consensus that the TC consider what would be in v3.1 vs v4.0 to determine which path makes the most sense to pursue from the perspective of increased value. Open Issues The TC reviewed and discussed the open issues in GitHub, including the use case for justifying the proposed changes to variable definitions. Cyril also reviewed which issues would be suited for v3.1 and/or 4.0 The TC will begin developing a list of features for each approach to begin determining the scope of each effort. There is general consensus that JSON should be playing a larger role within the specification. There is also general consensus that the existing TC wiki page should be migrated into gitHub. Meeting adjourned. Next meeting: 29 February, 2024. Same time.