[IPv6]Gorry Fairhurst's No Objection on draft-ietf-6man-deprecate-router-alert-09: (with COMMENT)
Gorry Fairhurst via Datatracker <noreply@ietf.org> Wed, 16 April 2025 13:31 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from [10.244.8.129] (unknown [104.131.183.230]) by mail2.ietf.org (Postfix) with ESMTP id 4556D1CFED48; Wed, 16 Apr 2025 06:31:10 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Gorry Fairhurst via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.38.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174481027001.1400938.18372676340153549087@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Wed, 16 Apr 2025 06:31:10 -0700
Message-ID-Hash: IEE5VMDKGOLDVJL6OXVPSXYLEZWSHZZQ
X-Message-ID-Hash: IEE5VMDKGOLDVJL6OXVPSXYLEZWSHZZQ
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-deprecate-router-alert@ietf.org, 6man-chairs@ietf.org, ipv6@ietf.org, bob.hinden@gmail.com
X-Mailman-Version: 3.3.9rc6
Reply-To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: [IPv6]Gorry Fairhurst's No Objection on draft-ietf-6man-deprecate-router-alert-09: (with COMMENT)
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/mrK2SyIe11ptCEBaAc0cc2Y8wsg>
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>
Gorry Fairhurst has entered the following ballot position for draft-ietf-6man-deprecate-router-alert-09: 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-deprecate-router-alert/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- The current problems originate from the way in which routers are required to action a Router Alert. I understand this I-D does not change any existing RFC, but seeks to restrict usage in new specifications. Thank you, it is well written. Note: It is a little sad that the I-D does not offer an alternative to identify packets sent by future protocols (such as protocols operating like RSVP would in future be identified in a network that wished to use this type of signalling to nodes on the path), this is presumably part of any future work.
- [IPv6]Gorry Fairhurst's No Objection on draft-iet… Gorry Fairhurst via Datatracker
- [IPv6]Re: Gorry Fairhurst's No Objection on draft… Ron Bonica
- [IPv6]Re: Gorry Fairhurst's No Objection on draft… Gorry Fairhurst