IP Traffic Engineering With Route Switched Paths (RSPs)
draft-shen-ip-te-rsp-03
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Naiming Shen | ||
| Last updated | 2004-11-02 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes a mechanism to establish traffic engineering IP tunnels. Resource ReSerVation Protocol (RSVP) is used as a signaling protocol described in Generalized Multi-Protocol Lable Swithing (GMPLS) RSVP Traffic Engineering technology, but no MPLS forwarding capability is assumed on the switched path. IP routing is used to switch IP traffic trunks. A simple GMPLS RSVP Traffic Engineering extension is needed to setup the IP Route Switched Paths (RSPs).
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)