[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Timeline for XRI 2.0
Mary, Jamie: On the XRI Editor's subcommittee call today, I took the action item to check with you regarding the potential timeline for submitting the XRI 2.0 specifications for voting as an OASIS standard. With IESG approval last week (after *4 years*!) of the new URI and IRI specifications (ftp://ftp.rfc-editor.org/in-notes/rfc3986.txt and ftp://ftp.rfc-editor.org/in-notes/rfc3987.txt respectively), the only other specification on which XRI 2.0 has a dependency is SAML 2.0. And with SAML 2.0 now submitted for a vote, we can for the first time begin planning the XRI 2.0 submission timeline. I just want to confirm the TC's understanding of the following process and ask a few clarifying questions: 1) If the SAML 2.0 specification is approved without negative votes at the end of February, it will immediately become an OASIS standard. (We understand there is an up-to-30 day waiting period if there are negative votes.) Does that mean the XRI TC could being officially referencing SAML 2.0 and thus take a vote on XRI 2.0 as early as March 1? Or is there a waiting period before we can officially reference the SAML 2.0 spec (for example, before it is assigned the OASIS standard identifier we need to reference it with)? 2) Once we approve XRI 2.0 as a Committee Draft, is there any waiting period before we can start the 30 day public review period? 3) Given that a specification must be submitted by the 15th of the month, it would appear that if the XRI TC approves XRI 2.0 as a Committee Draft in early March, and begins the public review period immediately, the earliest the TC could submit the specification for a vote as an OASIS standard would be prior to April 15. In this case, if the application is complete, the member review period could begin May 1, and member voting on May 15. Have I missed anything? Are there any other factors we haven't mentioned that we should be aware of? Thanks for your help. We look forward very much to submitting XRI 2.0 for a vote as an OASIS standard. =Drummond ================ Drummond Reed CTO, Cordance Corporation Co-Chair, OASIS XRI & XDI TCs http://public.xdi.org/=Drummond.Reed -----Original Message----- From: Mary McRae [mailto:mary.mcrae@oasis-open.org] Sent: Tuesday, February 01, 2005 11:59 AM To: members@lists.oasis-open.org; tc-announce@lists.oasis-open.org Subject: [members] SAML 2.0 Specification submitted for OASIS Standard OASIS members: The OASIS Security Services TC has submitted the set of documents collectively referred to as SAML 2.0, an approved Committee Draft, to be considered as an OASIS Standard. The TC's submission is attached below. In accordance with the OASIS Technical Committee Process, the specification has already gone through a 30 day public review period. (http://lists.oasis-open.org/archives/tc-announce/200412/msg00005.html) OASIS members now have until the 15th of February to familiarize themselves with the submission below. OASIS members should give their input on this question to the voting representative of their organization. By the 16th of the month we will send out a Call For Vote to the voting representatives of the OASIS member organizations, who will have until the end of the month to cast their ballots on whether this Committee Draft should be approved as an OASIS Standard. The normative TC Process for approval of Committee Drafts as OASIS Standards is found at http://www.oasis-open.org/committees/process.php#standard Any statements related to the IPR of this specification are posted at http://www.oasis-open.org/committees/security/ipr.php Mary P McRae Manager of TC Administration, OASIS email: mary.mcrae@oasis-open.org --------------------------------- On January 15, 2005 the OASIS SAML TC voted to submit the set of documents collectively referred to as SAML 2.0 to be voted on as an OASIS Standard. We hereby provide the materials required by the OASIS TC process. 1. A formal specification that is a valid member of its type, together with appropriate documentation for the specification, both of which must be written using approved OASIS templates A consolidated zip file with all specifications and schema is publicly available from: http://www.oasis-open.org/committees/download.php/11045/sstc-saml-2.0-cd-04- pdf-xsd.zip The 8 individual SAML V2.0 PDF files (with no diff's) are publicly available at: http://www.oasis-open.org/committees/download.php/11044/sstc-saml-conformanc e-2.0-cd-04.pdf http://www.oasis-open.org/committees/download.php/11042/sstc-saml-core-2.0-c d-04.pdf http://www.oasis-open.org/committees/download.php/11040/sstc-saml-bindings-2 .0-cd-04.pdf http://www.oasis-open.org/committees/download.php/11038/sstc-saml-profiles-2 .0-cd-04.pdf http://www.oasis-open.org/committees/download.php/11036/sstc-saml-metadata-2 .0-cd-04.pdf http://www.oasis-open.org/committees/download.php/11047/sstc-saml-authn-cont ext-2.0-cd-04.pdf http://www.oasis-open.org/committees/download.php/11031/sstc-saml-sec-consid er-2.0-cd-04.pdf http://www.oasis-open.org/committees/download.php/11029/sstc-saml-glossary-2 .0-cd-04.pdf The 7 individual main SAML V2.0 schema files are publicly available at: http://www.oasis-open.org/committees/download.php/11027/sstc-saml-schema-ass ertion-2.0.xsd http://www.oasis-open.org/committees/download.php/11026/sstc-saml-schema-pro tocol-2.0.xsd http://www.oasis-open.org/committees/download.php/11025/sstc-saml-schema-ecp -2.0.xsd http://www.oasis-open.org/committees/download.php/11024/sstc-saml-schema-met adata-2.0.xsd http://www.oasis-open.org/committees/download.php/11023/sstc-saml-schema-x50 0-2.0.xsd http://www.oasis-open.org/committees/download.php/11022/sstc-saml-schema-xac ml-2.0.xsd http://www.oasis-open.org/committees/download.php/11021/sstc-saml-schema-dce -2.0.xsd The 2 individual core SAML V2.0 Authentication Context schema files are publicly available at: http://www.oasis-open.org/committees/download.php/11020/sstc-saml-schema-aut hn-context-2.0.xsd http://www.oasis-open.org/committees/download.php/11019/sstc-saml-schema-aut hn-context-types-2.0.xsd The 24 individual SAML V2.0-defined Authentication Context Class schema files are publicly available at: http://www.oasis-open.org/committees/download.php/11018/sstc-saml-schema-aut hn-context-auth-telephony-2.0.xsd http://www.oasis-open.org/committees/download.php/11017/sstc-saml-schema-aut hn-context-ip-2.0.xsd http://www.oasis-open.org/committees/download.php/11016/sstc-saml-schema-aut hn-context-ippword-2.0.xsd http://www.oasis-open.org/committees/download.php/11015/sstc-saml-schema-aut hn-context-kerberos-2.0.xsd http://www.oasis-open.org/committees/download.php/11014/sstc-saml-schema-aut hn-context-mobileonefactor-reg-2.0.xsd http://www.oasis-open.org/committees/download.php/11013/sstc-saml-schema-aut hn-context-mobileonefactor-unreg-2.0.xsd http://www.oasis-open.org/committees/download.php/11012/sstc-saml-schema-aut hn-context-mobiletwofactor-reg-2.0.xsd http://www.oasis-open.org/committees/download.php/11011/sstc-saml-schema-aut hn-context-mobiletwofactor-unreg-2.0.xsd http://www.oasis-open.org/committees/download.php/11010/sstc-saml-schema-aut hn-context-nomad-telephony-2.0.xsd http://www.oasis-open.org/committees/download.php/11009/sstc-saml-schema-aut hn-context-personal-telephony-2.0.xsd http://www.oasis-open.org/committees/download.php/11008/sstc-saml-schema-aut hn-context-pgp-2.0.xsd http://www.oasis-open.org/committees/download.php/11007/sstc-saml-schema-aut hn-context-ppt-2.0.xsd http://www.oasis-open.org/committees/download.php/11006/sstc-saml-schema-aut hn-context-pword-2.0.xsd http://www.oasis-open.org/committees/download.php/11005/sstc-saml-schema-aut hn-context-session-2.0.xsd http://www.oasis-open.org/committees/download.php/11004/sstc-saml-schema-aut hn-context-smartcard-2.0.xsd http://www.oasis-open.org/committees/download.php/11003/sstc-saml-schema-aut hn-context-smartcardpki-2.0.xsd http://www.oasis-open.org/committees/download.php/11002/sstc-saml-schema-aut hn-context-softwarepki-2.0.xsd http://www.oasis-open.org/committees/download.php/11001/sstc-saml-schema-aut hn-context-spki-2.0.xsd http://www.oasis-open.org/committees/download.php/11000/sstc-saml-schema-aut hn-context-srp-2.0.xsd http://www.oasis-open.org/committees/download.php/10999/sstc-saml-schema-aut hn-context-sslcert-2.0.xsd http://www.oasis-open.org/committees/download.php/10998/sstc-saml-schema-aut hn-context-telephony-2.0.xsd http://www.oasis-open.org/committees/download.php/10997/sstc-saml-schema-aut hn-context-timesync-2.0.xsd http://www.oasis-open.org/committees/download.php/10996/sstc-saml-schema-aut hn-context-x509-2.0.xsd http://www.oasis-open.org/committees/download.php/10995/sstc-saml-schema-aut hn-context-xmldsig-2.0.xsd 2. A clear English-language summary of the specification: The Security Assertion Markup Language (SAML) defines the syntax and processing semantics of assertions made about a subject by a system entity. In the course of making, or relying upon such assertions, SAML system entities may use other protocols to communicate either regarding an assertion itself, or the subject of an assertion. This specification defines both the structure of SAML assertions, and an associated set of protocols, in addition to the processing rules involved in managing a SAML system. SAML assertions and protocol messages are encoded in XML and use XML namespaces. They are typically embedded in other structures for transport, such as HTTP POST requests or XML-encoded SOAP messages. The SAML bindings specification provides frameworks for the embedding and transport of SAML protocol messages. The SAML profiles specification provides a baseline set of profiles for the use of SAML assertions and protocols to accomplish specific use cases or achieve interoperability when using SAML features. 3. A statement regarding the relationship of this specification to similar work of other OASIS TCs or other standards developing organizations: To our knowledge, this specification has no relationship to the work of other OASIS TCs or other standards developing organizations. 4. Certification by at least three OASIS member organizations that they are successfully using the specification consistently with the OASIS IPR Policy: (a) Trustgenix attestation of successful use of SAML 2.0: http://lists.oasis-open.org/archives/security-services/200412/msg00014.html (b) Entrust attestation of SAML 2.0 implementation: http://lists.oasis-open.org/archives/security-services/200411/msg00042.html (c) Sun Microsystems attestation of successful use of SAML V2.0: http://lists.oasis-open.org/archives/security-services/200411/msg00105.html 5. An account of each of the comments/issues raised during the public review period, along with its resolution: Available from http://lists.oasis-open.org/archives/security-services/200501/msg00070.html 6. An account of and results of the voting to approve the approve the specification as a Committee Draft: (a) Vote to affirm approval of the current specification set as a committee draft: 34 Yes, 0 No, 0 Abstain (Out of 39). Two-thirds vote required for passage. http://www.oasis-open.org/apps/org/workgroup/security/ballot.php?id=667& (b) Vote to submit current specification set to OASIS for standardization. 33 Yes, 0 No, 0 Abstain (Out of 39). Simple majority required for passage. http://www.oasis-open.org/apps/org/workgroup/security/ballot.php?id=668& 7. An account of or pointer to votes and comments received in any earlier attempts to standardize substantially the same specification, together with the originating TC's response to each comment; This specification has not previously been submitted to OASIS for standardization. 8. A pointer to the publicly visible comments archive for the originating TC; http://lists.oasis-open.org/archives/security-services-comment/ 9. A statement from the chair of the TC certifying that all members of the TC have been provided with a copy of the OASIS IPR Policy: Notice published to the list on November 30, 2004: http://lists.oasis-open.org/archives/security-services/200411/msg00131.html 10. Optionally, a pointer to any minority reports submitted by one or more TC members who did not vote in favor of approving the Committee Draft, or certification by the chair that no minority reports exist. No such report exists. _______________________________________________________________ This email list is used solely by OASIS for official consortium communications. Opt-out requests may be sent to member_services@oasis-open.org, however, all members are strongly encouraged to maintain a subscription to this list.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]