Re: [DNSOP] Fw: New Version Notification for draft-bellis-dns-recursive-discovery-00

Joe Abley <jabley@hopcount.ca> Wed, 21 October 2009 14:44 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@core3.amsl.com
Delivered-To: dnsop@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0BCC628C12F for <dnsop@core3.amsl.com>; Wed, 21 Oct 2009 07:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.699
X-Spam-Level:
X-Spam-Status: No, score=-1.699 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_44=0.6, J_CHICKENPOX_54=0.6]
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 eFGwc1RPr4wG for <dnsop@core3.amsl.com>; Wed, 21 Oct 2009 07:44:46 -0700 (PDT)
Received: from monster.hopcount.ca (monster.hopcount.ca [216.235.14.38]) by core3.amsl.com (Postfix) with ESMTP id 3C65228C123 for <dnsop@ietf.org>; Wed, 21 Oct 2009 07:44:46 -0700 (PDT)
Received: from [199.212.90.22] (helo=dh22.r2.owls.hopcount.ca) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69 (FreeBSD)) (envelope-from <jabley@hopcount.ca>) id 1N0cQj-000IDp-Bz; Wed, 21 Oct 2009 14:44:50 +0000
Mime-Version: 1.0 (Apple Message framework v1076)
Content-Type: text/plain; charset="us-ascii"; format="flowed"; delsp="yes"
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <5866378D-2A58-4D5F-ABBE-86B69CAB147B@virtualized.org>
Date: Wed, 21 Oct 2009 10:44:45 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <300DC5AE-E698-4561-BDFD-47201B8E4BA3@hopcount.ca>
References: <OFA656600E.F5229B3D-ON80257650.005247BF-80257650.00527644@nominet.org.uk> <82skde36c9.fsf@mid.bfk.de> <DE23E9BF50E437E2D5CA65C8@Ximines.local> <82ljj61gle.fsf@mid.bfk.de> <200910202329.n9KNT56j048843@drugs.dv.isc.org> <1F61DD04-14A6-4349-8650-9CF27D27C3BC@hopcount.ca> <200910210145.n9L1j8of033780@drugs.dv.isc.org> <8263a9xnem.fsf@mid.bfk.de> <OFD7B965B7.53CC1C17-ON80257656.0028D85C-80257656.002974DF@nominet.org.uk> <82zl7luov4.fsf@mid.bfk.de> <5866378D-2A58-4D5F-ABBE-86B69CAB147B@virtualized.org>
To: David Conrad <drc@virtualized.org>
X-Mailer: Apple Mail (2.1076)
Cc: dnsop WG <dnsop@ietf.org>, Florian Weimer <fweimer@bfk.de>
Subject: Re: [DNSOP] Fw: New Version Notification for draft-bellis-dns-recursive-discovery-00
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2009 14:44:47 -0000

On 2009-10-21, at 09:39, David Conrad wrote:

> On Oct 21, 2009, at 1:34 AM, Florian Weimer wrote:
>>> Indeed LOCAL.ARPA would need to be unsigned.
>> Not really.  Why would it need to exist in the public tree at all?
>> All we need is agreement from both ICANN and IETF that LOCAL.ARPA is
>> reserved and not to be delegated in the official tree.
>
> Entries in the ARPA tree are (now) only created by the IAB or a  
> protocol action. ICANN merely implements what we're told. I'd  
> suggest an IANA considerations section that simply said that  
> "LOCAL.ARPA" is reserved and must not be delegated.

This is already in the draft. It makes use of the registry proposed by  
Olafur and me for use by SINK.ARPA.

Note that the draft specifies that LOCAL.ARPA *not* be delegated, not  
that any change be made to the ARPA zone. The document further  
requests approval from the IAB in section 9. All procedural bases seem  
well-covered here (to the extent that the SINK.ARPA proposal has legs).


Joe

...

8.  IANA Considerations


    This document directs the IANA to add the following record to the
    ARPA Reserved Names Registry [I-D.jabley-sink-arpa]:

    +------------+----------------------+--------- 
+---------------------+
    | Name       | Purpose              | RRTypes |  
Reference           |
    +------------+----------------------+--------- 
+---------------------+
    | LOCAL.ARPA | Locally administered | NONE    | This  
document       |
    |            | infrastructure       |         | (RFCXXXX)  S.  
3     |
    +------------+----------------------+--------- 
+---------------------+

...

9.  IAB Considerations

    The addition of "LOCAL.ARPA" to the ARPA Reserved Names Registry
    requires IAB approval.

...