Requirements for a Zero-Configuration IPv6 CPE
draft-baker-v6ops-cpe-autoconfigure-00

Document Type Active Internet-Draft (individual)
Last updated 2017-06-17
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)
IPv6 Operations                                                 F. Baker
Internet-Draft                                             June 17, 2017
Intended status: Best Current Practice
Expires: December 19, 2017

             Requirements for a Zero-Configuration IPv6 CPE
                 draft-baker-v6ops-cpe-autoconfigure-00

Abstract

   This note is a breif exploration of what is required for a CPE to be
   auto-configurable from the perspective on an ISP or other upstream
   network.  It assumes that the CPE may also be IPv4-capable (probably
   using NAPT), but that the requirements for that are well understood
   and need no further specification.

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 December 19, 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
   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.

Baker                   Expires December 19, 2017               [Page 1]
Internet-Draft                                                 June 2017

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirements Language . . . . . . . . . . . . . . . . . .   2
   2.  Operational Requirements  . . . . . . . . . . . . . . . . . .   2
   3.  Expected Behavior . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Prefix Delegation . . . . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .   4
   8.  Human Rights Considerations . . . . . . . . . . . . . . . . .   5
   9.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     10.1.  Normative References . . . . . . . . . . . . . . . . . .   5
     10.2.  Informative References . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   6
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   We observe that, in today's offerings, "IPv6-capable" has many
   different meanings.  These often require specific configuration and
   are non-interoperable.

   The objective is to enable a customer to purchase a CPE router from a
   mass market store, or for an ISP to purchase CPE Routers for its
   managed service offering, that implement IPv6 [RFC2460] and can be
   attached to any residential/SOHO network and any ISP or other
   upstream network "as is out of the box", and work correctly.

1.1.  Requirements Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
   document are to be interpreted as described in [RFC2119].

2.  Operational Requirements

   The goal stated in Section 1 requires that downstream, which is to
   say within the home or SOHO , the CPE must presume that there may
   exist systems that will autoconfigure [RFC4862] themselves using
   information in a Router Advertisement [RFC4861], and that there may
   exist systems that require address assignment using DHCPv6 [RFC3315].
   It may offer a DNS service using a provider such as OpenDNS, Google
   Public DNS, Amazon Route 53, or some other such service, or relay the
   address of an ISP-provided DNS server.

Baker                   Expires December 19, 2017               [Page 2]
Internet-Draft                                                 June 2017

   Similarly, the stated goal requires that upstream, the CPE must
   presume that it will be required to solicit and observe a Router
   Advertisement [RFC4861], and

   o  learn an upstream DHCPv6 server address,
Show full document text