[dhcwg] DHCPv6 and IPv6ND

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 14 November 2017 03:46 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 7832A126C2F for <dhcwg@ietfa.amsl.com>; Mon, 13 Nov 2017 19:46:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id z37yt9bA2UXU for <dhcwg@ietfa.amsl.com>; Mon, 13 Nov 2017 19:46:39 -0800 (PST)
Received: from phx-mbsout-02.mbs.boeing.net (phx-mbsout-02.mbs.boeing.net []) (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 3A5011242EA for <dhcwg@ietf.org>; Mon, 13 Nov 2017 19:46:38 -0800 (PST)
Received: from localhost (localhost []) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id vAE3kbPU021523; Mon, 13 Nov 2017 20:46:37 -0700
Received: from XCH15-06-09.nw.nos.boeing.com (xch15-06-09.nw.nos.boeing.com []) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vAE3kTlh021498 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK) for <dhcwg@ietf.org>; Mon, 13 Nov 2017 20:46:29 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-09.nw.nos.boeing.com (2002:8988:efac::8988:efac) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 13 Nov 2017 19:46:28 -0800
Received: from XCH15-06-08.nw.nos.boeing.com ([]) by XCH15-06-08.nw.nos.boeing.com ([]) with mapi id 15.00.1320.000; Mon, 13 Nov 2017 19:46:28 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: DHCPv6 and IPv6ND
Thread-Index: AdNc+j0Y/64lorm6QoWdIRZ/749NYQ==
Date: Tue, 14 Nov 2017 03:46:28 +0000
Message-ID: <cf2e41a05fd742a3b576ee317c5392f6@XCH15-06-08.nw.nos.boeing.com>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
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/dhcwg/hxH9X9wn-lDxiQ8jFYlvXCVgJG8>
Subject: [dhcwg] DHCPv6 and IPv6ND
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: Tue, 14 Nov 2017 03:46:40 -0000


I have been using DHCPv6 PD for a long time to get delegated prefixes on
devices like Android handsets. But, I am troubled by the fact that I need to
also do RS/RA in order to get default router lifetimes and other information
specific to the link in addition to the DHCPv6 Solicit/Reply.

If my DHCPv6 server will always be on the same router that will serve as my
default router, is there any way to get DHCPv6 to also provide the information
normally conveyed in RAs? For example, define a new DHCPv6 option that
embeds an IPv6 ND RA?

Thanks - Fred