Advertising Encapsulation Capability Using IS-IS
draft-xu-isis-encapsulation-cap-01

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2015-02-13 (latest revision 2014-08-12)
Replaced by draft-ietf-isis-encapsulation-cap
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-xu-isis-encapsulation-cap-01.txt

Abstract

In a particular network environment where MPLS-SPRING-enabled routers are partially deployed, it needs to transport MPLS traffic through an IP-based tunnel between two MPLS-SPRING-enabled routers so as to traverse non-MPLS routers. The ingress of the IP-based tunnel must know which encapsulation type is supported by the egress of that IP- based tunnel.This document describes how to advertise the encapsulation capability of MPLS-SPRING-enabled routers using IS-IS. Note that this encapsulation capablity advertisment could be applicalbe to other use cases besides that as mentioned above as well.

Authors

Xiaohu Xu (xuxiaohu@huawei.com)
Robert Raszuk (robert@raszuk.net)
Uma Chunduri (uma.chunduri@ericsson.com)
Victor Lopezalvarez (victor.lopezalvarez@telefonica.com)

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