IETF Logo Mail Archive

Re: IPv6 Type 0 Routing Header issues

Jeroen Massar <jeroen@unfix.org> Fri, 27 April 2007 09:19 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 1HhMbU-000657-5Y; Fri, 27 Apr 2007 05:19:00 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhMbS-0005zu-97 for ipv6@ietf.org; Fri, 27 Apr 2007 05:18:58 -0400
Received: from purgatory.unfix.org ([2001:7b8:20d:0:290:27ff:fe24:c19f]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhMbP-0001kS-LZ for ipv6@ietf.org; Fri, 27 Apr 2007 05:18:58 -0400
Received: from [IPv6:2001:770:100:9e::2] (cl-159.dub-01.ie.sixxs.net [IPv6:2001:770:100:9e::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jeroen) by purgatory.unfix.org (Postfix) with ESMTP id 64B28140C3E6; Fri, 27 Apr 2007 11:18:54 +0200 (CEST)
Message-ID: <4631C005.2000609@spaghetti.zurich.ibm.com>
Date: Fri, 27 Apr 2007 10:19:01 +0100
From: Jeroen Massar <jeroen@unfix.org>
Organization: Unfix
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.10) Gecko/20070221 Thunderbird/1.5.0.10 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: Alun Evans <alun@cisco.com>
References: <20070425082408.GB73965@Space.Net> <ec091ee63209add27eb5fa7ac883049c@localhost> <20070425101001.GH73965@Space.Net> <CA7D9B4A761066448304A6AFC09ABDA9015AD161@XCH-NE-1V2.ne.nos.boeing.com> <017501c78855$84a6f380$8df4da80$@net> <m2ps5qsk1y.wl%gnn@neville-neil.com> <ygvn8xcechny.fsf@ukse-xdm1.cisco.com>
In-Reply-To: <ygvn8xcechny.fsf@ukse-xdm1.cisco.com>
X-Enigmail-Version: 0.94.3.0
OpenPGP: id=333E7C23
X-Virus-Scanned: ClamAV 0.90.1/3168/Fri Apr 27 10:23:30 2007 on purgatory.unfix.org
X-Virus-Status: Clean
X-Spam-Score: -2.8 (--)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Cc: ipv6@ietf.org
Subject: Re: IPv6 Type 0 Routing Header issues
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>
Content-Type: multipart/mixed; boundary="===============1305948131=="
Errors-To: ipv6-bounces@ietf.org

Alun Evans wrote:
> 
> On Fri 27 Apr '07 at 02:06 "George V. Neville-Neil" <gnn@neville-neil.com> wrote:
>> Hi,
>>
>> I would be interested in a list of cases FOR the Type 0 Routing
>> Header.  If there are no good cases for it, it seems to me that
>> removing it is the best thing to do.
> 
> I quite like traceroute for the return path.

This 'problem' can be solved with looking glass websites, not which such
an obvious security problem as RH0.

That said, there should be a well defined system for Looking Glasses.
Please see the proposal I made to the RIPE Database WG to define these:
http://www.ripe.net/ripe/maillists/archives/db-wg/2007/msg00040.html

As there where at least no negative comments, I guess I should make a
more formal proposal soon to solve this, for both IPv4 and IPv6 and in a
standard way (hoping that the other RIR's will follow in providing this
data too, but as some RIR's don't have a real IRR yet that might take time).

Greets,
 Jeroen


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

v2.23.0 | Report a Bug | By Email