draft-ietf-isis-rfc6326bis-01.txt   draft-ietf-isis-rfc6326bis-02.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Network Working Group Donald Eastlake Network Working Group Donald Eastlake
INTERNET-DRAFT Huawei INTERNET-DRAFT Huawei
Intended status: Proposed Standard Tissa Senevirathne Intended status: Proposed Standard Tissa Senevirathne
Obsoletes: 6326 Cisco Obsoletes: 6326 Cisco
Anoop Ghanwani Anoop Ghanwani
Dell Dell
Dinesh Dutt Dinesh Dutt
Cumulus Networks Cumulus Networks
Ayan Banerjee Ayan Banerjee
Insieme Networks Insieme Networks
Expires: October 7, 2013 April 8, 2013 Expires: July 21, 2014 January 22, 2014
Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS Transparent Interconnection of Lots of Links (TRILL) Use of IS-IS
<draft-ietf-isis-rfc6326bis-01.txt> <draft-ietf-isis-rfc6326bis-02.txt>
Abstract Abstract
The IETF TRILL (Transparent Interconnection of Lots of Links) The IETF TRILL (Transparent Interconnection of Lots of Links)
protocol provides optimal pair-wise data frame forwarding without protocol provides optimal pair-wise data frame forwarding without
configuration in multi-hop networks with arbitrary topology and link configuration in multi-hop networks with arbitrary topology and link
technology, and support for multipathing of both unicast and technology, and support for multipathing of both unicast and
multicast traffic. This document specifies the data formats and code multicast traffic. This document specifies the data formats and code
points for the IS-IS extensions to support TRILL. These data formats points for the IS-IS extensions to support TRILL. These data formats
and code points may also be used by technologies other than TRILL. and code points may also be used by technologies other than TRILL.
skipping to change at page 2, line 51 skipping to change at page 2, line 51
4.1 TRILL IIH PDUs......................................35 4.1 TRILL IIH PDUs......................................35
4.2 Area Address........................................35 4.2 Area Address........................................35
4.3 Protocols Supported.................................35 4.3 Protocols Supported.................................35
4.4 Link State PDUs (LSPs)..............................36 4.4 Link State PDUs (LSPs)..............................36
4.5 Originating LSP Buffer Size.........................36 4.5 Originating LSP Buffer Size.........................36
5. IANA Considerations....................................37 5. IANA Considerations....................................37
5.1 TLVs................................................37 5.1 TLVs................................................37
5.2 sub-TLVs............................................37 5.2 sub-TLVs............................................37
5.3 PDUs................................................39 5.3 PDUs................................................39
5.4 Reserved and Capability Bits........................39 5.4 Reserved and Capability Bits........................39
5.5 TRILL Neighbor Record Flags.........................39 5.5 TRILL Neighbor Record Flags.........................40
6. Security Considerations................................41 6. Security Considerations................................41
7. Change from RFC 6326...................................42 7. Change from RFC 6326...................................42
8. Normative References...................................44 8. Normative References...................................44
9. Informative References.................................45 9. Informative References.................................45
Acknowledgements..........................................46 Acknowledgements..........................................47
Authors' Addresses........................................47 Authors' Addresses........................................48
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
1. Introduction 1. Introduction
The IETF TRILL (Transparent Interconnection of Lots of Links) The IETF TRILL (Transparent Interconnection of Lots of Links)
protocol [RFC6325] [RFC6327] provides transparent forwarding in protocol [RFC6325] [RFC6327] provides transparent forwarding in
multi-hop networks with arbitrary topology and link technologies multi-hop networks with arbitrary topology and link technologies
using a header with a hop count and link state routing. TRILL using a header with a hop count and link state routing. TRILL
provides optimal pair-wise forwarding without configuration, safe provides optimal pair-wise forwarding without configuration, safe
skipping to change at page 7, line 24 skipping to change at page 7, line 24
listener not restricted by source. It then has a 6-byte (48-bit) listener not restricted by source. It then has a 6-byte (48-bit)
multicast MAC address followed by 6-byte source MAC addresses. If multicast MAC address followed by 6-byte source MAC addresses. If
the sources do not fit in a single sub-TLV, the same group address the sources do not fit in a single sub-TLV, the same group address
may be repeated with different source addresses in another sub-TLV may be repeated with different source addresses in another sub-TLV
of another instance of the Group Address TLV. of another instance of the Group Address TLV.
The GMAC-ADDR sub-TLV is carried only within a GADDR TLV. The GMAC-ADDR sub-TLV is carried only within a GADDR TLV.
2.1.2 Group IPv4 Address Sub-TLV 2.1.2 Group IPv4 Address Sub-TLV
The Group IPv4 Address (GIP-ADDR) sub-TLV is IS-IS sub-TLV type TBD The Group IPv4 Address (GIP-ADDR) sub-TLV is IS-IS sub-TLV type TBDa
[2 suggested] within the GADDR TLV. It has the same format as the [2 suggested] within the GADDR TLV. It has the same format as the
Group MAC Address sub-TLV described in Section 2.1.1 except that k=4. Group MAC Address sub-TLV described in Section 2.1.1 except that k=4.
The fields are as follows: The fields are as follows:
o Type: sub-TLV Type, set to TBD [2 suggested] (GIP-ADDR). o Type: sub-TLV Type, set to TBDa [2 suggested] (GIP-ADDR).
o Length: 5 + m + k*n = 5 + m + 4*n where m is the number of group o Length: 5 + m + k*n = 5 + m + 4*n where m is the number of group
records and n is the sum of the number of group and source records and n is the sum of the number of group and source
addresses. addresses.
o Topology-Id: This field carries a topology ID [RFC5120] or zero if o Topology-Id: This field carries a topology ID [RFC5120] or zero if
topologies are not in use. topologies are not in use.
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.
skipping to change at page 8, line 13 skipping to change at page 8, line 13
source addresses in another sub-TLV of another instance of the source addresses in another sub-TLV of another instance of the
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
Group Address TLV. Group Address TLV.
The GIP-ADDR sub-TLV is carried only within a GADDR TLV. The GIP-ADDR sub-TLV is carried only within a GADDR TLV.
2.1.3 Group IPv6 Address Sub-TLV 2.1.3 Group IPv6 Address Sub-TLV
The Group IPv6 Address (GIPV6-ADDR) sub-TLV is IS-IS sub-TLV type TBD The Group IPv6 Address (GIPV6-ADDR) sub-TLV is IS-IS sub-TLV type
[3 suggested] within the GADDR TLV. It has the same format as the TBDb [3 suggested] within the GADDR TLV. It has the same format as
Group MAC Address sub-TLV described in Section 2.1.1 except that the Group MAC Address sub-TLV described in Section 2.1.1 except that
k=16. The fields are as follows: k=16. The fields are as follows:
o Type: sub-TLV Type, set to TBD [3 suggested] (GIPV6-ADDR). o Type: sub-TLV Type, set to TBDb [3 suggested] (GIPV6-ADDR).
o Length: 5 + m + k*n = 5 + m + 16*n where m is the number of group o Length: 5 + m + k*n = 5 + m + 16*n where m is the number of group
records and n is the sum of the number of group and source records and n is the sum of the number of group and source
addresses. addresses.
o Topology-Id: This field carries a topology ID [RFC5120] or zero if o Topology-Id: This field carries a topology ID [RFC5120] or zero if
topologies are not in use. topologies are not in use.
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.
skipping to change at page 9, line 43 skipping to change at page 9, line 43
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source 1 Address (k bytes) | | Source 1 Address (k bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source 2 Address (k bytes) | | Source 2 Address (k bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ..... | | ..... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Source M Address (k bytes) | | Source M Address (k bytes) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: GADDR sub-TLV Type, set to TBD [4 suggested] (GLMAC-ADDR). o Type: GADDR sub-TLV Type, set to TBDc [4 suggested] (GLMAC-ADDR).
o Length: 6 + m + k*n = 6 + m + 6*n where m is the number of group o Length: 6 + m + k*n = 6 + m + 6*n where m is the number of group
records and n is the sum of the number of group and source records and n is the sum of the number of group and source
addresses. addresses.
o RESV: Reserved. 4-bit field that MUST be sent as zero and ignored o RESV: Reserved. 4-bit field that MUST be sent as zero and ignored
on receipt. on receipt.
o Topology-ID: This field carries a topology ID [RFC5120] or zero if o Topology-ID: This field carries a topology ID [RFC5120] or zero if
topologies are not in use. topologies are not in use.
o Label: This carries the fine-grained label identifier for all o Label: This carries the fine-grained label [RFCfgl] identifier for
subsequent MAC addresses in this sub-TLV, or the value zero if no all subsequent MAC addresses in this sub-TLV, or the value zero if
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
label is specified. no label is specified.
o Number of Group Records: A 1-byte unsigned integer that is the o Number of Group Records: A 1-byte unsigned integer that is the
number of group records in this sub-TLV. number of group records in this sub-TLV.
o Group Record: Each group record carries the number of sources. If o Group Record: Each group record carries the number of sources. If
this field is zero, it indicates a listener for (*,G), that is, a this field is zero, it indicates a listener for (*,G), that is, a
listener not restricted by source. It then has a 6-byte (48-bit) listener not restricted by source. It then has a 6-byte (48-bit)
multicast address followed by 6-byte source MAC addresses. If the multicast address followed by 6-byte source MAC addresses. If the
sources do not fit in a single sub-TLV, the same group address may sources do not fit in a single sub-TLV, the same group address may
be repeated with different source addresses in another sub-TLV of be repeated with different source addresses in another sub-TLV of
another instance of the Group Address TLV. another instance of the Group Address TLV.
The GLMAC-ADDR sub-TLV is carried only within a GADDR TLV. The GLMAC-ADDR sub-TLV is carried only within a GADDR TLV.
2.1.5 Group Labeled IPv4 Address Sub-TLV 2.1.5 Group Labeled IPv4 Address Sub-TLV
The Group Labeled IPv4 Address (GLIP-ADDR) sub-TLV is IS-IS sub-TLV The Group Labeled IPv4 Address (GLIP-ADDR) sub-TLV is IS-IS sub-TLV
type TBD [5 suggested] within the GADDR TLV. It has the same format type TBDd [5 suggested] within the GADDR TLV. It has the same format
as the Group Labeled MAC Address sub-TLV described in Section 2.1.4 as the Group Labeled MAC Address sub-TLV described in Section 2.1.4
except that k=4. The fields are as follows: except that k=4. The fields are as follows:
o Type: sub-TLV Type, set to TBD [5 suggested] (GLIP-ADDR). o Type: sub-TLV Type, set to TBDd [5 suggested] (GLIP-ADDR).
o Length: 6 + m + k*n = 6 + m + 4*n where m is the number of group o Length: 6 + m + k*n = 6 + m + 4*n where m is the number of group
records and n is the sum of the number of group and source records and n is the sum of the number of group and source
addresses. addresses.
o Topology-Id: This field carries a topology ID [RFC5120] or zero if o Topology-Id: This field carries a topology ID [RFC5120] or zero if
topologies are not in use. topologies are not in use.
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 Label: This carries the fine-grained label identifier for all o Label: This carries the fine-grained label [RFCfgl] identifier for
subsequent IPv4 addresses in this sub-TLV, or the value zero if no all subsequent IPv4 addresses in this sub-TLV, or the value zero
label is specified. if no label 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 sub-TLV. number of group records in this sub-TLV.
o Group Record: Each group record carries the number of sources. If o Group Record: Each group record carries the number of sources. If
this field is zero, it indicates a listener for (*,G), that is, a this field is zero, it indicates a listener for (*,G), that is, a
listener not restricted by source. It then has a 4-byte (32-bit) listener not restricted by source. It then has a 4-byte (32-bit)
IPv4 Group Address followed by 4-byte source IPv4 addresses. If IPv4 Group Address followed by 4-byte source IPv4 addresses. If
the number of sources do not fit in a single sub-TLV, it is the number of sources do not fit in a single sub-TLV, it is
permitted to have the same group address repeated with different permitted to have the same group address repeated with different
skipping to change at page 11, line 14 skipping to change at page 11, line 14
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
Group Address TLV. Group Address TLV.
The GLIP-ADDR sub-TLV is carried only within a GADDR TLV. The GLIP-ADDR sub-TLV is carried only within a GADDR TLV.
2.1.6 Group Labeled IPv6 Address Sub-TLV 2.1.6 Group Labeled IPv6 Address Sub-TLV
The Group Labeled IPv6 Address (GLIPV6-ADDR) sub-TLV is IS-IS sub-TLV The Group Labeled IPv6 Address (GLIPV6-ADDR) sub-TLV is IS-IS sub-TLV
type TBD [6 suggested] within the GADDR TLV. It has the same format type TBDe [6 suggested] within the GADDR TLV. It has the same format
as the Group Labeled MAC Address sub-TLV described in Section 2.1.4 as the Group Labeled MAC Address sub-TLV described in Section 2.1.4
except that k=16. The fields are as follows: except that k=16. The fields are as follows:
o Type: sub-TLV Type, set to TBD [6 suggested] (GLIPV6-ADDR). o Type: sub-TLV Type, set to TBDe [6 suggested] (GLIPV6-ADDR).
o Length: 6 + m + k*n = 6 + m + 16*n where m is the number of group o Length: 6 + m + k*n = 6 + m + 16*n where m is the number of group
records and n is the sum of the number of group and source records and n is the sum of the number of group and source
addresses. addresses.
o Topology-Id: This field carries a topology ID [RFC5120] or zero if o Topology-Id: This field carries a topology ID [RFC5120] or zero if
topologies are not in use. topologies are not in use.
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 Label: This carries the fine-grained label identifier for all o Label: This carries the fine-grained label [RFCfgl] identifier for
subsequent IPv6 addresses in this sub-TLV, or the value zero if no all subsequent IPv6 addresses in this sub-TLV, or the value zero
label is specified. if no label 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 sub-TLV. number of group records in this sub-TLV.
o Group Record: Each group record carries the number of sources. If o Group Record: Each group record carries the number of sources. If
this field is zero, it indicates a listener for (*,G), that is, a this field is zero, it indicates a listener for (*,G), that is, a
listener not restricted by source. It then has a 16-byte (128-bit) listener not restricted by source. It then has a 16-byte (128-bit)
IPv6 Group Address followed by 16-byte source IPv6 addresses. If IPv6 Group Address followed by 16-byte source IPv6 addresses. If
the number of sources do not fit in a single sub-TLV, it is the number of sources do not fit in a single sub-TLV, it is
permitted to have the same group address repeated with different permitted to have the same group address repeated with different
skipping to change at page 12, line 15 skipping to change at page 12, line 15
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
this Section 2.2 specify the sub-TLVs transported by the MT-PORT-CAP this Section 2.2 specify the sub-TLVs transported by the MT-PORT-CAP
TLV for TRILL. TLV for TRILL.
2.2.1 Special VLANs and Flags Sub-TLV 2.2.1 Special VLANs and Flags Sub-TLV
In TRILL, a Special VLANs and Flags (VLAN-Flags) sub-TLV is carried In TRILL, a Special VLANs and Flags (VLAN-Flags) sub-TLV is carried
in every IIH PDU. It has the following format: in every IIH PDU. It has the following format:
+-+-+-+-+-+-+-+-+ +--+--+--+--+--+--+--+--+
| Type | (1 byte) | Type | (1 byte)
+-+-+-+-+-+-+-+-+ +--+--+--+--+--+--+--+--+
| Length | (1 byte) | Length | (1 byte)
+---------------+---------------+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Port ID | (2 bytes) | Port ID | (2 bytes)
+-------------------------------+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Sender Nickname | (2 bytes) | Sender Nickname | (2 bytes)
+--+--+--+--+-------------------+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|AF|AC|VM|BY| Outer.VLAN | (2 bytes) |AF|AC|VM|BY| Outer.VLAN | (2 bytes)
+--+--+--+--+-------------------+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
|TR|R |R |R | Desig.VLAN | (2 bytes) |TR|R |R |R | Designated-VLAN | (2 bytes)
+--+--+--+--+-------------------+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
o Type: sub-TLV type, set to MT-PORT-CAP VLAN-FLAGs sub-TLV 1. o Type: sub-TLV type, set to MT-PORT-CAP VLAN-FLAGs sub-TLV 1.
o Length: 8. o Length: 8.
o Port ID: An ID for the port on which the enclosing TRILL IIH o Port ID: An ID for the port on which the enclosing TRILL IIH
PDU is being sent as specified in [RFC6325], Section 4.4.2. PDU is being sent as specified in [RFC6325], Section 4.4.2.
o Sender Nickname: If the sending IS is holding any nicknames as o Sender Nickname: If the sending IS is holding any nicknames as
discussed in [RFC6325], Section 3.7, one MUST be included here. discussed in [RFC6325], Section 3.7, one MUST be included here.
skipping to change at page 12, line 53 skipping to change at page 12, line 53
[RFC6325], Section 4.6.2, point 8). It is also referenced in [RFC6325], Section 4.6.2, point 8). It is also referenced in
connection with the VLANs Appointed Sub-TLV (see Section 2.2.5) connection with the VLANs Appointed Sub-TLV (see Section 2.2.5)
and can be used as the egress on one-hop RBridge Channel and can be used as the egress on one-hop RBridge Channel
messages [Channel], for example those use for BFD over TRILL messages [Channel], for example those use for BFD over TRILL
[RFCtrillBFD]. [RFCtrillBFD].
o Outer.VLAN: A copy of the 12-bit outer VLAN ID of the TRILL IIH o Outer.VLAN: A copy of the 12-bit outer VLAN ID of the TRILL IIH
frame containing this sub-TLV, as specified in [RFC6325], frame containing this sub-TLV, as specified in [RFC6325],
Section 4.4.5. Section 4.4.5.
o Desig.VLAN: The 12-bit ID of the Designated VLAN for the link, o Designated-VLAN: The 12-bit ID of the Designated VLAN for the
as specified in [RFC6325], Section 4.2.4.2. link, as specified in [RFC6325], Section 4.2.4.2.
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
o AF, AC, VM, BY, and TR: These flag bits have the following o AF, AC, VM, BY, and TR: These flag bits have the following
meanings when set to one, as specified in the listed section of meanings when set to one, as specified in the listed section of
[RFC6325]: [RFC6325]:
RFC 6325 RFC 6325
Bit Section Meaning if bit is one Bit Section Meaning if bit is one
-------------------------------------- --------------------------------------
skipping to change at page 15, line 43 skipping to change at page 15, line 43
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Max-version | (1 byte) | Max-version | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+
| Capabilities and Header Flags Supported | (4 bytes) | Capabilities and Header Flags Supported | (4 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-...-+-+
0 1 3 0 1 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 0 1
o Type: MT-PORT-CAP sub-TLV type, set to TBD [7 suggested] (PORT- o Type: MT-PORT-CAP sub-TLV type, set to TBDf [7 suggested] (PORT-
TRILL-VER). TRILL-VER).
o Length: 5. o Length: 5.
o Max-version: A one byte unsigned integer set to maximum version o Max-version: A one byte unsigned integer set to maximum version
supported. supported.
o Capabilities and Header Flags Supported: A bit vector of 32 bits o Capabilities and Header Flags Supported: A bit vector of 32 bits
numbered 0 through 31 in network order. Bits 3 through 13 indicate numbered 0 through 31 in network order. Bits 3 through 13 indicate
that the corresponding TRILL Header hop-by-hop extended flags that the corresponding TRILL Header hop-by-hop extended flags
skipping to change at page 16, line 46 skipping to change at page 16, line 46
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Type | (1 byte) | Type | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| RESV | Start VLAN ID | (2 bytes) | RESV | Start VLAN ID | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN bit-map.... | VLAN bit-map....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV type, set to MT-PORT-CAP VLANS-Appointed sub-TLV TBD o Type: sub-TLV type, set to MT-PORT-CAP VLANS-Appointed sub-TLV
[8 suggested]. TBDg [8 suggested].
o Length: Variable, minimum 3. o Length: Variable, minimum 3.
o RESV: 4 reserved bits that MUST be sent as zero and ignored on o RESV: 4 reserved bits that MUST be sent as zero and ignored on
receipt. receipt.
o Start VLAN ID: The 12-bit VLAN ID that is represented by the high o Start VLAN ID: The 12-bit VLAN ID that is represented by the high
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
skipping to change at page 24, line 45 skipping to change at page 24, line 45
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 a secondary VLAN in the VLAN o Secondary VLAN ID: This identifies a secondary VLAN in the VLAN
Group. Group.
o more Secondary VLAN IDs: zero or more byte pairs, each with the o more Secondary VLAN IDs: zero or more byte pairs, each with the
top 4 bits as a RESV field and the low 12 bits as a VLAN ID. top 4 bits as a RESV field and the low 12 bits as a VLAN ID.
2.3.8 Interested Labels and Spanning Tree Roots Sub-TLV 2.3.8 Interested Labels and Spanning Tree Roots Sub-TLV
An IS that can handle fine-grained labeling announces its fine- An IS that can handle fine-grained labeling [RFCfgl] announces its
grained label connectivity and related information in the "Interested fine-grained label connectivity and related information in the
Labels and Bridge Spanning Tree Roots sub-TLV" (INT-LABEL) which is a "Interested Labels and Bridge Spanning Tree Roots sub-TLV" (INT-
variation of the "Interested VLANs and Spanning Tree Roots sub-TLV" LABEL) which is a variation of the "Interested VLANs and Spanning
(INT-VLAN) structured as below. Tree Roots sub-TLV" (INT-VLAN) structured as below.
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type= INT-LABEL| (1 byte) |Type= INT-LABEL| (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nickname | (2 bytes) | Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+
| Interested Labels | (7 bytes) | Interested Labels | (7 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+-+-+
| Appointed Forwarder Status Lost Counter | (4 bytes) | Appointed Forwarder Status Lost Counter | (4 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+
| Root Bridges | (6*n bytes) | Root Bridges | (6*n bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...+-+-+
o Type: Router and MT Capability sub-TLV Type, set to TBD [15 o Type: Router and MT Capability sub-TLV Type, set to TBDh [15
suggested] (INT-LABEL). suggested] (INT-LABEL).
o Length: 11 + 6*n where n is the number of root bridge IDs. o Length: 11 + 6*n where n is the number of root bridge IDs.
o Nickname: This field may be used to associate a nickname held by o Nickname: This field may be used to associate a nickname held by
the originating IS with the Labels indicated. When not used in the originating IS with the Labels indicated. When not used in
this way, it is set to zero. this way, it is set to zero.
o Interested Labels: The Interested Labels field is seven bytes long o Interested Labels: The Interested Labels field is seven bytes long
and formatted as shown below. and formatted as shown below.
skipping to change at page 26, line 8 skipping to change at page 26, line 8
- BM: If the BM (Bit Map) bit is zero, the last three bytes of - BM: If the BM (Bit Map) bit is zero, the last three bytes of
the Interested Labels is a Label.end label number. If the BM the Interested Labels is a Label.end label number. If the BM
bit is one, those bytes are a bit map as described below. bit is one, those bytes are a bit map as described below.
- R: These reserved bits MUST be sent as zero and are ignored on - R: These reserved bits MUST be sent as zero and are ignored on
receipt. receipt.
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
- Label.start and Label.end: If the BM bit is zero: This fine- - Label.start and Label.end: If the BM bit is zero: This fine-
grained label ID range is inclusive. These fields are treated grained label [RFCfgl] ID range is inclusive. These fields are
as unsigned integers. Setting them both to that same label ID treated as unsigned integers. Setting them both to that same
value indicates a range of one label ID. If Label.end is less label ID value indicates a range of one label ID. If Label.end
than Label.start, the sub-TLV is ignored. is less than Label.start, the sub-TLV is ignored.
- Label.start and Bit Map: If the BM bit is one: The fine-grained - Label.start and Bit Map: If the BM bit is one: The fine-grained
labels that the IS is interested in are indicated by a 24-bit labels that the IS is interested in are indicated by a 24-bit
bit map. The interested labels are the Label.start number plus bit map. The interested labels are the Label.start number plus
the bit number of each one bit in the bit map. So, if bit zero the bit number of each one bit in the bit map. So, if bit zero
of the bit map is a one, the IS in interested in the label with of the bit map is a one, the IS in interested in the label with
value Label.start and if bit 23 of the bit map is a one, the IS value Label.start and if bit 23 of the bit map is a one, the IS
is interested in the label with value Label.start+23. is interested in the label with value Label.start+23.
o Appointed Forwarder Status Lost Counter: This is a count of how o Appointed Forwarder Status Lost Counter: This is a count of how
skipping to change at page 27, line 16 skipping to change at page 27, line 16
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Type=RBCHANNELS| (1 byte) |Type=RBCHANNELS| (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...
| Zero or more bit vectors (variable) | Zero or more bit vectors (variable)
+-+-+-+-... +-+-+-+-...
o Type: Router and MT Capabilities RBridge Channel Protocols sub- o Type: Router and MT Capabilities RBridge Channel Protocols sub-
TLV, set to TBD [16 suggested] (RBCHANNELS). TLV, set to TBDi [16 suggested] (RBCHANNELS).
o Length: variable. o Length: variable.
o Bit Vectors: Zero or more byte-aligned bit vectors where a one bit o Bit Vectors: Zero or more byte-aligned bit vectors where a one bit
indicates support of a particular RBridge Channel protocol. Each indicates support of a particular RBridge Channel protocol. Each
byte-aligned bit vector is formatted as follows: byte-aligned bit vector is formatted as follows:
| 0 1 2 3 4 5 6 7| 8 9 10 11 12 13 14 15| | 0 1 2 3 4 5 6 7| 8 9 10 11 12 13 14 15|
+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+--+
| Bit Vector Length | Bit Vector Offset | | Bit Vector Length | Bit Vector Offset |
skipping to change at page 29, line 26 skipping to change at page 29, line 26
| .......... | ..........
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| AFFINITY RECORD N | | AFFINITY RECORD N |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Where each AFFINITY RECORD is structured as follows: Where each AFFINITY RECORD is structured as follows:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Nickname | (2 bytes) | Nickname | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|Affinity Flags | (1 byte |Affinity Flags | (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Number of trees| (1 byte) |Number of trees| (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tree-num of 1st root | (2 bytes) | Tree-num of 1st root | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tree-num of 2nd root | (2 bytes) | Tree-num of 2nd root | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| .......... | | .......... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Tree-num of Nth root | (2 bytes) | Tree-num of Nth root | (2 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: Router and MT Capability sub-TLV type, set to TBD [17 o Type: Router and MT Capability sub-TLV type, set to TBDj [17
suggested] (AFFINITY). suggested] (AFFINITY).
o Length: 1 + size of all Affinity Records included, where an o Length: 1 + size of all Affinity Records included, where an
Affinity Record listing n tree roots is 3+2*n bytes long. Affinity Record listing n tree roots is 3+2*n bytes long.
o Nickname: 16-bit nickname of the IS whose associations to the o Nickname: 16-bit nickname of the IS whose associations to the
multi-destination trees listed in the Affinity Record are through multi-destination trees listed in the Affinity Record are through
the originating IS. the originating IS.
o Affinity Flags: 8 bits reserved for future needs to provide o Affinity Flags: 8 bits reserved for future needs to provide
skipping to change at page 30, line 16 skipping to change at page 30, line 16
o Tree-num of roots: The tree numbers of the distribution trees this o Tree-num of roots: The tree numbers of the distribution trees this
Affinity Record is announcing. Affinity Record is announcing.
There is no need for a field giving the number of Affinity Records as There is no need for a field giving the number of Affinity Records as
this can be determined by processing those records. this can be determined by processing those records.
2.3.11 Label Group Sub-TLV 2.3.11 Label Group Sub-TLV
The Label Group sub-TLV consists of two or more fine-grained label The Label Group sub-TLV consists of two or more fine-grained label
IDs. This sub-TLV indicates that shared Label MAC address learning [RFCfgl] IDs. This sub-TLV indicates that shared Label MAC address
is occurring at the announcing IS between the listed Labels. It is learning is occurring at the announcing IS between the listed Labels.
structured as follows: It is structured as follows:
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
|Typ=LABEL-GROUP| (1 byte) |Typ=LABEL-GROUP| (1 byte)
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| Length | (1 byte) | Length | (1 byte)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Primary Label ID | (3 bytes) | Primary Label ID | (3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Secondary Label ID | (3 bytes) | Secondary Label ID | (3 bytes)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| more Secondary Label IDs ... (3 bytes each) | more Secondary Label IDs ... (3 bytes each)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: Router and MT Capability sub-TLV type, set to TBD [18 o Type: Router and MT Capability sub-TLV type, set to TBDk [18
suggested] (LABEL-GROUP). suggested] (LABEL-GROUP).
o Length: 6 + 3*n, where n is the number of secondary VLAN ID fields o Length: 6 + 3*n, where n is the number of secondary VLAN ID fields
beyond the first. n MAY be zero. beyond the first. n MAY be zero.
o Primary Label ID: This identifies the primary Label ID. o Primary Label ID: This identifies the primary Label ID.
o Secondary Label ID: This identifies a secondary Label in the Label o Secondary Label ID: This identifies a secondary Label in the Label
Group. Group.
skipping to change at page 32, line 41 skipping to change at page 32, line 41
ignored on receipt. ignored on receipt.
o SIZE: The SNPA size as an unsigned integer in bytes except that 6 o SIZE: The SNPA size as an unsigned integer in bytes except that 6
is encoded as zero. An actual size of zero is meaningless and is encoded as zero. An actual size of zero is meaningless and
cannot be encoded. The meaning of the value 6 in this field is cannot be encoded. The meaning of the value 6 in this field is
reserved and TRILL Neighbor TLVs received with a SIZE of 6 are reserved and TRILL Neighbor TLVs received with a SIZE of 6 are
ignored. The SIZE is inherent to the technology of a link and is ignored. The SIZE is inherent to the technology of a link and is
fixed for all TRILL Neighbor TLVs on that link but may vary fixed for all TRILL Neighbor TLVs on that link but may vary
between different links in the campus if those links are different between different links in the campus if those links are different
technologies. For example, 6 for EUI-48 SNPAs or 8 for EUI-64 technologies. For example, 6 for EUI-48 SNPAs or 8 for EUI-64
SNPAs [RFC5342]. (The SNPA size on the various links in a TRILL SNPAs [RFC7042]. (The SNPA size on the various links in a TRILL
campus is independent of the System ID size.) campus is independent of the System ID size.)
o F: failed. This bit is a one if MTU testing to this neighbor o F: failed. This bit is a one if MTU testing to this neighbor
failed at the required campus-wide MTU (see [RFC6325], Section failed at the required campus-wide MTU (see [RFC6325], Section
4.3.1). 4.3.1).
o O: OOMF. This bit is a one if the IS sending the enclosing TRILL o O: OOMF. This bit is a one if the IS sending the enclosing TRILL
Neighbor TLV is willing to offer the Overload Originated Multi- Neighbor TLV is willing to offer the Overload Originated Multi-
destination Frame (OOMF) service [ClearCorrect] to the IS whose destination Frame (OOMF) service [ClearCorrect] to the IS whose
port has the SNPA in the enclosing Neighbor RECORD. port has the SNPA in the enclosing Neighbor RECORD.
skipping to change at page 37, line 10 skipping to change at page 37, line 10
The originatingLSPBufferSize TLV (#14) MUST be in LSP number zero; The originatingLSPBufferSize TLV (#14) MUST be in LSP number zero;
however, if found in other LSP fragments, it is processed normally. however, if found in other LSP fragments, it is processed normally.
Should there be more than one originatingLSPBufferSize TLV for an IS, Should there be more than one originatingLSPBufferSize TLV for an IS,
the minimum size, but not less than 1470, is used. the minimum size, but not less than 1470, is used.
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
5. IANA Considerations 5. IANA Considerations
This section gives IANA Considerations for the TLVs, sub-TLVs, and This section gives IANA Considerations for the TLVs, sub-TLVs, and
PDUs specified herein. PDUs specified herein. A number of new code points are assigned and
those that were assigned by [RFC6326] are included here for
convenience. IANA is requested to replace all [RFC6326] references
in the IANA Registries with references to this document.
5.1 TLVs 5.1 TLVs
This document specifies two IS-IS TLV types -- namely, the Group This document specifies two IS-IS TLV types -- namely, the Group
Address TLV (GADDR-TLV, type 142) and the TRILL Neighbor TLV (type Address TLV (GADDR-TLV, type 142) and the TRILL Neighbor TLV (type
145). The PDUs in which these TLVs are permitted for TRILL are shown 145). The PDUs in which these TLVs are permitted for TRILL are shown
in the table below along with the section of this document where they in the table below along with the section of this document where they
are discussed. The final "NUMBER" column indicates the permitted are discussed. The final "NUMBER" column indicates the permitted
number of occurrences of the TLV in their PDU, or set of PDUs in the number of occurrences of the TLV in their PDU, or set of PDUs in the
case of LSP, which in these two cases is "*" indicating that the TLV case of LSP, which in these two cases is "*" indicating that the TLV
skipping to change at page 37, line 51 skipping to change at page 38, line 5
Column Head TLV RFCref TLV Name Column Head TLV RFCref TLV Name
=========== ===== ======== ============== =========== ===== ======== ==============
Grp. Adr. 142 This doc Group Address Grp. Adr. 142 This doc Group Address
MT Port 143 6165 MT-PORT-CAP MT Port 143 6165 MT-PORT-CAP
MT Cap. 242 4971 Router CAPABILITY MT Cap. 242 4971 Router CAPABILITY
144 6329 MT-Capability 144 6329 MT-Capability
INTERNET-DRAFT TRILL Use of IS-IS
Ext. Reach 22 5305 Extended IS Reachability Ext. Reach 22 5305 Extended IS Reachability
222 5120 MT ISN 222 5120 MT ISN
INTERNET-DRAFT TRILL Use of IS-IS
The final "NUMBER" column below indicates the permitted number of The final "NUMBER" column below indicates the permitted number of
occurrences of the sub-TLV cumulatively within all occurrences of occurrences of the sub-TLV cumulatively within all occurrences of
their TLV(s) in those TLVs' carrying PDU (or set of PDUs in the case their TLV(s) in those TLVs' carrying PDU (or set of PDUs in the case
of LSP), as follows: of LSP), as follows:
0-1 = MAY occur zero or one times. 0-1 = MAY occur zero or one times.
1 = MUST occur exactly once. If absent, the PDU is ignored. If it 1 = MUST occur exactly once. If absent, the PDU is ignored. If it
occurs more than once, results are unspecified. occurs more than once, results are unspecified.
* = MAY occur 0, 1, or more times. * = MAY occur 0, 1, or more times.
The values in the "Section" and "NUMBER" columns are irrelevant to The values in the "Section" and "NUMBER" columns are irrelevant to
the IANA sub-registries. The numbers in square brackets are suggested the IANA sub-registries. The numbers in square brackets are suggested
values. values.
sub- Grp. MT MT Ext. sub- Grp. MT MT Ext.
Name Section TLV# Adr. Port Cap. Reach NUMBER Name Section TLV# Adr. Port Cap. Reach NUMBER
================================================================ =================================================================
GMAC-ADDR 2.1.1 1 X - - - * GMAC-ADDR 2.1.1 1 X - - - *
GIP-ADDR 2.1.2 TBD[2] X - - - * GIP-ADDR 2.1.2 TBDa[2] X - - - *
GIPV6-ADDR 2.1.3 TBD[3] X - - - * GIPV6-ADDR 2.1.3 TBDb[3] X - - - *
GLMAC-ADDR 2.1.4 TBD[4] X - - - * GLMAC-ADDR 2.1.4 TBDc[4] X - - - *
GLIP-ADDR 2.1.5 TBD[5] X - - - * GLIP-ADDR 2.1.5 TBDd[5] X - - - *
GLIPV6-ADDR 2.1.6 TBD[6] X - - - * GLIPV6-ADDR 2.1.6 TBDe[6] X - - - *
VLAN-FLAGS 2.2.1 1 - X - - 1 VLAN-FLAGS 2.2.1 1 - X - - 1
Enabled-VLANs 2.2.2 2 - X - - * Enabled-VLANs 2.2.2 2 - X - - *
AppointedFwrdrs 2.2.3 3 - X - - * AppointedFwrdrs 2.2.3 3 - X - - *
PORT-TRILL-VER 2.2.4 TBD[7] - X - - 0-1 PORT-TRILL-VER 2.2.4 TBDf[7] - X - - 0-1
VLANs-Appointed 2.2.5 TBD[8] - X - - * VLANs-Appointed 2.2.5 TBDg[8] - X - - *
NICKNAME 2.3.2 6 - - X - * NICKNAME 2.3.2 6 - - X - *
TREES 2.3.3 7 - - X - 0-1 TREES 2.3.3 7 - - X - 0-1
TREE-RT-IDs 2.3.4 8 - - X - * TREE-RT-IDs 2.3.4 8 - - X - *
TREE-USE-IDs 2.3.5 9 - - X - * TREE-USE-IDs 2.3.5 9 - - X - *
INT-VLAN 2.3.6 10 - - X - * INT-VLAN 2.3.6 10 - - X - *
TRILL-VER 2.3.1 13 - - X - 0-1 TRILL-VER 2.3.1 13 - - X - 0-1
VLAN-GROUP 2.3.7 14 - - X - * VLAN-GROUP 2.3.7 14 - - X - *
INT-LABEL 2.3.8 TBD[15] - - X - * INT-LABEL 2.3.8 TBDh[15] - - X - *
RBCHANNELS 2.3.9 TBD[16] - - X - * RBCHANNELS 2.3.9 TBDi[16] - - X - *
AFFINITY 2.3.10 TBD[17] - - X - * AFFINITY 2.3.10 TBDj[17] - - X - *
LABEL-GROUP 2.3.11 TBD[18] - - X - * LABEL-GROUP 2.3.11 TBDk[18] - - X - *
MTU 2.4 28 - - - X 0-1 MTU 2.4 28 - - - X 0-1
================================================================ =================================================================
Name Section sub- Grp. MT MT Ext. NUMBER Name Section sub- Grp. MT MT Ext. NUMBER
TLV# Adr. Port Cap. Reach TLV# Adr. Port Cap. Reach
IANA is requested to enter the newly assigned sub-TLV numbers in the
above table in the one or two relevant existing sub-TLV registries,
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
as determined by which column has an X opposite that sub-TLV. For the
sub-TLVs from NICKNAME through and including VLAN-GROUP, which
currently exist only in the registry of sub-TLVs under TLV 242, IANA
is requested to add each sub-TLV with the same sub-TLV number to the
existing registry for sub-TLVs under TLV 144.
5.3 PDUs 5.3 PDUs
The IS-IS PDUs registry remains as established in [RFC6326] except The IS-IS PDUs registry remains as established in [RFC6326] except
that the references to [RFC6326] are updated to reference this that the references to [RFC6326] are updated to reference this
document. document.
5.4 Reserved and Capability Bits 5.4 Reserved and Capability Bits
Any reserved bits (R) or bits in reserved fields (RESV) or the Any reserved bits (R) or bits in reserved fields (RESV) or the
capabilities bits in the PORT-TRILL-VER and TRILL-VER sub-TLVs, which capabilities bits in the PORT-TRILL-VER and TRILL-VER sub-TLVs, which
skipping to change at page 39, line 30 skipping to change at page 39, line 36
Two sub-registries are created within the TRILL Parameters Registry Two sub-registries are created within the TRILL Parameters Registry
as follows: as follows:
Sub-Registry Name: TRILL-VER Sub-TLV Capability Flags Sub-Registry Name: TRILL-VER Sub-TLV Capability Flags
Registration Procedures: IETF Review Registration Procedures: IETF Review
Reference: (This document) Reference: (This document)
Bit Description Reference Bit Description Reference
===== ============= =========== ===== ============= ===========
0 Affinity sub-TLV support. [Affinity] 0 Affinity sub-TLV support. [Affinity]
1-13 Available 1-13 Unassigned
14-31 Extended header flag support. [ExtendHeader] 14-31 Extended header flag support. [ExtendHeader]
Sub-Registry Name: PORT-TRILL-VER Sub-TLV Capability Flags Sub-Registry Name: PORT-TRILL-VER Sub-TLV Capability Flags
Registration Procedures: IETF Review Registration Procedures: IETF Review
Reference: (This document) Reference: (This document)
Bit Description Reference Bit Description Reference
===== ============= =========== ===== ============= ===========
0 Hello reduction support. [ClearCorrect] 0 Hello reduction support. [ClearCorrect]
1-2 Available 1-2 Unassigned
3-13 Hop-by-hop extended flag support. [ExtendHeader] 3-13 Hop-by-hop extended flag support. [ExtendHeader]
14-31 Available 14-31 Unassigned
INTERNET-DRAFT TRILL Use of IS-IS
5.5 TRILL Neighbor Record Flags 5.5 TRILL Neighbor Record Flags
A sub-registry is created within the TRILL Parameters Registry as A sub-registry is created within the TRILL Parameters Registry as
follows: follows:
INTERNET-DRAFT TRILL Use of IS-IS
Sub-Registry Name: TRILL Neighbor TLV NEIGHBOR RECORD Flags Sub-Registry Name: TRILL Neighbor TLV NEIGHBOR RECORD Flags
Registration Procedures: Standards Action Registration Procedures: Standards Action
Reference: (This document) Reference: (This document)
Bit Short Name Description Reference Bit Short Name Description Reference
============== ============= =========== ============== ============= ===========
0 Fail Failed MTU test. [RFC6325] 0 Fail Failed MTU test [RFC6325]
1 OOMF Offering OOMF service. [ClearCorrect] 1 OOMF Offering OOMF service [ClearCorrect]
2-7 - Available. 2-7 - Unassigned
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
6. Security Considerations 6. Security Considerations
For general TRILL protocol security considerations, see the TRILL For general TRILL protocol security considerations, see the TRILL
base protocol standard [RFC6325]. base protocol standard [RFC6325].
This document raises no new security issues for IS-IS. IS-IS security This document raises no new security issues for IS-IS. IS-IS security
may be used to secure the IS-IS messages discussed here. See may be used to secure the IS-IS messages discussed here. See
skipping to change at page 42, line 50 skipping to change at page 42, line 50
implementation because they are not in LSP number zero will implementation because they are not in LSP number zero will
decide that that implementation supports only version zero with decide that that implementation supports only version zero with
no extended flag or capabilities support, which will be correct. no extended flag or capabilities support, which will be correct.
(Section 2.3.1) (Section 2.3.1)
5. Clarification of the use of invalid VLAN IDs (0x000 and 0xFFF) in 5. Clarification of the use of invalid VLAN IDs (0x000 and 0xFFF) in
the Appointed Forwarders sub-TLV and the Interested VLANs and the Appointed Forwarders sub-TLV and the Interested VLANs and
Spanning Tree Roots sub-TLV. (Sections 2.2.3 and 2.3.6) Spanning Tree Roots sub-TLV. (Sections 2.2.3 and 2.3.6)
6. Addition of the Interested Labels and Spanning Tree Roots sub-TLV 6. Addition of the Interested Labels and Spanning Tree Roots sub-TLV
to indicate attachment of an IS to a fine-grained label analogous to indicate attachment of an IS to a fine-grained label [RFCfgl]
to the existing Interested VLANs and Spanning Tree Roots sub-TLV analogous to the existing Interested VLANs and Spanning Tree
for VLANs. (Section 2.3.8) Roots sub-TLV for VLANs. (Section 2.3.8)
7. Addition of the RBridge Channel Protocols sub-TLV so ISs can 7. Addition of the RBridge Channel Protocols sub-TLV so ISs can
announce the RBridge Channel protocols they support. (Section announce the RBridge Channel protocols they support. (Section
2.3.9) 2.3.9)
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
8. Permit specification of the length of the link SNPA field in 8. Permit specification of the length of the link SNPA field in
TRILL Neighbor TLVs. This change is backwards compatible because TRILL Neighbor TLVs. This change is backwards compatible because
the size of 6 bytes is specially encoded as zero, the previous the size of 6 bytes is specially encoded as zero, the previous
skipping to change at page 45, line 20 skipping to change at page 45, line 20
draft-ietf-trill-rbridge-channel, in RFC Editor's queue. draft-ietf-trill-rbridge-channel, in RFC Editor's queue.
[ClearCorrect] - D. Eastlake, M. Zhang, A. Ghanwani, V. Manral, A. [ClearCorrect] - D. Eastlake, M. Zhang, A. Ghanwani, V. Manral, A.
Banerjee, draft-ietf-trill-clear-correct, in RFC Editor's Banerjee, draft-ietf-trill-clear-correct, in RFC Editor's
queue. queue.
[ExtendHeader] - D. Eastlake, A. Ghanwani, V. Manral, Y. Li, C. [ExtendHeader] - D. Eastlake, A. Ghanwani, V. Manral, Y. Li, C.
Bestler, draft-ietf-trill-rbridge-extension, in RFC Editor's Bestler, draft-ietf-trill-rbridge-extension, in RFC Editor's
queue. queue.
[RFCfgl] - Eastlake, D., M. Zhang, P. Agarwal, R. Perlman, D. Dutt,
"TRILL (Transparent Interconnection of Lots of Links): Fine-
Grained Labeling", draft-ietf-trill-fine-labeling, in RFC
Ediotr's queue.
9. Informative References 9. Informative References
[Err2869] - RFC Errata, Errata ID 2869, RFC 6326, http://www.rfc- [Err2869] - RFC Errata, Errata ID 2869, RFC 6326, http://www.rfc-
editor.org. editor.org.
[RFC5304] - Li, T. and R. Atkinson, "IS-IS Cryptographic [RFC5304] - Li, T. and R. Atkinson, "IS-IS Cryptographic
Authentication", RFC 5304, October 2008. Authentication", RFC 5304, October 2008.
[RFC5310] - Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R., [RFC5310] - Bhatia, M., Manral, V., Li, T., Atkinson, R., White, R.,
and M. Fanto, "IS-IS Generic Cryptographic Authentication", RFC and M. Fanto, "IS-IS Generic Cryptographic Authentication", RFC
5310, February 2009. 5310, February 2009.
[RFC5342] - Eastlake 3rd, D., "IANA Considerations and IETF Protocol
Usage for IEEE 802 Parameters", BCP 141, RFC 5342, September
2008.
[RFC6039] - Manral, V., Bhatia, M., Jaeggli, J., and R. White, [RFC6039] - Manral, V., Bhatia, M., Jaeggli, J., and R. White,
"Issues with Existing Cryptographic Protection Methods for "Issues with Existing Cryptographic Protection Methods for
Routing Protocols", RFC 6039, October 2010. Routing Protocols", RFC 6039, October 2010.
[RFC6326] - Eastlake, D., Banerjee, A., Dutt, D., Perlman, R., and A. [RFC6326] - Eastlake, D., Banerjee, A., Dutt, D., Perlman, R., and A.
Ghanwani, "Transparent Interconnection of Lots of Links (TRILL) Ghanwani, "Transparent Interconnection of Lots of Links (TRILL)
Use of IS-IS", RFC 6326, July 2011. Use of IS-IS", RFC 6326, July 2011.
[RFC7042] - Eastlake 3rd, D. and J. Abley, "IANA Considerations and
IETF Protocol and Documentation Usage for IEEE 802 Parameters",
BCP 141, RFC 7042, October 2013.
[RFCtrillBFD] - V. Manral, D, Eastlake, D. Ward, A. Banerjee, draft- [RFCtrillBFD] - V. Manral, D, Eastlake, D. Ward, A. Banerjee, draft-
ietf-trill-rbridge-bfd, in RFC Editor's queue. ietf-trill-rbridge-bfd-07.txt, in RFC Editor's queue.
[Affinity] - draft-ietf-trill-cmt, work in progress. [Affinity] - draft-ietf-trill-cmt, work in progress.
INTERNET-DRAFT TRILL Use of IS-IS
[MultiLevel] - draft-perlman-trill-rbridge-multilevel, work in [MultiLevel] - draft-perlman-trill-rbridge-multilevel, work in
progress. progress.
[Resilient] - draft-zhang-trill-resilient-trees, work in progress. [Resilient] - draft-zhang-trill-resilient-trees, work in progress.
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
Acknowledgements Acknowledgements
The authors gratefully acknowledge the contributions and review by The authors gratefully acknowledge the contributions and review by
the following: the following:
Adrian Farrel, Radia Perlman, Joe Touch. Ross Callon, Adrian Farrel, Alexey Melnikov, Radia Perlman, Carlos
Pignataro, Joe Touch.
And the contributions by the following to [RFC6326]: And the contributions by the following to [RFC6326]:
Mike Shand, Stewart Bryant, Dino Farinacci, Les Ginsberg, Sam Mike Shand, Stewart Bryant, Dino Farinacci, Les Ginsberg, Sam
Hartman, Dan Romascanu, Dave Ward, and Russ White. In particular, Hartman, Dan Romascanu, Dave Ward, and Russ White. In particular,
thanks to Mike Shand for the detailed and helpful comments. thanks to Mike Shand for the detailed and helpful comments.
This document was produced with raw nroff. All macros used were This document was produced with raw nroff. All macros used were
defined in the source files. defined in the source files.
skipping to change at page 48, line 9 skipping to change at page 49, line 9
Insieme Networks Insieme Networks
210 West Tasman Drive 210 West Tasman Drive
San Jose, CA 95134 USA San Jose, CA 95134 USA
Email: ayabaner@gmail.com Email: ayabaner@gmail.com
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
Copyright, Disclaimer, and Additional IPR Provisions Copyright, Disclaimer, and Additional IPR Provisions
Copyright (c) 2013 IETF Trust and the persons identified as the Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. The definitive version of described in the Simplified BSD License.
an IETF Document is that published by, or under the auspices of, the
IETF. Versions of IETF Documents that are published by third parties,
including those that are translated into other languages, should not
be considered to be definitive versions of IETF Documents. The
definitive version of these Legal Provisions is that published by, or
under the auspices of, the IETF. Versions of these Legal Provisions
that are published by third parties, including those that are
translated into other languages, should not be considered to be
definitive versions of these Legal Provisions. For the avoidance of
doubt, each Contributor to the IETF Standards Process licenses each
Contribution that he or she makes as part of the IETF Standards
Process to the IETF Trust pursuant to the provisions of RFC 5378. No
language to the contrary, or terms, conditions or rights that differ
from or are inconsistent with the rights and licenses granted under
RFC 5378, shall have any effect and shall be null and void, whether
published or posted by such Contributor, or included with or in such
Contribution.
 End of changes. 49 change blocks. 
111 lines changed or deleted 131 lines changed or added

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