Re: [v6ops] [dhcwg] IPv6-Only Preferred DHCPv4 option

Jen Linkova <furry13@gmail.com> Thu, 05 December 2019 07:01 UTC

Return-Path: <furry13@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D210A120059; Wed, 4 Dec 2019 23:01:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 rfk1gU0x5zqg; Wed, 4 Dec 2019 23:01:29 -0800 (PST)
Received: from mail-qv1-xf42.google.com (mail-qv1-xf42.google.com [IPv6:2607:f8b0:4864:20::f42]) (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 5F2BD120096; Wed, 4 Dec 2019 23:01:29 -0800 (PST)
Received: by mail-qv1-xf42.google.com with SMTP id t5so911495qvs.5; Wed, 04 Dec 2019 23:01:29 -0800 (PST)
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=DLBRk41jf03ru8mMdUsqk1vqU4PQnmJxImb/gf3yRH8=; b=A67dv5rTdDNPYPXhC9mLxVdtcRoeXqLKVM8NycA77/CMaURhQWPGSmIzdcVJo4Man/ acKbolYNJk741mlKenh8BtvX4g1lwkFgu29k+R0Nb0m7UlJbIuXV0ShjTzf13pyiEovb 862dHsHhklzqj+6gRjfIMKmDZYIOugPS4lW/iCalwaZax7f8RjeB/NIXwxup1KT2TY3z nJK3iF4xr1ELg5nNA24871H6kKFgDpUPG7HBJj+w+fOHxjFTS7I6etwCotRMIgm0jWLz odKP4EMSPRQsN6N1apXO9zNo99UtK7O7clvpCBIgGOetRMRWcr+JcSDfG83It1mf2q1w SnbA==
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=DLBRk41jf03ru8mMdUsqk1vqU4PQnmJxImb/gf3yRH8=; b=ZiqkDLFVvlYDI1XIC8Q1Amzdk7BMyNL/Eyg4QpeTzbI3tY/1h5P+42juoyoSnYBjrH sR9T1pwqDzFpXbPlaHk7+mhsQTc5XzSYIgZISZyFCXjsN6Wx8+V9bSX4053q3ELu2eo2 QYPiJUfyIYfLLTKkISTz8HPNKLvXaqBoTcR7++lMkjtLv0yZZWaXwa00lJylGF1P7C5T mJ3V0HfdN8re6pQMN2XigVKYwyVc4GdRTWt/DG/Mbn06PdiKgXYk0W1M5tBpGUFqY8y7 GwcU7XuWy48YMZf1WXnBthP1pTIWYg8L8uQvuWiUa9qZqiV43x/v+8jwY6pbctgGW9ld HdVg==
X-Gm-Message-State: APjAAAUMOop9gHvS8KKjq8Gt01GxthEAEOvQYOCO68g4hz3WDsQ7hu0A 3lEEIgN/9ILlhShj/27todG31lzed3fHAkFZ9FkaMamteBQ=
X-Google-Smtp-Source: APXvYqx2mYKV3o7+TlHO1wwifBQXbnPI3AOJWVFUgcTkPiTjocMcVKqcwaoIOzGMJyqOlLfRg9DCpj/JK1PELvkcjuQ=
X-Received: by 2002:a0c:eed2:: with SMTP id h18mr6231674qvs.184.1575529288013; Wed, 04 Dec 2019 23:01:28 -0800 (PST)
MIME-Version: 1.0
References: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com> <da078a21-b606-f0d9-3833-d66b20410853@marples.name> <CAFU7BASdWZv1RTVa5v4thbKPqCrmG886G+hK2J0UoZ3TbELDnw@mail.gmail.com> <b52fdd35-9663-e7df-7303-748a6b3a57ce@marples.name>
In-Reply-To: <b52fdd35-9663-e7df-7303-748a6b3a57ce@marples.name>
From: Jen Linkova <furry13@gmail.com>
Date: Thu, 05 Dec 2019 18:01:16 +1100
Message-ID: <CAFU7BAREX1MX_jRNMMyRskiCTcsXJO_Gmc4aSJ78cdrL7eMh8Q@mail.gmail.com>
To: Roy Marples <roy@marples.name>
Cc: dhcwg@ietf.org, draft-link-dhc-v6only@ietf.org, V6 Ops List <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/FoHmC9RoQ7_raqm5cJ9gKuXapVo>
Subject: Re: [v6ops] [dhcwg] IPv6-Only Preferred DHCPv4 option
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Dec 2019 07:01:31 -0000

On Thu, Dec 5, 2019 at 12:12 PM Roy Marples <roy@marples.name> wrote:
> It assmues only IPv6.
> I dislike it when different protocol families discuss each other - IPv6
> should not turn off IPv4, likewise IPv4 should not turn off IPv6.
> I would prefer it if Iv6 was not mentioned at all outside of a use case
> for the option.

There is a catch there.
Right now the *only* possible scenario when a host might consider IPv4
optional is that:
1) the host supports IPv6
2) either all applications on that host work in NAT64 environment or
the host is doing 464XLAT.
3) the network provides NAT64.
The host knows if conditions #1 and #2 are met and signals it to the
network, so DHCP server responds 'OK, #3 is met as well'.

Now if we stop assuming IPv6 - even worse, if we stop assuming NAT64
being the only transition mechanism - we might end up in a following
situation:
[host] : dear network, IPv4 is optional for me  (because the host can
work in NAT64 environment)
[ the network] ah great, we've been trying to reduce IPv4 footprint so
we deployed IPv15 and the corresponding transition mechanisms, namely
NAT15-to-4, so I'm not going to give an address.

So the host is willing to make IPv4 optional *conditionally*  and
currently that condition is 'NAT64'. We either explicitly describe
that condition in the draft or - as it's been suggested in the thread
- we start encoding it in the option. So if the option value is '1' it
means 'IPv6-Only with NAT64', value 2 - some other 6-to-4 transition
technology we might invent tomorrow, and 3 - some shiny IPv4-to-IPv15
thingy.

> > The draft covers that scenario. DHCPv4 is disabled for V6ONLY_WAIT seconds.
>
> Is the wait seconds even needed?
> Just set the T2 timer and treat it as leasing the unspecified address.
> Less data on the wire, less churn in DHCP clients. V6ONLY_WAIT provides
> nothing of value as I see it.

I suspect it would complicate the configuration. Currently my lease
time is 30 mins. But I do not want IPv6-only capable clients to come
back so often, so I'd be probably setting V6ONLY_WAIT to a number of
hours. While IPv4 clients will continue to receive short lease time.


-- 
SY, Jen Linkova aka Furry