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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ws-sx message

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


Subject: New Issue: Change key to crucial in SC text


PLEASE DO NOT REPLY TO THIS EMAIL OR START A DISCUSSISON THREAD UNTIL THE ISSUE IS ASSIGNED A NUMBER.  
The issues coordinators will notify the list when that has occurred.
 
Title: Change key to crucial in SC text
Protocol:  ws-sc 
Artifact:  spec 
Type: editorial
 
Description: 

The word “key” is used too many times in the sentences below. I suggest the word “crucial” as a substitute.

 

Proposal:

 

Section 4

Proof of possession of the key associated with the security context MUST be proven in order for context to be amended. It is RECOMMENDED that the proof of possession is done by creating a signature over the message body and key crucial headers using the key associated with the security context

 

Change key headers to crucial headers in example.

 

 

Section 5

Proof of possession of the key associated with the security context MUST be proven in order for security context to be renewed. It is RECOMMENDED that this is done by creating the original claims signature over the signature that signs message body and key crucial headers.

 

Change key headers to crucial headers in example.

 

 

Section 6

Proof of possession of the key associated with the security context MUST be proven in order for security context to be cancelled. It is RECOMMENDED that this is done by creating a signature over the message body and key crucial headers using the key associated with the security context.

 

Change key headers to crucial headers in example.

 

 

Section 8

Change key headers to crucial headers in example.

 

 



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