IETF Logo Mail Archive

Re: IPv6 Type 0 Routing Header issues

Remi Denis-Courmont <rdenis@simphalempin.com> Wed, 25 April 2007 08:46 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 1Hgd9O-00019P-N3; Wed, 25 Apr 2007 04:46:58 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Hgd9N-00015X-48 for ipv6@ietf.org; Wed, 25 Apr 2007 04:46:57 -0400
Received: from poy.chewa.net ([2002:c2f2:7249::1]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Hgd9L-00067X-PW for ipv6@ietf.org; Wed, 25 Apr 2007 04:46:57 -0400
Received: by poy.chewa.net (Postfix, from userid 33) id 4C001967E2; Wed, 25 Apr 2007 10:46:54 +0200 (CEST)
To: Gert Doering <gert@space.net>
MIME-Version: 1.0
Date: Wed, 25 Apr 2007 10:46:54 +0200
From: Remi Denis-Courmont <rdenis@simphalempin.com>
Organization: Remlab.net
In-Reply-To: <20070425082408.GB73965@Space.Net>
References: <20070425082408.GB73965@Space.Net>
Message-ID: <ec091ee63209add27eb5fa7ac883049c@localhost>
X-Sender: rdenis@simphalempin.com
User-Agent: RoundCube Webmail/0.1b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Spam-Score: -2.8 (--)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc: ipv6@ietf.org, Mohacsi Janos <mohacsi@niif.hu>, IPv6 Ops list <ipv6-ops@lists.cluenet.de>, v6ops@ops.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>
Errors-To: ipv6-bounces@ietf.org

On Wed, 25 Apr 2007 10:24:08 +0200, Gert Doering <gert@space.net> wrote:
> Well, one could argue that the standard isn't very well-written then - a
> machine that is a *host* should NEVER forward packets, period.

That's a BSD bug, not a standard bug.

The IPv6 specification says host must process RT0. It does not say they must
forward packets as if they were routers on the sole basis of RT0 presence.

By the current spec (as far as I understand), if a host receives a RT0, it
must process it. Then it must apply the same rules to the "new" packet
destination as it would do to any packet it receives; in particular, if the
packet cannot be delivered locally, it is dropped. You do the exact same
thing when you receive a packet from link-layer while you are not the
destination at network-layer.

Whether RT0 is evil and it should be deprecated so routers do not handle it
anymore is the real problem.

--
Rémi Denis-Courmont
http://www.remlab.net/


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