Re: I-D ACTION:draft-jabley-ipv6-rh0-is-evil-00.txt

JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp> Fri, 11 May 2007 12:56 UTC

Return-path: <ipv6-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmUfB-0008PJ-B7; Fri, 11 May 2007 08:56:01 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmUfA-0008Ox-7l for ipv6@ietf.org; Fri, 11 May 2007 08:56:00 -0400
Received: from shuttle.wide.toshiba.co.jp ([2001:200:1b1::35]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmUf8-0005mS-Oc for ipv6@ietf.org; Fri, 11 May 2007 08:56:00 -0400
Received: from jmb.local (t050096.ppp.asahi-net.or.jp [203.189.50.96]) by shuttle.wide.toshiba.co.jp (Postfix) with ESMTP id 6F47F7301E; Fri, 11 May 2007 21:55:57 +0900 (JST)
Date: Fri, 11 May 2007 21:55:06 +0900
Message-ID: <m1646zv7th.wl%jinmei@isl.rdc.toshiba.co.jp>
From: JINMEI Tatuya / 神明達哉 <jinmei@isl.rdc.toshiba.co.jp>
To: Guillaume Valadon / ギョーム バ ラドン <guedou@hongo.wide.ad.jp>
In-Reply-To: <145F856D-2CD6-4964-8256-33D20B5336BD@hongo.wide.ad.jp>
References: <31D43DED-5BEE-4730-8FCB-476FA9EE1A97@eads.net> <46432309.1020902@innovationslab.net> <m2tzukn0xp.wl%gnn@neville-neil.com> <ED9B698C-6892-4FE8-87FD-02372C4DA338@ca.afilias.info> <m1irb0umsu.wl%jinmei@isl.rdc.toshiba.co.jp> <145F856D-2CD6-4964-8256-33D20B5336BD@hongo.wide.ad.jp>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/22.0 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3
Cc: ipv6@ietf.org
Subject: Re: I-D ACTION:draft-jabley-ipv6-rh0-is-evil-00.txt
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "IP Version 6 Working Group \(ipv6\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
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>
Errors-To: ipv6-bounces@ietf.org

At Fri, 11 May 2007 14:16:41 +0200,
Guillaume Valadon <guedou@hongo.wide.ad.jp> wrote:

> > Since there is at least one know popular (but
> > non-attacking) usage of RH0, i.e., probing 'return path' by
> > traceroute, we'll still see non-attacking packets containing RH0.
> 
> Except some custom-made traceroute6 and KAME's implementation, I am  
> not aware of such usage of RH0. What I mean here, is that deprecating  
> RH0 won't harm anyone (except some reasearchers).
> Discovering the 'return path' is a really cool feature, but the  
> discussions during the last weeks proved that RH0 is not the right  
> solution. Its benefit is too small comparing to the problem related  
> to RH0.
> 
> Deprecating RH0 seems to be the only reasonable choice. I do not get  
> why some people want a 'disable by default' solution to this problem.  
> Do we need to explain one more time why RH0 MUST NOT be turned on ?

You missed my point (I didn't advocate not deprecating RH0).  Please
reread my message.

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