IPv6 Stateless Prefix Management
draft-naveen-slaac-prefix-management-00

Document Type Active Internet-Draft (individual)
Last updated 2018-11-06
Stream (None)
Intended RFC status (None)
Formats plain text xml 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                             Naveen Kottapalli, Ed.
Internet-Draft                                             Benu Networks
Intended status: Informational                          November 6, 2018
Expires: May 10, 2019

                    IPv6 Stateless Prefix Management
                draft-naveen-slaac-prefix-management-00

Abstract

   The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) provides a
   provision for the hosts to request for a specific IPv6 address and
   manage the same, whereas the StateLess Address AutoConfiguration
   (SLAAC) doesn't have such a provision.  Also, unavailability of
   DHCPv6 across all OS platforms has limited the IPv6 nodes to not use
   features like soliciting a prefix of desired length and lifetime,
   renewing, releasing / declining a prefix, etc.  This document
   proposes IPv6ND extensions for enabling SLAAC devices to solicit
   prefix information as a hint PIO in RS and other methods like
   renewing or releasing or declining a prefix without introducing any
   new ICMPv6 message or option types.

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 May 10, 2019.

Copyright Notice

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

Naveen Kottapalli         Expires May 10, 2019                  [Page 1]
Internet-Draft           SLAAC Prefix Management           November 2018

   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
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  /64 Prefix  . . . . . . . . . . . . . . . . . . . . .   3
       2.1.2.  Non /64 Prefix  . . . . . . . . . . . . . . . . . . .   3
       2.1.3.  Requesting Node . . . . . . . . . . . . . . . . . . .   3
       2.1.4.  Delegating Node or Router . . . . . . . . . . . . . .   4
       2.1.5.  Requirements Language . . . . . . . . . . . . . . . .   4
   3.  Related works . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     4.1.  Host Soliciting a Prefix  . . . . . . . . . . . . . . . .   4
     4.2.  CPE or Downstream Router Soliciting a Prefix  . . . . . .   5
   5.  Soliciting Prefix . . . . . . . . . . . . . . . . . . . . . .   6
     5.1.  Requesting Node Specification . . . . . . . . . . . . . .   6
     5.2.  Delegating Router Specification . . . . . . . . . . . . .   8
   6.  Renewing Prefix . . . . . . . . . . . . . . . . . . . . . . .   9
     6.1.  Requesting Node Specification . . . . . . . . . . . . . .  10
     6.2.  Delegating Router Specification . . . . . . . . . . . . .  10
   7.  Releasing Prefix  . . . . . . . . . . . . . . . . . . . . . .  11
     7.1.  Requesting Node Specification . . . . . . . . . . . . . .  11
     7.2.  Delegating Router Specification . . . . . . . . . . . . .  11
   8.  Declining Prefix  . . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Requesting Node Specification . . . . . . . . . . . . . .  12
     8.2.  Delegating Router Specification . . . . . . . . . . . . .  12
   9.  Processing Router Advertisements  . . . . . . . . . . . . . .  12
   10. Unsolicited Router Advertisements . . . . . . . . . . . . . .  12
     10.1.  Requesting Node Specification  . . . . . . . . . . . . .  12
     10.2.  Delegating Router Specification  . . . . . . . . . . . .  12
   11. Backward Compatibility  . . . . . . . . . . . . . . . . . . .  13
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  13
   13. Security Considerations . . . . . . . . . . . . . . . . . . .  13
   14. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  13
Show full document text