IETF Logo Mail Archive

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

=JeffH <Jeff.Hodges@KingsMountain.com> Sat, 03 July 2010 05:47 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
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 E6CA83A657C for <certid@core3.amsl.com>; Fri, 2 Jul 2010 22:47:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.302
X-Spam-Level:
X-Spam-Status: No, score=-0.302 tagged_above=-999 required=5 tests=[AWL=0.474, BAYES_05=-1.11, IP_NOT_FRIENDLY=0.334]
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 utBOFv-K5Qnz for <certid@core3.amsl.com>; Fri, 2 Jul 2010 22:47:52 -0700 (PDT)
Received: from cpoproxy1-pub.bluehost.com (cpoproxy1-pub.bluehost.com [69.89.21.11]) by core3.amsl.com (Postfix) with SMTP id 9EFE13A6823 for <certid@ietf.org>; Fri, 2 Jul 2010 22:47:47 -0700 (PDT)
Received: (qmail 16152 invoked by uid 0); 3 Jul 2010 05:47:36 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy1.bluehost.com with SMTP; 3 Jul 2010 05:47:36 -0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=kingsmountain.com; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=LOhDF6noBvzJGGKpkPBWYoLXGTI/KVCfrxDXcEm6bxt/mWDk0byzPNFGWmOq9OPm1tm5PopOWa2L8YTAk2GDVOfJ3W2BTLkeLnRexGwJX0OOL+9AmAOd+GHR31gCrimB;
Received: from c-24-4-122-173.hsd1.ca.comcast.net ([24.4.122.173] helo=[192.168.11.10]) by box514.bluehost.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1OUvZg-0002mw-D3 for certid@ietf.org; Fri, 02 Jul 2010 23:47:36 -0600
Message-ID: <4C2ECEF6.6060200@KingsMountain.com>
Date: Fri, 02 Jul 2010 22:47:34 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: IETF cert-based identity <certid@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 24.4.122.173 authed with jeff.hodges+kingsmountain.com}
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: Sat, 03 Jul 2010 05:47:56 -0000

Peter Saint-Andre <stpeter@stpeter.im> replied..
 >
 > On 6/30/10 2:51 PM, Love Hörnquist Åstrand wrote:
 >
 >> Can you please add a DER encoded Name, the asn1parse/dump version of
 >> the name, and the LDAP version of string and annotation what the
 >> different parts are called, this confuses me every time I try to in
 >> parse the rfc's and drafts.
 >
 > I'm still just learning about all of these different terms, formats,
 > versions, and representations. And yes it is quite confusing. Perhaps
 > I'll ask one of the co-editors or contributors to come up with a good
 > example as you have requested...

I can take a whack at doing that.

=JeffH

v2.8.7 | Report a Bug | By Email