Last Call Review of draft-ietf-6man-sids-03
review-ietf-6man-sids-03-opsdir-lc-qu-2023-10-30-00

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

The document is almost ready with a few minor issues that should be considered
by the author before publication.

General comments:
The draft is informational. However it does ask IANA to allocate a block for
SRv6 SIDs, and this will have operational impacts. I'd suggest to expand the
current IANA considerations with more details.

Section 4 should be updated to reflect considerations for the latest compressed
SID definitions as in draft-ietf-spring-srv6-srh-compression.

The following warnings from idnits should be fixed:

  == Unused Reference: 'RFC8200' is defined on line 285, but no explicit
     reference was found in the text

  == Outdated reference: A later version (-09) exists of
     draft-ietf-spring-srv6-srh-compression-04

A few nits that should be fixed:

16    behaviors in some situations.  This document explores the
17    characteristics of SRv6 SIDs and to clarify the relationship of SRv6
18    SIDs to the IPv6 Addressing Architecture.

nit: s/to clarify/clarifies

70    underlying data plane.  In SRv6, SR source nodes initiate packets
71    with a segment identifier in the Destination Address of the IPv6
72    header, and SR segment endpoint nodes process a local segment present
73    the Destination Address of an IPv6 header.

nit: should it be "present in the Destination Address"?

118   3.  SRv6 SIDs and the IPv6 addressing architecture

nit: s/addressing architecture/Addressing Architecture