Re: [v6ops] Protocol Action: 'Deprecating Anycast Prefix for 6to4 Relay Routers' to Best Current Practice (draft-ietf-v6ops-6to4-to-historic-11.txt)

David Farmer <farmer@umn.edu> Tue, 10 March 2015 05:24 UTC

Return-Path: <farmer@umn.edu>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B653C1A1B07 for <v6ops@ietfa.amsl.com>; Mon, 9 Mar 2015 22:24:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_QP_LONG_LINE=0.001, 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 eI7MRbP-_MUM for <v6ops@ietfa.amsl.com>; Mon, 9 Mar 2015 22:24:05 -0700 (PDT)
Received: from vs-w.tc.umn.edu (vs-w.tc.umn.edu [134.84.119.20]) by ietfa.amsl.com (Postfix) with ESMTP id 46C801A0111 for <v6ops@ietf.org>; Mon, 9 Mar 2015 22:24:05 -0700 (PDT)
Received: from mail-ie0-f179.google.com (mail-ie0-f179.google.com [209.85.223.179]) by vs-w.tc.umn.edu (UMN smtpd) with ESMTP for <v6ops@ietf.org>; Tue, 10 Mar 2015 00:24:03 -0500 (CDT)
X-Umn-Remote-Mta: [N] mail-ie0-f179.google.com [209.85.223.179] #+LO+TS+TR
X-Umn-Classification: local
Received: by iecsf10 with SMTP id sf10so1055760iec.2 for <v6ops@ietf.org>; Mon, 09 Mar 2015 22:24:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:from:subject:date:to; bh=wLpfDxA4YzRxDb3P9SgDXJiUOYdmh+vla0bjI/oD/e8=; b=kGQBNfmQUrvV2cfd2pFsm/Oo0vlXN1p/GaDpI9eOkHjnUgYy6yPLA8SrqpQnMMQcDp ujCWPZ6TFr9uXHpYGhVEn3uhH5Z+r62S/WmLToKtPhne34F5beuqCGcqyLgfkBt95ozQ L06R1tZbc/oQt+4fPhZoDo1dnXtD1wWQJYNEQ=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:references:in-reply-to:mime-version:content-type :message-id:content-transfer-encoding:cc:from:subject:date:to; bh=wLpfDxA4YzRxDb3P9SgDXJiUOYdmh+vla0bjI/oD/e8=; b=SK+8hfaMEGrIl4eZqmjluZsDYM/UcPZOIY9T+Z5Ii7h/ul6U7epko7b1K7D31+sEAr o/SbyhT1m+Zf+S2kEpVtsjbA6aaajhOgY8zmAH7kR59EPFKZhGnIQ/SBVlQORb6DaH/g FbQuUdWLGpkmt/feUTDx7FpUiHqJqjGPtlnwUfL+8lXBe/w0HWFb2ShOipVSF/uPC8vZ J96yvvhGmH4oBU5a2W51G1oSj/IByAN4MzRu6V7MjF/1ceLDne1tuAAWIsPDym5FeQAT LNNrTTdvVpoeHk/oK6sYD1RxxFF2i+kZeCRJftUV59P9q7eMWi+aJ3wp+wnu0dJAjjsm KUyA==
X-Gm-Message-State: ALoCoQlZjE6qA/vxRMg7dn4KkUp/Ku0iYBG58GUXz/cq6aSSahyU0Z5J8A1oy7AmJJZjStMghIi9AXx4b10w42/jJrs7YjUwX2Z056rwSgVI/BnV09nHIIIRSh6phWoje6TFg03WcLrc
X-Received: by 10.107.169.146 with SMTP id f18mr23725205ioj.6.1425965043463; Mon, 09 Mar 2015 22:24:03 -0700 (PDT)
X-Received: by 10.107.169.146 with SMTP id f18mr23725188ioj.6.1425965043345; Mon, 09 Mar 2015 22:24:03 -0700 (PDT)
Received: from [10.0.0.21] (c-75-73-121-154.hsd1.mn.comcast.net. [75.73.121.154]) by mx.google.com with ESMTPSA id n15sm5020854ioe.6.2015.03.09.22.24.00 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Mar 2015 22:24:00 -0700 (PDT)
References: <20150309163330.30198.34988.idtracker@ietfa.amsl.com> <54FE0A1B.2010009@umn.edu> <54FE56D3.4050104@gmail.com>
In-Reply-To: <54FE56D3.4050104@gmail.com>
Mime-Version: 1.0 (1.0)
Content-Type: text/plain; charset="us-ascii"
Message-Id: <66EBE2FE-2BE2-4529-AFE4-B30EADFE7521@umn.edu>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPad Mail (12B466)
From: David Farmer <farmer@umn.edu>
Date: Tue, 10 Mar 2015 00:23:58 -0500
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Archived-At: <http://mailarchive.ietf.org/arch/msg/v6ops/Lt-yXHOPp_FDv-IFhZ-DjrixaFA>
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] Protocol Action: 'Deprecating Anycast Prefix for 6to4 Relay Routers' to Best Current Practice (draft-ietf-v6ops-6to4-to-historic-11.txt)
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2015 05:24:06 -0000

