Transparent Interconnection of Lots of Links (TRILL): Edge Directory Assistance Mechanisms
RFC 8171

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06
• 07
• 08
• 09
• 10
• 11
• 12

draft-ietf-trill-directory-assist-mechanisms-12.txt:
xym 0.3.2:

Internet Engineering Task Force (IETF)                   D. Eastlake 3rd
Request for Comments: 8171                                     L. Dunbar
Category: Standards Track                                         Huawei
ISSN: 2070-1721                                               R. Perlman
                                                                     EMC
                                                                   Y. Li
                                                                  Huawei
                                                               June 2017

         Transparent Interconnection of Lots of Links (TRILL):
                  Edge Directory Assistance Mechanisms

Abstract

   This document describes mechanisms for providing directory service to
   TRILL (Transparent Interconnection of Lots of Links) edge switches.
   The directory information provided can be used in reducing multi-
   destination traffic, particularly ARP / Neighbor Discovery (ND) and
   unknown unicast flooding.  It can also be used to detect traffic with
   forged source addresses.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force
   (IETF).  It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).  Further information on
   Internet Standards is available in Section 2 of RFC 7841.

   Information about the current status of this document, any errata,
   and how to provide feedback on it may be obtained at
   http://www.rfc-editor.org/info/rfc8171.

Eastlake, et al.             Standards Track                    [Page 1]
RFC 8171           TRILL: Directory Service Mechanisms         June 2017

Copyright Notice

   Copyright (c) 2017 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1. Introduction ....................................................3
      1.1. Uses of Directory Information ..............................5
      1.2. Terminology ................................................6
   2. Push Model Directory Assistance Mechanisms ......................7
      2.1. Requesting Push Service ....................................7
      2.2. Push Directory Servers .....................................8
      2.3. Push Directory Server State Machine ........................9
           2.3.1. Push Directory States ...............................9
           2.3.2. Push Directory Events and Conditions ...............11
           2.3.3. State Transition Diagram and Table .................13
      2.4. End Stations and Push Directories .........................15
      2.5. Additional Push Details ...................................15
      2.6. Providing Secondary Servers with Data from a
           Primary Server ............................................16
      2.7. Push Directory Configuration ..............................17
   3. Pull Model Directory Assistance Mechanisms .....................17
      3.1. Pull Directory Message: Common Format .....................19
           3.1.1. Version Negotiation ................................20
      3.2. Pull Directory Query and Response Messages ................21
           3.2.1. Pull Directory Query Message Format ................21
           3.2.2. Pull Directory Responses ...........................24
                  3.2.2.1. Pull Directory Response Message Format ....24
                  3.2.2.2. Pull Directory Forwarding .................27
      3.3. Cache Consistency .........................................28
           3.3.1. Update Message Format ..............................32
           3.3.2. Acknowledge Message Format .........................33
      3.4. Summary of Record Formats in Messages .....................34

Eastlake, et al.             Standards Track                    [Page 2]
RFC 8171           TRILL: Directory Service Mechanisms         June 2017

      3.5. End Stations and Pull Directories .........................34
           3.5.1. Pull Directory Hosted on an End Station ............35
           3.5.2. Use of Pull Directory by End Stations ..............36
           3.5.3. Native Pull Directory Messages .....................37
      3.6. Pull Directory Message Errors .............................38