IETF Logo Mail Archive

[SRv6OPS] Re: [spring] Re: Second WG Last Call: draft-ietf-spring-srv6-security-14 (Ends 2026-06-02)

Tom Hill <tom@ninjabadger.net> Tue, 02 June 2026 17:05 UTC

Return-Path: <tom@ninjabadger.net>
X-Original-To: srv6ops@mail2.ietf.org
Delivered-To: srv6ops@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id AEEBBF96799E; Tue, 2 Jun 2026 10:05:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1780419933; bh=1WyR1QiSQRtUF2k4dBuQ8XBRrUUcqr4O03gSZGXkG8k=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=lL2cDVACmhWI8j09gHAnKNDm0lyRPlifRVe0hql8B946ol5Uryy5WpYIaSGH46qwQ TkzMOm8OUd3SuOo/iStQ7zslUIhAHrX4faCaHP8NfJ1McQ/oHI0DoHriBuiPpEj+Nn 7uSHuvgno9mxwWfNc/rao3AxbHAOxFjXPDBQ4cJs=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nDZjLgxzYzdZ; Tue, 2 Jun 2026 10:05:33 -0700 (PDT)
Received: from a-painless.mh.aa.net.uk (a-painless.mh.aa.net.uk [IPv6:2001:8b0:0:30::51]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 46618F9678B9; Tue, 2 Jun 2026 10:05:03 -0700 (PDT)
Received: from a-webmail.thn.aa.net.uk ([2001:8b0:0:62::22] helo=webmail.aa.net.uk) by painless-a.thn.aa.net.uk with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from <tom@ninjabadger.net>) id 1wUSXa-00000009Vcb-0FF3; Tue, 02 Jun 2026 18:04:34 +0100
Received: from 2a10:d582:2ea:1:b97d:f97f:6fc9:bb06 by webmail.aa.net.uk with HTTP (HTTP/1.1 POST); Tue, 02 Jun 2026 17:04:04 +0000
MIME-Version: 1.0
Date: Tue, 02 Jun 2026 18:04:04 +0100
From: Tom Hill <tom@ninjabadger.net>
To: Nick Buraglio <buraglio@forwardingplane.net>
In-Reply-To: <bf5cc9954330ce3332c8e155c6ac0e15@ninjabadger.net>
References: <177913349668.557208.2581503410373976317@dt-datatracker-7688897f84-l74h4> <3194284ee3b2476985fcbd10925bdb91@huawei.com> <2b006a0d3b94739-00016.Richmail.00003012868091865446@chinamobile.com> <CACMsEX-a6rNg0e7kgKC1AhN7=MfN9yBAN8FO-6kEyqfK54Y6WA@mail.gmail.com> <44e252a15f7997264c59fc3591953448@ninjabadger.net> <bf5cc9954330ce3332c8e155c6ac0e15@ninjabadger.net>
Message-ID: <67b6dcffdfde414823270d1520ec9377@ninjabadger.net>
X-Sender: tom@ninjabadger.net
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: L376VHVQUYD2VJMBFOIMOPOK7CAQ4M52
X-Message-ID-Hash: L376VHVQUYD2VJMBFOIMOPOK7CAQ4M52
X-MailFrom: tom@ninjabadger.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Weiqiang Cheng <chengweiqiang@chinamobile.com>, Alvaro Retana <aretana.ietf@gmail.com>, draft-ietf-spring-sr <draft-ietf-spring-srv6-security@ietf.org>, "spring-chairs@ietf.o" <spring-chairs@ietf.org>, spring@ietf.org, zali@cisco.com, srv6ops@ietf.org, ipv6@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [SRv6OPS] Re: [spring] Re: Second WG Last Call: draft-ietf-spring-srv6-security-14 (Ends 2026-06-02)
List-Id: "SRv6 Operations (SRv6OPS) Working Group List" <srv6ops.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/srv6ops/k1bl1LEBSrTH8mnemhK_6BDM0r0>
List-Archive: <https://mailarchive.ietf.org/arch/browse/srv6ops>
List-Help: <mailto:srv6ops-request@ietf.org?subject=help>
List-Owner: <mailto:srv6ops-owner@ietf.org>
List-Post: <mailto:srv6ops@ietf.org>
List-Subscribe: <mailto:srv6ops-join@ietf.org>
List-Unsubscribe: <mailto:srv6ops-leave@ietf.org>

On 2026-06-02 14:35, Tom Hill wrote:
> NEW TEXT: SRv6 deployments that exceed their trusted domain (per 
> [RFC8402, Section 4.2) including cases where multiple SR instances 
> exist under the same administrative entitty, but are logically or 
> operationally distinct, are out of the scope of this document. Where an 
> attack originates from within a different trusted domain it is 
> considered an external attack in the context of this document.

Found myself a nit already -- "(per [RFC8402, Section 4.2)" should of 
course be "(per [RFC8402], Section 8)".

Tom

v2.46.0 | Report a Bug | By Email | System Status