Re: Question for IPv6 w.g. on [Re: IPv6 Type 0 Routing Header issues]

Jari Arkko <jari.arkko@piuha.net> Fri, 27 April 2007 17:43 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 1HhUU9-0005iN-B9; Fri, 27 Apr 2007 13:43:57 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HhUU7-0005iB-Oa for ipv6@ietf.org; Fri, 27 Apr 2007 13:43:55 -0400
Received: from p130.piuha.net ([193.234.218.130]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HhUU6-0003qn-AN for ipv6@ietf.org; Fri, 27 Apr 2007 13:43:55 -0400
Received: from p130.piuha.net (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2A0E119868D; Fri, 27 Apr 2007 20:43:53 +0300 (EEST)
Received: from [127.0.0.1] (p130.piuha.net [193.234.218.130]) by p130.piuha.net (Postfix) with ESMTP id D8E0E19867E; Fri, 27 Apr 2007 20:43:52 +0300 (EEST)
Message-ID: <46323659.2090406@piuha.net>
Date: Fri, 27 Apr 2007 20:43:53 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 1.5.0.10 (X11/20070306)
MIME-Version: 1.0
To: bob.hinden@nokia.com
References: <462D4706.4000504@spaghetti.zurich.ibm.com> <462E7AB4.3050807@piuha.net> <m2mz0xp6je.wl%gnn@neville-neil.com> <20070425093402.A30586@mignon.ki.iif.hu> <20070425141336.E95D522875@thrintun.hactrn.net> <462F7005.50700@sri.com> <CE11116E-DF68-481D-AB30-E592C339CEFB@nokia.com>
In-Reply-To: <CE11116E-DF68-481D-AB30-E592C339CEFB@nokia.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: ClamAV using ClamSMTP
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: Brian Carpenter <brc@zurich.ibm.com>, IETF IPv6 Mailing List <ipv6@ietf.org>
Subject: Re: Question for IPv6 w.g. on [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>
Errors-To: ipv6-bounces@ietf.org

>  1) Deprecate all usage of RH0
>  2) Recommend that RH0 support be off by default in hosts and routers
>  3) Recommend that RH0 support be off by default in hosts
>  4) Limit it's usage to one RH0 per IPv6 packet and limit the number
> of addresses in one RH0.

My preference is 2 or alternatively 1. I am currently not
aware of any real use case for Type 0 header (but please
educate me if there is some). It has been known to be
dangerous for a long time and without a use case, it
seems waste of energy to work on 4 or other more
detailed limitations to make it safe. In particular
I would very much like to see us publishing the
RFC deprecating/turning this off soon. Developing the
rules for 4 is possible, but it will take time.

More fundamentally, I believe functions like this
need to be tailored to a specific need before they
can be made restricted enough to be safe and
useful at the same. This is what was done with
Type 2, for instance. If we will see a future need
for something like this, I suspect that it may need
a new Type number anyway.

Alternative 3 is an interesting one. It would actually
align IPv6 with current IPv4 specifications. RFC 1812
calls for a configuration option to turn off source routes,
but requires the default to be that the source routes
are processed. I'm not sure this is right, however...
perhaps we should update corresponding IPv4
specifications at the same time, too.

Jari


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