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

Joe Abley <jabley@ca.afilias.info> Thu, 10 May 2007 21:09 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 1HmFtZ-0004Oj-QW; Thu, 10 May 2007 17:09:53 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HmFtY-0004Oe-H9 for ipv6@ietf.org; Thu, 10 May 2007 17:09:52 -0400
Received: from monster.hopcount.ca ([199.212.90.4]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HmFtX-0000wZ-4f for ipv6@ietf.org; Thu, 10 May 2007 17:09:52 -0400
Received: from [64.235.108.48] (helo=[192.168.182.6]) by monster.hopcount.ca with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.64 (FreeBSD)) (envelope-from <jabley@ca.afilias.info>) id 1HmFwA-0003vs-IB; Thu, 10 May 2007 21:12:35 +0000
In-Reply-To: <m2tzukn0xp.wl%gnn@neville-neil.com>
References: <31D43DED-5BEE-4730-8FCB-476FA9EE1A97@eads.net> <46432309.1020902@innovationslab.net> <m2tzukn0xp.wl%gnn@neville-neil.com>
Mime-Version: 1.0 (Apple Message framework v752.3)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <ED9B698C-6892-4FE8-87FD-02372C4DA338@ca.afilias.info>
Content-Transfer-Encoding: 7bit
From: Joe Abley <jabley@ca.afilias.info>
Date: Thu, 10 May 2007 17:09:31 -0400
To: "George V. Neville-Neil" <gnn@neville-neil.com>
X-Mailer: Apple Mail (2.752.3)
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: Brian Haberman <brian@innovationslab.net>, IETF IPv6 Mailing List <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 10-May-2007, at 11:38, George V. Neville-Neil wrote:

> At Thu, 10 May 2007 09:50:01 -0400,
> Brian Haberman wrote:
>>> The sentence could be modified in :
>>>
>>> "Compliant IPv6 hosts and routers MUST NOT process RH0 in packets
>>>   addressed to them. Those packets MUST be dropped without further
>>>   processing. In particular, the value of the Segments Left field
>>>   MUST not be considered."
>>>
>>
>> This is much clearer and easier to implement.
>
> Though I am not a router vendor I am the person who has to handle this
> on FreeBSD.  I like the above sentence as well.

The above sentences far more closely resemble what I meant to write,  
compared to the text that actually appeared in the draft :-)

I note that KAME's response to this is similar, but it's not clear to  
me that it's precisely identical: a patched KAME implementation  
treats the type 0 routing header as an unknown routing header  
(according to <http://www.kame.net/newsletter/20070502/>). This  
suggests to me that a patched KAME implementation will process a  
datagram containing RH0, but that RH0 header(s) in the datagram will  
not be acted upon. I would welcome corrections to my feeble  
assumptions in this area (I have done no tests, nor read any source  
code to confirm).

A packet containing RH0 presumably is intended not to be processed on  
the system identified by the destination address field; if it was, no  
RH0 would be present. This suggests to me that "MUST drop" is the  
right thing, rather than "process as if RH0 was not there"; in  
addition, if we assume that today any packet with RH0 is likely to be  
malicious, any processing of a packet containing RH0 which has the  
potential to result in backscatter seems like it should properly be  
avoided.


Joe

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