IETF Logo Mail Archive

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

j h woodyatt <jhw@conjury.org> Thu, 09 May 2019 17:14 UTC

Return-Path: <jhw@conjury.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 3BA98120278 for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 10:14:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=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 TzZQqYyUmJP9 for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 10:14:23 -0700 (PDT)
Received: from mail.conjury.org (prime.conjury.org [IPv6:2607:f2f8:a938::2]) by ietfa.amsl.com (Postfix) with ESMTP id B0983120302 for <ipv6@ietf.org>; Thu, 9 May 2019 10:14:20 -0700 (PDT)
Received: from [192.168.0.188] (zoox-inc.wh.edge1.sanjose2.level3.net [4.28.172.66]) by mail.conjury.org (Postfix) with ESMTPSA id 128FFE6110 for <ipv6@ietf.org>; Thu, 9 May 2019 09:37:07 -0700 (PDT)
From: j h woodyatt <jhw@conjury.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_8957195B-F80E-4BFC-8EA9-922891ADE6D1"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.8\))
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
Date: Thu, 09 May 2019 10:14:19 -0700
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org> <8b9fd743-bfcc-525c-98f6-154f3fa713cc@foobar.org> <CAO42Z2zEWvt9NyemMb8H0AEvPvmNSDGa4wcXiS6n5yRxNFCHQg@mail.gmail.com> <c7e18765-be04-6494-8193-984dbccb520b@foobar.org> <CANMZLAYh+V57yrWOzmUyjSMK0g95u1D5_GZmyZBMOMKAZnrnCg@mail.gmail.com> <3F474511-6FE3-4A0A-9B84-7C37F08FBB5D@steffann.nl> <E352C226-C708-4418-BCDE-10525CAB109A@jisc.ac.uk> <652fb10e-b8ce-0151-a9a0-62d2378caed2@gmail.com> <0079c716-d56c-7199-f493-f5e56e1307ae@foobar.org> <b33de303-eaca-f7f6-804e-2c9343eb92a1@gmail.com> <6C4ABEF1-2565-4BA9-9FC5-5B3C45A719AD@gmail.com> <c2222416-6491-1906-a403-d012777a4b38@gmail.com> <CABNhwV0-SdKZqQa4z9jhpc8h1Eq=8UxRhtvHt1==BYEMTVRjug@mail.gmail.com> <96790121-7D50-4C6F-924F-87065B989E44@gmail.com> <ccab3694-54f2-bdd1-f8ac-cb159dbc0a81@gont.com.ar> <CAN-Dau0_w0n9C6grqi1bXAL-k239K7RMiQyhx5=c-Y_wqrV2OQ@mail.gmail.com> <CAO42Z2wwftO6wtF7PAJ9CCK2iBvtOj0BQP7O0UREr-pMmPegvQ@mail.gmail.com>
To: IPv6 List <ipv6@ietf.org>
In-Reply-To: <CAO42Z2wwftO6wtF7PAJ9CCK2iBvtOj0BQP7O0UREr-pMmPegvQ@mail.gmail.com>
Message-Id: <A116C7B4-9ED0-4268-9086-5768CB53898D@conjury.org>
X-Mailer: Apple Mail (2.3445.104.8)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mOhLiXssVvr3S78BQrUdBUA0-g0>
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: Thu, 09 May 2019 17:14:29 -0000

On May 8, 2019, at 23:09, Mark Smith <markzzzsmith@gmail.com> wrote:
> 
> The primary goal is to reduce and ideally entirely eliminate link-layer broadcasts on the link caused by IPv4.

I don’t think 6MAN can work on that goal. I’m looking at the active charter, and I’m just not seeing where it says it can have that as a goal for its work. There is a clause about addressing "protocol limitations/issues discovered during deployment and operation” but I think it’s a big stretch to tag this goal with that topic. This isn’t a limitation or issue with the IPv6 protocol.

--james woodyatt <jhw@conjury.org>

v2.23.0 | Report a Bug | By Email