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> Wed, 07 February 2018 15:42 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 E11CC12D7F0 for <ipv6@ietfa.amsl.com>; Wed, 7 Feb 2018 07:42:28 -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 UPUrhGACijvo for <ipv6@ietfa.amsl.com>; Wed, 7 Feb 2018 07:42:26 -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 7C60B12704A for <ipv6@ietf.org>; Wed, 7 Feb 2018 07:42:26 -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 w17FgO6X008835; Wed, 7 Feb 2018 08:42:25 -0700
Received: from XCH15-06-11.nw.nos.boeing.com (xch15-06-11.nw.nos.boeing.com [137.136.239.220]) by phx-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id w17FgJpX008779 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Wed, 7 Feb 2018 08:42:19 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-11.nw.nos.boeing.com (2002:8988:efdc::8988:efdc) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 7 Feb 2018 07:42:18 -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; Wed, 7 Feb 2018 07:42:18 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ole Troan <otroan@employees.org>, Alexandre Petrescu <alexandre.petrescu@gmail.com>
CC: 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+XphU4VAEi3RwdAAJZ/9A=
Date: Wed, 07 Feb 2018 15:42:18 +0000
Message-ID: <6e6070c1be0d47c09bef88d8aae84924@XCH15-06-08.nw.nos.boeing.com>
References: <086f874f250e46a5bdf7429b14e3fd87@XCH15-06-08.nw.nos.boeing.com> <18FFCE36-BEDE-464B-89E1-40ABCF381565@employees.org> <04bbf4d5-5eeb-4944-7a71-7606fcf671aa@gmail.com> <3DBDC8F8-DCE0-412E-884A-9AD701A921B6@employees.org>
In-Reply-To: <3DBDC8F8-DCE0-412E-884A-9AD701A921B6@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/rj58cf0agJOPhdEMI_KBGtjZCkU>
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, 07 Feb 2018 15:42:29 -0000

Hi Ole,

> -----Original Message-----
> From: ipv6 [mailto:ipv6-bounces@ietf.org] On Behalf Of Ole Troan
> Sent: Wednesday, February 07, 2018 6:23 AM
> To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
> Cc: 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?
> >
> > Err, yes.
> >
> > Like the new transport protocol QUIC is transported in the old transport protocol UDP, or so I am told.
> 
> And just like QUIC this would be a new protocol.

I think a better analogy might be the long-term bedrock standards looked
at from today's perspective. For example, IPv6 is over 20yrs old and if we
were to redesign it today there would doubtless be any number of things
we would do differently. Same with BGP, OSPF, DNS, etc.

The only critique I have heard about DHCPv6 concerns its aesthetics. There
is nothing broken that I am aware of that needs fixed. The standard has
been out for a long time and the (bis) is in late stages of publication. If we
think there is something wrong, we need to speak up now. But, throwing
it out and doing a redesign just because some people don't like the way
it looks just seems wrong. Beauty is in the eye of the beholder.

Fred

> Ole

v2.23.0 | Report a Bug | By Email