Discovering Provisioning Domain Names and Data
draft-ietf-intarea-provisioning-domains-05

The information below is for an old version of the document
Document Type Active Internet-Draft (intarea WG)
Last updated 2019-06-18 (latest revision 2019-03-08)
Replaces draft-bruneau-intarea-provisioning-domains
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Reviews
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
intarea                                                       P. Pfister
Internet-Draft                                            E. Vyncke, Ed.
Intended status: Standards Track                                   Cisco
Expires: December 20, 2019                                      T. Pauly
                                                                   Apple
                                                             D. Schinazi
                                                              Google LLC
                                                                 W. Shao
                                                                   Cisco
                                                           June 18, 2019

             Discovering Provisioning Domain Names and Data
               draft-ietf-intarea-provisioning-domains-05

Abstract

   An increasing number of hosts access the Internet via multiple
   interfaces or, in IPv6 multi-homed networks, via multiple IPv6 prefix
   configurations context.

   This document describes a way for hosts to identify such contexts,
   called Provisioning Domains (PvDs), where Fully Qualified Domain
   Names (FQDNs) act as PvD identifiers.  Those identifiers are
   advertised in a new Router Advertisement (RA) option and, when
   present, are associated with the set of information included within
   the RA.

   Based on this FQDN, hosts can retrieve additional information about
   their network access characteristics via an HTTP over TLS query.
   This allows applications to select which Provisioning Domains to use
   as well as to provide configuration parameters to the transport layer
   and above.

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."

Pfister, et al.         Expires December 20, 2019               [Page 1]
Internet-Draft            Provisioning Domains                 June 2019

   This Internet-Draft will expire on December 20, 2019.

Copyright Notice

   Copyright (c) 2019 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
   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 . . . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Provisioning Domain Identification using Router
       Advertisements  . . . . . . . . . . . . . . . . . . . . . . .   4
     3.1.  PvD ID Option for Router Advertisements . . . . . . . . .   5
     3.2.  Router Behavior . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  Non-PvD-aware Host Behavior . . . . . . . . . . . . . . .   8
     3.4.  PvD-aware Host Behavior . . . . . . . . . . . . . . . . .   8
       3.4.1.  DHCPv6 configuration association  . . . . . . . . . .   9
       3.4.2.  DHCPv4 configuration association  . . . . . . . . . .   9
       3.4.3.  Connection Sharing by the Host  . . . . . . . . . . .   9
       3.4.4.  Usage of DNS Servers  . . . . . . . . . . . . . . . .  10
   4.  Provisioning Domain Additional Information  . . . . . . . . .  11
     4.1.  Retrieving the PvD Additional Information . . . . . . . .  11
     4.2.  Operational Consideration to Providing the PvD Additional
           Information . . . . . . . . . . . . . . . . . . . . . . .  13
     4.3.  PvD Additional Information Format . . . . . . . . . . . .  13
       4.3.1.  Example . . . . . . . . . . . . . . . . . . . . . . .  15
     4.4.  Detecting misconfiguration and misuse . . . . . . . . . .  15
   5.  Operational Considerations  . . . . . . . . . . . . . . . . .  16
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  17
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  18
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
     8.1.  Additional Information PvD Keys Registry  . . . . . . . .  18
Show full document text