TRILL Edge Directory Assistance Framework
draft-ietf-trill-directory-framework-01

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2012-10-22
Replaces draft-dunbar-trill-directory-assisted-edge
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TRILL working group                                           L. Dunbar
Internet Draft                                              D. Eastlake
Category: Informational                                          Huawei
                                                          Padia Perlman
                                                                  Intel
                                                         Igor Gashinsky
                                                                  Yahoo

Expires: April 2013                                    October 22, 2012

                 TRILL Edge Directory Assistance Framework

                  draft-ietf-trill-directory-framework-01

Status of this Memo

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

   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/ietf/1id-abstracts.txt.

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

Copyright Notice

   Copyright (c) 2012 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

Dunbar, et al           Expires November 2013                 [Page 1]
Internet-Draft       TRILL Directory Assistance Framework      Oct 2012

   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.

Abstract

   Edge RBridges currently learn the mapping between MAC addresses and
   their egress RBridges by observing the data packets traversed
   through. When an ingress RBridge receives a data frame with its
   destination address (MAC&VLAN) unknown, the data frame is flooded
   within the VLAN across the TRILL campus. When there are more than
   one RBridge ports connected to one bridged LAN, only one of them can
   be designated as the Appointed Forwarder port for
   forwarding/receiving native traffic to/from each VLAN, the other
   RBridge ports on that LAN have to be disabled for native traffic in
   that VLAN.

   This draft describes the framework for using directory services to
   assist edge RBridges by reducing multi-destination frames,
   particularly unknown unicast frames flooding, and ARP/ND, improving
   TRILL network scalability in environment, such as data centers.

Conventions used in this document

   The terms ''Subnet'' and ''VLAN'' are used interchangeably in this
   document because it is common to map one subnet to one VLAN. The
   terms ''TRILL switch'' and ''RBridge'' are used interchangeably in
   this document.

Table of Contents

   1. Introduction ................................................ 4
   2. Terminology ................................................. 5
   3. RBridge Campus Impact of Massive Number of End Stations in a DC5
      3.1. Issues of Flooding Based Learning in DCs ................5
      3.2. Some Examples .......................................... 7
   4. Benefits of Directory Assisted Edge RBridge in DC ............8
   5. Generic operation of Directory Assistance ....................9
      5.1. Information in Directory for Edge Bridges ...............9
      5.2. Push Model ............................................ 10
      5.3. Pull Model ............................................ 11
   6. Conclusion and Recommendation............................... 12
   7. Security Considerations..................................... 12
   8. IANA Considerations ........................................ 12

Dunbar, et al                                                [Page 2]
Internet-Draft       TRILL Directory Assistance Framework      Oct 2012

   9. Acknowledgements ........................................... 13
   10. References ................................................ 13
      10.1. Normative References.................................. 13
      10.2. Informative References................................ 13
Show full document text