Re: [v6ops] Fwd: New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt

Nick Hilliard <nick@foobar.org> Tue, 18 July 2017 13:15 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DF49C12EB8C for <v6ops@ietfa.amsl.com>; Tue, 18 Jul 2017 06:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 N5boGcAIdUxy for <v6ops@ietfa.amsl.com>; Tue, 18 Jul 2017 06:14:57 -0700 (PDT)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 279BB131B46 for <v6ops@ietf.org>; Tue, 18 Jul 2017 06:14:56 -0700 (PDT)
X-Envelope-To: v6ops@ietf.org
Received: from cupcake.local (089-101-195156.ntlworld.ie [89.101.195.156] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id v6IDEr8H021030 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 18 Jul 2017 14:14:53 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-195156.ntlworld.ie [89.101.195.156] (may be forged) claimed to be cupcake.local
Message-ID: <596E09CC.3@foobar.org>
Date: Tue, 18 Jul 2017 14:14:52 +0100
From: Nick Hilliard <nick@foobar.org>
User-Agent: Postbox 5.0.15 (Macintosh/20170609)
MIME-Version: 1.0
To: Ted Lemon <mellon@fugue.com>
CC: IPv6 Operations <v6ops@ietf.org>
References: <596CF817.8040900@foobar.org> <CAPt1N1mm6gMEQN0KQ60e=vROOEbooxOBpZEGBm9SGP4WwBDtnw@mail.gmail.com> <596D2E63.3070401@foobar.org> <CAAedzxpT89AYcM6QWq9MHb_dJfeEm7rwpVDunRNUrHah-AhgOw@mail.gmail.com> <596DFD26.4050206@foobar.org> <CAPt1N1kYSj0de_wdiEffNooe2WjVub5wz7kawCNM=MRFa-YsJQ@mail.gmail.com>
In-Reply-To: <CAPt1N1kYSj0de_wdiEffNooe2WjVub5wz7kawCNM=MRFa-YsJQ@mail.gmail.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/NvqJE0r289Fc_YjSGRnYgOcj54I>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Jul 2017 13:15:04 -0000

Ted Lemon wrote:
> Nick, it's not actually up to you to determine consensus, and you do not
> seem to actually be describing a situation where there was a lack of
> consensus.   If you feel that there was indeed an error made by the
> chairs, who /were/ responsible for calling consensus, the right thing to
> do would be to appeal to the chairs, and if you are not satisfied by
> their response, to appeal to the IESG, and so on.

I'm not attempting to determine consensus, simply expressing an opinion
that there was substantial opposition to the principals behind a
sentence that was inserted into the draft, i.e. querying whether that
consensus existed to start with.  There isn't a problem with querying a
decision.

The difficulty with formally appealing the consensus call is that the
change was inserted into the document in Feb 2016, and there were
several more revisions of the document before it was published as a BCP
some months later, and there were no objections because it wasn't
obvious what it meant at the time.

As an aside, the fact that there is a good deal of disagreement on its
interpretation today makes it clear that that this sentence is open to
vastly different interpretations.

So procedurally, there was not a problem with the consensus process
which means that an appeal to the chairs / IESG / etc would be almost
certain to fail, not least because this happened some time ago.  The
only obvious way to deal with the problem is to bring it back to the
working group with an explicit statement of the semantic problem, which
is what has happened.

It would be useful for the chairs to express an opinion if a different
approach were more appropriate.

Nick