rfc9522v3.txt   rfc9522.txt 
skipping to change at line 400 skipping to change at line 400
assigned to a flow or traffic aggregate in order to deliver assigned to a flow or traffic aggregate in order to deliver
"acceptable service quality" to the flow or traffic aggregate. "acceptable service quality" to the flow or traffic aggregate.
See [KELLY] for a more mathematical definition. See [KELLY] for a more mathematical definition.
Egress node: The device (router) at which traffic leaves a network Egress node: The device (router) at which traffic leaves a network
toward a destination (host, server, etc.) or to another network. toward a destination (host, server, etc.) or to another network.
End-to-end: This term is context-dependent and often applies to the End-to-end: This term is context-dependent and often applies to the
life of a traffic flow from original source to final destination. life of a traffic flow from original source to final destination.
In contrast, edge-to-edge is often used to describe the traffic In contrast, edge-to-edge is often used to describe the traffic
flow from the entry of a domain or network, to the exit of that flow from the entry of a domain or network to the exit of that
domain or network. However, in some contexts (for example, where domain or network. However, in some contexts (for example, where
there is a service interface between a network and the client of there is a service interface between a network and the client of
that network or where a path traverses multiple domains under the that network or where a path traverses multiple domains under the
control of a single process), end-to-end is used to refer to the control of a single process), end-to-end is used to refer to the
full operation of the service that may be composed of concatenated full operation of the service that may be composed of concatenated
edge-to-edge operations. Thus, in the context of TE, the term edge-to-edge operations. Thus, in the context of TE, the term
"end-to-end" may refer to the full TE path but not to the complete "end-to-end" may refer to the full TE path but not to the complete
path of the traffic from source application to ultimate path of the traffic from source application to ultimate
destination. destination.
skipping to change at line 1724 skipping to change at line 1724
IETF Network Slices are defined such that they are independent of the IETF Network Slices are defined such that they are independent of the
underlying infrastructure connectivity and technologies used. From a underlying infrastructure connectivity and technologies used. From a
customer's perspective, an IETF Network Slice looks like a VPN customer's perspective, an IETF Network Slice looks like a VPN
connectivity matrix with additional information about the level of connectivity matrix with additional information about the level of
service that the customer requires between the endpoints. From an service that the customer requires between the endpoints. From an
operator's perspective, the IETF Network Slice looks like a set of operator's perspective, the IETF Network Slice looks like a set of
routing or tunneling instructions with the network resource routing or tunneling instructions with the network resource
reservations necessary to provide the required service levels as reservations necessary to provide the required service levels as
specified by the SLOs. The concept of an IETF Network Slice is specified by the SLOs. The concept of an IETF Network Slice is
consistent with an enhanced VPN (VPN+) [ENHANCED-VPN]. consistent with an enhanced VPN [ENHANCED-VPN].
5.1.3. IETF Techniques Used by TE Mechanisms 5.1.3. IETF Techniques Used by TE Mechanisms
5.1.3.1. Constraint-Based Routing 5.1.3.1. Constraint-Based Routing
Constraint-based routing refers to a class of routing systems that Constraint-based routing refers to a class of routing systems that
compute routes through a network subject to the satisfaction of a set compute routes through a network subject to the satisfaction of a set
of constraints and requirements. In the most general case, of constraints and requirements. In the most general case,
constraint-based routing may also seek to optimize overall network constraint-based routing may also seek to optimize overall network
performance while minimizing costs. performance while minimizing costs.
skipping to change at line 3250 skipping to change at line 3250
DOI 10.1109/ICCCN.1998.998795, October 1998, DOI 10.1109/ICCCN.1998.998795, October 1998,
<https://ieeexplore.ieee.org/document/998795>. <https://ieeexplore.ieee.org/document/998795>.
[E.360.1] ITU-T, "Framework for QoS routing and related traffic [E.360.1] ITU-T, "Framework for QoS routing and related traffic
engineering methods for IP-, ATM-, and TDM-based engineering methods for IP-, ATM-, and TDM-based
multiservice networks", ITU-T Recommendation E.360.1, May multiservice networks", ITU-T Recommendation E.360.1, May
2002, <https://www.itu.int/rec/T-REC-E.360.1-200205-I/en>. 2002, <https://www.itu.int/rec/T-REC-E.360.1-200205-I/en>.
[ENHANCED-VPN] [ENHANCED-VPN]
Dong, J., Bryant, S., Li, Z., Miyasaka, T., and Y. Lee, "A Dong, J., Bryant, S., Li, Z., Miyasaka, T., and Y. Lee, "A
Framework for Enhanced Virtual Private Network (VPN+)", Framework for NRP-based Enhanced Virtual Private Network",
Work in Progress, Internet-Draft, draft-ietf-teas- Work in Progress, Internet-Draft, draft-ietf-teas-
enhanced-vpn-15, 23 October 2023, enhanced-vpn-17, 25 December 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-teas- <https://datatracker.ietf.org/doc/html/draft-ietf-teas-
enhanced-vpn-15>. enhanced-vpn-17>.
[Err309] RFC Errata, Erratum ID 309, RFC 3272, [Err309] RFC Errata, Erratum ID 309, RFC 3272,
<https://www.rfc-editor.org/errata/eid309>. <https://www.rfc-editor.org/errata/eid309>.
[EVPN-UNEQUAL-LB] [EVPN-UNEQUAL-LB]
Malhotra, N., Ed., Sajassi, A., Rabadan, J., Drake, J., Malhotra, N., Ed., Sajassi, A., Rabadan, J., Drake, J.,
Lingala, A., and S. Thoria, "Weighted Multi-Path Lingala, A., and S. Thoria, "Weighted Multi-Path
Procedures for EVPN Multi-Homing", Work in Progress, Procedures for EVPN Multi-Homing", Work in Progress,
Internet-Draft, draft-ietf-bess-evpn-unequal-lb-18, 1 June Internet-Draft, draft-ietf-bess-evpn-unequal-lb-21, 7
2023, <https://datatracker.ietf.org/doc/html/draft-ietf- December 2023, <https://datatracker.ietf.org/doc/html/
bess-evpn-unequal-lb-18>. draft-ietf-bess-evpn-unequal-lb-21>.
[FLJA93] Floyd, S. and V. Jacobson, "Random Early Detection [FLJA93] Floyd, S. and V. Jacobson, "Random Early Detection
Gateways for Congestion Avoidance", IEEE/ACM Transactions Gateways for Congestion Avoidance", IEEE/ACM Transactions
on Networking, Volume 1, Issue 4, Pages 397-413, on Networking, Volume 1, Issue 4, Pages 397-413,
DOI 10.1109/90.251892, August 1993, DOI 10.1109/90.251892, August 1993,
<https://www.icir.org/floyd/papers/early.twocolumn.pdf>. <https://www.icir.org/floyd/papers/early.twocolumn.pdf>.
[FT00] Fortz, B. and M. Thorup, "Internet Traffic Engineering by [FT00] Fortz, B. and M. Thorup, "Internet Traffic Engineering by
Optimizing OSPF Weights", Proceedings IEEE INFOCOM 2000, Optimizing OSPF Weights", Proceedings IEEE INFOCOM 2000,
DOI 10.1109/INFCOM.2000.832225, March 2000, DOI 10.1109/INFCOM.2000.832225, March 2000,
skipping to change at line 3333 skipping to change at line 3333
Framework for Network Slices in Networks Built from IETF Framework for Network Slices in Networks Built from IETF
Technologies", Work in Progress, Internet-Draft, draft- Technologies", Work in Progress, Internet-Draft, draft-
ietf-teas-ietf-network-slices-25, 14 September 2023, ietf-teas-ietf-network-slices-25, 14 September 2023,
<https://datatracker.ietf.org/doc/html/draft-ietf-teas- <https://datatracker.ietf.org/doc/html/draft-ietf-teas-
ietf-network-slices-25>. ietf-network-slices-25>.
[PERFORMANCE-ROUTING] [PERFORMANCE-ROUTING]
Xu, X., Hegde, S., Talaulikar, K., Boucadair, M., and C. Xu, X., Hegde, S., Talaulikar, K., Boucadair, M., and C.
Jacquenet, "Performance-based BGP Routing Mechanism", Work Jacquenet, "Performance-based BGP Routing Mechanism", Work
in Progress, Internet-Draft, draft-ietf-idr-performance- in Progress, Internet-Draft, draft-ietf-idr-performance-
routing-03, 21 December 2020, routing-03, 22 December 2020,
<https://datatracker.ietf.org/doc/html/draft-ietf-idr- <https://datatracker.ietf.org/doc/html/draft-ietf-idr-
performance-routing-03>. performance-routing-03>.
[QUIC-MULTIPATH] [QUIC-MULTIPATH]
Liu, Y., Ed., Ma, Y., Ed., De Coninck, Q., Ed., Liu, Y., Ed., Ma, Y., Ed., De Coninck, Q., Ed.,
Bonaventure, O., Huitema, C., and M. Kühlewind, Ed., Bonaventure, O., Huitema, C., and M. Kühlewind, Ed.,
"Multipath Extension for QUIC", Work in Progress, "Multipath Extension for QUIC", Work in Progress,
Internet-Draft, draft-ietf-quic-multipath-06, 23 October Internet-Draft, draft-ietf-quic-multipath-06, 23 October
2023, <https://datatracker.ietf.org/doc/html/draft-ietf- 2023, <https://datatracker.ietf.org/doc/html/draft-ietf-
quic-multipath-06>. quic-multipath-06>.
skipping to change at line 4018 skipping to change at line 4018
A.1. RFC 3272 A.1. RFC 3272
* Section 1.0 ("Introduction"): Edited in place in Section 1. * Section 1.0 ("Introduction"): Edited in place in Section 1.
- Section 1.1 ("What is Internet Traffic Engineering?"): Edited - Section 1.1 ("What is Internet Traffic Engineering?"): Edited
in place in Section 1.1. in place in Section 1.1.
- Section 1.2 ("Scope"): Moved to Section 1.3. - Section 1.2 ("Scope"): Moved to Section 1.3.
- Section 1.3 ("Terminology): Moved to Section 1.4 with some - Section 1.3 ("Terminology"): Moved to Section 1.4 with some
obsolete terms removed and a little editing. obsolete terms removed and a little editing.
* Section 2.0 ("Background"): Retained as Section 2 with some text * Section 2.0 ("Background"): Retained as Section 2 with some text
removed. removed.
- Section 2.1 ("Context of Internet Traffic Engineering"): - Section 2.1 ("Context of Internet Traffic Engineering"):
Retained as Section 2.1. Retained as Section 2.1.
- Section 2.2 ("Network Context"): Rewritten as Section 2.2. - Section 2.2 ("Network Context"): Rewritten as Section 2.2.
- Section 2.3 ("Problem Context"): Rewritten as Section 2.3. - Section 2.3 ("Problem Context"): Rewritten as Section 2.3.
o Section 2.3.1 ("Congestion and its Ramifications): Retained o Section 2.3.1 ("Congestion and its Ramifications"): Retained
as Section 2.3.1. as Section 2.3.1.
- Section 2.4 ("Solution Context"): Edited as Section 2.4. - Section 2.4 ("Solution Context"): Edited as Section 2.4.
o Section 2.4.1 ("Combating the Congestion Problem"): o Section 2.4.1 ("Combating the Congestion Problem"):
Reformatted as Section 2.4.1. Reformatted as Section 2.4.1.
- Section 2.5 ("Implementation and Operational Context"): - Section 2.5 ("Implementation and Operational Context"):
Retained as Section 2.5. Retained as Section 2.5.
skipping to change at line 4184 skipping to change at line 4184
- Section 2.1: Based on Section 2.1 of [RFC3272]. - Section 2.1: Based on Section 2.1 of [RFC3272].
- Section 2.2: Based on Section 2.2 of [RFC3272]. - Section 2.2: Based on Section 2.2 of [RFC3272].
- Section 2.3: Based on Section 2.3 of [RFC3272]. - Section 2.3: Based on Section 2.3 of [RFC3272].
o Section 2.3.1: Based on Section 2.3.1 of [RFC3272]. o Section 2.3.1: Based on Section 2.3.1 of [RFC3272].
- Section 2.4: Based on Section 2.4 of [RFC3272]. - Section 2.4: Based on Section 2.4 of [RFC3272].
o Section 2.4.1: Based on Section 2.4.1 of [RFC3272] o Section 2.4.1: Based on Section 2.4.1 of [RFC3272].
- Section 2.5: Based on Section 2.5 of [RFC3272]. - Section 2.5: Based on Section 2.5 of [RFC3272].
* Section 3: Based on Section 3 of [RFC3272]. * Section 3: Based on Section 3 of [RFC3272].
- Section 3.1: Based on Sections 3.1, 3.2, 3.3, and 3.4 of - Section 3.1: Based on Sections 3.1, 3.2, 3.3, and 3.4 of
[RFC3272]. [RFC3272].
* Section 4: Based on Section 5 of [RFC3272]. * Section 4: Based on Section 5 of [RFC3272].
 End of changes. 10 change blocks. 
12 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.48.