draft-ginsberg-isis-l2bundles-01.txt   draft-ginsberg-isis-l2bundles-02.txt 
Networking Working Group L. Ginsberg Networking Working Group L. Ginsberg
Internet-Draft A. Bashandy Internet-Draft A. Bashandy
Intended status: Standards Track C. Filsfils Intended status: Standards Track C. Filsfils
Expires: July 7, 2016 S. Previdi Expires: August 19, 2016 S. Previdi
Cisco Systems Cisco Systems
M. Nanduri M. Nanduri
Microsoft Microsoft
E. Aries E. Aries
Facebook Private Contributer
January 04, 2016 February 16, 2016
Advertising L2 Bundle Member Link Attributes in IS-IS Advertising L2 Bundle Member Link Attributes in IS-IS
draft-ginsberg-isis-l2bundles-01.txt draft-ginsberg-isis-l2bundles-02.txt
Abstract Abstract
There are deployments where the Layer 3 interface on which IS-IS
operates is a Layer 2 interface bundle. Existing IS-IS
advertisements only support advertising link attributes of the Layer
3 interface. If entities external to IS-IS wish to control traffic
flows on the individual physical links which comprise the Layer 2
interface bundle link attribute information about the bundle members
is required.
This document introduces the ability for IS-IS to advertise the link This document introduces the ability for IS-IS to advertise the link
attributes of layer 2 (L2) bundle members. attributes of layer 2 (L2) bundle members.
Requirements Language Requirements Language
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].
Status of This Memo Status of This Memo
skipping to change at page 1, line 42 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on August 19, 2016.
This Internet-Draft will expire on July 7, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 39 skipping to change at page 2, line 45
7.2. Informational References . . . . . . . . . . . . . . . . 12 7.2. Informational References . . . . . . . . . . . . . . . . 12
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
There are deployments where the Layer 3 interface on which an IS-IS There are deployments where the Layer 3 interface on which an IS-IS
adjacency is established is a Layer 2 interface bundle, for instance adjacency is established is a Layer 2 interface bundle, for instance
a Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the a Link Aggregation Group (LAG) [IEEE802.1AX]. This reduces the
number of adjacencies which need to be maintained by the routing number of adjacencies which need to be maintained by the routing
protocol in cases where there are parallel links between the protocol in cases where there are parallel links between the
neighbors. However, if there is still a desire to control traffic neighbors. Entities external to IS-IS such as Path Computation
flows on individual physical links, information about each of the L2 Elements (PCE) [RFC4655] may wish to control traffic flows on
bundle members is required. This document introduces a new TLV to individual members of the underlying Layer 2 bundle. In order to do
advertise link attribute information for each of the L2 bundle so link attribute information about individual bundle members is
members. required - but currently IS-IS only supports advertising link
attributes for the Layer 3 interfaces on which it operates.
This document introduces a new TLV to advertise link attribute
information for each of the L2 bundle members which comprise the
Layer 3 interface on which IS-IS operates.
[SR] introduces a new link attribute - adjacency segment identifier [SR] introduces a new link attribute - adjacency segment identifier
(Adj-SID) - which can be used as an instruction to forwarding to send (Adj-SID) - which can be used as an instruction to forwarding to send
traffic over a specific link. This document introduces additional traffic over a specific link. This document introduces additional
sub-TLVs to advertise Adj-SIDs for L2 Bundle members. sub-TLVs to advertise Adj-SIDs for L2 Bundle members.
Note that the new advertisements defined in this document are
intended to be provided to external entities.
2. L2 Bundle Member Attributes TLV 2. L2 Bundle Member Attributes TLV
A new TLV is introduced to advertise L2 Bundle member attributes. A new TLV is introduced to advertise L2 Bundle member attributes.
Although much of the information is identical to and uses the same Although much of the information is identical to and uses the same
sub-TLVs included in Extended IS-Neighbor advertisements (TLVs 22 and sub-TLVs included in Extended IS-Neighbor advertisements (TLVs 22 and
222), a new TLV is used so that changes to the advertisement of the 222), a new TLV is used so that changes to the advertisement of the
L2 Bundle member link attributes does not trigger unnecessary action L2 Bundle member link attributes does not trigger unnecessary action
by the [ISO10589] Decision process. by the [ISO10589] Decision process.
This new TLV utilizes the sub-TLV space defined for TLVs 22, 23, 141, This new TLV utilizes the sub-TLV space defined for TLVs 22, 23, 141,
skipping to change at page 12, line 7 skipping to change at page 12, line 7
in Support of Generalized Multi-Protocol Label Switching in Support of Generalized Multi-Protocol Label Switching
(GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008, (GMPLS)", RFC 5307, DOI 10.17487/RFC5307, October 2008,
<http://www.rfc-editor.org/info/rfc5307>. <http://www.rfc-editor.org/info/rfc5307>.
[RFC6119] Harrison, J., Berger, J., and M. Bartlett, "IPv6 Traffic [RFC6119] Harrison, J., Berger, J., and M. Bartlett, "IPv6 Traffic
Engineering in IS-IS", RFC 6119, DOI 10.17487/RFC6119, Engineering in IS-IS", RFC 6119, DOI 10.17487/RFC6119,
February 2011, <http://www.rfc-editor.org/info/rfc6119>. February 2011, <http://www.rfc-editor.org/info/rfc6119>.
7.2. Informational References 7.2. Informational References
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655,
DOI 10.17487/RFC4655, August 2006,
<http://www.rfc-editor.org/info/rfc4655>.
[SR] "IS-IS Extensions for Segment Routing, draft-ietf-isis- [SR] "IS-IS Extensions for Segment Routing, draft-ietf-isis-
segment-routing-extensions-06(work in progress)", December segment-routing-extensions-06(work in progress)", December
2015. 2015.
[SR-ARCH] "Segment Routing Architecture, draft-ietf-spring-segment- [SR-ARCH] "Segment Routing Architecture, draft-ietf-spring-segment-
routing-07(work in progress)", December 2015. routing-07(work in progress)", December 2015.
Authors' Addresses Authors' Addresses
Les Ginsberg Les Ginsberg
skipping to change at page 12, line 42 skipping to change at page 13, line 4
Email: cf@cisco.com Email: cf@cisco.com
Stefano Previdi Stefano Previdi
Cisco Systems Cisco Systems
Via Del Serafico 200 Via Del Serafico 200
Rome 0144 Rome 0144
Italy Italy
Email: sprevidi@cisco.com Email: sprevidi@cisco.com
Mohan Nanduri Mohan Nanduri
Microsoft Microsoft
Email: mnanduri@microsft.com Email: mnanduri@microsft.com
Ebben Aries Ebben Aries
Facebook Private Contributer
Email: exa@fb.com Email: exa@dscp.org
 End of changes. 12 change blocks. 
13 lines changed or deleted 33 lines changed or added

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