draft-ietf-isis-layer2-08.txt   draft-ietf-isis-layer2-09.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: May 27, 2011 Juniper Networks Expires: June 23, 2011 Juniper Networks
November 23, 2010 December 20, 2010
Extensions to IS-IS for Layer-2 Systems Extensions to IS-IS for Layer-2 Systems
draft-ietf-isis-layer2-08 draft-ietf-isis-layer2-09
Abstract Abstract
This document specifies the IS-IS extensions necessary to support This document specifies the IS-IS extensions necessary to support
link state routing to any protocols running directly over layer 2. link state routing for any protocols running directly over layer 2.
While supporting this concept involves several pieces, this document While supporting this concept involves several pieces, this document
only describes extensions to IS-IS. Furthermore, the TLVs described only describes extensions to IS-IS. Furthermore, the TLVs described
in this document are generic layer 2 additions and specific ones as in this document are generic layer 2 additions and specific ones as
needed are defined in the IS-IS technology specific extensions. We needed are defined in the IS-IS technology specific extensions. We
leave it to the systems using these IS-IS extensions to explain how leave it to the systems using these IS-IS extensions to explain how
the information carried in IS-IS is used. the information carried in IS-IS is used.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 May 27, 2011. This Internet-Draft will expire on June 23, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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 4, line 12 skipping to change at page 4, line 12
"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
In this section we specify the enhancements for the TLVs that are In this section we specify the enhancements for the TLVs that are
needed in common by Layer-2 technologies. needed in common by Layer-2 technologies.
2.1. The MAC-Reachability TLV 2.1. The MAC-Reachability TLV
The MAC-Reachability (MAC-RI) TLV is IS-IS TLV type 141 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)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname | (2 bytes) | Topology-Id/ Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Confidence | (1 byte) | Confidence | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESV | VLAN-ID | (2 bytes) | RESV | VLAN-ID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC (1) (6 bytes) | | MAC (1) (6 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC (N) (6 bytes) | | MAC (N) (6 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to 141 (MAC-RI). o Type: TLV Type, set to 147 (MAC-RI).
o Length: Total number of bytes contained in the value field given o Length: Total number of bytes contained in the value field given
by 5 + 6*n bytes. by 5 + 6*n bytes.
o Topology-Id/Nickname : Depending on the technology in which it is o Topology-Id/Nickname : Depending on the technology in which it is
used, this carries the topology-id or nickname. When this field used, this carries the topology-id or nickname. When this field
is set to zero this implies that the MAC addresses are reachable is set to zero this implies that the MAC addresses are reachable
across all topologies or across all nicknames of the originating across all topologies or across all nicknames of the originating
IS. IS.
o Confidence: This carries an 8-bit quantity indicating the o Confidence: This carries an 8-bit quantity indicating the
confidence level in the MAC addresses being transported. Whether confidence level in the MAC addresses being transported. Whether
this field is used, and its semantics if used, are further defined this field is used, and its semantics if used, are further defined
by the specific protocol using Layer-2-IS-IS. If not used, it by the specific protocol using Layer-2-IS-IS. If not used, it
MUST be set to zero on transmission and be ignored on receipt. MUST be set to zero on transmission and be ignored on receipt.
o RESV: Must be sent as zero on transmission and is ignored on o RESV: MUST be sent as zero and ignored on receipt.
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. It The MAC-RI TLV is carried in a standard Level 1 link state PDU (LSP).
MUST contain only unicast addresses. The manner in which these TLVs This TLV can be carried multiple times in an LSP and in multiple
are generated by the various Layer 2 routing technologies, and the LSPs. It MUST contain only unicast addresses. The manner in which
manner they are consumed are detailed in the technology specific these TLVs are generated by the various Layer 2 routing technologies,
documents. and the manner they are consumed are detailed in the technology
specific 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.
2.2. Multi Topology aware Port Capability TLV 2.2. Multi Topology aware Port Capability TLV
The Multi Topology aware Port Capability (MT-PORT-CAP) is an IS-IS The Multi Topology aware Port Capability (MT-PORT-CAP) is an IS-IS
TLV type 143 [TBD], and has the following format: TLV type 143 [TBD], and has the following format:
0 1 2 3 0 1 2 3
skipping to change at page 5, line 39 skipping to change at page 5, line 40
|Type=MT PORTCAP| Length |R|R|R|R| Topology Identifier | |Type=MT PORTCAP| Length |R|R|R|R| Topology Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLVs | | sub-TLVs |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to MT-PORT-CAP TLV 143 [TBD]. o Type: TLV Type, set to MT-PORT-CAP TLV 143 [TBD].
o Length: Total number of bytes contained in the value field, o Length: Total number of bytes contained in the value field,
including the length of the sub-TLVs carried in this TLV. including the length of the sub-TLVs carried in this TLV.
o R: Reserved, MUST be sent as zero on transmission and is ignored o R: Reserved, MUST be sent as zero and ignored on receipt.
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 aware Port Capabilities TLV value contains sub- o sub-TLVs: The MT aware Port Capabilities TLV value contains sub-
TLVs formatted as described in [RFC5305]. They are defined in the TLVs formatted as described in [RFC5305]. They are defined in the
technology scoped documents. technology 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 only
skipping to change at page 8, line 8 skipping to change at page 8, line 8
Mike Shand, and Russ White for their useful comments. Mike Shand, and Russ White for their useful comments.
4. Security Considerations 4. Security Considerations
This document adds no additional security risks to IS-IS, nor does it This document adds no additional security risks to IS-IS, nor does it
provide any additional security for IS-IS. provide any additional security for IS-IS.
5. IANA Considerations 5. IANA Considerations
This document specifies the definition of a set of new IS-IS TLVs, This document specifies the definition of a set of new IS-IS TLVs,
the MAC-Reachability TLV (type 141), and the Port-Capability TLV the Port-Capability TLV (type 143), and the MAC-Reachability TLV
(type 143) that needs to be reflected in the IS-IS TLV code-point (type 147) that needs to be reflected in the IS-IS TLV code-point
registry. registry.
IIH LSP SNP IIH LSP SNP
MAC-RI TLV (141) - X -
MT-Port-Cap-TLV (143) X - - MT-Port-Cap-TLV (143) X - -
MAC-RI TLV (147) - X -
6. References 6. References
6.1. Normative References 6.1. Normative References
[IS-IS] ISO/IEC 10589:2002, Second Edition, "Intermediate System [IS-IS] ISO/IEC 10589:2002, Second Edition, "Intermediate System
to Intermediate System Intra-Domain Routing Exchange to Intermediate System Intra-Domain Routing Exchange
Protocol for use in Conjunction with the Protocol for Protocol for use in Conjunction with the Protocol for
Providing the Connectionless-mode Network Service (ISO Providing the Connectionless-mode Network Service (ISO
8473)", 2002. 8473)", 2002.
 End of changes. 12 change blocks. 
20 lines changed or deleted 18 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/