IETF Logo Mail Archive

RE: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])

"Templin, Fred L" <Fred.L.Templin@boeing.com> Fri, 02 February 2018 15:47 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 A742B12D961 for <ipv6@ietfa.amsl.com>; Fri, 2 Feb 2018 07:47:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 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] 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 5GB8N-Vidmbg for <ipv6@ietfa.amsl.com>; Fri, 2 Feb 2018 07:47:45 -0800 (PST)
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 07BDD126C25 for <ipv6@ietf.org>; Fri, 2 Feb 2018 07:47:45 -0800 (PST)
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 w12FlhaA045954; Fri, 2 Feb 2018 08:47:44 -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 w12FlXYL045760 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Fri, 2 Feb 2018 08:47:33 -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.1347.2; Fri, 2 Feb 2018 07:47:33 -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.1347.000; Fri, 2 Feb 2018 07:47:33 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>
CC: Mikael Abrahamsson <swmike@swm.pp.se>, 6man WG <ipv6@ietf.org>
Subject: RE: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])
Thread-Topic: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])
Thread-Index: AdObk8sYTbsNjEvkTWWp+W+XphU4VAAq9lcAAAC8f6A=
Date: Fri, 02 Feb 2018 15:47:32 +0000
Message-ID: <ce217177be3a4ede8ba1a3324799c17c@XCH15-06-08.nw.nos.boeing.com>
References: <086f874f250e46a5bdf7429b14e3fd87@XCH15-06-08.nw.nos.boeing.com> <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org>
In-Reply-To: <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org>
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/3SC7C6DF8LAsEWwxl9QzsR9D8IY>
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: Fri, 02 Feb 2018 15:47:47 -0000


> -----Original Message-----
> From: Ole Troan [mailto:otroan@employees.org]
> Sent: Friday, February 02, 2018 12:05 AM
> To: Templin, Fred L <Fred.L.Templin@boeing.com>
> Cc: Mikael Abrahamsson <swmike@swm.pp.se>; 6man WG <ipv6@ietf.org>
> Subject: Re: DHCPv6 PD and IPv6 ND unification ((RE: L=0 [was draft-pioxfolks-6man-pio-exclusive-bit-02.txt])
> 
> >
> >> I'd prefer if we took some of DHCPv6 option space, some of the state
> >> machines, and ditched the rest, and explained how this was done using
> >> something else, for instance ND.
> >>
> >> But short of that yes, there should be operational documents (in v6ops
> >> perhaps) that tells implementors how SLAAC and DHCPv6 works together, and
> >> what certain SLAAC messages means for DHCPv6 based resources.
> >
> > Let's start with embedding DHCPv6 PD messages in IPv6 ND RS/RA options
> > and see where that takes us.
> 
> If you were going to design a new configuration protocol in 2018, is that really where you would start?

Because why not start with a mature standard that is already known to work and
is widely deployed? And, can be harmonized with the also mature IPv6 ND standard
to create a single unified service?

Fred

v2.23.0 | Report a Bug | By Email