Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05

Nick Hilliard <nick@foobar.org> Mon, 29 April 2019 20:25 UTC

Return-Path: <nick@foobar.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 213E5120071 for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 13:25:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=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 y4dJVy9v8n2f for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 13:25:19 -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 40968120653 for <ipv6@ietf.org>; Mon, 29 Apr 2019 13:25:18 -0700 (PDT)
X-Envelope-To: ipv6@ietf.org
Received: from crumpet.local (089-101-070074.ntlworld.ie [89.101.70.74] (may be forged)) (authenticated bits=0) by mail.netability.ie (8.15.2/8.15.2) with ESMTPSA id x3TKPCEe007023 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 29 Apr 2019 21:25:12 +0100 (IST) (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host 089-101-070074.ntlworld.ie [89.101.70.74] (may be forged) claimed to be crumpet.local
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: Ole Troan <otroan@employees.org>
Cc: 6man WG <ipv6@ietf.org>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <8b9fd743-bfcc-525c-98f6-154f3fa713cc@foobar.org>
Date: Mon, 29 Apr 2019 21:25:11 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:52.0) Gecko/20100101 PostboxApp/6.1.15
MIME-Version: 1.0
In-Reply-To: <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/B3f-n_gbvBkmyNiEuljyC2-7CbE>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Apr 2019 20:25:22 -0000

Ole Troan wrote on 29/04/2019 13:01:
> On 29 Apr 2019, at 13:03, Nick Hilliard <nick@foobar.org> wrote:
>> So, is this ID proceeding on a point of procedure at this point? 
>> I.e. is the the slate going to be wiped clean every time an update 
>> is issued, no matter how minor, and all previous objections are 
>> automatically invalidated?
> 
> Yes, I think that's a somewhat correct reading of working group 
> process.

Ok.  Frustrating for all.

> If I read you correctly, you don't think there is anything that can 
> be done with this document to fix those objections. And that the
> only outcome is to retire the document?

That would be the gist of it, yeah.

> I was also surprised by the lack of resistance in the room. Therefore
> the extra confirmation on the mailing list.

Lots of us can't get to ietf meetings. :-(

Nick