[IPv6]Roman Danyliw's No Objection on draft-ietf-6man-comp-rtg-hdr-08: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 29 May 2024 20:16 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 3E16FC14F5EA; Wed, 29 May 2024 13:16:13 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw 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: <171701377324.25767.13095299411095254728@ietfa.amsl.com>
Date: Wed, 29 May 2024 13:16:13 -0700
Message-ID-Hash: VYUORULIFOBAVOOZLNAIKDIVOMMCNOZF
X-Message-ID-Hash: VYUORULIFOBAVOOZLNAIKDIVOMMCNOZF
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-comp-rtg-hdr@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, bob.hinden@gmail.com
X-Mailman-Version: 3.3.9rc4
Reply-To: Roman Danyliw <rdd@cert.org>
Subject: [IPv6]Roman Danyliw's No Objection on draft-ietf-6man-comp-rtg-hdr-08: (with COMMENT)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mYJzj0UUYQfcAb_7TADMq1ynlwQ>
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>
Roman Danyliw has entered the following ballot position for draft-ietf-6man-comp-rtg-hdr-08: 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-comp-rtg-hdr/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Elwyn Davies for the GENART review. ** Section 12. The abstract said “another purpose is to demonstrate that the security considerations, described in this document, can be addressed with access control lists.” Based on the text in this section it isn’t clear what the unknown (requiring an experiment) is around implementing these Security Considerations. ** Section 14. The nature of the experiment isn’t clear in the following cases: -- At the highest level, how do we know the experiment was a success? -- Per “Effort required to secure”, what is the units of this effort? -- Per “Effectiveness of risk mitigation with ACLs”, how is one expected to answer this question? -- Per “Effectiveness and sufficiency of OAM mechanism - Did PING work? - Did TRACEROUTE work? - Did Wireshark work? - Did TCPDUMP work?” In what way is support in these tools an open-ended question requiring experimentation on a production network? Can’t one check functionality/support per a given version number of these tools?
- [IPv6]Roman Danyliw's No Objection on draft-ietf-… Roman Danyliw via Datatracker