RE: Issue 087 - WS-Discovery - Incorrect reference to RFC 5280

This issue in the pending state,
however some of the changes related to this issue are no longer valid as the
reference to RFC 5280 was removed when applying the change for Issue-126. The
working draft is updated to reflect this. 

 

As part of this issue Tony
provided a feedback to clarify that the KeyId and SignatureValue are encoded in
base64 format. I have retained those changes. You can review the changes in the
working draft that I will update shortly on the website.

 

Thanks,

Vipul

 

From: Ram Jeyaraman
[mailto:] 

Sent: Monday, December 01, 2008 2:21 PM

To: 

Subject: [ws-dd] Issue 087 - WS-Discovery - Incorrect reference to RFC
5280

 

This issue is assigned the
number 087. For further discussions on this issue, please refer to this issue
number or use this thread.

From: Vipul Modi 

Sent: Wednesday, November 26, 2008 3:41 PM

To: Ram Jeyaraman

Subject: New Issue: WS-Discovery: Incorrect reference to RFC 5280

 

Document: WS-Discovery specification

Version: Working Draft 04 

 

Issue

The section 8.2 Compact Signature Format references RFC 5380
in describing the d:Security/d:Sig/@KeyId. It should be referencing RFC 5280
instead. 5380 is about  Hierarchical Mobile IPv6 (HMIPv6) Mobility
Management which has nothing to do with this section, it was an editorial
mistake. 

 

The citation of 5280 is also pointing to the wrong document.
It is currently pointing to RFC 4122. This also appears to be an editorial
cut-and-paste error.

 

Current text in Section 8.2:

d:Security/d:Sig/@KeyId 

The key identifier of the signing
token. MUST be specified if a public key token is used. If included, MUST be
Subject Key Identifier (see [RFC 5380] Section 4.2.1.2) of the signing token.
If the signing token does not have a Subject Key Identifier, it MUST be the
SHA-1 hash of the public key of the signing token. If omitted, the semantics
are undefined.

 

Proposed text in Section 8.2:

d:Security/d:Sig/@KeyId 

The key identifier of the signing
token. MUST be specified if a public key token is used. If included, MUST be
Subject Key Identifier (see [RFC 5280] Section 4.2.1.2)
of the signing token. If the signing token does not have a Subject Key
Identifier, it MUST be the SHA-1 hash of the public key of the signing token.
If omitted, the semantics are undefined. 

 

Current Text in Section 1.5

[RFC
5280]        P.
Leach, et al, A Universally Unique IDentifier (UUID) URN Namespace, http://www.ietf.org/rfc/rfc4122.txt,
IETF RFC 4122, July 2005.

 

Modified test in Section 1.5

[RFC 5280]          
D. Cooper, et al, Internet X.509 Public Key Infrastructure
Certificate and Certificate Revocation List (CRL) Profile, http://www.ietf.org/rfc/rfc5280.txt,
IETF RFC 5280, May 2008.