>> On Mar 9, 2015, at 21:28, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> 
>>> On 10/03/2015 10:01, David Farmer wrote:
>>> On 3/9/15 11:33 , The IESG wrote:
>>> The IESG has approved the following document:
>>> - 'Deprecating Anycast Prefix for 6to4 Relay Routers'
>>>   (draft-ietf-v6ops-6to4-to-historic-11.txt) as Best Current Practice
>> 
>> Good News!
>> 
>> ...
>>> In response to the IANA review:
>>> 
>>> OLD:
>>> 
>>>    Instead, IANA is requested to mark the 192.88.99.0/24
>>>    prefix originally defined by [RFC3068] as "Deprecated (6to4 Relay
>>>    Anycast)", pointing to the present document.
>>> 
>>> NEW:
>>> 
>>>    Instead, IANA is requested to mark the 192.88.99.0/24
>>>    prefix originally defined by [RFC3068] as "Deprecated (6to4 Relay
>>>    Anycast)", pointing to the present document. The Boolean values
>>>    for the address block 192.88.99.0/24 will all be removed.
>> 
>> What is the rationale for removing the Boolean values?  Wouldn't the current values apply until the prefix is repurposed or
>> removed by future protocol action?
>> 
>> I'm not sure I really care, but I don't understand what is served by removing the current values.  I'm not sure what purpose the
>> Boolean values really serve, but the current values seem the most appropriate until the prefix is permanently removed or
>> repurposed.
> 
> Well, IANA wanted this change. I sympathise because it means they never have
> to revisit this in the future.
> 
>    Brian

Why would IANA have to revisit it?  Why couldn't the Boolean values be left forever for historic reference or at least until it is reassigned or removed by future protocol action, which by definition IANA would have to revisit it anyway.

Also, the IANA review says; "and added a Termination Date upon approval of this draft."  Does than mean the termination date in the IPv4 special-purpose registry will be the publication date of this document?  Is that what we want?  That doesn't seem to jive with the general feel of the rest of the recommendations in the document. In my opinion a Termination Date, two, three, or five years later would be much more in line with the feel of the rest of the document, that is why I brought it up months ago, back around -08.  I let it go thinking there wouldn't be a termination date, I guess my mistake.

My suggestion would be, leave the Boolean values as-is forever, or until reassigned, with a termination date some years after publication of this document, personally I'd pick three years, but anything more that a year out would be just fine.

-- 
===============================================
David Farmer                          Email: farmer@umn.edu
Office of Information Technology
University of Minnesota    
2218 University Ave SE         Phone: +1-612-626-0815
Minneapolis, MN 55414-3029   Cell: +1-612-812-9952
===============================================