RE: [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 22 November 2017 17:31 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43B31129494; Wed, 22 Nov 2017 09:31:42 -0800 (PST)
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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=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 5cly663AL68p; Wed, 22 Nov 2017 09:31:41 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net [130.76.184.179]) (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 179D5129492; Wed, 22 Nov 2017 09:31:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id vAMHVe5r048212; Wed, 22 Nov 2017 10:31:40 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (xch15-06-08.nw.nos.boeing.com [137.136.238.222]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vAMHVUSJ047750 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 22 Nov 2017 10:31:30 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 22 Nov 2017 09:31:29 -0800
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; Wed, 22 Nov 2017 09:31:29 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "dhcwg@ietf.org" <dhcwg@ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>, "6man@ietf.org" <6man@ietf.org>
Subject: RE: [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function
Thread-Topic: [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function
Thread-Index: AdNiReoj4OrwrQYST+iGtIF1uM57NgAkcdkAADO+44AAE7ZgAAAPkJMw
Date: Wed, 22 Nov 2017 17:31:29 +0000
Message-ID: <53abe623d4bd418c9799b9e8d94e8006@XCH15-06-08.nw.nos.boeing.com>
References: <9debb1672e3d4f0d89d672d64e0fe579@XCH15-06-08.nw.nos.boeing.com> <CAKD1Yr1+a+Bg3N=pX5_X2vhvkf50hY7N_Ay=aQQyq5ogsEWWMw@mail.gmail.com> <4e01cd6cc5234daca2f7be55b8cc28b0@XCH15-06-08.nw.nos.boeing.com> <27327.1511369630@obiwan.sandelman.ca>
In-Reply-To: <27327.1511369630@obiwan.sandelman.ca>
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: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/tp-NKNKQVKKDMSOpSHLiSoMwEvA>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Nov 2017 17:31:42 -0000

Hi Michael,

This isn't an experiment; this is a unified stateless/stateful autoconfiguration
service for IPv6 for all time.

We all want prefix delegation, and that will necessarily be a stateful function.
And, if the prefix delegation service would not be DHCPv6 PD then we would
need to develop a new PD architecture. Either way, though, it should be
implemented as a unified function with IPv6ND.

Thanks - Fred

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Michael Richardson
> Sent: Wednesday, November 22, 2017 8:54 AM
> To: dhcwg@ietf.org; v6ops@ietf.org; 6man@ietf.org
> Subject: Re: [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function
> 
> 
> My understanding is that Fred Templin essentially wants to carry DHCP
> (configuration) options in ND/RA.
> 
> I think that they are most often stateless (i.e. not addresses at all or
> other resources).
> 
> I've heard the IPv4 PPP folks lament that they should have just had an IPCP
> option to carry DHCPv4 options, and indeed that's why we have almost no IP6CP
> options, as it's all done by ND and DHCPv6.
> 
> {Having implemented a DHCPv6 server just to serve PPP links, it really feels
> dumb.  Yes, the management is all centralized, but it's centralized via
> RADIUS, not via DHCP relays. }
> 
> So I suggest that Fred should go ahead with his document as Experimental,
> with our blessing, and an obligation to report on how well it works in
> his situation.   Given the timescales that I think his industry works at, he
> might need more time than an average Experimental code allocation.
> He would have to deal how/if/when all experimental systems would be withdrawn
> should the experiment be unsuccessful, I think.
> 
> I guess he could use ND codes 253/254, but I think an assignment would not
> kill here.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>;, Sandelman Software Works
>  -= IPv6 IoT consulting =-
> 
>