Re: [certid] Need to define "most specific RDN"

Paul Hoffman <paul.hoffman@vpnc.org> Wed, 30 June 2010 00:31 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: certid@core3.amsl.com
Delivered-To: certid@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D4AD93A68D3 for <certid@core3.amsl.com>; Tue, 29 Jun 2010 17:31:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.659
X-Spam-Level:
X-Spam-Status: No, score=0.659 tagged_above=-999 required=5 tests=[AWL=0.105, BAYES_50=0.001, HELO_MISMATCH_COM=0.553]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lQ3RIaTVrvEK for <certid@core3.amsl.com>; Tue, 29 Jun 2010 17:31:20 -0700 (PDT)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 31E873A68C7 for <certid@ietf.org>; Tue, 29 Jun 2010 17:31:20 -0700 (PDT)
Received: from [10.20.30.158] (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id o5U0RSWT013019 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 29 Jun 2010 17:27:29 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0
Message-Id: <p06240843c8503cb6de63@[10.20.30.158]>
In-Reply-To: <4C2A6E8B.7060005@stpeter.im>
References: <p062408bcc83880a30dd0@[10.20.30.158]> <4C2A6E8B.7060005@stpeter.im>
Date: Tue, 29 Jun 2010 17:17:28 -0700
To: Peter Saint-Andre <stpeter@stpeter.im>, certid@ietf.org
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Subject: Re: [certid] Need to define "most specific RDN"
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Representation and verification of identity in certificates <certid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/certid>
List-Post: <mailto:certid@ietf.org>
List-Help: <mailto:certid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/certid>, <mailto:certid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jun 2010 00:31:20 -0000

At 4:07 PM -0600 6/29/10, Peter Saint-Andre wrote:
>Is the first RDN most specific, or is the last RDN most specific? I
>realize that the first one now will later be last [1] depending on the
>string representation, but my understanding is that in the DER encoding
>it's the first RDN that is most specific. Corrections are welcome.

This paragraph shows why it is crazy to assume that developers understand this.

First: if the RDN is a sequence, then whether it is encoded in DER or BER is irrelevant. The difference in the two encodings is only relevant for SETs.

According to RFC 5280:
   RDNSequence ::= SEQUENCE OF RelativeDistinguishedName

   RelativeDistinguishedName ::=
     SET SIZE (1..MAX) OF AttributeTypeAndValue

However, RFC 5280 does not say which of the sequence is "most specific".

--Paul Hoffman, Director
--VPN Consortium