Re: TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04

Joe Touch <> Thu, 16 February 2017 16:47 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 4FC34129DA4; Thu, 16 Feb 2017 08:47:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id EMXgh15Qx4Kd; Thu, 16 Feb 2017 08:47:04 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 56A3D129D9B; Thu, 16 Feb 2017 08:47:04 -0800 (PST)
Received: from [] ( []) (authenticated bits=0) by (8.13.8/8.13.8) with ESMTP id v1GGklDY019234 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 16 Feb 2017 08:46:49 -0800 (PST)
Subject: Re: TSV-ART Telechat review of draft-ietf-6man-rfc1981bis-04
To: "" <>, "" <>
References: <>
From: Joe Touch <>
Message-ID: <>
Date: Thu, 16 Feb 2017 08:46:46 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: multipart/alternative; boundary="------------177C5A21A21EB33F6008D7DE"
X-ISI-4-43-8-MailScanner: Found to be clean
Archived-At: <>
Cc: 6man <>
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 Feb 2017 16:47:06 -0000

Adding the missing boilerplate:

I've reviewed this document as part of the transport area directorate's
ongoing effort to review key IETF documents. These comments were written
primarily for the transport area directors, but are copied to the
document's authors for their information and to allow them to address
any issues raised. When done at the time of IETF Last Call, the authors
should consider this review together with any other last-call comments
they receive. Please always CC if you reply to or
forward this review.

On 2/15/2017 1:51 PM, Joe Touch wrote:
> Document: draft-ietf-6man-rfc1981bis-04
> Reviewer: Joe Touch
> Review Date: February 15, 2017
> IETF LC End Date: March 3, 2017
> IESG Telechat date: February 28, 2017
> Review result: significant issues
> NOTE: some of this review is informed by tracking some of the issues raised by others on the IETF list, notably Gorry Fairhurst.
> Major issues:
> 1) the current text is insufficiently realistic about the (in)ability of this mechanism to operate in current networks, regardless of the support for generating ICMPs at routers or PMTUD support at endpoints, due to ICMP filtering for security reasons. [this comment is already being addressed by consensus text]
> 2) the current text is insufficiently clear on on the difference between the path MTU, which determines the largest supported IPv6 fragment, vs. the effective MTU to receive (EMTU_R), which determines the largest IP packet that can transit between the source and destination. The document should be more explicit throughput about its goal being to manage or avoid IPv6 source fragmentation rather than about source to destination packet maximums, and in specific in clearly referring to maximum fragments or atomic packets rather than maximum packets.
> E.g.: see the following text, which is incorrect in its current form:
>    Nodes not implementing Path MTU Discovery use the IPv6 minimum link
>    MTU defined in [I-D.ietf-6man-rfc2460bis
> <>] as the maximum packet size.
> The value used by either Path MTU Discovery or its default represents the path MTU, which is the largest IPv6 *fragment* (or atomic packet, see RFC6864) that can be supported on the path between the endpoints. The maximum IP packet size is limited by the effective MTU to receive (EMTU_R) [RFC1122], which is at least 1500 bytes for IPv6 and not necessarily related to the link MTUs. The text should also clearly indicate that there is no ICMP mechanism for determining larger EMTU_R support.
> E.g., the following text is also incorrect in its current form:
>    The value sent in the TCP MSS option is independent of the PMTU.
>    This MSS option value is used by the other end of the connection,
>    which may be using an unrelated PMTU value. 
> The first sentence is correct because TCP MSS is related to EMTU_R (and needs to account for headers, as per RFC6691), and EMTU_R is not directly related to the PMTU (except that it would never be smaller than the PMTU). The MSS option is calculated from EMTU_R, not PMTU.
> In addition, it should be noted that ICMPv6 PTB messages are NOT sent when source fragmentation is enabled.
> 3. need verification of current support for some features, esp. regarding TCP and NFS interactions
> See Gorry's note of 2/14/17
> 4. the concept of a single path MTU value between two IP addresses does not account for multipath routing, e.g., ECMP (as currently deployed, noted in RFC7690, which should be cited) or BANANA (and its solutions in development) See Fred Templin's posts on this on 2/15/17
> Minor issues:
> - some of the updates and/or current text could be updated to reflect current terminology or practice. See Gorry Fairhursts's post of 2/14/17
> - fragmentation, while considered harmful and costly, is absolutely necessary to support tunnels even in the presence of PMTUD. The text on this issue should reflect this reality.
> - the requirement that transports be notified of PTB messages might usefully cite the corresponding IPv4, TCP, and UDP sections of RFC1122
> - section 5.4 should cite and include context from RFC6691, especially including a discussion of the impact of variable IP EHs on the interaction between TCP MSS and ICMP PTB
> --