Neighbor Cache Entries on First-Hop Routers: Operational Considerations
draft-linkova-v6ops-nd-cache-init-01

Document Type Active Internet-Draft (v6ops WG)
Last updated 2019-07-25 (latest revision 2019-07-05)
Stream IETF
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream WG state Candidate for WG Adoption
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
v6ops                                                         J. Linkova
Internet-Draft                                                    Google
Intended status: Informational                              July 5, 2019
Expires: January 6, 2020

Neighbor Cache Entries on First-Hop Routers: Operational Considerations
                  draft-linkova-v6ops-nd-cache-init-01

Abstract

   Neighbor Discovery (RFC4861) is used by IPv6 nodes to determine the
   link-layer addresses of neighboring nodes as well as to discover and
   maintain reachability information.  This document discusses how the
   neighbor discovery state machine on a first-hop router is causing
   user-visible connectivity issues when a new (not being seen on the
   network before) IPv6 address is being used.

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 https://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 January 6, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Linkova                  Expires January 6, 2020                [Page 1]
Internet-DraNeighbor Cache Entries on First-Hop Routers: Oper  July 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
     1.2.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   4
   2.  Potential Solutions . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Do Nothing  . . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.1.  Pros  . . . . . . . . . . . . . . . . . . . . . . . .   5
       2.1.2.  Cons  . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Change to the Registration-Based Neighbor Discovery . . .   5
     2.3.  Hosts Explicitly Advertizing Their GUAs Using Existing ND
           Mechanisms  . . . . . . . . . . . . . . . . . . . . . . .   6
       2.3.1.  Host Sending Unsolicited NA . . . . . . . . . . . . .   6
         2.3.1.1.  Pros  . . . . . . . . . . . . . . . . . . . . . .   7
         2.3.1.2.  Cons  . . . . . . . . . . . . . . . . . . . . . .   7
       2.3.2.  Host Sending NS to the Router Address from Its GUA  .   7
         2.3.2.1.  Pros  . . . . . . . . . . . . . . . . . . . . . .   7
         2.3.2.2.  Cons  . . . . . . . . . . . . . . . . . . . . . .   7
       2.3.3.  Host Sending Router Solicitation from its GUA . . . .   8
         2.3.3.1.  Pros  . . . . . . . . . . . . . . . . . . . . . .   8
         2.3.3.2.  Cons  . . . . . . . . . . . . . . . . . . . . . .   8
     2.4.  Initiating Hosts2Routers Communication  . . . . . . . . .   8
       2.4.1.  Pros  . . . . . . . . . . . . . . . . . . . . . . . .   9
       2.4.2.  Cons  . . . . . . . . . . . . . . . . . . . . . . . .   9
     2.5.  Tweaking Probing Algorithms . . . . . . . . . . . . . . .   9
     2.6.  Routers Buffering More Packets  . . . . . . . . . . . . .   9
       2.6.1.  Pros  . . . . . . . . . . . . . . . . . . . . . . . .  10
       2.6.2.  Cons  . . . . . . . . . . . . . . . . . . . . . . . .  10
   3.  Recommendations . . . . . . . . . . . . . . . . . . . . . . .  10
     3.1.  Avoiding Disruption . . . . . . . . . . . . . . . . . . .  10
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  11
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  11
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  12
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  12
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .  12
     7.2.  Informative References  . . . . . . . . . . . . . . . . .  13
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  13

1.  Introduction

   The section 7.2.5 of [RFC4861] states: "When a valid Neighbor
Show full document text