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

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 21 November 2017 15:52 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 2818412955F; Tue, 21 Nov 2017 07:52:26 -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, 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 HW-fkMptjflL; Tue, 21 Nov 2017 07:52:18 -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 50E5C129534; Tue, 21 Nov 2017 07:50:47 -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 vALFojDV013407; Tue, 21 Nov 2017 08:50:45 -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 vALFobZS013336 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Tue, 21 Nov 2017 08:50:38 -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; Tue, 21 Nov 2017 07:50:37 -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; Tue, 21 Nov 2017 07:50:37 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Mark Smith <markzzzsmith@gmail.com>
CC: 6MAN <6man@ietf.org>, v6ops list <v6ops@ietf.org>, "dhcwg@ietf.org" <dhcwg@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+iGtIF1uM57NgAhww6AAASvdJA=
Date: Tue, 21 Nov 2017 15:50:37 +0000
Message-ID: <73d88abadeb643c68670093eee31d31a@XCH15-06-08.nw.nos.boeing.com>
References: <9debb1672e3d4f0d89d672d64e0fe579@XCH15-06-08.nw.nos.boeing.com> <CAO42Z2x8h7RVXP5Hy4vaDXc8kpZBSxJAq=Z7xXTsNN4R8E-Qgw@mail.gmail.com>
In-Reply-To: <CAO42Z2x8h7RVXP5Hy4vaDXc8kpZBSxJAq=Z7xXTsNN4R8E-Qgw@mail.gmail.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.137.12.6]
Content-Type: multipart/alternative; boundary="_000_73d88abadeb643c68670093eee31d31aXCH150608nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/etj87MCdV88M4hGoq3IUVg4tbvs>
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: Tue, 21 Nov 2017 15:52:26 -0000

Hi Mark,

What we are doing here is properly joining the IPv6 ND and DHCPv6 functions into
a single unified autoconfiguration service for all time. Routers that don’t recognize
the DHCPv6 option in RS messages will simply ignore it and process it as a plain
vanilla RFC4861 RS. In that case, all RFC4861 functions still apply, including the
processing of the ‘M’ and ‘O’ bits. It is fully backwards compatible and does
not require any changes to existing routers.

Thanks - Fred

From: Mark Smith [mailto:markzzzsmith@gmail.com]
Sent: Monday, November 20, 2017 9:31 PM
To: Templin, Fred L <Fred.L.Templin@boeing.com>;
Cc: 6MAN <6man@ietf.org>;; v6ops list <v6ops@ietf.org>;; dhcwg@ietf.org
Subject: Re: [v6ops] Combining IPv6 ND and DHCPv6 into a single, unified function

Hi Fred,

I think this fundamentally violates the principle that the network is application agnostic or transparent, allowing it to support any new host residing application without any upgrades to the network. I think the principle of network application transparency should apply to application configuration.

We don't have to upgrade routers to carry new application protocols, we shouldn't have to upgrade routers to support configuring new applications.


"Internet Transparency and Application Configuration"
https://tools.ietf.org/html/draft-smith-v6ops-ce-dhcpv6-transparency-00#section-2


Regards,
Mark.




On 21 Nov. 2017 08:41, "Templin, Fred L" <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote:
Hello,

IPv6 ND and DHCPv6 have traditionally been thought of as independent functions,
with the requirement that the IPv6 ND RS/RA exchange has to happen first so that
the node can examine the M/O bits to determine whether it can use DHCPv6. As
nearly as I can tell, this two round-trip process (IPv6 RS/RA followed by DHCPv6
Solicit/Reply) is the only argument conceivable against DHCPv6 from a functional
standpoint.

The two round-trip process can add significant delay and waste bandwidth especially
on low-end data links like many aviation wireless links. It can also impart unnecessary
messaging overhead on more robust links during periods of congestion.

This document therefore proposes a unification of IPv6 ND and DHCPv6 where
the two functions work together as if they were one. This is accommodated by
a new IPv6 ND option in RS/RA messages called the "DHCPv6 option". By working
together as one function, IPv6 ND and DHCPv6 can supply requesting nodes with
all link-specific autoconfiguration information and any managed address/prefix
delegations in a single round trip message exchange.

I would ask these discussion lists to consider what is it that you really don't
like about DHCPv6. Maybe you think it is ugly. Maybe you don't like the way
the acronym rolls off your tongue when you speak it. Maybe it has an onerous
stigma of being stateful. But, then I would also ask you to consider what a
replacement would look like. Because, I think any suitable replacement
would have to essentially duplicate what DHCPv6 already does.

Comments?

Fred


-----Original Message-----
From: I-D-Announce [mailto:i-d-announce-bounces@ietf.org<mailto:i-d-announce-bounces@ietf.org>] On Behalf Of internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Sent: Monday, November 20, 2017 1:21 PM
To: i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>
Subject: I-D Action: draft-templin-6man-dhcpv6-ndopt-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.


        Title           : The DHCPv6 Option for IPv6 Neighbor Discovery
        Author          : Fred L. Templin
        Filename        : draft-templin-6man-dhcpv6-ndopt-00.txt
        Pages           : 6
        Date            : 2017-11-20

Abstract:
   IPv6 Neighbor Discovery (IPv6ND) specifies a control message set for
   nodes to discover neighbors, routers, prefixes and other services on
   the link.  It also supports a manner of StateLess Address
   AutoConfiguration (SLAAC).  The Dynamic Host Configuration Protocol
   for IPv6 (DHCPv6) specifies a service for the stateful delegation of
   addresses and prefixes.

   Currently, at least two round-trip message exchanges are necessary in
   order to perform the IPv6ND router discovery and DHCPv6 address/
   prefix delegation functions.  This document presents a protocol for
   combining these two round trips into a single round trip by joining
   the two services into a single unified service.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-templin-6man-dhcpv6-ndopt/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-templin-6man-dhcpv6-ndopt-00
https://datatracker.ietf.org/doc/html/draft-templin-6man-dhcpv6-ndopt-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<http://tools.ietf.org>.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org<mailto:I-D-Announce@ietf.org>
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org>
https://www.ietf.org/mailman/listinfo/v6ops