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

Gyan Mishra <hayabusagsm@gmail.com> Wed, 08 May 2019 04:51 UTC

Return-Path: <hayabusagsm@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 7B685120134 for <ipv6@ietfa.amsl.com>; Tue, 7 May 2019 21:51:21 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 WN-A37046KBI for <ipv6@ietfa.amsl.com>; Tue, 7 May 2019 21:51:19 -0700 (PDT)
Received: from mail-io1-xd32.google.com (mail-io1-xd32.google.com [IPv6:2607:f8b0:4864:20::d32]) (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 A945312004A for <ipv6@ietf.org>; Tue, 7 May 2019 21:51:19 -0700 (PDT)
Received: by mail-io1-xd32.google.com with SMTP id p2so4867089iol.2 for <ipv6@ietf.org>; Tue, 07 May 2019 21:51:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UsTHsA7KJ90P95npon3K1vEIo+OFgtFBqFD7O9vXGzw=; b=idVVbJa13NH3bFmYEfAjCDH1BCvr4OsVceJwtMtsKzUl/CL+MD1/IMjz9MOwLmDIIH VBtJ9tO9QNAD/nYZjsHyme+kosA+bXHB9hUTXmp4tPvXwLMLru07NlawGNgZlhuK7YoM wllvOwGBlylHztNoqpkUkxdGK02LG7Bet/hareixYA9o8cIZpTTzHIt6r8nfvrdds+d2 LkKm7A8oy5a3YDRkbUgDQKzo2BXVnefJ/5SRJ5pdR6Uk0cUPlnqPdW35jwUrfDkB/klI uu2J5HetXaSehvrU6q5+ndUD2EXRtYa6/bxi8pABhelW0+6yf39m90YWJPpBBO2lWlzZ 5zVA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=UsTHsA7KJ90P95npon3K1vEIo+OFgtFBqFD7O9vXGzw=; b=NmUzo0w+TIldpEvntEgWmxUYEtdwog0Qptkand/Z9qoSFK0oqt8gVy6b5rqUlzK2hE v+NWO6KpIOCjgb+e1ruPAy0Jt+uEVxllMyKGCwbLg4LchEZaWq8bhd8Ty8CKl3GQ1WOA tLnkAOzwd6sNUrNRJgYQmH+1c8NPSzeNGv7Zexk8/EwBRlLQAVqNaJaGnvus4OBHvIrQ +NPqB0g+mFSQ2ZjFaECd97GK71iKMbGhM6doZJaoQWHg3N26PiBzeFP2pYfomp8omiYI LdYD4NnffcReN1K95RNDAxKhhze/m/DOidui1NrbZaLSNgrLpaWCMertTm8LXpMVj3xx bgsA==
X-Gm-Message-State: APjAAAUxAq6TZo2yhjW+LVsbw6bbBliVHLTkSeDZ91h2mSxT5C9KZKR9 fuZsGWcw8zmf0Es4Fp2z/HpkD4qMC8TUFxYnCns=
X-Google-Smtp-Source: APXvYqyr3zIae5+bHoyBGPN3uPFDhNXTXywZQAx30hpX2Cn+vjNu5I9Y0LzFBhm9cf5zgxWiD79X67xw5cZWOYguEAg=
X-Received: by 2002:a5e:9516:: with SMTP id r22mr13130347ioj.22.1557291078756; Tue, 07 May 2019 21:51:18 -0700 (PDT)
MIME-Version: 1.0
References: <F8BFFCAD-E58E-4736-8A1C-56579B6F6032@employees.org> <a2465e81-a17f-ab48-efda-20fe12a70077@foobar.org> <30239E0C-C444-4A7E-8342-AEE47BF8A2BB@employees.org> <20190505200449.GB7546@vurt.meerval.net> <80073906-c3c0-1f22-9e7f-c2b349063936@gmail.com> <CAO42Z2xzVW3m0mN7jEn8SYyYCYhrufVnkfp3rBjJcijBkvucNQ@mail.gmail.com> <CACWOCC-35yVYXSRR0sRL-MBMHyOFZtJx9E9h14G8qqVh5T7qGA@mail.gmail.com> <232c1a43-0fd9-4eae-737b-260a3906f72a@gmail.com> <51F2BD2A-A590-4AF1-B8C1-FE62C9416340@steffann.nl> <8C63324F-FEF6-40BD-B918-B413CDEF9186@gmail.com> <BC988F7C-B262-4FF3-929A-02E6BCCE2266@steffann.nl> <BC23F51B-4135-47C6-B22F-8AE5CD8CB6F6@lists.zabbadoz.net>
In-Reply-To: <BC23F51B-4135-47C6-B22F-8AE5CD8CB6F6@lists.zabbadoz.net>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Wed, 08 May 2019 00:51:08 -0400
Message-ID: <CABNhwV138HVDDZf3+0wYPZoeu6j1nX5sZWhpfiaTzsQw=3BQKw@mail.gmail.com>
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: "Bjoern A. Zeeb" <bzeeb-lists@lists.zabbadoz.net>
Cc: Sander Steffann <sander@steffann.nl>, IPv6 List <ipv6@ietf.org>, Bob Hinden <bob.hinden@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008fadfa058859157c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/Dm6wlct4RcwpP5zheneIyfpgM0s>
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: Wed, 08 May 2019 04:51:21 -0000

I like this option below gives flexibility to the managed networks or use
cases where the desktops are not yet ready for IPv6 only and they can flip
the switch when the time is right in the future.

***From B Zeeb***
Given as of the last draft there is an option to disable processing
despite implementing, OS vendors can implement the draft and do what
they think suits their users.   Even more so they might leave the
default to “off” for now as an “advanced option to turn on” and
with a major OS update, once the world has moved on, flip the switch in
the future.

Gyan

On Tue, May 7, 2019 at 1:36 PM Bjoern A. Zeeb <
bzeeb-lists@lists.zabbadoz.net> wrote:

> On 7 May 2019, at 16:54, Sander Steffann wrote:
>
> > Hi Bob,
> >
> >> Would it help if the draft said the focus is for managed networks?
> >
> > Hmm. Just stating where it's supposed to be used doesn't prevent abuse
> > in other situations. If we can actually limit the potential impact on
> > devices on unmanaged networks then that would be great.
> >
> > I understand this is not easy, as the same devices will be used on
> > both networks.
>
> Given as of the last draft there is an option to disable processing
> despite implementing, OS vendors can implement the draft and do what
> they think suits their users.   Even more so they might leave the
> default to “off” for now as an “advanced option to turn on” and
> with a major OS update, once the world has moved on, flip the switch in
> the future.
>
> I can foresee a time when ISPs really don’t want to deal with the IPv4
> for end users anymore and you’ll be happy to have the option then.
> Based on 8+ years of an ipv6-only unmanaged home network (but some code
> under my control) I can tell you that I’ll be happy if more vendors
> start thinking “what if there’s no DCHPv4 or IPv4 gateway
> anymore?” now!  Especially all the smart gadgets that make it into the
> homes at the moment and multi-function devices.  If it doesn’t happen
> soon, your support calls will come the moment you want to have the flag
> and turn it on and it’s not there.  This is investing in a future to
> come now with the option to leave it off until we get to the point.
>
> That said I am sure ISPs already talking to many of these “smart
> entertainment device vendors” given they probably get enough support
> calls for them anyway..  It’s in your hands to give them an extra bit
> to better prepare for the future, and possibly in the meantime improving
> the dual-stack IPv6 as well.
>
> /bz
>
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>


-- 
Gyan S. Mishra
IT Network Engineering & Technology Consultant
Routing & Switching / Service Provider MPLS & IPv6 Expert
www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT
Mobile – 202-734-1000