Discovering Provisioning Domain Names and Data
RFC 8801
Document | Type | RFC - Proposed Standard (July 2020; No errata) | |
---|---|---|---|
Authors | Pierre Pfister , Éric Vyncke , Tommy Pauly , David Schinazi , Wenqin Shao | ||
Last updated | 2020-07-29 | ||
Replaces | draft-bruneau-intarea-provisioning-domains | ||
Stream | IETF | ||
Formats | plain text html xml 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 | RFC 8801 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Yes | ||
Telechat date | |||
Responsible AD | Suresh Krishnan | ||
Send notices to | Erik Kline <ek@loon.com> | ||
IANA | IANA review state | Version Changed - Review Needed | |
IANA action state | RFC-Ed-Ack | ||
IANA expert review state | Expert Reviews OK |
Internet Engineering Task Force (IETF) P. Pfister Request for Comments: 8801 É. Vyncke Category: Standards Track Cisco ISSN: 2070-1721 T. Pauly Apple Inc. D. Schinazi Google LLC W. Shao Cisco July 2020 Discovering Provisioning Domain Names and Data Abstract Provisioning Domains (PvDs) are defined as consistent sets of network configuration information. PvDs 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 PvD Additional Information that can be retrieved using HTTP over TLS. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at https://www.rfc-editor.org/info/rfc8801. Copyright Notice Copyright (c) 2020 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 1.1. Specification of Requirements 2. Terminology 3. Provisioning Domain Identification Using Router Advertisements 3.1. PvD Option for Router Advertisements 3.2. Router Behavior 3.3. Non-PvD-Aware Host Behavior 3.4. PvD-Aware Host Behavior 3.4.1. DHCPv6 Configuration Association 3.4.2. DHCPv4 Configuration Association 3.4.3. Connection Sharing by the Host 3.4.4. Usage of DNS Servers 4. Provisioning Domain Additional Information 4.1. Retrieving the PvD Additional Information 4.2. Operational Consideration to Providing the PvD Additional Information 4.3. PvD Additional Information Format 4.3.1. Example 4.4. Detecting Misconfiguration and Misuse 5. Operational Considerations 5.1. Exposing Extra RA Options to PvD-Aware Hosts 5.2. Different RAs for PvD-Aware and Non-PvD-Aware Hosts 5.3. Enabling Multihoming for PvD-Aware Hosts 5.4. Providing Additional Information to PvD-Aware Hosts 6. Security Considerations 7. Privacy Considerations 8. IANA Considerations 8.1. Change to IPv6 Neighbor Discovery Option Formats Registry 8.2. New Entry in the Well-Known URIs Registry 8.3. New Additional Information PvD Keys Registry 8.4. New PvD Option Flags Registry 8.5. PvD JSON Media Type Registration 9. References 9.1. Normative References 9.2. Informative References Acknowledgments Authors' Addresses 1. Introduction Provisioning Domains (PvDs) are defined in [RFC7556] as consistent sets of network configuration information. This information includes properties that are traditionally associated with a single networking interface, such as source addresses, DNS configuration, proxy configuration, and gateway addresses. Clients that are aware of PvDs can take advantage of multiple network interfaces simultaneously. This enables using two PvDs in parallel for separate connections or for multi-path transports. While most PvDs today are discovered implicitly (such as by receiving information via Router Advertisements from a router on a network thatShow full document text