draft-ietf-isis-rfc6326bis-02.txt   draft-ietf-isis-rfc6326bis-03.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: July 21, 2014 January 22, 2014 Expires: July 23, 2014 January 24, 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-02.txt> <draft-ietf-isis-rfc6326bis-03.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 15, line 9 skipping to change at page 15, line 9
o Length: 6*n bytes, where there are n appointments. o Length: 6*n bytes, where there are n appointments.
o Appointee Nickname: The nickname of the IS being appointed a o Appointee Nickname: The nickname of the IS being appointed a
forwarder. forwarder.
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
o RESV: 4 bits that MUST be sent as zero and ignored on receipt. o RESV: 4 bits that MUST be sent as zero and ignored on receipt.
o Start.VLAN, End.VLAN: These fields are the VLAN IDs of the o Start.VLAN, End.VLAN: This VLAN ID range is inclusive. Setting
appointment range, inclusive. To specify a single VLAN, the VLAN's both VLAN.start and VLAN.end to the same value indicates a range
ID appears as both the start and end VLAN. As specified in of one VLAN ID. If VLAN.start is not equal to VLAN.end and
[RFC6439], appointing an IS forwarder on a port for a VLAN not VLAN.start is 0x000, the sub-TLV is interpreted as if VLAN.start
enabled on that port has no effect. If the range specified is or was 0x001. If VLAN.start is not equal to VLAN.end and VLAN.end is
includes the value 0x000 or 0xFFF, such values are ignored as they 0xFFF, the sub-TVL is interpreted as if VLAN.end was 0xFFE. If
are not valid VLAN numbers and a port cannot be enabled for them. VLAN.end is less than VLAN.start, the sub-TLV is ignored. If both
VLAN.start and VLAN.end are 0x000 or both are 0xFFF, the sub-TLV
is ignored. The values 0x000 or 0xFFF are not valid VLAN IDs and
a port cannot be enabled for them.
An IS's nickname may occur as appointed forwarder for multiple VLAN An IS's nickname may occur as appointed forwarder for multiple VLAN
ranges by occurrences of this sub-TLV within the same or different MT ranges by occurrences of this sub-TLV within the same or different MT
Port Capability TLVs within an IIH PDU. See [RFC6439]. Port Capability TLVs within an IIH PDU. See [RFC6439].
2.2.4 Port TRILL Version Sub-TLV 2.2.4 Port TRILL Version Sub-TLV
The Port TRILL Version (PORT-TRILL-VER) sub-TLV indicates the maximum The Port TRILL Version (PORT-TRILL-VER) sub-TLV indicates the maximum
version of the TRILL standard supported and the support of optional version of the TRILL standard supported and the support of optional
hop-by-hop capabilities. By implication, lower versions are also hop-by-hop capabilities. By implication, lower versions are also
skipping to change at page 15, line 52 skipping to change at page 16, line 4
o Type: MT-PORT-CAP sub-TLV type, set to TBDf [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
that the corresponding TRILL Header hop-by-hop extended flags
[ExtendHeader] are supported. Bits 0 through 2 and 14 to 31 are
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
numbered 0 through 31 in network order. Bits 3 through 13 indicate
that the corresponding TRILL Header hop-by-hop extended flags
[ExtendHeader] are supported. Bits 0 through 2 and 14 to 31 are
reserved to indicate support of optional capabilities. A one bit reserved to indicate support of optional capabilities. A one bit
indicates that the flag or capability is supported by the sending indicates that the flag or capability is supported by the sending
IS. Bits in this field MUST be set to zero except as permitted for IS. Bits in this field MUST be set to zero except as permitted for
a capability being advertised or if a hop-by-hop extended header a capability being advertised or if a hop-by-hop extended header
flag is supported. flag is supported.
This sub-TLV, if present, MUST occur in an MT-PORT-CAP TLV in a TRILL This sub-TLV, if present, MUST occur in an MT-PORT-CAP TLV in a TRILL
IIH. If there is more than one occurrence, the minimum of the IIH. If there is more than one occurrence, the minimum of the
supported versions is assumed to be correct and a capability or supported versions is assumed to be correct and a capability or
header flag is assumed to be supported only if indicated by all header flag is assumed to be supported only if indicated by all
skipping to change at page 16, line 52 skipping to change at page 17, line 4
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN bit-map.... | VLAN bit-map....
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
o Type: sub-TLV type, set to MT-PORT-CAP VLANS-Appointed sub-TLV o Type: sub-TLV type, set to MT-PORT-CAP VLANS-Appointed sub-TLV
TBDg [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.
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
receipt.
o Start VLAN ID: The 12-bit VLAN ID that is represented by the high
order bit of the first byte of the VLAN bit-map. order bit of the first byte of the VLAN bit-map.
o VLAN bit-map: The highest order bit indicates the VLAN equal to o VLAN bit-map: The highest order bit indicates the VLAN equal to
the start VLAN ID, the next highest bit indicates the VLAN equal the start VLAN ID, the next highest bit indicates the VLAN equal
to start VLAN ID + 1, continuing to the end of the VLAN bit-map to start VLAN ID + 1, continuing to the end of the VLAN bit-map
field. field.
If this sub-TLV occurs more than once in a Hello, the originating IS If this sub-TLV occurs more than once in a Hello, the originating IS
is declaring that it believes itself to be appointed forwarder on the is declaring that it believes itself to be appointed forwarder on the
port on which the enclosing IIH was sent for the union of the sets of port on which the enclosing IIH was sent for the union of the sets of
skipping to change at page 17, line 50 skipping to change at page 18, line 5
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
| 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: Router Capability sub-TLV type, set to 13 (TRILL-VER).
INTERNET-DRAFT TRILL Use of IS-IS INTERNET-DRAFT TRILL Use of IS-IS
o Type: Router Capability sub-TLV type, set to 13 (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 14 through 31 numbered 0 through 31 in network order. Bits 14 through 31
indicate that the corresponding TRILL Header extended flags indicate that the corresponding TRILL Header extended flags
[ExtendHeader] are supported. Bits 0 through 13 are reserved to [ExtendHeader] are supported. Bits 0 through 13 are reserved to
indicate support of optional capabilities. A one bit indicates indicate support of optional capabilities. A one bit indicates
skipping to change at page 23, line 29 skipping to change at page 23, line 29
ignored on receipt. ignored on receipt.
- VLAN.start and VLAN.end: This VLAN ID range is inclusive. - VLAN.start and VLAN.end: This VLAN ID range is inclusive.
Setting both VLAN.start and VLAN.end to the same value Setting both VLAN.start and VLAN.end to the same value
indicates a range of one VLAN ID. If VLAN.start is not equal to indicates a range of one VLAN ID. If VLAN.start is not equal to
VLAN.end and VLAN.start is 0x000, the sub-TLV is interpreted as VLAN.end and VLAN.start is 0x000, the sub-TLV is interpreted as
if VLAN.start was 0x001. If VLAN.start is not equal to VLAN.end if VLAN.start was 0x001. If VLAN.start is not equal to VLAN.end
and VLAN.end is 0xFFF, the sub-TVL is interpreted as if and VLAN.end is 0xFFF, the sub-TVL is interpreted as if
VLAN.end was 0xFFE. If VLAN.end is less than VLAN.start, the VLAN.end was 0xFFE. If VLAN.end is less than VLAN.start, the
sub-TLV is ignored. If both VLAN.start and VLAN.end are 0x000 sub-TLV is ignored. If both VLAN.start and VLAN.end are 0x000
or both are 0xFFF, the sub-TLV is ignored. or both are 0xFFF, the sub-TLV is ignored. The values 0x000 or
0xFFF are not valid VLAN IDs and a port cannot be enabled for
them.
o Appointed Forwarder Status Lost Counter: This is a count of how o Appointed Forwarder Status Lost Counter: This is a count of how
many times a port that was appointed forwarder for the VLANs in many times a port that was appointed forwarder for the VLANs in
the range given has lost the status of being an appointed the range given has lost the status of being an appointed
forwarder for some port as discussed in Section 4.8.3 of forwarder for some port as discussed in Section 4.8.3 of
[RFC6325]. It is initialized to zero at an IS when the zeroth LSP [RFC6325]. It is initialized to zero at an IS when the zeroth LSP
sequence number is initialized. No special action need be taken at sequence number is initialized. No special action need be taken at
rollover; the counter just wraps around. rollover; the counter just wraps around.
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
skipping to change at page 47, line 12 skipping to change at page 47, line 12
[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:
Ross Callon, Adrian Farrel, Alexey Melnikov, Radia Perlman, Carlos Ross Callon, Spencer Dawkins, Adrian Farrel, Alexey Melnikov,
Pignataro, Joe Touch. 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.
 End of changes. 11 change blocks. 
20 lines changed or deleted 25 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/