Re: Spec updated

Hi Shivaram -

Attached is a zipfile contgaining the spec samples.  The samples that
changed are

- Part1-Paragraph-252-RegisterResult.xml
- Part1-Paragraph-267-RecoverRequest.xml
- Part1-Paragraph-268-RecoverResult.xml

Also, Appendix C.txt  contains the complete Appendix C.

There appears to be an inconsistency between the strings mentioned in
paragraph [248] and C.1.3 - I chose to use the string mentioned in
C.1.3  (3N9CJ-K4JKS-04JWF-0934J-SR09JW-IK4) and paragraph [248]
therefore needs modification - the string mentioned there is currently
3n9cj-jk4jk-s04jf-20934-jsr09-jwik4.

Regards
Tommy

On Mon, 14 Feb 2005 20:30:54 -0800 (PST), Shivaram Mysore
<shivarammysore@yahoo.com> wrote:
> Folks, 
>   
> I have updated the editor's draft of the spec [1].  I request everyone to go
> thro' the spec and notify me of any more changes.  
>   
> Tommy, could you please verify the samples once more and send  me any
> changes/updates. 
>   
> The following are the updates to the spec: 
>  
> Fixed Issue - section 8.1 - deleted para [329] and inserted paras [329a]
> [329b] [329c] and reference para [397b] for SASLPREP 
> Fixed Issue 328-jr - PART 2 of the SPEC 
> Fixed Issue 330-tlr-1 - Replaced AbstractRequestType with
> RequestAbstractType in paras [111] and [128] 
> Fixed Issue 330-tlr-2 - updated para [189] by modifying explanation for
> ValidityInterval 
> Fixed Issue 330-tlr-3 - deleted the first 2 sentences in para [288] as
> suggested; Added clarification statement in para [363] about guessing of
> shared secrets. 
> Fixed Issue 331 - Servers may ignore an UnverifiedKeyBinding's Indeterminate
> value as status value & Clients may set an Indeterminate status value.
> Updated Paras [205] [221] 
> Fixed Section 9 - Conformance Section - 
> Samples Updated - 
> Editorial update para [179] - Replaced "<UseKeyWith>element"for "one use key
> with" 
> Replaced all instances of QNames with anyURIs - paras [100] [104] [119]
> [120] [122] [208] [209] 
> 
> Also, the Appendix E Changes have been updated with a new way of recording
> changes.  This is in preparation for PR.  I have also been maintaining the
> current way of logging changes - which will be removed just before this goes
> PR. 
> 
> I will update Part 2 of the spec soon 
> 
> /Shivaram
> 
>  
> --
> Secure Web Services, PKI, Software Architecture, Java, 
> Product Strategy and Management Consultant:
> http://www.geocities.com/shivarammysore/