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

Tomek Mrugalski <tomasz.mrugalski@gmail.com> Tue, 10 December 2019 00:35 UTC

Return-Path: <tomasz.mrugalski@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 5ECEB120810; Mon, 9 Dec 2019 16:35:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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] 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 kwU2ciY1TeB7; Mon, 9 Dec 2019 16:35:07 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 1A54F120020; Mon, 9 Dec 2019 16:35:07 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id d20so17758273ljc.12; Mon, 09 Dec 2019 16:35:06 -0800 (PST)
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-transfer-encoding:content-language; bh=MC500x2BUnfihAkUcsGLlwzAz+LZjMwAJ4QgMovNuaw=; b=Fc6zLEUjJirN/ixqXNCpXQZ9o85V4s7SE6h2rUX7d79iIJWC2VjI3qKqdfc8fErd7h uQf9fGSY9q+68rGuV8lePChMDX2EXCwsJu5hyMna1wkXStGMbVHVJSXab7+UT7ocjrS5 d8Uts/enp286LPvKon6QTqSTvwqPdNCVUwH626LqsLwk51tIsKLqgWVUhHGDa2ugH+vT QAgKoqG4fgdwX5hWA09YynZtLMAkI2SsPkShrprojQ+lShyiW8ZGDY5eiK4LjzklIav5 +6+jzgDqX5Qa5fjT6GtEYxoDYi5gyVYQvrwlfKi6CyCHQ5/CyLvu2vYp6pzy8ztiw6QY z2mw==
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-transfer-encoding :content-language; bh=MC500x2BUnfihAkUcsGLlwzAz+LZjMwAJ4QgMovNuaw=; b=A39DcPuXFNBzrH+YlhgsPYaxhznIIYO+hg2S4K+15mo9RAVt4YbxSI5ouwfs/+jbjZ 8xcQ8boCJfxuF5CAUcxNvCCOnt1Q/lI/I+Weu6saS0KaccD6ReUkQVqxaabQs2TQOWGN FUB86QkO0SHLMNHBnbMV/0ngLmvTT/r3xt+JeK/eo8yVtw8A3inImk1nQ7DLmH6IaDS4 thEb/ehRvdKM6ZDYvMFUAmlj30QonbYxa1qHhEu8+0O4wxq5ZBB5RJOoClUV8L+5xle+ dnmTjJz0kOYEOYHwub2FZhugH4ca1SM2auxyKEcNnqYfHQsW1Kx5ukXV5+Tdum12S2ml 3+dQ==
X-Gm-Message-State: APjAAAXgCPYBEfmQYqTbT1Gi6rctSBmyl4V8iXGNStKh/sknlQzWkSmY 7k20OHfEiZkoEhJpXNK9aHHW+fNIpcwgkw==
X-Google-Smtp-Source: APXvYqwqTBhGFYZqnU6bjS/P44Q6dsd4jqTnxdQtL0PEN/3akPoxne28Tnt1kUBYI1TShvxp62vTTw==
X-Received: by 2002:a05:651c:285:: with SMTP id b5mr18669449ljo.14.1575938105031; Mon, 09 Dec 2019 16:35:05 -0800 (PST)
Received: from [192.168.1.100] (109241079151.gdansk.vectranet.pl. [109.241.79.151]) by smtp.gmail.com with ESMTPSA id m24sm855081ljb.81.2019.12.09.16.35.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 09 Dec 2019 16:35:04 -0800 (PST)
To: "Bernie Volz (volz)" <volz@cisco.com>, Ted Lemon <mellon@fugue.com>, Jen Linkova <furry13@gmail.com>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, V6 Ops List <v6ops@ietf.org>, "draft-link-dhc-v6only@ietf.org" <draft-link-dhc-v6only@ietf.org>
References: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com> <32A5E9AF-60E8-413D-B724-400363F32B09@fugue.com> <DM6PR11MB4137D1FD0EB273C41886E307CF5D0@DM6PR11MB4137.namprd11.prod.outlook.com>
From: Tomek Mrugalski <tomasz.mrugalski@gmail.com>
Message-ID: <45763b7f-1d76-78b0-5d7f-6469b25a007c@gmail.com>
Date: Tue, 10 Dec 2019 01:35:01 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <DM6PR11MB4137D1FD0EB273C41886E307CF5D0@DM6PR11MB4137.namprd11.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/yFJPMh-KYkBL65uR6KsWcdw7vqE>
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: Tue, 10 Dec 2019 00:35:09 -0000

On 04.12.2019 19:36, Bernie Volz (volz) wrote:
> A minor note about the draft requesting use of (DHCPv4) option code 108. Per RFC3679 this was in use as a "swap path" option at some point, though never published as a draft. That is why it is marked as "REMOVED/unassigned" as the idea was to NOT reuse these option numbers until there was a need (i.e., no other just "unassigned" option codes were available). While I have no objection if the draft wishes to request use of that option code, I just wanted to point out that there could be some other conflicting usage out in the wild.

As a person who put that text there, let me explain my reasons. RFC2132
(Mar 1997) said that option codes 128-255 were reserved for
site-specific options. RFC3942 (Nov 2004) reclassified 128-223 as a
general purpose option codes under IANA governance. However, any
implementation created between 1997 and 2004 could have used those
option codes for whatever purpose they desired. It's been quite a long
time ago, but we all know about long tails.

With that in mind, I tried to find the lowest option code that's
available. I was not able to find any specific information about prior
use of codes 102-107, except RFC3679 saying they were returned (and thus
previously used by someone). Code 108 seems safer than other codes - it
is below 128, RFC3679 explicitly says that there was an idea to use it
for swap path, but that must have died quickly if no I-D was ever
published about it. So it seems like a safe bet.

At the end of the day, this is only a request for IANA. If this gets
published, they may honor or ignore it.

Tomek

p.s.
Apologies for sending it today. Museums are supposed to be closed on
Mondays.