TRILL Smart Endnodes
draft-ietf-trill-smart-endnodes-00

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2014-12-15
Replaces draft-perlman-trill-smart-endnodes
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd Susan Hares
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Susan Hares" <shares@ndzh.com>
TRILL WG                                                  Radia. Perlman
Internet-Draft                                           EMC Corporation
Intended status: Standards Track                             Fangwei. Hu
Expires: June 18, 2015                                   ZTE Corporation
                                                    Donald. Eastlake 3rd
                                                       Huawei technology
                                                      Kesava. Krupakaran
                                                                    Dell
                                                              Ting. Liao
                                                         ZTE Corporation
                                                       December 15, 2014

                          TRILL Smart Endnodes
                 draft-ietf-trill-smart-endnodes-00.txt

Abstract

   This draft addresses the problem of the size and freshness of the
   endnode learning table in edge RBridges, by allowing endnodes to
   volunteer for endnode learning and encapsulation/decapsulation.  Such
   an endnode is known as a "smart endnode".  Only the attached RBridge
   can distinguish a "smart endnode" from a "normal endnode".  The smart
   endnode uses the nickname of the attached RBridge, so this solution
   does not consume extra nicknames.  The solution also enables Fine
   Grained Label aware endnodes.

Status of This Memo

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

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   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."

   This Internet-Draft will expire on June 18, 2015.

Perlman, et al.           Expires June 18, 2015                 [Page 1]
Internet-Draft            TRILL Smart Endnodes             December 2014

Copyright Notice

   Copyright (c) 2014 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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Smart-Hello Content . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Edge RBridge's Smart-Hello  . . . . . . . . . . . . . . .   4
     3.2.  Smart Endnode's Smart-Hello . . . . . . . . . . . . . . .   5
   4.  Frame Processing  . . . . . . . . . . . . . . . . . . . . . .   6
     4.1.  Frame Processing for Smart Endnode  . . . . . . . . . . .   6
     4.2.  Frame Processing for Edge RBridge . . . . . . . . . . . .   6
   5.  Multi-homing  . . . . . . . . . . . . . . . . . . . . . . . .   7
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   9.  Normative References  . . . . . . . . . . . . . . . . . . . .   8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   9

1.  Introduction

   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol [RFC6325] provides optimal pair-wise data frame forwarding
   without configuration, safe forwarding even during periods of
   temporary loops, and support for multipathing of both unicast and
   multicast traffic.  TRILL accomplishes this by using IS-IS [IS-IS]
   [RFC7176] link state routing and encapsulating traffic using a header
   that includes a hop count.  Devices that implement TRILL are called
   "RBridges" (Routing Bridges) or TRILL Switches.

   An RBridge that attaches to endnodes is called an "edge RBridge",
   whereas one that exclusively forwards encapsulated frames is known as
   a "transit RBridge".  An edge RBridge traditionally is the one that
   encapsulates a native Ethernet packet with a TRILL header, or that
   receives a TRILL-encapsulated packet and decapsulates the TRILL

Perlman, et al.           Expires June 18, 2015                 [Page 2]
Show full document text