Re: last call discussion status on draft-iab-2870bis

Ted Lemon <Ted.Lemon@nominum.com> Wed, 11 March 2015 16:47 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8D90A1A06E9 for <ietf@ietfa.amsl.com>; Wed, 11 Mar 2015 09:47:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.91
X-Spam-Level:
X-Spam-Status: No, score=-3.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_LETTER=-2, T_RP_MATCHES_RCVD=-0.01] 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 WFQk1u47AMN4 for <ietf@ietfa.amsl.com>; Wed, 11 Mar 2015 09:47:01 -0700 (PDT)
Received: from sjc1-mx02-inside.nominum.com (sjc1-mx02-inside.nominum.com [64.89.234.25]) (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 8837C1A1A96 for <ietf@ietf.org>; Wed, 11 Mar 2015 09:47:01 -0700 (PDT)
Received: from webmail.nominum.com (cas-04.win.nominum.com [64.89.235.67]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certificate Authority - G2" (verified OK)) by sjc1-mx02-inside.nominum.com (Postfix) with ESMTPS id 513FCDA0469; Wed, 11 Mar 2015 16:47:01 +0000 (UTC)
Received: from [10.0.20.107] (71.233.43.215) by CAS-04.WIN.NOMINUM.COM (192.168.1.101) with Microsoft SMTP Server (TLS) id 14.3.224.2; Wed, 11 Mar 2015 09:47:01 -0700
Content-Type: text/plain; charset="windows-1252"
MIME-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: last call discussion status on draft-iab-2870bis
From: Ted Lemon <Ted.Lemon@nominum.com>
In-Reply-To: <4B545BEB-EA0E-4BA8-A45E-15AF12CDB1EC@piuha.net>
Date: Wed, 11 Mar 2015 12:46:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-ID: <00E1C89A-5BF8-4E79-9EAB-61895FCD2BDA@nominum.com>
References: <20140520204238.21772.64347.idtracker@ietfa.amsl.com> <500031A0-DF45-409E-AACB-F79C32032E38@viagenie.ca> <4B545BEB-EA0E-4BA8-A45E-15AF12CDB1EC@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1878.6)
X-Originating-IP: [71.233.43.215]
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf/yci6UdwVGoFIRXKSqZout6x4bfY>
Cc: IAB <iab@iab.org>, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2015 16:47:02 -0000

On Mar 4, 2015, at 10:43 PM, Jari Arkko <jari.arkko@piuha.net> wrote:
> 4) I’ve also received feedback from IESG members that the text about moving 2870 to Historic in Section 1.1 could be problematic. While I’m not sure that is necessarily the case, I think this draft merely replaces 2870, so I am not sure we need to say anything more. I have confirmed with the IAB that it does not believe the part about moving 2870 to Historic is necessary. Does anyone object to this change?

Somewhat belatedly, what struck me about this is that we are obsoleting a BCP document and replacing it with an ICANN document the PDF for which has the word DRAFT emblazoned in large friendly letters on every page.   What gives here?   If we are replacing a BCP with some document, hadn't that document ought to be a finished document?   I don't object to the change in principle, but it seems a bit weird to make the change when part of what is obsoleting 2870 is a document that's not been published yet.

I guess it's easier to do it in one step than two, but if what we are really doing is ceding authority to ICANN for specifying how root servers are operated, shouldn't we say that rather than referencing an ICANN work-in-progress document?   I think that is what we are effectively doing whether we say so explicitly or not.

I apologize if all this has already been discussed, but I can't find a discussion of this specific issue in the mailing list archives.