RE: [dhcwg] static route option for dhcpv6

"Vijayabhaskar A K" <vijayak@india.hp.com> Wed, 16 January 2002 09:04 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA03022 for <dhcwg-archive@odin.ietf.org>; Wed, 16 Jan 2002 04:04:41 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id EAA22975 for dhcwg-archive@odin.ietf.org; Wed, 16 Jan 2002 04:04:44 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22325; Wed, 16 Jan 2002 03:53:18 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA22299 for <dhcwg@optimus.ietf.org>; Wed, 16 Jan 2002 03:53:16 -0500 (EST)
Received: from atlrel6.hp.com (atlrel6.hp.com [156.153.255.205]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02878 for <dhcwg@ietf.org>; Wed, 16 Jan 2002 03:53:13 -0500 (EST)
Received: from hpuxsrv.india.hp.com (hpuxsrv.india.hp.com [15.10.45.132]) by atlrel6.hp.com (Postfix) with ESMTP id CBD3060062C; Wed, 16 Jan 2002 03:52:40 -0500 (EST)
Received: from nt4147 (nt4147.india.hp.com [15.10.41.47]) by hpuxsrv.india.hp.com with SMTP (8.8.6 (PHNE_17135)/8.8.6 SMKit7.02) id OAA16934; Wed, 16 Jan 2002 14:18:23 +0530 (IST)
Reply-To: vijayak@india.hp.com
From: Vijayabhaskar A K <vijayak@india.hp.com>
To: 'Martin Stiemerling' <Martin.Stiemerling@ccrle.nec.de>, dhcwg@ietf.org
Subject: RE: [dhcwg] static route option for dhcpv6
Date: Wed, 16 Jan 2002 14:23:30 +0530
Message-ID: <001a01c19e6b$45f3cf20$2f290a0f@india.hp.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook CWS, Build 9.0.2416 (9.0.2911.0)
In-reply-to: <8550000.1011170070@elgar>
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Importance: Normal
Content-Transfer-Encoding: 7bit
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: <dhcwg.ietf.org>
X-BeenThere: dhcwg@ietf.org
Content-Transfer-Encoding: 7bit

Hi Martin,

RFC for autoconf says that, in the absence of router,
the host must use DHCP. In this case, the static
route option will be very much helpful, for configuring 
the routes. 

Regards
Vijay

> -----Original Message-----
> From: Martin Stiemerling [mailto:Martin.Stiemerling@ccrle.nec.de]
> Sent: Wednesday, January 16, 2002 2:05 PM
> To: vijayak@india.hp.com; dhcwg@ietf.org
> Subject: Re: [dhcwg] static route option for dhcpv6
> 
> 
> Hi Vijay,
> 
> why do you think a static route option is needed at all?
> For the sake of autoconfiguration it is better to keep the routing 
> information in the routers and to provide only a default 
> router to the host 
> (which is done through the router advertisements). In the 
> case that the 
> router is not the best choice for a specific route, the 
> router will  send 
> an ICMP redirect message to the corresponding host, to inform about a 
> better router for this route.
> 
> Regards
> Martin
> 
> 
> --On Dienstag, Januar 15, 2002 20:05:56 +0530 Vijayabhaskar A K 
> <vijayak@india.hp.com> wrote:
> 
> > I have gone through the dhcpv6 22 spec.
> > I felt that, static route option (option 33 in RFC 2132) is missing.
> > which is useful for routing. Can we include this option
> > also in the spec?
> > thanks and regards
> > Vijay
> >
> >
> >
> > _______________________________________________
> > 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