IETF Logo Mail Archive

Re: PI: 10: draft-ietf-pkix-pi-10.txt - single serialNumber attribute

Russ Housley <housley@vigilsec.com> Thu, 22 July 2004 16:26 UTC

Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA03447 for <pkix-archive@lists.ietf.org>; Thu, 22 Jul 2004 12:26:16 -0400 (EDT)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id i6MFFbd5024051; Thu, 22 Jul 2004 08:15:37 -0700 (PDT) (envelope-from owner-ietf-pkix@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id i6MFFb8d024050; Thu, 22 Jul 2004 08:15:37 -0700 (PDT)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-pkix@mail.imc.org using -f
Received: from woodstock.binhost.com (woodstock.binhost.com [144.202.240.3]) by above.proper.com (8.12.11/8.12.9) with SMTP id i6MFFa6w024042 for <ietf-pkix@imc.org>; Thu, 22 Jul 2004 08:15:36 -0700 (PDT) (envelope-from housley@vigilsec.com)
Received: (qmail 3716 invoked by uid 0); 22 Jul 2004 15:08:24 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (138.88.94.19) by woodstock.binhost.com with SMTP; 22 Jul 2004 15:08:24 -0000
Message-Id: <6.1.1.1.2.20040722080258.08257d30@mail.binhost.com>
X-Sender: housley@mail.binhost.com
X-Mailer: QUALCOMM Windows Eudora Version 6.1.1.1
Date: Thu, 22 Jul 2004 08:08:12 -0400
To: "David P. Kemp" <dpkemp@missi.ncsc.mil>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: PI: 10: draft-ietf-pkix-pi-10.txt - single serialNumber attribute
Cc: ietf-pkix@imc.org
In-Reply-To: <200407211952.i6LJqXAJ022508@stingray.missi.ncsc.mil>
References: <73388857A695D31197EF00508B08F29806EE1B42@ntmsg0131.corpmail.telstra.com.au> <6.1.1.1.2.20040721105229.035faf80@mail.binhost.com> <40FE9323.8090306@bull.net> <200407211952.i6LJqXAJ022508@stingray.missi.ncsc.mil>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Sender: owner-ietf-pkix@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-pkix/mail-archive/>
List-ID: <ietf-pkix.imc.org>
List-Unsubscribe: <mailto:ietf-pkix-request@imc.org?body=unsubscribe>

Dave:

I reread it, and you are correct.

The first time I read it, the part that stuck with me was: "The set that 
forms an RDN contains exactly one AttributeTypeAndDistinguishedValue for 
each attribute which contains distinguished values in the entry ..."  Which 
made me think that non-distinguished values could employ a second instance 
of the same attribute type.  Not so.  It goes on to say: "... that is, a 
given attribute type cannot appear twice in the same RDN."

My issue is resolved.

Russ

At 03:57 PM 7/21/2004, David P. Kemp wrote:
>X.501 (02/2001) section 9.3, which appears to be normative,
>not informative, prohibits a given attribute type from
>appearing more than once in the same RDN.  The origin of
>Russ' comments regarding the possibility of multiple
>serialNumber attributes in a single RDN is unclear.

v2.23.0 | Report a Bug | By Email