[IPv6]Jim Guichard's No Objection on draft-ietf-6man-hbh-processing-17: (with COMMENT)
Jim Guichard via Datatracker <noreply@ietf.org> Mon, 27 May 2024 13:00 UTC
Return-Path: <noreply@ietf.org>
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 462B4C18DBA4; Mon, 27 May 2024 06:00:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Jim Guichard via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171681480925.55239.15261304726333719634@ietfa.amsl.com>
Date: Mon, 27 May 2024 06:00:09 -0700
Message-ID-Hash: K7ZVPSEG22ZSNFMB46NQIHY36DK64SPM
X-Message-ID-Hash: K7ZVPSEG22ZSNFMB46NQIHY36DK64SPM
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ipv6.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-6man-hbh-processing@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org
X-Mailman-Version: 3.3.9rc4
Reply-To: Jim Guichard <james.n.guichard@futurewei.com>
Subject: [IPv6]Jim Guichard's No Objection on draft-ietf-6man-hbh-processing-17: (with COMMENT)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/L9bUEwB-fStAZhqdtIPeN1YzMKA>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Owner: <mailto:ipv6-owner@ietf.org>
List-Post: <mailto:ipv6@ietf.org>
List-Subscribe: <mailto:ipv6-join@ietf.org>
List-Unsubscribe: <mailto:ipv6-leave@ietf.org>
Jim Guichard has entered the following ballot position for draft-ietf-6man-hbh-processing-17: 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/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-6man-hbh-processing/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Jim Guichard, RTG AD, comments for draft-ietf-6man-hbh-processing-17. All comments provide indits line numbers from v-17 of the document. 84 An IPv6 packet includes Hop-by-Hop options by including a Hop-by-Hop 85 Option header. The current list of defined Hop-by-Hop options can be 86 found at [IANA-HBH]. The focus for this document is to set the 87 minimum requirements for router processing of Hop-by-Hop options. Jim> The previous paragraph says that the document has the goal of making IPv6 Hop-by-Hop options useful to deploy and use at IPv6 routers and hosts. However, the above does not mention hosts (?). Is this just an omission in the text or is the focus only for routers and therefore the previous paragraph is inaccurate? Please clarify. 111 * control plane: IPv6 routers exchange control information through 112 the control plane. This processes the management and routing 113 information exchanged with other routers. Routers process fields 114 contained in packet headers. However, they do not process 115 information contained in packet payloads. Jim> Are the last two sentences accurate in the context of a control plane definition? While both sentences are true they do not seem relevant to the control plane. 309 When a packet includes one or more Extension Headers, the Next Header 310 field of the IPv6 Header does not identify the transport protocol. Jim> Wouldn’t it be better to say ‘what’ the Next Header field indicates rather than what it ‘does not’. There are lots of things it ‘does not’ indicate.
- [IPv6]Jim Guichard's No Objection on draft-ietf-6… Jim Guichard via Datatracker