Benoit Claise's No Objection on draft-ietf-6man-rfc1981bis-07: (with COMMENT)
Benoit Claise <bclaise@cisco.com> Sat, 20 May 2017 11:31 UTC
Return-Path: <bclaise@cisco.com>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 118F0129408; Sat, 20 May 2017 04:31:35 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benoit Claise <bclaise@cisco.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-6man-rfc1981bis@ietf.org, Ole Troan <otroan@employees.org>, 6man-chairs@ietf.org, otroan@employees.org, ipv6@ietf.org
Subject: Benoit Claise's No Objection on draft-ietf-6man-rfc1981bis-07: (with COMMENT)
X-Test-IDTracker: no
X-IETF-IDTracker: 6.51.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <149527989499.30807.4417390399225260349.idtracker@ietfa.amsl.com>
Date: Sat, 20 May 2017 04:31:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/9q8Crn62i-qOafA2at6OOD5hdcI>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Sat, 20 May 2017 11:31:35 -0000
Benoit Claise has entered the following ballot position for draft-ietf-6man-rfc1981bis-07: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-6man-rfc1981bis/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- In this document, I see: IPv6 nodes SHOULD implement Path MTU Discovery in order to discover and take advantage of paths with PMTU greater than the IPv6 minimum link MTU [I-D.ietf-6man-rfc2460bis]. A minimal IPv6 implementation (e.g., in a boot ROM) may choose to omit implementation of Path MTU Discovery. In draft-ietf-6man-rfc2460bis-09: It is strongly recommended that IPv6 nodes implement Path MTU Discovery [RFC1981], in order to discover and take advantage of path MTUs greater than 1280 octets. However, a minimal IPv6 implementation (e.g., in a boot ROM) may simply restrict itself to sending packets no larger than 1280 octets, and omit implementation of Path MTU Discovery. So a SHOULD in one document versus "strongly recommended" in the other. We should reconcile the two texts. Note: may and may are consistent. ICMPv6 PTB => ICMPv6 Packet to Big (PTB)
- Benoit Claise's No Objection on draft-ietf-6man-r… Benoit Claise