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

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 29 April 2019 18:01 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 240631200CD for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 11:01:32 -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 t5GIA7n2r_VJ for <ipv6@ietfa.amsl.com>; Mon, 29 Apr 2019 11:01:30 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 004B1120096 for <ipv6@ietf.org>; Mon, 29 Apr 2019 11:01:29 -0700 (PDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 52C393826C; Mon, 29 Apr 2019 14:01:04 -0400 (EDT)
Received: by sandelman.ca (Postfix, from userid 179) id 9ED09D91; Mon, 29 Apr 2019 14:01:27 -0400 (EDT)
Received: from sandelman.ca (localhost [127.0.0.1]) by sandelman.ca (Postfix) with ESMTP id 9C5D3A98; Mon, 29 Apr 2019 14:01:27 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Ole Troan <otroan@employees.org>, 6man WG <ipv6@ietf.org>
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
In-Reply-To: <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org>
X-Mailer: MH-E 8.6; nmh 1.7+dev; GNU Emacs 24.5.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Mon, 29 Apr 2019 14:01:27 -0400
Message-ID: <22774.1556560887@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vNoTlvqebXvkWqAgJe2L4KlSMjs>
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 18:01:32 -0000

I am a supporter of the operational goal of signaling ipv6only networks.
I am generally agnostic as to the bits-on-the-wire mechanism.  Based upon
objections, I am uncertain if the mechanism (a flag in the IANA-RF) is
justified, given the paupacity of the flags involved.   I think that the
proposal would be easier to accept if it was an RA Option.

I think that the objectors have been rather few, have been unreasonably loud
and very repetitive.  I think that the objections are mostly in the rough,
however.   I have not heard, an https://tools.ietf.org/html/rfc7282 Section 4
objection of the form "Option A does not work in situation X".

I thought I heard that a number of host stack implementors would be unwilling
to implement this.  I would like to have confirmation of this.

I would ask Old to (a)-recruit someone outside else for help, since Bob Hinden
is an author, and (b) to go through RFC7282 sections 4, 5 and 6 and
write some statements of the form found there.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-