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

 


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-member-discuss message

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


Subject: Re: [oasis-member-discuss] Proposed Submission of OASIS WS-Security v1.1 ...


Last month, certain OASIS members proposed, under the terms of our
Liaison Policy, that OASIS send the OASIS Standard:

WS-Security v1.1

to the International Telecommunications Union, Telecommunication
Standardization Sector (ITU-T), Study Group 17 on Security, for its
further approval as an ITU-T Recommendation.  This proposal was
announced to OASIS members here:
    http://lists.oasis-open.org/archives/oasis-member-discuss/201003/msg00000.html
for member comment.  Our policy on submissions to outside organizations is here:
    http://www.oasis-open.org/committees/liaison_policy.php#submitwork

The review period has closed;  a number of comments were posted to our
[oasis-member-discuss] list, which is archived here:
    http://lists.oasis-open.org/archives/oasis-member-discuss/
We appreciate the input that was provided.  Particularly, the five
members who originally proposed the submission, along with four other
members, many of who were involved in the original WS-Security TC,
proposed that we instead submit the OASIS Standard to ISO/IEC Joint
Technical Committee 1 (JTC1).  That proposal appears here:
    http://lists.oasis-open.org/archives/oasis-member-discuss/201004/msg00001.html

Submitting WS-Security to JTC1 does not necessary rule out a future
submission to ITU-T as well, and it is our plan to discuss with ITU-T
representatives, as well as the JTC1 leadership, what feasible methods
may be available, as a practical matter, for additional or cooperative
submissions.  While we will pursue those conversations, and maintain
our liaison relationships will all relevant stakeholders, in light of
the unanimous view of the members who voiced an opinion, the best
course seems to be to submit to JTC1 now.

The Liaison Policy permits us to change the terms of submission stated
in the original notice to members, by announcing those changes here.

The submission has been approved, on the *modified* terms noted below.
 These are altered only slightly from the original proposed terms
posted last month, to reflect the change of recipient organization.
OASIS plans to confirm the transmission of the standards to JTC1
shortly, as provided by our policy.

MODIFIED TERMS OF SUBMISSION

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:  CA, Fujitsu, HP, IBM, Microsoft, Oracle, Red Hat, SAP

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:  ISO / IEC JTC1.  OASIS will request that, if administrative
responsibility for resolution or transposition is required, it be
assigned to JTC1's SC38 (Distributed Application Platforms &
Services).

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 an ISO/IEC International Standard under the
JTC1 Publicly Available Specifications ("PAS") submission rules for
qualified SDOs like OASIS who are certified as PAS submitters.
Preservation of the content without alteration, except for
non-technical, front-page-type matter.  It is anticipated that the
submission will be transmitted to JTC1 for a PAS mail ballot vote,
usually 6 months in duration, in early May 2010.

Q4. An explanation of how the submission will benefit OASIS.

A4:  Increased visibility and implementation of the established
standard, due to the positive sanction associated with the JTC1
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 standard is, and will continue to be, permitted
under the terms of the OASIS IPR Policy. As with prior PAS
submissions, our submission would call to the attention of JTC1 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/wss/ipr.php),  OASIS plans to
contact parties listed there, to advise them of this submission, and
the possibility of further inquiry about availability from JTC1.

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 JTC1 any material
errata data, and submit back to JTC1 for re-transposition any future
approved OASIS Standard versions or Approved Errata.  OASIS and JTC1
have an established maintenance routine, used in prior successful PAS
submissions, based on our Liaison Policy's submission terms.  As
before, 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, because the originating TC has completed its work, any such
changes would be conditioned on the competent convening of a new OASIS
TC, under all applicable OASIS rules, and the approval of that TC's
work through the usual OASIS process.

Respectfully, JBC

~ James Bryce Clark
~ General Counsel, OASIS


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