[secdir] Secdir ietf last call review of draft-ietf-bess-bgp-srv6-args-06

Mališa Vučinić via Datatracker <noreply@ietf.org> Fri, 11 April 2025 18:12 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mališa Vučinić via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <174439517903.891069.3289237247230753856@dt-datatracker-64c5c9b5f9-hz6qg>
Date: Fri, 11 Apr 2025 11:12:59 -0700
Message-ID-Hash: MZTBSFPWGPNSGIDITSM57JGAIKMWBOKM
CC: bess@ietf.org, draft-ietf-bess-bgp-srv6-args.all@ietf.org, last-call@ietf.org
Reply-To: Mališa Vučinić <malisa.vucinic@inria.fr>
Subject: [secdir] Secdir ietf last call review of draft-ietf-bess-bgp-srv6-args-06
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/P7YROxY5DYOlaI_ZgJRj5e3FSvs>

Document: draft-ietf-bess-bgp-srv6-args
Title: SRv6 Argument Signaling for BGP Services
Reviewer: Mališa Vučinić
Review result: Ready

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG. These comments
were written primarily for the benefit of the security area directors. Document
editors and WG chairs should treat these comments just like any other last call
comments.

The document updates RFC 9252 in what concerns signaling and processing of SRv6
SID advertisements. The security considerations section claims no new security
considerations other than those described in RFC 9252. Based on my non-expert
understanding of the document, I agree with this conclusion.

[secdir] Secdir ietf last call review of draft-ie… Mališa Vučinić via Datatracker