< draft-ietf-trill-rbridge-channel-06.txt   draft-ietf-trill-rbridge-channel-07.txt >
TRILL Working Group Donald Eastlake TRILL Working Group Donald Eastlake
INTERNET-DRAFT Huawei INTERNET-DRAFT Huawei
Intended status: Proposed Standard Vishwas Manral Intended status: Proposed Standard Vishwas Manral
HP Networking HP Networking
Li Yizhou Li Yizhou
Sam Aldrin Sam Aldrin
Huawei Huawei
Dave Ward Dave Ward
Cisco Cisco
Expires: November 14, 2012 May 15, 2012 Expires: December 25, 2012 June 26, 2012
TRILL: RBridge Channel Support TRILL: RBridge Channel Support
<draft-ietf-trill-rbridge-channel-06.txt> <draft-ietf-trill-rbridge-channel-07.txt>
Abstract Abstract
This document specifies a general channel mechanism for sending This document specifies a general channel mechanism for sending
messages, such as BFD (Bidirectional Forwarding Detection) messages, messages, such as BFD (Bidirectional Forwarding Detection) messages,
between RBridges (Routing Bridges) and between RBridges and end between RBridges (Routing Bridges) and between RBridges and end
stations in an RBridge campus through extensions to the TRILL stations in an RBridge campus through extensions to the TRILL
(TRansparent Interconnection of Lots of Links) protocol. (TRansparent Interconnection of Lots of Links) protocol.
Status of This Memo Status of This Memo
skipping to change at page 1, line 44 skipping to change at page 1, line 44
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/1id-abstracts.html http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
Shadow Directories can be accessed at
The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html.
http://www.ietf.org/shadow.html
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
Table of Contents Table of Contents
1. Introduction............................................3 1. Introduction............................................3
1.1 RBridge Channel Requirements...........................3 1.1 RBridge Channel Requirements...........................3
1.2 Relation to the MPLS Generic Channel...................4 1.2 Relation to the MPLS Generic Channel...................4
1.3 Terminology............................................4 1.3 Terminology............................................4
2. Inter-RBridge Channel Messages..........................5 2. Inter-RBridge Channel Messages..........................5
2.1 The RBridge Channel Message Inner Frame................6 2.1 The RBridge Channel Message Inner Frame................6
2.1.1 RBridge Channel Header...............................6 2.1.1 RBridge Channel Header...............................6
2.1.2 Inner Ethernet Header................................7 2.1.1 Inner Ethernet Header................................8
2.1.3 Inner.VLAN Tag.......................................8 2.1.3 Inner.VLAN Tag.......................................8
2.2 The TRILL Header for RBridge Channel Messages..........9 2.2 The TRILL Header for RBridge Channel Messages..........9
2.3 Ethernet Link Header and Trailer......................10 2.3 Ethernet Link Header and Trailer......................10
2.4 Special Transmission and Rate Considerations..........10 2.4 Special Transmission and Rate Considerations..........10
3. Processing RBridge Channel TRILL Data Messages.........11 3. Processing RBridge Channel TRILL Data Messages.........12
3.1 Processing the RBridge Channel Header.................11 3.1 Processing the RBridge Channel Header.................12
3.2 RBridge Channel Errors................................12 3.2 RBridge Channel Errors................................13
4. Native RBridge Channel Frames..........................14 4. Native RBridge Channel Frames..........................15
5. Indicating Support for RBridge Channel Protocols.......16 5. Indicating Support for RBridge Channel Protocols.......17
6. Allocation Considerations..............................17 6. Allocation Considerations..............................18
6.1 IANA Considerations...................................17 6.1 IANA Considerations...................................18
6.2 IEEE Registration Authority Considerations............18 6.2 IEEE Registration Authority Considerations............19
7. Security Considerations................................19 7. Security Considerations................................20
8. References.............................................20 8. References.............................................21
8.1 Normative References..................................20 8.1 Normative References..................................21
8.2 Informative References................................20 8.2 Informative References................................21
Appendix: Change History..................................22 Appendix: Change History..................................23
Acknowledgments...........................................25 Acknowledgments...........................................26
Authors' Addresses........................................25
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
1. Introduction 1. Introduction
RBridge campuses provide transparent least-cost path forwarding using RBridge campuses provide transparent least-cost forwarding using the
the TRILL (TRansparent Interconnection of Lots of Links) protocol TRILL (TRansparent Interconnection of Lots of Links) protocol that
that builds on IS-IS (Intermediate System to Intermediate System) builds on IS-IS (Intermediate System to Intermediate System) routing
routing [IS-IS] [RFC1195] [RFC6326bis]. Devices that implement TRILL [IS-IS] [RFC1195] [RFC6326bis]. Devices that implement TRILL are
are called RBridges (Routing Bridges) or TRILL Switches. However, the called RBridges (Routing Bridges) or TRILL Switches. However, the
TRILL base protocol standard [RFC6325] provides only for TRILL Data TRILL base protocol standard [RFC6325] provides only for TRILL Data
messages and TRILL IS-IS messages. messages and TRILL IS-IS messages.
This document specifies a general channel mechanism for the This document specifies a general channel mechanism for the
transmission of other messages within an RBridge campus, such as BFD transmission of other messages within an RBridge campus, such as BFD
(Bidirectional Forwarding Detection, [RFC5880]) messages, (1) between (Bidirectional Forwarding Detection, [RFC5880]) messages, (1) between
RBridges and end stations that are directly connected on the same RBridges and end stations that are directly connected on the same
link and (2) between RBridges. This mechanism supports a requirement link and (2) between RBridges. This mechanism supports a requirement
to be able to operate with minimal configuration. to be able to operate with minimal configuration.
Familiarity with [RFC6325] and [RFC6327] is assumed in this document.
1.1 RBridge Channel Requirements 1.1 RBridge Channel Requirements
It is anticipated that various protocols operating at the TRILL level It is anticipated that various protocols operating at the TRILL layer
will be desired in RBridge campuses. For example, there is a need for will be desired in RBridge campuses. For example, there is a need for
rapid response continuity checking with a protocol such as BFD rapid response continuity checking with a protocol such as BFD
[RFC5880] [RFC5882] and for a variety of optional reporting. [RFC5880] [RFC5882] and for a variety of optional reporting.
To avoid the requirement to design and specify a way to carry each To avoid the requirement to design and specify a way to carry each
such protocol, this document specifies a general channel for sending such protocol, this document specifies a general channel for sending
messages between RBridges in a campus at the TRILL level by extending messages between RBridges in a campus at the TRILL level by extending
the TRILL protocol. To accommodate a wide variety of protocols, this the TRILL protocol. To accommodate a wide variety of protocols, this
RBridge Channel facility accommodates all the regular modes of TRILL RBridge Channel facility accommodates all the regular modes of TRILL
Data transmission including single and multiple hop unicast as well Data transmission including single and multiple hop unicast as well
skipping to change at page 4, line 4 skipping to change at page 3, line 53
RBridges as if they were TRILL Data frames; however, to enable RBridges as if they were TRILL Data frames; however, to enable
processing at transit RBridges when required by particular messages, processing at transit RBridges when required by particular messages,
they may optionally use the RBridge Channel Alert TRILL extended they may optionally use the RBridge Channel Alert TRILL extended
header flags [RFCext] that causes a transit RBridge implementing the header flags [RFCext] that causes a transit RBridge implementing the
flag to more closely examine a flagged frame. flag to more closely examine a flagged frame.
This document also specifies a format for sending RBridge Channel This document also specifies a format for sending RBridge Channel
messages between RBridges and end stations that are directly messages between RBridges and end stations that are directly
connected over a link, in either direction, when provided for by the connected over a link, in either direction, when provided for by the
protocol involved. For the most part, this format is the same as the protocol involved. For the most part, this format is the same as the
INTERNET-DRAFT TRILL: RBridge Channel
format that is TRILL Data encapsulated for inter-RBridge channel format that is TRILL Data encapsulated for inter-RBridge channel
messages. messages.
INTERNET-DRAFT TRILL: RBridge Channel
Each particular protocol using the RBridge Channel facility will Each particular protocol using the RBridge Channel facility will
likely use only a subset of the facilities specified herein. likely use only a subset of the facilities specified herein.
1.2 Relation to the MPLS Generic Channel 1.2 Relation to the MPLS Generic Channel
The RBridge Channel is similar to the MPLS Generic Channel specified The RBridge Channel is similar to the MPLS Generic Channel specified
in [RFC5586]. Instead of using a special MPLS label to indicate a in [RFC5586]. Instead of using a special MPLS label to indicate a
special channel message, an RBridge Channel message is indicated by a special channel message, an RBridge Channel message is indicated by a
special multicast Inner.MacDA and inner Ethertype. special multicast Inner.MacDA and inner Ethertype (see Section 2.1).
1.3 Terminology 1.3 Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
The terminology and acronyms of [RFC6325] are used in this document The terminology and acronyms of [RFC6325] are used in this document
with the additions listed below. with the additions listed below.
skipping to change at page 5, line 37 skipping to change at page 5, line 37
+--------------------------------+ +--------------------------------+
| Inner Ethernet Header | Section 2.1.2 | Inner Ethernet Header | Section 2.1.2
+--------------------------------+ +--------------------------------+
| RBridge Channel Header | Section 2.1.1 | RBridge Channel Header | Section 2.1.1
+--------------------------------+ +--------------------------------+
| Protocol Specific Payload | See specific channel protocol | Protocol Specific Payload | See specific channel protocol
+--------------------------------+ +--------------------------------+
| Link Trailer (FCS if Ethernet) | | Link Trailer (FCS if Ethernet) |
+--------------------------------+ +--------------------------------+
Figure 1. RBridge Channel Frame Structure
Optionally, some channel messages may require examination of the Optionally, some channel messages may require examination of the
frame by transit RBridges that support the RBridge Channel feature, frame by transit RBridges that support the RBridge Channel feature,
to determine if they need to take any action. To indicate this, such to determine if they need to take any action. To indicate this, such
messages use a RBridge Channel Alert extended TRILL header flag as messages use a RBridge Channel Alert extended TRILL header flag as
further described in Section 3 below. further described in Section 3 below.
The Sections 2.1 and 2.2 below describe the Inner frame and the TRILL The Sections 2.1 and 2.2 below describe the Inner frame and the TRILL
Header for frames sent in an RBridge Channel. As always, the Outer Header for frames sent in an RBridge Channel. As always, the Outer
link header and trailer are whatever is needed to get a TRILL Data link header and trailer are whatever is needed to get a TRILL Data
frame to the next hop RBridge, depending on the technology of the frame to the next hop RBridge, depending on the technology of the
link, and can change with each hop for multi-hop messages. Section link, and can change with each hop for multi-hop messages. Section
2.3 describes the outer Link Header for Ethernet. And Section 2.4 2.3 describes the outer Link Header for Ethernet links. And Section
discusses some special considerations for the first hop transmission 2.4 discusses some special considerations for the first hop
of RBridge Channel messages. transmission of RBridge Channel messages.
Section 3 describes some details of RBridge Channel message Section 3 describes some details of RBridge Channel message
processing. Section 4 provides the specifications for native RBridge processing. Section 4 provides the specifications for native RBridge
Channel frames between RBridges and end stations that are directly Channel frames between RBridges and end stations that are directly
connected over a link.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
connected over a link.
2.1 The RBridge Channel Message Inner Frame 2.1 The RBridge Channel Message Inner Frame
The encapsulated inner frame within an RBridge Channel message frame The encapsulated inner frame within an RBridge Channel message frame
is as shown below. is as shown below.
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
Inner Ethernet Header: Inner Ethernet Header:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Special Inner.MacDA = All-Egress-RBridges | | Special Inner.MacDA = All-Egress-RBridges |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Special Inner.MacDA cont. | Inner.MacSA | | Special Inner.MacDA cont. | Inner.MacSA |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Inner.MacSA cont. | | Inner.MacSA cont. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| VLAN Tag Ethertype | Priority, DEI, VLAN ID | | VLAN Tag Ethertype | Priority, DEI, VLAN ID |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 6, line 34 skipping to change at page 6, line 38
| RBridge-Channel Ethertype | CHV | Channel Protocol | | RBridge-Channel Ethertype | CHV | Channel Protocol |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | ERR | | Flags | ERR |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
RBridge Channel Protocol Specific Information: RBridge Channel Protocol Specific Information:
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| | | |
+ Channel Protocol Specific Data + Channel Protocol Specific Data
| ... | ...
Figure 2. RBridge Channel Inner Frame Header Fields
The Channel Protocol Specific Data contains the information related The Channel Protocol Specific Data contains the information related
to the specific channel protocol used in the channel message. Details to the specific channel protocol used in the channel message. Details
of that data are outside the scope of this document, except in the of that data are outside the scope of this document, except in the
case of the RBridge Channel Error protocol specified below. case of the RBridge Channel Error protocol specified below.
2.1.1 RBridge Channel Header 2.1.1 RBridge Channel Header
As shown in the diagram above, the RBridge Channel header starts with As shown in Figure 2, the RBridge Channel header starts with the
the RBridge-Channel Ethertype (see Section 6.2). Following that is a RBridge-Channel Ethertype (see Section 6.2). Following that is a
four-byte quantity with four sub-fields as follows: four-byte quantity with four sub-fields as follows:
CHV: A 4-bit field that gives the RBridge Channel Header Version. CHV: A 4-bit field that gives the RBridge Channel Header Version.
This document species version zero. This document specifies version zero.
INTERNET-DRAFT TRILL: RBridge Channel
Channel Protocol: A 12-bit unsigned integer that specifies the Channel Protocol: A 12-bit unsigned integer that specifies the
particular RBridge Channel protocol to which the message particular RBridge Channel protocol to which the message
applies. applies.
Flags: Provides 12 bits of flags described below. Flags: Provides 12 bits of flags described below.
INTERNET-DRAFT TRILL: RBridge Channel
ERR: A 4-bit unsigned integer used in connection with error ERR: A 4-bit unsigned integer used in connection with error
reporting at the RBridge Channel level as described in reporting at the RBridge Channel level as described in
Section 3. Section 3.
The flag bits are numbered from 0 to 11 as shown below. The flag bits are numbered from 0 to 11 as shown below.
0 1 2 3 4 5 6 7 8 9 10 11 | 0 1 2 3 4 5 6 7 8 9 10 11|
+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+
|SL|MH|NA| Reserved | |SL|MH|NA| Reserved |
+--+--+--+--+--+--+--+--+--+--+--+--+ +--+--+--+--+--+--+--+--+--+--+--+--+
Figure 3. Channel Header Flag Bits
Bit 0, which is the high order bit in network order, is defined as Bit 0, which is the high order bit in network order, is defined as
the SL or Silent bit. If it is a one, it suppresses RBridge the SL or Silent bit. If it is a one, it suppresses RBridge
Channel Error messages (see Section 3). Channel Error messages (see Section 3).
Bit 1 is the MH or Multi-Hop bit. It is used to inform the Bit 1 is the MH or Multi-Hop bit. It is used to inform the
destination RBridge protocol that the message may be multi-hop destination RBridge protocol that the message may be multi-hop
(MH=1) or was intended to be one-hop only (MH=0). (MH=1) or was intended to be one-hop only (MH=0).
Bit 2 is the NA or Native bit. It is used as described in Section 4 Bit 2 is the NA or Native bit. It is used as described in Section 4
below. below.
Reserved: Bits reserved for future specification that MUST be sent as Reserved: Bits reserved for future specification that MUST be sent as
zero and ignored on receipt. zero and ignored on receipt.
The RBridge Channel Protocol field specifies the protocol that the The RBridge Channel Protocol field specifies the protocol that the
channel message relates to. The initial defined value is listed channel message relates to. The initial defined value is listed
below. See Section 6 for IANA Considerations. below.
Protocol Name - Section of this Document Protocol Name - Section of this Document
-------- ------------------------------- -------- -------------------------------
0x001 RBridge Channel Error - Section 3 0x001 RBridge Channel Error - Section 3
2.1.2 Inner Ethernet Header IANA Considerations for RBridge Channel protocol numbers are provided
in Section 6. These include provisions for Private Use protocol
numbers. Because different uses of Private Use RBridge Channel
protocol numbers may conflict, such use MUST be within a private
network. It is the responsibility of the private network manager to
avoid conflicting use of these code points and unacceptable burdens
within the private network from their use.
INTERNET-DRAFT TRILL: RBridge Channel
2.1.1 Inner Ethernet Header
The special Inner.MacDA is the All-Egress-RBridges multicast MAC The special Inner.MacDA is the All-Egress-RBridges multicast MAC
address to signal that the frame is intended for the egress address to signal that the frame is intended for the egress
(decapsulating) RBridge itself (or the egress RBridges themselves if (decapsulating) RBridge itself (or the egress RBridges themselves if
the frame is multi-destination). (This address is called the All- the frame is multi-destination). (This address is called the All-
ESADI-RBridges address in [RFC6325].) The RBridge-Channel Ethertype ESADI-RBridges address in [RFC6325].) The RBridge-Channel Ethertype
indicates that the frame is an RBridge Channel message. The only indicates that the frame is an RBridge Channel message. The only
other Ethertype currently specified for use with the All-Egress- other Ethertype currently specified for use with the All-Egress-
RBridges Inner.MacDA is L2-IS-IS to indicate an ESADI frame RBridges Inner.MacDA is L2-IS-IS to indicate an ESADI frame
[RFC6325]. In the future additional Ethertypes may be specified for [RFC6325]. In the future additional Ethertypes may be specified for
use with the All-Egress-RBridges multicast address. use with the All-Egress-RBridges multicast address.
The RBridge originating the channel message selects the Inner.MacSA. The RBridge originating the channel message selects the Inner.MacSA.
INTERNET-DRAFT TRILL: RBridge Channel
The Inner.MacSA MUST be set by the originating RBridge to a MAC The Inner.MacSA MUST be set by the originating RBridge to a MAC
address unique within the campus owned by the originating RBridge. address unique within the campus owned by the originating RBridge.
This MAC address can be considered, in effect, the MAC address of a This MAC address can be considered, in effect, the MAC address of a
virtual internal end station that handles the RBridge Channel frames virtual internal end station that handles the RBridge Channel frames
originated by or destined for that RBridge. It MAY be the same as the originated by or destined for that RBridge. It MAY be the same as the
Inner.MacSA used by the RBridge when it originates ESADI frames Inner.MacSA used by the RBridge when it originates ESADI frames
[RFC6325]. [RFC6325].
2.1.3 Inner.VLAN Tag 2.1.3 Inner.VLAN Tag
skipping to change at page 8, line 40 skipping to change at page 8, line 54
default value for the Inner.VLAN ID is VLAN 1 but particular RBridge default value for the Inner.VLAN ID is VLAN 1 but particular RBridge
Channel protocols MAY specify other values. Channel protocols MAY specify other values.
The Inner.VLAN also specifies a three-bit frame priority for which The Inner.VLAN also specifies a three-bit frame priority for which
the following recommendations apply: the following recommendations apply:
1. For one-hop channel messages critical to network connectivity, 1. For one-hop channel messages critical to network connectivity,
such as one-hop BFD for rapid link failure detection in support such as one-hop BFD for rapid link failure detection in support
of TRILL IS-IS, the RECOMMENDED priority is 7. of TRILL IS-IS, the RECOMMENDED priority is 7.
2. For single and multi-hop known unicast channel messages 2. For single and multi-hop unicast channel messages important to
important to network operation but not critical for
connectivity, the RECOMMENDED priority is 6.
3. For other known unicast channel messages and all multi- INTERNET-DRAFT TRILL: RBridge Channel
destination channel messages, it is RECOMMENDED that the
default priority zero be used. In any case, priorities higher network operation but not critical for connectivity, the
than 5 SHOULD NOT be used for such frames. RECOMMENDED priority is 6.
3. For other unicast channel messages and all multi-destination
channel messages, it is RECOMMENDED that the default priority
zero be used. In any case, priorities higher than 5 SHOULD NOT
be used for such frames.
There is one additional bit in a VLAN tag value between the 12-bit There is one additional bit in a VLAN tag value between the 12-bit
VLAN ID and 3-bit priority, the Drop Eligibility Indicator (DEI, VLAN ID and 3-bit priority, the Drop Eligibility Indicator (DEI,
[ClearCorrect]). It is RECOMMENDED that this bit be zero for the [ClearCorrect]). It is RECOMMENDED that this bit be zero for the
first two categories of channel messages listed immediately above. first two categories of channel messages listed immediately above.
The setting of this bit for channel messages in the third category The setting of this bit for channel messages in the third category
may be dependent on the channel protocol and no general may be dependent on the channel protocol and no general
INTERNET-DRAFT TRILL: RBridge Channel
recommendation is made for that case. recommendation is made for that case.
2.2 The TRILL Header for RBridge Channel Messages 2.2 The TRILL Header for RBridge Channel Messages
After the outer Link Header (that, for Ethernet, ends with the TRILL After the outer Link Header (that, for an Ethernet link, ends with
Ethertype) and before the encapsulated frame, the channel message's the TRILL Ethertype) and before the encapsulated frame, the channel
TRILL Header initially appears as follows: message's TRILL Header initially appears as follows:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=0| R |M| Op-Len | Hop Count | |V=0| R |M| Op-Len | Hop Count |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Egress Nickname | Ingress Nickname | | Egress Nickname | Ingress Nickname |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4. RBridge Channel TRILL Header Fields
The TRILL Header version V MUST be zero, the R bits are reserved, the The TRILL Header version V MUST be zero, the R bits are reserved, the
M bit is set appropriately as the channel message is to be forwarded M bit is set appropriately as the channel message is to be forwarded
as known unicast (M=0) or multi-destination (M=1) regardless of the as known destination unicast (M=0) or multi-destination (M=1)
fact that the Inner.MacDA is always the All-Egress-RBridges multicast regardless of the fact that the Inner.MacDA is always the All-Egress-
address, and Op-Len is set appropriately for the length of the TRILL RBridges multicast address, and Op-Len is set appropriately for the
Header extensions area, if any, all as specified in [RFC6325]. length of the TRILL Header extensions area, if any, all as specified
in [RFC6325].
When an RBridge Channel message is originated, the Hop Count field When an RBridge Channel message is originated, the Hop Count field
defaults to the maximum value, 0x3F, but particular RBridge Channel defaults to the maximum value, 0x3F, but particular RBridge Channel
protocols MAY specify other values. For messages sent a known number protocols MAY specify other values. For messages sent a known number
of hops, such as one-hop messages or a two-hop self-addressed message of hops, such as one-hop messages or a two-hop self-addressed message
intended to loop back through an immediate neighbor RBridge, setting intended to loop back through an immediate neighbor RBridge, setting
the Hops field to the maximum value and checking the Hop Count field the Hops field to the maximum value and checking the Hop Count field
on receipt provides an additional validity check as discussed in on receipt provides an additional validity check as discussed in
[RFC5082]. [RFC5082].
INTERNET-DRAFT TRILL: RBridge Channel
The RBridge originating a channel message places a nickname that it The RBridge originating a channel message places a nickname that it
holds into the ingress nickname field. holds into the ingress nickname field.
There are several cases for the egress nickname field. If the channel There are several cases for the egress nickname field. If the channel
message is multi-destination, then the egress nickname designates the message is multi-destination, then the egress nickname designates the
distribution tree to use. If the channel message is a multi-hop distribution tree to use. If the channel message is a multi-hop
unicast message, then the egress nickname is a nickname of the target unicast message, then the egress nickname is a nickname of the target
RBridge; this includes the special case of a message intended to loop RBridge; this includes the special case of a message intended to loop
back from an immediate neighbor where the originator places one of back from an immediate neighbor where the originator places one of
its own nicknames in both the ingress and egress nickname fields. If its own nicknames in both the ingress and egress nickname fields. If
the channel message is a one-hop unicast message, there are two the channel message is a one-hop unicast message, there are two
possibilities for the egress nickname. possibilities for the egress nickname.
o The egress nickname can be set to a nickname of the target o The egress nickname can be set to a nickname of the target
neighbor RBridge. neighbor RBridge.
o The special nickname Any-RBridge may be used. RBridges supporting o The special nickname Any-RBridge may be used. RBridges supporting
the RBridge Channel facility MUST recognize the Any-RBridge the RBridge Channel facility MUST recognize the Any-RBridge
INTERNET-DRAFT TRILL: RBridge Channel
special nickname and accept TRILL Data frames having that value in special nickname and accept TRILL Data frames having that value in
the egress nickname field as being sent to them as the egress. the egress nickname field as being sent to them as the egress.
Thus, for such RBridges, using this egress nickname guarantees Thus, for such RBridges, using this egress nickname guarantees
processing by an immediate neighbor regardless of the state of processing by an immediate neighbor regardless of the state of
nicknames. nicknames.
2.3 Ethernet Link Header and Trailer 2.3 Ethernet Link Header and Trailer
An RBridge Channel frame has the usual link header and trailer for a An RBridge Channel frame has the usual link header and trailer for a
TRILL Data frame depending on the type of link on which it is sent. TRILL Data frame depending on the type of link on which it is sent.
skipping to change at page 10, line 36 skipping to change at page 11, line 5
And the link trailer is the Ethernet FCS. And the link trailer is the Ethernet FCS.
2.4 Special Transmission and Rate Considerations 2.4 Special Transmission and Rate Considerations
If a multi-hop RBridge Channel message is received by an RBridge, the If a multi-hop RBridge Channel message is received by an RBridge, the
criteria and method of forwarding it are the same as for any TRILL criteria and method of forwarding it are the same as for any TRILL
Data frame. If it is so forwarded, it will be on a link that was Data frame. If it is so forwarded, it will be on a link that was
included in the routing topology because it was in the Report state included in the routing topology because it was in the Report state
as specified in [RFC6327]. as specified in [RFC6327].
INTERNET-DRAFT TRILL: RBridge Channel
However, special considerations apply to single hop messages because, However, special considerations apply to single hop messages because,
for some RBridge Channel protocols, it may be desirable to send for some RBridge Channel protocols, it may be desirable to send
RBridge Channel messages over a link that is not yet fully up. In RBridge Channel messages over a link that is not yet fully up. In
particular, it is permissible, if specified by the particular channel particular, it is permissible, if specified by the particular channel
protocol, for the source RBridge that has created an RBridge Channel protocol, for the source RBridge that has created an RBridge Channel
message to attempt to transmit it to a next hop RBridge when the link message to attempt to transmit it to a next hop RBridge when the link
is in the Detect or Two-Way states, as specified in [RFC6327], as is in the Detect or Two-Way states, as specified in [RFC6327], as
well as when it is in the Report state. Such messages can also be well as when it is in the Report state. Such messages can also be
sent on point-to-point links that are not in the Up state. sent on point-to-point links that are not in the Up state.
skipping to change at page 11, line 11 skipping to change at page 12, line 11
in a campus and should be rate limited, especially if they are sent in a campus and should be rate limited, especially if they are sent
as high priority, multi-destination, or multi-hop frames or have an as high priority, multi-destination, or multi-hop frames or have an
RBridge Channel Alert extended header flag set. RBridge Channel Alert extended header flag set.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
3. Processing RBridge Channel TRILL Data Messages 3. Processing RBridge Channel TRILL Data Messages
RBridge Channel TRILL Data messages are designed to look like and, to RBridge Channel TRILL Data messages are designed to look like and, to
the extent practical, be forwarded as regular TRILL Data frames. On the extent practical, be forwarded as regular TRILL Data frames. On
receiving a channel message, the initial tests on the Outer.MacDA, receiving a channel message, an RBridge performs the usual initial
Outer Ethertype, TRILL Header V and Hop Count fields and the Reverse tests on the frame and makes the same forwarding and/or decapsulation
Path Forwarding Check if the frame is multi-destination, are all decisions as for a regular TRILL Data frame [RFC6325] with following
performed as usual. The forwarding and/or decapsulation decisions are exceptions for RBridges implementing the RBridge Channel facility:
the same as for a regular TRILL Data frame with following exceptions
for RBridges implementing the RBridge Channel facility:
1. An RBridge implementing the RBridge Channel facility MUST 1. An RBridge implementing the RBridge Channel facility MUST
recognize the Any-RBridge egress nickname in TRILL Data frames, recognize the Any-RBridge egress nickname in TRILL Data frames,
decapsulating such frames if they meet other checks. (Such a decapsulating such frames if they meet other checks. (Such a
frame cannot be a valid multi-destination frame because the frame cannot be a valid multi-destination frame because the
Any-RBridge nickname is not a valid distribution tree root.) Any-RBridge nickname is not a valid distribution tree root.)
2. If an RBridge Channel Alert extended header flag is set, then 2. If an RBridge Channel Alert extended header flag is set, then
the RBridge MUST process the RBridge Channel message as the RBridge MUST process the RBridge Channel message as
described below even if it is not egressing the frame. If it is described below even if it is not egressing the frame. If it is
skipping to change at page 12, line 4 skipping to change at page 12, line 53
Knowing that it has an RBridge Channel message, the egress RBridge, Knowing that it has an RBridge Channel message, the egress RBridge,
and any transit RBridge if an RBridge Channel Alert bit is set in the and any transit RBridge if an RBridge Channel Alert bit is set in the
TRILL Header, looks at the CHV (RBridge Channel Header Version) and TRILL Header, looks at the CHV (RBridge Channel Header Version) and
Channel Protocol fields. Channel Protocol fields.
If any of the following conditions occur at an egress RBridge, the If any of the following conditions occur at an egress RBridge, the
frame is not processed, an error may be generated as specified in frame is not processed, an error may be generated as specified in
Section 3.2, and the frame is discarded. The behavior is the same if Section 3.2, and the frame is discarded. The behavior is the same if
the frame is being processed at a transit RBridge because the the frame is being processed at a transit RBridge because the
critical RBridge Channel Alert flag is set [RFCext]. However, if critical RBridge Channel Alert flag is set [RFCext]. However, if
these conditions are detected at a transit RBridge examining the
message because the non-critical RBridge Channel Alert flag is set
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
these conditions are detected at a transit RBridge examining the
message because the non-critical RBridge Channel Alert flag is set
[RFCext] but the critical flag is not set, no error is generated and [RFCext] but the critical flag is not set, no error is generated and
the frame is still forwarded normally. the frame is still forwarded normally.
Error Conditions: Error Conditions:
1. The Ethertype is not RBridge-Channel and not any other 1. The Ethertype is not RBridge-Channel and not any other
Ethertype known to the RBridge as usable with the All-Egress- Ethertype known to the RBridge as usable with the All-Egress-
RBridges Inner.MacDA, or the frame is so short that the RBridges Inner.MacDA, or the frame is so short that the
Ethertype is truncated. Ethertype is truncated.
skipping to change at page 13, line 5 skipping to change at page 13, line 53
A variety of problems at the RBridge Channel level cause the return A variety of problems at the RBridge Channel level cause the return
of an RBridge Channel Error frame unless one of the following apply: of an RBridge Channel Error frame unless one of the following apply:
(a) the "SL" (Silent) flag is a one in the channel message for which (a) the "SL" (Silent) flag is a one in the channel message for which
the problem was detected, (b) the processing is due to the non- the problem was detected, (b) the processing is due to the non-
critical RBridge Channel Alert bit being set, (c) the frame in error critical RBridge Channel Alert bit being set, (c) the frame in error
appears, itself, to be an RBridge Channel error frame (has a non-zero appears, itself, to be an RBridge Channel error frame (has a non-zero
ERR field or a Channel Protocol of 0x001), or (d) the error is ERR field or a Channel Protocol of 0x001), or (d) the error is
suppressed due to rate limiting. suppressed due to rate limiting.
An RBridge Channel Error frame is a multi-hop unicast RBridge Channel
message with the ingress nickname set to a nickname of the RBridge
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
An RBridge Channel Error frame is a multi-hop unicast RBridge Channel
message with the ingress nickname set to the nickname of the RBridge
detecting the error, and the egress nickname set to the value of the detecting the error, and the egress nickname set to the value of the
ingress nickname in the channel message for which the error was ingress nickname in the channel message for which the error was
detected. No per-hop transit processing is specified for such error detected. No per-hop transit processing is specified for such error
frames, so the RBridge Channel Alert extended header flags SHOULD, if frames, so the RBridge Channel Alert extended header flags SHOULD, if
an extension is present, be set to zero. The SL and MH flags SHOULD an extension is present, be set to zero. The SL and MH flags SHOULD
be set to one, the NA flag MUST be zero, and the ERR field MUST be be set to one, the NA flag MUST be zero, and the ERR field MUST be
non-zero as described below. For the protocol specific data area, an non-zero as described below. For the protocol specific data area, an
RBridge Channel Message Error frame has at least the first 256 bytes RBridge Channel Message Error frame has at least the first 256 bytes
(or less if less are available) of the erroneous decapsulated channel (or less if less are available) of the erroneous decapsulated channel
message starting with the TRILL Header. (Note: The TRILL Header does message starting with the TRILL Header. (Note: The TRILL Header does
not include the TRILL Ethertype that is part of the Link Header on not include the TRILL Ethertype that is part of the Link Header on
Ethernet Links.) Ethernet Links.)
The following values for ERR are specified: The following values for ERR are specified:
ERR Meaning ERR RBridge Channel Error Code Meaning
--- ------- --- ----------------------------------
0 - Not an RBridge Channel error frame. 0 - No error
1 Frame too short (truncated Ethertype or RBridge Channel Header) 1 Frame too short (truncated Ethertype or Channel Header)
2 Unrecognized Ethertype 2 Unrecognized Ethertype
3 Unimplemented value of CHV 3 Unimplemented value of CHV
4 Wrong value of NA flag 4 Wrong value of NA flag
5 Channel Protocol is reserved or unimplemented 5 Channel Protocol is reserved or unimplemented
6-14 - Available for allocation, see Section 6. 6-14 - Available for allocation, see Section 6.
15 Reserved 15 Reserved (see Note)
Note: Intended to be allocated by Standards Action for an error
code expansion feature when it appears likely that all other
available error codes are being allocated.
All RBridges implementing the RBridge Channel feature MUST recognize All RBridges implementing the RBridge Channel feature MUST recognize
the RBridge Channel Error protocol value (0x001). They MUST NOT the RBridge Channel Error protocol value (0x001). They MUST NOT
generate an RBridge Channel Error message in response to a RBridge generate an RBridge Channel Error message in response to a RBridge
Channel Error message, that is, a channel message with a protocol Channel Error message, that is, a channel message with a protocol
value of 0x001 or with a non-zero ERR field. value of 0x001 or with a non-zero ERR field.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
4. Native RBridge Channel Frames 4. Native RBridge Channel Frames
skipping to change at page 14, line 46 skipping to change at page 15, line 46
different from All-Edge-RBridges, is discarded. If the frame is different from All-Edge-RBridges, is discarded. If the frame is
multicast by an RBridge to all the devices that TRILL considers multicast by an RBridge to all the devices that TRILL considers
to be end stations on a link that support an RBridge Channel to be end stations on a link that support an RBridge Channel
protocol that uses this transport, the destination MAC address protocol that uses this transport, the destination MAC address
is the TRILL-End-Stations multicast address (see Section 6). A is the TRILL-End-Stations multicast address (see Section 6). A
native RBridge Channel frame received at an end station with a native RBridge Channel frame received at an end station with a
destination MAC address that is a unicast address different destination MAC address that is a unicast address different
from that of the port or multicast address different from from that of the port or multicast address different from
TRILL-End-Stations, is discarded. TRILL-End-Stations, is discarded.
3. The RBridge-Channel outer Ethertype must be present. In the 3. The RBridge-Channel outer Ethertype must be present. In the
future there may be other protocols using the All-Edge-RBridges future there may be other protocols using the All-Edge-RBridges
and/or TRILL-End-Stations multicast addresses on native frames and/or TRILL-End-Stations multicast addresses on native frames
distinguished by different Ethertypes. distinguished by different Ethertypes.
4. The NA or native bit in the RBridge Channel Header flags must 4. The NA or native bit in the RBridge Channel Header flags must
be a one. be a one.
5. There might be additional tags present between the Outer.MacDA, 5. There might be additional tags present between the Outer.MacDA,
Outer.MacSA pair and the RBridge-Channel Ethertype. Outer.MacSA pair and the RBridge-Channel Ethertype.
skipping to change at page 16, line 5 skipping to change at page 16, line 38
Data RBridge Channel message would result in a TRILL Data RBridge Data RBridge Channel message would result in a TRILL Data RBridge
channel error message. However, in a native RBridge Channel error channel error message. However, in a native RBridge Channel error
message, the NA flag MUST be one. Also, since there is no TRILL message, the NA flag MUST be one. Also, since there is no TRILL
Header in native RBridge Channel protocol frames, the beginning part Header in native RBridge Channel protocol frames, the beginning part
of the frame in which the error was detected that is included in of the frame in which the error was detected that is included in
native RBridge Channel error frames starts with the RBridge Channel native RBridge Channel error frames starts with the RBridge Channel
Header (including the RBridge-Channel Ethertype). The destination MAC Header (including the RBridge-Channel Ethertype). The destination MAC
address of such error messages is set to the source MAC address of address of such error messages is set to the source MAC address of
the native RBridge Channel message that was in error. the native RBridge Channel message that was in error.
There is no mechanism to stop end stations from exchanging native
RBridge Channel messages but such usage is beyond the scope of this
document.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
5. Indicating Support for RBridge Channel Protocols 5. Indicating Support for RBridge Channel Protocols
Support for RBridge Channel protocols is indicated by the presence of Support for RBridge Channel protocols is indicated by the presence of
one or more TLVs and/or sub-TLVs in an RBridge's LSP as documented in one or more TLVs and/or sub-TLVs in an RBridge's LSP as documented in
[RFC6326bis]. [RFC6326bis].
RBridge Channel protocols 0 and 0xFFF are reserved and protocol 1, RBridge Channel protocols 0 and 0xFFF are reserved and protocol 1,
the RBridge Channel error protocol, MUST be implemented as part of the RBridge Channel error protocol, MUST be implemented as part of
skipping to change at page 17, line 34 skipping to change at page 18, line 34
IANA is requested to allocate two previously unassigned TRILL IANA is requested to allocate two previously unassigned TRILL
Multicast address as follows: Multicast address as follows:
TRILL-End-Stations TBD (01-80-C2-00-00-45 suggested) TRILL-End-Stations TBD (01-80-C2-00-00-45 suggested)
All-Edge-RBridges TBD (01-80-C2-00-00-46 suggested) All-Edge-RBridges TBD (01-80-C2-00-00-46 suggested)
IANA is requested to create an additional sub-registry in the TRILL IANA is requested to create an additional sub-registry in the TRILL
Parameter Registry for RBridge Channel Protocols, with initial Parameter Registry for RBridge Channel Protocols, with initial
contents as follows: contents as follows:
Protocol Description Reference Protocol Description Reference
-------- ----------- --------- -------- ----------- ---------
0x000 Reserved (This document) 0x000 Reserved, not to be allocated (This document)
0x001 RBridge Channel Error (This document) 0x001 RBridge Channel Error (This document)
0x002-0x0FF Available (1) 0x002-0x0FF Available (1)
0x100-0xFF7 Available (2) 0x100-0xFF7 Available (2)
0xFF8-0xFFE Private Use 0xFF8-0xFFE Private Use
0xFFF Reserved (This document) 0xFFF Reserved, not to be allocated (This document)
(1) RBridge Channel protocol code points from 0x002 to 0x0FF require (1) RBridge Channel protocol code points from 0x002 to 0x0FF require
a Standards Action, as modified by [RFC4020], for allocation. a Standards Action, as modified by [RFC4020], for allocation.
(2) RBridge Channel protocol code points from 0x100 to 0xFF7 require (2) RBridge Channel protocol code points from 0x100 to 0xFF7 are RFC
RFC Publication to allocate a single value or IETF Review to allocate Required to allocate a single value or IESG Approval to allocate
multiple values. multiple values.
IANA is requested to create an additional sub-registry in the TRILL IANA is requested to create an additional sub-registry in the TRILL
Parameter Registry for RBridge Channel Header Flags with initial Parameter Registry for RBridge Channel Header Flags with initial
contents as follows: contents as follows:
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
Flag Bit Mnemonic Allocation Flag Bit Mnemonic Allocation
-------- -------- ---------- -------- -------- ----------
0 SL Silent 0 SL Silent
1 MH Multi-hop 1 MH Multi-hop
2 NA Native 2 NA Native
3-11 - Available for allocation 3-11 - Available for allocation
Allocation of an RBridge Channel Header Flag is based on Standards Allocation of an RBridge Channel Header Flag is based on IETF Review.
Action as modified by [RFC4020].
IANA is requested to create an additional sub-registry in the TRILL IANA is requested to create an additional sub-registry in the TRILL
Parameter Registry for RBridge Channel Error codes with initial Parameter Registry for RBridge Channel Error codes with initial
contents as listed in Section 3.2 above and with available values contents as listed in Section 3.2 above and with available values
allocated by Standards Action as modified by [RFC4020]. allocated by Standards Action as modified by [RFC4020].
6.2 IEEE Registration Authority Considerations 6.2 IEEE Registration Authority Considerations
The IEEE Registration Authority has assigned the Ethertype <TBD> for The IEEE Registration Authority has assigned the Ethertype <TBD> for
RBridge-Channel. RBridge-Channel.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
7. Security Considerations 7. Security Considerations
See [RFC6325] for general TRILL Security Considerations.
No general integrity, authentication, or encryption mechanisms are No general integrity, authentication, or encryption mechanisms are
provided herein for RBridge Channel messages. If these services are provided herein for RBridge Channel messages. If these services are
required for a particular RBridge Channel protocol, they must be required for a particular RBridge Channel protocol, they MUST be
supplied by that channel protocol. See, for example, the BFD supplied by that channel protocol. See, for example, the BFD
Authentication mechanism [RFC5880]. Authentication mechanism [RFC5880].
See [RFC6325] for general TRILL Security Considerations. As stated
therein, no protection is provided by TRILL against forging of the
ingress nickname in a TRILL Data formatted channel message or the
Outer.MacSA in a native RBridge Channel frame on an Ethernet link.
This may result in misdirected return responses or error messages.
However, link level security protocols may be used to authenticate
the origin station on a link and protect against attacks on links.
See also Section 2.4 above concerning congestion.
If indication of RBridge Channel Protocol support are improperly If indication of RBridge Channel Protocol support are improperly
absent from an RBridge's LSP, it could deny all RBridge Channel absent from an RBridge's LSP, it could deny all RBridge Channel
services, for example some BFD services, for the RBridge in question. services, for example some BFD services, for the RBridge in question.
If a particular RBridge channel protocol is incorrectly not If a particular RBridge channel protocol is incorrectly not
advertised as supported, it would deny the service of that channel advertised as supported, it could deny the service of that channel
protocol to the RBridge in question. protocol to the RBridge in question.
Incorrect presence of indication of RBridge Channel Protocol support Incorrect presence of indication of RBridge Channel Protocol support
or incorrect assertion of support for a channel protocol could or incorrect assertion of support for a channel protocol could
encourage RBridge channel messages to be sent to an RBridge that does encourage RBridge channel messages to be sent to an RBridge that does
not support the channel feature or the particular channel protocol not support the channel feature or the particular channel protocol
used. The inner frame of such messages could be decapsulated and that used. The inner frame of such messages could be decapsulated and that
inner frame could be sent out all ports that are appointed forwarders inner frame could be sent out all ports that are appointed forwarders
for the frame's Inner.VLAN. However, this is unlikely to cause much for the frame's Inner.VLAN. However, this is unlikely to cause much
harm; in particular, there are two possibilities as follows: (a) If harm; in particular, there are two possibilities as follows: (a) If
end stations do not recognize the RBridge-Channel Ethertype of the end stations do not recognize the RBridge-Channel Ethertype of the
frame, they will drop it. (b) If end stations do recognize the frame, they will drop it. (b) If end stations do recognize the
RBridge-Channel Ethertype and the channel protocol indicated in the RBridge-Channel Ethertype and the channel protocol indicated in the
frame, they should refuse to process the frame due to an incorrect frame, they should refuse to process the frame due to an incorrect
value of the RBridge Channel Header NA flag. value of the RBridge Channel Header NA flag.
No protection is provided against forging of the ingress nickname in
a TRILL Data formatted channel message or the Outer.MacSA in a native
RBridge Channel frame. This may result in misdirected return
responses or error messages.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
8. References 8. References
The following sections list normative and informative references for The following sections list normative and informative references for
this document. this document.
8.1 Normative References 8.1 Normative References
[IS-IS] - ISO/IEC 10589:2002, Second Edition, "Intermediate System to [IS-IS] - ISO/IEC 10589:2002, Second Edition, "Intermediate System to
skipping to change at page 25, line 5 skipping to change at page 25, line 15
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
Changes from -05 to -06 Changes from -05 to -06
1. Improve wording in 2.1.1 re CHV values. 1. Improve wording in 2.1.1 re CHV values.
2. Revert "Ext-Len" to "Op-Len". 2. Revert "Ext-Len" to "Op-Len".
3. Fix typos and make minor editorial changes. 3. Fix typos and make minor editorial changes.
Changes from -06 to -07
1. Add bit numbers at top of figures where they were missing.
2. Add figure numbers and captions.
3. Add text to Section 2.1.1 concerning Private Use RBridge Channel
protocol numbers.
4. Change IANA Considerations for the allocation of multiple RBridge
Channel protocol numbers in the 0x100 to 0xFF7 range from IETF
Review to IESG Approval.
5. Add text that the intended use for ERR code 15 is for some future
error code expansion feature should more error codes be required
and indicate that protocol numbers 0x000 and 0xFFF are not to be
allocated.
6. Captialize the first occurrence of "must" in Section 7.
7. Add statement that directly connected end-stations are not blocked
from communicating with each other using channel messages but such
messages are beyond the scope of this document.
8. Re-order and add some references to the Securty Considertions
section.
9. Typo fixes and various editorial changes.
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
Acknowledgments Acknowledgments
The authors gratefully acknowledge the comments and contributions of The authors gratefully acknowledge the comments and contributions of
the follows, listed is alphabetic order: Somnath Chatterjee, Anoop the follows, listed is alphabetic order: Stewart Bryant, Somnath
Ghanwani, Rakesh Kumar, and Tissa Senevirathne. Chatterjee, Adrian Farrel, Stephen Farrell, Miguel A. Garcia, Anoop
Ghanwani, Brian Haberman, Rakesh Kumar, Barry Leiba, and Tissa
Senevirathne.
This document was prepared with raw nroff. All macros used were
defined in the document source files.
Authors' Addresses Authors' Addresses
Donald Eastlake 3rd Donald Eastlake 3rd
Huawei R&D USA Huawei R&D USA
155 Beaver Street 155 Beaver Street
Milford, MA 01757 USA Milford, MA 01757 USA
Tel: +1-508-333-2270 Tel: +1-508-333-2270
EMail: d3e3e3@gmail.com EMail: d3e3e3@gmail.com
skipping to change at page 25, line 47 skipping to change at page 27, line 5
Email: liyizhou@huawei.com Email: liyizhou@huawei.com
Sam Aldrin Sam Aldrin
Huawei Technologies Huawei Technologies
2330 Central Expressway 2330 Central Expressway
Santa Clara, CA 95050 USA Santa Clara, CA 95050 USA
Phone: +1-408-330-5000 Phone: +1-408-330-5000
Email: sam.aldrin@huawei.com Email: sam.aldrin@huawei.com
INTERNET-DRAFT TRILL: RBridge Channel
Dave Ward Dave Ward
Cisco Systems Cisco Systems
170 W. Tasman Drive 170 W. Tasman Drive
San Jose, CA 95134 USA San Jose, CA 95134 USA
INTERNET-DRAFT TRILL: RBridge Channel
EMail: dward@cisco.com EMail: dward@cisco.com
INTERNET-DRAFT TRILL: RBridge Channel INTERNET-DRAFT TRILL: RBridge Channel
Copyright, Disclaimer, and Additional IPR Provisions Copyright, Disclaimer, and Additional IPR Provisions
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 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
 End of changes. 60 change blocks. 
118 lines changed or deleted 177 lines changed or added

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