RE: [dhcwg] static route option for dhcpv6

Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de> Mon, 21 January 2002 08:37 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 DAA02766 for <dhcwg-archive@odin.ietf.org>; Mon, 21 Jan 2002 03:37:11 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA26069 for dhcwg-archive@odin.ietf.org; Mon, 21 Jan 2002 03:37:14 -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 DAA25489; Mon, 21 Jan 2002 03:28:08 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA25462 for <dhcwg@optimus.ietf.org>; Mon, 21 Jan 2002 03:28:06 -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 DAA02652 for <dhcwg@ietf.org>; Mon, 21 Jan 2002 03:28:02 -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 g0L8RGH81290; Mon, 21 Jan 2002 09:27:17 +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 68309C05B; Mon, 21 Jan 2002 09:26:41 +0100 (CET)
Date: Mon, 21 Jan 2002 09:26:41 +0100
From: Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de>
To: John Schnizlein <jschnizl@cisco.com>, vijayak@india.hp.com
Cc: "'Jim Bound'" <seamus@bit-net.com>, dhcwg@ietf.org
Subject: RE: [dhcwg] static route option for dhcpv6
Message-ID: <11550000.1011601601@elgar>
In-Reply-To: <4.3.2.7.2.20020118151943.01892130@diablo.cisco.com>
References: <8140000.1011342023@elgar> <4.3.2.7.2.20020118151943.01892130@diablo.cisco.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


--On Freitag, Januar 18, 2002 15:22:36 -0500 John Schnizlein 
<jschnizl@cisco.com> wrote:

> At 01:05 PM 1/18/2002, Vijayabhaskar A K wrote:
>
>> Please note that, there are no routers in the networks. That's why
>> i mentioned that node as the one conneceted to two network and having
>> ipv6forwarding enabled, instead of routers. This is for the networks
>> which have not deployed IPv6 routing completely. I think there is no
>> harm in having this option.
>
> If the purpose of the option is to enable situations where hosts
> have ipv6forwarding enabled, but do not act as proper v6 routers,
> then we should not support it. That is just bad practice. (IMHO)

I totaly agree with this.

> The use for tunnelling might be justifiable.

This is, what I have mentioned some emails before. Give the child the 
proper name and it is OK.

Martin


>
> John
>
>
> _______________________________________________
> 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