Re: Question regarding router redirect

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Thu, 11 March 2004 01:44 UTC

Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19802 for <ipv6-archive@odin.ietf.org>; Wed, 10 Mar 2004 20:44:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1FFG-0006nE-2S for ipv6-archive@odin.ietf.org; Wed, 10 Mar 2004 20:44:22 -0500
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id i2B1iM5T026111 for ipv6-archive@odin.ietf.org; Wed, 10 Mar 2004 20:44:22 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1FFF-0006n1-Mh for ipv6-web-archive@optimus.ietf.org; Wed, 10 Mar 2004 20:44:21 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19795 for <ipv6-web-archive@ietf.org>; Wed, 10 Mar 2004 20:44:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B1FFD-0007NK-00 for ipv6-web-archive@ietf.org; Wed, 10 Mar 2004 20:44:19 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B1FEC-0007DW-00 for ipv6-web-archive@ietf.org; Wed, 10 Mar 2004 20:43:17 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B1FDZ-00073T-00 for ipv6-web-archive@ietf.org; Wed, 10 Mar 2004 20:42:37 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1FCz-0006PM-I4; Wed, 10 Mar 2004 20:42:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 1B1FCJ-0006Om-CK for ipv6@optimus.ietf.org; Wed, 10 Mar 2004 20:41:19 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA19502 for <ipv6@ietf.org>; Wed, 10 Mar 2004 20:41:17 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B1FCH-0006p7-00 for ipv6@ietf.org; Wed, 10 Mar 2004 20:41:17 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B1FBF-0006bP-00 for ipv6@ietf.org; Wed, 10 Mar 2004 20:40:14 -0500
Received: from shuttle.wide.toshiba.co.jp ([202.249.10.124]) by ietf-mx with esmtp (Exim 4.12) id 1B1FAL-0006Q6-00 for ipv6@ietf.org; Wed, 10 Mar 2004 20:39:17 -0500
Received: from ocean.jinmei.org (unknown [2001:200:0:8002:adaf:3d21:3dbf:c495]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 48FFC15210; Thu, 11 Mar 2004 10:39:11 +0900 (JST)
Date: Thu, 11 Mar 2004 10:39:10 +0900
Message-ID: <y7v7jxs40xt.wl@ocean.jinmei.org>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Mattias Pettersson <mattias.l.pettersson@ericsson.com>
Cc: Bhaskar S <Bhaskar.S@motorola.com>, ipv6@ietf.org
Subject: Re: Question regarding router redirect
In-Reply-To: <404F3190.9010008@ericsson.com>
References: <404E8525.A4F5DEE@motorola.com> <404F3190.9010008@ericsson.com>
User-Agent: Wanderlust/2.10.1 (Watching The Wheels) Emacs/21.3 Mule/5.0 (SAKAKI)
Organization: Research & Development Center, Toshiba Corp., Kawasaki, Japan.
MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen")
Content-Type: text/plain; charset="US-ASCII"
Sender: ipv6-admin@ietf.org
Errors-To: ipv6-admin@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Id: IP Version 6 Working Group (ipv6) <ipv6.ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

>>>>> On Wed, 10 Mar 2004 16:17:36 +0100, 
>>>>> Mattias Pettersson <mattias.l.pettersson@ericsson.com> said:

>> Internet
>> |
>> R1
>> +---+-----------+------+-----+ 
>> |                  |
>> R2                  H1
>> |
>> H2
>> 
>> Let us say Router R1 is the default router for H1. R1 connects
>> H1 to internet (IPv6). Also Router R1, R2 and H1 are all on the
>> same link. H2 is connected to Router R2. If host H1 wants to
>> reach H2 can router R1 redirect it to R2 for this particular
>> route?

> Yes, R1 will tell H1 that R2 is a better next hop.

>> 
>> Or will H1 be able to learn about H2 from R2 router
>> advertisements?

> R2 shouldn't advertise on that (upper) link.

I think R2 actually should.  Otherwise, H1 won't be able to
communicate with H2 when R1 is down.  So, both R1 and R2 should
advertise RAs on the upper link (from R2).  If the "redirect storms"
really matter, we then should use a new feature described in
draft-ietf-ipv6-router-selection-03.txt.

					JINMEI, Tatuya
					Communication Platform Lab.
					Corporate R&D Center, Toshiba Corp.
					jinmei@isl.rdc.toshiba.co.jp

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------