datatracker.ietf.org
Sign In
Version 4.51.p2, 2013-06-11
Report a bug

IPv6 RA Options for Multiple Interface Next Hop Routes
draft-sarikaya-mif-6man-ra-route-02

Active Internet-Draft (None)
Document Stream: No stream defined
Last updated: 2013-02-25
Intended RFC status: (None)
Other versions: plain text, pdf, html

Document shepherd:(None)
Shepherd writeup

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                        B. Sarikaya
Internet-Draft                                                Huawei USA
Intended status: Standards Track                       February 25, 2013
Expires: August 29, 2013

         IPv6 RA Options for Multiple Interface Next Hop Routes
                  draft-sarikaya-mif-6man-ra-route-02

Abstract

   This draft defines new Router Advertisement options for configuring
   next hop routes on the mobile or fixed nodes.  Using these options,
   an operator can easily configure nodes with multiple interfaces (or
   otherwise multi-homed) to enable them to select the routes to a
   destination.  Each option is defined together with definitions of
   host and router behaviors.

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 August 29, 2013.

Copyright Notice

   Copyright (c) 2013 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
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as

Sarikaya                 Expires August 29, 2013                [Page 1]
Internet-Draft               New RA Options                February 2013

   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . . 3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . 3
   3.  Default Route Configuration . . . . . . . . . . . . . . . . . . 4
   4.  Host Configuration  . . . . . . . . . . . . . . . . . . . . . . 4
   5.  Router Configuration  . . . . . . . . . . . . . . . . . . . . . 4
   6.  Route Prefix option . . . . . . . . . . . . . . . . . . . . . . 5
   7.  Next Hop Address option . . . . . . . . . . . . . . . . . . . . 5
   8.  Next Hop Address with Route Prefix option . . . . . . . . . . . 6
   9.  Security Considerations . . . . . . . . . . . . . . . . . . . . 6
   10. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 7
   11. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . . . 7
   12. References  . . . . . . . . . . . . . . . . . . . . . . . . . . 8
     12.1.  Normative References . . . . . . . . . . . . . . . . . . . 8
     12.2.  Informative References . . . . . . . . . . . . . . . . . . 8
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . . . 9

Sarikaya                 Expires August 29, 2013                [Page 2]
Internet-Draft               New RA Options                February 2013

1.  Introduction

   IPv6 Neighbor Discovery and IPv6 Stateless Address Autoconfiguration
   protocols can be used to configure fixed and mobile nodes with
   various parameters related to addressing and routing [RFC4861],
   [RFC4862], [RFC4191].  DNS Recursive Server Addresses and Domain Name
   Search Lists are additional parameters that can be configured using
   router advertisements [RFC6106].

   Router Advertisements can also be used to configure fixed and mobile
   nodes in multi-homed scenarios with route information and next hop
   address.  Different scenarios exist such as the node is
   simultaneously connected to multiple access network of e.g.  WiFi and
   3G. The node may also be connected to more than one gateway.  Such
   connectivity may be realized by means of dedicated physical or
   logical links that may also be shared with other users nodes such as
   in residential access networks.

2.  Terminology

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this