Re: [kmip] Groups - KMIP v.1.1 Updates for Converting Certificate EncodedValues to Text Strings (v3KMIP1.1ConversiontoStringProposal.doc) uploaded

[Bruce Rich <brich@us.ibm.com>]

Judy,

The RFC that you wish us to use to produce
canonical Issuer Distinguished Name strings (RFC 2253) seem to leave a
fair amount of wiggle room.  For example, section 4 requires implementations
to accept variant forms that I think will be interoperability issues.
In particular, language like 

   Implementations MUST
allow a semicolon character to be used instead
   of a comma to separate RDNs in a distinguished name, and MUST also
   allow whitespace characters to be present on either side of the
comma
   or semicolon.  The whitespace characters are ignored, and
the
   semicolon replaced with a comma.

   Implementations MUST allow an oid in the attribute type to be
   prefixed by one of the character strings "oid." or "OID.".

   Implementations MUST allow for space (' ' ASCII 32) characters
to be
   present between name-component and ',', between attributeTypeAndValue
   and '+', between attributeType and '=', and between '=' and
   attributeValue.  These space characters are ignored when parsing.

   Implementations MUST allow a value to be surrounded by quote ('"'
   ASCII 34) characters, which are not part of the value.  Inside
the
   quoted value, the following characters can occur without any
   escaping:

                   ",",
"=", "+", "<", ">", "#"
and ";"

is really worrisome.  Section 4
was put in to tolerate older apps, so would it be acceptable to modify
your proposal to OMIT the variants required in section 4?

Bruce A Rich
brich at-sign us dot ibm dot com




From:      
 Judith.Furlong@emc.com
To:      
 kmip@lists.oasis-open.org
Date:      
 08/10/2011 03:46 PM
Subject:    
   [kmip] Groups
- KMIP v.1.1 Updates for Converting Certificate Encoded Values to  
Text Strings (v3KMIP1.1ConversiontoStringProposal.doc) uploaded

---

Changed shoulds to SHALLs

 -- Ms. Judith Furlong

The document revision named KMIP v.1.1 Updates for Converting Certificate
Encoded Values to Text Strings (v3KMIP1.1ConversiontoStringProposal.doc)
has been submitted by Ms. Judith Furlong to the OASIS Key Management
Interoperability Protocol (KMIP) TC document repository.  This document
is
revision #2 of KMIP1.1UGASN.1toStringProposal.doc.

Document Description:
This addresses Topic 4 of the open PKI items.

Converted from a proposal against the UG to a proposal agains the Spec
as
of revision 2

View Document Details:
http://www.oasis-open.org/committees/document.php?document_id=43168

Download Document:  
http://www.oasis-open.org/committees/download.php/43168/v3KMIP1.1ConversiontoStringProposal.doc

Revision:
This document is revision #2 of KMIP1.1UGASN.1toStringProposal.doc.  The
document details page referenced above will show the complete revision
history.


PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy
and paste
the entire link address into the address field of your web browser.

-OASIS Open Administration