IETF Logo Mail Archive

Re: [dnsext] I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt

Stephane Bortzmeyer <bortzmeyer@nic.fr> Fri, 04 March 2011 09:14 UTC

Return-Path: <bortzmeyer@nic.fr>
X-Original-To: dnsext@core3.amsl.com
Delivered-To: dnsext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8EE253A68B3 for <dnsext@core3.amsl.com>; Fri, 4 Mar 2011 01:14:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.129
X-Spam-Level:
X-Spam-Status: No, score=-110.129 tagged_above=-999 required=5 tests=[AWL=0.120, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 zUcy14hXQ4KO for <dnsext@core3.amsl.com>; Fri, 4 Mar 2011 01:14:47 -0800 (PST)
Received: from mx2.nic.fr (mx2.nic.fr [IPv6:2001:660:3003:2::4:11]) by core3.amsl.com (Postfix) with ESMTP id 74EC13A6933 for <dnsext@ietf.org>; Fri, 4 Mar 2011 01:14:47 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id 47B121C0111; Fri, 4 Mar 2011 10:15:55 +0100 (CET)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx2.nic.fr (Postfix) with ESMTP id 433ED1C0106; Fri, 4 Mar 2011 10:15:55 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay1.nic.fr (Postfix) with ESMTP id 37F555680AD; Fri, 4 Mar 2011 10:15:55 +0100 (CET)
Date: Fri, 04 Mar 2011 10:15:55 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Tony Finch <dot@dotat.at>
Message-ID: <20110304091555.GA11147@nic.fr>
References: <20110227191542.6824.qmail@joyce.lan> <335963D7-3440-45E6-843C-38F419462792@cisco.com> <4D6C3FD3.7010801@ucd.ie> <302DAD77E927757D3DEA05DF@nimrod.local> <alpine.LSU.2.00.1103031107460.14985@hermes-1.csi.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <alpine.LSU.2.00.1103031107460.14985@hermes-1.csi.cam.ac.uk>
X-Operating-System: Debian GNU/Linux 6.0
X-Kernel: Linux 2.6.32-5-686 i686
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.5.20 (2009-06-14)
Cc: dnsext@ietf.org
Subject: Re: [dnsext] I-D Action:draft-ietf-dnsext-aliasing-requirements-00.txt
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 Mar 2011 09:14:48 -0000

On Thu, Mar 03, 2011 at 11:18:33AM +0000,
 Tony Finch <dot@dotat.at> wrote 
 a message of 37 lines which said:

> There is no specification for how to validate the TLS certificate
> for an MX server, and it is not obvious what such a specification
> should say.

RFC 3207, section 4.1 ?

Also, in the RFC editor queue:

http://www.rfc-editor.org/queue.html#draft-saintandre-tls-server-id-check

v2.23.0 | Report a Bug | By Email