Re: [keyassure] The draft and subj alt names

Jeff Schmidt <jschmidt@jasadvisors.com> Fri, 01 April 2011 21:34 UTC

Return-Path: <jschmidt@jasadvisors.com>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3B46928C0D8 for <keyassure@core3.amsl.com>; Fri, 1 Apr 2011 14:34:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 wYZbVeZ68wAz for <keyassure@core3.amsl.com>; Fri, 1 Apr 2011 14:34:07 -0700 (PDT)
Received: from relay-hub202.domainlocalhost.com (relay-hub202.domainlocalhost.com [74.115.204.52]) by core3.amsl.com (Postfix) with ESMTP id 76FC33A698E for <keyassure@ietf.org>; Fri, 1 Apr 2011 14:34:07 -0700 (PDT)
Received: from MBX202.domain.local ([169.254.2.125]) by HUB202.domain.local ([74.115.204.52]) with mapi id 14.01.0255.000; Fri, 1 Apr 2011 17:35:47 -0400
From: Jeff Schmidt <jschmidt@jasadvisors.com>
To: Paul Wouters <paul@xelerance.com>, Jay Daley <jay@nzrs.net.nz>
Thread-Topic: [keyassure] The draft and subj alt names
Thread-Index: AQHL74s8QmwRa1lb4kmHso/AEMV0KpRHjQYAgACe8QCAALMqgIAAmoaA
Date: Fri, 1 Apr 2011 21:35:46 +0000
Message-ID: <C9BBAF0A.686D%jschmidt@jasadvisors.com>
In-Reply-To: <alpine.LFD.1.10.1104010319130.18318@newtla.xelerance.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.2.0.101115
x-originating-ip: [192.168.64.22]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <47EE21DFBAB895409A293E7E95EA946F@domain.local>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "keyassure@ietf.org" <keyassure@ietf.org>
Subject: Re: [keyassure] The draft and subj alt names
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2011 21:34:08 -0000

On 4/1/11 2:22 AM, "Paul Wouters" <paul@xelerance.com> wrote:
>The cert is just a legacy container for the public key. We should not be
>adding policy
>in DANE that entangles DANE with PKIX (or any other trust scheme)

+1.  Or have an easy way to unwind any such entanglements (i.e. make them
optional).

Jeff