Proposals to discover Provisioning Domains
draft-bruneau-intarea-provisioning-domains-00

Document Type Active Internet-Draft (individual)
Last updated 2017-03-13
Replaces draft-bruneau-pvd
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)
intarea                                                       B. Bruneau
Internet-Draft                                       Ecole polytechnique
Intended status: Informational                                P. Pfister
Expires: September 14, 2017                                        Cisco
                                                             D. Schinazi
                                                                T. Pauly
                                                                   Apple
                                                          E. Vyncke, Ed.
                                                                   Cisco
                                                          March 13, 2017

               Proposals to discover Provisioning Domains
             draft-bruneau-intarea-provisioning-domains-00

Abstract

   This document describes one possible way for hosts to retrieve
   additional information about their Internet access configuration.
   The set of configuration items required to access the Internet is
   called a Provisioning Domain (PvD) and is identified by a Fully
   Qualified Domain Name.

   This document separates the way of getting the Provisioning Domain
   identifier, the way of getting the Provisioning Domain information
   and the potential information contained in the Provisioning Domain.

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 September 14, 2017.

Bruneau, et al.        Expires September 14, 2017               [Page 1]
Internet-Draft           Possibilities for PvDs               March 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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Requirements Language . . . . . . . . . . . . . . . . . .   4
   3.  Retrieving the PvD ID . . . . . . . . . . . . . . . . . . . .   4
     3.1.  Using One Router Advertisement per PvD  . . . . . . . . .   4
     3.2.  Rationale for not selecting other techniques  . . . . . .   5
       3.2.1.  Using DNS-SD  . . . . . . . . . . . . . . . . . . . .   5
       3.2.2.  Using Reverse DNS lookup  . . . . . . . . . . . . . .   5
     3.3.  IoT Considerations  . . . . . . . . . . . . . . . . . . .   6
     3.4.  Linking IPv4 Information to an IPv6 PvD . . . . . . . . .   6
   4.  Getting the full set of PvD information . . . . . . . . . . .   6
     4.1.  Using the PvD Bootstrap Information Option  . . . . . . .   7
     4.2.  Downloading a JSON file over HTTPS  . . . . . . . . . . .   7
       4.2.1.  Advantages  . . . . . . . . . . . . . . . . . . . . .   7
       4.2.2.  Disadvantages . . . . . . . . . . . . . . . . . . . .   8
     4.3.  Using DNS TXT ressource records (not selected)  . . . . .   8
       4.3.1.  Advantages  . . . . . . . . . . . . . . . . . . . . .   8
       4.3.2.  Disadvantages . . . . . . . . . . . . . . . . . . . .   8
       4.3.3.  Using DNS SRV ressource records . . . . . . . . . . .   8
   5.  PvD Information . . . . . . . . . . . . . . . . . . . . . . .   9
     5.1.  PvD Name  . . . . . . . . . . . . . . . . . . . . . . . .   9
     5.2.  Trust of the bootstrap PvD  . . . . . . . . . . . . . . .  10
     5.3.  Reachability  . . . . . . . . . . . . . . . . . . . . . .  11
     5.4.  DNS Configuration . . . . . . . . . . . . . . . . . . . .  12
     5.5.  Connectivity Characteristics  . . . . . . . . . . . . . .  13
     5.6.  Connection monetary cost  . . . . . . . . . . . . . . . .  14
Show full document text