Re: [dnsext] [Technical Errata Reported] RFC3363 (3220)

Chris Thompson <cet1@cam.ac.uk> Wed, 09 May 2012 22:15 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FC1121F843F; Wed, 9 May 2012 15:15:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1336601730; bh=un3p/4icYJgfrsqSmL5XtBN5HEiX+v8/G4tk0P8gvwI=; h=Date:From:To:Message-ID:In-Reply-To:References:Mime-Version:Cc: Subject:Reply-To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:Content-Transfer-Encoding:Content-Type: Sender; b=Lt6DSCNModGs9XgFlaeQidJdlpT9oe+kYGROw6+6oG5fCG5doL+gq0buZkQGcjdV4 UxU8QfqW7wzpcQbeNwnDywDWTOxAq7LE6DcGhr3CUYlAY+qKHVAciG6cb93tsnKavf TrLUT6CkIk/+Co0XTu5PB0WDdbH0m9dstgU9COh0=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D77E821F8440 for <dnsext@ietfa.amsl.com>; Wed, 9 May 2012 15:15:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YAiOL0RAosXG for <dnsext@ietfa.amsl.com>; Wed, 9 May 2012 15:15:28 -0700 (PDT)
Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by ietfa.amsl.com (Postfix) with ESMTP id F360921F843F for <dnsext@ietf.org>; Wed, 9 May 2012 15:15:27 -0700 (PDT)
X-Cam-AntiVirus: no malware found
X-Cam-SpamDetails: not scanned
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-2.csi.cam.ac.uk ([131.111.8.54]:40246) by ppsw-50.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:cet1) id 1SSFAI-0007Zf-rL (Exim 4.72) (return-path <cet1@hermes.cam.ac.uk>); Wed, 09 May 2012 23:15:22 +0100
Received: from prayer by hermes-2.csi.cam.ac.uk (hermes.cam.ac.uk) with local (PRAYER:cet1) id 1SSFAI-0003OW-Gu (Exim 4.67) (return-path <cet1@hermes.cam.ac.uk>); Wed, 09 May 2012 23:15:22 +0100
Received: from [131.111.11.47] by webmail.hermes.cam.ac.uk with HTTP (Prayer-1.3.4); 09 May 2012 23:15:22 +0100
Date: Wed, 09 May 2012 23:15:22 +0100
From: Chris Thompson <cet1@cam.ac.uk>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Message-ID: <Prayer.1.3.4.1205092315220.29217@hermes-2.csi.cam.ac.uk>
In-Reply-To: <20120509214500.0ED1862180@rfc-editor.org>
References: <20120509214500.0ED1862180@rfc-editor.org>
X-Mailer: Prayer v1.3.4
Mime-Version: 1.0
Cc: brian@innovationslab.net, rdroms.ietf@gmail.com, ogud@ogud.com, dnsext@ietf.org
Subject: Re: [dnsext] [Technical Errata Reported] RFC3363 (3220)
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cet1@cam.ac.uk
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

On May 9 2012, RFC Errata System wrote:

>The following errata report has been submitted for RFC3363,
>"Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS)".
>
>--------------------------------------
>You may review the report below and at:
>http://www.rfc-editor.org/errata_search.php?rfc=3363&eid=3220
>
>--------------------------------------
>Type: Technical
>Reported by: Mark Andrews <marka@isc.org>
>
>Section: 4
>
>Original Text
>-------------
>4.  DNAME in IPv6 Reverse Tree
>
>   The issues for DNAME in the reverse mapping tree appears to be
>   closely tied to the need to use fragmented A6 in the main tree: if
>   one is necessary, so is the other, and if one isn't necessary, the
>   other isn't either.  Therefore, in moving RFC 2874 to experimental,
>   the intent of this document is that use of DNAME RRs in the reverse
>   tree be deprecated.
>
>
>Corrected Text
>--------------
>4. DNAME in IPv6 Reverse Tree
>
>[Deleted due to faulty premise.]
>
>Notes
>-----
>The opening premise of this section is demonstrably wrong, and so the conclusion based on that premise is wrong.  The use of DNAME in the reverse tree is and always has been independent of A6.
>
>Instructions:
>-------------
>This errata is currently posted as "Reported". If necessary, please
>use "Reply All" to discuss whether it should be verified or
>rejected. When a decision is reached, the verifying party (IESG)
>can log in to change the status and edit the report, if necessary. 
>
>--------------------------------------
>RFC3363 (draft-ietf-dnsext-ipv6-addresses-02)
>--------------------------------------
>Title               : Representing Internet Protocol version 6 (IPv6) Addresses in the Domain Name System (DNS)
>Publication Date    : August 2002
>Author(s)           : R. Bush, A. Durand, B. Fink, O. Gudmundsson, T. Hain
>Category            : INFORMATIONAL
>Source              : DNS Extensions
>Area                : Internet
>Stream              : IETF
>Verifying Party     : IESG
>_______________________________________________
>dnsext mailing list
>dnsext@ietf.org
>https://www.ietf.org/mailman/listinfo/dnsext

I don't really know whether this is technically an erratum, but it was a
quite unnecessary and unjustified side-swipe at DNAME.

As it happens, our primary use of DNAME is in the IPv4 reverse tree rather
than the IPv6 one (the wording in RFC 3363 is slithery in at least half-
implying that ought to be deprecated as well), because its primary use
(or that of CNAME, for that matter) is consolidation, and at this time
IPv4 space is much more fragmented.

-- 
Chris Thompson               University of Cambridge Computing Service,
Email: cet1@ucs.cam.ac.uk    New Museums Site, Cambridge CB2 3QH,
Phone: +44 1223 334715       United Kingdom.
_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext