Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 7177

Transparent Interconnection of Lots of Links (TRILL): Adjacency,May 2014

File formats:
icon for text fileicon for PDFicon for HTML
Status:
PROPOSED STANDARD
Obsoletes:
RFC 6327
Updates:
RFC 6325
Updated by:
RFC 7780,RFC 8139,RFC 8249,RFC 8377,RFC 8564
Authors:
D. Eastlake 3rd
R. Perlman
A. Ghanwani
H. Yang
V. Manral
Stream:
IETF
Source:
trill (int)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7177

Discuss this RFC: Send questions or comments to the mailing listtrill@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7177


Abstract

The IETF Transparent Interconnection of Lots of Links (TRILL)protocol supports arbitrary link technologies between TRILL switches,including point-to-point links and multi-access Local AreaNetwork (LAN) links that can have multiple TRILL switches and end stationsattached. TRILL uses Intermediate System to IntermediateSystem (IS-IS) routing. This document specifies the establishment,reporting, and termination of IS-IS adjacencies between TRILLswitches, also known as RBridges (Routing Bridges). It also concernsfour other link-local aspects of TRILL: Designated RBridge (DRB)selection, MTU (Maximum Transmission Unit) testing, pseudonodecreation, and BFD (Bidirectional Forwarding Detection) sessionbootstrapping in connection with adjacency. State diagrams areincluded where appropriate. This document obsoletes RFC 6327 andupdates RFC 6325.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp