Multipath Extensions for MPLS Traffic Engineering
draft-villamizar-mpls-tp-multipath-te-extn-02

 
Document
Type Replaced Internet-Draft (individual)
Last updated 2013-01-10 (latest revision 2012-10-07)
Replaced by draft-villamizar-mpls-multipath-extn
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
Stream state (No stream defined)
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-villamizar-mpls-multipath-extn
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR 1 References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
//www.ietf.org/archive/id/draft-villamizar-mpls-tp-multipath-te-extn-02.txt

Abstract

Extensions to OSPF-TE, ISIS-TE, and RSVP-TE are defined in support of carrying LSP with strict packet ordering requirements over multipath and and carrying LSP with strict packet ordering requirements within LSP without violating requirements to maintain packet ordering. LSP with strict packet ordering requirements include MPLS-TP LSP. OSPF-TE and ISIS-TE extensions defined here indicate node and link capability regarding support for ordered aggregates of traffic, multipath traffic distribution, and abilities to support multipath load distribution differently per LSP. RSVP-TE extensions either identifies an LSP as requiring strict packet order, or identifies an LSP as carrying one or more LSP that requires strict packet order further down in the label stack, or identifies an LSP as having no restrictions on packet ordering except the restriction to avoid reordering microflows. In addition an extension indicates whether the first nibble of payload will reliably indicate whether payload is IPv4, IPv6, or other type of payload, most notably pseudowire using a pseudowire control word.

Authors

Curtis Villamizar (curtis@occnc.com)

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