[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Proposed Submission of XSPA Profiles for SAML & XACML to ITU (cross-post)
To OASIS members, member announce lists: OASIS has been asked, by the TC noted below, to submit the following OASIS Standards to the International Telecommunications Union, Telecommunication Standardization Sector (ITU-T), Study Group 17 on Security: XSPA Profile of SAML for Healthcare Version v1.0 [n1] XSPA Profile of XACML v2.0 for Healthcare Version v1.0 [n2] The OASIS Liaison Policy sets requirements for submissions of OASIS specifications to external standards organizations. [n3] In the case of a work produced by an active Technical Committee, OASIS rules require that the TC approve the request, which it has. The submission proposal is attached below. It includes more detailed information on the proposed submission and its terms. OASIS has determined that the proposed request meets the policy's initial requirements. Our rules provide that any such request be posted to OASIS members for comment. The member review starts today, 4 March 2010, and ends 3 April 2010. This is an open invitation to members to comment. Under our Liaison Policy, OASIS will make a final determination to confirm the submission at the close of the review period. More information about the specifications, and the XSPA TC who originated them, may be found at the public home page of the TC. [n4] Additional non-normative information about the proposed submission also may be posted to the [oasis-member-discuss] list, during the review period. This is a cross-posted copy of the original notice, found here: http://www.oasis-open.org/apps/org/workgroup/oasis-member-discuss/email/archives/201003/msg00001.html Comments on this proposed submission should be sent to that list: oasis-member-discuss@lists.oasis-open.org. It is publicly archived [n5], and any OASIS member may subscribe. [n6] The submission request is appended below. Respectfully, JBC ~ James Bryce Clark ~ General Counsel, OASIS ~ http://www.oasis-open.org/who/staff.php#clark [n1] XSPA-SAML, as approved: See http://www.oasis-open.org/specs/index.php#xspa-saml [n2] XSPA-XACML, as approved: See http://www.oasis-open.org/specs/index.php#xspa-xacml [n3] Liaison Policy: http://www.oasis-open.org/committees/liaison_policy.php#submitwork [n4] TC pages: http://www.oasis-open.org/committees/xspa [n5] List archive: http://lists.oasis-open.org/archives/oasis-member-discuss/ [n6] Comment lists & subscriptions: http://lists.oasis-open.org/archives/ ==== Proposed Submission Request terms [The six questions are quoted from the OASIS Liaison Policy] Specifications to be submitted: XSPA Profile of SAML for Healthcare Version v1.0 See http://www.oasis-open.org/specs/index.php#xspa-saml XSPA Profile of XACML v2.0 for Healthcare Version v1.0 See http://www.oasis-open.org/specs/index.php#xspa-xacml Q1. The name(s) of the submission requester(s), that is, the TC, the Member Section, or the OASIS Organizational Members that support the submission request as described in section 1(d). A1: Requested by the OASIS Cross-Enterprise Security and Privacy Authorization (XSPA) TC. Q2. The name of the intended receiving standards organization. The request may also suggest the committee or group in that organization which should process that submission. A2: ITU-T Study Group 17 on Security. Q3. The intended status or outcome that the request seeks from the receiving organization's process; and a short description of the receiving organization's approval process, including estimated time required, stages of approval and who votes at each stage. A3: Final approval as ITU Recommendations without change. Preservation of the content without alteration, except for non-technical, front-page-type matter. It is anticipated that the submission will be transmitted to ITU-T SG17, and submitted for study group consent vote at their regular plenary in April 2010, followed by an ITU member review & confirmation process that may conclude in late May. The standards to be submitted are profiles that relate to, but we expect them to be numbered separately from, SAML v2 (already submitted and approved as ITU-T X.1141) and XACML v2 (already submitted and approved as ITU-T Rec. X.1142). Q4. An explanation of how the submission will benefit OASIS. A4: Increased visibility and implementation of the established standards, due to the positive sanction associated with the ITU process. Q5. The expected licensing, copyright and other intellectual property terms that will be used by the receiving organization in regard to the submission. A5: Use of the OASIS standards is, and will continue to be, permitted under the terms of the OASIS IPR Policy. As before, our submission would call to the attention of ITU (and potential users of its works) the existence of the disclosures and license statements made pursuant to the OASIS process. See http://www.oasis-open.org/committees/xspa/ipr.php. OASIS would plan to contact any parties that make disclosures there, to advise them of the submission and the possibility of further inquiry about availability from ITU-T. Q6. A statement of the intended future plans for versioning and maintenance of the OASIS Standard and/or Approved Errata for that standard, and the expected roles of OASIS and the receiving organization. This must include clear statements of the rules of the receiving organization applicable to maintenance of an approved submitted standard, and to future versions of that standard; any requirements regarding the submission of future versions; and a description of how OASIS and the submission requesters expect to comply with those rules. A6: If the original submission is successfully approved, OASIS would enter into the usual commitments to share with ITU any material errata data, and submit back to ITU for re-transposition any future approved OASIS Standard versions or Approved Errata. As with prior ITU submissions, a condition of this OASIS submission would be the requirement that any changes to the established Specification be submitted through the OASIS TC process, in order to preserve the continuity of the work for the established base of implementers who rely on it. In this case, any such changes would be submitted to the OASIS XSPA TC, and the approval of that TC's work product through the usual OASIS process. (end of submission request)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]