Hi WG,
I read this version and support the publication of this document since it
provides useful extensions for SRv6.
While I am not an expert for DHCP, I just have two editorial suggestions for
authors' consideration.
In section 1 Introduction:
OLD: A Segment Routing Policy (SR Policy) [RFC8402]
NEW: A Segment Routing Policy (SR Policy) [RFC9256]
Section 4 Title:
OLD: 4. DHCPv6 extension
NEW: 4. DHCPv6 Extensions
Best Regards,
Quan
<Subject: WG Last Call: draft-ietf-spring-dhc-distribute-srv6-locator-dhcp-09
<(Ends 2025-09-11)
<This message starts a 2-week WG Last Call for this document.
<Abstract:
< In an SRv6 network, each SRv6 Segment Endpoint Node must be assigned
< an SRv6 locator, and segment IDs are generated within the address
<space of this SRv6 locator. This document describes a method for
< assigning SRv6 locators to SRv6 Segment Endpoint Nodes through
<DHCPv6.
<File can be retrieved
from:https://datatracker.ietf.org/doc/draft-ietf-spring-dhc-distribute-srv6-locator-dhcp/Please
review and indicate your support or <objection to proceed with the
<publication of this document by replying to this email keepingspr...@ietf.org
in copy. Objections should be motivated and suggestions to
<resolve them are highly appreciated.
<Authors, and WG participants in general, are reminded again of the
<Intellectual Property Rights (IPR) disclosure obligations described in BCP 79
<[1]. Appropriate IPR disclosures required for full conformance with the
<provisions of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of
<any. Sanctions available for application to violators of IETF IPR Policy can
<be found at [3].
Thank you.
[1] https://datatracker.ietf.org/doc/bcp78/[2]
https://datatracker.ietf.org/doc/bcp79/[3]
https://datatracker.ietf.org/doc/rfc6701/
_______________________________________________
spring mailing list -- spring@ietf.org
To unsubscribe send an email to spring-le...@ietf.org
