IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 May 2019 23:02 UTC

Return-Path: <brian.e.carpenter@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 72AC912012C for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 16:02:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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_PASS=-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 b5OA5D7OcyAs for <ipv6@ietfa.amsl.com>; Thu, 9 May 2019 16:02:06 -0700 (PDT)
Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) (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 5AB3D1200DF for <ipv6@ietf.org>; Thu, 9 May 2019 16:02:06 -0700 (PDT)
Received: by mail-pg1-x52c.google.com with SMTP id h17so1974881pgv.0 for <ipv6@ietf.org>; Thu, 09 May 2019 16:02:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=CCTHGxX1/VCKI7keAINX++Br6C3cNzLik2JZaHA7o4Y=; b=Oguou0f00tJnI2h1DHiNPnSq9bGn8mrSSvJ5xLtyZhVbP1D76mb04+8QdaaZdvf9Hh 6Ves0EU5iZS31SrUJ5lDuiowQZWGjgom45fxCSULm4hm1b5NR/iBF4FjF8MxH6UtX8iz PF6Im468exAMVUlsJxiHWSdyyYFUW3dYxyIBCpldfAjiD2wjedkxbR5RGH2kAGMiRCWm 7YgjK14dd2oXvgvKZJ5LHvbUul8hPHPvZQIIgJHdXU3QASisupw0vevYUvCqx6niMF+u 7/SEAQoENd2eMaAymZoZZO2opeuf98tNFNvhZe2WmYRZPmJxdyomFBX79otxiDA8hbYw Omww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=CCTHGxX1/VCKI7keAINX++Br6C3cNzLik2JZaHA7o4Y=; b=t3WNF6r4iJHHkX5dUd7qc6vh6pGXadNZ0xxcUIuyJs1A2U1DuCPRaOAxMxE9GlpC81 y9qDfS6WCbjXWFgbnRF0WIkr1rLCBvoZ30A3neCCeeygRxIV3c2z9ejGDhCziCEvB0BT uIG6S+KktQ+oSsFbY3c3RAYkvamSawSv6QFs+Eq2Fhyb6yPV7ocwslDgoDMON9ChjWNq Rjj7nmOddxyU6HW7a+OzHxFZ01Z/l22DC8AeNh1vMIiq5YBy6/eo5Urzk3D067xGowJ+ E2ftpjBPGCb1dr5HkEi9fIN4Rgy8nuIOaQyvoTDyvd3pGyBiQhi9ql5qOnyI/tTQRf64 jR2A==
X-Gm-Message-State: APjAAAVaYsF7G64KoROWwvIowE/09xopuIcmjxS7CHNVnIQfn4tIag5l 4qFOShu1/JP8wiPOn1ckW+MFigLq
X-Google-Smtp-Source: APXvYqy0NLnEI6Fl5Dey4tLmTPSjKkPkgMSWRZBUjwI6kRRF4Djyc6PtklxMGX8QtBByCld9it5HFg==
X-Received: by 2002:a63:10c:: with SMTP id 12mr9431277pgb.276.1557442925871; Thu, 09 May 2019 16:02:05 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.72.205]) by smtp.gmail.com with ESMTPSA id c23sm9953823pfp.0.2019.05.09.16.02.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 09 May 2019 16:02:05 -0700 (PDT)
Subject: Re: Confirmation to advance: draft-ietf-6man-ipv6only-flag-05
To: Philip Homburg <pch-ipv6-ietf-6@u-1.phicoh.com>, ipv6@ietf.org
Cc: Lorenzo Colitti <lorenzo=40google.com@dmarc.ietf.org>
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> <m1hOfCR-0000JYC@stereo.hq.phicoh.net>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <7d6c1a74-0164-cc05-6cd7-4b68db88e1ef@gmail.com>
Date: Fri, 10 May 2019 11:02:02 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <m1hOfCR-0000JYC@stereo.hq.phicoh.net>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/8-8E5dnHD2xo1hfawRs9CBetrYw>
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 23:02:09 -0000

On 09-May-19 21:18, Philip Homburg wrote:
>> 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:

True, but rather irrelevant to the value of *this* hint.

   Brian

> 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.
> 
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>

v2.23.0 | Report a Bug | By Email