TRILL: ARP/ND Optimization
draft-ietf-trill-arp-optimization-06

The information below is for an old version of the document
Document Type Active Internet-Draft (trill WG)
Last updated 2016-08-24 (latest revision 2016-04-22)
Replaces draft-yizhou-trill-arp-optimization, draft-trill-trill-arp-optimization
Stream IETF
Intended RFC status Proposed Standard
Formats pdf htmlized bibtex
Reviews
Stream WG state WG Document
Revised I-D Needed - Issue raised by IESG
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2016-03-17)
IESG IESG state AD is watching::Revised I-D Needed
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to (None)
IANA IANA review state IANA OK - No Actions Needed
TRILL Working Group                                                Y. Li
INTERNET-DRAFT                                               D. Eastlake
Intended Status: Standard Track                                L. Dunbar
                                                     Huawei Technologies
                                                              R. Perlman
                                                                     EMC
Expires: October 25, 2016                                 April 23, 2016

                       TRILL: ARP/ND Optimization
                  draft-ietf-trill-arp-optimization-06

Abstract

   This document describes mechanisms to optimize the ARP (Address
   Resolution Protocol) and ND (Neighbor Discovery) traffic in TRILL
   campus. Such optimization reduces packet flooding over a TRILL
   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) 2016 IETF Trust and the persons identified as the
   document authors. All rights reserved.

 

Yizhou, et al                                                   [Page 1]
INTERNET DRAFT         TRILL ARP/ND Optimization              April 2016

   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  . . . . . . . . . . . . . . . . . . . .  4
   3 Handling ARP/ND Messages . . . . . . . . . . . . . . . . . . . .  4
     3.1 Get Sender's IP/MAC Mapping Information for Non-zero IP  . .  5
     3.2 Determine How to Reply to ARP/ND . . . . . . . . . . . . . .  5
     3.3 Determine How to Handle the ARP/ND Response  . . . . . . . .  7
   4 Handling RARP (Reverse Address Resolution Protocol) Messages . .  7
   5 Security Considerations  . . . . . . . . . . . . . . . . . . . .  7
   6 IANA Considerations  . . . . . . . . . . . . . . . . . . . . . .  8
   7 Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . . .  8
   8 References . . . . . . . . . . . . . . . . . . . . . . . . . . .  8
     8.1 Normative References . . . . . . . . . . . . . . . . . . . .  8
     8.2 Informative References . . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . .  9

 

Yizhou, et al                                                   [Page 2]
INTERNET DRAFT         TRILL ARP/ND Optimization              April 2016

1 Introduction

   ARP [RFC826] and ND [RFC4861] are normally sent by broadcast and
   multicast respectively. To reduce the burden on a TRILL campus caused
   by these multi-destination messages, RBridges MAY implement an
   "optimized ARP/ND response", as specified herein, when the target's
   location is known by the ingress RBridge or can be obtained from a
   directory. This avoids ARP/ND query flooding.

1.1  Terminology

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

   The acronyms and terminology in [RFC6325] are used herein. Some of
   these are listed below for convenience  along with some additions:

   APPsub-TLV     Application sub-Type-Length-Values

   ARP            Address Resolution Protocol [RFC826]

   Campus         A TRILL network consisting of RBridges, links, and
   possibly bridges bounded by end stations and IP routers.
Show full document text