IETF Logo Mail Archive

Re: [certid] Domain Components

Martin Rex <mrex@sap.com> Thu, 24 June 2010 21:03 UTC

Return-Path: <mrex@sap.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 D16513A689E for <certid@core3.amsl.com>; Thu, 24 Jun 2010 14:03:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.915
X-Spam-Level:
X-Spam-Status: No, score=-7.915 tagged_above=-999 required=5 tests=[AWL=-0.080, BAYES_40=-0.185, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_HI=-8]
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 UFmgrzFOb+FU for <certid@core3.amsl.com>; Thu, 24 Jun 2010 14:03:21 -0700 (PDT)
Received: from smtpde01.sap-ag.de (smtpde01.sap-ag.de [155.56.68.170]) by core3.amsl.com (Postfix) with ESMTP id D80243A6836 for <certid@ietf.org>; Thu, 24 Jun 2010 14:03:20 -0700 (PDT)
Received: from mail.sap.corp by smtpde01.sap-ag.de (26) with ESMTP id o5OL3QDc000753 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 24 Jun 2010 23:03:26 +0200 (MEST)
From: Martin Rex <mrex@sap.com>
Message-Id: <201006242103.o5OL3PO6019652@fs4113.wdf.sap.corp>
To: phoffman@imc.org (Paul Hoffman)
Date: Thu, 24 Jun 2010 23:03:25 +0200 (MEST)
In-Reply-To: <p0624082dc84286e8b770@[10.20.30.158]> from "Paul Hoffman" at Jun 19, 10 07:42:25 am
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Scanner: Virus Scanner virwal06
X-SAP: out
Cc: certid@ietf.org
Subject: Re: [certid] Domain Components
X-BeenThere: certid@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: mrex@sap.com
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: Thu, 24 Jun 2010 21:03:21 -0000

Paul Hoffman wrote:
> 
> If you feel that way, fine. We have historically seen deployed PKIX
> implementations that got the order wrong because they had no certs
> to test with. I do not hold it against someone to get the order wrong,
> particularly because all of the text examples in RFC 5280 say
> "dc=example,dc=com".

You're right on the spot -- all of the DC= examples in rfc-5280 are
purely about >>domain name<<.  There is also a server mentioned
"ldap.example.com", but there is not a single example in rfc-5280
that puts a >>hostname<< into a DC component.

So why does draft-saintandre-tls-server-id-check-06
come up with the idea of performing a server endpoint identification
against a DC that includes a hostname?
Rfc-2818 never suggested this!

-Martin

v2.8.7 | Report a Bug | By Email