rfc9603v3.txt | rfc9603.txt | |||
---|---|---|---|---|
skipping to change at line 827 ¶ | skipping to change at line 827 ¶ | |||
Mechanisms defined in [RFC5440], [RFC8231], and [RFC8664] also apply | Mechanisms defined in [RFC5440], [RFC8231], and [RFC8664] also apply | |||
to PCEP extensions defined in this document. | to PCEP extensions defined in this document. | |||
8. IANA Considerations | 8. IANA Considerations | |||
8.1. PCEP ERO and RRO Subobjects | 8.1. PCEP ERO and RRO Subobjects | |||
This document defines a new subobject type for the PCEP Explicit | This document defines a new subobject type for the PCEP Explicit | |||
Route Object (ERO) and a new subobject type for the PCEP Reported | Route Object (ERO) and a new subobject type for the PCEP Reported | |||
Route Object (RRO). These have been registered in the “Resource | Route Object (RRO). These have been registered in the "Resource | |||
Reservation Protocol (RSVP) Parameters” registry group as shown | Reservation Protocol (RSVP) Parameters" registry group as shown | |||
below. | below. | |||
IANA has allocated the following new subobject in the "Subobject type | IANA has allocated the following new subobject in the "Subobject type | |||
- 20 EXPLICIT_ROUTE - Type 1 Explicit Route" registry: | - 20 EXPLICIT_ROUTE - Type 1 Explicit Route" registry: | |||
+=======+==========================+ | +=======+==========================+ | |||
| Value | Description | | | Value | Description | | |||
+=======+==========================+ | +=======+==========================+ | |||
| 40 | SRv6-ERO (PCEP-specific) | | | 40 | SRv6-ERO (PCEP-specific) | | |||
+-------+--------------------------+ | +-------+--------------------------+ | |||
skipping to change at line 1128 ¶ | skipping to change at line 1128 ¶ | |||
A., and P. Mattes, "Segment Routing Policy Architecture", | A., and P. Mattes, "Segment Routing Policy Architecture", | |||
RFC 9256, DOI 10.17487/RFC9256, July 2022, | RFC 9256, DOI 10.17487/RFC9256, July 2022, | |||
<https://www.rfc-editor.org/info/rfc9256>. | <https://www.rfc-editor.org/info/rfc9256>. | |||
[RFC9352] Psenak, P., Ed., Filsfils, C., Bashandy, A., Decraene, B., | [RFC9352] Psenak, P., Ed., Filsfils, C., Bashandy, A., Decraene, B., | |||
and Z. Hu, "IS-IS Extensions to Support Segment Routing | and Z. Hu, "IS-IS Extensions to Support Segment Routing | |||
over the IPv6 Data Plane", RFC 9352, DOI 10.17487/RFC9352, | over the IPv6 Data Plane", RFC 9352, DOI 10.17487/RFC9352, | |||
February 2023, <https://www.rfc-editor.org/info/rfc9352>. | February 2023, <https://www.rfc-editor.org/info/rfc9352>. | |||
[PCEP-YANG] | [PCEP-YANG] | |||
Dhody, D., Beeram, V. P., Hardwick, J., and J. Tantsura, | Dhody, D., Ed., Beeram, V., Hardwick, J., and J. Tantsura, | |||
"A YANG Data Model for Path Computation Element | "A YANG Data Model for Path Computation Element | |||
Communications Protocol (PCEP)", Work in Progress, | Communications Protocol (PCEP)", Work in Progress, | |||
Internet-Draft, draft-ietf-pce-pcep-yang-25, 21 May 2024, | Internet-Draft, draft-ietf-pce-pcep-yang-25, 21 May 2024, | |||
<https://datatracker.ietf.org/doc/html/draft-ietf-pce- | <https://datatracker.ietf.org/doc/html/draft-ietf-pce- | |||
pcep-yang-25>. | pcep-yang-25>. | |||
[PCEP-SRv6-YANG] | [PCEP-SRv6-YANG] | |||
Li, C., Sivabalan, S., Peng, S., Koldychev, M., and L. | Li, C., Sivabalan, S., Peng, S., Koldychev, M., and L. | |||
Ndifor, "A YANG Data Model for Segment Routing (SR) Policy | Ndifor, "A YANG Data Model for Segment Routing (SR) Policy | |||
and SR in IPv6 (SRv6) support in Path Computation Element | and SR in IPv6 (SRv6) support in Path Computation Element | |||
End of changes. 2 change blocks. | ||||
3 lines changed or deleted | 3 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |