draft-ietf-isis-layer2-10.txt   draft-ietf-isis-layer2-11.txt 
Network Working Group A. Banerjee Network Working Group A. Banerjee
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track D. Ward Intended status: Standards Track D. Ward
Expires: July 31, 2011 Juniper Networks Expires: August 13, 2011 Juniper Networks
January 27, 2011 February 9, 2011
Extensions to IS-IS for Layer-2 Systems Extensions to IS-IS for Layer-2 Systems
draft-ietf-isis-layer2-10 draft-ietf-isis-layer2-11
Abstract Abstract
This document specifies the Intermediate System to Intermediate This document specifies the Intermediate System to Intermediate
System (IS-IS) extensions necessary to support link state routing for System (IS-IS) extensions necessary to support link state routing for
any protocols running directly over Layer-2. While supporting this any protocols running directly over Layer-2. While supporting this
concept involves several pieces, this document only describes concept involves several pieces, this document only describes
extensions to IS-IS. Furthermore, the Type, Length, Value pairs extensions to IS-IS. Furthermore, the Type, Length, Value pairs
(TLVs) described in this document are generic Layer-2 additions and (TLVs) described in this document are generic Layer-2 additions and
specific ones as needed are defined in the IS-IS technology specific specific ones as needed are defined in the IS-IS technology specific
skipping to change at page 1, line 39 skipping to change at page 1, line 39
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 July 31, 2011. This Internet-Draft will expire on August 13, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2011 IETF Trust and the persons identified as the Copyright (c) 2011 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 3, line 21 skipping to change at page 3, line 21
almost all the technologies mentioned above, classical Layer-2 almost all the technologies mentioned above, classical Layer-2
packets are encapsulated with an outer header. The outer header packets are encapsulated with an outer header. The outer header
format varies across all these technologies. This outer header is format varies across all these technologies. This outer header is
used to route the encapsulated packets to their destination. used to route the encapsulated packets to their destination.
Each Intermediate System (IS) advertises one or more IS-IS Link State Each Intermediate System (IS) advertises one or more IS-IS Link State
Protocol Data Units (PDUs) with routing information. Each Link State Protocol Data Units (PDUs) with routing information. Each Link State
PDU (LSP) is composed of a fixed header and a number of tuples, each PDU (LSP) is composed of a fixed header and a number of tuples, each
consisting of a Type, a Length, and a Value. Such tuples are consisting of a Type, a Length, and a Value. Such tuples are
commonly known as TLVs. In this document we specify a set of TLVs to commonly known as TLVs. In this document we specify a set of TLVs to
be added to [IS-IS] level 1 PDUs, to support these proposed systems. be added to [IS-IS] PDUs, to support these proposed systems. The
The TLVs are generic Layer-2 additions and specific ones, as needed, TLVs are generic Layer-2 additions and specific ones, as needed, are
are defined in the IS-IS technology specific extensions. This draft defined in the IS-IS technology specific extensions. This draft does
does not propose any new forwarding mechanisms using this additional not propose any new forwarding mechanisms using this additional
information carried within IS-IS. information carried within IS-IS.
1.1. Terminology 1.1. Terminology
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. document are to be interpreted as described in RFC 2119.
2. TLV Enhancements to IS-IS 2. TLV Enhancements to IS-IS
skipping to change at page 4, line 40 skipping to change at page 4, line 40
o R: Reserved 4-bits, MUST be sent as zero and ignored on receipt. o R: Reserved 4-bits, MUST be sent as zero and ignored on receipt.
o Topology Identifier: MT ID is a 12-bit field containing the MT ID o Topology Identifier: MT ID is a 12-bit field containing the MT ID
of the topology being announced. This field when set to zero of the topology being announced. This field when set to zero
implies that it is being used to carry base topology information. implies that it is being used to carry base topology information.
o sub-TLVs: The MT-PORT-CAP TLV value contains sub-TLVs formatted as o sub-TLVs: The MT-PORT-CAP TLV value contains sub-TLVs formatted as
described in [RFC 5305]. They are defined in the technology described in [RFC 5305]. They are defined in the technology
scoped documents. scoped documents.
The MT-PORT-CAP TLV may occur multiple times, and is carried only The MT-PORT-CAP TLV may occur multiple times, and is carried within a
within a IS-IS Hello (IIH) PDU. IS-IS Hello (IIH) PDU.
2.2. The MAC-Reachability TLV 2.2. The MAC-Reachability TLV
The MAC-Reachability (MAC-RI) TLV is IS-IS TLV type 147 and has the The MAC-Reachability (MAC-RI) TLV is IS-IS TLV type 147 and has the
following format: following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type= MAC-RI | (1 byte) | Type= MAC-RI | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
skipping to change at page 5, line 49 skipping to change at page 5, line 49
o RESV: (4-bits) MUST be sent as zero and ignored on receipt. o RESV: (4-bits) MUST be sent as zero and ignored on receipt.
o VLAN-ID: This carries a 12-bit VLAN identifier that is valid for o VLAN-ID: This carries a 12-bit VLAN identifier that is valid for
all subsequent MAC addresses in this TLV, or the value zero if no all subsequent MAC addresses in this TLV, or the value zero if no
VLAN is specified. VLAN is specified.
o MAC(i): This is the 48-bit MAC address reachable from the IS that o MAC(i): This is the 48-bit MAC address reachable from the IS that
is announcing this TLV. is announcing this TLV.
The MAC-RI TLV is carried in a standard Level 1 link state PDU (LSP). The MAC-RI TLV is carried in a standard Link State PDU (LSP). This
This TLV can be carried multiple times in an LSP and in multiple TLV can be carried multiple times in an LSP and in multiple LSPs. It
LSPs. It MUST contain only unicast addresses. The manner in which MUST contain only unicast addresses. The manner in which these TLVs
these TLVs are generated by the various Layer-2 routing technologies, are generated by the various Layer-2 routing technologies, and the
and the manner they are consumed are detailed in the technology manner they are consumed are detailed in the technology specific
specific documents. documents.
In most of the technologies, these MAC-RI TLVs will translate to In most of the technologies, these MAC-RI TLVs will translate to
populating the hardware with these entries with appropriate next-hop populating the hardware with these entries with appropriate next-hop
information as derived from the advertising IS. information as derived from the advertising IS.
3. Acknowledgements 3. Acknowledgements
The authors would like to thank Peter Ashwood-Smith, Donald E. The authors would like to thank Peter Ashwood-Smith, Donald E.
Eastlake 3rd, Dino Farinacci, Don Fedyk, Les Ginsberg, Radia Perlman, Eastlake 3rd, Dino Farinacci, Don Fedyk, Les Ginsberg, Radia Perlman,
Mike Shand, and Russ White for their useful comments. Mike Shand, and Russ White for their useful comments.
 End of changes. 6 change blocks. 
16 lines changed or deleted 16 lines changed or added

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