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

Bob Hinden <bob.hinden@gmail.com> Tue, 28 May 2019 01:24 UTC

Return-Path: <bob.hinden@gmail.com>
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 047D712006B for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 18:24:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 0y9k8QIb_pzd for <ipv6@ietfa.amsl.com>; Mon, 27 May 2019 18:24:42 -0700 (PDT)
Received: from mail-vk1-xa2e.google.com (mail-vk1-xa2e.google.com [IPv6:2607:f8b0:4864:20::a2e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58FA8120045 for <ipv6@ietf.org>; Mon, 27 May 2019 18:24:42 -0700 (PDT)
Received: by mail-vk1-xa2e.google.com with SMTP id j4so4269065vke.11 for <ipv6@ietf.org>; Mon, 27 May 2019 18:24:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PgM0RHDX5wHivDcf7xbTm67B1NjkRLLu0Kgy2ayyvgM=; b=fX5GzERIB6joFsOcOkxOFnGh3jyXqN4tDzwtezxfFb+1JtWp1/UlsHsHv0D8iFZ56I NlLmoNLUyOqmQ7ikRuOxrgsMZs9iJnqqERsPj1PMBYZHdMAi+bO22bphoGSGHZ+BdwkF sCXcUJ8MXmvT5zspHyukZVLLNTSvkAm0pUcQaW+JOvYV8v3ZCAzkUAfFpuxsn28AbTq/ MDE4Bs5TmPgltOX3rbh7M3ulRTcIPxbXAc1mQkou+uLMevFGXWKgiOIFDJ+f19ViGo9G 6N4shHUjgx7v12/NIe7DkG3ZIEZLLa0Noe1gtRD07RGsfrym3PHxNfo1hpQJgHSJgIGp P7kw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=PgM0RHDX5wHivDcf7xbTm67B1NjkRLLu0Kgy2ayyvgM=; b=uheF1KD98gV2gFAmSa45y/HjKUj2hYbH9AJHD10XnflI3RC5cKEaqeoAfdnP6k4VJp o0XoAIczMiSgJHdCwmse+Yft2MbXf4YyWZN+eh7A7adV2per+EH04Yby6++2+R1yDVMX rllELCj87xOFRTaegimp51zH2pwiKKI37BAEuwoLjRDcp48HFJs30Lm3lqxmvQArp77H 89OgAkA8UNwsHTIgFHrnlPSw4uNTfyGZp/wy6im3Co/kxXDvDdN5hpqDjJ9vzxfH+3/c cKDHKaCVHREfur39Wir8OrDHDNB3miCJ4lwphJCucsFnK4PYf1M5cRZZv1pdjhYOFoar XWQA==
X-Gm-Message-State: APjAAAVVjsEe+NobijQZsCyND7NOuq43PGxCs1x3wJ79MwmDuXwjkXkT 80COy8Nds2h/xJCeqdpB+3I=
X-Google-Smtp-Source: APXvYqxbOJNGA2Mu9Ld2wYS3RjJ72rRbRsSXyjTP8FCTj5PiMQRdmwD6yYJtLOIHos4oP+/kTk2D2w==
X-Received: by 2002:ac5:c7bb:: with SMTP id d27mr17327455vkn.79.1559006680873; Mon, 27 May 2019 18:24:40 -0700 (PDT)
Received: from [172.20.2.217] ([65.153.65.2]) by smtp.gmail.com with ESMTPSA id j92sm4271251uad.2.2019.05.27.18.24.40 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 May 2019 18:24:40 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
From: Bob Hinden <bob.hinden@gmail.com>
In-Reply-To: <e3078d9a-c4ef-abb5-aae5-e5381332fb20@oneunified.net>
Date: Mon, 27 May 2019 21:24:39 -0400
Cc: Bob Hinden <bob.hinden@gmail.com>, IPv6 List <ipv6@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <88396BCA-5612-4691-B061-971FDBED068B@gmail.com>
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <m1hQ7Dm-0000M3C@stereo.hq.phicoh.net> <CAN-Dau040j6U+1CCn0QJiVMy2nVShHqqSFdCkM-FbMAH-2wjRA@mail.gmail.com> <m1hQCYr-0000KBC@stereo.hq.phicoh.net> <561d9dc3-c769-c774-8f65-f975ac2a10a0@gont.com.ar> <m1hT1DZ-0000HEC@stereo.hq.phicoh.net> <ce07ade8-5105-055f-4798-f4ef20a2393c@si6networks.com> <CAN-Dau02MYCrKx2BgyuYJeHBdoz6SHCnp+-byM+LMM8af0S+rA@mail.gmail.com> <40e99171-6dda-29e3-6152-da5ca5219ed9@foobar.org> <CAN-Dau0ALqfAA-Dz56oHAfOtY7E2obx5E7TgoeH357Mckp3t9g@mail.gmail.com> <093ba8e2-6f0a-4c91-9df1-cda33fffea97@foobar.org> <CAN-Dau3kVqb+ZEHB7iPGeRuq1Mu8UHR3FEZv8SgmiqZexaFhuA@mail.gmail.com> <12db9629-f92a-e12a-5ff1-7db2c5d2137e@foobar.org> <374F009B -98E1-40D0-AC0D-1C82CBE378BD@steffann.nl> <CAN-Dau0EGN+bLZCTA-A4ksd40KprhKn-HkL4gotG=v-=kD0zrg@mail.gmail.com> <F6F0C9DC-545E-4FE5-BB4C-55BB29022E84@steffann.nl> <e191d0f2-235b-bc97-2a02-878783c4c308@gmail.com> <e3078d9a-c4ef-abb5-aae5-e5381332fb20@oneunified.net>
To: Raymond Burkholder <ray@oneunified.net>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/wbCulwLtuujmEUIjcqeCZNzthkQ>
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: Tue, 28 May 2019 01:24:45 -0000

Raymond,

> On May 27, 2019, at 9:07 PM, Raymond Burkholder <ray@oneunified.net> wrote:
> 
> On 2019-05-27 5:54 p.m., Brian E Carpenter wrote:
>> Then stop telling people to filter Ethertype 0x0800 because you can't use RFC2563 in the presence of such filters.
>>> Those are different options, depending on your situation.
>> Well, yes. But if an operator chooses to filter 0x0800 and wishes to actively
>> inform hosts that IPv4 is unavailable, only an IPv6 mechanism can do so.
>> So here we are.
> 'only an IPv6 mechanism can do so'  -- is that necessarily true?
> 
> This time I did read through https://tools.ietf.org/html/draft-ietf-6man-ipv6only-flag-05.  I see there is an inclusion of the IPv4 Sunset draft for turning off ipv4 (and someone else did point out that the Sunset WG has been itself 'sunsetted' I believe).
> 
> I also took a look at table called 'EtherType values for some notable protocols' at https://en.wikipedia.org/wiki/EtherType
> 
> A network link may have many other protocols other than ipv4 or ipv6: PTP, MacSec, LLDP, PBB, CFM, RoCE, ATAoE, MPLS, PPPoE, .... not to mention STP and the like which is very noisy.  I didn't see a summary in the document of how that might be handled.
> 
> So I guess this is IPv6-only in the sense of IPv6 with no IPv4.

Yes, it says that in Section 4. "IPv6-Only Definition”.  Reading the actual document is helpful in these discussions, not just the email thread :-)

Bob


> 
> I can't remember if there was mention of IPv4 only hosts knowing how to evaluate an IPv6 flag in an IPv6 protocol, or how vendors would/could/want to implement such a thing.
> 
> Maybe rather than saying IPv6 only, maybe create another EtherType which network stacks would know how to interpret, and it could be used to turn off other protocols.  Maybe some networks might want to run IPv4 and turn off IPv6 (saying half jokingly).
> 
> This independent protocol could be used to turn off other protocols that the network stack might see as well.  The flags then become universally applicable to any stack that has been designed to interpret xxx-only flags.  It would then have long lasting applicability, as protocols come and go.
> 
> Raymond.
> 
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------