Discovering Provisioning Domain Names and Data
draft-ietf-intarea-provisioning-domains-08
|
| Document |
Type |
|
Active Internet-Draft (intarea WG)
|
|
Last updated |
|
2019-10-09
(latest revision 2019-10-08)
|
|
Replaces |
|
draft-bruneau-intarea-provisioning-domains
|
|
Stream |
|
IETF
|
|
Intended RFC status |
|
Proposed Standard
|
|
Formats |
|
plain text
pdf
htmlized
bibtex
|
|
Reviews |
|
|
| Stream |
WG state
|
|
Submitted to IESG for Publication
|
|
Document shepherd |
|
Erik Kline
|
|
Shepherd write-up |
|
Show
(last changed 2019-10-06)
|
| IESG |
IESG state |
|
AD Evaluation
|
|
Consensus Boilerplate |
|
Yes
|
|
Telechat date |
|
|
|
Responsible AD |
|
Suresh Krishnan
|
|
Send notices to |
|
Erik Kline <ek@loon.com>
|
Network Working Group P. Pfister
Internet-Draft E. Vyncke
Intended status: Standards Track Cisco
Expires: April 10, 2020 T. Pauly
Apple Inc.
D. Schinazi
Google LLC
W. Shao
Cisco
October 08, 2019
Discovering Provisioning Domain Names and Data
draft-ietf-intarea-provisioning-domains-08
Abstract
Provisioning Domains (PvDs) are defined as consistent sets of network
configuration information. This allows hosts to manage connections
to multiple networks and interfaces simultaneously, such as when a
home router provides connectivity through both a broadband and
cellular network provider.
This document defines a mechanism for explicitly identifying PvDs
through a Router Advertisement (RA) option. This RA option announces
a PvD identifier, which hosts can compare to differentiate between
PvDs. The option can directly carry some information about a PvD and
can optionally point to additional PvD information that can be
retrieved using HTTP over TLS.
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 April 10, 2020.
Pfister, et al. Expires April 10, 2020 [Page 1]
Internet-Draft Provisioning Domains October 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
1.1. Specification of Requirements . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Provisioning Domain Identification using Router
Advertisements . . . . . . . . . . . . . . . . . . . . . . . 5
3.1. PvD ID Option for Router Advertisements . . . . . . . . . 5
3.2. Router Behavior . . . . . . . . . . . . . . . . . . . . . 8
3.3. Non-PvD-aware Host Behavior . . . . . . . . . . . . . . . 9
3.4. PvD-aware Host Behavior . . . . . . . . . . . . . . . . . 9
3.4.1. DHCPv6 configuration association . . . . . . . . . . 10
3.4.2. DHCPv4 configuration association . . . . . . . . . . 10
3.4.3. Connection Sharing by the Host . . . . . . . . . . . 11
3.4.4. Usage of DNS Servers . . . . . . . . . . . . . . . . 12
4. Provisioning Domain Additional Information . . . . . . . . . 12
4.1. Retrieving the PvD Additional Information . . . . . . . . 13
4.2. Operational Consideration to Providing the PvD Additional
Information . . . . . . . . . . . . . . . . . . . . . . . 15
4.3. PvD Additional Information Format . . . . . . . . . . . . 15
4.3.1. Example . . . . . . . . . . . . . . . . . . . . . . . 17
4.4. Detecting misconfiguration and misuse . . . . . . . . . . 17
5. Operational Considerations . . . . . . . . . . . . . . . . . 18
5.1. Exposing Extra RA Options to PvD-Aware Hosts . . . . . . 18
5.2. Different RAs for PvD-Aware and Non-PvD-Aware Hosts . . . 18
5.3. Enabling Multi-homing for PvD-Aware Hosts . . . . . . . . 20
6. Security Considerations . . . . . . . . . . . . . . . . . . . 21
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 21
Show full document text