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

Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com> Thu, 09 May 2019 09:18 UTC

Return-Path: <pch-b9D3CB0F5@u-1.phicoh.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 DFB17120020 for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 02:18:52 -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] autolearn=unavailable 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 0B6rYRySsW-1 for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 02:18:52 -0700 (PDT)
Received: from stereo.hq.phicoh.net (stereo6-tun.hq.phicoh.net [IPv6:2001:888:1044:10:2a0:c9ff:fe9f:17a9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7A111200CD for <ipv6@ietf.org>; Thu, 9 May 2019 02:18:51 -0700 (PDT)
Received: from stereo.hq.phicoh.net (localhost [::ffff:127.0.0.1]) by stereo.hq.phicoh.net with esmtp (TLS version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384) (Smail #157) id m1hOfCR-0000JYC; Thu, 9 May 2019 11:18:47 +0200
Message-Id: <m1hOfCR-0000JYC@stereo.hq.phicoh.net>
To: ipv6@ietf.org
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
From: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>
Sender: pch-b9D3CB0F5@u-1.phicoh.com
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> <478d5dc5-af00-4ab0-d8ef-75e41cd501d4@foobar.org> <CAKD1Yr1OcQqxv1Z5XA7OBMfyC7kayXUOLJEGvY8QVu0XB-H=Xw@mail.gmail.com> <17174.1557343049@localhost> <CAKD1Yr0LMbqmS_C0y0K8m3mm0MTTon8FqsHp_chNTHYh-zWCQA@mail.gmail.com>
In-reply-to: Your message of "Thu, 9 May 2019 08:50:06 +0900 ." <CAKD1Yr0LMbqmS_C0y0K8m3mm0MTTon8FqsHp_chNTHYh-zWCQA@mail.gmail.com>
Date: Thu, 09 May 2019 11:18:46 +0200
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/6D-8Xlzxy2h4Ky8lC25koEObYKs>
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 09:18:53 -0000

>The most obvious thing
>to do with it would be to reduce the DHCP  client exponential backoff or
>perhaps even give up on DHCP altogether if it did not succeed within a
>given timeout.

I think there are already plenty of other hints that can be used to backoff
DHCP:
1) If the host has working IPv6 and working IPv4aaS then it can agressively
   backoff DHCPv4 or give up.
2) If a host has working IPv6 it can agressively backoff DHCPv4 until it 
   first resolves a domain that only has an A record and no AAAA (or there is
   another reason to connect to an IPv4 address)
3) In theory, but I don't know if there are operational issues with this,
   if a host sees DHCPv4 discovers from other hosts and no offers then the
   host can agressively backoff DHCPv4. When the host sees an offer it can
   try again.