From owner-freebsd-hackers@FreeBSD.ORG Tue Aug 30 07:55:32 2005 Return-Path: X-Original-To: freebsd-hackers@FreeBSD.org Delivered-To: freebsd-hackers@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D979A16A41F for ; Tue, 30 Aug 2005 07:55:32 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mail2.fluidhosting.com [204.14.90.62]) by mx1.FreeBSD.org (Postfix) with SMTP id 2BDD343D45 for ; Tue, 30 Aug 2005 07:55:32 +0000 (GMT) (envelope-from dougb@FreeBSD.org) Received: (qmail 80822 invoked by uid 399); 30 Aug 2005 07:55:31 -0000 Received: from mail1.fluidhosting.com (204.14.90.61) by mail2.fluidhosting.com with SMTP; 30 Aug 2005 07:55:31 -0000 Received: (qmail 2924 invoked by uid 399); 30 Aug 2005 07:55:31 -0000 Received: from localhost (HELO ?192.168.1.100?) (dougb@dougbarton.net@127.0.0.1) by localhost with SMTP; 30 Aug 2005 07:55:31 -0000 Message-ID: <431410F1.7020509@FreeBSD.org> Date: Tue, 30 Aug 2005 00:55:29 -0700 From: Doug Barton Organization: http://www.FreeBSD.org/ User-Agent: Mozilla Thunderbird 1.0.6 (X11/20050829) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-hackers@FreeBSD.org, freebsd-arch@freebsd.org X-Enigmail-Version: 0.92.0.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: ip6.int deprecated X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Aug 2005 07:55:33 -0000 [ -hackers and -arch cc'ed to try and get a wide audience for this. Please pick the one list that is most appropriate for any topics you want to follow up on. Thanks. ] Howdy, RFC 4159 was published today, which officially deprecates ip6.int. You can find the full text at http://www.rfc-editor.org/rfc/rfc4159.txt. Here is a relevant excerpt: In August 2001 the IETF published [RFC3152], which advised that the use of "ip6.int" as the domain for reverse-mapping of IPv6 addresses to DNS names was deprecated. The document noted that the use of "ip6.int" would be phased out in an orderly fashion. As of 1 September 2005, the IETF advises the community that the DNS domain "ip6.int" should no longer be used to perform reverse mapping of IPv6 addresses to domain names, and that the domain "ip6.arpa" should be used henceforth, in accordance with the IANA Considerations described in [RFC3596]. The domain "ip6.int" is deprecated, and its use in IPv6 implementations that conform to the IPv6 Internet Standards is discontinued. The one step I'm going to take directly to support this deprecation is to remove the ip6.int example from the sample named.conf file in the base. I'm sending this message to provide notice of that, and notice to the community generally that we should start moving in the direction of deprecating ip6.int wherever it might be found. For those not aware of the history, ip6.int was the first stab at creating a reverse DNS zone for IP version 6. Eventually, the "issues" surrounding this topic were sorted out, and it was agreed to do reverse DNS in IPv6 in .arpa instead. Unfortunately, that left a lot of early adopters in a difficult position, and so the various players in the game (ICANN, the Regional Internet Registries, etc.) have been supporting both zones since 2001. In order to reduce the workload associated with this issue, and in order to encourage complete migration to ip6.arpa before wide deployment of IPv6 (and I'm sure for a lot of other reasons), the decision was made to officially deprecate ip6.int from the IETF perspective. Other than some old references in src/contrib/bind9, the only place I see a reference to ip6.int in our base is in the named.conf file that I mentioned above. I hope that this note is useful however as a more general source of information, and of course if there is anything I've missed, I welcome others to take appropriate action. Regards, Doug -- This .signature sanitized for your protection