datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Routing Bridges (RBridges): Adjacency
draft-ietf-trill-adj-07

RFC
Document Stream: IETF
Last updated: 2011-04-29
Intended RFC status: Proposed Standard
Other versions: (expired, archived): plain text, pdf, html

IETF State: WG Document (trill)
Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 6327
IANA Action State: RFC-Ed-Ack 
Responsible AD: Ralph Droms
IESG Note: Erik Nordmark (nordmark@acm.org) is the document shepherd.
Send notices to: trill-chairs@tools.ietf.org, draft-ietf-trill-adj@tools.ietf.org

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-trill-adj.

Abstract:
The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol provides optimal pair-wise data forwarding without configuration, 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 Routing Bridges (RBridges).

Authors:
Radia Perlman <radia@alum.mit.edu>
Anoop Ghanwani <anoop@brocade.com>
Vishwas Manral <vishwas@ipinfusion.com>
Dinesh Dutt <ddutt@cisco.com>
Donald Eastlake <d3e3e3@gmail.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)