Re: [v6ops] RFC 4890 ICMPv6 Filtering Recommendations to BCP?

Sander Steffann <sander@steffann.nl> Thu, 03 January 2013 16:26 UTC

Return-Path: <sander@steffann.nl>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C6B821F8610 for <v6ops@ietfa.amsl.com>; Thu, 3 Jan 2013 08:26:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.976
X-Spam-Level:
X-Spam-Status: No, score=0.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_EQ_IP_ADDR=1.119, RCVD_IN_PBL=0.905, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ztP5kmhPHfD4 for <v6ops@ietfa.amsl.com>; Thu, 3 Jan 2013 08:26:20 -0800 (PST)
Received: from mail.sintact.nl (mail.sintact.nl [IPv6:2001:4038:0:16::7]) by ietfa.amsl.com (Postfix) with ESMTP id 8040621F872D for <v6ops@ietf.org>; Thu, 3 Jan 2013 08:26:20 -0800 (PST)
Received: from [172.20.10.2] (unknown [62.140.137.93]) by mail.sintact.nl (Postfix) with ESMTP id ECDD7200A; Thu, 3 Jan 2013 17:26:18 +0100 (CET)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Sander Steffann <sander@steffann.nl>
In-Reply-To: <E1829B60731D1740BB7A0626B4FAF0A65E0EED37DE@XCH-NW-01V.nw.nos.boeing.com>
Date: Thu, 03 Jan 2013 17:26:19 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <9FA4069A-FE71-4391-879B-BC996E7092BF@steffann.nl>
References: <8C48B86A895913448548E6D15DA7553B72A35D@xmb-rcd-x09.cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65E0EED37DE@XCH-NW-01V.nw.nos.boeing.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
X-Mailer: Apple Mail (2.1499)
Cc: "v6ops@ietf.org" <v6ops@ietf.org>
Subject: Re: [v6ops] RFC 4890 ICMPv6 Filtering Recommendations to BCP?
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Jan 2013 16:26:21 -0000

Hi,

> Something that has always bothered me about RFC4890 is the
> following text of Section A.2:
> 
>   "If a network chooses to generate packets that are no larger than the
>   Guaranteed Minimum MTU (1280 octets) and the site's links to the
>   wider Internet have corresponding MTUs, Packet Too Big messages
>   should not be expected at the firewall and could be dropped if they
>   arrive."
> 
> This seems to preclude PTB messages reporting a size smaller
> than 1280, which are necessary to ensure proper operation of
> IPv6, e.g., per the final paragraph of RFC2460, Section 5.
> 
> My recommendation is that the RFC4890, Section A.2 text be dropped
> when preparing the (bis) version for publication as a BCP.

+1

This advise will cause problems with (atomic) fragment requirement in RFC2460 section 5, so it should not be in a BCP.
Sander