Re: [dhcwg] static route option for dhcpv6
Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de> Wed, 16 January 2002 08:26 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 DAA02654 for <dhcwg-archive@odin.ietf.org>; Wed, 16 Jan 2002 03:26:08 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA21556 for dhcwg-archive@odin.ietf.org; Wed, 16 Jan 2002 03:26:10 -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 DAA21451; Wed, 16 Jan 2002 03:19:53 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA21424 for <dhcwg@optimus.ietf.org>; Wed, 16 Jan 2002 03:19:52 -0500 (EST)
Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA02565 for <dhcwg@ietf.org>; Wed, 16 Jan 2002 03:19:49 -0500 (EST)
Received: from citadel.mobility.ccrle.nec.de ([192.168.156.1]) by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id g0G8JfH49639; Wed, 16 Jan 2002 09:19:49 +0100 (CET)
Received: from elgar (elgar.heidelberg.ccrle.nec.de [192.168.102.180]) by citadel.mobility.ccrle.nec.de (Postfix on SuSE eMail Server 2.0) with ESMTP id 21F03C052; Wed, 16 Jan 2002 09:19:05 +0100 (CET)
Date: Wed, 16 Jan 2002 09:34:30 +0100
From: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
To: vijayak@india.hp.com, dhcwg@ietf.org
Subject: Re: [dhcwg] static route option for dhcpv6
Message-ID: <8550000.1011170070@elgar>
In-Reply-To: <001301c19dd1$f1acbd80$2f290a0f@india.hp.com>
References: <001301c19dd1$f1acbd80$2f290a0f@india.hp.com>
X-Mailer: Mulberry/2.1.1 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
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 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
- [dhcwg] static route option for dhcpv6 Vijayabhaskar A K
- RE: (ngtrans) RE: [dhcwg] Questions about DHCPv6 … Bernie Volz (EUD)
- RE: (ngtrans) RE: [dhcwg] Questions about DHCPv6 … Jim Bound
- Re: [dhcwg] static route option for dhcpv6 Martin Stiemerling
- RE: [dhcwg] static route option for dhcpv6 Vijayabhaskar A K
- RE: [dhcwg] static route option for dhcpv6 Martin Stiemerling
- RE: [dhcwg] static route option for dhcpv6 Vijayabhaskar A K
- RE: [dhcwg] static route option for dhcpv6 Martin Stiemerling
- RE: [dhcwg] static route option for dhcpv6 Vernon Schryver
- RE: [dhcwg] static route option for dhcpv6 Martin Stiemerling
- RE: [dhcwg] static route option for dhcpv6 Vijayabhaskar A K
- RE: [dhcwg] static route option for dhcpv6 Martin Stiemerling