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

Jen Linkova <furry13@gmail.com> Thu, 05 December 2019 00:26 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 6927B12004C; Wed, 4 Dec 2019 16:26:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level:
X-Spam-Status: No, score=-1.748 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 NjjCeybECM2t; Wed, 4 Dec 2019 16:26:26 -0800 (PST)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 D73B412002F; Wed, 4 Dec 2019 16:26:25 -0800 (PST)
Received: by mail-qk1-x730.google.com with SMTP id v23so1833572qkg.2; Wed, 04 Dec 2019 16:26:25 -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:content-transfer-encoding; bh=S8bVSEGBopxFiO6OKdHrplV117IxcuV4hHFvnD4usRI=; b=gD5WaYjDq63yKka8tiS0t/iC3Cf/9go4iRLz2mwvFfQCPDXfZ/IOyWiZzo2xEM5Xdg 8pXG21QzkEf0o4+CR9VWCmapjGhO3vk02ETLu8F/AzoaGC8fThz/+kV4m7gF3Y2fTTbt rCw4Iqo1Jb7GFbGS6j8CXdIeHCyxdtYeICBXxB8ZgZ3gMfMCSA9W/1fKxOAZKc17HLDg nV+u9yLu7o/qMRFlXbaZYiQfK2+CxAVvozl8/Zy6lcbmUseH0+rohBwfkma5vQxmYohP JnOAXWl4QHKd/y73BcxUQ9wZ38QC7jqsKOkoJ0QknSrVIVuINirpXaKvucdgrn7iaDjF Ha2g==
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:content-transfer-encoding; bh=S8bVSEGBopxFiO6OKdHrplV117IxcuV4hHFvnD4usRI=; b=DpOf8BQfzZ2dvKXVkLdlgeERl3TK9nEcTfuRWv0/FTxfKlMSeUFUSnYaNJrSzar7oe npTElIzBnN/7jwQwZx59JUEjXh6XBqC3Sn/jE5nOuNOFQPUpSFaAbxpbkQVe0IQoblBj OH/sErJBReQfjt6uygZZPz+fh5nul1zohxWp5ubecoP8mgOffYP/RoK6FdMF69A2v/RN fOn0lHhotLpHITevB5exxu/0JCHfKoxmVbfm93U54EQ0rru2nxKJzms/po//DWrvHemE 4XTGmIVzVDIXJv9Le7tQIjOJGgCmw+IQcncCBBZylf7IVClMfauuyCXO25Y2yIkQQ37P fInA==
X-Gm-Message-State: APjAAAWKbLFFzlJSgexbcGal99xvft6Gp/dQsqCO3REsXWhJnU+ZbEjr 8xE246Oeh5IZu0RfKJdbrpj5VTI/Q9fQQi6yQlU=
X-Google-Smtp-Source: APXvYqyP1dOSgrNU4y6SKr4Ox2XgydfqVP5QJowzAGqtyZyH4d61bmVM1pUuhHBj4BMjJ9oxmiuFkAJ2cMm6AFPnW/I=
X-Received: by 2002:a05:620a:10b8:: with SMTP id h24mr5917757qkk.332.1575505584593; Wed, 04 Dec 2019 16:26:24 -0800 (PST)
MIME-Version: 1.0
References: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com> <DM6PR11MB413728801AD154A439114E6BCF5D0@DM6PR11MB4137.namprd11.prod.outlook.com>
In-Reply-To: <DM6PR11MB413728801AD154A439114E6BCF5D0@DM6PR11MB4137.namprd11.prod.outlook.com>
From: Jen Linkova <furry13@gmail.com>
Date: Thu, 05 Dec 2019 11:26:12 +1100
Message-ID: <CAFU7BASCMjFLBh+cbvS3Rg396vxMxN1ZN-hEbLss8_afA3ddXg@mail.gmail.com>
To: "Bernie Volz (volz)" <volz@cisco.com>
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "draft-link-dhc-v6only@ietf.org" <draft-link-dhc-v6only@ietf.org>, V6 Ops List <v6ops@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/JnlSiP4uaTFMfKgqUctGYKKV6v8>
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 00:26:27 -0000

On Thu, Dec 5, 2019 at 7:21 AM Bernie Volz (volz) <volz@cisco.com> wrote:
> I think there is a typo in Section 2 (middle paragraph):
>
>    Another benefit of using DHCPv4 for signalling is that IPv4 will be
>    disabled only if both the client and the server indicate IPv6-only
>    capability.  It allows IPv6-only capable clients to turn off **IPv6**
>    only upon receiving an explicit signal from the network and operate
>    in dual-stack or IPv4-only mode otherwise.
>
> I think that "turn off IPv6" should be "turn off IPv4".

Oh indeed! Will be fixed in -01.
Thanks for pointing out!

> -----Original Message-----
> From: dhcwg <dhcwg-bounces@ietf.org> On Behalf Of Jen Linkova
> Sent: Wednesday, December 4, 2019 7:09 AM
> To: dhcwg@ietf.org
> Cc: draft-link-dhc-v6only@ietf.org; V6 Ops List <v6ops@ietf.org>
> Subject: [dhcwg] IPv6-Only Preferred DHCPv4 option
>
> Hello,
>
> One of the biggest issue in deploying IPv6-only LANs is how to do it incrementally, when some hosts work just fine in NAT64 environment while some legacy devices still need IPv4. Doubling the number of network segments (having an IPv6-only and dual-stack segments of each
> type) is an operational nightmare. So it would be just awesome if all devices can co-exist in the same network segment and hosts capable of operating in IPv6-only environment do not consume IPv4 addresses.
> So here is the draft proposing a new DHCPv4 option to help saving IPv4 addresses and deploying IPv4-as-a-service:
>
> Name:           draft-link-dhc-v6only
> Revision:       00
> Title:          IPv6-Only-Preferred Option for DHCP
> Document date:  2019-12-04
> Group:          Individual Submission
> Pages:          9
> URL:
> https://www.ietf.org/internet-drafts/draft-link-dhc-v6only-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-link-dhc-v6only/
> Htmlized:       https://tools.ietf.org/html/draft-link-dhc-v6only-00
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-link-dhc-v6only
>
>
> Abstract:
>    This document specifies a DHCP option to indicate that a host
>    supports an IPv6-only mode and willing to forgo obtaining a IPv4
>    address if the network provides IPv6 access.
>
> Any comments/suggestions/reviews are highly appreciated!
>
> Adding v6ops@ to Cc: as the problem is related to operating IPv6-only networks.
>
> Thank you!
> --
> SY, Jen Linkova aka Furry
>
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg



-- 
SY, Jen Linkova aka Furry