[Docs] [txt|pdf] [Tracker] [WG] [Email] [Nits]

Versions: 00

INTERNET-DRAFT                                           Donald Eastlake
Intended status: Proposed Standard                          Linda Dunbar
                                                                  Huawei
                                                           Radia Perlman
                                                                     EMC
                                                              Fangwei Hu
                                                                     ZTE
Expires: January 7, 2017                                    July 8, 2016


                       TRILL Directory Extensions
             <draft-ietf-trill-directory-extensions-00.txt>


Abstract

   TRILL (Transparent Interconnection of Lots of Links) push and pull
   directories (RFC 7067) specified in draft-ietf-trill-directory-
   assist-mechanisms provide directory services to TRILL switches but
   not to end stations. This document extends those services so that end
   stations can pull directory information from Pull Directory severs
   and can have directory information pushed to them from Push Directory
   servers. In each case, at least one co-operating edge TRILL switch is
   required.


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 authors or the TRILL working group mailing list:
   trill@ietf.org

   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                            Directory Assisted TRILL Encap


Table of Contents

      1. Introduction............................................3
      1.1 Terminology............................................3

      2. Extensions to Pull Directory............................4

      3. Extensions to Push Directory............................5

      4. IANA Considerations.....................................6

      5. Security Considerations.................................7

      Normative References.......................................8
      Informative References.....................................8

      Acknowledgments............................................8

      Authors' Addresses.........................................9

































D. Eastlake, et al                                              [Page 2]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


1. Introduction

   TRILL (Transparent Interconnection of Lots of Links) [RFC6325] push
   and pull directories [RFC7067] specified in [Directory] provide
   directory services to TRILL switches but not to end stations. This
   document extends those services so that end stations can pull
   directory information from Pull Directory severs and can have
   directory information pushed to them from Push Directory servers. In
   each case, at least one co-operating edge RBridge is required.

   Section 2 specifies the extensions to Pull Directories. Section 3
   Specifies the extensions to Push Directories.



1.1 Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

   TBD






























D. Eastlake, et al                                              [Page 3]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


2. Extensions to Pull Directory

   Pull Directory support is optionally extended to end station clients
   as specified in this section.

   When Pull Directory support is provided by an edge RBridge to end
   stations, the messages used are as specified in [Directory] for the
   support of a Pull Directory hosted on an end station with the
   following changes:

   (1) a different RBridge Channel [RFC7178] protocol number is used,
       and

   (2) the roles of the end station and edge RBridge are reversed, that
       is, instead of the edge RBridge using a Pull Directory on an end
       station there is an end station using a Pull Directory service
       through an edge RBridge.

   An end station can tell which, if any, of the edge RBridges to which
   it is attached support this service by examining their TRILL IS-IS
   Hellos messages to see if they support the "Pull Directory Service to
   End Station" RBridge Channel Protocol (see Section 4).






























D. Eastlake, et al                                              [Page 4]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


3. Extensions to Push Directory

   TBD

















































D. Eastlake, et al                                              [Page 5]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


4. IANA Considerations

   IANA is requested to assign an RBridge Channel protocol number from
   the range assigned based on standards action as the "Pull Directory
   Service to End Station" protocol adding a line to the RBridge Channel
   Protocols registry on the TRILL Parameters web page as follows:

      Protocol Description                           Reference
      -------- -----------                           ---------
         TBD   Pull Directory Service to End Station [this document]










































D. Eastlake, et al                                              [Page 6]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


5. Security Considerations

   TBD

   For security considerations of directory services, see [Directory].

   For general TRILL security considerations, see [RFC6325].













































D. Eastlake, et al                                              [Page 7]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


Normative References

   [RFC2119] - Bradner, S., "Key words for use in RFCs to Indicate
          Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119,
          March 1997, <http://www.rfc-editor.org/info/rfc2119>.

   [RFC6325] - Perlman, R., Eastlake 3rd, D., Dutt, D., Gai, S., and A.
          Ghanwani, "Routing Bridges (RBridges): Base Protocol
          Specification", RFC 6325, DOI 10.17487/RFC6325, July 2011,
          <http://www.rfc-editor.org/info/rfc6325>.

   [RFC7178] - Eastlake 3rd, D., Manral, V., Li, Y., Aldrin, S., and D.
          Ward, "Transparent Interconnection of Lots of Links (TRILL):
          RBridge Channel Support", RFC 7178, DOI 10.17487/RFC7178, May
          2014, <http://www.rfc-editor.org/info/rfc7178>.

   [Directory] - D. Eastlake, L. Dunbar, R. Perlman, Y. Li, "TRILL: Edge
          Directory Assist Mechanisms", draft-ietf-trill-directory-
          assist-mechanisms, work in progress.



Informative References

   [RFC7067] - Dunbar, et, al "Directory Assistance Problem and High-
          Level Design Proposal", RFC7067, Nov, 2013.



Acknowledgments

   The document was prepared in raw nroff. All macros used were defined
   within the source file.



















D. Eastlake, et al                                              [Page 8]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


Authors' Addresses

      Donald Eastlake
      Huawei Technologies
      155 Beaver Street
      Milford, MA 01757 USA

      Phone: +1-508-333-2270
      Email: d3e3e3@gmail.com


      Linda Dunbar
      Huawei Technologies
      5340 Legacy Drive, Suite 175
      Plano, TX 75024, USA

      Phone: +1-469-277-5840
      Email: linda.dunbar@huawei.com


      Radia Perlman
      EMC
      2010 256th Avenue NE, #200
      Bellevue, WA 98007 USA

      Email: Radia@alum.mit.edu


      Fangwei Hu
      ZTE Corporation
      No.889 Bibo Rd
      Shanghai 201203 China

      Phone: +86 21 68896273
      Email: hu.fangwei@zte.com.cn

















D. Eastlake, et al                                              [Page 9]


INTERNET-DRAFT                            Directory Assisted TRILL Encap


Copyright, Disclaimer, and Additional IPR Provisions

   Copyright (c) 2016 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.  The definitive version of
   an IETF Document is that published by, or under the auspices of, the
   IETF. Versions of IETF Documents that are published by third parties,
   including those that are translated into other languages, should not
   be considered to be definitive versions of IETF Documents. The
   definitive version of these Legal Provisions is that published by, or
   under the auspices of, the IETF. Versions of these Legal Provisions
   that are published by third parties, including those that are
   translated into other languages, should not be considered to be
   definitive versions of these Legal Provisions.  For the avoidance of
   doubt, each Contributor to the IETF Standards Process licenses each
   Contribution that he or she makes as part of the IETF Standards
   Process to the IETF Trust pursuant to the provisions of RFC 5378. No
   language to the contrary, or terms, conditions or rights that differ
   from or are inconsistent with the rights and licenses granted under
   RFC 5378, shall have any effect and shall be null and void, whether
   published or posted by such Contributor, or included with or in such
   Contribution.





















D. Eastlake, et al                                             [Page 10]


Html markup produced by rfcmarkup 1.121, available from https://tools.ietf.org/tools/rfcmarkup/