draft-ietf-isis-layer2-02.txt   draft-ietf-isis-layer2-03.txt 
Network Working Group A. Banerjee, Ed. Network Working Group A. Banerjee, Ed.
Internet-Draft Cisco Systems Internet-Draft Cisco Systems
Intended status: Standards Track February 10, 2010 Intended status: Standards Track March 8, 2010
Expires: August 14, 2010 Expires: September 9, 2010
Extensions to IS-IS for Layer-2 Systems Extensions to IS-IS for Layer-2 Systems
draft-ietf-isis-layer2-02 draft-ietf-isis-layer2-03
Abstract Abstract
This document specifies the IS-IS extensions necessary to support This document specifies the IS-IS extensions necessary to support
multi-link IPv4 and IPv6 networks, as well as to provide true link multi-link IPv4 and IPv6 networks, as well as to provide true link
state routing to any protocols running directly over layer 2. While state routing to any protocols running directly over layer 2. While
supporting this concept involves several pieces, this document only supporting this concept involves several pieces, this document only
describes extensions to IS-IS. We leave it to the systems using describes extensions to IS-IS. We leave it to the systems using
these IS-IS extensions to explain how the information carried in these IS-IS extensions to explain how the information carried in
IS-IS is used. IS-IS is used.
skipping to change at page 1, line 42 skipping to change at page 1, line 42
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
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.
This Internet-Draft will expire on August 14, 2010. This Internet-Draft will expire on September 9, 2010.
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 2, line 22 skipping to change at page 2, line 22
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4 1.1. Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. PDU, TLV and sub-TLV Enhancements to IS-IS . . . . . . . . . . 4 2. PDU, TLV and sub-TLV Enhancements to IS-IS . . . . . . . . . . 4
2.1. The MAC-Reachability TLV . . . . . . . . . . . . . . . . . 4 2.1. The MAC-Reachability TLV . . . . . . . . . . . . . . . . . 4
2.2. The Group Address TLV . . . . . . . . . . . . . . . . . . 6 2.2. The Group Address TLV . . . . . . . . . . . . . . . . . . 6
2.2.1. The Group MAC Address sub-TLV . . . . . . . . . . . . 6 2.2.1. The Group MAC Address sub-TLV . . . . . . . . . . . . 6
2.2.2. The Group IP Address sub-TLV . . . . . . . . . . . . . 8 2.2.2. The Group IP Address sub-TLV . . . . . . . . . . . . . 8
2.2.3. The Group IPv6 Address sub-TLV . . . . . . . . . . . . 9 2.2.3. The Group IPv6 Address sub-TLV . . . . . . . . . . . . 10
2.2.4. The SPBV MAC Address sub-TLV . . . . . . . . . . . . . 11 2.2.4. The SPBV MAC Address sub-TLV . . . . . . . . . . . . . 11
2.3. Multi Topology aware Port Capability TLV . . . . . . . . . 13 2.3. Multi Topology aware Port Capability TLV . . . . . . . . . 13
2.3.1. The Special VLANs and Flags sub-TLV . . . . . . . . . 13 2.3.1. The Special VLANs and Flags sub-TLV . . . . . . . . . 14
2.3.2. Enabled VLANs sub-TLV . . . . . . . . . . . . . . . . 14 2.3.2. Enabled VLANs sub-TLV . . . . . . . . . . . . . . . . 15
2.3.3. Appointed Forwarders sub-TLV . . . . . . . . . . . . . 15 2.3.3. Appointed Forwarders sub-TLV . . . . . . . . . . . . . 16
2.3.4. Hop-by-Hop Options (HBHOPT) sub-TLV . . . . . . . . . 17 2.3.4. Hop-by-Hop Options (HBHOPT) sub-TLV . . . . . . . . . 17
2.3.5. Base VLAN-Identifiers sub-TLV . . . . . . . . . . . . 18 2.3.5. Base VLAN-Identifiers sub-TLV . . . . . . . . . . . . 18
2.3.6. SPB Digest sub-TLV . . . . . . . . . . . . . . . . . . 19 2.3.6. SPB Digest sub-TLV . . . . . . . . . . . . . . . . . . 19
2.3.7. Site Identifier sub-TLV . . . . . . . . . . . . . . . 20 2.3.7. Site Identifier sub-TLV . . . . . . . . . . . . . . . 21
2.3.8. Site Group IPv4 sub-TLV . . . . . . . . . . . . . . . 20 2.3.8. Site Group IPv4 sub-TLV . . . . . . . . . . . . . . . 21
2.3.9. Site Group IPv6 sub-TLV . . . . . . . . . . . . . . . 21 2.3.9. Site Group IPv6 sub-TLV . . . . . . . . . . . . . . . 22
2.3.10. Adjacency Server IPv4 sub-TLV . . . . . . . . . . . . 21 2.3.10. Adjacency Server IPv4 sub-TLV . . . . . . . . . . . . 22
2.3.11. Adjacency Server IPv6 sub-TLV . . . . . . . . . . . . 22 2.3.11. Adjacency Server IPv6 sub-TLV . . . . . . . . . . . . 23
2.4. Sub-TLVs for the Router Capability TLV . . . . . . . . . . 22 2.4. Sub-TLVs for the Router Capability TLV . . . . . . . . . . 23
2.4.1. The TRILL Version sub-TLV . . . . . . . . . . . . . . 22 2.4.1. The TRILL Version sub-TLV . . . . . . . . . . . . . . 23
2.4.2. The Nickname sub-TLV . . . . . . . . . . . . . . . . . 23 2.4.2. The Nickname sub-TLV . . . . . . . . . . . . . . . . . 24
2.4.3. The Trees sub-TLV . . . . . . . . . . . . . . . . . . 24 2.4.3. The Trees sub-TLV . . . . . . . . . . . . . . . . . . 25
2.4.4. The Tree Root Identifiers Sub-TLV . . . . . . . . . . 25 2.4.4. The Tree Identifiers Sub-TLV . . . . . . . . . . . . . 26
2.4.5. The Trees Used Identifiers Sub-TLV . . . . . . . . . . 26 2.4.5. The Trees Used Identifiers Sub-TLV . . . . . . . . . . 27
2.4.6. Interested VLANs and Spanning Tree Roots sub-TLV . . . 26 2.4.6. Interested VLANs and Spanning Tree Roots sub-TLV . . . 27
2.4.7. The VLAN Group sub-TLV . . . . . . . . . . . . . . . . 28 2.4.7. The VLAN Group sub-TLV . . . . . . . . . . . . . . . . 29
2.4.8. The Ingress-to-Egress Options (ITEOPT) sub-TLV . . . . 29 2.4.8. The Ingress-to-Egress Options (ITEOPT) sub-TLV . . . . 30
2.4.9. VLAN Mapping (VMAP) sub-TLV . . . . . . . . . . . . . 30 2.4.9. VLAN Mapping (VMAP) sub-TLV . . . . . . . . . . . . . 31
2.5. Multi Topology Aware Capability TLV . . . . . . . . . . . 31 2.5. Multi Topology Aware Capability TLV . . . . . . . . . . . 32
2.5.1. SPB Instance sub-TLV . . . . . . . . . . . . . . . . . 32 2.5.1. SPB Instance sub-TLV . . . . . . . . . . . . . . . . . 33
2.5.2. SPBM Service Identifier and Unicast Address sub-TLV . 34 2.5.2. SPBM Service Identifier and Unicast Address sub-TLV . 36
2.6. Sub-TLVs of the Extended Reachability TLV . . . . . . . . 35 2.6. Sub-TLVs of the Extended Reachability TLV . . . . . . . . 37
2.6.1. SPB Link Metric sub-TLV . . . . . . . . . . . . . . . 35 2.6.1. SPB Link Metric sub-TLV . . . . . . . . . . . . . . . 37
2.6.2. MTU sub-TLV . . . . . . . . . . . . . . . . . . . . . 36 2.6.2. MTU sub-TLV . . . . . . . . . . . . . . . . . . . . . 38
2.7. TRILL Neighbor TLV . . . . . . . . . . . . . . . . . . . . 37 2.7. TRILL Neighbor TLV . . . . . . . . . . . . . . . . . . . . 39
2.8. The Group Membership Active Source TLV . . . . . . . . . . 38 2.8. The Group Membership Active Source TLV . . . . . . . . . . 40
2.8.1. The Group MAC Active Source sub-TLV . . . . . . . . . 39 2.8.1. The Group MAC Active Source sub-TLV . . . . . . . . . 41
2.8.2. The Group IP Active Source sub-TLV . . . . . . . . . . 41 2.8.2. The Group IP Active Source sub-TLV . . . . . . . . . . 42
2.8.3. The Group IPv6 Active Source sub-TLV . . . . . . . . . 42 2.8.3. The Group IPv6 Active Source sub-TLV . . . . . . . . . 44
2.9. PDU Extensions to IS-IS . . . . . . . . . . . . . . . . . 44 2.9. PDU Extensions to IS-IS . . . . . . . . . . . . . . . . . 46
2.9.1. The Multicast Group PDU . . . . . . . . . . . . . . . 44 2.9.1. The Multicast Group PDU . . . . . . . . . . . . . . . 46
2.9.2. The TRILL-Hello PDU . . . . . . . . . . . . . . . . . 46 2.9.2. The TRILL-Hello PDU . . . . . . . . . . . . . . . . . 48
2.9.3. The MTU PDU . . . . . . . . . . . . . . . . . . . . . 47 2.9.3. The MTU PDU . . . . . . . . . . . . . . . . . . . . . 49
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 48 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 50
4. Security Considerations . . . . . . . . . . . . . . . . . . . 48 4. Security Considerations . . . . . . . . . . . . . . . . . . . 50
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 48 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 50
6. Contributing Authors . . . . . . . . . . . . . . . . . . . . . 51 6. Contributing Authors . . . . . . . . . . . . . . . . . . . . . 53
7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 52 7. References . . . . . . . . . . . . . . . . . . . . . . . . . . 54
7.1. Normative References . . . . . . . . . . . . . . . . . . . 52 7.1. Normative References . . . . . . . . . . . . . . . . . . . 54
7.2. Informative References . . . . . . . . . . . . . . . . . . 52 7.2. Informative References . . . . . . . . . . . . . . . . . . 55
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 53 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 55
1. Overview 1. Overview
There are a number of systems (for example, [RBRIDGES], [802.1aq]) There are a number of systems (for example, [RBRIDGES], [802.1aq])
that use layer 2 addresses carried in a link state routing protocol, that use layer 2 addresses carried in a link state routing protocol,
specifically IS-IS [IS-IS] [RFC1195], to provide true layer 2 specifically IS-IS [IS-IS] [RFC1195], to provide true layer 2
routing. This document specifies a set of TLVs and sub-TLVs to be routing. This document specifies a set of TLVs and sub-TLVs to be
added to [IS-IS] level 1 PDUs, and six new PDU types, to support added to [IS-IS] level 1 PDUs, and six new PDU types, to support
these proposed systems. Some of these TLVs are generic layer 2 these proposed systems. Some of these TLVs are generic layer 2
additions and some are specific to [RBRIDGES] or to [802.1aq]. This additions and some are specific to [RBRIDGES] or to [802.1aq]. This
draft does not propose any new forwarding mechanisms using this draft does not propose any new forwarding mechanisms using this
additional information carried within IS-IS. additional information carried within IS-IS.
This document specifies additional TLVs and sub-TLVs, to carry This document specifies additional TLVs and sub-TLVs, to carry
unicast and multicast attached address information. It also proposes unicast and multicast attached address information. It also
additional TLVs and sub-TLVs to carry information as required by the specifies additional TLVs and sub-TLVs to carry information as
IETF TRILL and IEEE 802.1aq protocols. required by the IETF TRILL and IEEE 802.1aq protocols.
This document specifies six new IS-IS PDUs. The Multicast Group This document specifies six new IS-IS PDUs. The Multicast Group
(MGROUP) PDU, for carrying a list of attached or joined multicast (MGROUP) PDU, for carrying a list of attached or joined multicast
groups. The Multicast Group Complete Sequence Number (MGROUP-CSNP) groups. The Multicast Group Complete Sequence Number (MGROUP-CSNP)
PDU and the Multicast Group Partial Sequence Number (MGROUP-PSNP) PDU PDU and the Multicast Group Partial Sequence Number (MGROUP-PSNP) PDU
packets are also defined to be used with the new MGROUP-PDU to packets are also defined to be used with the new MGROUP-PDU to
perform database exchange on the MGROUP PDUs. The TRILL-Hello PDU perform database exchange on the MGROUP PDUs. The TRILL-Hello PDU
provides the subnet specific layer of IS-IS for TRILL links. The provides the subnet specific layer of IS-IS for TRILL links. The
MTU-probe and MTU-ack PDUs provide a means of testing link MTU. MTU-probe and MTU-ack PDUs provide a means of testing link MTU.
skipping to change at page 4, line 43 skipping to change at page 4, line 43
The term "Hello" or "Hello PDU" in this document, when not further The term "Hello" or "Hello PDU" in this document, when not further
qualified, includes the TRILL IIH PDU, the LAN IIH PDU and the P2P qualified, includes the TRILL IIH PDU, the LAN IIH PDU and the P2P
IIH PDU. IIH PDU.
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. PDU, TLV and sub-TLV Enhancements to IS-IS 2. PDU, TLV and sub-TLV Enhancements to IS-IS
In this section we describe the enhancements that are being proposed In this section we specify the enhancements for the PDUs, TLVs and
for the PDUs, TLVs and sub-TLVs as needed by Layer-2 technologies. sub-TLVs as needed 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 141 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-Id | (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) |
skipping to change at page 5, line 34 skipping to change at page 5, line 34
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 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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the MAC addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESV: Must be sent as zero on transmission and is ignored on o RESV: Must be sent as zero on transmission and is 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. It
MUST contain only unicast addresses. MUST contain only unicast addresses.
2.2. The Group Address TLV 2.2. The Group Address TLV
The Group Address (GADDR) TLV is IS-IS TLV type 142 [TBD] and has the The Group Address (GADDR) TLV is IS-IS TLV type 142 [TBD] and has the
following format: following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type=GADDRTLV | (1 byte)
|Type = GADDRTLV| Length | sub-TLVs | +-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLVs (variable bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to GADDR-TLV 142 [TBD]. o Type: TLV Type, set to GADDR-TLV 142 [TBD].
o Length: Total number of bytes contained in the value field, which o Length: Total number of bytes contained in the value field, which
includes the length of the sub-TLVs carried in this TLV. includes the length of the sub-TLVs carried in this TLV.
o sub-TLVs: The Group Address TLV value contains sub-TLVs formatted o sub-TLVs: The Group Address TLV value contains sub-TLVs formatted
as described in [RFC5305]. The sub-TLVs for this TLV are as described in [RFC5305]. The sub-TLVs for this TLV are
specified in the following subsections. specified in the following subsections.
The GADDR TLV is carried within Multicast Group Level 1 link state The GADDR TLV is carried only within a Multicast Group Level 1 link
PDU. state PDU.
2.2.1. The Group MAC Address sub-TLV 2.2.1. The Group MAC Address sub-TLV
The Group MAC Address (GMAC-ADDR) sub-TLV is IS-IS sub-TLV type 1 The Group MAC Address (GMAC-ADDR) sub-TLV is IS-IS sub-TLV type 1
within the GADDR TLV and has the following format: within the GADDR TLV and has the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type=GMAC-ADDR| (1 byte) | Type=GMAC-ADDR| (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname-Id | (2 bytes) | Topology-Id/ Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Confidence | (1 byte) | Confidence | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESV | VLAN-ID | (2 bytes) | RESV | VLAN-ID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Num Group Recs | (1 byte) |Num Group Recs | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (1) | | GROUP RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
skipping to change at page 7, line 29 skipping to change at page 7, line 32
o Type: sub-TLV Type, set to 1 (GMAC-ADDR) of length 1 byte. o Type: sub-TLV Type, set to 1 (GMAC-ADDR) of length 1 byte.
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the MAC addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESERVED: Must be sent as zero on transmission and is ignored on o RESERVED: Must be sent as zero on transmission and is 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 Number of Group Records: This is of length 1 byte and lists the o Number of Group Records: This is of length 1 byte and lists the
number of group records in this TLV. number of group records in this TLV.
o Group Record: Each group record has a reserved space and is o Group Record: Each group record has a one byte reserved space and
followed by the number of sources, each of length 1 byte. It then the next byte carries the number of sources. It then has a 48-bit
has a 48-bit multicast Group Address followed by 48-bit source MAC multicast Group Address followed by 48-bit source MAC addresses.
addresses. An address being a group multicast address or unicast
source address can be checked using the multicast bit in the
address. If the number of sources do not fit in a single sub-TLV,
it is permitted to have the same group address repeated with
different source addresses in another sub-TLV of another instance
of the Group Address TLV.
The GMAC-ADDR sub-TLV is carried within the GADDR TLV and MUST be An address being a group multicast address or unicast source
address can be checked using the multicast bit in the address. If
the number of sources do not fit in a single sub-TLV, it is
permitted to have the same group address repeated with different
source addresses in another sub-TLV of another instance of the
Group Address TLV.
The GMAC-ADDR sub-TLV is carried only within a GADDR TLV and MUST be
carried in a standard Level 1 link state MGROUP PDU. carried in a standard Level 1 link state MGROUP PDU.
2.2.2. The Group IP Address sub-TLV 2.2.2. The Group IP Address sub-TLV
The Group IP Address (GIP-ADDR) sub-TLV is IS-IS TLV type 2 and has The Group IP Address (GIP-ADDR) sub-TLV IS-IS sub-TLV type 2 within
the following format: the GADDR TLV and has the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type=GIP-ADDR | | Type=GIP-ADDR |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+
| Confidence | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname-Id | (2 bytes) | Topology-Id/ Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Confidence | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESV | VLAN-ID | (2 bytes) | RESV | VLAN-ID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Num Group Recs | (1 byte) |Num Group Recs | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (1) | | GROUP RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (N) | | GROUP RECORDS (N) |
skipping to change at page 9, line 15 skipping to change at page 9, line 30
o Length: Total number of bytes contained in the value field of the o Length: Total number of bytes contained in the value field of the
TLV. TLV.
o Confidence: This carries an 8-bit quantity indicating the o Confidence: This carries an 8-bit quantity indicating the
confidence level in the IP addresses being transported. Whether confidence level in the IP 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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESERVED: Must be sent as zero on transmission and is ignored on o RESERVED: Must be sent as zero on transmission and is 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 addresses in this TLV, or the value zero if no VLAN
VLAN is specified. is specified.
o Number of Group Records: This is of length 1 byte and lists the o Number of Group Records: This is of length 1 byte and lists the
number of group records in this TLV. number of group records in this TLV.
o Group Record: Each group record has a reserved space and is o Group Record: Each group record has a one byte reserved space and
followed by the number of sources, each of length 1 byte. It is the next byte carries the number of sources. It is followed by a
followed by a 32-bit IPv4 Group Address followed by 32-bit source 32-bit IPv4 Group Address followed by 32-bit source IPv4
IPv4 addresses. If the number of sources do not fit in a single addresses. If the number of sources do not fit in a single sub-
sub-TLV, it is permitted to have the same group address repeated TLV, it is permitted to have the same group address repeated with
with different source addresses repeated in another sub-TLV of different source addresses repeated in another sub-TLV of another
another instance of the Group Address TLV. instance of the Group Address TLV.
The GIP-ADDR TLV is carried within the GADDR TLV and MUST be carried The GIP-ADDR sub-TLV is carried only within a GADDR TLV and MUST be
in a standard Level 1 link state MGROUP PDU. carried in a standard Level 1 link state MGROUP PDU.
2.2.3. The Group IPv6 Address sub-TLV 2.2.3. The Group IPv6 Address sub-TLV
The Group IPv6 Address (GIPV6-ADDR) TLV is IS-IS sub-TLV type 3 and The Group IPv6 Address (GIPV6-ADDR) TLV is IS-IS sub-TLV type 3 and
has the following format: has the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=GIPv6-ADDR| |Type=GIPv6-ADDR|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname-Id | (2 bytes) | Topology-Id/ Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Confidence | (1 byte) | Confidence | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESV | VLAN-ID | (2 bytes) | RESV | VLAN-ID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Num Group Recs | (1 byte) |Num Group Recs | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (1) | | GROUP RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
skipping to change at page 10, line 51 skipping to change at page 11, line 11
o Type: sub-TLV Type, set to 3 (GIPV6-ADDR). o Type: sub-TLV Type, set to 3 (GIPV6-ADDR).
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o Confidence: This carries an 8-bit quantity indicating the o Confidence: This carries an 8-bit quantity indicating the
confidence level in the IPv6 addresses being transported. Whether confidence level in the IPv6 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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESERVED: Must be sent as zero on transmission and is ignored on o RESERVED: Must be sent as zero on transmission and is 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 addresses in this TLV, or the value zero if no VLAN
VLAN is specified. is specified.
o Number of Group Records: This of length 1 byte and lists the o Number of Group Records: This of length 1 byte and lists the
number of group records in this TLV. number of group records in this TLV.
o Group Record: Each group record has a reserved space and is o Group Record: Each group record has a one byte reserved space and
followed by the number of sources, each of length 1 byte. It is the next byte carries the number of sources. It is followed by a
followed by a 128-bit multicast IPv6 Group Address followed by 128-bit multicast IPv6 Group Address followed by 128-bit source
128-bit source IPv6 addresses. If the number of sources do not IPv6 addresses. If the number of sources do not fit in a single
fit in a single sub-TLV, it is permitted to have the same group sub-TLV, it is permitted to have the same group address repeated
address repeated with different source addresses repeated in with different source addresses repeated in another sub-TLV in
another sub-TLV in another instance of the Group Address TLV. another instance of the Group Address TLV.
The GIPV6-ADDR sub-TLV is carried within the GADDR TLV and MUST be The GIPV6-ADDR sub-TLV is carried only within a GADDR TLV and MUST be
carried in a standard Level 1 link state MGROUP PDU. carried in a standard Level 1 link state MGROUP PDU.
2.2.4. The SPBV MAC Address sub-TLV 2.2.4. The SPBV MAC Address sub-TLV
The SPBV MAC Address (SPBV-MAC-ADDR) TLV is IS-IS sub-TLV type 4 and The SPBV MAC Address (SPBV-MAC-ADDR) TLV is IS-IS sub-TLV type 4 and
has the following format: has the following format:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|# MAC Addresses| reserved |SR | SPVID | | Type=SPBV-ADDR| (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|T|R| Reserved | MAC Address (6 bytes) | | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | T|R| Reserved | |R|R|S|R| SPVID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MAC Address (6 bytes) | |T|R| Reserved | MAC 1 Address | (1+6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | T|R| Reserved | | | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | MAC N Address | (1+6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 4 (SPBV-MAC-ADDR). o Type: sub-TLV Type, set to 4 (SPBV-MAC-ADDR).
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field. The
number of MAC address associated with the SPVID is computed by
o Number of MAC address (1 byte): Number of MAC address must be set. (Length - 2)/7.
It is the number of addresses associated with the SPVID that
follow. This is the number of addresses associated with this
SPVID.
o SR bits (2-bits) The SR bits are the service requirement parameter o SR bits (2-bits) The SR bits are the service requirement parameter
from MMRP. The service requirement parameters have the value 0 from MMRP. The service requirement parameters have the value 0
(Forward all Groups) (and 1 (Forward All Unregistered Groups) (Forward all Groups) and 1 (Forward All Unregistered Groups)
defined. However this attribute may also be missing. So the SR defined. However this attribute may also be missing. So the SR
bits are defined as 0 not declared, 1 Forward all Groups and 2 bits are defined as 0 not declared, 1 Forward all Groups and 2
Forward All Unregistered Groups. Forward All Unregistered Groups. These bits have a two Reserved
bits set before them.
o SPVID (12-bits) The SPVID and by association Base VID and the ECT- o SPVID (12-bits) The SPVID and by association Base VID and the ECT-
ALGORITHM and SPT Set that the MAC addresses defined below will ALGORITHM and SPT Set that the MAC addresses defined below will
use. If the SPVID is not allocated the SPVID Value is 0. Note use. If the SPVID is not allocated the SPVID Value is 0. Note
that if the ECT-Algorithm in use is Spanning Tree Algorithm this that if the ECT-Algorithm in use is Spanning Tree Algorithm this
value should be populated with the Base VID and the MAC can be value should be populated with the Base VID and the MAC can be
populated. populated.
o T Bit (1-bit) This is the Transmit allowed Bit for the following o T Bit (1-bit) This is the Transmit allowed Bit for the following
group MAC address. This is an indication that SPBV Group MAC group MAC address. This is an indication that SPBV Group MAC
skipping to change at page 12, line 46 skipping to change at page 13, line 18
this Group MAC Address with the T bit set) and installed when the this Group MAC Address with the T bit set) and installed when the
bridge computing the trees lies on the corresponding shortest path bridge computing the trees lies on the corresponding shortest path
for this ECT-ALGORITHM between this receiver and any transmitter for this ECT-ALGORITHM between this receiver and any transmitter
on this Group MAC Address. An entry that does not have this bit on this Group MAC Address. An entry that does not have this bit
set for a Group MAC Address is prevented from receiving on this set for a Group MAC Address is prevented from receiving on this
Group MAC Address because transit bridges will not install Group MAC Address because transit bridges will not install
multicast forwarding state towards it in their FDBs or the traffic multicast forwarding state towards it in their FDBs or the traffic
is explicitly filtered. is explicitly filtered.
o MAC Address (48-bits) The MAC is the address is either a group o MAC Address (48-bits) The MAC is the address is either a group
address or an individual address. When the MAC address is a group address or an individual address. Individual addresses are
address declares this bridge as part of the multicast interest for optional and normal MAC learning can be used. When the MAC
this destination MAC address. Multicast trees can be efficiently address is a group address it declares this bridge as part of the
constructed for destination by populating multicast FDB entries multicast interest for this destination MAC address. Multicast
for the subset of the shortest path tree that connects the bridges trees can be efficiently constructed for destination by populating
supporting the multicast address. This replaces the function of multicast FDB entries for the subset of the shortest path tree
MMRP for SPTs. The T and R bits above have meaning if this is a that connects the bridges supporting the multicast address. This
group address. Individual addresses are populated only as if the replaces the function of MMRP for SPTs. The T and R bits above
R bit was not set. have meaning if this is a group address. Individual addresses are
populated only as if the R bit was not set.
The SPBV-MAC-ADDR sub-TLV is carried within the GADDR TLV and MUST be The SPBV-MAC-ADDR sub-TLV is carried within the GADDR TLV and MUST be
carried in a standard Level 1 link state MGROUP PDU. carried only in a standard Level 1 link state MGROUP PDU.
2.3. Multi Topology aware Port Capability TLV 2.3. 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
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Type=MT PORTCAP| Length |O|R|R|R| Topology Identifier | |Type=MT PORTCAP| Length |O|R|R|R| Topology Identifier |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 13, line 42 skipping to change at page 14, line 16
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.
In TRILL this value is set to ZERO, however, in IEEE SPB and SPBB, In TRILL this value is set to ZERO, however, in IEEE SPB and SPBB,
it may be non-zero. it may be non-zero.
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
next sections. next sections.
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
within a IIH PDU. within a Hello PDU.
2.3.1. The Special VLANs and Flags sub-TLV 2.3.1. The Special VLANs and Flags sub-TLV
The Special VLANs and Flags (VLAN and Flags) sub-TLV MUST appear in a The Special VLANs and Flags (VLAN and Flags) sub-TLV MUST only appear
MT-PORT-CAP TLV. This is carried only once in every TRILL IIH PDU. in a MT-PORT-CAP TLV. This is carried exactly once in every TRILL
It has the following format: IIH PDU. It has the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=VLAN Flags| |Type=VLAN Flags| (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+------+-------------------------+ +--------------------------------+
| Port ID (2 bytes) | | Port ID | (2 bytes)
+----+----+----+----+------------+----------+------------+ +--------------------------------+
| AF | AC | VM | BY | Outer.VLAN | Reserved | Desig.VLAN | | Sender Nickname | (2 bytes)
+----+----+----+----+------------+----------+------------+ +--+--+--+--+--------------------+
0 1 2 3 4 - 15 16 - 19 20 - 31 |AF|AC|VM|BY| Outer.VLAN | (2 bytes)
+-----------+--------------------+
|Reserved | Desig.VLAN | (2 bytes)
+-----------+--------------------+
o Type: TLV Type, set to VLAN and Flags sub-TLV 1 [TBD]. o Type: TLV Type, set to VLAN and Flags sub-TLV 1 [TBD].
o Length: 6 - Number of bytes contained in the value field. o Length: 8 - Number of bytes contained in the value field.
o Port ID: An ID for the port on which the enclosing TRILL IIH PDU o Port ID: An ID for the port on which the enclosing TRILL IIH PDU
is being sent. The transmitting RBridge assigns this ID such that is being sent. The transmitting RBridge assigns this ID such that
each of its ports has an ID different from all of its other ports. each of its ports has an ID different from all of its other ports.
o The first and second bytes have a copy of the Outer VLAN ID o Sender nickname: If the sending intermediate system is holding any
nicknames, one MUST be included here. Otherwise, the field is set
to zero. This field is to support intelligent end stations that
determine the egress RBridge for unicast data through a directory
service or the like and need a nickname for their first hop to
insert as the ingress nickname to correctly format a TRILL
encapsulated data frame.
o The fifth and sixth bytes have a copy of the Outer VLAN ID
associated with the Hello frame when it was sent. The lower 4 associated with the Hello frame when it was sent. The lower 4
bits of the first byte give the upper ID bits of the VLAN ID and bits of the fifth byte give the upper ID bits of the VLAN ID and
the second byte gives the lower VLAN ID bits. the sixth byte gives the lower VLAN ID bits.
o The upper 4 bits of the first byte are flag bits as shown. The AF o The upper 4 bits of the fifth byte are flag bits as shown. The AF
bit, if one, indicates that the sending Intermediate System bit, if one, indicates that the sending Intermediate System
believes it is Appointed Forwarder for the VLAN and port on which believes it is Appointed Forwarder for the VLAN and port on which
the Hello was sent. The AC bit, if one, indicates that the the Hello was sent. The AC bit, if one, indicates that the
sending port is configured as an access port. The VM bit, if a sending port is configured as an access port. The VM bit, if a
one, indicates that the sending Intermediate System has detected one, indicates that the sending Intermediate System has detected
VLAN mapping within the link. The BY bit, if set, indicates VLAN mapping within the link. The BY bit, if set, indicates
bypass psuedonode. bypass psuedonode.
o The third and forth bytes give the Designated VLAN for the link. o The seventh and eighth bytes give the Designated VLAN for the
The lower 4 bits of the third byte give the upper ID bits of the link. The lower 4 bits of the seventh byte give the upper ID bits
Designated VLAN and the forth byte gives the lower VLAN ID bits. of the Designated VLAN and the eighth byte gives the lower VLAN ID
The upper 4 bits of the third byte are reserved and MUST be sent bits. The upper 4 bits of the seventh byte are reserved and MUST
as zero and ignored on receipt. be sent as zero and ignored on receipt.
The VLAN and Flags sub-TLV is carried within the MT-PORT-CAP TLV. It The VLAN and Flags sub-TLV is carried within the MT-PORT-CAP TLV. It
MUST be carried only once in a TRILL IIH PDU. It MUST NOT be carried MUST be carried exactly once in a TRILL IIH PDU. It MUST NOT be
within a LAN or a P2P IIH PDU. carried within a LAN or a P2P IIH PDU.
2.3.2. Enabled VLANs sub-TLV 2.3.2. Enabled VLANs sub-TLV
The Enabled VLAN sub-TLV specifies the VLANs enabled for end station The Enabled VLAN sub-TLV specifies the VLANs enabled for end station
service at the port on which the Hello was sent. service at the port on which the Hello was sent.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=EnabledVLAN| |Type=EnabledVLAN|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
skipping to change at page 15, line 24 skipping to change at page 16, line 4
o Type: sub-TLV Type, set to Enabled VLANs sub-TLV 2 [TBD]. o Type: sub-TLV Type, set to Enabled VLANs sub-TLV 2 [TBD].
o Length: variable, depending on contents described next. o Length: variable, depending on contents described next.
o The minimum size of the value is 3 bytes. The third and o The minimum size of the value is 3 bytes. The third and
subsequent bytes provide a bit map of enabled VLANs starting at subsequent bytes provide a bit map of enabled VLANs starting at
the VLAN ID indicated in the first two bytes. The lower order the VLAN ID indicated in the first two bytes. The lower order
four bits of the first byte give the upper bits of the starting four bits of the first byte give the upper bits of the starting
VLAN ID and the second byte gives the lower bits of that VLAN ID. VLAN ID and the second byte gives the lower bits of that VLAN ID.
The upper four bits of the first byte are reserved and MUST be The upper four bits of the first byte are reserved and MUST be
sent as zero and ignored on receipt. The highest order bit of the sent as zero and ignored on receipt. The highest order bit of the
third byte indicates the VLAN equal to the starting ID while the third byte indicates the VLAN equal to the starting ID while the
lowest order bit of the third byte indicated that ID plus 7. For lowest order bit of the third byte indicates that ID plus 7. For
example, VLANs 1 and 14 being enabled for end station service example, VLANs 1 and 14 being enabled for end station service
could be encoded in 4-bytes value 0x00 0x01 0x80 0x04 or, could be encoded in 4-bytes value 0x00 0x01 0x80 0x04 or,
alternatively, as 0x00 0x00 0x40 0x02. alternatively, as 0x00 0x00 0x40 0x02.
This sub-TLV may occur more than once in a Hello and a VLAN is This sub-TLV may occur more than once in a Hello and a VLAN is
enabled for end station service on the port where the Hellos was sent enabled for end station service on the port where the Hello was sent
if this is indicated by any occurrence in the Hello. For example, a if this is indicated by any occurrence in the Hello. For example, a
receiver could allocate a 512-byte buffer and, with appropriate receiver could allocate a 512-byte buffer and, with appropriate
shifting operations, OR in the enabled bits for each subTLV of this shifting operations, OR in the enabled bits for each subTLV of this
type it finds in a Hello to derive the complete bit map of these type it finds in a Hello to derive the complete bit map of these
VLANs. VLANs.
The Enabled VLAN sub-TLV is carried only within the MT-PORT-CAP TLV. The Enabled VLAN sub-TLV is carried only within the MT-PORT-CAP TLV.
If present, it MUST be carried in TRILL IIH PDU. It MUST NOT be If present, it MUST be carried in TRILL IIH PDU. It MUST NOT be
carried within a LAN IIH or a P2P IIH PDU. carried within a LAN IIH or a P2P IIH PDU.
skipping to change at page 16, line 15 skipping to change at page 16, line 42
o Type: sub-TLV Type, set to Appointed Forwarders sub-TLV 3 [TBD]. o Type: sub-TLV Type, set to Appointed Forwarders sub-TLV 3 [TBD].
o Length: The size of the value is 6*n bytes where there are n o Length: The size of the value is 6*n bytes where there are n
appointments. Each 6-byte part of the value is formatted as appointments. Each 6-byte part of the value is formatted as
follows: follows:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=App Frwrdr| |Type=App Frwrdr|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+----------------+-----+-----+---------+-----+----+---------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| byte 1 - 2 | byte 3 | byte 4 | byte 5 | byte 6 | | Appointment Information (1) | (6 bytes)
+----------------+-----+-----+---------+-----+----+---------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Appointee Nick | Res | Start VLAN ID | Res | End VLAN ID | | ................. |
+----------------+-----+-----+---------+-----+----+---------+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Appointment Information (N) | (6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o where each appointment information is of the form:
+---------------------------+
| Appointee Nick | (2 bytes)
+---------------------------+
| Res | Start VLAN ID | (2 bytes)
+---------------------------+
| Res | End VLAN ID | (2 bytes)
+---------------------------+
o The appointed forwarder Intermediate System is specified by its o The appointed forwarder Intermediate System is specified by its
nickname in the first two bytes. nickname in the first two bytes.
o The "Res" fields of 4 bits each are reserved and MUST be sent as o The "Res" fields of 4 bits each are reserved and MUST be sent as
zero and ignored on receipt. zero and ignored on receipt.
The VLAN range given is inclusive. To specify a single VLAN, that The VLAN range given is inclusive. To specify a single VLAN, that
VLAN ID appears as both the start and end VLAN. The Intermediate VLAN ID appears as both the start and end VLAN. The Intermediate
System whose nickname is given is appointed forwarder for those VLANs System whose nickname is given is appointed forwarder for those VLANs
skipping to change at page 17, line 14 skipping to change at page 17, line 52
2.3.4. Hop-by-Hop Options (HBHOPT) sub-TLV 2.3.4. Hop-by-Hop Options (HBHOPT) sub-TLV
By including this sub-TLV within one or more MT aware Port Capability By including this sub-TLV within one or more MT aware Port Capability
TLVs in its Hellos, an Intermediate System can advertise the Hop-by- TLVs in its Hellos, an Intermediate System can advertise the Hop-by-
Hop options it supports on the port through which it sends the Hello. Hop options it supports on the port through which it sends the Hello.
This sub-TLV may appear zero or more times within a MT aware Port This sub-TLV may appear zero or more times within a MT aware Port
Capability TLV. By default, in the absence of any HBHOPT sub-TLVs, Capability TLV. By default, in the absence of any HBHOPT sub-TLVs,
no Hop-by-Hop options are supported. no Hop-by-Hop options are supported.
There are two types of Hop-by-Hop option encoding within the TRILL There are two types of Hop-by-Hop option encodings within the TRILL
Header: bit options and TLV encoded options. Header: bit options and TLV encoded options.
The bit-encoded options supported are indicated by an HBHOPT sub-TLV The bit-encoded options supported are indicated by an HBHOPT sub-TLV
of length 3: an initial value byte of 0x00 followed by two bytes in of length 3: an initial value byte of 0x00 followed by two bytes in
which each bit indicates that the corresponding bit option is which each bit indicates that the corresponding bit option is
implemented; in those two bytes the top two bits (0xC000) are implemented; in those two bytes the top two bits (0xC000) are
critical option summary bits that all RBridges MUST understand; critical option summary bits that all RBridges MUST understand;
therefore support for these bits need not be advertised. Those two therefore support for these bits need not be advertised. Those two
bits are reserved in the HBHOPT sub-TLV and must be sent as zero are bits are reserved in the HBHOPT sub-TLV and must be sent as zero and
ignored on receipt. are ignored on receipt.
The implementation of a TLV encoded option is indicated by an HBHOPT The implementation of a TLV encoded option is indicated by an HBHOPT
sub-TLV whose value starts with a byte equal to the first byte of the sub-TLV whose value starts with a byte equal to the first byte of the
option. Such HBHOPT sub-TLVs may have additional value bytes further option. Such HBHOPT sub-TLVs may have additional value bytes further
indicating how the option is supported as specified with the option's indicating how the option is supported as specified with the option's
definition, for example a list of supported security algorithms. definition, for example a list of supported security algorithms.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type = HBHOPT | | Type = HBHOPT |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
skipping to change at page 17, line 46 skipping to change at page 18, line 35
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Option | (1 byte) | Option | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option dependent variable length information | | Option dependent variable length information |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to Hop-by-Hop sub-TLV 4 [TBD]. o Type: sub-TLV Type, set to Hop-by-Hop sub-TLV 4 [TBD].
o Length: variable, minimum 1. o Length: variable, minimum 1.
o Value: The first byte of the option followed by option dependent o Value: The first byte of the TLV encoded option which must be non-
information. zero, followed by option dependent information.
2.3.5. Base VLAN-Identifiers sub-TLV 2.3.5. Base VLAN-Identifiers sub-TLV
This sub-TLV is added to an IIH PDU to indicate the algorithms for This sub-TLV is added to an IIH PDU to indicate the algorithms for
the VIDs and the Base VIDs and VIDs or Backbone-VIDs (B-VIDs) are in the VIDs and the Base VIDs and VIDs or Backbone-VIDs (B-VIDs) that
use. This information should be the same on all bridges in the are in use. This information should be the same on all bridges in
topology identified by MT-PORT-CAP TLV it is being carried. the topology identified by MT-PORT-CAP TLV it is being carried.
Discrepancies between neighbours with respect to this sub-TLV are Discrepancies between neighbours with respect to this sub-TLV are
temporarily allowed but the Base-VID must agree and use a spanning temporarily allowed but the Base-VID must agree and use a spanning
tree algorithm. tree algorithm.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = B-VID | |Type = B-VID |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-------------------------------- +-+-+-+-+-+-+-+-+--------------------------------
| ECT - VID Tuple (1) (6 bytes) | | ECT - VID Tuple (1) (6 bytes) |
+-----------------------------------------------+ +-----------------------------------------------+
| ......................... | | ......................... |
+-----------------------------------------------+ +-----------------------------------------------+
| ECT - VID Tuples (N) (6 bytes) | | ECT - VID Tuples (N) (6 bytes) |
+-----------------------------------------------+ +-----------------------------------------------+
o Type: sub-TLV Type, set to Base-VALN-ID sub-TLV 5 [TBD]. o Type: sub-TLV Type, set to Base-VLAN-ID sub-TLV 5 [TBD].
o Length: The size of the value is ECT-VID Tuples*6 bytes. Each o Length: The size of the value is ECT-VID Tuples*6 bytes. Each
6-byte part of the ECT-VID tuple is formatted as follows: 6-byte part of the ECT-VID tuple is formatted as follows:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ECT - Algorithm (32 bits) | | ECT - Algorithm (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Base VID (12 bits) |U|M|RES| | Base VID (12 bits) |U|M|RES|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o ECT-ALGORITHM (4 bytes) The ECT-ALGORITHM is advertised when the o ECT-ALGORITHM (4 bytes) The ECT-ALGORITHM is advertised when the
bridge supports a given ECT-ALGORITHM (by OUI/Index) on a given bridge supports a given ECT-ALGORITHM (by OUI/Index) on a given
Base VID Base VID
o Base VID (12-bits) The Base-VID that is associate with the SPT o Base VID (12-bits) The Base-VID that is associated with the SPT
Set. Set.
o Use-Flag (1-bit) The Use-flag is set if this bridge, or any bridge o Use-Flag (1-bit) The Use-flag is set if this bridge, or any bridge
that this bridge sees is currently using this ECTALGORITHM and that this bridge sees is currently using this ECTALGORITHM and
Base VID. Base VID.
o M-Bit (1-bit) The M-bit indicates if this is SPBM or SPBV mode. o M-Bit (1-bit) The M-bit indicates if this is SPBM or SPBV mode.
The Base VLAN-Identifier sub-TLV is carried within the MT-PORT-CAP The Base VLAN-Identifier sub-TLV is carried within the MT-PORT-CAP
TLV and this is carried in a IIH PDU. TLV and this is carried in a IIH PDU.
2.3.6. SPB Digest sub-TLV 2.3.6. SPB Digest sub-TLV
This sub-TLV is added to an IIH PDU to indicate the algorithms for This sub-TLV is added to an IIH PDU to indicate the digest for
the VIDs and the Base VIDs and VIDs or Backbone-VIDs (B-VIDs) are in Multiple spanning tree configuration Digests (MCID) and the IS-IS
use. This information should be the same on all bridges in the agreement Digest. This information should be the same on all bridges
topology identified by MT-PORT-CAP TLV it is being carried. in the topology identified by MT-PORT-CAP TLV it is being carried.
Discrepancies between neighbours with respect to this sub-TLV are These digest indicate when the configuration and the topology are
temporarily allowed but the Base-VID must agree and use a spanning synchronized and are used to control the updating of forwarding
tree algorithm. information. The MCID is controlled solely by configuration and is a
digest of the allocated VIDs to various protocols. Two MCIDs are
carried to allow transitions when the configuration changes are non-
critical. During the propagation of LSPs the agreement digest will
vary between neighbors until the LSPs are common. During that period
switches or bridges running SPB will not allow multicast forwarding
between neighbors that have differing digests. Discrepancies between
neighbours with respect to this sub-TLV are temporarily allowed but
the Base-VID must agree and use a spanning tree algorithm.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type =SPBDigest| |Type =SPBDigest|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MCID (50 Bytes) | | MCID (50 Bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Aux MCID (50 Bytes) | | Aux MCID (50 Bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Agreement Digest (32 Bytes) | | Agreement Digest (32 Bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|RES | A| D| |RES | A | D|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to SPB Digest sub-TLV 6 [TBD]. o Type: sub-TLV Type, set to SPB Digest sub-TLV 6 [TBD].
o Length: The size of the value defined below. o Length: The size of the value defined below.
o MCID (50-bytes) The complete MCID defined in IEEE 802.1Q which o MCID (50-bytes) The complete MCID defined in IEEE 802.1Q which
identifies an SPT Region. identifies an SPT Region.
o Aux MCID (50-bytes) The complete MCID defined in IEEE 802.1Q which o Aux MCID (50-bytes) The complete MCID defined in IEEE 802.1Q which
skipping to change at page 20, line 35 skipping to change at page 21, line 33
o Type: sub-TLV Type, set to Site Identifier sub-TLV 250 [TBD]. o Type: sub-TLV Type, set to Site Identifier sub-TLV 250 [TBD].
o Length: The size of the value. o Length: The size of the value.
o System Id: The system-id of the site. o System Id: The system-id of the site.
o Cluster Id: The cluster-id within the site. o Cluster Id: The cluster-id within the site.
o Flags: Indicates unicast reachability. o Flags: Indicates unicast reachability.
The Site Capability sub-TLV is carried within the MT-PORT-CAP TLV and
this is carried in a Hello PDU.
2.3.8. Site Group IPv4 sub-TLV 2.3.8. Site Group IPv4 sub-TLV
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=SiteGrpIP | |Type=SiteGrpIP |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address (4 bytes) | | IPv4 address (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| .................. | | .................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address (4 bytes) | | IPv4 address (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to Site Group IP sub-TLV 251 [TBD]. o Type: sub-TLV Type, set to Site Group IP sub-TLV 251 [TBD].
o Length: The size of the value. o Length: The size of the value.
o Value: The list of IPv4 addresses used by the site. o Value: The list of IPv4 addresses used by the site.
The Site Group IP sub-TLV is carried within the MT-PORT-CAP TLV and
this is carried in a Hello PDU.
2.3.9. Site Group IPv6 sub-TLV 2.3.9. Site Group IPv6 sub-TLV
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=SiteGrpIPv6| |Type=SiteGrpIPv6|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 address (16 bytes) | | IPv6 address (16 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| .................. | | .................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 address (16 bytes) | | IPv6 address (16 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to Site Group IPv6 sub-TLV 252 [TBD]. o Type: sub-TLV Type, set to Site Group IPv6 sub-TLV 252 [TBD].
o Length: The size of the value. o Length: The size of the value.
o Value: The list of IPv6 addresses used by the site. o Value: The list of IPv6 addresses used by the site.
The Site Group IPv6 sub-TLV is carried within the MT-PORT-CAP TLV and
this is carried in a Hello PDU.
2.3.10. Adjacency Server IPv4 sub-TLV 2.3.10. Adjacency Server IPv4 sub-TLV
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = ASIPv4 | |Type = ASIPv4 |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address (4 bytes) | | IPv4 address (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv4 address (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags(1 byte)| | Flags(1 byte)|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to Adjacency Server IP sub-TLV 253 [TBD]. o Type: sub-TLV Type, set to Adjacency Server IP sub-TLV 253 [TBD].
o Length: The size of the value. o Length: The size of the value.
o Value: The list of IPv4 addresses used by the site. o Value: The list of IPv4 addresses used by the site.
o Flags: Indicates unicast reachability. o Flags: Indicates unicast reachability.
The Adjacency Server IP sub-TLV is carried within the MT-PORT-CAP TLV
and this is carried in a Hello PDU.
2.3.11. Adjacency Server IPv6 sub-TLV 2.3.11. Adjacency Server IPv6 sub-TLV
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = ASIPv6 | |Type = ASIPv6 |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 address (16 bytes) | | IPv6 address (16 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IPv6 address (16 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags(1 byte)| | Flags(1 byte)|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to Adjacency Server IPv6 sub-TLV 254 o Type: sub-TLV Type, set to Adjacency Server IPv6 sub-TLV 254
[TBD]. [TBD].
o Length: The size of the value. o Length: The size of the value.
o Value: The list of IPv6 addresses used by the site. o Value: The list of IPv6 addresses used by the site.
o Flags: Indicates unicast reachability. o Flags: Indicates unicast reachability.
The Adjacency Server IPv6 sub-TLV is carried within the MT-PORT-CAP
TLV and this is carried in a Hello PDU.
2.4. Sub-TLVs for the Router Capability TLV 2.4. Sub-TLVs for the Router Capability TLV
The Router Capability TLV is an optional TLV [RFC 4971] that may be The Router Capability TLV is an optional TLV [RFC 4971] that may be
generated by the originating Intermediate System. We specify these generated by the originating Intermediate System. We specify these
additional sub-TLVs that can be carried in it. These sub-TLVs additional sub-TLVs that can be carried in it. These sub-TLVs
announce the capabilities of the Intermediate System for the entire announce the capabilities of the Intermediate System to the entire
IS-IS routing domain. IS-IS routing domain.
2.4.1. The TRILL Version sub-TLV 2.4.1. The TRILL Version sub-TLV
The TRILL Version (TRILL-VER) sub-TLV indicates support of TRILL The TRILL Version (TRILL-VER) sub-TLV indicates support of TRILL
Versions. The device announces the maximum version of TRILL, it is Versions. The device announces the maximum version of TRILL, it is
capable of supporting, including lower versions. In the event, this capable of supporting, including lower versions. In the event, this
sub-TLV is missing, this implies that the node can only support the sub-TLV is missing, this implies that the node can only support the
base version of the protocol. base version of the protocol.
0 1 2 3 0 1 2 3
skipping to change at page 23, line 4 skipping to change at page 24, line 12
The TRILL Version (TRILL-VER) sub-TLV indicates support of TRILL The TRILL Version (TRILL-VER) sub-TLV indicates support of TRILL
Versions. The device announces the maximum version of TRILL, it is Versions. The device announces the maximum version of TRILL, it is
capable of supporting, including lower versions. In the event, this capable of supporting, including lower versions. In the event, this
sub-TLV is missing, this implies that the node can only support the sub-TLV is missing, this implies that the node can only support the
base version of the protocol. base version of the protocol.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Max-version | | Type | Length | Reserved | Max-version |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 5 (TRILL-VER). o Type: sub-TLV Type, set to 5 (TRILL-VER).
o Length: 2 - Total number of bytes contained in the vlaue. o Length: 2 - Total number of bytes contained in the value.
o Reserved: Set to zero on transmission and ignored on receipt. o Reserved: Set to zero on transmission and ignored on receipt.
o Max-version: Set to application dependent values. o Max-version: Set to application dependent values.
2.4.2. The Nickname sub-TLV 2.4.2. The Nickname sub-TLV
The Nickname (NICKNAME) sub-TLV carries information about the The Nickname (NICKNAME) sub-TLV carries information about the
nicknames of the advertising device, along with information about its nicknames of the advertising device, along with information about its
priority to hold those nicknames. The Nickname sub-TLV MUST be priority to hold those nicknames. The Nickname sub-TLV MUST be
skipping to change at page 23, line 42 skipping to change at page 25, line 4
where each nickname record is of the form: where each nickname record is of the form:
+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+
|Nickname Priority| (1 byte) |Nickname Priority| (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tree Root Priority | (2 byte) | Tree Root Priority | (2 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nickname | (2 bytes) | Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 6 (NICKNAME).
o Type: TLV Type, set to 6 (NICKNAME).
o Length: 5*N, where N is the number of nickname records present. o Length: 5*N, where N is the number of nickname records present.
o Nickname Priority: Priority with which this node holds this o Nickname Priority: This is an unsigned 8-bit integer that gives
nickname. the priority with which this node holds this nickname.
o Tree Root Priority: This is an unsigned 16-bit integer that gives o Tree Root Priority: This is an unsigned 16-bit integer that gives
the value of the priority with which this nickname wants to be the the value of the priority with which this nickname wants to be the
highest priority root node in the Layer-2 domain. highest priority root node in the Layer-2 domain.
o Nickname: This is an unsigned 16-bit integer that gives device o Nickname: This is an unsigned 16-bit integer that gives device
identifier or alias. identifier or alias.
Each nickname record consists of a one-byte priority set to Each nickname record consists of a one-byte priority set to
application dependent values, two bytes of tree root priority and two application dependent values, two bytes of tree root priority and two
skipping to change at page 24, line 24 skipping to change at page 25, line 33
The Trees sub-TLV MUST occur only once and is carried within the The Trees sub-TLV MUST occur only once and is carried within the
Router CAPABILITY TLV in a level-1 non-pseudo-node LSP generated by Router CAPABILITY TLV in a level-1 non-pseudo-node LSP generated by
the originating IS. Each device announces three numbers: the number the originating IS. Each device announces three numbers: the number
of trees it dictates that all other Intermediate Systems in the of trees it dictates that all other Intermediate Systems in the
campus compute if it is the highest priority tree root; the maximum campus compute if it is the highest priority tree root; the maximum
number of trees it is able to compute; and the number of distribution number of trees it is able to compute; and the number of distribution
trees it wishes to be able to use in forwarding multi-destination trees it wishes to be able to use in forwarding multi-destination
traffic. traffic.
Once a node receives a new LSP, it runs an election algorithm to All nodes run the same algorithm as described in [RBRIDGES] and the
ensure if this node is reachable. On the reachable set of the nodes, elected highest priority tree root dictates the number of
independently of the other nodes in the network, it determine if it distribution tree roots to be used in the network domain and can
has the nickname that has the highest priority root. The node that additionally list those roots in the tree roots identifier sub-TLV.
announced the numerically highest priority nickname to become a tree
root is elected to be the highest priority tree root. If two devices
advertise the same priority, the device with the higher system ID has
the higher priority to be a tree root. If system IDs also tie, the
device with the highest nickname value, considered as an unsigned
integer, wins. The elected highest priority tree root dictates the
number of distribution tree roots to be used in the network domain
and can list those roots in the tree roots identifier sub-TLV.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = TREE | |Type = TREE |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Number of trees to compute | (2 byte) | Number of trees to compute | (2 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Maximum trees able to compute | (2 byte) | Maximum trees able to compute | (2 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 25, line 20 skipping to change at page 26, line 21
this device becomes the highest priority tree root in the domain. this device becomes the highest priority tree root in the domain.
o Maximum number of trees able to compute: This is an unsigned 16- o Maximum number of trees able to compute: This is an unsigned 16-
bit integer that give the maximum number of threes that the bit integer that give the maximum number of threes that the
originating IS is able to compute for the campus. originating IS is able to compute for the campus.
o Number of trees to use: This is an unsigned 16-bit integer that o Number of trees to use: This is an unsigned 16-bit integer that
gives the number of distribution trees the originating IS wishes gives the number of distribution trees the originating IS wishes
to be able to use. to be able to use.
2.4.4. The Tree Root Identifiers Sub-TLV 2.4.4. The Tree Identifiers Sub-TLV
The tree root identifiers sub-TLV is an ordered list of nicknames. The tree identifiers sub-TLV is an ordered list of nicknames. When
When originated by the Intermediate System which is the highest originated by the Intermediate System which is the highest priority
priority tree root, this list is the tree roots for which other tree root, this list is the trees which the other Intermediate
Intermediate Systems are required to compute trees. If this Systems are required to compute. If this information is spread
information is spread across multiple sub-TLVs, the starting tree across multiple sub-TLVs, the starting tree number is used to figure
root identifier is used to figure out the ordered list. It is out the ordered list. It is carried within the Router CAPABILITY TLV
carried within the Router CAPABILITY TLV in a level-1 non-pseudo-node in a level-1 non-pseudo-node LSP and is given as:
LSP and is given as:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=TREE-RT-ID| |Type=TREE-RT-ID|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Starting Tree Root Identifier| (2 bytes) |Starting Tree Number | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nickname (K-th root) | (2 bytes) | Nickname (K-th root) | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nickname (K+1 - th root) | (2 bytes) | Nickname (K+1 - th root) | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nickname (...) | | Nickname (...) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 8 (TREE-RT-IDs). o Type: sub-TLV Type, set to 8 (TREE-RT-IDs).
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o Starting Tree Number: This identifies the starting tree number of o Starting Tree Number: This identifies the starting tree number of
the nicknames which are roots for the domain. This is set to 1 the nicknames that are trees for the domain. This is set to 1 for
for the first sub-TLV. The starting value and the length field the first sub-TLV. The starting value and the length field gives
gives the number of nicknames being carried in the sub-TLV. In the number of nicknames being carried in the sub-TLV. In the
the event a tree identifier can be computed from two such sub-TLVs event a tree identifier can be computed from two such sub-TLVs and
and are different, then it is assumed that this is a transient are different, then it is assumed that this is a transient
condition which will get cleared. condition that will get cleared.
o Nickname: The nickname on which this tree is based. o Nickname: The nickname on which this tree is based.
2.4.5. The Trees Used Identifiers Sub-TLV 2.4.5. The Trees Used Identifiers Sub-TLV
This sub-TLV has the same structure as the Tree Roots Identifier sub- This sub-TLV has the same structure as the Tree Identifiers sub-TLV
TLV specified in the above section. The only difference is that its specified in the above section. The only difference is that its sub-
sub-TLV type is set to 9 TBD (TREE-USE-IDs) and the roots listed are TLV type is set to 9 TBD (TREE-USE-IDs) and the trees listed are only
only those that the originating intermediate systems wishes to use. those that the originating intermediate systems wishes to use.
2.4.6. Interested VLANs and Spanning Tree Roots sub-TLV 2.4.6. Interested VLANs and Spanning Tree Roots sub-TLV
The value of this sub-TLV consists of a VLAN range, flags, and a The value of this sub-TLV consists of a VLAN range, flags, and a
variable length list of spanning tree root bridge IDs. This sub-TLV variable length list of spanning tree root bridge IDs. This sub-TLV
may appear zero, one, or many times. The union of the VLAN ranges in may appear zero, one, or many times. The union of the VLAN ranges in
all occurrences MUST be precisely the set of VLANs for which the all occurrences MUST be precisely the set of VLANs for which the
originating Intermediate System is appointed forwarder on at least originating Intermediate System is appointed forwarder on at least
one port and the VLAN ranges in multiple VLANs sub-TLVs for an one port and the VLAN ranges in multiple VLANs sub-TLVs for an
Intermediate System MUST NOT overlap. That is, the intersection of Intermediate System MUST NOT overlap. That is, the intersection of
the VLAN ranges for any pair of these sub-TLVs originated by an the VLAN ranges for any pair of these sub-TLVs originated by an
Intermediate System must be null. The value length is 10 + 6*n where Intermediate System must be null. The value length is 10 + 6*n where
n is the number of root bridge IDs. The TLV layout is as follows: n is the number of root bridge IDs. The TLV layout is as follows:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = INT-VLAN| |Type = INT-VLAN|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+---------------+-----+ +---------------+-----+
| Nickname-Id | (2 bytes) | Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Interested VLANS | (8 bytes) | Interested VLANS | (8 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Root Bridges | (6*n bytes) | Root Bridges | (6*n bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 10 (INT-VLAN). o Type: sub-TLV Type, set to 10 (INT-VLAN).
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o Nickname Id: If this is set to 0, then it applies to all device- o Nickname: If this is set to 0, then it applies to all device-ids
ids generated by the node. It may alternatively be set to a generated by the node. It may alternatively be set to a specific
specific nickname-id, in the event a node wants to segregate nickname, in the event a node wants to segregate traffic using
traffic using multiple device-ids. multiple device-ids.
o Interested VLANS: In the Interested VLANs, as shown below, the M4 o Interested VLANS: In the Interested VLANs, as shown below, the M4
bit indicates that there is an IPv4 multicast router on a link for bit indicates that there is an IPv4 multicast router on a link for
which the originating Intermediate System is appointed forwarder which the originating Intermediate System is appointed forwarder
for every VLAN in the indicated range. The M6 bit indicates the for every VLAN in the indicated range. The M6 bit indicates the
same for an IPv6 multicast router. The R and Reserved bits MUST same for an IPv6 multicast router. The R and Reserved bits MUST
be sent as zero and are ignored on receipt. The VLAN start and be sent as zero and are ignored on receipt. The VLAN start and
end IDs are inclusive. A range of one VLAN ID is indicated by end IDs are inclusive. A range of one VLAN ID is indicated by
setting them both to that VLAN ID value. The Appointed Forwarder setting them both to that VLAN ID value. The Appointed Forwarder
Status Lost Counter is also included here. It is a count of how Status Lost Counter is also included here. It is a count of how
skipping to change at page 28, line 4 skipping to change at page 29, line 4
multiple sub-TLVs each indicating only VLANs with the same M4, M6, multiple sub-TLVs each indicating only VLANs with the same M4, M6,
and Appointed Forwarder Status Lost Counter values. If there are any and Appointed Forwarder Status Lost Counter values. If there are any
two VLANs in the range indicated for which the set of root bridge IDs two VLANs in the range indicated for which the set of root bridge IDs
see on all links for which the Intermediate System is appointed see on all links for which the Intermediate System is appointed
forwarder for the VLAN are not the same, the sub-TLV is incorrect and forwarder for the VLAN are not the same, the sub-TLV is incorrect and
must be split into multiple subTLVs each indicating only VLANs with must be split into multiple subTLVs each indicating only VLANs with
the same set of DRB seen root bridge IDs. It is always safe to use the same set of DRB seen root bridge IDs. It is always safe to use
sub-TLVs with a "range" of one VLAN ID but this may be too verbose. sub-TLVs with a "range" of one VLAN ID but this may be too verbose.
Wherever possible, an implementation SHOULD advertise the update to a Wherever possible, an implementation SHOULD advertise the update to a
interested vlan and spanning trees sub-TLV in the same LSP fragment interested vlan and spanning tree roots sub-TLV in the same LSP
as the advertisement that it replaces. Where this is not possible, fragment as the advertisement that it replaces. Where this is not
the two affected LSP fragments should be flooded as an atomic action. possible, the two affected LSP fragments should be flooded as an
atomic action.
Systems that receive an update to an existing interested vlan and Systems that receive an update to an existing interested vlan and
spanning sub-TLV can minimize the potential disruption associated spanning tree roots sub-TLV can minimize the potential disruption
with the update by employing a holddown time prior to processing the associated with the update by employing a holddown time prior to
update so as to allow for the receipt of multiple LSP fragments processing the update so as to allow for the receipt of multiple LSP
associated with the same update prior to beginning processing. fragments associated with the same update prior to beginning
processing.
Where a receiving system has two copies of a interested vlan and Where a receiving system has two copies of a interested vlan and
spanning sub-TLV from the same system that have different settings spanning tree roots sub-TLV from the same system that have different
for a given vlan, the procedure used to choose which copy shall be settings for a given vlan, the procedure used to choose which copy
used is undefined (refer to RFC 4971, Section 3). shall be used is undefined (refer to RFC 4971, Section 3).
This sub-TLV is carried within the CAPABILITY TLV in a level-1 non- This sub-TLV is carried within the CAPABILITY TLV in a level-1 non-
pseudo-node LSP. pseudo-node LSP.
2.4.7. The VLAN Group sub-TLV 2.4.7. The VLAN Group sub-TLV
The VLAN Group sub-TLV consists of two or more 16-bit fields each of The VLAN Group sub-TLV consists of two or more 16-bit fields each of
which has a VLAN ID in the low order 12 bits. The top 4 bits MUST be which has a VLAN ID in the low order 12 bits. The top 4 bits MUST be
sent as zero and ignored on receipt. The first such VLAN ID is the sent as zero and ignored on receipt. The first such VLAN ID is the
primary, or may be zero if there is no primary. It is carried within primary, or may be zero if there is no primary. It is carried within
the CAPABILITY TLV in a level-1 non-pseudo-node LSP and is structured the CAPABILITY TLV in a level-1 non-pseudo-node LSP and is structured
as follows: as follows:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=VLAN-GROUP| |Type=VLAN-GROUP|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Primary VLAN ID (2 bytes) | Secondary VLAN ID (2 bytes) | | Primary VLAN ID (2 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ........ Possibly more Secondary VLAN IDs .......... | | Secondary VLAN ID (2 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| more Secondary VLAN IDs ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to 11 (VLAN-GROUPs). o Type: TLV Type, set to 11 (VLAN-GROUPs).
o Length: Total number of bytes contained in the value field, 4 + o Length: Total number of bytes contained in the value field, 4 +
2*n, where n may be 0. 2*n, where n may be 0.
o Primary VLAN-ID: This identifies the primary VLAN-ID. o Primary VLAN-ID: This identifies the primary VLAN-ID.
o Secondary VLAN-ID: This identifies the secondary VLAN-ID, address o Secondary VLAN-ID: This identifies the secondary VLAN-ID, address
learning is shared at the Intermediate System that announces this learning is shared at the Intermediate System that announces this
sub-TLV. sub-TLV.
This sub-TLV may appear zero, one, or multiple times. This sub-TLV may appear zero, one, or multiple times. It should be
noted that all VLAN ID values described above have a 4 bit reserved
section followed by a 12-bit value. It is carried within the
CAPABILITY TLV.
2.4.8. The Ingress-to-Egress Options (ITEOPT) sub-TLV 2.4.8. The Ingress-to-Egress Options (ITEOPT) sub-TLV
By including this sub-TLV within one or more Router Capability TLVs By including this sub-TLV within one or more Router Capability TLVs
in its LSPs, an RBridge can advertise the Ingress-to-Egress options in its LSPs, an RBridge can advertise the Ingress-to-Egress options
it supports. This sub-TLV may appear zero or more times within a it supports. This sub-TLV may appear zero or more times within a
Router Capability TLV. By default, in the absence of any ITEOPT sub- Router Capability TLV. By default, in the absence of any ITEOPT sub-
TLVs, no Ingress-to-Egress options are supported. TLVs, no Ingress-to-Egress options are supported.
There are two types of Ingress-to-Egress option encoding within the There are two types of Ingress-to-Egress option encoding within the
skipping to change at page 30, line 11 skipping to change at page 31, line 14
o Value: The first byte of the option followed by option dependent o Value: The first byte of the option followed by option dependent
information. information.
2.4.9. VLAN Mapping (VMAP) sub-TLV 2.4.9. VLAN Mapping (VMAP) sub-TLV
The VLAN Mapping (VMAP) TLV carries information concerning VLAN The VLAN Mapping (VMAP) TLV carries information concerning VLAN
mappings configured at the originating IS. VLAN mapping is used when mappings configured at the originating IS. VLAN mapping is used when
an RBridge campus is divided into regions such that the same VLAN is an RBridge campus is divided into regions such that the same VLAN is
represented by different VLAN IDs in different regions or there is a represented by different VLAN IDs in different regions or there is a
VLAN is one region that has no equivalent in another region. As VLAN is one region that has no equivalent in another region. Each
specified in [VMAP], each port on each of the border RBridges between port on each of the border RBridges between two or more regions MUST
two or more regions MUST be configured at to which region each port be configured at to which region each port connects with. The
connects with. The numbering of regions is an arbitrary choice but numbering of regions is an arbitrary choice but all border RBridges
all border RBridges in the campus MUST agree on the number of each in the campus MUST agree on the number of each region.
region.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type = VMAP | | Type = VMAP |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+----------...+ +-+-+-+-+-+-+-+-+----------...+
| Mapping 1 | (8 bytes) | Mapping 1 | (8 bytes)
+-+-+-+-+-+-+-+------------... +-+-+-+-+-+-+-+------------...
| Mapping N, etc.| | Mapping N, etc.|
+--------------------------... +--------------------------...
skipping to change at page 30, line 49 skipping to change at page 31, line 51
o Length: variable, 8*N. o Length: variable, 8*N.
o Value: Specific information on each VLAN mapping as diagrammed o Value: Specific information on each VLAN mapping as diagrammed
above and specified below: above and specified below:
* Count: If this four bit unsigned integer is zero or 1, then the * Count: If this four bit unsigned integer is zero or 1, then the
mapping of a single VLAN ID is being specified. If it is any mapping of a single VLAN ID is being specified. If it is any
value from 2 through 15, then a block of that many contiguous value from 2 through 15, then a block of that many contiguous
VLAN IDs starting with the From VLAN ID is mapped to a block of VLAN IDs starting with the From VLAN ID is mapped to a block of
that many contiguous VLAN IDS starting with the To VLAN ID. that many contiguous VLAN IDs starting with the To VLAN ID.
* From VLAN ID: This is the VLAN ID that, when received on a port * From VLAN ID: This is the VLAN ID that, when received on a port
connect to the From Region on a frame being sent to the To connect to the From Region on a frame being sent to the To
Region, is mapped to the To VLAN ID. This must be a real VLAN Region, is mapped to the To VLAN ID. This must be a real VLAN
ID, that is, the values 0x000 and 0xFFF are prohibited. ID, that is, the values 0x000 and 0xFFF are prohibited.
* From Region: This is the region number, within the campus, such * From Region: This is the region number, within the campus, such
that frames received on a port connected to that region and that frames received on a port connected to that region and
destined to a port connected to the To Region have their VLAN destined to a port connected to the To Region have their VLAN
ID mapped as specified by the From VLAN ID and To VLAN ID ID mapped as specified by the From VLAN ID and To VLAN ID
fields. fields.
* RESV: MUST be sent as zero on sub-TLV creation and ignored on * RESV: MUST be sent as zero and ignored on receipt.
receipt.
* To VLAN ID: This is the VLAN ID to be used on frames sent out a * To VLAN ID: This is the VLAN ID to be used on frames sent out a
port connected to the To Region if they were received on a port port connected to the To Region if they were received on a port
connected to the From Region with the From VLAN ID; except that connected to the From Region with the From VLAN ID; except that
if the To VLAN ID is 0x000 the frame is dropped. The value if the To VLAN ID is 0x000 the frame is dropped. The value
invalid VLAN ID 0xFFF is prohibited in this field. invalid VLAN ID 0xFFF is prohibited in this field.
* To Region: This is the region number, within the campus, such * To Region: This is the region number, within the campus, such
that frames sent on a port connected to this region from a port that frames sent on a port connected to this region from a port
connected to the From Region have their VLAN ID mapped as connected to the From Region have their VLAN ID mapped as
skipping to change at page 32, line 33 skipping to change at page 34, line 5
The SPB Instance sub-TLV gives the SPSourceID for this node/topology The SPB Instance sub-TLV gives the SPSourceID for this node/topology
instance. This is the 20 bit value that is used in the formation of instance. This is the 20 bit value that is used in the formation of
multicast DA addresses for packets originating from this node/ multicast DA addresses for packets originating from this node/
instance. The SPSourceID occupies the upper 20 bits of the multicast instance. The SPSourceID occupies the upper 20 bits of the multicast
DA together with 4 other bits (see the SPB 802.1ah multicast DA DA together with 4 other bits (see the SPB 802.1ah multicast DA
address format section). address format section).
This sub-TLV SHOULD be carried within the MT-Capability TLV in the This sub-TLV SHOULD be carried within the MT-Capability TLV in the
fragment ZERO LSP. fragment ZERO LSP.
+-+-+-+-+-+-+-+-+
|Type = SPB-Inst|
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIST Root Identifier (4 bytes) | | CIST Root Identifier (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIST Root Identifier (cont) (4 bytes) | | CIST Root Identifier (cont) (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| CIST External ROOT Path Cost (4 bytes) | | CIST External ROOT Path Cost (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Bridge Priority | (2 bytes) | Bridge Priority | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R R R R| SPS Flags |V| SPSOURCEID | (4 bytes) |R R R R| SPS Flags |V| SPSOURCEID | (4 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| N-VID Trees | (2 bytes) | Num of Trees | (1 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID (1) Tuples (48 bytes) | | VLAN-ID (1) Tuples (8 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID (N) Tuples (48 bytes) | | VLAN-ID (N) Tuples (8 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ECT-Alg-Len | (1 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Algorithm (32 bytes) | | Opaque ECT Algorithm (32 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Information (variable ) | | Opaque ECT Information (variable ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where VLAN-ID tuples have the format as: where VLAN-ID tuples have the format as:
0 1 2- 3 4 - 15 16 - 19 20 - 31 0 1 2 3
+-+-+---------+-------+-----------+------------+ 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
|A|U|Reserved | VID | Algorithm | B-VID | +-+-+-+-+-+-+-+-+
+-+-+---------+-------+-----------+------------+ |U|M|A| Res |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ECT - Algorithm (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Base VID 12 bits) | SPTVID 12 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to SPB Instance sub-TLV 1 [TBD]. o Type: sub-TLV Type, set to SPB Instance sub-TLV 1 [TBD].
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o CIST Root Identifier (64-bits)The CIST Root Identifier is for SPB o CIST Root Identifier (64-bits)The CIST Root Identifier is for SPB
interworking with RSTO and MSTP at SPT RegionBoundaries. This is interworking with RSTO and MSTP at SPT RegionBoundaries. This is
an imported value from a Spanning tree. an imported value from a Spanning tree.
o CIST External Root Path Cost (32-bits) The CIST External Root Path o CIST External Root Path Cost (32-bits) The CIST External Root Path
Cost is the cost from the Spanning tree algorithm to the Root. Cost is the cost from the Spanning tree algorithm to the Root.
o Bridge Priority (16-bits) Bridge priority is the 16 bits that o Bridge Priority (16-bits) Bridge priority is the 16 bits that
together with the low 6 bytes of the System ID form the Bridge together with the low 6 bytes of the System ID form the Bridge
Identifier. The Bridge Identifier is the Spanning tree compatible Identifier. The Bridge Identifier is the Spanning tree compatible
Bridge identifier. This is configured exactly as specified in Bridge identifier. This is configured exactly as specified in
IEEE802 [802.1D]. This allows SPB to build a compatible Spanning IEEE802 [802.1D]. This allows SPB to build a compatible Spanning
tree using link state by combining the Bridge Priority and the tree using link state by combining the Bridge Priority and the
System ID to form the 8 byte Bridge Identifier. The 8 byte Bridge System ID to form the 8 byte Bridge Identifier. The 8 byte Bridge
Identifier is also the input to the 16 pre defined ECT tie breaker Identifier is also the input to the 16 pre-defined ECT tie breaker
algorithms. algorithms.
o V bit (1-Bit) The V bit (SPBM) indicates this SPSourceID is auto o V bit (1-Bit) The V bit (SPBM) indicates this SPSourceID is auto
allocated(27.11). If the V bit is clear the SPSourceID has been allocated(27.11). If the V bit is clear the SPSourceID has been
configured and must be unique. When the bridge allocating configured and must be unique. Allocation of SPSourceID is in
receives the complete LSP from the IS-IS adjacency it will [IEEE 802.1aq]. Bridges running SPBM will allocate an SPSourceID
allocate a SPSourceID according to the allocation logic(27.11). if they are not configured with an explicit SPSourceID. The V Bit
allows neighbor bridges to determine if the auto allocation was
enabled. In the rare chance of a collision of SPsourceID the
bridge with the highest priority Bridge Identifier will win
conflicts and the lower priority Bridge will be re-allocated or if
the lower priority Bridge is configured it will not be allowed to
joint the SPT Region.
o The SPSOURCEID is a 20 bit value used to construct multicast DA's o The SPSOURCEID is a 20 bit value used to construct multicast DA's
as described below for multicast packets originating from the as described below for multicast packets originating from the
origin (SPB node) of the link state packet (LSP) that contains origin (SPB node) of the link state packet (LSP) that contains
this TLV. More details are in [IEEE 802.1aq]. this TLV. More details are in [IEEE 802.1aq].
o Number of Trees (8-bits) The Number of Trees is be set to the o Number of Trees (8-bits) The Number of Trees is be set to the
number of [ECT-ALGORITHM, Base-VID plus flags] sub TLV's that number of [ECT-ALGORITHM, Base-VID plus flags] sub TLV's that
follow. Each ECT-ALGORITHM has an Base VID, an SPVID and some follow. Each ECT-ALGORITHM has an Base VID, an SPVID and some
flags described below. This must be set to at least one ECT. flags described below. This must be set to at least one ECT.
These define the standard ECTs. In addition proprietary ECTs may These define the standard ECTs.
be defined in the opaque TLV S bit indicates the presence of sub-
TLVs following this value.
o Each VID Tuple consists of: o Each VID Tuple consists of:
o * U-Bit (1-bit) The Use flag is set if this bridge is currently
* U-Bit (1-bit) The Use flag is set if this bridge, is currently
using this ECT-ALGORITHM for I-SIDs it sources or sinks. This using this ECT-ALGORITHM for I-SIDs it sources or sinks. This
is a bit different than the U-bit found in the Hello, which is a bit different than the U-bit found in the Hello, which
will set the Use-Flag if it sees other nodal Use-Flags are set will set the Use-Flag if it sees other nodal Use-Flags are set
OR it sources or sinks itself. OR it sources or sinks itself.
* M-Bit (1-bit) The M-bit indicates if this is SPBM or SPBV mode. * M-Bit (1-bit) The M-bit indicates if this is SPBM or SPBV mode.
* A bit, The A bit (SPB) when set declares this is an SPVID with * A bit, The A bit (SPB) when set declares this is an SPVID with
auto allocation(27.11). If the VID value is zero. A VID will auto allocation. The VID allocation logic details are in [IEEE
be allocated once the bridge has synchronized the IS-IS 802.1aq]. Since SPVIDs are from a small pool of resources
LSPs.Neighbor bridges can distribute the LSPs but must not (1000 or less) the chances of collision are high. To allow
populate filtering databases (forwarding) for traffic from a auto allocation LSPs are exchanged with the allocated bridge
bridge that has an SPVID of 0. When the bridge allocating is setting the SPVID to 0.
synchronized with the IS-IS adjacency, it will allocate one or
more SPVIDs according to the allocation logic. o ECT-ALG-LEN (1 byte): This gives the length of the ECT Algorithm.
o ECT-ALGORITHM (4-bytes) ECT-ALGORITHM is advertised when the o ECT-ALGORITHM (4-bytes) ECT-ALGORITHM is advertised when the
bridge supports a given ECT-ALGORITHM (by OUI/Index) on a given bridge supports a given ECT-ALGORITHM (by OUI/Index) on a given
VID. This declaration must match the declaration in the Hello PDU VID. This declaration must match the declaration in the Hello PDU
originating from the same bridge. The ECT-ALGORITHM, BASE-VID originating from the same bridge. The ECT-ALGORITHM, BASE-VID
should match what is generated in the Hellos of the same node. should match what is generated in the Hellos of the same node.
The ECT-ALGORITHM, BASE-VIDs pairs can come in any order however. The ECT-ALGORITHM, BASE-VIDs pairs can come in any order however.
o Base VID (12-bits) The Base-VID that associated the SPT Set via o Base VID (12-bits) The Base-VID that associated the SPT Set via
the ECT-ALGORITHM. the ECT-ALGORITHM.
skipping to change at page 35, line 5 skipping to change at page 36, line 35
o an opaque ECT Data TLV (type TBD) whose first 32 bits are the ECT- o an opaque ECT Data TLV (type TBD) whose first 32 bits are the ECT-
ALGORITHM which this data applies to. ALGORITHM which this data applies to.
2.5.2. SPBM Service Identifier and Unicast Address sub-TLV 2.5.2. SPBM Service Identifier and Unicast Address sub-TLV
The SPBM Service Identifier and Unicast Address sub-TLV is used to The SPBM Service Identifier and Unicast Address sub-TLV is used to
introduce service group membership on the originating node and/or to introduce service group membership on the originating node and/or to
advertise an additional B-MAC unicast address present on, or advertise an additional B-MAC unicast address present on, or
reachable by the node. reachable by the node.
0 1 2 3 +-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |Type = SPBM-SI |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| B-MAC ADDRESS | | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| B-MAC ADDRESS (cont) | Res. | Base-VID | | B-MAC ADDRESS (6 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #1 | | Res. | Base-VID | ( 2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #2 | |T|R| Reserved | ISID #1 | (1+3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #n | |T|R| Reserved | ISID #2 | (1+3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #n | (1+3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to SPBM Service Identifier and Unicast o Type: sub-TLV Type, set to SPBM Service Identifier and Unicast
Address sub-TLV 2 [TBD]. Address sub-TLV 2 [TBD].
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o B-MAC ADDRESS is a unicast address of this node. It may be either o B-MAC ADDRESS is a unicast address of this node. It may be either
the single nodal address, or may address a port or any other level the single nodal address, or may address a port or any other level
of granularity relative to the node. In the case where the node of granularity relative to the node. In the case where the node
only has one B-MAC address this should be the same as the SYS-ID only has one B-MAC address this should be the same as the SYS-ID
of the node. To add multiple B-MACs this TLV must be repeated per of the node. To add multiple B-MACs this TLV must be repeated per
skipping to change at page 36, line 8 skipping to change at page 38, line 5
Extended Reachability TLV (type 22). Extended Reachability TLV (type 22).
2.6.1. SPB Link Metric sub-TLV 2.6.1. SPB Link Metric sub-TLV
The SPB Link Metric sub-TLV occurs nested as within the Extended The SPB Link Metric sub-TLV occurs nested as within the Extended
Reachability TLV (type 22), or the Multi Topology Intermediate System Reachability TLV (type 22), or the Multi Topology Intermediate System
TLV (type 222). If this sub TLV is not present for an ISIS adjacency TLV (type 222). If this sub TLV is not present for an ISIS adjacency
then that adjacency MUST NOT carry SPB traffic for the given topology then that adjacency MUST NOT carry SPB traffic for the given topology
instance. instance.
0 1 2 3 +-+-+-+-+-+-+-+-+
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 |Type=SPB-Metric|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Reserved (must be 0) | | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SPB-LINK-METRIC | Num port ID | | SPB-LINK-METRIC | (3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Identifier | | Num of ports | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Algorithm (32 bytes) | | Port Identifier | ( 2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Information (variable ) | | Opaque ECT Algorithm (32 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Information (variable ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to SPB Link Metric sub-TLV 5 [TBD]. o Type: TLV Type, set to SPB Link Metric sub-TLV 5 [TBD].
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o SPB-LINK-METRIC indicates the administrative cost or weight of o SPB-LINK-METRIC indicates the administrative cost or weight of
using this link as a 24 bit unsigned number. Smaller numbers using this link as a 24 bit unsigned number. Smaller numbers
indicate lower weights and are more likely to carry SPB traffic. indicate lower weights and are more likely to carry SPB traffic.
Only one metric is allowed per SPB instance per link. If multiple Only one metric is allowed per SPB instance per link. If multiple
metrics are required multiple SPB instances are required, either metrics are required multiple SPB instances are required, either
within IS-IS or within several independent IS-IS instances. within IS-IS or within several independent IS-IS instances.
o Num of Ports is the number of ports associated with this link. o Num of Ports is the number of ports associated with this link.
o Port Identifier is the standard IEEE port identifier used to build o Port Identifier is the standard IEEE port identifier used to build
a spanning tree associated with this link. a spanning tree associated with this link.
o an opaque ECT Data TLV (type TBD) whose first 32 bits are the ECT- o an opaque ECT Data TLV (type TBD) whose first 32 bits are the ECT-
ALGORITHM which this data applies to. ALGORITHM to which this data applies.
2.6.2. MTU sub-TLV 2.6.2. MTU sub-TLV
The MTU sub-TLV is used to optionally announce the MTU of a link. It The MTU sub-TLV is used to optionally announce the MTU of a link. It
occurs nested as within the Extended Reachability TLV (type 22). occurs nested as within the Extended Reachability TLV (type 22).
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type = MTU | | Type = MTU |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|F| Reserved | (2 bytes) |F| Reserved | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| MTU | (2 bytes) | MTU | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to MTU sub-TLV 6 [TBD]. o Type: TLV Type, set to MTU sub-TLV 6 [TBD].
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o Failed: This bit is a one if MTU testing on this link failed at o Failed: This bit is a one if MTU testing on this link failed at
the required campus-wide MTU. the required campus-wide MTU.
o MTU: This field is set to the largest successfully tested MTU size o MTU: This field is set to the largest successfully tested MTU size
for this link or zero if it has not been tested. for this link or zero if it has not been tested.
2.7. TRILL Neighbor TLV 2.7. TRILL Neighbor TLV
The TRILL Neighbor TLV is used in the TRILL-Hello PDU in place of the The TRILL Neighbor TLV is used in the TRILL-Hello PDU in place of the
IS Neighbor TLV. It differs in that MTU information is provided per IS Neighbor TLV. It differs in that MTU information is provided per
neighbor and provision is made for fragmentation, so that not all neighbor and provision is made for fragmentation, so that not all
neighbors need be reported in each TRILL-Hello, to support the hard neighbors need be reported in each TRILL-Hello, to support the hard
limit on the size of TRILL-Hellos. The structure of the TRILL limit on the size of TRILL-Hellos. This TLV can occur zero, one, or
multiple times in a TRILL-Hello PDU. The structure of the TRILL
Neighbor TLV is as follows: Neighbor TLV is as follows:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type = TNeigh | | Type = TNeigh |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|S|L| Reserved | (2 bytes) |S|L| Reserved | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sender nickname |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor RECORDS (1) | | Neighbor RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Neighbor RECORDS (N) | | Neighbor RECORDS (N) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
The list of neighbors MUST be ordered by MAC address, considering The list of neighbors MUST be ordered by MAC address, considering
each 6-byte MAC address to be an unsigned integer, starting with the each 6-byte MAC address to be an unsigned integer, starting with the
skipping to change at page 38, line 12 skipping to change at page 40, line 4
each 6-byte MAC address to be an unsigned integer, starting with the each 6-byte MAC address to be an unsigned integer, starting with the
smallest. The information present for each neighbor is as follows: smallest. The information present for each neighbor is as follows:
+-+-------------------+ +-+-------------------+
|F| Reserved | (2 bytes) |F| Reserved | (2 bytes)
+-+-------------------+ +-+-------------------+
| MTU | (2 bytes) | MTU | (2 bytes)
+--------------------------------------------------------+ +--------------------------------------------------------+
| MAC Address | (6 bytes) | MAC Address | (6 bytes)
+--------------------------------------------------------+ +--------------------------------------------------------+
o Type: TLV Type, set to TRILL-Neighbor TLV XX [TBD]. o Type: TLV Type, set to TRILL-Neighbor TLV XX [TBD].
o Length: Total number of bytes contained in the value field, 4 o Length: Total number of bytes contained in the value field, 2 +
+10*n, where n is the number of neighbor records. 10*n, where n is the number of neighbor records.
o S: smallest flag. If this bit is a one, then the list of o S: smallest flag. If this bit is a one, then the list of
neighbors includes the neighbor with the smallest MAC address. neighbors includes the neighbor with the smallest MAC address.
o L: largest flag. If this bit is a one, then the list of neighbors o L: largest flag. If this bit is a one, then the list of neighbors
includes the neighbor with the largest MAC address. includes the neighbor with the largest MAC address.
o Reserved: These bits are reserved for future use and MUST be set o Reserved: These bits are reserved for future use and MUST be set
to zero on transmission and ignored on receipt. to zero on transmission and ignored on receipt.
o Sender nickname: If the sending intermediate system is holding any
nicknames, one MUST be included here. Otherwise, the field is set
to zero. This field is to support intelligent end stations that
determine the egress RBridge for unicast data through a directory
service or the like and need a nickname for their first hop to
insert as the ingress nickname to correctly format a TRILL
encapsulated data frame.
o F: failed. This bit is a one if MTU testing to their neighbor o F: failed. This bit is a one if MTU testing to their neighbor
(see Section 3.3) failed at the required campus-wide MTU (see Section 3.3) failed at the required campus-wide MTU
o MTU: This field is set to the largest successfully tested MTU size o MTU: This field is set to the largest successfully tested MTU size
for this neighbor or zero if it has not been tested. for this neighbor or zero if it has not been tested.
o MAC Address: The MAC address of the neighbor as in the IS Neighbor o MAC Address: The MAC address of the neighbor as in the IS Neighbor
RLV (#6). RLV (#6).
2.8. The Group Membership Active Source TLV 2.8. The Group Membership Active Source TLV
The Group Active Source (GMAS) TLV is IS-IS TLV type 146 [TBD] and The Group Active Source (GMAS) TLV is IS-IS TLV type 146 [TBD] and
has the following format: has the following format:
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = GMAS | (1 byte)
|Type = GMAS | Length | sub-TLVs | +-+-+-+-+-+-+-+-+
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLVs (variable bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: TLV Type, set to GMAS-TLV 146 [TBD]. o Type: TLV Type, set to GMAS-TLV 146 [TBD].
o Length: Total number of bytes contained in the value field, which o Length: Total number of bytes contained in the value field, which
includes the length of the sub-TLVs carried in this TLV. includes the length of the sub-TLVs carried in this TLV.
o sub-TLVs: The Group Active Source TLV value contains sub-TLVs o sub-TLVs: The Group Active Source TLV value contains sub-TLVs
formatted as described in [RFC5305]. The sub-TLVs for this TLV formatted as described in [RFC5305]. The sub-TLVs for this TLV
are specified in the following subsections. are specified in the following subsections.
The GMAS TLV is carried within Multicast Group Level 1 link state The GMAS TLV is carried within Multicast Group Level 1 link state
PDU. PDU.
2.8.1. The Group MAC Active Source sub-TLV 2.8.1. The Group MAC Active Source sub-TLV
The Group MAC Source (GMAS-MAC) sub-TLV is IS-IS sub-TLV type 1 The Group MAC Source (GMAS-MAC) sub-TLV is IS-IS sub-TLV type 1
within the GMAS TLV and has the following format: within the GMAS TLV and has the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type=GMAS-MAC | (1 byte) | Type=GMAS-MAC | (1 byte)
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Confidence | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname-Id | (2 bytes) |D|D| R | Vlan ID | (2 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|G|S|R|R| VLAN-ID | (2 bytes) | Address family | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delivery group (afi scoped number of bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delivery Source (afi scoped number of bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Num Group Recs | (1 byte) |Num Group Recs | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (1) | | GROUP RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (N) | | GROUP RECORDS (N) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where each group record is of the form: where each group record is of the form:
skipping to change at page 40, line 29 skipping to change at page 42, line 14
o Type: sub-TLV Type, set to 1 (GMAS-MAC) of length 1 byte. o Type: sub-TLV Type, set to 1 (GMAS-MAC) of length 1 byte.
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the MAC addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESERVED: Must be sent as zero on transmission and is ignored on o RESERVED: Must be sent as zero on transmission and is ignored on
receipt. receipt.
o G: Delivery Group is set o G: Delivery Group is set
o S: Delivery Source is set o S: Delivery Source is set
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 Number of Group Records: This is of length 1 byte and lists the o Number of Group Records: This is of length 1 byte and lists the
number of group records in this TLV. number of group records in this TLV.
o Group Record: Each group record has a reserved space and is o Group Record: Each group record has a one byte reserved space and
followed by the number of sources, each of length 1 byte. It then the next byte carries the number of sources. It then has a 48-bit
has a 48-bit multicast Group Address followed by 48-bit source MAC multicast Group Address followed by 48-bit source MAC addresses.
addresses. An address being a group multicast address or unicast An address being a group multicast address or unicast source
source address can be checked using the multicast bit in the address can be checked using the multicast bit in the address. If
address. If the number of sources do not fit in a single sub-TLV, the number of sources do not fit in a single sub-TLV, it is
it is permitted to have the same group address repeated with permitted to have the same group address repeated with different
different source addresses in another sub-TLV of another instance source addresses in another sub-TLV of another instance of the
of the Group Active Source TLV. Group Active Source TLV.
The GMAS-MAC sub-TLV is carried within the GMAS TLV and MUST be The GMAS-MAC sub-TLV is carried within the GMAS TLV and MUST be
carried in a standard Level 1 link state MGROUP PDU. carried in a standard Level 1 link state MGROUP PDU.
2.8.2. The Group IP Active Source sub-TLV 2.8.2. The Group IP Active Source sub-TLV
The Group IP Address (GMAS-IP) sub-TLV is IS-IS TLV type 2 and has The Group IP Address (GMAS-IP) sub-TLV is IS-IS TLV type 2 and has
the following format: the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type=GMAS-IP | | Type=GMAS-IP | (1 byte)
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Confidence | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname-Id | (2 bytes) |D|D| R | Vlan ID | (2 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|G|S|R|R| VLAN-ID | (2 bytes) | Address family | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delivery group (afi scoped number of bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delivery Source (afi scoped number of bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Num Group Recs | (1 byte) |Num Group Recs | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (1) | | GROUP RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (N) | | GROUP RECORDS (N) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where each group record is of the form: where each group record is of the form:
skipping to change at page 42, line 17 skipping to change at page 44, line 7
o Length: Total number of bytes contained in the value field of the o Length: Total number of bytes contained in the value field of the
TLV. TLV.
o Confidence: This carries an 8-bit quantity indicating the o Confidence: This carries an 8-bit quantity indicating the
confidence level in the IP addresses being transported. Whether confidence level in the IP 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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the MAC addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESERVED: Must be sent as zero on transmission and is ignored on o RESERVED: Must be sent as zero on transmission and is ignored on
receipt. receipt.
o G: Delivery Group is set o G: Delivery Group is set
o S: Delivery Source is set o S: Delivery Source is set
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 Number of Group Records: This is of length 1 byte and lists the o Number of Group Records: This is of length 1 byte and lists the
number of group records in this TLV. number of group records in this TLV.
o Group Record: Each group record has a reserved space and is o Group Record: Each group record has a one byte reserved space and
followed by the number of sources, each of length 1 byte. It is the next byte carries the number of sources. It is followed by a
followed by a 32-bit IPv4 Group Address followed by 32-bit source 32-bit IPv4 Group Address followed by 32-bit source IPv4
IPv4 addresses. If the number of sources do not fit in a single addresses. If the number of sources do not fit in a single sub-
sub-TLV, it is permitted to have the same group address repeated TLV, it is permitted to have the same group address repeated with
with different source addresses repeated in another sub-TLV of different source addresses repeated in another sub-TLV of another
another instance of the Group Active Source TLV. instance of the Group Active Source TLV.
The GMAS-IP TLV is carried within the GMAS TLV and MUST be carried in The GMAS-IP TLV is carried within the GMAS TLV and MUST be carried in
a standard Level 1 link state MGROUP PDU. a standard Level 1 link state MGROUP PDU.
2.8.3. The Group IPv6 Active Source sub-TLV 2.8.3. The Group IPv6 Active Source sub-TLV
The Group IPv6 Active Source (GMAS-IPv6) TLV is IS-IS sub-TLV type 3 The Group IPv6 Active Source (GMAS-IPv6) TLV is IS-IS sub-TLV type 3
and has the following format: and has the following format:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=GMAS-IPv6 | | Type=GMAS-IP | (1 byte)
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Confidence | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Topology-Id/ Nickname-Id | (2 bytes) |D|D| R | Vlan ID | (2 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|G|S|R|R| VLAN-ID | (2 bytes) | Address family | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delivery group (afi scoped number of bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Delivery Source (afi scoped number of bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Num Group Recs | (1 byte) |Num Group Recs | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (1) | | GROUP RECORDS (1) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ................. | | ................. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| GROUP RECORDS (N) | | GROUP RECORDS (N) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where each group record is of the form: where each group record is of the form:
skipping to change at page 43, line 51 skipping to change at page 46, line 6
o Type: sub-TLV Type, set to 3 (GIPV6-ADDR). o Type: sub-TLV Type, set to 3 (GIPV6-ADDR).
o Length: Total number of bytes contained in the value field. o Length: Total number of bytes contained in the value field.
o Confidence: This carries an 8-bit quantity indicating the o Confidence: This carries an 8-bit quantity indicating the
confidence level in the IPv6 addresses being transported. Whether confidence level in the IPv6 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 Topology-Id/Nickname-Id: Depending on the technology in which it o Topology-Id/Nickname : Depending on the technology in which it is
is used, this carries the topology-id or nickname-id. When this used, this carries the topology-id or nickname. When this field
field is set to zero this implies that the MAC addresses are is set to zero this implies that the MAC addresses are reachable
reachable across all topologies or across all nicknames of the across all topologies or across all nicknames of the originating
originating IS. IS.
o RESERVED: Must be sent as zero on transmission and is ignored on o RESERVED: Must be sent as zero on transmission and is ignored on
receipt. receipt.
o G: Delivery Group is set o G: Delivery Group is set
o S: Delivery Source is set o S: Delivery Source is set
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 Number of Group Records: This of length 1 byte and lists the o Number of Group Records: This of length 1 byte and lists the
number of group records in this TLV. number of group records in this TLV.
o Group Record: Each group record has a reserved space and is o Group Record: Each group record has a one byte reserved space and
followed by the number of sources, each of length 1 byte. It is the next byte carries the number of sources. It is followed by a
followed by a 128-bit multicast IPv6 Group Address followed by 128-bit multicast IPv6 Group Address followed by 128-bit source
128-bit source IPv6 addresses. If the number of sources do not IPv6 addresses. If the number of sources do not fit in a single
fit in a single sub-TLV, it is permitted to have the same group sub-TLV, it is permitted to have the same group address repeated
address repeated with different source addresses repeated in with different source addresses repeated in another sub-TLV in
another sub-TLV in another instance of the Group Address TLV. another instance of the Group Address TLV.
The GMAS-IPv6 sub-TLV is carried within the GMAS TLV and MUST be The GMAS-IPv6 sub-TLV is carried within the GMAS TLV and MUST be
carried in a standard Level 1 link state MGROUP PDU. carried in a standard Level 1 link state MGROUP PDU.
2.9. PDU Extensions to IS-IS 2.9. PDU Extensions to IS-IS
2.9.1. The Multicast Group PDU 2.9.1. The Multicast Group PDU
The systems that this document is concerned with want to carry not The systems that this document is concerned with want to carry not
only layer-2 unicast information in the link state protocols, but only layer-2 unicast information in the link state protocols, but
skipping to change at page 45, line 46 skipping to change at page 47, line 50
specifications. specifications.
2.9.1.2. The Multicast Group Complete Sequence Number PDU 2.9.1.2. The Multicast Group Complete Sequence Number PDU
The Multicast Group Complete Sequence Number PDU (MGROUP-CSNP) PDU is The Multicast Group Complete Sequence Number PDU (MGROUP-CSNP) PDU is
used to reliably flood the MGROUP PDU following the base protocol used to reliably flood the MGROUP PDU following the base protocol
specifications. specifications.
2.9.1.3. Enhancements to the flooding process 2.9.1.3. Enhancements to the flooding process
This document proposes that the information contained in the MGROUP- This document specifies that the information contained in the MGROUP-
PDU is in a parallel database and its update mechanisms mimic that of PDU is in a parallel database and its update mechanisms mimic that of
the regular database. Nodes running IS-IS in an L2 domain MUST the regular database. Nodes running IS-IS in an L2 domain MUST
support these additional MGROUP PDUs defined in this document. In support these additional MGROUP PDUs defined in this document. In
general, the flooding of the MGROUP-PDU in tandem with the MGROUP- general, the flooding of the MGROUP-PDU in tandem with the MGROUP-
PSNP and MGROUP-CSNP PDUs uses the same update procedures as defined PSNP and MGROUP-CSNP PDUs uses the same update procedures as defined
for the regular LSP, PSNP, and CSNP PDUs. for the regular LSP, PSNP, and CSNP PDUs.
For example, on P2P links CSNP is exchanged on the formation of an For example, on P2P links CSNP is exchanged on the formation of an
adjacency. In a similar fashion a MGROUP-CSNP MUST also be exchanged adjacency. In a similar fashion a MGROUP-CSNP MUST also be exchanged
between the neighbors at the same time. This gets the initial between the neighbors at the same time. This gets the initial
skipping to change at page 47, line 18 skipping to change at page 49, line 23
42 bytes shorter than the reasonable lower bound for the link MTU. 42 bytes shorter than the reasonable lower bound for the link MTU.
For example, for an 802.3 Ethernet link, the MTU SHOULD be assumed to For example, for an 802.3 Ethernet link, the MTU SHOULD be assumed to
be 1512 bytes for the purpose of determining the maximum size of be 1512 bytes for the purpose of determining the maximum size of
TRILL-Hello PDUs on that link. Thus, for such a link, TRILL-Hellos TRILL-Hello PDUs on that link. Thus, for such a link, TRILL-Hellos
MUST NOT exceed 1470 bytes. MUST NOT exceed 1470 bytes.
The following MUST appear in every TRILL-Hello PDU: a Port Capability The following MUST appear in every TRILL-Hello PDU: a Port Capability
TLV (see Section 2.3) containing a Special VLANs and Flags sub-TLV. TLV (see Section 2.3) containing a Special VLANs and Flags sub-TLV.
Additional TLVs/sub-TLVs MAY appear in a TRILL-Hello including the Additional TLVs/sub-TLVs MAY appear in a TRILL-Hello including the
TRILL Hello TLV specified in Section 2.7 and the following sub-TLVs TRILL Neighbor TLV specified in Section 2.7 and the following sub-
specified in Section 2.3: Enabled VLANs sub-TLV, Appointed Forwarders TLVs specified in Section 2.3: Enabled VLANs sub-TLV, Appointed
sub-TLV, and Hop-by-Hop Options sub-TLV. Forwarders sub-TLV, and Hop-by-Hop Options sub-TLV.
The Padding TLV (#8) SHOULD NOT appear in a TRILL-Hello. The Padding TLV (#8) SHOULD NOT appear in a TRILL-Hello.
The IS-IS Neighbor TLV (#6) MUST NOT appear in a TRILL-Hello. The IS-IS Neighbor TLV (#6) MUST NOT appear in a TRILL-Hello.
Instead, it uses the TRILL Neighbor TLV (see Section 2.7). Instead, it uses the TRILL Neighbor TLV (see Section 2.7).
2.9.3. The MTU PDU 2.9.3. The MTU PDU
The MTU-probe and MTU-ack PDUs are used to determine the MTU on a The MTU-probe and MTU-ack PDUs are used to determine the MTU on a
link between intermediate systems. An MTU-probe MUST be padded to link between intermediate systems. An MTU-probe MUST be padded to
skipping to change at page 49, line 10 skipping to change at page 51, line 14
MTU-ACK-PDU Level-1 PDU Type: 28 MTU-ACK-PDU Level-1 PDU Type: 28
This document specifies the definition a set of new IS-IS TLVs, the This document specifies the definition a set of new IS-IS TLVs, the
MAC-Reachability TLV (type 141), the Group Address TLV (type 142), MAC-Reachability TLV (type 141), the Group Address TLV (type 142),
the Port-Capability TLV (type 143), the MT-Capability TLV (type 144), the Port-Capability TLV (type 143), the MT-Capability TLV (type 144),
and the Trill-Neighbor TLV (type 145), and Group Member Active Source and the Trill-Neighbor TLV (type 145), and Group Member Active Source
TLV (type 146) that needs to be reflected in the IS-IS TLV code-point TLV (type 146) that needs to be reflected in the IS-IS TLV code-point
registry. registry.
This document creates a number of new sub-TLVs in the numbering space This document creates a number of new sub-TLVs in the numbering space
for the Group Address TLV, the Link Capability TLV, and the for the Group Address TLV, the MT Port Capability TLV, the Extended
Capability TLV. The TLV and sub-TLVs are given below along with Reachability TLV, the MT-Capability TLV, and the Capability TLV. The
technologies that use them. TLV and sub-TLVs are given below along with technologies that use
them.
IIH LSP SNP MCAST MCAST TRILL/ IIH LSP SNP MCAST MCAST TRILL/
LSP SNP IEEE LSP SNP IEEE
MAC-RI TLV (141) - X - - - T/I MAC-RI TLV (141) - X - - - T/I
GADDR-TLV (142) - - - X - -/I GADDR-TLV (142) - - - X - -/I
GADDR-TLV.GMAC-ADDR sub-TLV 1 - - - X - T/I GADDR-TLV.GMAC-ADDR sub-TLV 1 - - - X - T/I
GADDR-TLV.GMAC-IP sub-TLV 2 - - - X - T/I GADDR-TLV.GMAC-IP sub-TLV 2 - - - X - T/I
GADDR-TLV.GMAC-IPV6 sub-TLV 3 - - - X - T/I GADDR-TLV.GMAC-IPV6 sub-TLV 3 - - - X - T/I
GADDR-TLV.SPBV-MAC-ADDR sub-TLV 4 - - - X - -/I GADDR-TLV.SPBV-MAC-ADDR sub-TLV 4 - - - X - -/I
skipping to change at page 50, line 31 skipping to change at page 52, line 31
PortCap.SPBDigest sub-TLV 6 X - - - - -/I PortCap.SPBDigest sub-TLV 6 X - - - - -/I
PortCap.SiteIdentifier sub-TLV 250 X - - - - -/- PortCap.SiteIdentifier sub-TLV 250 X - - - - -/-
PortCap.SiteGroupIP sub-TLV 251 X - - - - -/- PortCap.SiteGroupIP sub-TLV 251 X - - - - -/-
PortCap.SiteGroupIPv6 sub-TLV 252 X - - - - -/- PortCap.SiteGroupIPv6 sub-TLV 252 X - - - - -/-
PortCap.AdjServerIP sub-TLV 253 X - - - - -/- PortCap.AdjServerIP sub-TLV 253 X - - - - -/-
PortCap.AdjServerIPv6 sub-TLV 254 X - - - - -/- PortCap.AdjServerIPv6 sub-TLV 254 X - - - - -/-
CAPABILITY.Trill-Version sub-TLV 5 - X - - - T/- CAPABILITY.Trill-Version sub-TLV 5 - X - - - T/-
CAPABILITY.Nickname sub-TLV 6 - X - - - T/- CAPABILITY.Nickname sub-TLV 6 - X - - - T/-
CAPABILITY.Tree sub-TLV 7 - X - - - T/- CAPABILITY.Tree sub-TLV 7 - X - - - T/-
CAPABILITY.Tree Roots Id sub-TLV 8 - X - - - T/- CAPABILITY.Tree Id sub-TLV 8 - X - - - T/-
CAPABILITY.TreeUseRootId sub-TLV 9 - X - - - T/- CAPABILITY.TreeUseRootId sub-TLV 9 - X - - - T/-
CAPABILITY.Int-VLANs sub-TLV 10 - X - X - T/- CAPABILITY.Int-VLANs sub-TLV 10 - X - X - T/-
CAPABILITY.VLAN-Groups sub-TLV 11 - X - - - T/- CAPABILITY.VLAN-Groups sub-TLV 11 - X - - - T/-
CAPABILITY.ITEOPT sub-TLV 12 - X - - - T/- CAPABILITY.ITEOPT sub-TLV 12 - X - - - T/-
CAPABILITY.VMAP sub-TLV 13 - X - - - T/- CAPABILITY.VMAP sub-TLV 13 - X - - - T/-
MT-Capability-TLV (144) - X - - - -/I MT-Capability-TLV (144) - X - - - -/I
MT-Cap.SPB Instance sub-TLV 1 - X - - - -/I MT-Cap.SPB Instance sub-TLV 1 - X - - - -/I
MT-Cap.Service Id. sub-TLV 2 - X - - - -/I MT-Cap.Service Id. sub-TLV 2 - X - - - -/I
TRILL-Nieghbor TLV (145) X - - - - T/- TRILL-Nieghbor TLV (145) X - - - - T/-
EXT-IS.SPB Link Metric sub-TLV 5 - X - - - -/I EXT-IS.SPB Link Metric sub-TLV 5 - X - - - -/I
EXT-IS.MTU sub-TLV 6 - X - - - -/I EXT-IS.MTU sub-TLV 6 - X - - - T/-
MT-EXT-IS.SPB LinkMetric sub-TLV 5 - X - - - -/I MT-EXT-IS.SPB LinkMetric sub-TLV 5 - X - - - -/I
Group Mem Active Source TLV (146) - - - X - -/- Group Mem Active Source TLV (146) - - - X - -/-
GMAS-TLV.GMAS-MAC sub-TLV 1 - - - X - -/- GMAS-TLV.GMAS-MAC sub-TLV 1 - - - X - -/-
GMAS-TLV.GMAS-IP sub-TLV 2 - - - X - -/- GMAS-TLV.GMAS-IP sub-TLV 2 - - - X - -/-
GMAS-TLV.GMAS-IPV6 sub-TLV 3 - - - X - -/- GMAS-TLV.GMAS-IPV6 sub-TLV 3 - - - X - -/-
IANA SHOULD manage the remaining space using the IETF Review method IANA SHOULD manage the remaining space using the IETF Review method
[RFC 5226]. [RFC 5226].
6. Contributing Authors 6. Contributing Authors
skipping to change at page 51, line 33 skipping to change at page 53, line 33
Dino Farinacci Dino Farinacci
Cisco Systems Cisco Systems
170 W Tasman Drive 170 W Tasman Drive
San Jose, CA 95138 San Jose, CA 95138
US US
Email: dino@cisco.com Email: dino@cisco.com
Radia Perlman Radia Perlman
Intel Labs
2200 Mission College Blvd.
Santa Clara, CA 95054-1549
US US
Phone: +1-408-765-8080
Email: Radia@alum.mit.edu Email: Radia@alum.mit.edu
Donald E. Eastlake 3rd Donald E. Eastlake 3rd
Stellar Switches Stellar Switches
155 Beaver Street 155 Beaver Street
Milford, MA 07157 Milford, MA 07157
US US
Phone: +1-508-333-2270
Email: d3e3e3@gmail.com Email: d3e3e3@gmail.com
Peter Ashwood-Smith Peter Ashwood-Smith
Huawei Technologies Canada Co. Ltd. Huawei Technologies Canada Co. Ltd.
411 Legget Drive, Suite 503 411 Legget Drive, Suite 503
Kanta, Ontario K2K 3C9 Kanta, Ontario K2K 3C9
CANADA CANADA
Email: Peter.AshwoodSmith@huawei.com Email: Peter.AshwoodSmith@huawei.com
Don Fedyk Don Fedyk
Alcatel-Lucent Alcatel-Lucent
skipping to change at page 53, line 9 skipping to change at page 55, line 14
7.2. Informative References 7.2. Informative References
[IEEE 802.1aq] [IEEE 802.1aq]
"Standard for Local and Metropolitan Area Networks / "Standard for Local and Metropolitan Area Networks /
Virtual Bridged Local Area Networks / Amendment 9: Virtual Bridged Local Area Networks / Amendment 9:
Shortest Path Bridging, Draft IEEE P802.1aq/D1.5", 2008. Shortest Path Bridging, Draft IEEE P802.1aq/D1.5", 2008.
[RBRIDGES] [RBRIDGES]
Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A. Perlman, R., Eastlake, D., Dutt, D., Gai, S., and A.
Ghanwani, "RBridges: Base Protocol Specification", 2009. Ghanwani, "RBridges: Base Protocol Specification", 2010.
[RFC 1584] [RFC 1584]
Moy, J., "Multicast Extensions to OSPF", March 1994. Moy, J., "Multicast Extensions to OSPF", March 1994.
Author's Address Author's Address
Ayan Banerjee (editor) Ayan Banerjee (editor)
Cisco Systems Cisco Systems
170 W Tasman Drive 170 W Tasman Drive
San Jose, CA 95138 San Jose, CA 95138
 End of changes. 140 change blocks. 
418 lines changed or deleted 486 lines changed or added

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