IETF Logo Mail Archive

RE: [dhcwg] static route option for dhcpv6

Martin Stiemerling <Martin.Stiemerling@ccrle.nec.de> Wed, 16 January 2002 12:24 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 HAA05202 for <dhcwg-archive@odin.ietf.org>; Wed, 16 Jan 2002 07:24:48 -0500 (EST)
Received: (from daemon@localhost) by optimus.ietf.org (8.9.1a/8.9.1) id HAA28621 for dhcwg-archive@odin.ietf.org; Wed, 16 Jan 2002 07:24:51 -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 HAA28195; Wed, 16 Jan 2002 07:11:10 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176]) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id HAA28171 for <dhcwg@optimus.ietf.org>; Wed, 16 Jan 2002 07:11:09 -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 HAA04969 for <dhcwg@ietf.org>; Wed, 16 Jan 2002 07:11:05 -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 g0GCB4H50960; Wed, 16 Jan 2002 13:11:04 +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 131F4C052; Wed, 16 Jan 2002 13:10:32 +0100 (CET)
Date: Wed, 16 Jan 2002 13:25:58 +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: <8370000.1011183958@elgar>
In-Reply-To: <001c01c19e7f$e22930b0$2f290a0f@india.hp.com>
References: <001c01c19e7f$e22930b0$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

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

v2.23.0 | Report a Bug | By Email