IETF Logo Mail Archive

Re: [dhcwg] MTU option for DHCPv6?

"Templin, Fred L" <Fred.L.Templin@boeing.com> Thu, 28 July 2016 15:51 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 7E39512D7CF for <dhcwg@ietfa.amsl.com>; Thu, 28 Jul 2016 08:51:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.921
X-Spam-Level:
X-Spam-Status: No, score=-1.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-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 u8nU5wyvJBKc for <dhcwg@ietfa.amsl.com>; Thu, 28 Jul 2016 08:51:44 -0700 (PDT)
Received: from ewa-mbsout-01.mbs.boeing.net (ewa-mbsout-01.mbs.boeing.net [130.76.20.194]) (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 2803412B005 for <dhcwg@ietf.org>; Thu, 28 Jul 2016 08:51:44 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id u6SFphlB039355; Thu, 28 Jul 2016 08:51:43 -0700
Received: from XCH15-05-06.nw.nos.boeing.com (xch15-05-06.nw.nos.boeing.com [137.137.100.84]) by ewa-mbsout-01.mbs.boeing.net (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id u6SFpfdF039082 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=OK); Thu, 28 Jul 2016 08:51:41 -0700
Received: from XCH15-05-05.nw.nos.boeing.com (2002:8989:6450::8989:6450) by XCH15-05-06.nw.nos.boeing.com (2002:8989:6454::8989:6454) with Microsoft SMTP Server (TLS) id 15.0.1178.4; Thu, 28 Jul 2016 08:51:40 -0700
Received: from XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) by XCH15-05-05.nw.nos.boeing.com ([137.137.100.80]) with mapi id 15.00.1178.000; Thu, 28 Jul 2016 08:51:40 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Simon Hobson <dhcp1@thehobsons.co.uk>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: [dhcwg] MTU option for DHCPv6?
Thread-Index: AdHoQoGGAMbjaqWBR9aaxP1yToT6sgAB2X5AAABnFgAAGFzKMQAPgxAAAAJ0X8AACryIAAAOhobQ//+Ps4CAAHT8YA==
Date: Thu, 28 Jul 2016 15:51:40 +0000
Message-ID: <8c1c7988acb24a4cbca1fc58e7b70bc6@XCH15-05-05.nw.nos.boeing.com>
References: <8c706ad593cc403d9e738c7aafec8360@XCH15-05-05.nw.nos.boeing.com> <5671d2f3bf364bec9b70ab8cbb9cd2a9@XCH-ALN-003.cisco.com> <9db5a86d50314519b4fcc4589717f802@XCH15-05-05.nw.nos.boeing.com> <f98d75f73d224798a406084fdb4cdedc@XCH-ALN-003.cisco.com> <F22A046E-27FA-4EED-9699-70A6B3D49A66@gmx.com> <CAKD1Yr0nw09qss1YMi1CLqjH+iYAaVTCP4xZLsj7eNwWyLUa6w@mail.gmail.com> <1eea216f2f914eddb73eeca7903c48d2@XCH15-05-05.nw.nos.boeing.com> <CAKD1Yr2o0wyLT1YFx-j=FuZecqpo8BbNr6bZbOr0cF1E_d639Q@mail.gmail.com> <00e69d1c8aaa4d44859f88e0793d2679@XCH15-05-05.nw.nos.boeing.com> <B1F3ABB8-E1B8-4D9E-98A0-ACF3E35D88B3@thehobsons.co.uk>
In-Reply-To: <B1F3ABB8-E1B8-4D9E-98A0-ACF3E35D88B3@thehobsons.co.uk>
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: 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/5hKuEfZVeTgtP5PWbaebq0Lr8Rc>
Subject: Re: [dhcwg] MTU option for DHCPv6?
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 28 Jul 2016 15:51:56 -0000

Hi Simon,

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Simon Hobson
> Sent: Thursday, July 28, 2016 8:45 AM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] MTU option for DHCPv6?
> 
> "Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:
> 
> > > What's wrong with adding the MTU option to that RA? That is supported by pretty much all routers and clients today.
> >
> > Being lazy as I am, I just don't want to have to send multiple messages to get
> > all of the configuration information the client needs. If the DHCPv6 Reply
> > contains all configuration information, then there is no need to also perform
> > an RS/RA just to get the MTU value.
> 
> I'm curious. OK I've probably missed a few things, but I was under the impression that clients won't (can't ?) do DHCPv6 unless the RA
> tells them it's a managed network. Also, if clients are self-configuring multiple addresses, doesn't that imply the RAs they are acting on
> have the wrong options set ?

The IPv6-over-(foo) document gets to tell how IPv6 ND and DHCPv6 operate over the
link. At least for the link type I am considering, nodes on the link use DHCPv6 without
waiting to first get an RA with M/O bits.

> And given that (AIUI) DHCPv6 doesn't include any routing information (as that's supposed to come from the RAs), how are the clients
> getting that information ?

Do you mean default router lifetime? For the link type I am considering, the
default router lifetime is derived from the IA_NA/IA_PD lease lifetime.

Thanks - Fred
fred.l.templin@boeing.com

______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email