Skip to main content

TRILL: Adjacency
draft-eastlake-trill-rfc6327bis-00

Document Type Replaced Internet-Draft (trill WG)
Expired & archived
Authors Donald E. Eastlake 3rd , Radia Perlman , Anoop Ghanwani , Vishwas Manral
Last updated 2013-06-27 (Latest revision 2013-04-28)
Replaced by draft-ietf-trill-rfc6327bis
RFC stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Formats
Additional resources Mailing list discussion
Stream WG state Adopted by a WG
Document shepherd (None)
IESG IESG state Replaced by draft-ietf-trill-rfc6327bis
Consensus boilerplate Unknown
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:

Abstract

The IETF TRILL (TRansparent Interconnection of Lots of Links) protocol supports arbitrary link technologies between TRILL switches including point-to-point links and multi-access LAN (Local Area Network) links that can have multiple TRILL switches and end stations attached. TRILL uses IS-IS (Intermediate System to Intermediate System) routing. This document specifies the establishment, reporting, and termination of IS-IS adjacency between TRILL switches, also known as RBridges. It also concerns four other link-local aspects of TRILL: Designated RBridge (DRB) selection, MTU (Maximum Transmission Unit) testing, pseudonode creation, and BFD (Bi- Directional Forwarding Detection) session bootstrapping in connection with adjacency. State diagrams are included where appropriate. This document obsoletes RFC 6327 and updates RFC 6325.

Authors

Donald E. Eastlake 3rd
Radia Perlman
Anoop Ghanwani
Vishwas Manral

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