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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Mon, 18 September 2017 18:30 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8D181332DF for <dhcwg@ietfa.amsl.com>; Mon, 18 Sep 2017 11:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.22
X-Spam-Level:
X-Spam-Status: No, score=-4.22 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 gV3cHus8TRsW for <dhcwg@ietfa.amsl.com>; Mon, 18 Sep 2017 11:30:35 -0700 (PDT)
Received: from phx-mbsout-01.mbs.boeing.net (phx-mbsout-01.mbs.boeing.net [130.76.184.178]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6414E1241F3 for <dhcwg@ietf.org>; Mon, 18 Sep 2017 11:30:35 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id v8IIUY6w013582; Mon, 18 Sep 2017 11:30:35 -0700
Received: from XCH15-06-10.nw.nos.boeing.com (xch15-06-10.nw.nos.boeing.com [137.136.239.219]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id v8IIUNlT013002 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 18 Sep 2017 11:30:23 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-10.nw.nos.boeing.com (2002:8988:efdb::8988:efdb) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 18 Sep 2017 11:30:22 -0700
Received: from XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) by XCH15-06-08.nw.nos.boeing.com ([137.136.238.222]) with mapi id 15.00.1320.000; Mon, 18 Sep 2017 11:30:22 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Bernie Volz (volz)" <volz@cisco.com>, Suresh Krishnan <suresh.krishnan@gmail.com>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'
Thread-Index: AdMdAAkfD4sQrO/BQ3+nFUZgsVrgiwA3VgYAAAldv1AEFjUMUACT6LkA
Date: Mon, 18 Sep 2017 18:30:22 +0000
Message-ID: <00e2e45c213d4e0cae5927012ebefc8b@XCH15-06-08.nw.nos.boeing.com>
References: <516c3b6d5f0a466793ba8b2927860787@XCH15-06-08.nw.nos.boeing.com> <61580826-0121-444E-8C15-05AE29D4D6B6@gmail.com> <0a4f1222018c4b6187c4da43fce49cf3@XCH15-06-08.nw.nos.boeing.com> <d459c197a1334283b69cb6925277684c@XCH-ALN-003.cisco.com>
In-Reply-To: <d459c197a1334283b69cb6925277684c@XCH-ALN-003.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [137.136.248.6]
Content-Type: multipart/alternative; boundary="_000_00e2e45c213d4e0cae5927012ebefc8bXCH150608nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/4JjNbLMUxDi0R6rEM4k0FWk2aSs>
Subject: Re: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 18 Sep 2017 18:30:38 -0000

Hi Bernie,

I am not opposing this draft going forward, but it is not the same thing as prefix
delegation. The document is about a router advertising a unique prefix per host,
whereas true prefix delegation is from a delegating router to a requesting router.
This is true even if the “requesting router” is an end system, as in:

https://datatracker.ietf.org/doc/draft-templin-v6ops-pdhost/

I think both of these mechanisms will have their respective use cases. Please
have a look at the above document and share your thoughts here.

Thanks - Fred

From: Bernie Volz (volz) [mailto:volz@cisco.com]
Sent: Friday, September 15, 2017 12:57 PM
To: Templin, Fred L <Fred.L.Templin@boeing.com>om>; Suresh Krishnan <suresh.krishnan@gmail.com>
Cc: dhcwg@ietf.org
Subject: RE: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'

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 [mailto:dhcwg-bounces@ietf.org] On Behalf Of Templin, Fred L
Sent: Friday, August 25, 2017 11:45 AM
To: Suresh Krishnan <suresh.krishnan@gmail.com<mailto:suresh.krishnan@gmail.com>>
Cc: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
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 [mailto:suresh.krishnan@gmail.com]
Sent: Friday, August 25, 2017 6:05 AM
To: Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>>
Cc: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: Re: [dhcwg] 'draft-ietf-v6ops-unique-ipv6-prefix-per-host'

Hi Fred,

On Aug 24, 2017, at 1:42 PM, Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote:

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

https://www.ietf.org/id/draft-ietf-v6ops-unique-ipv6-prefix-per-host-07.txt

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<https://tools.ietf.org/html/rfc7934> [RFC7934] section 8<https://tools.ietf.org/html/rfc7934#section-8>"

I have asked for the motivation for the text (See my ballot at https://datatracker.ietf.org/doc/draft-ietf-v6ops-unique-ipv6-prefix-per-host/ballot/#suresh-krishnan)

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

Is there some specific text you are concerned about?

Thanks
Suresh