[IPv6]draft-ietf-6man-sidlist-clarification-02 ietf last call Secdir review
Peter Yee via Datatracker <noreply@ietf.org> Mon, 27 April 2026 10:49 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: ipv6@ietf.org
Delivered-To: ipv6@mail2.ietf.org
Received: from [10.244.6.0] (unknown [4.156.85.76]) by mail2.ietf.org (Postfix) with ESMTP id 0A1BBE3D73A2; Mon, 27 Apr 2026 03:49:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777286958; bh=aLydu+cEtrgzTxyY8Ahyi9vGBhxQxJ5W+xD49hdSWyg=; h=From:To:Cc:Subject:Reply-To:Date; b=pPvtpaUu3nenH0yHuleoDTOeqvsPjG33n9tAZO9Adi18WQ+0B57JCvy+fTJ/zNDZp O6Vc5X5xHHcl4mikbcg8z4BWptUyQniDBiv+g5df30qOpX2n68AmzH18i2Ly9sBx+F bWydRx0V+RtBCkqs0/wIubR+2a6mSTAsvZrnsLYE=
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Peter Yee via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 12.62.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <177728695792.1984793.13560343093683153239@dt-datatracker-b45949c58-5szpr>
Date: Mon, 27 Apr 2026 03:49:17 -0700
Message-ID-Hash: EU5QCREJD4HYJGH6FQUADD7MLETY3KTA
X-Message-ID-Hash: EU5QCREJD4HYJGH6FQUADD7MLETY3KTA
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-sidlist-clarification.all@ietf.org, ipv6@ietf.org, last-call@ietf.org
X-Mailman-Version: 3.3.9rc6
Reply-To: Peter Yee <peter@akayla.com>
Subject: [IPv6]draft-ietf-6man-sidlist-clarification-02 ietf last call Secdir review
List-Id: "IPv6 Maintenance Working Group (6man)" <ipv6.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/d-IJdeUEKthfSQSjQh3gWGY4Ct0>
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>
Document: draft-ietf-6man-sidlist-clarification Title: Clarifying SRv6 SID List Processing Reviewer: Peter Yee Review result: Has Nits Document: draft-ietf-6man-sidlist-clarification Title: Clarifying SRv6 SID List Processing Reviewer: Peter Yee Review result: Has Nits This draft clarifies that Segment Identifier (SID) entries in the Segment Routing Header are not necessarily routable IPv6 addresses but may require mapping to routable and usable IPv6 addresses. From a security perspective, I don’t have great concerns, although the mapping process (not specified in this draft) could potentially cause packets to be misrouted if it makes an incorrect mapping. The document has a few piddling nits that could be fixed. Major concerns: None Minor concerns: None Nits: Page 2, section 1, 2nd paragraph: append a comma after “[RFC8754]”. Page 3, 2nd paragraph, 2nd sentence: delete the comma after “addresses)”. Page 4, paragraph after figure: change “128 bit” to “128-bit”. Page 5, figure: in both cases, change “addresses to address”. Each entry is presumably mapped to a single address. Page 5, 2nd paragraph: change “128 bit” to “128-bit”.
- [IPv6]draft-ietf-6man-sidlist-clarification-02 ie… Peter Yee via Datatracker
- [IPv6]Re: draft-ietf-6man-sidlist-clarification-0… Adrian Farrel
- [IPv6]Re: draft-ietf-6man-sidlist-clarification-0… peter