RE: [dhcwg] static route option for dhcpv6

Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de> Fri, 18 January 2002 08:27 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 DAA03845 for <dhcwg-archive@odin.ietf.org>; Fri, 18 Jan 2002 03:27:09 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id DAA00037 for dhcwg-archive@odin.ietf.org; Fri, 18 Jan 2002 03:27:11 -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 DAA29966; Fri, 18 Jan 2002 03:22:09 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id DAA29940 for <dhcwg@optimus.ietf.org>; Fri, 18 Jan 2002 03:22:07 -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 DAA03694 for <dhcwg@ietf.org>; Fri, 18 Jan 2002 03:22:04 -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 g0I8M5H64249; Fri, 18 Jan 2002 09:22:05 +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 8E6BDC05B; Fri, 18 Jan 2002 09:21:36 +0100 (CET)
Date: Fri, 18 Jan 2002 09:21:34 +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: <8590000.1011342094@elgar>
In-Reply-To: <001001c19eb9$f2211fc0$2f290a0f@india.hp.com>
References: <001001c19eb9$f2211fc0$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

Ok, plesse see me prior email.

Martin


--On Mittwoch, Januar 16, 2002 23:46:40 +0530 Vijayabhaskar A K 
<vijayak@india.hp.com> wrote:

> We can use this for forwarding from the network which
> don't have any router advertisement, but has a node
> in the network, attached to the another network and has
> ip-forwarding enabled.
> ~vijay
>
>> -----Original Message-----
>> From: dhcwg-admin@ietf.org [mailto:dhcwg-admin@ietf.org]On Behalf Of
>> Martin Stiemerling
>> Sent: Wednesday, January 16, 2002 5:56 PM
>> To: vijayak@india.hp.com; dhcwg@ietf.org
>> Subject: RE: [dhcwg] static route option for dhcpv6
>>
>>
>> >> In the case of no on-link router, no routes are required!
>> >
>> > In the absence of an on-link IPv6 router, hosts might use configured
>> > tunnels to reach other IPv6 networks. Such routes can be sent in
>> > static-route option.
>> >
>>
>> Yes, this might be useful, but doesn't sound directly like
>>
> static routes,
>> but more than transistioning mechanismen (IPv6 over IPv4
>> tunnel). There are
>> two DSTM options in the draft, but they may not be sufficient
>> for this
>> purpose.
>>
>> Martin
>>
>>
>>
>> _______________________________________________
>> 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 mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg