metasystema.org
ObsoletedPROPOSED STANDARDIETF stream

RFC 6439: Routing Bridges (RBridges): Appointed Forwarders

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 8139.

Current version: RFC 8139 — Transparent Interconnection of Lots of Links (TRILL): Appointed Forwarders

In plain English — editorial summary, not part of the RFC

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]

Document record

Document ID
RFC6439
Published
November 2011
Authors
R. Perlman; D. Eastlake; Y. Li; A. Banerjee; F. Hu
Status
PROPOSED STANDARD
Stream
IETF
Area
rtg
Pages
15
Also known as
—
Obsoleted by:
RFC 8139
Updates:
RFC 6325
Updated by:
RFC 7180

Topics

Referenced by

2 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/6439-routing-bridges-rbridges-appointed-forwarders