draft-ietf-softwire-bgp-te-attribute-02.txt   draft-ietf-softwire-bgp-te-attribute-03.txt 
Network Working Group Hamid Ould-Brahim (Nortel Networks) Network Working Group Hamid Ould-Brahim (Nortel Networks)
Internet Draft Don Fedyk (Nortel Networks) Internet Draft Don Fedyk (Nortel Networks)
Expiration Date: March 2009 Yakov Rekhter (Juniper Networks) Expiration Date: March 2009 Yakov Rekhter (Juniper Networks)
Intended Status: Proposed Standard Intended Status: Proposed Standard
Traffic Engineering Attribute BGP Traffic Engineering Attribute
draft-ietf-softwire-bgp-te-attribute-02.txt draft-ietf-softwire-bgp-te-attribute-03.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 41 skipping to change at page 1, line 41
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Abstract Abstract
This document defines a new BGP attribute, Traffic Engineering This document defines a new BGP attribute, Traffic Engineering
attribute, than enables BGP to carry Traffic Engineering information. attribute, than enables BGP to carry Traffic Engineering information.
The scope and applicability of this attribute currently excludes its The scope and applicability of this attribute currently excludes its
use for non-VPN deployment scenarios. use for non-VPN reachability information.
1. Specification of Requirements 1. Specification of Requirements
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
In certain cases (e.g., L1VPN [RFC5195]) it may be useful to augment In certain cases (e.g., L1VPN [RFC5195]) it may be useful to augment
reachability information carried in BGP with the Traffic Engineering VPN reachability information carried in BGP with the Traffic
information. Engineering information.
This document defines a new BGP attribute, Traffic Engineering This document defines a new BGP attribute, Traffic Engineering
attribute, than enables BGP [RFC4271] to carry Traffic Engineering attribute, than enables BGP [RFC4271] to carry Traffic Engineering
information. information.
Section 4 of [RFC5195] describes one possible usage of this Section 4 of [RFC5195] describes one possible usage of this
attribute. attribute.
The scope and applicability of this attribute currently excludes its The scope and applicability of this attribute currently excludes its
use for non-VPN deployment scenarios. use for non-VPN reachability information.
Procedures for modifying the Traffic Engineering attribute, when re-
advertising a route that carries such attribute are outside the scope
of this document.
3. Traffic Engineering Attribute 3. Traffic Engineering Attribute
Traffic Engineering attribute is an optional non-transitive BGP Traffic Engineering attribute is an optional non-transitive BGP
attribute. attribute.
The information carried in this attribute is identical to what is The information carried in this attribute is identical to what is
carried in the Interface Switching Capability Descriptor, as carried in the Interface Switching Capability Descriptor, as
specified in [RFC4203], [RFC4205]. specified in [RFC4203], [RFC4205].
 End of changes. 5 change blocks. 
6 lines changed or deleted 10 lines changed or added

This html diff was produced by rfcdiff 1.35. The latest version is available from http://tools.ietf.org/tools/rfcdiff/