IETF Logo Mail Archive

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

Stephane Bortzmeyer <bortzmeyer@nic.fr> Mon, 28 February 2011 08:48 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 8C8043A6AC6 for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 00:48:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.949
X-Spam-Level:
X-Spam-Status: No, score=-109.949 tagged_above=-999 required=5 tests=[AWL=0.300, 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 i8Np6zau2mss for <dnsext@core3.amsl.com>; Mon, 28 Feb 2011 00:48:01 -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 441B33A6A81 for <dnsext@ietf.org>; Mon, 28 Feb 2011 00:48:01 -0800 (PST)
Received: from mx2.nic.fr (localhost [127.0.0.1]) by mx2.nic.fr (Postfix) with SMTP id EEED11C0038; Mon, 28 Feb 2011 09:48:59 +0100 (CET)
Received: from relay2.nic.fr (relay2.nic.fr [192.134.4.163]) by mx2.nic.fr (Postfix) with ESMTP id EA0CD1C0021; Mon, 28 Feb 2011 09:48:59 +0100 (CET)
Received: from bortzmeyer.nic.fr (batilda.nic.fr [192.134.4.69]) by relay2.nic.fr (Postfix) with ESMTP id DE0617B0037; Mon, 28 Feb 2011 09:48:59 +0100 (CET)
Date: Mon, 28 Feb 2011 09:48:59 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Alex Bligh <alex@alex.org.uk>
Message-ID: <20110228084859.GA6668@nic.fr>
References: <20110223001502.31614.56353.idtracker@localhost> <20110223114720.GA10740@bikeshed.isc.org> <D3C451913423BA973D633EC1@Ximines.local>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <D3C451913423BA973D633EC1@Ximines.local>
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: Mon, 28 Feb 2011 08:48:02 -0000

On Sat, Feb 26, 2011 at 01:07:54PM +0000,
 Alex Bligh <alex@alex.org.uk> wrote 
 a message of 402 lines which said:

> > technology; it can be done, and is done today, entirely with
> > provisioning logic and registry policy.
> 
> +AB: Note this isn't only a registry solution. It could be done by
> +AB: users too (e.g. through a zonefile preprocessor that was
> +AB: run prior to signing of the zone).

A registry can be at any level. See the IDN RFCs which use the word
"registry" for "anything that manage a zone, whether the zone is .com
or foobar.momandpop.example".

v2.23.0 | Report a Bug | By Email