[DNSOP] On draft-ietf-dnsop-rfc6304bis and obsoleting RFC 6304

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 01 December 2014 03:19 UTC

Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F7471A0373 for <dnsop@ietfa.amsl.com>; Sun, 30 Nov 2014 19:19:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6n0lQkombOz7 for <dnsop@ietfa.amsl.com>; Sun, 30 Nov 2014 19:19:36 -0800 (PST)
Received: from proper.com (Hoffman.Proper.COM [207.182.41.81]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B1D4A1A0222 for <dnsop@ietf.org>; Sun, 30 Nov 2014 19:19:36 -0800 (PST)
Received: from [10.20.30.90] (142-254-17-119.dsl.dynamic.fusionbroadband.com [142.254.17.119]) (authenticated bits=0) by proper.com (8.14.9/8.14.7) with ESMTP id sB13JZuV021466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <dnsop@ietf.org>; Sun, 30 Nov 2014 20:19:36 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: proper.com: Host 142-254-17-119.dsl.dynamic.fusionbroadband.com [142.254.17.119] claimed to be [10.20.30.90]
From: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <4AA10CE4-A0F0-4CF9-A4E0-F10F0381DB11@vpnc.org>
Date: Sun, 30 Nov 2014 19:19:34 -0800
To: dnsop <dnsop@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
X-Mailer: Apple Mail (2.1993)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/f0CVEG4EYqJSMN2CPVaVD3xsz8I
Subject: [DNSOP] On draft-ietf-dnsop-rfc6304bis and obsoleting RFC 6304
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Mon, 01 Dec 2014 03:19:38 -0000

Greetings again. draft-ietf-dnsop-rfc6304bis obsoletes RFC 6304, therefore it should not be indicating that the reader should be familiar with RFC 6304. However, the text confuses this in a few ways.

   RFC6304 described the steps required to install a new AS112 node, and
   offered advice relating to such a node's operation.  This document
   updates that advice to facilitate the addition and removal of zones
   for which query traffic will be sunk at AS112 nodes, using DNAME,
   whilst still supporting direct delegations to AS112 name servers.

This document doesn't "update that advice", it replaces it.

   [RFC6304] describes an approach whereby zones whose traffic should be
   directed towards an AS112 sink should be directly delegated to AS112
   name servers.  Correspondingly, each AS112 node is manually
   configured to answer appropriately for those zones.

   The guidance in this document preserves this capability for the zones
   that were originally delegated in this fashion.  AS112 nodes that
   were implemented in accordance with the guidance in [RFC6304] will
   continue to provide service for those zones.

This should be "This document describes an approach..." and "...with the guidance in this document will..."

--Paul Hoffman