<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.ietf-trill-rfc6327bis" target="https://datatracker.ietf.org/doc/html/draft-ietf-trill-rfc6327bis-00">
   <front>
      <title>TRILL: Adjacency</title>
      <author initials="D. E." surname="Eastlake" fullname="Donald E. Eastlake 3rd">
         </author>
      <author initials="R." surname="Perlman" fullname="Radia Perlman">
         </author>
      <author initials="A." surname="Ghanwani" fullname="Anoop Ghanwani">
         </author>
      <author initials="V." surname="Manral" fullname="Vishwas Manral">
         </author>
      <date month="June" day="18" year="2013" />
      <abstract>
	 <t>   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.



	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-ietf-trill-rfc6327bis-00" />
   
</reference>
