Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-as112-dname-00

Paul Hoffman <paul.hoffman@vpnc.org> Sat, 07 December 2013 16:34 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 1FC181AE38C for <dnsop@ietfa.amsl.com>; Sat, 7 Dec 2013 08:34:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] autolearn=no
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 L1aZ1y7kIONj for <dnsop@ietfa.amsl.com>; Sat, 7 Dec 2013 08:34:06 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 056661AE37C for <dnsop@ietf.org>; Sat, 7 Dec 2013 08:34:05 -0800 (PST)
Received: from [10.20.30.90] (50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41]) (authenticated bits=0) by hoffman.proper.com (8.14.7/8.14.7) with ESMTP id rB7GY0xF016389 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsop@ietf.org>; Sat, 7 Dec 2013 09:34:01 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 50-0-66-41.dsl.dynamic.sonic.net [50.0.66.41] claimed to be [10.20.30.90]
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <52A32A53.9060402@teamaol.com>
Date: Sat, 07 Dec 2013 08:33:59 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <A420FC34-0D15-4809-A1AD-C9ED716EAB31@vpnc.org>
References: <52A32A53.9060402@teamaol.com>
To: dnsop <dnsop@ietf.org>
X-Mailer: Apple Mail (2.1822)
Subject: Re: [DNSOP] Working Group Last Call for draft-ietf-dnsop-as112-dname-00
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: Sat, 07 Dec 2013 16:34:07 -0000

Alas, this document is definitely not ready for publication as an RFC. It still is very unclear which parts are restatements of RFC 6304, which are changes, and which are speculative. Appendix B makes an attempt to make this clearer, but fails spectacularly by saying that Appendix B should be removed from the final document.

The lead paragraph of Appendix B says:

   The following changes are required to [RFC6304] to provide support
   for AS112 redirection.  It is proposed that a successor document to
   [RFC6304] be prepared for joint publication with this document in the
   interests of providing clear advice to prospective new AS112
   operators.  The following sub-sections are hence provided mainly only
   to describe the scope of the changes required for 6304bis, and are
   not intended for publication in this document.  References to this
   section in this document should ultimately be replaced with
   references to 6304bis.

...but there is no successor document seems to have been started. So, now we are left with RFC 6304, a bunch of changes (or not) to it in this document, and no roadmap.

I propose that this document be scrapped completely, and that the RFC 6304 successor simply be published with these changes. That new document should have what is Appendix B of this document as a sub-section of its introduction (because the changes are significant), and should retain Appendix A of this document (because it shows due diligence for the changes).

--Paul Hoffman