IETF Logo Mail Archive

Re: [dhcwg] DHCPv6 and IPv6ND

"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 14 November 2017 06:20 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87F4F129405 for <dhcwg@ietfa.amsl.com>; Mon, 13 Nov 2017 22:20: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 PJh9dQmS6YpI for <dhcwg@ietfa.amsl.com>; Mon, 13 Nov 2017 22:20:25 -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 32838129417 for <dhcwg@ietf.org>; Mon, 13 Nov 2017 22:20:25 -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 vAE6KNeV006163; Mon, 13 Nov 2017 23:20:23 -0700
Received: from XCH15-06-12.nw.nos.boeing.com (xch15-06-12.nw.nos.boeing.com [137.136.239.221]) by phx-mbsout-02.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id vAE6KJDY006140 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=OK); Mon, 13 Nov 2017 23:20:19 -0700
Received: from XCH15-06-08.nw.nos.boeing.com (2002:8988:eede::8988:eede) by XCH15-06-12.nw.nos.boeing.com (2002:8988:efdd::8988:efdd) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Mon, 13 Nov 2017 22:20:19 -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; Mon, 13 Nov 2017 22:20:19 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Ted Lemon <mellon@fugue.com>
CC: "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] DHCPv6 and IPv6ND
Thread-Index: AdNc+j0Y/64lorm6QoWdIRZ/749NYQAVCNOAAA+Bc2A=
Date: Tue, 14 Nov 2017 06:20:18 +0000
Message-ID: <8d935331012947aa942e8dc2a48d889f@XCH15-06-08.nw.nos.boeing.com>
References: <cf2e41a05fd742a3b576ee317c5392f6@XCH15-06-08.nw.nos.boeing.com> <E94F8CD6-EC4E-4B61-92B6-99FBD1D494A4@fugue.com>
In-Reply-To: <E94F8CD6-EC4E-4B61-92B6-99FBD1D494A4@fugue.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.136.248.6]
Content-Type: multipart/alternative; boundary="_000_8d935331012947aa942e8dc2a48d889fXCH150608nwnosboeingcom_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/2aTsuu3PlS47E_BNdYm6wT1FIuU>
Subject: Re: [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 06:20:26 -0000

Hi Ted,

I don't want to perpetuate the endless debate going on over there, but I
think I have a fair question. How can we get the functionality of IPv6ND
RA and DHCPv6 PD in a single request/response message exchange?

Thanks - Fred

From: Ted Lemon [mailto:mellon@fugue.com]
Sent: Monday, November 13, 2017 9:42 PM
To: Templin, Fred L <Fred.L.Templin@boeing.com>
Cc: dhcwg@ietf.org
Subject: Re: [dhcwg] DHCPv6 and IPv6ND

On Nov 14, 2017, at 11:46 AM, Templin, Fred L <Fred.L.Templin@boeing.com<mailto:Fred.L.Templin@boeing.com>> wrote:
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?

This would be something to bring up in 6man.   Because why not discuss it one more time...?   :]

v2.23.0 | Report a Bug | By Email