Re: [certid] DC should be MUST NOT

=JeffH <Jeff.Hodges@KingsMountain.com> Sat, 03 July 2010 05:48 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 E5D5B3A6829 for <certid@core3.amsl.com>; Fri, 2 Jul 2010 22:48:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.074
X-Spam-Level:
X-Spam-Status: No, score=-1.074 tagged_above=-999 required=5 tests=[AWL=1.191, BAYES_00=-2.599, 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 SWzyASIm62Vd for <certid@core3.amsl.com>; Fri, 2 Jul 2010 22:48:56 -0700 (PDT)
Received: from cpoproxy2-pub.bluehost.com (cpoproxy2-pub.bluehost.com [67.222.39.38]) by core3.amsl.com (Postfix) with SMTP id 071383A6823 for <certid@ietf.org>; Fri, 2 Jul 2010 22:48:55 -0700 (PDT)
Received: (qmail 22893 invoked by uid 0); 3 Jul 2010 05:49:08 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 3 Jul 2010 05:49:08 -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=AjTxU3RfeiWtXIc9o8/hHbFZ2W636A1LtzE7Ixypb/UplRKXJfl6mCm+2OSJr36iPfas+4v0HZuRr8J6atDBnRbAvGD9Az0QQWSGEXvlZ04o6xWiALh0j+4lpauFqOnw;
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 1OUvbA-0003w1-3T for certid@ietf.org; Fri, 02 Jul 2010 23:49:08 -0600
Message-ID: <4C2ECF52.8070502@KingsMountain.com>
Date: Fri, 02 Jul 2010 22:49:06 -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: 7bit
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] DC should be MUST NOT
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:48:58 -0000

Martin Rex <mrex@sap.com> postulated..
 >
 > I assume the idea of the DC= components could be to establish something like
 >  a hierarchical LDAP directory model based on DNS rather than assuming a
 > single global X.500 directory hierarchy and full-fledged DAP.

Yes, in large part, that's the rationale behind the DC= components.

=JeffH (a former LDAPv3 contributor and DNS-based directory hierarchy proponent)