Route Information Options in IPv6 Neighbor Discovery
draft-templin-6man-rio-redirect-02

Document Type Active Internet-Draft (individual)
Last updated 2017-04-06
Stream (None)
Intended RFC status (None)
Formats plain text pdf html 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)
Network Working Group                                    F. Templin, Ed.
Internet-Draft                              Boeing Research & Technology
Updates: rfc4191, rfc4861 (if approved)                      J. Woodyatt
Intended status: Standards Track                                  Google
Expires: October 8, 2017                                  April 06, 2017

          Route Information Options in IPv6 Neighbor Discovery
                 draft-templin-6man-rio-redirect-02.txt

Abstract

   The IPv6 Neighbor Discovery protocol provides a Redirect function
   allowing routers to inform recipients of a better next hop neighbor
   on the link toward the destination, and a Neighbor Solicitation (NS)
   function allowing nodes to solicit a Neighbor Advertisement (NA)
   response from the neighbor.  This document specifies backward-
   compatible extensions to Redirect, NS and NA messages to support the
   discovery of more-specific routes.

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 October 8, 2017.

Copyright Notice

   Copyright (c) 2017 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
   (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

Templin & Woodyatt       Expires October 8, 2017                [Page 1]
Internet-Draft              RIOs in Redirects                 April 2017

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Motivation  . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Route Information Options in IPv6 Neighbor Discovery Messages   4
     4.1.  Classical Redirection Scenario  . . . . . . . . . . . . .   4
     4.2.  RIO Redirection Scenario  . . . . . . . . . . . . . . . .   6
       4.2.1.  Router Specification  . . . . . . . . . . . . . . . .   6
       4.2.2.  Source Specification  . . . . . . . . . . . . . . . .   6
       4.2.3.  Target Specification  . . . . . . . . . . . . . . . .   7
       4.2.4.  Operation Without Redirects . . . . . . . . . . . . .   8
       4.2.5.  Multiple RIOs . . . . . . . . . . . . . . . . . . . .   8
       4.2.6.  Why NS/NA?  . . . . . . . . . . . . . . . . . . . . .   8
   5.  Implementation Status . . . . . . . . . . . . . . . . . . . .   9
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   9
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .   9
   8.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   9.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  10
     9.1.  Normative References  . . . . . . . . . . . . . . . . . .  10
     9.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Appendix A.  Link-layer Address Changes . . . . . . . . . . . . .  12
   Appendix B.  Interfaces with Multiple Link-Layer Addresses  . . .  12
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

   "Neighbor Discovery for IP version 6 (IPv6)" [RFC4861] (IPv6 ND)
   provides a Redirect function allowing routers to inform recipients of
   a better next hop neighbor on the link toward the destination, and a
   Neighbor Solicitation (NS) function allowing nodes to solicit a
   Neighbor Advertisement (NA) response from the neighbor.  Further
   guidance for processing Redirect messages is given in "First-Hop
   Router Selection by Hosts in a Multi-Prefix Network" [RFC8028].

   "Default Router Preferences and More-Specific Routes" [RFC4191]
   specifies a Route Information Option (RIO) that routers can include
Show full document text