%% You should probably cite rfc6439 instead of this I-D. @techreport{ietf-trill-rbridge-af-05, number = {draft-ietf-trill-rbridge-af-05}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-trill-rbridge-af/05/}, author = {Radia Perlman and Ayan Banerjee and fangwei hu and Donald E. Eastlake 3rd and Yizhou Li}, title = {{Routing Bridges (RBridges): Appointed Forwarders}}, pagetotal = 15, year = 2011, month = sep, day = 26, abstract = {The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides least cost pair-wise data forwarding without configuration in multi-hop networks with arbitrary topology, safe forwarding even during periods of temporary loops, and support for multipathing of both unicast and multicast traffic. TRILL accomplishes this by using IS-IS (Intermediate System to Intermediate System) link state routing and by encapsulating traffic using a header that includes a hop count. Devices that implement TRILL are called "RBridges" (Routing Bridges). TRILL supports multi-access LAN (Local Area Network) links that can have multiple end stations and RBridges attached. Where multiple RBridges are attached to a link, native traffic to and from end stations on that link is handled by a subset of those RBridges called "Appointed Forwarders", with the intent that native traffic in each VLAN (Virtual LAN) be handled by at most one RBridge. The purpose of this document is to improve the documentation of the Appointed Forwarder mechanism; thus, it updates RFC 6325. {[}STANDARDS-TRACK{]}}, }