draft-ietf-intarea-provisioning-domains-01.txt   draft-ietf-intarea-provisioning-domains-02.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: August 13, 2018 T. Pauly Expires: December 6, 2018 T. Pauly
D. Schinazi D. Schinazi
Apple Apple
February 9, 2018 W. Shao
Telecom-ParisTech
June 4, 2018
Discovering Provisioning Domain Names and Data Discovering Provisioning Domain Names and Data
draft-ietf-intarea-provisioning-domains-01 draft-ietf-intarea-provisioning-domains-02
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. configurations context.
This document describes a way for hosts to identify such means, This document describes a way for hosts to identify such contexts,
called Provisioning Domains (PvDs), with Fully Qualified Domain Names called Provisioning Domains (PvDs), where Fully Qualified Domain
(FQDN). Those identifiers are advertised in a new Router Names (FQDNs) act as PvD identifiers. Those identifiers are
Advertisement (RA) option and, when present, are associated with the advertised in a new Router Advertisement (RA) option and, when
set of information included within the RA. present, are associated with the set of information included within
the RA.
Based on this FQDN, hosts can retrieve additional information about Based on this FQDN, hosts can retrieve additional information about
their network access characteristics via an HTTP over TLS query. their network access characteristics via an HTTP over TLS query.
This allows applications to select which Provisioning Domains to use This allows applications to select which Provisioning Domains to use
as well as to provide configuration parameters to the transport layer as well as to provide configuration parameters to the transport layer
and above. and above.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
skipping to change at page 1, line 46 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 December 6, 2018.
This Internet-Draft will expire on August 13, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2018 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 28 skipping to change at page 2, line 29
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 . . . . . . . . . . . . . . . . . . . . . . . . . 3 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 3
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 . . . . . . . . . 4
3.2. Router Behavior . . . . . . . . . . . . . . . . . . . . . 7 3.2. Router Behavior . . . . . . . . . . . . . . . . . . . . . 7
3.3. Host Behavior . . . . . . . . . . . . . . . . . . . . . . 7 3.3. Non-PvD-aware Host Behavior . . . . . . . . . . . . . . . 8
3.3.1. DHCPv6 configuration association . . . . . . . . . . 8 3.4. PvD-aware Host Behavior . . . . . . . . . . . . . . . . . 8
3.3.2. DHCPv4 configuration association . . . . . . . . . . 8 3.4.1. DHCPv6 configuration association . . . . . . . . . . 9
3.3.3. Interconnection Sharing by the Host . . . . . . . . . 9 3.4.2. DHCPv4 configuration association . . . . . . . . . . 9
4. Provisioning Domain Additional Information . . . . . . . . . 9 3.4.3. Connection Sharing by the Host . . . . . . . . . . . 9
4.1. Retrieving the PvD Additional Information . . . . . . . . 9 4. Provisioning Domain Additional Information . . . . . . . . . 10
4.1. Retrieving the PvD Additional Information . . . . . . . . 10
4.2. Operational Consideration to Providing the PvD Additional 4.2. Operational Consideration to Providing the PvD Additional
Information . . . . . . . . . . . . . . . . . . . . . . . 10 Information . . . . . . . . . . . . . . . . . . . . . . . 12
4.3. PvD Additional Information Format . . . . . . . . . . . . 11 4.3. PvD Additional Information Format . . . . . . . . . . . . 12
4.3.1. Private Extensions . . . . . . . . . . . . . . . . . 12 4.3.1. Private Extensions . . . . . . . . . . . . . . . . . 13
4.3.2. Example . . . . . . . . . . . . . . . . . . . . . . . 12 4.3.2. Example . . . . . . . . . . . . . . . . . . . . . . . 13
4.4. Detecting misconfiguration and misuse . . . . . . . . . . 13 4.4. Detecting misconfiguration and misuse . . . . . . . . . . 14
5. Operation Considerations . . . . . . . . . . . . . . . . . . 13 5. Operational Considerations . . . . . . . . . . . . . . . . . 14
6. Security Considerations . . . . . . . . . . . . . . . . . . . 15 6. Security Considerations . . . . . . . . . . . . . . . . . . . 16
7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 15 7. Privacy Considerations . . . . . . . . . . . . . . . . . . . 16
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 16 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 17
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 16 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 17
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 16 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 18
10.1. Normative references . . . . . . . . . . . . . . . . . . 16 10.1. Normative references . . . . . . . . . . . . . . . . . . 18
10.2. Informative references . . . . . . . . . . . . . . . . . 17 10.2. Informative references . . . . . . . . . . . . . . . . . 19
Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 19 Appendix A. Changelog . . . . . . . . . . . . . . . . . . . . . 20
A.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 19 A.1. Version 00 . . . . . . . . . . . . . . . . . . . . . . . 20
A.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 19 A.2. Version 01 . . . . . . . . . . . . . . . . . . . . . . . 20
A.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 20 A.3. Version 02 . . . . . . . . . . . . . . . . . . . . . . . 21
A.4. WG Document version 00 . . . . . . . . . . . . . . . . . 20 A.4. WG Document version 00 . . . . . . . . . . . . . . . . . 22
A.5. WG Document version 01 . . . . . . . . . . . . . . . . . 21 A.5. WG Document version 01 . . . . . . . . . . . . . . . . . 22
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 21 A.6. WG Document version 02 . . . . . . . . . . . . . . . . . 23
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 23
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. To describe the set of network configurations associated
with each access method, the concept of Provisioning Domain (PvD) was with each access method, the concept of Provisioning Domain (PvD) was
defined in [RFC7556]. 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
skipping to change at page 3, line 39 skipping to change at page 3, line 43
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 additional
information related to a specific PvD by means of an HTTP over TLS information related to a specific PvD by means of an HTTP over TLS
query using an URI derived from the PvD ID. The retrieved JSON query using an URI derived from the PvD ID. The retrieved JSON
object contains additional information that would typically be object contains additional information that would typically be
considered unfit, or too large, to be directly included in the Router considered unfit, or too large, to be directly included in the Router
Advertisement, but might be considered useful to the applications, or Advertisement, but might be considered useful to the applications, or
even sometimes users, when choosing which PvD and transport should be even sometimes users, when choosing which PvD should be used.
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 4, line 16 skipping to change at page 4, line 18
information; for more information, see [RFC7556]. information; for more information, see [RFC7556].
PvD ID: A Fully Qualified Domain Name (FQDN) used to identify a PvD ID: A Fully Qualified Domain Name (FQDN) used to identify a
PvD. PvD.
Explicit PvD: A PvD uniquely identified with a PvD ID. For more Explicit PvD: A PvD uniquely identified with a PvD ID. For more
information, see [RFC7556]. information, see [RFC7556].
Implicit PvD: A PvD that, in the absence of a PvD ID, is identified Implicit PvD: A PvD that, in the absence of a PvD ID, is identified
by the host interface to which it is attached and the address of by the host interface to which it is attached and the address of
the advertising router. the advertising router. See also [RFC7556].
PvD-aware host A host that supports the association of network
configuration information into PvDs and the use of these PvDs.
Also named PvD-aware node in [RFC7556].
3. Provisioning Domain Identification using Router Advertisements 3. Provisioning Domain Identification using Router Advertisements
Explicit PvDs are identified by a PvD ID. The PvD ID is a Fully Explicit PvDs are identified by a PvD ID. The PvD ID is a Fully
Qualified Domain Name (FQDN) which MUST belong to the network Qualified Domain Name (FQDN) which MUST belong to the network
operator in order to avoid naming collisions. The same PvD ID MAY be operator in order to avoid naming collisions. The same PvD ID MAY be
used in several access networks when they ultimately provide used in several access networks when they ultimately provide
identical services (e.g., in all home networks subscribed to the same identical services (e.g., in all home networks subscribed to the same
service). service); else, the PvD ID MUST be different to follow section 2.4 of
[RFC7556].
3.1. PvD ID Option for Router Advertisements 3.1. PvD ID Option for Router Advertisements
This document introduces a Router Advertisement (RA) option called This document introduces a Router Advertisement (RA) option called
PvD ID Router Advertisement option. It is used to convey the FQDN PvD option. It is used to convey the FQDN identifying a given PvD
identifying a given PvD (see Figure 1), bind the PvD ID with (see Figure 1), bind the PvD ID with configuration information
configuration information received over DHCPv4 (see Section 3.3.2), received over DHCPv4 (see Section 3.4.2), enable the use of HTTP over
enable the use of HTTP over TLS to retrieve the PvD Additional TLS to retrieve the PvD Additional Information JSON object (see
Information JSON object (see Section 4), as well as contain any other Section 4), as well as contain any other RA options which would
RA options which would otherwise be valid in the RA. otherwise be valid in the RA.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length |H|L|A| Reserved | | Type | Length |H|L|R| Reserved | Delay |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sequence Number | ... | Sequence Number | ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ...
... PvD ID FQDN ... ... PvD ID FQDN ...
... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
... | Padding | ... | Padding |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... | ...
... Router Advertisement message header ... ... Router Advertisement message header ...
... (Only present when A-flag is set) ... ... (Only present when R-flag is set) ...
... | ... |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Options ... | Options ...
+-+-+-+-+-+-+-+-+-+-+-+- +-+-+-+-+-+-+-+-+-+-+-+-
Figure 1: PvD ID Router Advertisements Option format Figure 1: PvD ID Router Advertisements Option format
Type : (8 bits) To be defined by IANA. Current Type : (8 bits) Set to 21.
experimentation uses the value of 254.
Length : (8 bits) The length of the option in units of 8 Length : (8 bits) The length of the option in units of 8
octets, including the Type and Length fields, the Router octets, including the Type and Length fields, the Router
Advertisement message header, if any, as well as the RA options Advertisement message header, if any, as well as the RA options
that are included within the PvD ID Option. that are included within the PvD Option.
H-flag : (1 bit) 'HTTP' flag stating whether some PvD H-flag : (1 bit) 'HTTP' flag stating whether some PvD
Additional Information is made available through HTTP over TLS, as Additional Information is made available through HTTP over TLS, as
described in Section 4. described in Section 4.
L-flag : (1 bit) 'Legacy' flag stating whether the router is L-flag : (1 bit) 'Legacy' flag stating whether the router is
also providing IPv4 information using DHCPv4 (see Section 3.3.2). also providing IPv4 information using DHCPv4 (see Section 3.4.2).
A-flag : (1 bit) 'Advertisement' flag stating whether the PvD R-flag : (1 bit) 'Router Advertisement' flag stating whether
ID Option is followed (right after padding to the next 64 bits the PvD Option is followed (right after padding to the next 64
boundary) by a Router Advertisement message header (See section bits boundary) by a Router Advertisement message header (See
4.2 of target="RFC4861"/>). section 4.2 of [RFC4861]).
Delay : (4 bits) Unsigned integer used to delay HTTP GET
queries from hosts by a randomized backoff (see Section 4.1).
Reserved : (13 bits) Reserved for later use. It MUST be set to Reserved : (13 bits) Reserved for later use. It MUST be set to
zero by the sender and ignored by the receiver. zero by the sender and ignored by the receiver.
Sequence Number: (16 bits) Sequence number for the PvD Additional Sequence Number: (16 bits) Sequence number for the PvD Additional
Information, as described in Section 4. Information, as described in Section 4.
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 A-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 'Type', 'Code' and 'Checksum' fields (i.e. the first 32 bits),
MUST be set to zero by the sender and ignored by the receiver. MUST be set to zero by the sender and ignored by the receiver.
The other fields are to be set and parsed as specified in The other fields are to be set and parsed as specified in
[RFC4861] or any updating documents. [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 ID Option such as to be ignored by hosts that included in the PvD Option such as to be ignored by hosts that are
are not 'PvD-aware'. not 'PvD-aware'.
Here is an example of a PvD ID 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: FQDN and including a RDNSS and prefix information options (it also
have the sequence number 123, presence of additional information to
be fetched with a delay indicated as 5):
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+---------------+-----------------------------------------------+ +---------------+-----------------------------------------------+
| Type: 254 | Length: 12 |0|0|0| Reserved | | Type: 21 | Length: 12 |1|0|0| Reserved |Delay:5|
+---------------+-------------------------------+---------------+ +---------------+-------------------------------+---------------+
| Sequence Number | 7 | e | | Seq number: 123 | 7 | e |
+---------------+-----------------------------------------------+ +---------------+-----------------------------------------------+
| m | a | m | p | | x | a | m | p |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| l | e | 3 | o | | l | e | 3 | o |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| r | g | 0 | 0 (padding) | | r | g | 0 | 0 (padding) |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| 0 (padding) | 0 (padding) | 0 (padding) | 0 (padding) | | 0 (padding) | 0 (padding) | 0 (padding) | 0 (padding) |
+---------------+---------------+---------------+---------------+ +---------------+---------------+---------------+---------------+
| RDNSS option (RFC 6106) length: 5 ... | RDNSS option (RFC 6106) length: 5 ...
... ... ... ...
... | ... |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
| Prefix Information Option (RFC 4861) length: 4 ... | Prefix Information Option (RFC 4861) length: 4 ...
... | ... |
... | ... |
+---------------------------------------------------------------+ +---------------------------------------------------------------+
Figure 2
3.2. Router Behavior 3.2. Router Behavior
A router MAY send RAs containing at most one PvD ID RA option, but A router MAY send RAs containing one PvD option, but MUST NOT include
MUST NOT include more than one PvD ID RA option in each RA. In more than one PvD option in each RA. In particular, the PvD option
particular, the PvD ID RA option MUST NOT contain further PvD ID RA MUST NOT contain further PvD options.
options.
The PvD ID Option MAY contain zero, one, or more RA options which The PvD Option MAY contain zero, one, or more RA options which would
would otherwise be valid as part of the same RA. Such options are otherwise be valid as part of the same RA. Such options are
processed by PvD-aware hosts, while ignored by others. processed by PvD-aware hosts, while ignored by others.
In order to provide multiple different PvDs, a router MUST send In order to provide multiple different PvDs, a router MUST send
multiple RAs. Different explicit PvDs MAY be advertised with RAs multiple RAs. Different explicit PvDs MAY be advertised with RAs
using the same IPv6 source address; but different implicit PvDs, using the same IPv6 source address; but different implicit PvDs,
advertised with different RAs, MUST use different link local advertised by different RAs, MUST use different link-local addresses
addresses. because these implicit PvDs are identified by the source addresses of
the RAs.
Whenever an RA, for a single PvD, would need to be sent via multiple Whenever an RA, for a single PvD, would need to be sent via multiple
packets, the PvD ID RA option header (i.e., all fields except the packets, the PvD option header (i.e., all fields except the 'Options'
'Options' field) MUST be repeated in all the transmitted RAs. But field) MUST be repeated in all the transmitted RAs. But the options
the options within the 'Options' field, MAY be transmitted only once, within the 'Options' field, MAY be transmitted only once, included in
included in one of the transmitted PvD ID RA options. one of the transmitted PvD options.
3.3. Host Behavior 3.3. Non-PvD-aware Host Behavior
As the PvD Option has a new option code, non-PvD-aware hosts will
simply ignore the PvD Option and all the options it contains. This
ensure the backward compatibility required in section 3.3 of
[RFC7556]. This behavior allows for a mixed-mode network with a mix
of PvD-aware and non-PvD-aware hosts coexist.
3.4. PvD-aware Host Behavior
Hosts MUST associate received RAs and included configuration Hosts MUST associate received RAs and included configuration
information (e.g., Router Valid Lifetime, Prefix Information information (e.g., Router Valid Lifetime, Prefix Information
[RFC4861], Recursive DNS Server [RFC8106], Routing Information [RFC4861], Recursive DNS Server [RFC8106], Routing Information
[RFC4191] options) with the explicit PvD identified by the first PvD [RFC4191] options) with the explicit PvD identified by the first PvD
ID Option present in the received RA, if any, or with the implicit Option present in the received RA, if any, or with the implicit PvD
PvD identified by the host interface and the source address of the identified by the host interface and the source address of the
received RA otherwise. received RA otherwise.
In case multiple PvD ID options are found in a given RA, hosts MUST In case multiple PvD options are found in a given RA, hosts MUST
ignore all but the first PvD ID option. ignore all but the first PvD option.
Similarly, hosts MUST associate all network configuration objects Similarly, hosts MUST associate all network configuration objects
(e.g., default routers, addresses, more specific routes, DNS (e.g., default routers, addresses, more specific routes, DNS
Recursive Resolvers) with the PvD associated with the RA which last Recursive Resolvers) with the PvD associated with the RA which last
updated the object. For example, addresses that are generated using updated the object. For example, addresses that are generated using
a received Prefix Information option (PIO) are associated with the a received Prefix Information option (PIO) are associated with the
PvD of the last received RA which included the given PIO. PvD of the last received RA which included the given PIO.
PvD IDs MUST be compared in a case-insensitive manner (i.e., A=a), PvD IDs MUST be compared in a case-insensitive manner (i.e., A=a),
assuming ASCII with zero parity while non-alphabetic codes must match assuming ASCII with zero parity while non-alphabetic codes must match
exactly (see also Section 3.1 of [RFC1035]). For example, exactly (see also Section 3.1 of [RFC1035]). For example,
pvd.example.com or PvD.Example.coM would refer to the same PvD. "pvd.example.com." or "PvD.Example.coM." would refer to the same PvD.
While resolving names, executing the default address selection While resolving names, executing the default address selection
algorithm [RFC6724] or executing the default router selection algorithm [RFC6724] or executing the default router selection
algorithm ([RFC2461], [RFC4191] and [RFC8028]), hosts MAY consider algorithm when forwarding packets ([RFC2461], [RFC4191] and
only the configuration associated with an arbitrary set of PvDs. [RFC8028]), hosts MAY consider only the configuration associated with
an arbitrary set of PvDs.
For example, a host MAY associate a given process with a specific For example, a host MAY associate a given process with a specific
PvD, or a specific set of PvDs, while associating another process PvD, or a specific set of PvDs, while associating another process
with another PvD. A PvD-aware application might also be able to with another PvD. A PvD-aware application might also be able to
select, on a per-connection basis, which PvDs should be used. In select, on a per-connection basis, which PvDs should be used. In
particular, constrained devices such as small battery operated particular, constrained devices such as small battery operated
devices (e.g. IoT), or devices with limited CPU or memory resources devices (e.g. IoT), or devices with limited CPU or memory resources
may purposefully use a single PvD while ignoring some received RAs may purposefully use a single PvD while ignoring some received RAs
containing different PvD IDs. containing different PvD IDs.
The way an application expresses its desire to use a given PvD, or a The way an application expresses its desire to use a given PvD, or a
set of PvDs, or the way this selection is enforced, is out of the set of PvDs, or the way this selection is enforced, is out of the
scope of this document. Useful insights about these considerations scope of this document. Useful insights about these considerations
can be found in [I-D.kline-mif-mpvd-api-reqs]. can be found in [I-D.kline-mif-mpvd-api-reqs].
3.3.1. DHCPv6 configuration association 3.4.1. DHCPv6 configuration association
When a host retrieves configuration elements using DHCPv6 (e.g., When a host retrieves configuration elements using DHCPv6 (e.g.,
addresses or DNS recursive resolvers), they MUST be associated with addresses or DNS recursive resolvers), they MUST be associated with
the explicit or implicit PvD of the RA received on the same the explicit or implicit PvD of the RA received on the same
interface, sent from the same LLA, and with the O-flag or M-flag set interface, sent from the same LLA, and with the O-flag or M-flag set
[RFC4861]. If no such PvD is found, or whenever multiple different [RFC4861]. If no such PvD is found, or whenever multiple different
PvDs are found, the host behavior is unspecified. PvDs are found, the host behavior is unspecified.
This process requires hosts to keep track of received RAs, associated This process requires hosts to keep track of received RAs, associated
PvD IDs, and routers LLA; it also assumes that the router either acts PvD IDs, and routers LLA; it also assumes that the router either acts
as a DHCPv6 server or relay and uses the same LLA for DHCPv6 and RA as a DHCPv6 server or relay and uses the same LLA for DHCPv6 and RA
traffic (which may not be the case when the router uses VRRP to send traffic (which may not be the case when the router uses VRRP to send
its RA). its RA).
3.3.2. DHCPv4 configuration association 3.4.2. DHCPv4 configuration association
When a host retrieves configuration elements from DHCPv4, they MUST When a host retrieves configuration elements from DHCPv4, they MUST
be associated with the explicit PvD received on the same interface, be associated with the explicit PvD received on the same interface,
whose PVD ID Options L-flag is set and, in the case of a non point- whose PVD Options L-flag is set and, in the case of a non point-to-
to-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.3.3. Interconnection Sharing by the Host 3.4.3. Connection Sharing by the Host
The situation when a node receives an RA on one interface (e.g. The situation when a node receives an RA on one interface (e.g.
cellular) and shares this connectivity by also acting as a router by cellular) and shares this connectivity by also acting as a router by
transmitting RA on another interface (e.g. WiFi) is known as transmitting RA on another interface (e.g. WiFi) is known as
'tethering'. It can be done as ND proxy. The exact behavior is TBD 'tethering'. It can be done as ND proxy. The exact behavior is out
but it is expected that the one or several PvD associated to the of scope of this document but it is expected that the one or several
shared interface (e.g. cellular) will also be advertised to the PvD associated to the shared interface (e.g. cellular) will also be
clients on the other interface (e.g. WiFi). advertised to the clients on the other interface (e.g. WiFi).
4. Provisioning Domain Additional Information 4. Provisioning Domain Additional Information
Additional information about the network characteristics can be Additional information about the network characteristics can be
retrieved based on the PvD ID. This set of information is called PvD retrieved based on the PvD ID. This set of information is called PvD
Additional Information, and is encoded as a JSON object [RFC7159]. Additional Information, and is encoded as a JSON object [RFC7159].
The purpose of this additional set of information is to securely The purpose of this additional set of information is to securely
provide additional information to applications about the connectivity provide additional information to applications about the connectivity
that is provided using a given interface and source address pair. It that is provided using a given interface and source address pair. It
typically includes data that would be considered too large, or not typically includes data that would be considered too large, or not
critical enough, to be provided within an RA option. The information critical enough, to be provided within an RA option. The information
contained in this object MAY be used by the operating system, network contained in this object MAY be used by the operating system, network
libraries, applications, or users, in order to decide which set of libraries, applications, or users, in order to decide which set of
PvDs should be used for which connection, as described in PvDs should be used for which connection, as described in
Section 3.3. Section 3.4.
4.1. Retrieving the PvD Additional Information 4.1. Retrieving the PvD Additional Information
When the H-flag of the PvD ID 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.
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.3. 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 PvD complete) before initiating the HTTP over TLS query. If the host has
allows for temporary address per [RFC4941], then hosts SHOULD use a a temporary address per [RFC4941] in this PvD, then hosts SHOULD use
temporary address to fetch the PvD Additional Information and SHOULD a temporary address to fetch the PvD Additional Information and
deprecate the used temporary address and generate a new temporary SHOULD deprecate the used temporary address and generate a new
address afterward. temporary address afterward.
If the HTTP status of the answer is greater than or equal to 400 the If the HTTP status of the answer is greater than or equal to 400 the
host MUST abandon and consider that there is no additional PvD host MUST abandon and consider that there is no additional PvD
information. If the HTTP status of the answer is between 300 and information. If the HTTP status of the answer is between 300 and
399, inclusive, it MUST follow the redirection(s). If the HTTP 399, inclusive, it MUST follow the redirection(s). If the HTTP
status of the answer is between 200 and 299, inclusive, the host MAY status of the answer is between 200 and 299, inclusive, the host MAY
get a file containing a single JSON object. When a JSON object could get a file containing a single JSON object. When a JSON object could
not be retrieved, an error message SHOULD be logged and/or displayed not be retrieved, an error message SHOULD be logged and/or displayed
in a rate-limited fashion. in a rate-limited fashion.
skipping to change at page 10, line 28 skipping to change at page 11, line 19
was retrieved (using serial number arithmetic comparisons [RFC1982]), was retrieved (using serial number arithmetic comparisons [RFC1982]),
or whenever the validity time included in the PVD Additional or whenever the validity time included in the PVD Additional
Information JSON object is expired, hosts MUST either perform a new Information JSON object is expired, hosts MUST either perform a new
query and retrieve a new version of the object, or, failing that, query and retrieve a new version of the object, or, failing that,
deprecate the object and stop using the additional information deprecate the object and stop using the additional information
provided in the JSON object. provided in the JSON object.
Hosts retrieving a new PvD Additional Information object MUST check Hosts retrieving a new PvD Additional Information object MUST check
for the presence and validity of the mandatory fields specified in for the presence and validity of the mandatory fields specified in
Section 4.3. A retrieved object including an expiration time that is Section 4.3. A retrieved object including an expiration time that is
already past or missing a mandatory element MUST be ignored. In already past or missing a mandatory element MUST be ignored.
order to avoid synchronized queries toward the server hosting the PvD
Additional Information when an object expires, a host which last In order to avoid synchronized queries toward the server hosting the
retrieved an object at a time A, including a validity time B, SHOULD PvD Additional Information when an object expires, object updates are
renew the object at a uniformly random time in the interval delayed by a randomized backoff time.
[(B-A)/2,A].
When a host performs an object update after it detected a change
in the PvD Option Sequence number, it MUST delay the query by a
random time between zero and 2**(Delay * 2) milliseconds, where
'Delay' corresponds to the 4 bits long unsigned integer in the
last received PvD Option.
When a host last retrieved an object at time A including a
validity time B, and is configured to keep the object up to date,
it MUST perform the update at a uniformly random time in the
interval [(B-A)/2,B].
In the example Figure 2, the delay field value is 5, this means that
host MUST delay the query by a random number between 0 and 2**(5 * 2)
milliseconds, i.e., between 0 and 1024 milliseconds.
Since the 'Delay' value is directly within the PvD Option rather than
the object itself, an operator may perform a push-based update by
incrementing the Sequence value while changing the Delay value
depending on the criticality of the update and its PvD Additional
Information servers capacity.
The PvD Additional Information object includes a set of IPv6 prefixes The PvD Additional Information object includes a set of IPv6 prefixes
(under the key "prefixes") which MUST be checked against all the (under the key "prefixes") which MUST be checked against all the
Prefix Information Options advertised in the RA. If any of the Prefix Information Options advertised in the RA. If any of the
prefixes included in the PIO is not covered by at least one of the prefixes included in the PIO is not covered by at least one of the
listed prefixes, the PvD associated with the tested prefix MUST be listed prefixes, the PvD associated with the tested prefix MUST be
considered unsafe and MUST NOT be used. While this does not prevent considered unsafe and MUST NOT be used. While this does not prevent
a malicious network provider, it does complicate some attack a malicious network provider, it does complicate some attack
scenarios, and may help detecting misconfiguration. scenarios, and may help detecting misconfiguration.
4.2. Operational Consideration to Providing the PvD Additional 4.2. Operational Consideration to Providing the PvD Additional
Information Information
Whenever the H-flag is set in the PvD RA Option, a valid PvD Whenever the H-flag is set in the PvD Option, a valid PvD Additional
Additional Information object MUST be made available to all hosts Information object MUST be made available to all hosts receiving the
receiving the RA by the network operator. In particular, when a RA by the network operator. In particular, when a captive portal is
captive portal is present, hosts MUST still be allowed to perform present, hosts MUST still be allowed to perform DNS, PKI and HTTP
DNS, PKI and HTTP over TLS operations related to the retrieval of the over TLS operations related to the retrieval of the object, even
object, even before logging into the captive portal. before logging into the captive portal.
Routers MAY increment the PVD ID Sequence number in order to inform Routers MAY increment the PVD Option Sequence number in order to
host that a new PvD Additional Information object is available and inform host that a new PvD Additional Information object is available
should be retrieved. and should be retrieved.
The server providing the JSON files SHOULD also check whether the The server providing the JSON files SHOULD also check whether the
client address is part of the prefixes listed into the additional client address is part of the prefixes listed into the additional
information and SHOULD return a 403 response code if there is no information and SHOULD return a 403 response code if there is no
match. match.
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.
skipping to change at page 13, line 32 skipping to change at page 14, line 40
prefix from the PvD Additional Information. An adversarial router prefix from the PvD Additional Information. An adversarial router
willing to fake the use of a given explicit PvD, without any access willing to fake the use of a given explicit PvD, without any access
to the actual PvD Additional Information, would need to perform NAT66 to the actual PvD Additional Information, would need to perform NAT66
in order to circumvent this check. in order to circumvent this check.
It is also RECOMMENDED that the HTTPS server checks the source It is also RECOMMENDED that the HTTPS server checks the source
addresses of incoming connections (see Section 4.1). This check give addresses of incoming connections (see Section 4.1). This check give
reasonable assurance that neither NPTv6 [RFC6296] nor NAT66 were used reasonable assurance that neither NPTv6 [RFC6296] nor NAT66 were used
and restricts the information to the valid network users. and restricts the information to the valid network users.
5. Operation Considerations 5. Operational Considerations
This section describes some use cases of PvD. For sake of This section describes some use cases of PvD. For the sake of
simplicity, the RA messages will not be described in the usual ASCII simplicity, the RA messages will not be described in the usual ASCII
art but rather in an indented list. For example, a RA message art but rather in an indented list. For example, a RA message
containing some options and a PvD ID option that also contains other containing some options and a PvD option that also contains other
options will be described as: options will be described as:
o RA Header: router lifetime = 6000 o RA Header: router lifetime = 6000
o Prefix Information Option: length = 4, prefix = 2001:db8:cafe::/64 o Prefix Information Option: length = 4, prefix = 2001:db8:cafe::/64
o PvD Option header: length = 3+ 5 +4 , PvD ID FQDN = example.org.,
o PvD ID header: length = 3+ 5 +4 , PvD ID FQDN = example.org, R-flag = 0 (actual length of the header with padding 24 bytes = 3
A-flag = 0 (actual length of the header with padding 24 bytes = 3
* 8 bytes) * 8 bytes)
* Recursive DNS Server: length = 5, addresses= * Recursive DNS Server: length = 5, addresses=
[2001:db8:cafe::53, 2001:db8:f00d::53] [2001:db8:cafe::53, 2001:db8:f00d::53]
* Prefix Information Option: length = 4, prefix = * Prefix Information Option: length = 4, prefix =
2001:db8:f00d::/64 2001:db8:f00d::/64
It is expected that for some years, networks will have a mix of PvD- It is expected that for some years, networks will have a mixed
aware hosts and PvD-ignorant hosts. If there is a need to give environment of PvD-aware hosts and non-PvD-aware hosts. If there is
specific information to PvD-aware hosts only, then it is recommended a need to give specific information to PvD-aware hosts only, then it
to send TWO RA messages: one for each class of hosts. For example, is recommended to send TWO RA messages: one for each class of hosts.
here is the RA for PvD-ignorant hosts: For example, here is the RA for non-PvD-aware hosts:
o RA Header: router lifetime = 6000 (PvD-ignorant hosts will use o RA Header: router lifetime = 6000 (non-PvD-aware hosts will use
this router as a default router) this router as a default router)
o Prefix Information Option: length = 4, prefix = 2001:db8:cafe::/64 o Prefix Information Option: length = 4, prefix = 2001:db8:cafe::/64
o Recursive DNS Server Option: length = 3, addresses= o Recursive DNS Server Option: length = 3, addresses=
[2001:db8:cafe::53] [2001:db8:cafe::53]
o PvD ID header: length = 3+ 2, PvD ID FQDN = foo.example.org, o PvD Option header: length = 3+ 2, PvD ID FQDN = foo.example.org.,
A-flag = 1 (actual length of the header 24 bytes = 3 * 8 bytes) R-flag = 1 (actual length of the header 24 bytes = 3 * 8 bytes)
* RA Header: router lifetime = 0 (PvD-aware hosts will not use * RA Header: router lifetime = 0 (PvD-aware hosts will not use
this router as a default router), implicit length = 2 this router as a default router), implicit length = 2
And here is a RA example for PvD-aware hosts: And here is a RA example for PvD-aware hosts:
o RA Header: router lifetime = 0 (PvD-ignorant hosts will not use o RA Header: router lifetime = 0 (non-PvD-aware hosts will not use
this router as a default router) this router as a default router)
o PvD ID header: length = 3+ 2 + 4 + 3, PvD ID FQDN = example.org, o PvD Option header: length = 3+ 2 + 4 + 3, PvD ID FQDN =
A-flag = 1 (actual length of the header 24 bytes = 3 * 8 bytes) example.org., R-flag = 1 (actual length of the header 24 bytes = 3
* 8 bytes)
* RA Header: router lifetime = 1600 (PvD-aware hosts will use * RA Header: router lifetime = 1600 (PvD-aware hosts will use
this router as a default router), implicit length = 2 this router as a default router), implicit length = 2
* Prefix Information Option: length = 4, prefix = * Prefix Information Option: length = 4, prefix =
2001:db8:f00d::/64 2001:db8:f00d::/64
* Recursive DNS Server Option: length = 3, addresses= * Recursive DNS Server Option: length = 3, addresses=
[2001:db8:f00d::53] [2001:db8:f00d::53]
In the above example, PvD-ignorant hosts will only use the first RA In the above example, non-PvD-aware hosts will only use the first RA
sent from their default router and using the 2001:db8:cafe::/64 sent from their default router and using the 2001:db8:cafe::/64
prefix. PvD-aware hosts will autonomously configure addresses from prefix. PvD-aware hosts will autonomously configure addresses from
both PIOs, but will only use the source address in 2001:db8:f00d::/64 both PIOs, but will only use the source address in 2001:db8:f00d::/64
to communicate past the first hop router since only the router to communicate past the first hop router since only the router
sending the second RA will be used as default router; similarly, they sending the second RA will be used as default router; similarly, they
will use the DNS server 2001:db8:f00d::53 when communicating with will use the DNS server 2001:db8:f00d::53 when communicating with
this adress. this adress.
6. Security Considerations 6. Security Considerations
Although some solutions such as IPsec or SeND [RFC3971] can be used Although some solutions such as IPsec or SeND [RFC3971] can be used
in order to secure the IPv6 Neighbor Discovery Protocol, actual in order to secure the IPv6 Neighbor Discovery Protocol, in practice
deployments largely rely on link layer or physical layer security actual deployments largely rely on link layer or physical layer
mechanisms (e.g. 802.1x [IEEE8021X]) in conjunction with RA Guard security mechanisms (e.g. 802.1x [IEEE8021X]) in conjunction with RA
[RFC6105]. Guard [RFC6105].
This specification does not improve the Neighbor Discovery Protocol This specification does not improve the Neighbor Discovery Protocol
security model, but extends the purely link-local trust relationship security model, but extends the purely link-local trust relationship
between the host and the default routers with HTTP over TLS between the host and the default routers with HTTP over TLS
communications which servers are authenticated as rightful owners of communications which servers are authenticated as rightful owners of
the FQDN received within the trusted PvD ID RA option. the FQDN received within the trusted PvD ID RA option.
It must be noted that Section 4.4 of this document only provides It must be noted that Section 4.4 of this document only provides
reasonable assurance against misconfiguration but does not prevent an reasonable assurance against misconfiguration but does not prevent an
hostile network access provider to wrong information that could lead hostile network access provider to advertize wrong information that
applications or hosts to select an hostile PvD. Users should always could lead applications or hosts to select an hostile PvD. Users
apply caution when connecting to an unknown network. should always apply caution when connecting to an unknown network.
7. Privacy Considerations 7. Privacy Considerations
Retrieval of the PvD Additional Information over HTTPS requires early Retrieval of the PvD Additional Information over HTTPS requires early
communications between the connecting host and a server which may be communications between the connecting host and a server which may be
located further than the first hop router. Although this server is located further than the first hop router. Although this server is
likely to be located within the same administrative domain as the likely to be located within the same administrative domain as the
default router, this property can't be ensured. Therefore, hosts default router, this property can't be ensured. Therefore, hosts
willing to retrieve the PvD Additional Information before using it willing to retrieve the PvD Additional Information before using it
without leaking identity information, SHOULD make use of an IPv6 without leaking identity information, SHOULD make use of an IPv6
Privacy Address and SHOULD NOT include any privacy sensitive data, Privacy Address and SHOULD NOT include any privacy sensitive data,
such as User Agent header or HTTP cookie, while performing the HTTP such as User Agent header or HTTP cookie, while performing the HTTP
over TLS query. over TLS query.
From a privacy perspective, retrieving the PvD Additional Information From a privacy perspective, retrieving the PvD Additional Information
is not different from establishing a first connexion to a remote is not different from establishing a first connection to a remote
server, or even performing a single DNS lookup. For example, most server, or even performing a single DNS lookup. For example, most
operating systems already perform early queries to well known web operating systems already perform early queries to well known web
sites, such as http://captive.example.com/hotspot-detect.html, in sites, such as http://captive.example.com/hotspot-detect.html, in
order to detect the presence of a captive portal. order to detect the presence of a captive portal.
There may be some cases where hosts, for privacy reasons, should There may be some cases where hosts, for privacy reasons, should
refrain from accessing servers that are located outside a certain refrain from accessing servers that are located outside a certain
network boundary. In practice, this could be implemented as a network boundary. In practice, this could be implemented as a
whitelist of 'trusted' FQDNs and/or IP prefixes that the host is whitelist of 'trusted' FQDNs and/or IP prefixes that the host is
allowed to communicate with. In such scenarios, the host SHOULD allowed to communicate with. In such scenarios, the host SHOULD
check that the provided PvD ID, as well as the IP address that it check that the provided PvD ID, as well as the IP address that it
resolves into, are part of the allowed whitelist. resolves into, are part of the allowed whitelist.
8. IANA Considerations 8. IANA Considerations
IANA is asked to assign the value TBD from the IPv6 Neighbor Upon publication of this document, IANA is asked to remove the
Discovery Option Formats registry for the PvD ID Router Advertisement 'reclaimable' tag off the value 21 for the PvD option (from the IPv6
option. Neighbor Discovery Option Formats registry).
IANA is asked to assign the value "pvd" from the Well-Known URIs IANA is asked to assign the value "pvd" from the Well-Known URIs
registry. registry.
IANA is asked to create and maintain a new registry entitled IANA is asked to create and maintain a new registry entitled
"Additional Information PvD Keys" containing ASCII strings. The "Additional Information PvD Keys" containing ASCII strings. The
initial content of this registry are given in Section 4.3; future initial content of this registry are given in Section 4.3; future
assignments are to be made through Expert Review [BCP36]. assignments are to be made through Expert Review [BCP36].
Finally, IANA is asked to create and maintain a new registry entitled Finally, IANA is asked to create and maintain a new registry entitled
"PvD ID Router Advertisement option Flags" reserving bit positions "PvD option Flags" reserving bit positions from 0 to 15 to be used in
from 0 to 15 to be used in the PvD ID Router Advertisement option the PvD option bitmask. Bit position 0, 1 and 2 are reserved by this
bitmask. Bit position 0, 1 and 2 are reserved by this document (as document (as specified in Figure 1). Future assignments require a
specified in Figure 1). Future assignments require a Standard Track Standard Track RFC document.
RFC document.
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 Abrahamson, Ray Bellis, Lorenzo Thanks also to Marcus Keane, Mikael Abrahamson, Ray Bellis, Zhen Cao,
Colitti, Bob Hinden, Tatuya Jinmei, Erik Kline, Ted Lemon, Jen Tim Chow, Lorenzo Colitti, Ian Farrer, Bob Hinden, Tatuya Jinmei,
Lenkova, Mark Townsley and James Woodyatt for useful and interesting Erik Kline, Ted Lemon, Jen Lenkova, Veronika McKillop, Mark Townsley
discussions. and James Woodyatt for useful and interesting discussions.
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 18, line 49 skipping to change at page 20, line 19
[RFC6296] Wasserman, M. and F. Baker, "IPv6-to-IPv6 Network Prefix [RFC6296] Wasserman, M. and F. Baker, "IPv6-to-IPv6 Network Prefix
Translation", RFC 6296, DOI 10.17487/RFC6296, June 2011, Translation", RFC 6296, DOI 10.17487/RFC6296, June 2011,
<https://www.rfc-editor.org/info/rfc6296>. <https://www.rfc-editor.org/info/rfc6296>.
[RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown, [RFC6724] Thaler, D., Ed., Draves, R., Matsumoto, A., and T. Chown,
"Default Address Selection for Internet Protocol Version 6 "Default Address Selection for Internet Protocol Version 6
(IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012, (IPv6)", RFC 6724, DOI 10.17487/RFC6724, September 2012,
<https://www.rfc-editor.org/info/rfc6724>. <https://www.rfc-editor.org/info/rfc6724>.
[RFC6731] Savolainen, T., Kato, J., and T. Lemon, "Improved
Recursive DNS Server Selection for Multi-Interfaced
Nodes", RFC 6731, DOI 10.17487/RFC6731, December 2012,
<https://www.rfc-editor.org/info/rfc6731>.
[RFC7556] Anipko, D., Ed., "Multiple Provisioning Domain [RFC7556] Anipko, D., Ed., "Multiple Provisioning Domain
Architecture", RFC 7556, DOI 10.17487/RFC7556, June 2015, Architecture", RFC 7556, DOI 10.17487/RFC7556, June 2015,
<https://www.rfc-editor.org/info/rfc7556>. <https://www.rfc-editor.org/info/rfc7556>.
[RFC8028] Baker, F. and B. Carpenter, "First-Hop Router Selection by [RFC8028] Baker, F. and B. Carpenter, "First-Hop Router Selection by
Hosts in a Multi-Prefix Network", RFC 8028, Hosts in a Multi-Prefix Network", RFC 8028,
DOI 10.17487/RFC8028, November 2016, DOI 10.17487/RFC8028, November 2016,
<https://www.rfc-editor.org/info/rfc8028>. <https://www.rfc-editor.org/info/rfc8028>.
[RFC8106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, [RFC8106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli,
skipping to change at page 21, line 29 skipping to change at page 23, line 5
intended to modify host's networking stack behavior, but rather intended to modify host's networking stack behavior, but rather
provide information to the Application, used to select which PvDs provide information to the Application, used to select which PvDs
must be used and provide configuration parameters to the transport must be used and provide configuration parameters to the transport
layer. layer.
The RA option padding is used to increase the option size to the The RA option padding is used to increase the option size to the
next 64 (was 32) bits boundary. next 64 (was 32) bits boundary.
Better detail the Security model and Privacy considerations. Better detail the Security model and Privacy considerations.
A.6. WG Document version 02
Use the IANA value of 21 in the text and update the IANA
considerations section accordingly
add the Delay field to avoid the thundering herd effect
add Wenqin Shao as author
keep the 1 PvD per RA model
changed the intro (per Zhen Cao) "when choosing which PvD and
transport should be used" => "when choosing which PvD should be
used"
rename A-flag in R-flag to avoid A-flag of PIO
use the wording "PvD Option", removing the ID token as it is now a
container with more then just an ID, removing 'RA' in the option
name to be consistent with other IANA NDP option
use "non-PvD-aware" rather than "PvD-ignorant"
added more reference to RFC 7556 (notably for PvD being globally
unique, introducing PvD-aware host vs. PvD-aware node)
Section 3.4.3 renamed from "interconnection shared by node" to
'connection shared by node"
Section 3.4 renamed into "PvD-aware Host Behavior"
Added a section "Non-PvD-aware Host Behavior"
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 22, line 4 skipping to change at page 24, line 16
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
Email: tpauly@apple.com Email: tpauly@apple.com
David Schinazi David Schinazi
Apple Apple
Email: dschinazi@apple.com Email: dschinazi@apple.com
Wenqin Shao
Telecom-ParisTech
France
Email: wenqin.shao@telecom-paristech.fr
 End of changes. 67 change blocks. 
156 lines changed or deleted 236 lines changed or added

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