Proposed language for clarification on the SenderNonRepudiation and ReceiverNonRepudiation elements in CPP and CPA contexts.

["Dale Moberg" <dmoberg@cyclonecommerce.com>]

Hi

I have been preparing version 2.1 that "rolls up" both errata and the
extensibility changes in schema version 2.1.

I noticed that I did not send the final errata language we had discussed
in May. I propose that we add the same
comment in two sections (8.4.43 and 8.4.54) to explain why
SignatureAlgorithm is repeatable in CPPs. Please comment 
on the list or in this week's teleconference on Friday June 11 at 8 AM
PDT. 

I think this is the last fix. I hope to have a draft of 2.1 available
for inspection around the end of June.

Thanks, 
Dale Moberg



8.4.43

The SenderNonRepudiation element is comprised of the following child
elements:
*	a REQUIRED NonRepudiationProtocol element, 
*	a REQUIRED HashFunction (e.g. SHA1, MD5) element, 
*	a REQUIRED SignatureAlgorithm element, 
*	a REQUIRED SigningCertificateRef element

When used within a CPP, the SignatureAlgorithm element can be repeated
to indicate supported capabilities. The order within a repeated list of
elements indicates comparative preference. When used within a CPA, the
SignatureAlgorithm value is the agreed upon signature algorithm.


8.4.54

The ReceiverNonRepudiation element is comprised of the following child
elements:
*	a REQUIRED NonRepudiationProtocol element (see Section 8.4.44),
*	a REQUIRED HashFunction (e.g. SHA1, MD5) element (see Section
8.4.45), 
*	a REQUIRED SignatureAlgorithm element (see Section 8.4.46), 
*	zero or one SigningSecurityDetailsRef element

When used within a CPP, the SignatureAlgorithm element can be repeated
to indicate supported capabilities. The order within a repeated list of
elements indicates comparative preference. When used within a CPA, the
SignatureAlgorithm value is the agreed upon signature algorithm.