RE: [dhcwg] Deafult Router information for DHCPv6

"Bernie Volz" <volz@cisco.com> Fri, 21 May 2004 16:55 UTC

Received: from optimus.ietf.org (www.iesg.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14952; Fri, 21 May 2004 12:55:40 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRDEg-0000J9-Nx; Fri, 21 May 2004 12:51:06 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRD4X-00067l-WC for dhcwg@optimus.ietf.org; Fri, 21 May 2004 12:40:38 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13970 for <dhcwg@ietf.org>; Fri, 21 May 2004 12:40:34 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRD4W-0002vQ-Dy for dhcwg@ietf.org; Fri, 21 May 2004 12:40:36 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRD3n-0002qW-00 for dhcwg@ietf.org; Fri, 21 May 2004 12:39:51 -0400
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx with esmtp (Exim 4.12) id 1BRD2w-0002eu-00 for dhcwg@ietf.org; Fri, 21 May 2004 12:38:58 -0400
Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 21 May 2004 09:42:08 -0700
X-BrightmailFiltered: true
Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id i4LGcN32015243; Fri, 21 May 2004 12:38:25 -0400 (EDT)
Received: from volzw2k (che-vpn-cluster-1-102.cisco.com [10.86.240.102]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AIR35146; Fri, 21 May 2004 12:37:09 -0400 (EDT)
From: "Bernie Volz" <volz@cisco.com>
To: "'Cristian Cadar'" <Cristian.Cadar@netlab.nec.de>, <dhcwg@ietf.org>
Subject: RE: [dhcwg] Deafult Router information for DHCPv6
Date: Fri, 21 May 2004 12:37:09 -0400
Organization: Cisco
Message-ID: <001e01c43f51$dc983540$6601a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.5709
In-Reply-To: <200405211746.27193.Cristian.Cadar@netlab.nec.de>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4927.1200
Importance: Normal
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit

There is no statement in RFC3315 because there doesn't need to be one. See
the IPv6 specifications (such as RFC 2462, 2461) as these cover the IPv6
requirements.

I also don't understand your "100 subnets [perfixes or links?]" situation
... You've got to configure the routers anyway, so they already have all of
the information! (Though they could use DHCPv6 & prefix delegation!!)

- Bernie

> -----Original Message-----
> From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On 
> Behalf Of Cristian Cadar
> Sent: Friday, May 21, 2004 11:46 AM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] Deafult Router information for DHCPv6
> 
> 
> Hi Bernie
> 
> I agree completely with you having only one solution for 
> that, I raised the question since I had not found any 
> statement saying that "When use statefull dhcpv6 MUST use RA 
> for getting the default route information" 
> 
> On the other hand having for instance an IPv6 network with 
> 100 subnets I would not 
> feel like installing and managing the radvd daemon on all of 
> the routers in the network just  to make the default router 
> information available for the clients, instead I'd rather 
> configure it through a statefull dhcpv6 server for all 
> clients of the network. 
> 
> Cristian
> 
> 
> On Friday 21 May 2004 13:39, Bernie Volz wrote:
> > It would be far better to have *ONE* way in which this 
> information is 
> > configured and as RAs already provide it, use that mechanism.
> > 
> > If you can come up with a VERY GOOD motivation for why 
> DHCPv6 needs to 
> > have an option to specify routing information, feel free to 
> write it 
> > up and submit it (personal submission draft) and request 
> for it to be 
> > considered a Working Group item.
> > 
> > - Bernie
> > 
> > > -----Original Message-----
> > > From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org] On
> > > Behalf Of Cristian Cadar
> > > Sent: Friday, May 21, 2004 4:50 AM
> > > To: dhcwg@ietf.org
> > > Subject: [dhcwg] Deafult Router information for DHCPv6
> > > 
> > > 
> > > 
> > > Hi,
> > > 
> > > I know that this issue was already discussed on the list but
> > > I ran into a problem which I would like to clarify here. 
> > > Seemingly the only way for getting the default router 
> > > information is to make use of 
> > > the RA. So when I'm using dhcpv6 and want get the default 
> > > router information 
> > > is it a MUST to use the RA for this pourpose? I could not 
> > > find any statement in any of the RFC/drafts saying that. I 
> > > mean for the time being I cannot see any other possibility. 
> > > There might be scenarios where the use of RA is not desired 
> > > and prefering to have a dhcpv6 option carrying this 
> > > information along. If the use of RA is not a MUST I think we 
> > > need a new option.
> > > 
> > > 
> > > Thanks,
> > > Cristian
> > > 
> > > 
> > > 
> > > 
> > > 
> > > _______________________________________________
> > > dhcwg mailing list
> > > dhcwg@ietf.org
> > > https://www1.ietf.org/mailman/listinfo/dhcwg
> > > 
> > 
> > 
> 
> -- 
> ________________________________________________________
> | Cristian Cadar                   cadar@netlab.nec.de
> | Network Laboratories Heidelberg  NEC Europe Ltd.
> | Kurfuerstenanlage 36             D 69115 Heidelberg
> | Tel. (+49) 6221 90511-21         Fax: (+49) 6221 90511-55
> | URL:  http://www.netlab.nec.de/heidelberg/index.html
> | ________________________________________________________
> 
> 
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg
> 


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg