Re: oversized-header-chains: Receipt of illegal first-fragments

Fernando Gont <fgont@si6networks.com> Thu, 19 July 2012 19:21 UTC

Return-Path: <fgont@si6networks.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4F0121F8737 for <ipv6@ietfa.amsl.com>; Thu, 19 Jul 2012 12:21:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9Pu1lqaz5-sr for <ipv6@ietfa.amsl.com>; Thu, 19 Jul 2012 12:21:41 -0700 (PDT)
Received: from web01.jbserver.net (web01.jbserver.net [IPv6:2a00:d10:2000:e::3]) by ietfa.amsl.com (Postfix) with ESMTP id DA33021F871D for <ipv6@ietf.org>; Thu, 19 Jul 2012 12:21:40 -0700 (PDT)
Received: from 132.66.37.188.rev.vodafone.pt ([188.37.66.132] helo=[10.0.0.196]) by web01.jbserver.net with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <fgont@si6networks.com>) id 1SrwIr-0003RU-HO; Thu, 19 Jul 2012 21:22:30 +0200
Message-ID: <50085DE8.2060906@si6networks.com>
Date: Thu, 19 Jul 2012 20:20:08 +0100
From: Fernando Gont <fgont@si6networks.com>
Organization: SI6 Networks
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: RJ Atkinson <rja.lists@gmail.com>
Subject: Re: oversized-header-chains: Receipt of illegal first-fragments
References: <C8E82E61-8AD2-4471-80AF-00B29EA72A32@gmail.com>
In-Reply-To: <C8E82E61-8AD2-4471-80AF-00B29EA72A32@gmail.com>
X-Enigmail-Version: 1.4.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: ipv6@ietf.org
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 Jul 2012 19:21:47 -0000

Hi, Ran,

As always, thanks so much for your feedback and elaborated comments.
Please find my response in-line...

On 07/19/2012 07:33 PM, RJ Atkinson wrote:
> I think the requirement that a packet that violates the
> proposed oversized-heacer-chain rule be dropped "silently" 
> is too strong and lacks operational flexibility.

FWIW, when I said "silently", I didn't meant to stress it. My point was
about including a requirement to drop such packets, than whether they
should be silently dropped, a counter incremented, etc.


> A device ought to be allowed, but not required, to send 
> an ICMPv6 Parameter Problem message if/when it drops 
> such a packet.
> 
> In some situations, it might be desirable for a device
> to drop the packet AND also generate an ICMPv6 
> "Parameter Problem" message for the packet originator. 

Agreed.



> 1) I'd prefer this draft say that such illegal packets MUST 
>    be dropped, but then also say that the device dropping the 
>    packet MAY send an ICMPv6 Parameter Problem control message 
>    back to the (alleged) sending node.  A brief sentence 
>    suggesting, but not requiring, that implementations make 
>    the sending of the ICMPv6 message configurable also would be 
>    sensible.

Should we make this latter bit (about this being configurable) a MAY, or
would you prefer to have non-RFC2119 language?



> 2) For the situation where an IPv6 packet is dropped for this
>    specific reason, I'd suggest that the "Reason Code" registry 
>    for an ICMPv6 "Type 4 - Parameter Problem" message be updated
>    with a new focused reason code defined.  As a straw man, 
>    I'd propose adding this new entry to that registry, 
>    as part of this proposal:
> 
>    CODE     NAME/DESCRIPTION
>      3      IPv6 Initial Fragment missing upper-layer protocol header
> 
>     Of course, this means an "IANA Considerations" section
>     update for the I-D would be in order.

I find your suggestion acceptable. Can others please weigh in?

Minor note: May be the description for the error code should be along
the lines of "IPv6 First Fragment missing entire IPv6 header chain"?
(I'm just thinking of IPv6 packets with no upper layer protocol, which
would remain legal, but would not have an "upper layer protocol header")



> 3) I'd also suggest a sentence or two clarifying that the
>    ICMPv6 "Parameter Problem" with the new Reason Code
>    is the appropriate message to send -- if the device dropping
>    the packet with oversized-header-chain sends an ICMPv6
>    message.  One would hope this would be obvious, but being
>    very clear is good.

Ok.


> 4) Security Considerations ought to note the importance of
>    deploying Source Address Forgery Prevention filters, in
>    order to reduce the threat of an adversary forging an
>    illegal packet with contains a victim/target's IP address
>    in the Source IPv6 Address field of the illegal packet.
>    [RFC-2827, RFC-3704]

I have no problem with this. However, should we really elaborate on this
topic, since it applies to all ICMPv6 error messages and hence is
probably a topic belonging to e.g. RFC 4443?

Thanks so much,
-- 
Fernando Gont
SI6 Networks
e-mail: fgont@si6networks.com
PGP Fingerprint: 6666 31C6 D484 63B2 8FB1 E3C4 AE25 0D55 1D4E 7492