Re: [dhcwg] Deafult Router information for DHCPv6

Cristian Cadar <Cristian.Cadar@netlab.nec.de> Fri, 21 May 2004 16:28 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 MAA12657; Fri, 21 May 2004 12:28:55 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRCX5-0003om-82; Fri, 21 May 2004 12:06:03 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1BRCFS-0007Ym-Uy for dhcwg@optimus.ietf.org; Fri, 21 May 2004 11:47:50 -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 LAA10149 for <dhcwg@ietf.org>; Fri, 21 May 2004 11:47:47 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BRCFR-0007Bd-Q8 for dhcwg@ietf.org; Fri, 21 May 2004 11:47:49 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BRCEh-000783-00 for dhcwg@ietf.org; Fri, 21 May 2004 11:47:04 -0400
Received: from tokyo.netlab.nec.de ([195.37.70.2] helo=tokyo.ccrle.nec.de) by ietf-mx with esmtp (Exim 4.12) id 1BRCE0-00072x-00 for dhcwg@ietf.org; Fri, 21 May 2004 11:46:20 -0400
Received: from venus.office (venus.office [10.1.1.11]) by tokyo.ccrle.nec.de (8.12.10/8.12.9) with ESMTP id i4LFjmDW080928 for <dhcwg@ietf.org>; Fri, 21 May 2004 17:45:48 +0200 (CEST)
Received: from cadar.office (cadar.office [10.1.1.118]) by venus.office (Postfix on SuSE Linux eMail Server 3.0) with ESMTP id E7D7F4E7E2 for <dhcwg@ietf.org>; Fri, 21 May 2004 17:45:47 +0200 (CEST)
From: Cristian Cadar <Cristian.Cadar@netlab.nec.de>
Organization: NEC Europe Ltd.
To: dhcwg@ietf.org
Subject: Re: [dhcwg] Deafult Router information for DHCPv6
Date: Fri, 21 May 2004 17:46:27 +0200
User-Agent: KMail/1.5.4
References: <000601c43f28$50c3fdc0$6601a8c0@amer.cisco.com>
In-Reply-To: <000601c43f28$50c3fdc0$6601a8c0@amer.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200405211746.27193.Cristian.Cadar@netlab.nec.de>
X-Scanned-By: MIMEDefang 2.35
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=none 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

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