IP Traffic Engineering Architecture with Network Programming

Document Type Expired Internet-Draft (individual)
Author Robert Raszuk 
Last updated 2020-03-29 (latest revision 2019-09-26)
Stream (None)
Intended RFC status (None)
Expired & archived
pdf htmlized (tools) htmlized 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


This document describes a control plane based IP Traffic Engineering Architecture where path information is kept in the control plane by selected nodes instead of being inserted into each packet on ingress of an administrative domain. The described proposal is also fully compatible with the concept of network programming. It is positioned as a complimentary technique to native SRv6 and can be used when there are concerns with increased packet size due to depth of SID stack, possible concerns regarding exceeding MTU or more strict simplicity requirements typically seen in number of enterprise networks. The proposed solution is applicable to both IPv4 or IPv6 based networks. As an additional added value, detection of end to end path liveness as well as dynamic path selection based on real time path quality is integrated from day one in the design.


Robert Raszuk (robert@raszuk.net)

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