TRILL: ARP/ND Optimization
draft-yizhou-trill-arp-optimization-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2014-10-27
Replaced by RFC 8302, RFC 8302
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
TRILL Working Group                                            Yizhou Li
INTERNET-DRAFT                                           Donald Eastlake
Intended Status: Standard Track                             Linda Dunbar
                                                     Huawei Technologies
                                                           Radia Perlman
                                                                     EMC
                                                          Igor Gashinsky
                                                                   Yahoo
Expires: April 30, 2015                                 October 27, 2014

                       TRILL: ARP/ND Optimization
                 draft-yizhou-trill-arp-optimization-00

Abstract

   This document describes mechanisms to optimize the ARP (Address
   Resolution Protocol) and ND (Neighbor Discovery) traffic in TRILL
   campus. Such optimization reduces the flooding over campus. 

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

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

Copyright and License Notice

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

Yizhou, et al                                                   [Page 1]
INTERNET DRAFT    Problems of Active-Active connection         July 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
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2 IP/MAC address mappings  . . . . . . . . . . . . . . . . . . . .  3
   3. Handling ARP/ND messages  . . . . . . . . . . . . . . . . . . .  4
     3.1 Get the mapping information of the sender's IP and MAC for
         non-zero IP. . . . . . . . . . . . . . . . . . . . . . . . .  4
     3.2 Determine how to reply the ARP/ND request. . . . . . . . . .  5
     3.3 Determine how to handle the ARP/ND response. . . . . . . . .  6
   4. Handling RARP (Reverse Address Resolution Protocol) messages  .  6
   5 Security Considerations  . . . . . . . . . . . . . . . . . . . .  6
   6  IANA Considerations . . . . . . . . . . . . . . . . . . . . . .  7
   6  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  7
     5.1  Normative References  . . . . . . . . . . . . . . . . . . .  7
     5.2  Informative References  . . . . . . . . . . . . . . . . . .  8
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  8

 

Yizhou, et al                                                   [Page 2]
INTERNET DRAFT    Problems of Active-Active connection         July 2013

1 Introduction

   IEEE 802.1 bridges forward an ARP/ND query as an ordinary
   broadcast/multicast frame to all links belonging to the same VLAN. 
   RBridges May implement an "optimized ARP/ND response" when the
   target's location is assumed to be known by the ingress RBridge.
   ARP/ND query flooding can be avoided.

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 RFC 2119 [RFC2119].

   The acronyms and terminology in [RFC6325] is used herein with the
   following additions:

   TRILL switch - an alternative term for an RBridge.

2 IP/MAC address mappings

   Traditionally an RBridge learns the MAC and nickname correspondence
   of a remote host as per [RFC6325] from TRILL data frame received. No
   IP address information is learned directly from the TRILL data frame.
Show full document text