draft-ietf-isis-layer2-04.txt   draft-ietf-isis-layer2-05.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 D. Ward Intended status: Standards Track D. Ward
Expires: October 18, 2010 Juniper Networks Expires: November 1, 2010 Juniper Networks
R. White R. White
D. Farinacci D. Farinacci
Cisco Systems Cisco Systems
R. Perlman R. Perlman
Intel Labs Intel Labs
D. Eastlake D. Eastlake
Stellar Switches Stellar Switches
P. Ashwood-Smith P. Ashwood-Smith
Huawei Huawei
D. Fedyk D. Fedyk
Alcatel-Lucent Alcatel-Lucent
April 16, 2010 April 30, 2010
Extensions to IS-IS for Layer-2 Systems Extensions to IS-IS for Layer-2 Systems
draft-ietf-isis-layer2-04 draft-ietf-isis-layer2-05
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 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 18, 2010. This Internet-Draft will expire on November 1, 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 30 skipping to change at page 2, line 30
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 . . . . . . . . . . 5 2. PDU, TLV and sub-TLV Enhancements to IS-IS . . . . . . . . . . 5
2.1. The MAC-Reachability TLV . . . . . . . . . . . . . . . . . 5 2.1. The MAC-Reachability TLV . . . . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . . 10 2.2.3. The Group IPv6 Address sub-TLV . . . . . . . . . . . . 10
2.2.4. The SPBV MAC Address sub-TLV . . . . . . . . . . . . . 12 2.3. Multi Topology aware Port Capability TLV . . . . . . . . . 12
2.3. Multi Topology aware Port Capability TLV . . . . . . . . . 14 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 . . . . . . . . . . . . . . . . 16 2.3.3. Appointed Forwarders sub-TLV . . . . . . . . . . . . . 15
2.3.3. Appointed Forwarders sub-TLV . . . . . . . . . . . . . 17 2.3.4. Hop-by-Hop Options (HBHOPT) sub-TLV . . . . . . . . . 16
2.3.4. Hop-by-Hop Options (HBHOPT) sub-TLV . . . . . . . . . 18 2.3.5. Base VLAN-Identifiers sub-TLV . . . . . . . . . . . . 17
2.3.5. Base VLAN-Identifiers sub-TLV . . . . . . . . . . . . 19 2.3.6. SPB Digest sub-TLV . . . . . . . . . . . . . . . . . . 18
2.3.6. SPB Digest sub-TLV . . . . . . . . . . . . . . . . . . 20 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 . . . . . . . . . . . . . . . 22 2.3.9. Site Group IPv6 sub-TLV . . . . . . . . . . . . . . . 21
2.3.9. Site Group IPv6 sub-TLV . . . . . . . . . . . . . . . 23 2.3.10. Adjacency Server IPv4 sub-TLV . . . . . . . . . . . . 22
2.3.10. Adjacency Server IPv4 sub-TLV . . . . . . . . . . . . 23 2.3.11. Adjacency Server IPv6 sub-TLV . . . . . . . . . . . . 22
2.3.11. Adjacency Server IPv6 sub-TLV . . . . . . . . . . . . 24 2.4. Sub-TLVs for the Router Capability TLV . . . . . . . . . . 23
2.4. Sub-TLVs for the Router Capability TLV . . . . . . . . . . 25 2.4.1. The TRILL Version sub-TLV . . . . . . . . . . . . . . 23
2.4.1. The TRILL Version sub-TLV . . . . . . . . . . . . . . 25 2.4.2. The Nickname sub-TLV . . . . . . . . . . . . . . . . . 24
2.4.2. The Nickname sub-TLV . . . . . . . . . . . . . . . . . 26 2.4.3. The Trees sub-TLV . . . . . . . . . . . . . . . . . . 25
2.4.3. The Trees sub-TLV . . . . . . . . . . . . . . . . . . 27 2.4.4. The Tree Identifiers Sub-TLV . . . . . . . . . . . . . 26
2.4.4. The Tree Identifiers Sub-TLV . . . . . . . . . . . . . 28 2.4.5. The Trees Used Identifiers Sub-TLV . . . . . . . . . . 27
2.4.5. The Trees Used Identifiers Sub-TLV . . . . . . . . . . 29 2.4.6. Interested VLANs and Spanning Tree Roots sub-TLV . . . 27
2.4.6. Interested VLANs and Spanning Tree Roots sub-TLV . . . 29 2.4.7. The VLAN Group sub-TLV . . . . . . . . . . . . . . . . 29
2.4.7. The VLAN Group sub-TLV . . . . . . . . . . . . . . . . 31 2.4.8. The Ingress-to-Egress Options (ITEOPT) sub-TLV . . . . 30
2.4.8. The Ingress-to-Egress Options (ITEOPT) sub-TLV . . . . 32 2.4.9. VLAN Mapping (VMAP) sub-TLV . . . . . . . . . . . . . 31
2.4.9. VLAN Mapping (VMAP) sub-TLV . . . . . . . . . . . . . 33
2.5. Multi Topology Aware Capability TLV . . . . . . . . . . . 34 2.5. Multi Topology Aware Capability TLV . . . . . . . . . . . 32
2.5.1. SPB Instance sub-TLV . . . . . . . . . . . . . . . . . 35 2.5.1. SPB Instance sub-TLV . . . . . . . . . . . . . . . . . 33
2.5.2. SPBM Service Identifier and Unicast Address sub-TLV . 38 2.5.2. SPB Opaque ECT Algorithm sub-TLV . . . . . . . . . . . 36
2.5.3. SPBM Service Identifier and Unicast Address sub-TLV . 37
2.5.4. The SPBV MAC Address sub-TLV . . . . . . . . . . . . . 38
2.6. Sub-TLVs of the Extended Reachability TLV . . . . . . . . 39 2.6. Sub-TLVs of the Extended Reachability TLV . . . . . . . . 39
2.6.1. SPB Link Metric sub-TLV . . . . . . . . . . . . . . . 39 2.6.1. SPB Link Metric sub-TLV . . . . . . . . . . . . . . . 39
2.6.2. MTU sub-TLV . . . . . . . . . . . . . . . . . . . . . 40 2.6.2. SPB Opaque ECT Algorithm sub-TLV . . . . . . . . . . . 40
2.6.3. MTU sub-TLV . . . . . . . . . . . . . . . . . . . . . 40
2.7. TRILL Neighbor TLV . . . . . . . . . . . . . . . . . . . . 41 2.7. TRILL Neighbor TLV . . . . . . . . . . . . . . . . . . . . 41
2.8. The Group Membership Active Source TLV . . . . . . . . . . 42 2.8. The Group Membership Active Source TLV . . . . . . . . . . 42
2.8.1. The Group MAC Active Source sub-TLV . . . . . . . . . 43 2.8.1. The Group MAC Active Source sub-TLV . . . . . . . . . 43
2.8.2. The Group IP Active Source sub-TLV . . . . . . . . . . 44 2.8.2. The Group IP Active Source sub-TLV . . . . . . . . . . 45
2.8.3. The Group IPv6 Active Source sub-TLV . . . . . . . . . 46 2.8.3. The Group IPv6 Active Source sub-TLV . . . . . . . . . 47
2.9. PDU Extensions to IS-IS . . . . . . . . . . . . . . . . . 48 2.9. PDU Extensions to IS-IS . . . . . . . . . . . . . . . . . 49
2.9.1. The Multicast Group PDU . . . . . . . . . . . . . . . 48 2.9.1. The Multicast Group PDU . . . . . . . . . . . . . . . 49
2.9.2. The Multicast Group Partial Sequence Number PDU . . . 49 2.9.2. The Multicast Group Partial Sequence Number PDU . . . 50
2.9.3. The Multicast Group Complete Sequence Number PDU . . . 49 2.9.3. The Multicast Group Complete Sequence Number PDU . . . 50
2.9.4. MGROUP PDU related changes to Base protocol . . . . . 49 2.9.4. MGROUP PDU related changes to Base protocol . . . . . 50
2.9.4.1. Enhancements to the flooding process . . . . . . . 50 2.9.4.1. Enhancements to the flooding process . . . . . . . 50
2.9.4.2. Enhancements to Graceful Restart . . . . . . . . . 50 2.9.4.2. Enhancements to Graceful Restart . . . . . . . . . 51
2.9.4.3. Enhancements to the maximum sequence number 2.9.4.3. Enhancements to the maximum sequence number
reached . . . . . . . . . . . . . . . . . . . . . 50 reached . . . . . . . . . . . . . . . . . . . . . 51
2.9.4.4. Enhancements to the SPF . . . . . . . . . . . . . 51 2.9.4.4. Enhancements to the SPF . . . . . . . . . . . . . 51
2.9.5. The TRILL-Hello PDU . . . . . . . . . . . . . . . . . 51 2.9.5. The TRILL-Hello PDU . . . . . . . . . . . . . . . . . 51
2.9.6. The MTU PDU . . . . . . . . . . . . . . . . . . . . . 51 2.9.6. The MTU PDU . . . . . . . . . . . . . . . . . . . . . 52
3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 53 3. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 54
4. Security Considerations . . . . . . . . . . . . . . . . . . . 54 4. Security Considerations . . . . . . . . . . . . . . . . . . . 55
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 55 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 56
6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58 6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 58
6.1. Normative References . . . . . . . . . . . . . . . . . . . 58 6.1. Normative References . . . . . . . . . . . . . . . . . . . 58
6.2. Informative References . . . . . . . . . . . . . . . . . . 58 6.2. Informative References . . . . . . . . . . . . . . . . . . 58
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 59 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 59
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],
[OTV]) that use layer 2 addresses carried in a link state routing [OTV]) that use layer 2 addresses carried in a link state routing
protocol, specifically IS-IS [IS-IS] [RFC1195], to provide true layer protocol, specifically IS-IS [IS-IS] [RFC1195], to provide true layer
2 routing. This document specifies a set of TLVs and sub-TLVs to be 2 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 [802.1aq] or [OTV]. additions and some are specific to [RBRIDGES] or [802.1aq] or [OTV].
This draft does not propose any new forwarding mechanisms using this 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 unicast and multicast attached address information. It also
specifies additional TLVs and sub-TLVs to carry information as specifies additional TLVs and sub-TLVs to carry information as
required by the IETF TRILL and IEEE 802.1aq protocols. required by the IETF TRILL, IEEE 802.1aq and OTV 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 12, line 29 skipping to change at page 12, line 29
the next byte carries the number of sources. It is followed by a the next byte carries the number of sources. It is followed by a
128-bit multicast IPv6 Group Address followed by 128-bit source 128-bit multicast IPv6 Group Address followed by 128-bit source
IPv6 addresses. If the number of sources do not fit in a single IPv6 addresses. If the number of sources do not fit in a single
sub-TLV, it is permitted to have the same group address repeated sub-TLV, it is permitted to have the same group address repeated
with different source addresses repeated in another sub-TLV in with different source addresses repeated 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 only within a 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
The SPBV MAC Address (SPBV-MAC-ADDR) sub-TLV is IS-IS sub-TLV type 4
and has the following format:
+-+-+-+-+-+-+-+-+
| Type=SPBV-ADDR| (1 byte)
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|R|S|R| SPVID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | MAC 1 Address | (1+6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | MAC N Address | (1+6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 4 (SPBV-MAC-ADDR).
o Length: Total number of bytes contained in the value field. The
number of MAC address associated with the SPVID is computed by
(Length - 2)/7.
o SR bits (2-bits) The SR bits are the service requirement parameter
from MMRP. The service requirement parameters have the value 0
(Forward all Groups) and 1 (Forward All Unregistered Groups)
defined. However this attribute may also be missing. So the SR
bits are defined as 0 not declared, 1 Forward all Groups and 2
Forward All Unregistered Groups. These bits have two Reserved
bits set before them.
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
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
value should be populated with the Base VID and the MAC can be
populated.
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
Address with SPVID of source should be populated (for the bridge
advertising this Group MAC), and installed in the FDB of transit
bridges, when the bridge computing the trees is on the
corresponding ECT-ALGORITHM shortest path between the bridge
advertising this MAC with the T bit set, and any receiver of this
Group MAC Address. A bridge that does not advertise this bit set
for an Group MAC Address should have no forwarding state installed
for traffic originating from that bridge on other transit bridges
in the network.
o R Bit (1-bit) This is the Receive allowed Bit for the following
Group MAC Address. This is an indication that SPBV Group MAC
Addresses as receiver should be populated (for bridges advertising
this Group MAC Address with the T bit set) and installed when the
bridge computing the trees lies on the corresponding shortest path
for this ECT-ALGORITHM between this receiver and any transmitter
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
Group MAC Address because transit bridges will not install
multicast forwarding state towards it in their FDBs or the traffic
is explicitly filtered.
o MAC Address (48-bits) The MAC is address is either a group address
or an individual address. Individual addresses are optional and
normal MAC learning can be used. When the MAC address is a group
address it declares this bridge as part of the multicast interest
for this destination MAC address. Multicast trees can be
efficiently constructed for destination by populating multicast
FDB entries for the subset of the shortest path tree that connects
the bridges supporting the multicast address. This replaces the
function of MMRP for SPTs. The T and R bits above 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
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-TLVs | | sub-TLVs |
skipping to change at page 19, line 29 skipping to change at page 17, line 43
o Value: Either 0x00 followed by implementation information for bit o Value: Either 0x00 followed by implementation information for bit
encoded options or a non-zero option type byte followed by option encoded options or a non-zero option type byte followed by option
dependent information for that option. dependent information for that option.
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) that the VIDs and the Base VIDs and VIDs or Backbone-VIDs (B-VIDs) that
are in use. This information should be the same on all bridges in are in use. This information should be the same on all bridges in
the 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 neighbors with respect to this sub-TLV are
temporarily allowed but the Base-VID must agree and use a spanning temporarily allowed but at least the active the Base-VID must agree
tree algorithm. and use the same ECT-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) |
+-----------------------------------------------+ +-----------------------------------------------+
| ......................... | | ......................... |
+-----------------------------------------------+ +-----------------------------------------------+
skipping to change at page 20, line 19 skipping to change at page 18, line 36
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
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 associated 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 ECT-ALGORITHM 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 digest for This sub-TLV is added to an IIH PDU to indicate the digest for
Multiple spanning tree configuration Digests (MCID) and the IS-IS Multiple spanning tree configuration Digests (MCID) and the IS-IS
agreement Digest. This information should be the same on all bridges agreement Digest. This information should be the same on all bridges
in the topology identified by MT-PORT-CAP TLV it is being carried. in the topology identified by MT-PORT-CAP TLV it is being carried.
These digests indicate when the configuration and the topology are These digests indicate when the configuration and the topology are
synchronized and are used to control the updating of forwarding synchronized and are used to control the updating of forwarding
information. The MCID is controlled solely by configuration and is a information. The MCID is controlled solely by configuration and is a
digest of the allocated VIDs to various protocols. Two MCIDs are digest of the allocated VIDs to various protocols. Two MCIDs are
carried to allow transitions when the configuration changes are non- carried to allow transitions when the configuration changes are non-
critical. During the propagation of LSPs the agreement digest will critical. During the propagation of LSPs the agreement digest will
vary between neighbors until the LSPs are common. During that period vary between neighbors until the LSPs are common. The digest is a
switches or bridges running SPB will not allow multicast forwarding summarized means of determining agreement between nodes on the
between neighbors that have differing digests. Discrepancies between distance to all multicast roots, hence is essential for loop
neighbors with respect to this sub-TLV are temporarily allowed but prevention. During the propagation of LSPs the agreement digest will
the Base-VID must agree and use a spanning tree algorithm. vary between neighbors until the required portions of LSPs are
common. For each shortest path tree where it has been determined the
distance to the root has changed, multicast forwarding is blocked
until the exchanged digests match. Discrepancies between neighbors
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) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 30, line 10 skipping to change at page 28, line 10
o Nickname: If this is set to 0, then it applies to all nicknames o Nickname: If this is set to 0, then it applies to all nicknames
generated by the node. It may alternatively be set to a specific generated by the node. It may alternatively be set to a specific
nickname, in the event a node wants to segregate traffic using nickname, in the event a node wants to segregate traffic using
multiple nicknames. multiple nicknames.
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 set as zero and are ignored on receipt. The VLAN start and end
end IDs are inclusive. A range of one VLAN ID is indicated by IDs are inclusive. A range of one VLAN ID is indicated by setting
setting them both to that VLAN ID value. The Appointed Forwarder them both to that VLAN ID value. The Appointed Forwarder Status
Status Lost Counter is also included here. It is a count of how Lost Counter is also included here. It is a count of how many
many times a port that was appointed forwarder for the VLANs in times a port that was appointed forwarder for the VLANs in the
the range given has lost the status of being an appointed range given has lost the status of being an appointed forwarder.
forwarder. It has the following format: It has the following format:
0 1 2 3 4 - 15 16 - 19 20 - 31 0 1 2 3 4 - 15 16 - 19 20 - 31
+----+----+----+----+------------+----------+------------+ +----+----+----+----+------------+----------+------------+
| M4 | M6 | R | R | VLAN start | Reserved | VLAN end | | M4 | M6 | R | R | VLAN start | Reserved | VLAN end |
+----+----+----+----+------------+----------+------------+ +----+----+----+----+------------+----------+------------+
| Appointed Forwarder Status Lost Counter | | Appointed Forwarder Status Lost Counter |
+----+----+----+----+------------+----------+------------+ +----+----+----+----+------------+----------+------------+
o Root Bridges: The list of zero or more spanning tree root bridge o Root Bridges: The list of zero or more spanning tree root bridge
IDs is the set of root bridge IDs seen for all ports for which the IDs is the set of root bridge IDs seen for all ports for which the
Intermediate System is appointed forwarder for the VLANs in the Intermediate System is appointed forwarder for the VLANs in the
skipping to change at page 31, line 28 skipping to change at page 29, line 28
settings for a given vlan, the procedure used to choose which copy settings for a given vlan, the procedure used to choose which copy
shall be 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 This sub-TLV is carried within the CAPABILITY TLV in a level-1
multicast group PDU. multicast group PDU.
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 set 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) | | Primary VLAN ID (2 bytes) |
skipping to change at page 32, line 5 skipping to change at page 30, line 5
| more Secondary VLAN IDs ... | | 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 a secondary VLAN in the VLAN
learning is shared at the Intermediate System that announces this Group.
sub-TLV.
This sub-TLV may appear zero, one, or multiple times. It should be This sub-TLV indicates that shared VLAN learning is occurring at the
noted that all VLAN ID values described above have a 4 bit reserved announcing Intermediate System between the listed VLANs. This sub-
section followed by a 12-bit value. It is carried within the TLV may appear zero, one, or multiple times. It should be noted that
CAPABILITY TLV. 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 35, line 37 skipping to change at page 33, line 37
2.5.1. SPB Instance sub-TLV 2.5.1. SPB Instance sub-TLV
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 MUST be carried within the MT-Capability TLV in the
fragment ZERO LSP. If there was an additional SPB instance it MUST
be declared under a separate MT-Topology and also carried in the
fragment ZERO LSP. fragment ZERO LSP.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = SPB-Inst| |Type = SPB-Inst|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | 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) |
skipping to change at page 36, line 26 skipping to change at page 34, line 26
| 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)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num of Trees | (1 bytes) | Num of Trees | (1 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID (1) Tuples (8 bytes) | | VLAN-ID (1) Tuples (8 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN-ID (N) Tuples (8 bytes) | | VLAN-ID (N) Tuples (8 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ECT-Alg-Len | (1 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Algorithm (32 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Information (variable ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
where VLAN-ID tuples have the format as: where VLAN-ID tuples have the format as:
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
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|U|M|A| Res | |U|M|A| Res |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ECT - Algorithm (32 bits) | | ECT - Algorithm (32 bits) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Base VID 12 bits) | SPTVID 12 bits) | | Base VID (12 bits) | SPVID (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.
skipping to change at page 37, line 20 skipping to change at page 35, line 13
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. Allocation of SPSourceID is in configured and must be unique. Allocation of SPSourceID is
[IEEE 802.1aq]. Bridges running SPBM will allocate an SPSourceID defined in [IEEE 802.1aq]. Bridges running SPBM will allocate an
if they are not configured with an explicit SPSourceID. The V Bit SPSourceID if they are not configured with an explicit SPSourceID.
allows neighbor bridges to determine if the auto allocation was The V Bit allows neighbor bridges to determine if the auto
enabled. In the rare chance of a collision of SPsourceID the allocation was enabled. In the rare chance of a collision of
bridge with the highest priority Bridge Identifier will win SPsourceID the bridge with the highest priority Bridge Identifier
conflicts and the lower priority Bridge will be re-allocated or if will win conflicts and the lower priority Bridge will be re-
the lower priority Bridge is configured it will not be allowed to allocated or if the lower priority Bridge is configured it will
joint the SPT Region. 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 a 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. These define the standard ECTs.
o Each VID Tuple consists of: o Each VID Tuple consists of:
* 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. The VID allocation logic details are in [IEEE auto allocation. The VID allocation logic details are in [IEEE
802.1aq]. Since SPVIDs are from a small pool of resources 802.1aq]. Since SPVIDs are from a small pool of resources
(1000 or less) the chances of collision are high. To allow (1000 or less) the chances of collision are high. To allow
auto allocation LSPs are exchanged with the allocated bridge auto allocation LSPs are exchanged with the allocated bridge
setting the SPVID to 0. setting the SPVID to 0.
o ECT-ALG-LEN (1 byte): This gives the length of the ECT Algorithm. * ECT-ALGORITHM (4-bytes) ECT-ALGORITHM is advertised when the
bridge supports a given ECT-ALGORITHM (by OUI/Index) on a given
VID. This declaration must match the declaration in the Hello
PDU originating from the same bridge. The ECT-ALGORITHM, BASE-
VID should match what is generated in the Hellos of the same
node. The ECT-ALGORITHM, BASE-VIDs pairs can come in any order
however.
o ECT-ALGORITHM (4-bytes) ECT-ALGORITHM is advertised when the * Base VID (12-bits) The Base-VID that associated the SPT Set via
bridge supports a given ECT-ALGORITHM (by OUI/Index) on a given the ECT-ALGORITHM.
VID. This declaration must match the declaration in the Hello PDU
originating from the same bridge. The ECT-ALGORITHM, BASE-VID
should match what is generated in the Hellos of the same node.
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 * SPVID (12-bits) The SPVID is the Shortest Path VID when using
the ECT-ALGORITHM. SPBV mode. It is not defined for SPBM Mode and should be 0 in
SPBM mode.
o SPVID (12-bits) The SPVID is the Shortest Path VID when using SPBV 2.5.2. SPB Opaque ECT Algorithm sub-TLV
mode. It is not defined for SPBM Mode and should be 0 in SPBM
mode.
o an opaque ECT Data sub-TLV (type TBD) whose first 32 bits are the There are multiple ECT algorithms defined for SPB, however for the
ECT-ALGORITHM which this data applies to. future additional algorithms may be defined. These algorithms would
use this optional TLV to define new algorithm tie breaking data.
There are two broad classes of algorithm, one which uses nodal data
to break ties and one which uses link data to break ties, as a result
this TLV can associate opaque data with a node or an adjacency or
both.
2.5.2. SPBM Service Identifier and Unicast Address sub-TLV This sub-TLV SHOULD be carried within the MT-Capability TLV. (along
with a valid SPB Instance sub-TLV (2.5.1)) and/or this sub-TLV SHOULD
be carried within the Extended Reachability TLV (type 22). Multiple
copies of this sub-TLV may be carried for different ECT-ALGORITHMs
both for a node and for an adjacency.
+-+-+-+-+-+-+-+-+
|Type = SPB-OALG|
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Algorithm (4 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Information (variable) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to SPB OALG sub-TLV 2 [TBD].
o Length: Total number of bytes contained in the value field.
o ECT-ALGORITHM: ECT-ALGORITHM is advertised when the bridge
supports a given ECT-ALGORITHM (by OUI/Index) on a given VID.
o ECT Information: ECT-ALGORITHM Information of variable length.
2.5.3. 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.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type = SPBM-SI | |Type = SPBM-SI |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
skipping to change at page 39, line 4 skipping to change at page 37, line 29
| B-MAC ADDRESS (6 bytes) | | B-MAC ADDRESS (6 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Res. | Base-VID | ( 2 bytes) | Res. | Base-VID | ( 2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #1 | (1+3 bytes) |T|R| Reserved | ISID #1 | (1+3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #2 | (1+3 bytes) |T|R| Reserved | ISID #2 | (1+3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | ISID #n | (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 3 [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
additional B-MAC. additional B-MAC.
skipping to change at page 39, line 30 skipping to change at page 38, line 7
forwarding state using the ISID and the node's SPSOURCEID to forwarding state using the ISID and the node's SPSOURCEID to
construct a multicast DA as described in IEEE 802.1aq LSB. Each construct a multicast DA as described in IEEE 802.1aq LSB. Each
ISID has a Transmit(T) and Receive(R) bit which indicates if the ISID has a Transmit(T) and Receive(R) bit which indicates if the
membership is as a Transmitter/Receiver or both (with both bits membership is as a Transmitter/Receiver or both (with both bits
set). In the case where the Transmit(T) and Receive(R) bits are set). In the case where the Transmit(T) and Receive(R) bits are
both zero, the ISID is ignored. If more ISIDs are associated with both zero, the ISID is ignored. If more ISIDs are associated with
a particular B-MAC than can fit in a single sub-TLV, this sub-TLV a particular B-MAC than can fit in a single sub-TLV, this sub-TLV
can be repeated with the same B-MAC but with different ISID can be repeated with the same B-MAC but with different ISID
values. values.
The SPBM Service Identifier sub-TLV SHOULD be carried within the MT-
Capability TLV and can occur multiple times in any LSP fragment.
2.5.4. The SPBV MAC Address sub-TLV
The SPBV MAC Address (SPBV-MAC-ADDR) sub-TLV is IS-IS sub-TLV type 4
and has the following format:
+-+-+-+-+-+-+-+-+
| Type=SPBV-ADDR| (1 byte)
+-+-+-+-+-+-+-+-+
| Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|R|S|R| SPVID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | MAC 1 Address | (1+6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|T|R| Reserved | MAC N Address | (1+6 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to 4 (SPBV-MAC-ADDR).
o Length: Total number of bytes contained in the value field. The
number of MAC address associated with the SPVID is computed by
(Length - 2)/7.
o SR bits (2-bits) The SR bits are the service requirement parameter
from MMRP. The service requirement parameters have the value 0
(Forward all Groups) and 1 (Forward All Unregistered Groups)
defined. However this attribute may also be missing. So the SR
bits are defined as 0 not declared, 1 Forward all Groups and 2
Forward All Unregistered Groups. These bits have two Reserved
bits set before them.
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
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
value should be populated with the Base VID and the MAC can be
populated.
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
Address with SPVID of source should be populated (for the bridge
advertising this Group MAC), and installed in the FDB of transit
bridges, when the bridge computing the trees is on the
corresponding ECT-ALGORITHM shortest path between the bridge
advertising this MAC with the T bit set, and any receiver of this
Group MAC Address. A bridge that does not advertise this bit set
for an Group MAC Address should have no forwarding state installed
for traffic originating from that bridge on other transit bridges
in the network.
o R Bit (1-bit) This is the Receive allowed Bit for the following
Group MAC Address. This is an indication that SPBV Group MAC
Addresses as receiver should be populated (for bridges advertising
this Group MAC Address with the T bit set) and installed when the
bridge computing the trees lies on the corresponding shortest path
for this ECT-ALGORITHM between this receiver and any transmitter
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
Group MAC Address because transit bridges will not install
multicast forwarding state towards it in their FDBs or the traffic
is explicitly filtered.
o MAC Address (48-bits) The MAC is address is either a group address
or an individual address. Individual addresses are optional and
normal MAC learning can be used. When the MAC address is a group
address it declares this bridge as part of the multicast interest
for this destination MAC address. Multicast trees can be
efficiently constructed for destination by populating multicast
FDB entries for the subset of the shortest path tree that connects
the bridges supporting the multicast address. This replaces the
function of MMRP for SPTs. The T and R bits above 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 SHOULD be carried within the MT-Capability
TLV and can occur multiple times in any LSP fragment.
2.6. Sub-TLVs of the Extended Reachability TLV 2.6. Sub-TLVs of the Extended Reachability TLV
This section specifies two new sub-TLVs that appear only within the This section specifies three new sub-TLVs that appear only within the
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 within the Extended Reachability The SPB Link Metric sub-TLV occurs within the Extended Reachability
TLV (type 22), or the Multi Topology Intermediate System TLV (type TLV (type 22), or the Multi Topology Intermediate System TLV (type
222). If this sub TLV is not present for an ISIS adjacency then that 222). If this sub TLV is not present for an ISIS adjacency then that
adjacency MUST NOT carry SPB traffic for the given topology instance. adjacency MUST NOT carry SPB traffic for the given topology instance.
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=SPB-Metric| |Type=SPB-Metric|
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| SPB-LINK-METRIC | (3 bytes) | SPB-LINK-METRIC | (3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Num of ports | (1 byte) | Num of ports | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Port Identifier | ( 2 bytes) | Port Identifier | ( 2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Algorithm (32 bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Opaque ECT Information (variable ) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV Type, set to SPB Link Metric sub-TLV 5 [TBD]. o Type: sub-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 sub-TLV (type TBD) whose first 32 bits are the o an opaque ECT Data sub-TLV (type TBD) whose first 32 bits are the
ECT-ALGORITHM to which this data applies. ECT-ALGORITHM to which this data applies.
2.6.2. MTU sub-TLV 2.6.2. SPB Opaque ECT Algorithm sub-TLV
This sub-TLV is identical in format and type as the 2.5.2 SPB Opaque
ECT Algorithm sub-TLV and carries future opaque data for the purpose
of extending ECT behavior. Multiple copies of the sub-TLV may occur
for different ECT-ALGORITHMs.
2.6.3. 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 | (1 byte) |F| Reserved | (1 byte)
skipping to change at page 56, line 9 skipping to change at page 56, line 36
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 MT Port Capability TLV, the Extended for the Group Address TLV, the MT Port Capability TLV, the Extended
Reachability TLV, the MT-Capability TLV, and the Capability TLV. The Reachability TLV, the MT-Capability TLV, and the Capability TLV. The
TLV and sub-TLVs are given below along with technologies that use TLV and sub-TLVs are given below along with technologies that use
them. them.
IIH LSP SNP MGROUP MGROUP TRILL/ IIH LSP SNP MGROUP MGROUP TRILL/
LSP SNP IEEE/OTV LSP SNP IEEE/OTV
MAC-RI TLV (141) - X - - - T/I/O MAC-RI TLV (141) - X - - - T/I/O
GADDR-TLV (142) - - - X - T/I/O GADDR-TLV (142) - - - X - T/-/O
GADDR-TLV.GMAC-ADDR sub-TLV 1 - - - X - T/-/O GADDR-TLV.GMAC-ADDR sub-TLV 1 - - - X - T/-/O
GADDR-TLV.GMAC-IP sub-TLV 2 - - - X - T/-/O GADDR-TLV.GMAC-IP sub-TLV 2 - - - X - T/-/O
GADDR-TLV.GMAC-IPV6 sub-TLV 3 - - - X - T/-/O GADDR-TLV.GMAC-IPV6 sub-TLV 3 - - - X - T/-/O
GADDR-TLV.SPBV-MAC-ADDR sub-TLV 4 - - - X - -/I/-
MT-Port-Cap-TLV (143) X - - - - T/I/O MT-Port-Cap-TLV (143) X - - - - T/I/O
PortCap.VLAN and Flags sub-TLV 1 X - - - - T/-/- PortCap.VLAN and Flags sub-TLV 1 X - - - - T/-/-
PortCap.Enabled-VLANs sub-TLV 2 X - - - - T/-/- PortCap.Enabled-VLANs sub-TLV 2 X - - - - T/-/-
PortCap.AppointedFwrdrs sub-TLV 3 X - - - - T/-/- PortCap.AppointedFwrdrs sub-TLV 3 X - - - - T/-/-
PortCap.HBHOPT sub-TLV 4 X - - - - T/-/- PortCap.HBHOPT sub-TLV 4 X - - - - T/-/-
PortCap.BaseVLANID sub-TLV 5 X - - - - -/I/- PortCap.BaseVLANID sub-TLV 5 X - - - - -/I/-
PortCap.SPBDigest sub-TLV 6 X - - - - -/I/- PortCap.SPBDigest sub-TLV 6 X - - - - -/I/-
PortCap.SiteIdentifier sub-TLV 250 X - - - - -/-/O PortCap.SiteIdentifier sub-TLV 250 X - - - - -/-/O
PortCap.SiteGroupIP sub-TLV 251 X - - - - -/-/O PortCap.SiteGroupIP sub-TLV 251 X - - - - -/-/O
PortCap.SiteGroupIPv6 sub-TLV 252 X - - - - -/-/O PortCap.SiteGroupIPv6 sub-TLV 252 X - - - - -/-/O
PortCap.AdjServerIP sub-TLV 253 X - - - - -/-/O PortCap.AdjServerIP sub-TLV 253 X - - - - -/-/O
PortCap.AdjServerIPv6 sub-TLV 254 X - - - - -/-/O PortCap.AdjServerIPv6 sub-TLV 254 X - - - - -/-/O
CAPABILITY.Trill-Version sub-TLV 5 - X - - - T/-/-
CAPABILITY.Trill-Version sub-TLV 5 - X - 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 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 - T/-/- CAPABILITY.Int-VLANs sub-TLV 10 - - - 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.Opaque Algorithm sub-TLV 2 - X - - - -/I/-
MT-Cap.Service Id. sub-TLV 3 - X - - - -/I/-
MT-Cap.SPBV-MAC-ADDR sub-TLV 4 - 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 - - - T/-/- 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 - -/-/O Group Mem Active Source TLV (146) - - - X - -/-/O
GMAS-TLV.GMAS-MAC sub-TLV 1 - - - X - -/-/O GMAS-TLV.GMAS-MAC sub-TLV 1 - - - X - -/-/O
GMAS-TLV.GMAS-IP sub-TLV 2 - - - X - -/-/O GMAS-TLV.GMAS-IP sub-TLV 2 - - - X - -/-/O
GMAS-TLV.GMAS-IPV6 sub-TLV 3 - - - X - -/-/O GMAS-TLV.GMAS-IPV6 sub-TLV 3 - - - X - -/-/O
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. References 6. References
6.1. Normative References 6.1. Normative References
[IS-IS] ISO/IEC 10589, "Intermediate System to Intermediate System [IS-IS] ISO/IEC 10589, "Intermediate System to Intermediate System
Intra-Domain Routing Exchange Protocol for use in Intra-Domain Routing Exchange Protocol for use in
Conjunction with the Protocol for Providing the Conjunction with the Protocol for Providing the
 End of changes. 42 change blocks. 
194 lines changed or deleted 238 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/