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

David Malone <dwmalone@maths.tcd.ie> Fri, 11 May 2007 21:18 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 1HmcVU-0007uJ-OR; Fri, 11 May 2007 17:18:32 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmcVS-0007u3-IZ for ipv6@ietf.org; Fri, 11 May 2007 17:18:30 -0400
Received: from salmon.maths.tcd.ie ([2001:770:10:300::86e2:510b]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1HmcVR-00055N-26 for ipv6@ietf.org; Fri, 11 May 2007 17:18:30 -0400
Received: from walton.maths.tcd.ie ([134.226.81.10] helo=walton.maths.tcd.ie) by salmon.maths.tcd.ie with SMTP id <aa31045@salmon>; 11 May 2007 22:18:27 +0100 (BST)
Date: Fri, 11 May 2007 22:18:27 +0100
From: David Malone <dwmalone@maths.tcd.ie>
To: Guillaume Valadon / ???????????? ???????????? <guedou@hongo.wide.ad.jp>
Message-ID: <20070511211827.GA28615@walton.maths.tcd.ie>
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>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <145F856D-2CD6-4964-8256-33D20B5336BD@hongo.wide.ad.jp>
User-Agent: Mutt/1.5.6i
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
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

On Fri, May 11, 2007 at 02:16:41PM +0200, Guillaume Valadon / ???????????? ???????????? wrote:
> 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.

IMHO, the existance of so many traceroute looking glasses is
significant evidence that operators (not just researchers) need
intermediate point traceroute. It is used by people to find routes
external to their network and to explore routes within their networks
(say big datacentre operators or big corporate networks). This
feature should be implementable in traceroute (where it seems to
belong) and not as a web/telnet application, which requires you to
have a cooperating server in each network you might want to trace
through.

This is why I think someone might want to turn RH0 back on again
(to get this feature on their own network). They can filter at the
border to prevent external abuse, and use the usual procedures to
deal with internal abuse. This is also the sort of feature that
ordinary users are not likely to use, which is why I think it is
reasonable to have it off by default.

I understand Itojun's suggestion that we can have a RH7 that will
allow useful source routing without the danger associated with RH0.
This sounds like a very good idea.  However, realistically, I suspect
that even if the RH7 standard was fully specified tomorrow, we would
be waiting more than two years to have it implemented in production
versions of software that operators are likely to be using.

	David.

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