[secdir] Secdir last call review of draft-ietf-spring-segment-routing-policy-14

Benjamin Schwartz via Datatracker <noreply@ietf.org> Tue, 23 November 2021 17:52 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Benjamin Schwartz via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: draft-ietf-spring-segment-routing-policy.all@ietf.org, last-call@ietf.org, spring@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <163768997021.9950.16814747984245499137@ietfa.amsl.com>
Reply-To: Benjamin Schwartz <bemasc@google.com>
Date: Tue, 23 Nov 2021 09:52:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/6BQ3KP3YOzTmsqU2Bic6eU-n9IQ>
Subject: [secdir] Secdir last call review of draft-ietf-spring-segment-routing-policy-14

Reviewer: Benjamin Schwartz
Review result: Ready

This document is ready with a few minor clarifications.  It does not seem to
require detailed Security Area review.

Section 2.1
"printable ASCII characters": Needs reference to what qualifies as "printable
ASCII".

"color is a 32-bit numerical value": specify unsigned?

Section 2.4
"represented as a 4-byte number": In what byte order?

Section 9 "Protection": It's not clear who this is protecting from what. 
Possible alternative title: "Recovering from segment failure".

[secdir] Secdir last call review of draft-ietf-sp… Benjamin Schwartz via Datatracker
Re: [secdir] Secdir last call review of draft-iet… Ketan Talaulikar