TRILL Smart Endnodes
draft-perlman-trill-smart-endnodes-02

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2013-11-13 (latest revision 2013-10-20)
Replaced by draft-ietf-trill-smart-endnodes
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd None
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
TRILL WG                                                   Radia Perlman
Internet-Draft                                                Intel Labs
Intended status: Standards Track                              Fangwei Hu
Expires: April 4, 2014                                   ZTE Corporation
                                                     Donald Eastlake 3rd
                                                       Huawei technology
                                                Kesava Vijaya Krupakaran
                                                                    Dell
                                                               Ting Liao
                                                         ZTE Corporation
                                                                Oct 2013

                          TRILL Smart Endnodes
               draft-perlman-trill-smart-endnodes-02.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.

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 April 4, 2014.

Copyright Notice

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

Perlman, et al.           Expires April 4, 2014                 [Page 1]
Internet-Draft            TRILL Smart Endnodes                  Oct 2013

   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
   2.  TRILL-Hello Content . . . . . . . . . . . . . . . . . . . . . . 4
     2.1.  Edge RBridge's TRILL-Hello  . . . . . . . . . . . . . . . . 4
     2.2.  Smart Endnode's TRILL-Hello . . . . . . . . . . . . . . . . 4
   3.  Frame Processing  . . . . . . . . . . . . . . . . . . . . . . . 5
     3.1.  Frame Processing for Smart Endnode  . . . . . . . . . . . . 5
     3.2.  Frame Processing for Edge RBridge . . . . . . . . . . . . . 6
   4.  Multi-homing  . . . . . . . . . . . . . . . . . . . . . . . . . 7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . . . 7
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 8
   7.  IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 8
   8.  Normative References  . . . . . . . . . . . . . . . . . . . . . 8
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . . . 9

Perlman, et al.           Expires April 4, 2014                 [Page 2]
Internet-Draft            TRILL Smart Endnodes                  Oct 2013

1.  Introduction

   The IETF TRILL (Transparent Interconnection of Lots of Links)
   protocol implemented by devices called RBridges (Routing Bridges,
   [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([RFC1195])
   ([RFC6165]) ([I-D.ietf-isis-rfc6326bis])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
Show full document text