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

Document Type Active Internet-Draft (trill WG)
Last updated 2017-01-13 (latest revision 2016-10-21)
Replaces draft-yizhou-trill-arp-optimization, draft-trill-trill-arp-optimization
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Consensus: Waiting for Write-Up
Revised I-D Needed - Issue raised by WG
Document shepherd Susan Hares
Shepherd write-up Show (last changed 2017-02-05)
IESG IESG state AD is watching
Consensus Boilerplate Yes
Telechat date
Responsible AD Alia Atlas
Send notices to (None)
IANA IANA review state Version Changed - Review Needed
IANA action state None
TRILL Working Group                                                Y. Li
INTERNET-DRAFT                                               D. Eastlake
Intended Status: Standard Track                                L. Dunbar
                                                     Huawei Technologies
                                                              R. Perlman
                                                                     EMC
                                                                M. Umair
                                                              IPinfusion
Expires: April 24, 2017                                 October 21, 2016

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

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
 

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

   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 . . . . . . . . . . . . . . . . . . . . . . . . . .  3
     1.1  Terminology . . . . . . . . . . . . . . . . . . . . . . . .  3
   2 ARP/ND Optimization Requirement and Solution . . . . . . . . . .  4
   3 IP/MAC Address Mappings  . . . . . . . . . . . . . . . . . . . .  5
   4 Handling ARP/ND Messages . . . . . . . . . . . . . . . . . . . .  5
     4.1 Get Sender's IP/MAC Mapping Information for Non-zero IP  . .  6
     4.2 Determine How to Reply to ARP/ND . . . . . . . . . . . . . .  6
     4.3 Determine How to Handle the ARP/ND Response  . . . . . . . .  8
   5 Handling RARP (Reverse Address Resolution Protocol) Messages . .  8
   6 Handling of DHCP messages  . . . . . . . . . . . . . . . . . . .  9
   7 Handling of Duplicate IP Addresses . . . . . . . . . . . . . . .  9
   8 ARP/ND Cache Liveness and MAC Mobility . . . . . . . . . . . . . 10
   9 Security Considerations  . . . . . . . . . . . . . . . . . . . . 10
   10 IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 11
   11 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . 11
   12 References  . . . . . . . . . . . . . . . . . . . . . . . . . . 11
     12.1 Normative References  . . . . . . . . . . . . . . . . . . . 11
     12.2 Informative References  . . . . . . . . . . . . . . . . . . 12
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12

 

Yizhou, et al                                                   [Page 2]
INTERNET DRAFT         TRILL ARP/ND Optimization            October 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 and answer flooding.

1.1  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Show full document text