TRILL: Edge Directory Assist Mechanisms
draft-ietf-trill-directory-assist-mechanisms-03

Document Type Active Internet-Draft (trill WG)
Last updated 2015-06-20
Replaces draft-dunbar-trill-scheme-for-directory-assist
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Susan Hares
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to "Susan Hares" <shares@ndzh.com>
INTERNET-DRAFT                                           Donald Eastlake
Intended status: Proposed Standard                          Linda Dunbar
                                                                  Huawei
                                                           Radia Perlman
                                                                     EMC
                                                          Igor Gashinsky
                                                                   Yahoo
                                                               Yizhou Li
                                                                  Huawei
Expires: December 19, 2015                                 June 20, 2015

                TRILL: Edge Directory Assist Mechanisms
         <draft-ietf-trill-directory-assist-mechanisms-03.txt>

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/ND and unknown unicast
   flooding. It can also be used to detect traffic with forged source
   addresses.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Distribution of this document is unlimited. Comments should be sent
   to the TRILL working group mailing list.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/1id-abstracts.html. The list of Internet-Draft
   Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

D. Eastlake, et al                                              [Page 1]
INTERNET-DRAFT                       TRILL: Directory Service Mechanisms

Table of Contents

      1. Introduction............................................3
      1.1 Uses of Directory Information..........................3
      1.2 Terminology............................................4

      2. Push Model Directory Assistance Mechanisms..............6
      2.1 Requesting Push Service................................6
      2.2 Push Directory Servers.................................6
      2.3 Push Directory Server State Machine....................7
      2.3.1 Push Directory States................................8
      2.3.2 Push Directory Events and Conditions.................9
      2.3.3 State Transition Diagram and Table..................10
      2.4 Additional Push Details...............................12
      2.5 Primary to Secondary Server Push Service..............13

      3. Pull Model Directory Assistance Mechanisms.............14
      3.1 Pull Directory Message Common Format..................15
      3.2 Pull Directory Query and Response Messages............16
      3.2.1 Pull Directory Query Message Format.................16
      3.2.2 Pull Directory Responses............................19
      3.2.2.1 Pull Directory Response Message Format............19
      3.2.2.2 Pull Directory Forwarding.........................21
      3.3 Cache Consistency.....................................22
      3.3.1 Update Message Format...............................25
      3.3.2 Acknowledge Message Format..........................26
      3.4 Summary of Records Formats in Messages................26
      3.5 Pull Directory Hosted on an End Station...............27
      3.6 Pull Directory Message Errors.........................28
      3.6.1 Error Codes.........................................29
      3.6.2 Sub-Errors Under Error Codes 1 and 3................30
      3.6.3 Sub-Errors Under Error Codes 128 and 131............30
      3.7 Additional Pull Details...............................31
      3.8 The No Data Flag......................................31

      4. Directory Use Strategies and Push-Pull Hybrids.........33
      5. Security Considerations................................35

      6. IANA Considerations....................................36
      6.1 ESADI-Parameter Data Extensions.......................36
      6.2 RBridge Channel Protocol Number.......................37
      6.3 The Pull Directory (PUL) and No Data (NOD) Bits.......37
      6.4 TRILL Pull Directory QTYPEs...........................37
      6.5 Pull Directory Error Code Registries..................38
Show full document text