Segment Routing interworking with RSVP-TE
draft-hu-spring-segment-routing-rsvp-te-interop-00

Document Type Expired Internet-Draft (individual)
Last updated 2019-01-01 (latest revision 2018-06-30)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-hu-spring-segment-routing-rsvp-te-interop-00.txt

Abstract

A Segment Routing (SR) node steers a packet through an ordered list of instructions, called segments. A segment can represent any instruction, topological or service-based. Segment Routing (SR) is a protocol designed to forward packets on the network based on the concept of source routing. The Segment Routing architecture can be directly applied to the MPLS data plane with no change in the forwarding plane. It simplifies the MPLS control protocol, simplifies the configuration of the network, and can achieve SDN better. Resource Reservation Protocol - Traffic Engineering (RSVP-TE) has the ability of path planning and resource reservation. In the process of traditional network evolution to Segment Routing, there will inevitably be coexistence of RSVP-TE and Segment Routing. The Document describes how to interact with nodes that support Segment Routing capabilities and nodes that support RSVP-TE capabilities.

Authors

Zhibo Hu (huzhibo@huawei.com)
Gang Yan (yangang@huawei.com)
Xia Chen (jescia.chenxia@huawei.com)
Junda Yao (yaojunda@huawei.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)