draft-ietf-intarea-provisioning-domains-04.txt   draft-ietf-intarea-provisioning-domains-05.txt 
intarea P. Pfister intarea P. Pfister
Internet-Draft E. Vyncke, Ed. Internet-Draft E. Vyncke, Ed.
Intended status: Standards Track Cisco Intended status: Standards Track Cisco
Expires: September 9, 2019 T. Pauly Expires: December 20, 2019 T. Pauly
Apple Apple
D. Schinazi D. Schinazi
Google LLC Google LLC
W. Shao W. Shao
Cisco Cisco
March 8, 2019 June 18, 2019
Discovering Provisioning Domain Names and Data Discovering Provisioning Domain Names and Data
draft-ietf-intarea-provisioning-domains-04 draft-ietf-intarea-provisioning-domains-05
Abstract Abstract
An increasing number of hosts access the Internet via multiple An increasing number of hosts access the Internet via multiple
interfaces or, in IPv6 multi-homed networks, via multiple IPv6 prefix interfaces or, in IPv6 multi-homed networks, via multiple IPv6 prefix
configurations context. configurations context.
This document describes a way for hosts to identify such contexts, This document describes a way for hosts to identify such contexts,
called Provisioning Domains (PvDs), where Fully Qualified Domain called Provisioning Domains (PvDs), where Fully Qualified Domain
Names (FQDNs) act as PvD identifiers. Those identifiers are Names (FQDNs) act as PvD identifiers. Those identifiers are
skipping to change at page 2, line 4 skipping to change at page 2, line 4
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on September 9, 2019. This Internet-Draft will expire on December 20, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 27 skipping to change at page 2, line 27
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4
3. Provisioning Domain Identification using Router 3. Provisioning Domain Identification using Router
Advertisements . . . . . . . . . . . . . . . . . . . . . . . 4 Advertisements . . . . . . . . . . . . . . . . . . . . . . . 4
3.1. PvD ID Option for Router Advertisements . . . . . . . . . 4 3.1. PvD ID Option for Router Advertisements . . . . . . . . . 5
3.2. Router Behavior . . . . . . . . . . . . . . . . . . . . . 7 3.2. Router Behavior . . . . . . . . . . . . . . . . . . . . . 7
3.3. Non-PvD-aware Host Behavior . . . . . . . . . . . . . . . 8 3.3. Non-PvD-aware Host Behavior . . . . . . . . . . . . . . . 8
3.4. PvD-aware Host Behavior . . . . . . . . . . . . . . . . . 8 3.4. PvD-aware Host Behavior . . . . . . . . . . . . . . . . . 8
3.4.1. DHCPv6 configuration association . . . . . . . . . . 9 3.4.1. DHCPv6 configuration association . . . . . . . . . . 9
3.4.2. DHCPv4 configuration association . . . . . . . . . . 9 3.4.2. DHCPv4 configuration association . . . . . . . . . . 9
3.4.3. Connection Sharing by the Host . . . . . . . . . . . 9 3.4.3. Connection Sharing by the Host . . . . . . . . . . . 9
3.4.4. Usage of DNS Servers . . . . . . . . . . . . . . . . 10 3.4.4. Usage of DNS Servers . . . . . . . . . . . . . . . . 10
4. Provisioning Domain Additional Information . . . . . . . . . 11 4. Provisioning Domain Additional Information . . . . . . . . . 11
4.1. Retrieving the PvD Additional Information . . . . . . . . 11 4.1. Retrieving the PvD Additional Information . . . . . . . . 11
4.2. Operational Consideration to Providing the PvD Additional 4.2. Operational Consideration to Providing the PvD Additional
Information . . . . . . . . . . . . . . . . . . . . . . . 13 Information . . . . . . . . . . . . . . . . . . . . . . . 13
4.3. PvD Additional Information Format . . . . . . . . . . . . 13 4.3. PvD Additional Information Format . . . . . . . . . . . . 13
4.3.1. Private Extensions . . . . . . . . . . . . . . . . . 14 4.3.1. Example . . . . . . . . . . . . . . . . . . . . . . . 15
4.3.2. Example . . . . . . . . . . . . . . . . . . . . . . . 14
4.4. Detecting misconfiguration and misuse . . . . . . . . . . 15 4.4. Detecting misconfiguration and misuse . . . . . . . . . . 15
5. Operational Considerations . . . . . . . . . . . . . . . . . 15 5. Operational Considerations . . . . . . . . . . . . . . . . . 16
6. Security Considerations . . . . . . . . . . . . . . . . . . . 17 6. Security Considerations . . . . . . . . . . . . . . . . . . . 17
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 17 7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 18
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18
8.1. Additional Information PvD Keys Registry . . . . . . . . 18 8.1. Additional Information PvD Keys Registry . . . . . . . . 18
8.2. PvD Option Flags Registry . . . . . . . . . . . . . . . . 18 8.2. PvD Option Flags Registry . . . . . . . . . . . . . . . . 19
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 18 8.3. PvD JSON Media Type Registration . . . . . . . . . . . . 19
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 19 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 20
10.1. Normative references . . . . . . . . . . . . . . . . . . 19 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 20
10.2. Informative references . . . . . . . . . . . . . . . . . 20 10.1. Normative references . . . . . . . . . . . . . . . . . . 20
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 22 10.2. Informative references . . . . . . . . . . . . . . . . . 21
A.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 22 Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 23
A.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 22 A.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 23
A.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 23 A.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 23
A.4. WG Document version 00 . . . . . . . . . . . . . . . . . 23 A.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 24
A.5. WG Document version 01 . . . . . . . . . . . . . . . . . 24 A.4. WG Document version 00 . . . . . . . . . . . . . . . . . 24
A.6. WG Document version 02 . . . . . . . . . . . . . . . . . 24 A.5. WG Document version 01 . . . . . . . . . . . . . . . . . 25
A.7. WG Document version 04 . . . . . . . . . . . . . . . . . 25 A.6. WG Document version 02 . . . . . . . . . . . . . . . . . 25
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 25 A.7. WG Document version 04 . . . . . . . . . . . . . . . . . 26
A.7.1. WG Document version 05 . . . . . . . . . . . . . . . 26
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 26
1. Introduction 1. Introduction
It has become very common in modern networks for hosts to access the It has become very common in modern networks for hosts to access the
internet through different network interfaces, tunnels, or next-hop internet through different network interfaces, tunnels, or next-hop
routers. To describe the set of network configurations associated routers. For example, if Alice has a mobile phone provider and a
with each access method, the concept of Provisioning Domain (PvD) was broadband provider in her home, her devices and her applications
defined in [RFC7556]. should be capable of seamlessly transitioning from one to the other
and be able to use her Wi-Fi to access local resources or use the
more suitable link on a per-application base. This document provides
the basic information necessary to make this choice intelligently.
There are similar use cases for IPsec Virtual Private Networks that
are already considered Explicit PvDs in [RFC7556].
To describe the set of network configurations associated with each
access method, the concept of Provisioning Domain (PvD) was defined
in [RFC7556].
This document specifies a way to identify PvDs with Fully Qualified This document specifies a way to identify PvDs with Fully Qualified
Domain Names (FQDN), called PvD IDs. Those identifiers are Domain Names (FQDN), called PvD IDs. Those identifiers are
advertised in a new Router Advertisement (RA) [RFC4861] option called advertised in a new Router Advertisement (RA) [RFC4861] option called
the PvD ID Router Advertisement option which, when present, the PvD ID Router Advertisement option which, when present,
associates the PvD ID with all the information present in the Router associates the PvD ID with all the information present in the Router
Advertisement as well as any configuration object, such as addresses, Advertisement as well as any configuration object, such as addresses,
deriving from it. The PVD ID Router Advertisement option may also deriving from it. The PVD ID Router Advertisement option may also
contain a set of other RA options. Since such options are only contain a set of other RA options. Since such options are only
considered by hosts implementing this specification, network considered by hosts implementing this specification, network
operators may configure hosts that are 'PvD-aware' with PvDs that are operators may configure hosts that are 'PvD-aware' with PvDs that are
ignored by other hosts. ignored by other hosts.
Since PvD IDs are used to identify different ways to access the Since PvD IDs are used to identify different ways to access the
internet, multiple PvDs (with different PvD IDs) could be provisioned internet, multiple PvDs (with different PvD IDs) could be provisioned
on a single host interface. Similarly, the same PvD ID could be used on a single host interface. Similarly, the same PvD ID could be used
on different interfaces of a host in order to inform that those PvDs on different interfaces of a host in order to inform that those PvDs
ultimately provide identical services. ultimately provide identical services.
This document also introduces a way for hosts to retrieve additional This document also introduces a way for hosts to retrieve optional
information related to a specific PvD by means of an HTTP over TLS and additional information related to a specific PvD by means of an
query using an URI derived from the PvD ID. The retrieved JSON HTTP over TLS query using an URI derived from the PvD ID. The
object contains additional information that would typically be retrieved JSON object contains additional information that would
considered unfit, or too large, to be directly included in the Router typically be considered unfit, or too large, to be directly included
Advertisement, but might be considered useful to the applications, or in the Router Advertisement, but might be considered useful to the
even sometimes users, when choosing which PvD should be used. applications, or even sometimes users, when choosing which PvD should
be used.
2. Terminology 2. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
[RFC2119]. [RFC2119].
In addition, this document uses the following terminology: In addition, this document uses the following terminology:
skipping to change at page 6, line 15 skipping to change at page 6, line 26
PvD ID FQDN : The FQDN used as PvD ID encoded in DNS format, as PvD ID FQDN : The FQDN used as PvD ID encoded in DNS format, as
described in Section 3.1 of [RFC1035]. Domain names compression described in Section 3.1 of [RFC1035]. Domain names compression
described in Section 4.1.4 of [RFC1035] MUST NOT be used. described in Section 4.1.4 of [RFC1035] MUST NOT be used.
Padding : Zero or more padding octets to the next 8 octets Padding : Zero or more padding octets to the next 8 octets
boundary. It MUST be set to zero by the sender, and ignored by boundary. It MUST be set to zero by the sender, and ignored by
the receiver. the receiver.
RA message header : (16 octets) When the R-flag is set, a full RA message header : (16 octets) When the R-flag is set, a full
Router Advertisement message header as specified in [RFC4861]. Router Advertisement message header as specified in [RFC4861].
The 'Type', 'Code' and 'Checksum' fields (i.e. the first 32 bits), The sender MUST set the 'Type' to 134, the value for "Router
MUST be set to zero by the sender and ignored by the receiver. Advertisement", and set the 'Code' to 0. Receivers MUST ignore
The other fields are to be set and parsed as specified in both of these fields. The 'Checksum' MUST be set to 0 by the
[RFC4861] or any updating documents. sender; non-zero checksums MUST be ignored by the receiver. All
other fields are to be set and parsed as specified in [RFC4861] or
any updating documents.
Options : Zero or more RA options that would otherwise be valid as Options : Zero or more RA options that would otherwise be valid as
part of the Router Advertisement main body, but are instead part of the Router Advertisement main body, but are instead
included in the PvD Option such as to be ignored by hosts that are included in the PvD Option such as to be ignored by hosts that are
not 'PvD-aware'. not 'PvD-aware'.
Here is an example of a PvD option with example.org as the PvD ID Here is an example of a PvD option with example.org as the PvD ID
FQDN and including a RDNSS and prefix information options (it also FQDN and including a RDNSS and prefix information options (it also
have the sequence number 123, presence of additional information to have the sequence number 123, presence of additional information to
be fetched with a delay indicated as 5): be fetched with a delay indicated as 5):
skipping to change at page 9, line 46 skipping to change at page 9, line 46
point link, using the same datalink address. If no such PvD is point link, using the same datalink address. If no such PvD is
found, or whenever multiple different PvDs are found, the found, or whenever multiple different PvDs are found, the
configuration elements coming from DHCPv4 MUST be associated with the configuration elements coming from DHCPv4 MUST be associated with the
implicit PvD identified by the interface on which the DHCPv4 implicit PvD identified by the interface on which the DHCPv4
transaction happened. The case of multiple explicit PvD for an IPv4 transaction happened. The case of multiple explicit PvD for an IPv4
interface is undefined. interface is undefined.
3.4.3. Connection Sharing by the Host 3.4.3. Connection Sharing by the Host
The situation when a host shares connectivity from an upstream The situation when a host shares connectivity from an upstream
interface (e.g. cellular) to a downstream interface (e.g. WiFi) is interface (e.g. cellular) to a downstream interface (e.g. Wi-Fi) is
known as 'tethering'. Techniques such as ND-proxy [RFC4389], 64share known as 'tethering'. Techniques such as ND-proxy [RFC4389], 64share
[RFC7278] or prefix delegation (e.g. using DHCPv6-PD [RFC8415]) may [RFC7278] or prefix delegation (e.g. using DHCPv6-PD [RFC8415]) may
be used for that purpose. be used for that purpose.
Whenever the RAs received from the upstream interface contain a PVD Whenever the RAs received from the upstream interface contain a PVD
RA option, hosts that are sharing connectivity SHOULD include a PVD RA option, hosts that are sharing connectivity SHOULD include a PVD
Option within the RAs sent downstream with: Option within the RAs sent downstream with:
The same PVD-ID FQDN. The same PVD-ID FQDN.
skipping to change at page 11, line 29 skipping to change at page 11, line 29
Section 3.4. Section 3.4.
4.1. Retrieving the PvD Additional Information 4.1. Retrieving the PvD Additional Information
When the H-flag of the PvD Option is set, hosts MAY attempt to When the H-flag of the PvD Option is set, hosts MAY attempt to
retrieve the PvD Additional Information associated with a given PvD retrieve the PvD Additional Information associated with a given PvD
by performing an HTTP over TLS [RFC2818] GET query to https://<PvD- by performing an HTTP over TLS [RFC2818] GET query to https://<PvD-
ID>/.well-known/pvd [RFC5785]. Inversely, hosts MUST NOT do so ID>/.well-known/pvd [RFC5785]. Inversely, hosts MUST NOT do so
whenever the H-flag is not set. whenever the H-flag is not set.
HTTP requests and responses for PvD additional information use the
"application/pvd+json" media type (see Section 8). Clients SHOULD
include this media type as an Accept header in their GET requests,
and servers MUST mark this media type as their Content-Type header in
responses.
Note that the DNS name resolution of the PvD ID, the PKI checks as Note that the DNS name resolution of the PvD ID, the PKI checks as
well as the actual query MUST be performed using the considered PvD. well as the actual query MUST be performed using the considered PvD.
In other words, the name resolution, PKI checks, source address In other words, the name resolution, PKI checks, source address
selection, as well as the next-hop router selection MUST be performed selection, as well as the next-hop router selection MUST be performed
while using exclusively the set of configuration information attached while using exclusively the set of configuration information attached
with the PvD, as defined in Section 3.4. In some cases, it may with the PvD, as defined in Section 3.4. In some cases, it may
therefore be necessary to wait for an address to be available for use therefore be necessary to wait for an address to be available for use
(e.g., once the Duplicate Address Detection or DHCPv6 processes are (e.g., once the Duplicate Address Detection or DHCPv6 processes are
complete) before initiating the HTTP over TLS query. If the host has complete) before initiating the HTTP over TLS query. If the host has
a temporary address per [RFC4941] in this PvD, then hosts SHOULD use a temporary address per [RFC4941] in this PvD, then hosts SHOULD use
skipping to change at page 13, line 36 skipping to change at page 13, line 40
4.3. PvD Additional Information Format 4.3. PvD Additional Information Format
The PvD Additional Information is a JSON object. The PvD Additional Information is a JSON object.
The following table presents the mandatory keys which MUST be The following table presents the mandatory keys which MUST be
included in the object: included in the object:
+----------+-----------------+-------------+------------------------+ +----------+-----------------+-------------+------------------------+
| JSON key | Description | Type | Example | | JSON key | Description | Type | Example |
+----------+-----------------+-------------+------------------------+ +----------+-----------------+-------------+------------------------+
| name | Human-readable | UTF-8 | "Awesome Wifi" | | name | Human-readable | UTF-8 | "Awesome Wi-Fi" |
| | service name | string | | | | service name | string | |
| | | [RFC3629] | | | | | [RFC3629] | |
| expires | Date after | [RFC3339] | "2017-07-23T06:00:00Z" | | expires | Date after | [RFC3339] | "2017-07-23T06:00:00Z" |
| | which this | | | | | which this | | |
| | object is not | | | | | object is not | | |
| | valid | | | | | valid | | |
| prefixes | Array of IPv6 | Array of | ["2001:db8:1::/48", | | prefixes | Array of IPv6 | Array of | ["2001:db8:1::/48", |
| | prefixes valid | strings | "2001:db8:4::/48"] | | | prefixes valid | strings | "2001:db8:4::/48"] |
| | for this PVD | | | | | for this PVD | | |
+----------+-----------------+-------------+------------------------+ +----------+-----------------+-------------+------------------------+
skipping to change at page 14, line 14 skipping to change at page 14, line 18
and/or displayed in a rate-limited fashion. If the PIO of the and/or displayed in a rate-limited fashion. If the PIO of the
received RA is not covered by at least one of the "prefixes" key, the received RA is not covered by at least one of the "prefixes" key, the
retrieved object SHOULD be ignored. retrieved object SHOULD be ignored.
The following table presents some optional keys which MAY be included The following table presents some optional keys which MAY be included
in the object. in the object.
+---------------+-----------------+---------+-----------------------+ +---------------+-----------------+---------+-----------------------+
| JSON key | Description | Type | Example | | JSON key | Description | Type | Example |
+---------------+-----------------+---------+-----------------------+ +---------------+-----------------+---------+-----------------------+
| localizedName | Localized user- | UTF-8 | "Wifi Genial" | | localizedName | Localized user- | UTF-8 | "Wi-Fi Genial" |
| | visible service | string | | | | visible service | string | |
| | name, language | | | | | name, language | | |
| | can be selected | | | | | can be selected | | |
| | based on the | | | | | based on the | | |
| | HTTP Accept- | | | | | HTTP Accept- | | |
| | Language header | | | | | Language header | | |
| | in the request. | | | | | in the request. | | |
| dnsZones | DNS zones | array | ["example.com","sub.e | | dnsZones | DNS zones | array | ["example.com","sub.e |
| | searchable and | of DNS | xample.org"] | | | searchable and | of DNS | xample.org"] |
| | accessible | zones | | | | accessible | zones | |
skipping to change at page 14, line 38 skipping to change at page 14, line 42
| | provides | | | | | provides | | |
| | restricted | | | | | restricted | | |
| | access to a set | | | | | access to a set | | |
| | of services | | | | | of services | | |
+---------------+-----------------+---------+-----------------------+ +---------------+-----------------+---------+-----------------------+
It is worth noting that the JSON format allows for extensions. It is worth noting that the JSON format allows for extensions.
Whenever an unknown key is encountered, it MUST be ignored along with Whenever an unknown key is encountered, it MUST be ignored along with
its associated elements. its associated elements.
4.3.1. Private Extensions Private-use or experimental keys MAY be used in the JSON dictionary.
In order to avoid such keys colliding with IANA registry keys,
JSON keys starting with "x-" are reserved for private use and can be implementers or vendors defining private-use or experimental keys
utilized to provide information that is specific to vendor, user or MUST create sub-dictionaries, where the sub-dictionary is added into
enterprise. It is RECOMMENDED to use one of the patterns "x-FQDN- the top-level JSON dictionary with a key of the format "vendor-*"
KEY" or "x-PEN-KEY" where FQDN is a fully qualified domain name or where the "*" is replaced by the implementers or vendors
PEN is a private enterprise number [PEN] under control of the author denomination. Upon receiving such a sub-dictionary, host MUST ignore
of the extension to avoid collisions. this sub-dictionary if it is unknown. When the vendor or implementor
is part of an IANA URN namespace [URN], the URN namespace SHOULD be
used rather than the "vendor-*" format.
4.3.2. Example 4.3.1. Example
Here are two examples based on the keys defined in this section. The following examples show how the JSON keys defined in this
document can be used:
{ {
"name": "Foo Wireless", "name": "Foo Wireless",
"localizedName": "Foo-France Wifi", "localizedName": "Foo-France Wi-Fi",
"expires": "2017-07-23T06:00:00Z", "expires": "2017-07-23T06:00:00Z",
"prefixes" : ["2001:db8:1::/48", "2001:db8:4::/48"], "prefixes" : ["2001:db8:1::/48", "2001:db8:4::/48"],
} }
{ {
"name": "Bar 4G", "name": "Bar 4G",
"localizedName": "Bar US 4G", "localizedName": "Bar US 4G",
"expires": "2017-07-23T06:00:00Z", "expires": "2017-07-23T06:00:00Z",
"prefixes": ["2001:db8:1::/48", "2001:db8:4::/48"], "prefixes": ["2001:db8:1::/48", "2001:db8:4::/48"],
} }
{
"name": "Company Network",
"localizedName": "Company Network",
"expires": "2017-07-23T06:00:00Z",
"prefixes": ["2001:db8:1::/48", "2001:db8:4::/48"],
"vendor-foo": { "private-key": "private-value" },
}
4.4. Detecting misconfiguration and misuse 4.4. Detecting misconfiguration and misuse
When a host retrieves the PvD Additional Information, it MUST verify When a host retrieves the PvD Additional Information, it MUST verify
that the TLS server certificate is valid for the performed request that the TLS server certificate is valid for the performed request
(e.g., that the Subject Name is equal to the PvD ID expressed as an (e.g., that the Subject Name is equal to the PvD ID expressed as an
FQDN). This authentication creates a secure binding between the FQDN). This authentication creates a secure binding between the
information provided by the trusted Router Advertisement, and the information provided by the trusted Router Advertisement, and the
HTTPS server. However, this does not mean the Advertising Router and HTTPS server. However, this does not mean the Advertising Router and
the PvD server belong to the same entity. the PvD server belong to the same entity.
skipping to change at page 18, line 44 skipping to change at page 19, line 14
8.2. PvD Option Flags Registry 8.2. PvD Option Flags Registry
IANA is also asked to create and maintain a new registry entitled IANA is also asked to create and maintain a new registry entitled
"PvD Option Flags" reserving bit positions from 0 to 15 to be used in "PvD Option Flags" reserving bit positions from 0 to 15 to be used in
the PvD option bitmask. Bit position 0, 1 and 2 are reserved by this the PvD option bitmask. Bit position 0, 1 and 2 are reserved by this
document (as specified in Figure 1). Future assignments require document (as specified in Figure 1). Future assignments require
Standards Action RFC8126 [RFC8126], via a Standards Track RFC Standards Action RFC8126 [RFC8126], via a Standards Track RFC
document. document.
8.3. PvD JSON Media Type Registration
This document registers the media type for PvD JSON text,
"application/pvd+json".
Type Name: application
Subtype Name: pvd+json
Required parameters: None
Optional parameters: None
Encoding considerations: Encoding considerations are identical to
those specified for the "application/json" media type.
Security considerations: See Section 6.
Interoperability considerations: This document specifies format of
conforming messages and the interpretation thereof.
Published specification: This document
Applications that use this media type: This media type is intended to
be used by network advertising additional Provisioning Domain
information, and clients looking up such information.
Additional information: None
Person and email address to contact for further information: See
Authors' Addresses section
Intended usage: COMMON
Restrictions on usage: None
Author: IETF
Change controller: IETF
9. Acknowledgements 9. Acknowledgements
Many thanks to M. Stenberg and S. Barth for their earlier work: Many thanks to M. Stenberg and S. Barth for their earlier work:
[I-D.stenberg-mif-mpvd-dns], as well as to Basile Bruneau who was [I-D.stenberg-mif-mpvd-dns], as well as to Basile Bruneau who was
author of an early version of this document. author of an early version of this document.
Thanks also to Marcus Keane, Mikael Abrahamsson, Ray Bellis, Zhen Thanks also to Marcus Keane, Mikael Abrahamsson, Ray Bellis, Zhen
Cao, Tim Chow, Lorenzo Colitti, Michael Di Bartolomeo, Ian Farrer, Cao, Tim Chow, Lorenzo Colitti, Michael Di Bartolomeo, Ian Farrer,
Bob Hinden, Tatuya Jinmei, Erik Kline, Ted Lemon, Jen Lenkova, Phillip Hallam-Baker, Bob Hinden, Tatuya Jinmei, Erik Kline, Ted
Veronika McKillop, Mark Townsley and James Woodyatt for useful and Lemon, Jen Lenkova, Veronika McKillop, Mark Townsley and James
interesting discussions. Woodyatt for useful and interesting discussions and reviews.
Finally, special thanks to Thierry Danis and Wenqin Shao for their Finally, special thanks to Thierry Danis and Wenqin Shao for their
valuable inputs and implementation efforts ([github]), Tom Jones for valuable inputs and implementation efforts ([github]), Tom Jones for
his integration effort into the NEAT project and Rigil Salim for his his integration effort into the NEAT project and Rigil Salim for his
implementation work. implementation work.
10. References 10. References
10.1. Normative references 10.1. Normative references
skipping to change at page 20, line 29 skipping to change at page 21, line 38
[I-D.stenberg-mif-mpvd-dns] [I-D.stenberg-mif-mpvd-dns]
Stenberg, M. and S. Barth, "Multiple Provisioning Domains Stenberg, M. and S. Barth, "Multiple Provisioning Domains
using Domain Name System", draft-stenberg-mif-mpvd-dns-00 using Domain Name System", draft-stenberg-mif-mpvd-dns-00
(work in progress), October 2015. (work in progress), October 2015.
[IEEE8021X] [IEEE8021X]
IEEE, "IEEE Standards for Local and Metropolitan Area IEEE, "IEEE Standards for Local and Metropolitan Area
Networks: Port based Network Access Control, IEEE Std". Networks: Port based Network Access Control, IEEE Std".
[PEN] IANA, "Private Enterprise Numbers",
<https://www.iana.org/assignments/enterprise-numbers>.
[RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet: [RFC3339] Klyne, G. and C. Newman, "Date and Time on the Internet:
Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002, Timestamps", RFC 3339, DOI 10.17487/RFC3339, July 2002,
<https://www.rfc-editor.org/info/rfc3339>. <https://www.rfc-editor.org/info/rfc3339>.
[RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, [RFC3971] Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander,
"SEcure Neighbor Discovery (SEND)", RFC 3971, "SEcure Neighbor Discovery (SEND)", RFC 3971,
DOI 10.17487/RFC3971, March 2005, DOI 10.17487/RFC3971, March 2005,
<https://www.rfc-editor.org/info/rfc3971>. <https://www.rfc-editor.org/info/rfc3971>.
[RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and
skipping to change at page 22, line 16 skipping to change at page 23, line 21
"IPv6 Router Advertisement Options for DNS Configuration", "IPv6 Router Advertisement Options for DNS Configuration",
RFC 8106, DOI 10.17487/RFC8106, March 2017, RFC 8106, DOI 10.17487/RFC8106, March 2017,
<https://www.rfc-editor.org/info/rfc8106>. <https://www.rfc-editor.org/info/rfc8106>.
[RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A., [RFC8415] Mrugalski, T., Siodelski, M., Volz, B., Yourtchenko, A.,
Richardson, M., Jiang, S., Lemon, T., and T. Winters, Richardson, M., Jiang, S., Lemon, T., and T. Winters,
"Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)",
RFC 8415, DOI 10.17487/RFC8415, November 2018, RFC 8415, DOI 10.17487/RFC8415, November 2018,
<https://www.rfc-editor.org/info/rfc8415>. <https://www.rfc-editor.org/info/rfc8415>.
[URN] IANA, "URN Namespaces", <https://www.iana.org/assignments/
urn-namespaces/urn-namespaces.xhtml#urn-namespaces-1>.
Appendix A. Changelog Appendix A. Changelog
Note to RFC Editors: Remove this section before publication. Note to RFC Editors: Remove this section before publication.
A.1. Version 00 A.1. Version 00
Initial version of the draft. Edited by Basile Bruneau + Eric Vyncke Initial version of the draft. Edited by Basile Bruneau + Eric Vyncke
and based on Basile's work. and based on Basile's work.
A.2. Version 01 A.2. Version 01
skipping to change at page 25, line 24 skipping to change at page 26, line 30
A.7. WG Document version 04 A.7. WG Document version 04
Updated reference for DHCPv6-PD from RFC 3633 to RFC 8415. Updated reference for DHCPv6-PD from RFC 3633 to RFC 8415.
Enhanced IANA considerations to clarify review process and new Enhanced IANA considerations to clarify review process and new
registries. registries.
Added a section on considerations for handling DNS on a PvD-aware Added a section on considerations for handling DNS on a PvD-aware
host. host.
A.7.1. WG Document version 05
Fixed nits about IPSEC and WiFi
Added use case per Phillip Hallam-Baker
Clarified some sentences
Authors' Addresses Authors' Addresses
Pierre Pfister Pierre Pfister
Cisco Cisco
11 Rue Camille Desmoulins 11 Rue Camille Desmoulins
Issy-les-Moulineaux 92130 Issy-les-Moulineaux 92130
France France
Email: ppfister@cisco.com Email: ppfister@cisco.com
Eric Vyncke (editor) Eric Vyncke (editor)
Cisco Cisco
De Kleetlaan, 6 De Kleetlaan, 6
Diegem 1831 Diegem 1831
Belgium Belgium
Email: evyncke@cisco.com Email: evyncke@cisco.com
Tommy Pauly Tommy Pauly
Apple Apple
skipping to change at page 25, line 44 skipping to change at page 27, line 14
Eric Vyncke (editor) Eric Vyncke (editor)
Cisco Cisco
De Kleetlaan, 6 De Kleetlaan, 6
Diegem 1831 Diegem 1831
Belgium Belgium
Email: evyncke@cisco.com Email: evyncke@cisco.com
Tommy Pauly Tommy Pauly
Apple Apple
One Apple Park Way
Cupertino, California 95014
USA
Email: tpauly@apple.com Email: tpauly@apple.com
David Schinazi David Schinazi
Google LLC Google LLC
1600 Amphitheatre Parkway 1600 Amphitheatre Parkway
Mountain View, California 94043 Mountain View, California 94043
USA USA
Email: dschinazi.ietf@gmail.com Email: dschinazi.ietf@gmail.com
Wenqin Shao Wenqin Shao
Cisco Cisco
 End of changes. 29 change blocks. 
58 lines changed or deleted 139 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/