| 1 | <?xml version='1.0' encoding='us-ascii'?>
|
| 2 | <!DOCTYPE rfc SYSTEM "rfc2629.dtd">
|
| 3 |
|
| 4 | <rfc submissionType="IETF" category="std" consensus="yes" number='8383'>
|
| 5 | <?rfc compact="yes"?>
|
| 6 | <?rfc text-list-symbols="-o*+"?>
|
| 7 | <?rfc subcompact="no"?>
|
| 8 | <?rfc sortrefs="yes"?>
|
| 9 | <?rfc symrefs="yes"?>
|
| 10 | <?rfc strict="yes"?>
|
| 11 | <?rfc toc="yes"?>
|
| 12 | <front>
|
| 13 | <title abbrev="TRILL Address Flush Message">Transparent Interconnection of Lots of Links (TRILL): Address Flush Message</title>
|
| 14 |
|
| 15 | <author fullname="Weiguo Hao" initials="W." surname="Hao">
|
| 16 |
|
| 17 | <organization abbrev="Huawei">Huawei Technologies</organization>
|
| 18 | <address><postal><street>101 Software Avenue,</street>
|
| 19 | <street>Nanjing 210012</street>
|
| 20 | <street>China</street>
|
| 21 | </postal>
|
| 22 | <phone>+86-25-56623144</phone>
|
| 23 | <email>haoweiguo@huawei.com</email>
|
| 24 | </address>
|
| 25 | </author>
|
| 26 | <author fullname="Donald Easlake 3rd" initials="D." surname="Eastlake, 3rd">
|
| 27 | <organization abbrev="Huawei">Huawei Technologies</organization>
|
| 28 | <address><postal><street>155 Beaver Street</street><street>Milford, MA 01757</street>
|
| 29 | <street>United States of America</street></postal>
|
| 30 | <phone>+1-508-333-2270</phone>
|
| 31 | <email>d3e3e3@gmail.com</email>
|
| 32 | </address>
|
| 33 | </author>
|
| 34 |
|
| 35 | <author fullname="Yizhou Li" initials="Y." surname="Li">
|
| 36 | <organization abbrev="Huawei">Huawei Technologies</organization>
|
| 37 | <address><postal><street>101 Software Avenue,</street>
|
| 38 | <street>Nanjing 210012</street>
|
| 39 | <street>China</street>
|
| 40 | </postal>
|
| 41 | <phone>+86-25-56624629</phone>
|
| 42 | <email>liyizhou@huawei.com</email>
|
| 43 | </address>
|
| 44 | </author>
|
| 45 |
|
| 46 | <author fullname="Mohammed Umair" initials="M." surname="Umair">
|
| 47 | <organization>Cisco</organization>
|
| 48 | <address><postal><street>Cessna Business Park, Kadubeesanahalli Village, Hobli,</street>
|
| 49 | <street>Sarjapur, Varthur Main Road, Marathahalli,</street>
|
| 50 | <street>Bengaluru, Karnataka 560087</street>
|
| 51 | <street>India</street>
|
| 52 | </postal>
|
| 53 | <email>mohammed.umair2@gmail.com</email>
|
| 54 | </address>
|
| 55 | </author>
|
| 56 |
|
| 57 | <date month="May" year="2018"/>
|
| 58 | <workgroup>TRILL Working Group</workgroup>
|
| 59 |
|
| 60 | <!-- [rfced] Please insert any keywords (beyond those that appear in
|
| 61 | the title) for use on https://www.rfc-editor.org/search.
|
| 62 | -->
|
| 63 |
|
| 64 | <keyword>example</keyword>
|
| 65 |
|
| 66 | <abstract>
|
| 67 | <t> The TRILL (Transparent Interconnection of Lots
|
| 68 | of Links) protocol, by default, learns end station addresses
|
| 69 | from observing the data plane. In particular, it learns local
|
| 70 | Media Access Control (MAC) addresses and the edge switch port of
|
| 71 | attachment from the receipt of local data frames and learns
|
| 72 | remote MAC addresses and the edge switch port of attachment from the
|
| 73 | decapsulation of remotely sourced TRILL Data packets.</t>
|
| 74 |
|
| 75 | <t>
|
| 76 | This document specifies a message by which a TRILL switch can
|
| 77 | explicitly request other TRILL switches to flush certain MAC
|
| 78 | reachability learned through the decapsulation of TRILL Data packets.
|
| 79 |
|
| 80 | <!--[rfced] To what does "the TRILL automatic address forgetting" refer? Will the reader understand this phrase?
|
| 81 |
|
| 82 | Original:
|
| 83 | This is a supplement to the TRILL automatic address forgetting and
|
| 84 | can assist in achieving more rapid convergence in case of topology or
|
| 85 | configuration change.
|
| 86 |
|
| 87 | -->
|
| 88 | This is a supplement to the TRILL automatic address forgetting and
|
| 89 | can assist in achieving more rapid convergence in case of topology or
|
| 90 | configuration change.</t>
|
| 91 |
|
| 92 | </abstract>
|
| 93 | </front>
|
| 94 |
|
| 95 | <middle>
|
| 96 | <section title="Introduction" anchor="section-1"><t>
|
| 97 | By default, edge TRILL (Transparent Interconnection of Lots of Links) switches
|
| 98 | <xref target="RFC6325"/> <xref target="RFC7780"/>, also called edge Routing Bridges (RBridges), learn end
|
| 99 | station MAC address reachability from observing the data plane. On
|
| 100 | receipt of a native frame from an end station, they would learn the
|
| 101 | local MAC address attachment of the source end station. And on
|
| 102 | egressing (decapsulating) a remotely originated TRILL Data packet,
|
| 103 | they learn the remote MAC address and remote attachment TRILL switch.
|
| 104 | Such learning is all scoped by data label (VLAN or Fine-Grained Label (FGL)
|
| 105 | <xref target="RFC7172"/>).</t>
|
| 106 |
|
| 107 | <t>
|
| 108 | TRILL has mechanisms for timing out such learning and appropriately
|
| 109 | clearing it based on some network connectivity and configuration
|
| 110 | changes; however, there are circumstances under which it would be
|
| 111 | helpful for a TRILL switch to be able to explicitly flush (purge)
|
| 112 | certain learned end station reachability information in remote
|
| 113 | RBridges to achieve more-rapid convergence. Section 6.2 of <xref target="RFC4762"/>
|
| 114 | is an example of the use of such a mechanism.</t>
|
| 115 |
|
| 116 | <t>
|
| 117 | Another example, based on Appendix A.3 of <xref target="RFC6325"/> ("Wiring Closet Topology"), presents a bridged LAN connected to a TRILL network via
|
| 118 | multiple RBridge ports. For optimum paths, Appendix A.3.3 suggests
|
| 119 | configuring the RBridge ports to be like one Spanning Tree Protocol
|
| 120 | (STP) tree root in the bridged LAN. The address flush message in this
|
| 121 | document could also be triggered in this case when one of the edge
|
| 122 | RBridges receives Topology Change (TC) information (e.g., TC
|
| 123 | in STP, Topology Change Notification (TCN) in Multiple
|
| 124 | Spanning Tree Protocol (MSTP) in order to rapidly flush the MAC addresses
|
| 125 | for specific VLANs learned at the other edge RBridge ports.</t>
|
| 126 |
|
| 127 | <t>
|
| 128 | A TRILL switch can easily flush any locally learned addresses it
|
| 129 | wants. This document specifies an RBridge Channel Support protocol <xref
|
| 130 | target="RFC7178"/> message to request flushing address information
|
| 131 | for specific VLANs or FGLs (<xref target="RFC7172"/>) learned from decapsulating TRILL Data
|
| 132 | packets.</t>
|
| 133 |
|
| 134 | <section title="Terminology and Abbreviations" anchor="section-1.1">
|
| 135 |
|
| 136 | <t> The key words "MUST", "MUST NOT",
|
| 137 | "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT",
|
| 138 | "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to
|
| 139 | be interpreted as described in <xref target="RFC2119"/> <xref
|
| 140 | target="RFC8174"/> when, and only when, they appear in all
|
| 141 | capitals, as shown here.</t>
|
| 142 |
|
| 143 | <t>
|
| 144 | This document uses the terms and abbreviations defined in <xref
|
| 145 | target="RFC6325"/> and <xref target="RFC7978"/> as well as the
|
| 146 | following:</t>
|
| 147 |
|
| 148 | <t><list hangIndent="3" style="hanging"><t hangText="Data Label:">A VLAN or FGL</t>
|
| 149 |
|
| 150 | <t hangText="Edge TRILL Switch:">A TRILL switch attached to one or more links that provide end station service
|
| 151 | </t>
|
| 152 |
|
| 153 | <t hangText="FCS:">Frame Check Sequence</t>
|
| 154 |
|
| 155 | <t hangText="FGL:">Fine-Grained Label <xref target="RFC7172"/></t>
|
| 156 |
|
| 157 | <t hangText="Management VLAN:"> A VLAN in which all TRILL switches in a campus
|
| 158 | indicate interest so that multi-destination TRILL Data packets,
|
| 159 | including RBridge Channel messages <xref target="RFC7978"/>, sent with that
|
| 160 | VLAN as the Inner.VLAN will be delivered to all TRILL switches
|
| 161 | in the campus. Usually, no end station service is offered in the
|
| 162 | Management VLAN.
|
| 163 | </t>
|
| 164 |
|
| 165 |
|
| 166 |
|
| 167 | <t hangText="MAC:">Media Access Control</t>
|
| 168 |
|
| 169 | <t hangText="RBridge:">An alternative name for a TRILL switch</t>
|
| 170 |
|
| 171 | <t hangText="STP:">Spanning Tree Protocol</t>
|
| 172 |
|
| 173 | <t hangText="TC:">Topology Change message</t>
|
| 174 |
|
| 175 | <t hangText="TCN:">Topology Change Notification message</t>
|
| 176 |
|
| 177 | <t hangText="TRILL switch:">A device implementing the TRILL protocol RFC 6235
|
| 178 | <xref target="RFC7780"/>
|
| 179 | </t>
|
| 180 |
|
| 181 | </list>
|
| 182 | </t>
|
| 183 |
|
| 184 | </section>
|
| 185 |
|
| 186 | </section>
|
| 187 |
|
| 188 | <section title="Address Flush Message Details" anchor="section-2"><t>
|
| 189 | The Address Flush message is an RBridge Channel protocol message
|
| 190 | <xref target="RFC7178"/>.</t>
|
| 191 |
|
| 192 | <t>
|
| 193 | The general structure of an RBridge Channel packet on a link between
|
| 194 | TRILL switches is shown in <xref target="ref-rbridge-channel-protocol-message-structure"/>. The Protocol field in the
|
| 195 | RBridge Channel Header gives the type of RBridge Channel packet and
|
| 196 | indicates how to interpret the Channel Protocol Specific Payload
|
| 197 |
|
| 198 | <!--[rfced] RFC 7178 does not use the specific term "Channel Protocol Specific Payload". We note that RFC-to-be 8381 updated to use "Channel-Protocol-Specific Payload". Please review the use of this term in this document and the other two and let us know if updates should be made.
|
| 199 |
|
| 200 | -->
|
| 201 | <xref target="RFC7178"/>.
|
| 202 |
|
| 203 |
|
| 204 |
|
| 205 | </t>
|
| 206 | <!--[rfced] We note that the content of Figure 1 is an exact replica
|
| 207 | of Figure 1 in RFC-to-be 8381. Only the titles are different.
|
| 208 | Please confirm that this is intentional and no updates should be
|
| 209 | made.
|
| 210 |
|
| 211 | RFC 8381:
|
| 212 | RBridge Channel Packet Structure
|
| 213 |
|
| 214 | This document:
|
| 215 | RBridge Channel Protocol Message Structure
|
| 216 |
|
| 217 | -->
|
| 218 |
|
| 219 | <figure title="RBridge Channel Protocol Message Structure" anchor="ref-rbridge-channel-protocol-message-structure"><artwork><![CDATA[
|
| 220 |
|
| 221 | +-----------------------------------+
|
| 222 | | Link Header |
|
| 223 | +-----------------------------------+
|
| 224 | | TRILL Header |
|
| 225 | +-----------------------------------+
|
| 226 | | Inner Ethernet Addresses |
|
| 227 | +-----------------------------------+
|
| 228 | | Data Label (VLAN or FGL) |
|
| 229 | +-----------------------------------+
|
| 230 | | RBridge Channel Header |
|
| 231 | +-----------------------------------+
|
| 232 | | Channel Protocol Specific Payload |
|
| 233 | +-----------------------------------+
|
| 234 | | Link Trailer (FCS if Ethernet) |
|
| 235 | +-----------------------------------+
|
| 236 | ]]></artwork>
|
| 237 | </figure>
|
| 238 |
|
| 239 | <t>
|
| 240 | By default, an Address Flush RBridge Channel message applies to
|
| 241 | addresses within the Data Label that appear right after the Inner
|
| 242 | Ethernet Addresses. Address Flush protocol messages are usually sent
|
| 243 | as multi-destination packets (TRILL Header M bit equal to one) so as
|
| 244 | to reach all TRILL switches offering end station service in the VLAN
|
| 245 | or FGL specified by that Data Label. Both multi-destination and
|
| 246 | unicast Address Flush messages SHOULD be sent at priority 6 since
|
| 247 | they are important control messages but are lower priority than
|
| 248 | control messages that establish or maintain adjacency.</t>
|
| 249 |
|
| 250 | <t>
|
| 251 | Nevertheless:</t>
|
| 252 |
|
| 253 | <t><list style="symbols">
|
| 254 |
|
| 255 | <t>There are provisions for optionally indicating the Data Label(s)
|
| 256 | to be flushed for cases where the Address Flush message is sent
|
| 257 | over a Management VLAN or the like.</t>
|
| 258 |
|
| 259 | <t>An Address Flush message can be sent unicast, if it is desired to
|
| 260 | clear addresses at one TRILL switch only.</t>
|
| 261 |
|
| 262 | <t>An Address Flush message can be sent selectively to the RBridges
|
| 263 | that have at least one access port configured as one of the VLANs or
|
| 264 | FGLs specified in the Address Flush message payload.</t>
|
| 265 |
|
| 266 | </list>
|
| 267 | </t>
|
| 268 |
|
| 269 | <t>
|
| 270 | Implementations should consider logging address flush messages
|
| 271 | received with appropriate protections against packet storms.</t>
|
| 272 |
|
| 273 | <section title="VLAN Block Only Case" anchor="section-2.1">
|
| 274 |
|
| 275 | <t>
|
| 276 | <xref target="ref-address-flush-message-vlan-block-case"/> expands
|
| 277 | the RBridge Channel Header and Channel Protocol Specific Payload
|
| 278 | from <xref
|
| 279 | target="ref-rbridge-channel-protocol-message-structure"/> for the
|
| 280 | case of the VLAN-only-based Address Flush message. This form of the
|
| 281 | Address Flush message is optimized for flushing MAC addresses based
|
| 282 | on nickname and blocks of VLANs. 0x8946 is the Ethertype assigned
|
| 283 | by IEEE for the RBridge Channel protocol.</t>
|
| 284 |
|
| 285 | <!--[rfced] Would a pointer to an IEEE registry be needed/wanted by the reader or others? If so, please let us know how to update.
|
| 286 |
|
| 287 | Original:
|
| 288 | 0x8946 is the Ethertype assigned by IEEE for the RBridge Channel protocol
|
| 289 |
|
| 290 | -->
|
| 291 |
|
| 292 | <figure title="Address Flush Message - VLAN Block Case" anchor="ref-address-flush-message-vlan-block-case"><artwork><![CDATA[
|
| 293 | 0 1 2 3
|
| 294 | 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
|
| 295 | RBridge Channel Header:
|
| 296 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 297 | | RBridge-Channel (0x8946) | 0x0 |Channel Protocol= 0x009|
|
| 298 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 299 | | Flags | ERR |
|
| 300 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 301 | Address Flush Protocol Specific:
|
| 302 | +-+-+-+-+-+-+-+-+
|
| 303 | | K-nicks |
|
| 304 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 305 | | Nickname 1 | Nickname 2 |
|
| 306 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 307 | | Nickname ... | Nickname K-nicks |
|
| 308 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 309 | | K-VLBs |
|
| 310 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 311 | | RESV | Start.VLAN 1 | RESV | End.VLAN 1 |
|
| 312 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 313 | | RESV | Start.VLAN 2 | RESV | End.VLAN 2 |
|
| 314 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 315 | | RESV | Start.VLAN ... | RESV | End.VLAN ... |
|
| 316 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 317 | | RESV | Start.VLAN K-VLBs | RESV | End.VLAN K-VLBs |
|
| 318 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 319 | ]]></artwork>
|
| 320 | </figure>
|
| 321 | <t>
|
| 322 | The fields in <xref target="ref-address-flush-message-vlan-block-case"/> related to the Address Flush message are as
|
| 323 | follows:</t>
|
| 324 |
|
| 325 | <t><list style="hanging" hangIndent="3">
|
| 326 | <t hangText="Channel Protocol:">
|
| 327 | The RBridge Channel Protocol value allocated
|
| 328 | for Address Flush (see <xref target="section-3"/>).
|
| 329 | </t>
|
| 330 |
|
| 331 | <t hangText="K-nicks:">The number of nicknames listed as an unsigned
|
| 332 | integer. If this is zero, the ingress nickname in the TRILL
|
| 333 | Header <xref target="RFC6325"/> is considered to be the only nickname to which
|
| 334 | the message applies. If non-zero, it gives the number of
|
| 335 | nicknames listed right after K-nicks to which the message
|
| 336 | applies, and, in this non-zero case, the flush does not apply to
|
| 337 | the ingress nickname in the TRILL Header unless it is also
|
| 338 | listed. The message flushes address learning due to egressing
|
| 339 | TRILL Data packets that had an ingress nickname to which the
|
| 340 | message applies.
|
| 341 | </t>
|
| 342 |
|
| 343 | <t hangText="Nickname:">A listed nickname to which it is intended that the Address Flush message apply. If an unknown or reserved
|
| 344 | nickname occurs in the list, it is ignored, but the address
|
| 345 | flush operation is still executed with the other nicknames. If
|
| 346 | an incorrect nickname occurs in the list, so that some address
|
| 347 | learning is flushed that should not have been flushed, the
|
| 348 | network will still operate correctly; however, it will be less efficient
|
| 349 | as the incorrectly flushed learning is relearned.
|
| 350 | </t>
|
| 351 |
|
| 352 | <t hangText="K-VLBs:">The number of VLAN blocks present as an unsigned
|
| 353 | integer. If this byte is zero, the message is the more general
|
| 354 | format specified in <xref target="section-2.2"/>. If it is non-zero, it gives
|
| 355 | the number of blocks of VLANs present. Thus, in the VLAN Block
|
| 356 | address flush case, K-VLBs will be at least one.
|
| 357 | </t>
|
| 358 |
|
| 359 | <t hangText="RESV:">4 reserved bits. MUST be sent as zero and ignored on
|
| 360 | receipt.
|
| 361 | </t>
|
| 362 |
|
| 363 | <t hangText="Start.VLAN, End.VLAN:">These 12-bit fields give the beginning and
|
| 364 | ending VLAN IDs of a block of VLANs. The block includes both
|
| 365 | the starting and ending values; so, a block of size one is
|
| 366 | indicated by setting End.VLAN equal to Start.VLAN. If
|
| 367 | Start.VLAN is 0x000, it is treated as if it was 0x001. If
|
| 368 | End.VLAN is 0xFFF, it is treated as if it was 0xFFE. If
|
| 369 | End.VLAN is smaller than Start.VLAN, considering both as
|
| 370 | unsigned integers, that VLAN block is ignored, but the address
|
| 371 | flush operation is still executed with other VLAN blocks in the
|
| 372 | message. VLAN blocks may overlap, in which case, the address
|
| 373 | flush operation is applicable to a VLAN covered by any one or
|
| 374 | more of the blocks in the message.
|
| 375 | </t>
|
| 376 |
|
| 377 | </list>
|
| 378 | </t>
|
| 379 |
|
| 380 |
|
| 381 | <t>
|
| 382 | This message flushes all addresses in an applicable VLAN learned from
|
| 383 | egressing TRILL Data packets with an applicable nickname as ingress.
|
| 384 | To flush addresses for all VLANs, it is easy to specify a block
|
| 385 | covering all valid VLAN IDs (i.e., from 0x001 to 0xFFE).</t>
|
| 386 |
|
| 387 | </section>
|
| 388 |
|
| 389 | <section title="Extensible Case" anchor="section-2.2"><t>
|
| 390 | A more general form of the Address Flush message is provided to
|
| 391 | support flushing by FGL and more efficient encodings of VLANs and
|
| 392 | FGLs where using a set of contiguous blocks is cumbersome. It also
|
| 393 | supports optionally specifying the MAC addresses to clear. This form
|
| 394 | is extensible.</t>
|
| 395 |
|
| 396 | <t>
|
| 397 | The extensible case is indicated by a zero in the byte shown in
|
| 398 | <xref target="ref-address-flush-message-vlan-block-case"/> as "K-VLBs" followed by other information encoded as TLVs.</t>
|
| 399 |
|
| 400 | <figure title="Address Flush Message - Extensible Case" anchor="ref-address-flush-message-extensible-case"><artwork><![CDATA[
|
| 401 | 0 1 2 3
|
| 402 | 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
|
| 403 | RBridge Channel Header:
|
| 404 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 405 | | RBridge-Channel (0x8946) | 0x0 |Channel Protocol=0x009 |
|
| 406 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 407 | | Flags | ERR |
|
| 408 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 409 | Address Flush Protocol Specific:
|
| 410 | +-+-+-+-+-+-+-+-+
|
| 411 | | K-nicks |
|
| 412 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 413 | | Nickname 1 | Nickname 2 |
|
| 414 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 415 | | Nickname ... | Nickname K-nicks |
|
| 416 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 417 | | 0 | TLVs ...
|
| 418 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+...
|
| 419 | ]]></artwork>
|
| 420 | </figure>
|
| 421 |
|
| 422 | <t><list style="hanging" hangIndent="3"><t hangText="Channel Protocol, K-nicks, Nickname:">These fields are as specified
|
| 423 | in <xref target="section-2.1"/>.
|
| 424 | </t>
|
| 425 |
|
| 426 | <t hangText="TLVs:">If the byte immediately before the TLVs field, which is the byte labeled "K-VLBs" in <xref target="ref-address-flush-message-vlan-block-case"/>, is zero, as shown in <xref target="ref-address-flush-message-extensible-case"/>, the remainder of the message consists of TLVs encoded as
|
| 427 | shown in <xref target="ref-type-length-value"/>.
|
| 428 | </t>
|
| 429 |
|
| 430 | </list>
|
| 431 | </t>
|
| 432 |
|
| 433 |
|
| 434 |
|
| 435 | <figure title="Type, Length, Value" anchor="ref-type-length-value"><artwork><![CDATA[
|
| 436 | 0 1 2 3 4 5 6 7 0 1 2 3 4 5 6 7
|
| 437 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|
| 438 | | Type | Length | Value
|
| 439 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|
| 440 | ]]></artwork>
|
| 441 | </figure>
|
| 442 |
|
| 443 | <t><list style="hanging" hangIndent="3"><t hangText="Type:">The 8-bit TLV type as shown in the table below. See
|
| 444 | subsections of <xref target="section-2.2"/> for details on each type
|
| 445 | assigned below. If the type is reserved or not known by a
|
| 446 | receiving RBridge, that receiving RBridge ignores the value and
|
| 447 | skips to the next TLV by use of the Length byte. There is no
|
| 448 | provision for a list of VLAN ID TLVs as there are few enough of
|
| 449 | them that an arbitrary subset of VLAN IDs can be represented as
|
| 450 | a bit map.
|
| 451 | </t>
|
| 452 |
|
| 453 | </list>
|
| 454 | </t>
|
| 455 |
|
| 456 |
|
| 457 | <figure><artwork><![CDATA[
|
| 458 | Type Description Reference
|
| 459 | ------ ------------------ -----------------
|
| 460 | 0 Reserved [RFC8383]
|
| 461 | 1 Blocks of VLANs [RFC8383]
|
| 462 | 2 Bit Map of VLANs [RFC8383]
|
| 463 | 3 Blocks of FGLs [RFC8383]
|
| 464 | 4 List of FGLs [RFC8383]
|
| 465 | 5 Bit Map of FGLs [RFC8383]
|
| 466 | 6 All Data Labels [RFC8383]
|
| 467 | 7 MAC Address List [RFC8383]
|
| 468 | 8 MAC Address Blocks [RFC8383]
|
| 469 | 9-254 Unassigned
|
| 470 | 255 Reserved [RFC8383]
|
| 471 | ]]></artwork>
|
| 472 | </figure>
|
| 473 |
|
| 474 | <t><list style="hanging" hangIndent="3"><t hangText="Length:">The 8-bit unsigned integer length in bytes of the
|
| 475 | remaining information in the TLV after the length byte. The
|
| 476 | length MUST NOT imply that the value extends beyond the end of the
|
| 477 | RBridge Channel Protocol Specific Payload area. If it does, the
|
| 478 | Address Flush message is corrupt and MUST be ignored.
|
| 479 | </t>
|
| 480 |
|
| 481 | </list>
|
| 482 | </t>
|
| 483 |
|
| 484 |
|
| 485 |
|
| 486 | <t><list hangIndent="3" style="hanging"><t hangText="Value:">Depends on the TLV type.</t>
|
| 487 |
|
| 488 | </list>
|
| 489 | </t>
|
| 490 |
|
| 491 | <t>
|
| 492 | In an extensible Address Flush message, when the TLVs are parsed,
|
| 493 | those TLVs having unknown types are ignored by the receiving RBridge.
|
| 494 | There may be multiple instances of TLVs with the same Type in the
|
| 495 | same address flush message, and TLVs are not required to be in any
|
| 496 | particular order.</t>
|
| 497 |
|
| 498 | <t><list style="symbols"><t>All RBridges implementing the Address Flush RBridge Channel
|
| 499 | message MUST implement types 1 and 2, the VLAN types, and type 6,
|
| 500 | which indicates addresses are to be flushed for all Data Labels.</t>
|
| 501 |
|
| 502 | <t>RBridges that implement the Address Flush message and implement
|
| 503 | FGL ingress/egress MUST implement types 3, 4, and 5, the FGL
|
| 504 | types. (An RBridge that is merely FGL safe <xref target="RFC7172"/>, but cannot
|
| 505 | egress FGL TRILL Data packets, SHOULD ignore the FGL types, as it
|
| 506 | will not learn any FGL-scoped MAC addresses from the data plane.)</t>
|
| 507 |
|
| 508 | <t>RBridges that implement the Address Flush message SHOULD implement
|
| 509 | types 7 and 8 so that specific MAC addresses can be flushed. If
|
| 510 | they do not, the effect will be to flush all MAC addresses for the
|
| 511 | indicated Data Labels, which may be inefficient as any MAC
|
| 512 | addresses not intended to be flushed will have to be relearned.</t>
|
| 513 |
|
| 514 | </list>
|
| 515 | </t>
|
| 516 |
|
| 517 | <t>
|
| 518 | The parsing of the TLVs by a receiving RBridge results in three pieces
|
| 519 | of information:</t>
|
| 520 |
|
| 521 | <t><list style="empty" hangIndent="3">
|
| 522 | <t><list style="numbers"><t>a flag indicating whether one or more Type 6 TLVs (All Data
|
| 523 | Labels) were encountered;</t>
|
| 524 |
|
| 525 | <t>a set of Data Labels accumulated from VLAN and/or FGL
|
| 526 | specifying TLVs in the message; and,</t>
|
| 527 | <!--[rfced] This sentence does not seem to parse. Please rephrase.
|
| 528 |
|
| 529 | Original:
|
| 530 | if the MAC address TLV types are implemented, and a set of MAC
|
| 531 | addresses accumulated from MAC address specifying TLVs in the message.
|
| 532 |
|
| 533 | -->
|
| 534 | <t>if the MAC address TLV types are implemented, and a set of MAC
|
| 535 | addresses accumulated from MAC address specifying TLVs in the
|
| 536 | message.</t>
|
| 537 |
|
| 538 | </list>
|
| 539 | </t>
|
| 540 |
|
| 541 | </list>
|
| 542 | </t>
|
| 543 |
|
| 544 | <t>
|
| 545 | VLANs/FGLs might be indicated more than once due to overlapping
|
| 546 | blocks or the like, and a VLAN/FGL is included in the above set of
|
| 547 | VLANs/FGLs if it occurs in any TLV in the address flush message. A
|
| 548 | MAC address might be indicated more than once due to overlapping
|
| 549 | blocks or the like, and a particular MAC address is included in the above set of
|
| 550 | MAC addresses if it occurs in any TLV in the address flush message.</t>
|
| 551 |
|
| 552 | <t>
|
| 553 | After the above information has been accumulated by parsing the TLVs,
|
| 554 | three sets are derived as described below: a set of nicknames, a set
|
| 555 | of Data Labels, and a set of MAC addresses. The address flush
|
| 556 | operation at the receiver applies to the cross product of these
|
| 557 | derived sets. That is, a { Data Label, MAC address, nickname } triple
|
| 558 | is flushed if and only if the Data Label matches an element in the
|
| 559 | derived set of Data Labels, the MAC address matches an element in the
|
| 560 | derived set of MAC address, and the nickname matches an element in
|
| 561 | the derived set of nicknames. In the case of Data Labels and MAC
|
| 562 | addresses, a special value of the set, {ALL}, is permitted, which
|
| 563 | matches all values.</t>
|
| 564 |
|
| 565 | <figure><artwork><![CDATA[
|
| 566 | The sets are derived as follows:
|
| 567 |
|
| 568 | Data Labels set:
|
| 569 | If the Type 6 TLV has been encountered, the set is {ALL}, else,
|
| 570 | if any Data Labels have been accumulated by processing Data
|
| 571 | Label TLVs (Types 1, 2, 3, 4, and 5), the set is those
|
| 572 | accumulated Data Labels, else,
|
| 573 | the Data Labels set is null and the address flush message does
|
| 574 | nothing.
|
| 575 |
|
| 576 | MAC Addresses set:
|
| 577 | In the receiver does not implement the MAC address types (Types
|
| 578 | 7 and 8) or it does implement those types but no MAC
|
| 579 | addresses are accumulated in parsing the TLVs, then the MAC
|
| 580 | Address set is {ALL},
|
| 581 | else, the MAC Addresses set is the set of MAC addresses
|
| 582 | accumulated in processing the TLVs.
|
| 583 |
|
| 584 | Nicknames set:
|
| 585 | If the K-nicks field in the Address Flush message was zero,
|
| 586 | then the ingress nickname in the TRILL Header of the message
|
| 587 | is the sole nickname set member, else,
|
| 588 | the nicknames set members are the K-nicks nicknames listed in
|
| 589 | the Address Flush message.
|
| 590 | ]]></artwork>
|
| 591 | </figure>
|
| 592 |
|
| 593 | <t>
|
| 594 | The various formats below are provided for encoding efficiency. A
|
| 595 | block of values is most efficient when there are a number of
|
| 596 | consecutive values. A bit map is most efficient if there are
|
| 597 | scattered values within a limited range. And a list of single values
|
| 598 | is most efficient if there are widely scattered values.</t>
|
| 599 |
|
| 600 | <section title="Blocks of VLANs" anchor="section-2.2.1"><t>
|
| 601 | If the TLV Type is 1, the value is a list of blocks of VLANs as
|
| 602 | follows:</t>
|
| 603 |
|
| 604 | <figure><artwork><![CDATA[
|
| 605 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 606 | | Type = 1 | Length |
|
| 607 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 608 | | RESV | Start.VLAN 1 | RESV | End.VLAN 1 |
|
| 609 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 610 | | RESV | Start.VLAN 2 | RESV | End.VLAN 2 |
|
| 611 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 612 | | RESV | Start.VLAN ... | RESV | End.VLAN ... |
|
| 613 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 614 | ]]></artwork>
|
| 615 | </figure>
|
| 616 | <t>
|
| 617 | The meaning of Start.VLAN and End.VLAN is as specified in <xref target="section-2.1"/>. Length MUST be a multiple of 4. If Length is not a multiple of
|
| 618 | 4, the TLV is corrupt and the Address Flush message MUST be
|
| 619 | discarded.</t>
|
| 620 |
|
| 621 | </section>
|
| 622 |
|
| 623 | <section title="Bit Map of VLANs" anchor="section-2.2.2"><t>If the TLV Type is 2, the value is a bit map of VLANs as follows:</t>
|
| 624 |
|
| 625 | <figure><artwork><![CDATA[
|
| 626 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 627 | | Type = 2 | Length |
|
| 628 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|
| 629 | | RESV | Start.VLAN | Bits...
|
| 630 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-
|
| 631 | ]]></artwork>
|
| 632 | </figure>
|
| 633 | <t>
|
| 634 | The value portion of the TLV begins with two bytes having the 12-bit
|
| 635 | starting VLAN ID right justified (the top 4 bits are as specified in
|
| 636 | <xref target="section-2.1"/> RESV). This is followed by bytes with one bit per VLAN
|
| 637 | ID. The high order bit of the first byte is for VLAN N. The next-to-the-highest order bit is for VLAN N+1. The low order bit of the first
|
| 638 | byte is for VLAN N+7. The high order bit of the second byte, if there
|
| 639 | is a second byte, is for VLAN N+8, and so on. If that bit is a one,
|
| 640 | the Address Flush message applies to that VLAN. If that bit is a
|
| 641 | zero, then addresses that have been learned in that VLAN are not
|
| 642 | flushed. Note that Length MUST be at least 2. If Length is 0 or 1,
|
| 643 | the TLV is corrupt and the Address Flush message MUST be discarded.
|
| 644 | VLAN IDs do not wrap around. If there are enough bytes so that some
|
| 645 | bits correspond to VLAN ID 0xFFF or higher, those bits are ignored,
|
| 646 | but the message is still processed for bits corresponding to valid
|
| 647 | VLAN IDs.</t>
|
| 648 |
|
| 649 | </section>
|
| 650 |
|
| 651 | <section title="Blocks of FGLs" anchor="section-2.2.3"><t>
|
| 652 | If the TLV Type is 3, the value is a list of blocks of FGLs as
|
| 653 | follows:</t>
|
| 654 |
|
| 655 | <figure><artwork><![CDATA[
|
| 656 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 657 | | Type = 3 | Length |
|
| 658 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 659 | | Start.FGL 1 |
|
| 660 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 661 | | End.FGL 1 |
|
| 662 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 663 | | Start.FGL 2 |
|
| 664 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 665 | | End.FGL 2 |
|
| 666 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 667 | | Start.FGL ... |
|
| 668 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 669 | | End.FGL ... |
|
| 670 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 671 | ]]></artwork>
|
| 672 | </figure>
|
| 673 | <t>
|
| 674 | The TLV value consists of sets of Start.FGL and End.FGL numbers. The
|
| 675 | Address Flush information applies to the FGLs in that range,
|
| 676 | inclusive. A single FGL is indicated by setting both Start.FGL and
|
| 677 | End.FGL to the same value. If End.FGL is less than Start.FGL,
|
| 678 | considering them as unsigned integers, that block is ignored, but the
|
| 679 | Address Flush message is still processed for any other blocks
|
| 680 | present. For this Type, Length MUST be a multiple of 6; if it is not,
|
| 681 | the TLV is corrupt and the Address Flush message MUST be discarded if
|
| 682 | the receiving RBridge implements Type 3.</t>
|
| 683 |
|
| 684 | </section>
|
| 685 |
|
| 686 | <section title="list of FGLs" anchor="section-2.2.4"><t>If the TLV Type is 4, the value is a list of FGLs as follows:</t>
|
| 687 |
|
| 688 | <figure><artwork><![CDATA[
|
| 689 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 690 | | Type = 4 | Length |
|
| 691 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 692 | | FGL 1 |
|
| 693 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 694 | | FGL 2 |
|
| 695 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 696 | | FGL ... |
|
| 697 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 698 | ]]></artwork>
|
| 699 | </figure>
|
| 700 | <t>
|
| 701 | The TLV value consists of FGL numbers each in 3 bytes. The Address
|
| 702 | Flush message applies to those FGLs. For this Type, Length MUST be a
|
| 703 | multiple of 3; if it is not, the TLV is corrupt and the address flush
|
| 704 | Message MUST be discarded if the receiving RBridge implements Type 4.</t>
|
| 705 |
|
| 706 | </section>
|
| 707 |
|
| 708 | <section title="Big Map of FGLs" anchor="section-2.2.5"><t>If the TLV Type is 5, the value is a bit map of FGLs as follows:</t>
|
| 709 |
|
| 710 |
|
| 711 | <figure><artwork><![CDATA[
|
| 712 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 713 | | Type = 5 | Length |
|
| 714 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 715 | | Start.FGL |
|
| 716 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 717 | | Bits...
|
| 718 | +-+-+-+-+-+-+-+-
|
| 719 | ]]></artwork>
|
| 720 | </figure>
|
| 721 | <t>
|
| 722 | The TLV value consists of three bytes with the 24-bit starting FGL
|
| 723 | value N. This is followed by bytes with one bit per FGL. The high
|
| 724 | order bit of the first byte is for FGL N. The next-to-the-highest
|
| 725 | order bit is for FGL N+1. The low order bit of the first byte is for
|
| 726 | FGL N+7. The high order bit of the second byte, if there is a second
|
| 727 | byte, is for FGL N+8, and so on. If that bit is a one, the Address
|
| 728 | Flush message applies to that FGL. If that bit is a zero, then
|
| 729 | addresses that have been learned in that FGL are not flushed. Note
|
| 730 | that Length MUST be at least 3. If Length is 0, 1, or 2 for a Type 5
|
| 731 | TLV, the TLV is corrupt and the Address Flush message MUST be
|
| 732 | discarded if type 5 is implemented. FGLs do not wrap around. If
|
| 733 | there are enough bytes so that some bits correspond to an FGL higher
|
| 734 | than 0xFFFFFF, those bits are ignored, but the message is still
|
| 735 | processed for bits corresponding to valid FGLs.</t>
|
| 736 |
|
| 737 | </section>
|
| 738 |
|
| 739 | <section title="All Data Labels" anchor="section-2.2.6"><t>If the TLV Type is 6, the value is null as follows:</t>
|
| 740 |
|
| 741 | <figure><artwork><![CDATA[
|
| 742 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 743 | | Type = 6 | Length = 0 |
|
| 744 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 745 | ]]></artwork>
|
| 746 | </figure>
|
| 747 | <t>
|
| 748 | This type is used when an RBridge wants to withdraw all addresses for
|
| 749 | all the Data Labels (all VLANs and FGLs). Length MUST be zero. If
|
| 750 | Length is any other value, the TLV is corrupt and the Address Flush
|
| 751 | message MUST be discarded.</t>
|
| 752 |
|
| 753 | </section>
|
| 754 |
|
| 755 | <section title="MAC Address List" anchor="section-2.2.7"><t>
|
| 756 | If the TLV Type is 7, the value is a list of MAC addresses as
|
| 757 | follows:</t>
|
| 758 |
|
| 759 | <figure><artwork><![CDATA[
|
| 760 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 761 | | Type = 7 | Length |
|
| 762 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 763 | | MAC 1 upper half |
|
| 764 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 765 | | MAC 1 lower half |
|
| 766 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 767 | | MAC 2 upper half |
|
| 768 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 769 | | MAC 2 lower half |
|
| 770 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 771 | | MAC ... upper half |
|
| 772 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 773 | | MAC ... lower half |
|
| 774 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 775 | ]]></artwork>
|
| 776 | </figure>
|
| 777 | <t>
|
| 778 | The TLV value consists of a list of 48-bit MAC addresses. Length MUST
|
| 779 | be a multiple of 6. If it is not, the TLV is corrupt, and the Address
|
| 780 | Flush message MUST be discarded if the receiving RBridge implements
|
| 781 | Type 7.</t>
|
| 782 |
|
| 783 | </section>
|
| 784 |
|
| 785 | <section title="MAC Address Blocks" anchor="section-2.2.8"><t>
|
| 786 | If the TLV Type is 8, the value is a list of blocks of MAC addresses
|
| 787 | as follows:</t>
|
| 788 |
|
| 789 | <figure><artwork><![CDATA[
|
| 790 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 791 | | Type = 8 | Length |
|
| 792 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 793 | | MAC.start 1 upper half |
|
| 794 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 795 | | MAC.start 1 lower half |
|
| 796 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 797 | | MAC.end 1 upper half |
|
| 798 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 799 | | MAC.end 1 lower half |
|
| 800 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 801 | | MAC.start 2 upper half |
|
| 802 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 803 | | MAC.start 2 lower half |
|
| 804 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 805 | | MAC.end 2 upper half |
|
| 806 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 807 | | MAC.end 2 lower half |
|
| 808 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 809 | | MAC.start ... upper half |
|
| 810 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 811 | | MAC.start ... lower half |
|
| 812 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 813 | | MAC.end ... upper half |
|
| 814 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 815 | | MAC.end ... lower half |
|
| 816 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
| 817 | ]]></artwork>
|
| 818 | </figure>
|
| 819 | <t>
|
| 820 | The TLV value consists of sets of Start.MAC and End.MAC numbers. The
|
| 821 | Address Flush information applies to the 48-bit MAC Addresses in that
|
| 822 | range, inclusive. A single MAC address is indicated by setting both
|
| 823 | Start.MAC and End.MAC to the same value. If End.MAC is less than
|
| 824 | Start.MAC, considering them as unsigned integers, that block is
|
| 825 | ignored but the Address Flush message is still processed for any
|
| 826 | other blocks present. For this Type, Length MUST be a multiple of 12;
|
| 827 | if it is not, the TLV is corrupt and the Address Flush message MUST
|
| 828 | be discarded if the receiving RBridge implements Type 7.</t>
|
| 829 |
|
| 830 | </section>
|
| 831 |
|
| 832 | </section>
|
| 833 |
|
| 834 | </section>
|
| 835 |
|
| 836 | <section title="IANA Considerations" anchor="section-3">
|
| 837 |
|
| 838 | <section title="Address Flush RBridge Channel Protocol Number" anchor="section-3.1"><t>
|
| 839 | IANA has assigned 0x009 as the Address Flush RBridge Channel
|
| 840 | Protocol number from the range of RBridge Channel protocols allocated
|
| 841 | by Standards Action <xref target="RFC7178"/> <xref target="RFC8126"/>.</t>
|
| 842 |
|
| 843 | <t>
|
| 844 | The added entry to the "RBridge Channel Protocols" registry at <https://www.iana.org/assignments/trill-parameters/> is as follows:</t>
|
| 845 |
|
| 846 | <figure><artwork><![CDATA[
|
| 847 | Protocol Description Reference
|
| 848 | -------- -------------- ------------------
|
| 849 | 0x009 Address Flush [RFC8383]
|
| 850 | ]]></artwork>
|
| 851 | </figure>
|
| 852 | </section>
|
| 853 |
|
| 854 | <section title="TRILL Address Flush TLV Types" anchor="section-3.2"><t>
|
| 855 | IANA has created the "TRILL Address Flush TLV Types" registry
|
| 856 | at <https://www.iana.org/assignments/trill-parameters/> as a subregistry of the "RBridge Channel
|
| 857 | Protocols" registry.
|
| 858 |
|
| 859 | <!--[rfced] Please review our update to the description of the relationship between the "RBridge Channel Protocols" registry and the "TRILL Address Flush TLV Types" registry (i.e., please confirm that the latter is a subregistry).
|
| 860 |
|
| 861 | -->
|
| 862 | Registry headers are as below. The initial
|
| 863 | entries are as in the table in <xref target="section-2.2"/>.</t>
|
| 864 |
|
| 865 | <figure><artwork><![CDATA[
|
| 866 | Registry: TRILL Address Flush TLV Types
|
| 867 | Registration Procedures: IETF Review
|
| 868 | Reference: [RFC8383]
|
| 869 | ]]></artwork>
|
| 870 | </figure>
|
| 871 |
|
| 872 |
|
| 873 |
|
| 874 | </section>
|
| 875 |
|
| 876 | </section>
|
| 877 |
|
| 878 | <section title="Security Considerations" anchor="section-4"><t>
|
| 879 | The Address Flush RBridge Channel Protocol itself provides no
|
| 880 | security assurances or features. However, Address Flush protocol
|
| 881 | messages can be secured by use of the RBridge Channel Header
|
| 882 | Extension <xref target="RFC7978"/>. It is RECOMMENDED that all RBridges that
|
| 883 | implement the address flush message be configured to ignore such
|
| 884 | messages unless they have been secured with an RBridge Channel Header
|
| 885 | Extension that meets local security policy.</t>
|
| 886 |
|
| 887 | <t>
|
| 888 | If RBridges receiving Address Flush messages do not require them to
|
| 889 | be at least authenticated, they are relatively easy to forge. In that
|
| 890 | case, such forged Address Flush messages can reduce network
|
| 891 | efficiency, by purging useful learned information that will have to
|
| 892 | be relearned. This provides a denial-of-service attack, but cannot
|
| 893 | cause incorrect operation in the sense that it cannot cause a frame
|
| 894 | to be improperly delivered.</t>
|
| 895 |
|
| 896 | <t>
|
| 897 | See <xref target="RFC7178"/> for general RBridge Channel Security Considerations.</t>
|
| 898 |
|
| 899 | <t>
|
| 900 | See <xref target="RFC6325"/> for general TRILL Security Considerations.</t>
|
| 901 |
|
| 902 | </section>
|
| 903 | </middle>
|
| 904 | <back>
|
| 905 |
|
| 906 |
|
| 907 |
|
| 908 | <references title="Normative References">
|
| 909 |
|
| 910 | <?rfc include="reference.RFC.2119"?>
|
| 911 | <?rfc include="reference.RFC.6325"?>
|
| 912 | <?rfc include="reference.RFC.7172"?>
|
| 913 | <?rfc include="reference.RFC.7178"?>
|
| 914 | <?rfc include="reference.RFC.7780"?>
|
| 915 | <?rfc include="reference.RFC.7978"?>
|
| 916 | <?rfc include="reference.RFC.8174"?>
|
| 917 |
|
| 918 |
|
| 919 | </references>
|
| 920 |
|
| 921 | <references title="Informative References">
|
| 922 |
|
| 923 | <?rfc include="reference.RFC.4762"?>
|
| 924 | <?rfc include="reference.RFC.8126"?>
|
| 925 |
|
| 926 | </references>
|
| 927 |
|
| 928 |
|
| 929 | <section title="Acknowledgements" numbered="no" anchor="acknowledgements"><t><list style="hanging" hangIndent="3"><t hangText="The following are thanked for their contributions:">
|
| 930 | <vspace blankLines="1"/>
|
| 931 | Ramkumar Parameswaran, Henning Rogge
|
| 932 | </t>
|
| 933 |
|
| 934 | </list>
|
| 935 | </t>
|
| 936 |
|
| 937 | <!--[rfced] Throughout the text, the following terminology appears to be used inconsistently.
|
| 938 |
|
| 939 | Please review these occurrences and let us know if/how they may be made
|
| 940 | consistent.
|
| 941 |
|
| 942 | RBridge Channel messages vs. RBridge Channel protocol message
|
| 943 |
|
| 944 | Address Flush message vs. address flush messages vs. address flush Message
|
| 945 |
|
| 946 | type # vs. Type # (e.g., type 6 vs. Type 6)
|
| 947 |
|
| 948 | length bypte vs. Length byte
|
| 949 |
|
| 950 | -->
|
| 951 |
|
| 952 |
|
| 953 | </section>
|
| 954 |
|
| 955 | </back>
|
| 956 |
|
| 957 | </rfc>
|
| 958 |
|