Re: [ws-sx] Proposed WS-SX motion

[Frederick Hirsch <frederick.hirsch@nokia.com>]

Proposed revised charter clarification motion based on WS-SX discussion:

Changes:
MOTION, s/amended/clarified
k s/mechanisms/protocol mechanisms
k s/SASL/SASL mechanisms

MOTION:
Shall the charter of the OASIS WS-SX TC be clarified as follows?

Modify the following sentence in the charter:
c. Specifying the scope of each returned security token using WS-
Policy [5] <wsp:AppliesTo>.

TO READ AS FOLLOWS:
c. Specifying the scope of each requested and returned security token
using WS-Policy [5] <wsp:AppliesTo> (eg. wsa:endpointReference).

After the following sentence in the charter:
j. Specifying characteristics of the requested type of keys.

ADD THE SENTENCE AS FOLLOWS:
k. Enabling additional negotiation and challenge protocol mechanisms  
to be used (e.g.
SASL mechanisms, SPNEGO) initiated by either client or server.

Modify the following sentence in the charter:
2. Actions and elements for responding with a renewed token.

TO READ AS FOLLOWS:
2. Actions and elements for responding with a renewed token (or tokens).

Modify the following sentence in the charter:
2. Actions and elements for responding about the validity of a token.

TO READ AS FOLLOWS:
2. Actions and elements for responding about the validity of a token
(or tokens).

After the following sentence in the charter:
7. Definition of APIs

ADD THE SENTENCES THAT FOLLOW:
8. Definition of additional negotiation and challenge protocol
mechanisms.
9. Developing the roadmaps [15], [16] or other specifications
mentioned in those roadmaps, beyond the material listed explicitly as
within the scope of this charter.

regards, Frederick

Frederick Hirsch
Nokia




On Dec 7, 2005, at 2:09 PM, ext Frederick Hirsch wrote:

> Here is the proposed motion for a WS-SX charter clarification, and  
> attached are redline and clean PDF versions with the changes:
>
> MOTION:
> Shall the charter of the OASIS WS-SX TC be amended as follows?
>
> Modify the following sentence in the charter:
> c. Specifying the scope of each returned security token using WS- 
> Policy [5] <wsp:AppliesTo>.
>
> TO READ AS FOLLOWS:
> c. Specifying the scope of each requested and returned security  
> token using WS-Policy [5] <wsp:AppliesTo> (eg. wsa:endpointReference).
>
> After the following sentence in the charter:
> j. Specifying characteristics of the requested type of keys.
>
> ADD THE SENTENCE AS FOLLOWS:
> k. Enabling additional negotiation and challenge mechanisms (e.g.  
> SASL, SPNEGO) initiated by either client or server.
>
> Modify the following sentence in the charter:
> 2. Actions and elements for responding with a renewed token.
>
> TO READ AS FOLLOWS:
> 2. Actions and elements for responding with a renewed token (or  
> tokens).
>
> Modify the following sentence in the charter:
> 2. Actions and elements for responding about the validity of a token.
>
> TO READ AS FOLLOWS:
> 2. Actions and elements for responding about the validity of a  
> token (or tokens).
>
> After the following sentence in the charter:
> 7. Definition of APIs
>
> ADD THE SENTENCES THAT FOLLOW:
> 8. Definition of additional negotiation and challenge protocol  
> mechanisms.
> 9. Developing the roadmaps [15], [16] or other specifications  
> mentioned in those roadmaps, beyond the material listed explicitly  
> as within the scope of this charter.
>
> ----
> END
>
> <WS-SX-Charter-Clarification-clean.pdf>
> <WS-SX-Charter-Clarification-redline.pdf>
> <mime-attachment.txt>