Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets

Jared Mauch <jared@puck.nether.net> Fri, 24 February 2017 03:38 UTC

Return-Path: <jared@puck.nether.net>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1BDE11294DA; Thu, 23 Feb 2017 19:38:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=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 o22hmu46kqgP; Thu, 23 Feb 2017 19:38:16 -0800 (PST)
Received: from puck.nether.net (puck.nether.net [204.42.254.5]) by ietfa.amsl.com (Postfix) with ESMTP id 0E59E1294C7; Thu, 23 Feb 2017 19:38:16 -0800 (PST)
Received: from [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f] (unknown [IPv6:2603:3015:3603:8e00:c505:8fff:dbfd:7e6f]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by puck.nether.net (Postfix) with ESMTPSA id 1EB23540BCD; Thu, 23 Feb 2017 22:37:59 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Subject: Re: [v6ops] draft-ietf-6man-rfc4291bis prohibiting non-/64 subnets
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
Date: Thu, 23 Feb 2017 22:37:53 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <28DBAE9B-1E48-4246-8EB7-2F0723D0BD32@puck.nether.net>
References: <58AF313D.3020905@foobar.org> <20170223190730.GL2367@Space.Net> <m2poi8s2cf.wl-randy@psg.com> <CAL9jLaYuDJm4qROZ3bgDxamG9Xo8Ot88Ej5yHhO7Mj7q+77DCg@mail.gmail.com> <CAKD1Yr0hc3DYK7tg0Vi0J5kEdd-CkD4D+cJ7LbaZw5WfNS=ZEg@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/gOVLNyff7a5c9LPL12sjVbrWfuo>
Cc: IPv6 Operations <v6ops@ietf.org>, ietf <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 24 Feb 2017 03:38:17 -0000

> On Feb 23, 2017, at 10:34 PM, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> On Fri, Feb 24, 2017 at 12:23 PM, Christopher Morrow <morrowc.lists@gmail.com> wrote:
> > The IESG plans to make a decision in the next few weeks, and solicits
> > final comments on this action. Please send substantive comments to the
> > ietf@ietf.org mailing lists by 2017-03-01. Exceptionally, comments may be
> > sent to iesg@ietf.org instead. In either case, please retain the
> > beginning of the Subject line to allow automated sorting."
> 
> Nothing in the past really matters here, what matters is: "Is the bis draft all set, did we fix all the things which must be fixed before this draft becomes a real 'standard'?"
> 
> I don't think you can say nothing in the past matters here. We know that there have been host implementations that relied on this guarantee, and we have to consider that if we change the standard, those implementations will become non-compliant.

This has always been the case and was a big excuse given by Cisco back in the 1990s for not fixing the directed-broadcast problem.

For progress to occur sometimes a prior behavior will become invalid, if we can’t handle this then there’s no hope.  I don’t live in a world without hope.

- Jared