Re: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'

"Bernie Volz (volz)" <> Fri, 15 September 2017 19:56 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0D18F133207 for <>; Fri, 15 Sep 2017 12:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Status: No, score=-14.519 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id u2ppri_i6ExK for <>; Fri, 15 Sep 2017 12:56:37 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id CFE001331F5 for <>; Fri, 15 Sep 2017 12:56:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=23686; q=dns/txt; s=iport; t=1505505396; x=1506714996; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=3rXW/+Z3qZuDyA+wV8opd4DXDUkdOzzu2dJD5mCk74o=; b=MjP1gZpxQnEwt9V0Zj4aARMZPnsQvdE88apt/6Cc33TghnG3aeqZl2X/ OMsyb5U3DnwutTUBzsUHqvD1pooUbCCeIwWwjEKDPuE8RwGdAQrxolRTS 527C2XMUa2lJ07+h4bLDJT7RPClp9S29RT1/zf3su9CQaEQmgQMie7UY3 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CaAQATL7xZ/5ldJa1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgm9rZG4nB4NumhOBdIg7jWyCEgolhRcCGoQQQBcBAgEBAQEBAQF?= =?us-ascii?q?rKIUYAQEBAQMjCkwQAgEIEQQBASgDAgICHxEUCQgBAQQBDQUIDAeJNEwDFRCra?= =?us-ascii?q?4InhzUNg2oBAQEBAQEBAQEBAQEBAQEBAQEBAQEYBYMrggKDMoMpgliCLgkPEIJ?= =?us-ascii?q?dgmAFoEk8AodZiAOEbpMBjFqILQIRGQGBOAEhATWBDXcVh2V2AYZTBYEtgQ8BA?= =?us-ascii?q?QE?=
X-IronPort-AV: E=Sophos; i="5.42,398,1500940800"; d="scan'208,217"; a="77985044"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Sep 2017 19:56:35 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v8FJuZ4D012967 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 15 Sep 2017 19:56:35 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1263.5; Fri, 15 Sep 2017 14:56:35 -0500
Received: from ([]) by ([]) with mapi id 15.00.1263.000; Fri, 15 Sep 2017 14:56:35 -0500
From: "Bernie Volz (volz)" <>
To: "Templin, Fred L" <>, Suresh Krishnan <>
CC: "" <>
Thread-Topic: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'
Thread-Index: AdMdAAkfD4sQrO/BQ3+nFUZgsVrgiwA3VgYAAAldv1AEFjUMUA==
Date: Fri, 15 Sep 2017 19:56:35 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_d459c197a1334283b69cb6925277684cXCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 15 Sep 2017 19:56:39 -0000

Hi Fred:

My personal view is …

While many of us would have liked to see DHCPv6 PD used in this situation, I think this work is a nice practical solution without requiring new functionality in hosts. It is a deployment document (hence why it is in v6ops) – anyone can do this without requiring anything from the hosts that they don’t already support. That isn’t the case with DHCPv6 PD (most hosts don’t support this).

-          Bernie

From: dhcwg [] On Behalf Of Templin, Fred L
Sent: Friday, August 25, 2017 11:45 AM
To: Suresh Krishnan <>
Subject: Re: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'

Hi Suresh,

My intent on posting was to make the dhc community aware that there is a
BCP document in the publication queue that makes statements about DHCPv6.
My point about IA_PD concerns the following draft text:

   o  M-flag = 0 (UE/subscriber address is not managed through DHCPv6),
      this flag may be set to 1 in the future if/when DHCPv6 prefix
      delegation support is desired)

I find the text “may be set to 1 in the future if/when DHCPv6 prefix delegation
support is desired” to sound as if it is casting doubts on whether that future will
ever arrive. Can this WG live with text of this nature going forward in a BCP?

I do not have any specific comments on IA_NA; my area of interest is IA_PD.
But, others in this community may want to have a look.

Thanks - Fred

From: Suresh Krishnan []
Sent: Friday, August 25, 2017 6:05 AM
To: Templin, Fred L <<>>
Subject: Re: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'

Hi Fred,

On Aug 24, 2017, at 1:42 PM, Templin, Fred L <<>> wrote:

Have people in this community seen the following document that is working
its way through the publication process in the 'v6ops' working group:

It seems to make some very limiting statements about DHCPv6 in a similar
spirit as was done in RFC7934 (the limiting statements apply to both IA_NA
and IA_PD).

There are a couple of references to DHCPv6 in the draft. I do not see any limitation to the use of IA_PD.

There is a recommendation against a IA_NA *only* network that is a straight reference to RFC7934 and nothing additional

"an IA_NA-only network is not recommended per RFC7934<> [RFC7934] section 8<>"

I have asked for the motivation for the text (See my ballot at

"however it SHOULD NOT use stateful DHCPv6 to receive a service provider managed IPv6 address”

Is there some specific text you are concerned about?