IETF Logo Mail Archive

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

"Bernie Volz (volz)" <volz@cisco.com> Wed, 04 December 2019 20:21 UTC

Return-Path: <volz@cisco.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 01D9C12093F; Wed, 4 Dec 2019 12:21:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=buhVbZZR; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=PHUXpdVa
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 0xhYGGlR8C58; Wed, 4 Dec 2019 12:21:49 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A23C120808; Wed, 4 Dec 2019 12:21:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2414; q=dns/txt; s=iport; t=1575490909; x=1576700509; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=zeiStX/euKrCU3ID/hSvmKQRFJdmD98mgss6Q+UsE/k=; b=buhVbZZR2V5JHBT/M8TeUVvpkgv8UmADPgY0LaFEVWEvqUBMdjcbm/31 Q5SjkKJfOZHcJHHADVDhSxL1ANs1TeB8Tdnk6Cm84dw4L33D5PiZlShMn XLLNXJHjUjWORQJLgqgGmlNTnuPU74LvLbc6l2o+FvUvl2aO1SjBLZbzm 8=;
IronPort-PHdr: 9a23:Vo7asRTc4VHrG/anOlyWZb5vHtpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUANfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15NksAKh0olCc+BB1f8Kav0aCgoNM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BXAQC+FOhd/4sNJK1lHAEBAQEBBwEBEQEEBAEBgW0EAQELAYFKJCwFbFggBAsqCodnA4p6gl+YBIJSA1QJAQEBDAEBGAsKAgEBhEACghAkNwYOAgMNAQEEAQEBAgEFBG2FNwyFUgEBAQEDAQEQKAYBASwLAQsEAgEIDgMEAQEfECcLHQgCBAENBQgagwGCRgMuAQIMpgYCgTiIYIIngn4BAQWBOQIOQYJ/GIIXAwaBNgGFG4Z7GoIAgViCTD6CZAEBAgEBgUkYg0CCLI09iFeYOgqCLoY7ZI5WmiaOSohBkWICBAIEBQIOAQEFgWgjgVhwFRohgmxQERSMZoNzhRSFP3QBgSePMAGBDwEB
X-IronPort-AV: E=Sophos;i="5.69,278,1571702400"; d="scan'208";a="670544030"
Received: from alln-core-6.cisco.com ([173.36.13.139]) by rcdn-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 04 Dec 2019 20:21:48 +0000
Received: from XCH-RCD-013.cisco.com (xch-rcd-013.cisco.com [173.37.102.23]) by alln-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id xB4KLl91000745 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 4 Dec 2019 20:21:48 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-RCD-013.cisco.com (173.37.102.23) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 14:21:47 -0600
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 4 Dec 2019 15:21:46 -0500
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Wed, 4 Dec 2019 14:21:46 -0600
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=EkclWdn5PqrKJQ4+3lxfNrZR2TvpGqJGqby70WVwGZh1h1sruVVRz21Ce2Liqb1skOFzazth+u4R4ZgjbAaybya8adtHft4QlJLO203XBMQ3K1al9+ZUDxBRmMCPKPypc++aJXb28ECRHLv9sq7fXQ0VUWWvRlK+KNk/MfJ48guFvhcRsXRxhMlcVX0umGGUE06TcBRke8+STr+4FHrwpqkqmX+ylrupiMjeyDMWsAxAYTBLNMQ/4C0eXXJ5n1eeeHjiTEd3UyKVEchXL+bs6pzHnK0ZfyIW2VB2LCCvnrg+bfJ5EcgVwlmNYHgl6jKXUsQga+9goPCHje0PIgJJrA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=u++daovVBX9NocYG3TXM3Yx5W2iTNLW4jRR9SbO36gw=; b=O/nz9c/4EPEa42CId26Qd0rE9MvtdbNpfatG0ToN5PSfpTexcWu0xRnfKwKlWQodhGG1fY3gG/eln+8xdD4MUZ5FPRPsYiQqxWcTqxGyYfoTXuCiiapijD3qqxKgGIs19sgG2MfG/BlPTC+PcbgLidcZFLSGn225Y2RU3mL6H5VpwZY475NhBNefUVnVM+6aS6/IdDFvYEgsa5qAMOec14b7UI2VziMySCsbU6m6E3ZYhogSDpFoiRNrfcnJUC7T64uBsRxO0gXFQdlZBwJOrwiG4FSK7Z7NfGpZ5kwB8U84gIOBqW9znV7Dq+SrZ2AaG1MpuPrmTiymozMjZe/41g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=u++daovVBX9NocYG3TXM3Yx5W2iTNLW4jRR9SbO36gw=; b=PHUXpdVajtfSpeX8MrmRrWedrbASJuhA9Dn69mu+KxqkFY0VI+4auTt8eIMmETCdn/Hnxoqc1Ho0l0FF0JAaqrE//+f3zPdVVobH354FHeJpEHQ6abbegrC2SZJJaN/CwcXzoUQ3KfvMj6xsJx8L0aVh+LQqE14Ne5q8ASRITSA=
Received: from DM6PR11MB4137.namprd11.prod.outlook.com (20.176.126.158) by DM6PR11MB3164.namprd11.prod.outlook.com (20.176.120.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2495.21; Wed, 4 Dec 2019 20:21:45 +0000
Received: from DM6PR11MB4137.namprd11.prod.outlook.com ([fe80::4194:dade:1d47:2678]) by DM6PR11MB4137.namprd11.prod.outlook.com ([fe80::4194:dade:1d47:2678%6]) with mapi id 15.20.2495.014; Wed, 4 Dec 2019 20:21:45 +0000
From: "Bernie Volz (volz)" <volz@cisco.com>
To: Jen Linkova <furry13@gmail.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
CC: "draft-link-dhc-v6only@ietf.org" <draft-link-dhc-v6only@ietf.org>, V6 Ops List <v6ops@ietf.org>
Thread-Topic: [dhcwg] IPv6-Only Preferred DHCPv4 option
Thread-Index: AQHVqpuzpq5GW9sfF0KRMvO8RARyP6eqau3A
Date: Wed, 04 Dec 2019 20:21:45 +0000
Message-ID: <DM6PR11MB413728801AD154A439114E6BCF5D0@DM6PR11MB4137.namprd11.prod.outlook.com>
References: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com>
In-Reply-To: <CAFU7BAR1JLUZps=CAqJfeQtUf-xQ88RYvgYrPCP+QP0Ter7YFg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=volz@cisco.com;
x-originating-ip: [173.38.117.78]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b84ae4bd-9cc4-4f17-8431-08d778f7954c
x-ms-traffictypediagnostic: DM6PR11MB3164:
x-microsoft-antispam-prvs: <DM6PR11MB316430EB6752AE2B925CF61BCF5D0@DM6PR11MB3164.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 0241D5F98C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(376002)(396003)(136003)(39860400002)(366004)(199004)(189003)(51444003)(13464003)(2501003)(110136005)(14444005)(8936002)(9686003)(74316002)(305945005)(55016002)(52536014)(6116002)(5660300002)(3846002)(54906003)(25786009)(11346002)(14454004)(478600001)(66574012)(99286004)(7736002)(186003)(53546011)(6246003)(19627235002)(8676002)(81166006)(26005)(86362001)(2906002)(102836004)(81156014)(71200400001)(7696005)(76176011)(6436002)(4326008)(76116006)(71190400001)(64756008)(66446008)(966005)(66476007)(66556008)(229853002)(6306002)(66946007)(316002)(6506007)(33656002); DIR:OUT; SFP:1101; SCL:1; SRVR:DM6PR11MB3164; H:DM6PR11MB4137.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: BqfgNKQFdXGGUJmzJ17Oto2RZ42HVqQclXJ8mr0Bl9DZ9yWJNx9i/dsxbhg+Srqv70TIPmkgWilKoZbl1O7j4nIV9tq6a5sGv9HrF6NYtI0EsIeCzcMVQqSsxMhuj5CuhKEtiM5bcP/QzAyH0WR6nGDDdpGJXkdQ+2+Bxz3k8N+m6suxKrkl8TJPUBXrPxDP8YP7rMnzMDPZSvae1e5r+lBG6/8UVHgK9KC/IjkxMti6WaftVa6y3K9I2k0aYdldInaNMCcljc1++1ZSPsYmjudONfTq/buKX7D1RZvCdNjYSIOvJhWgYNBfRLwYzmpuzsOvkDBnvbn3yQ7Hoe1X2sqGflYnBdYdeJ0c7m8NNjd4Nfo6bVjn0BNJb2L/Jp98wvQTRrNU5zxPNkiO3jnsOgCtiNRsywpF5TiGYztp7WapfZyHmgvWk7E8/5eDOQ8DM3P+yMJBuUzOhdGETYIHbOmTZCTyRFmttO/8AmHPnE7zBbXpXN2Ca003IE6iO7tcTut6/B15w3BkQt7Bt2HHPsC9G1aXLBSHp2m61RXhXWgyG4+f1VnGqpjjXoB4Sk2D
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b84ae4bd-9cc4-4f17-8431-08d778f7954c
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Dec 2019 20:21:45.1600 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: //RQ0PzTcFJgJu9V6ZvlEfILkOBlzTF4Xy5DNtsme2CFTf+lA4Of3vUV5h7tvKy1
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR11MB3164
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.23, xch-rcd-013.cisco.com
X-Outbound-Node: alln-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/8rLQ1cPrDcOdnBJ2oBE90V4DL4w>
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: Wed, 04 Dec 2019 20:21:51 -0000

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".

Also s/signalling/signaling/.

- Bernie

-----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

v2.23.0 | Report a Bug | By Email