draft-ietf-6man-rdnss-rfc6106bis-13.txt   draft-ietf-6man-rdnss-rfc6106bis-14.txt 
Network Working Group J. Jeong Network Working Group J. Jeong
Internet-Draft Sungkyunkwan University Internet-Draft Sungkyunkwan University
Obsoletes: 6106 (if approved) S. Park Obsoletes: 6106 (if approved) S. Park
Intended status: Standards Track Samsung Electronics Intended status: Standards Track Samsung Electronics
Expires: November 29, 2016 L. Beloeil Expires: December 16, 2016 L. Beloeil
France Telecom R&D France Telecom R&D
S. Madanapalli S. Madanapalli
iRam Technologies iRam Technologies
May 28, 2016 June 14, 2016
IPv6 Router Advertisement Options for DNS Configuration IPv6 Router Advertisement Options for DNS Configuration
draft-ietf-6man-rdnss-rfc6106bis-13 draft-ietf-6man-rdnss-rfc6106bis-14
Abstract Abstract
This document specifies IPv6 Router Advertisement (RA) options This document specifies IPv6 Router Advertisement (RA) options
(called DNS RA options) to allow IPv6 routers to advertise a list of (called DNS RA options) to allow IPv6 routers to advertise a list of
DNS recursive server addresses and a DNS Search List to IPv6 hosts. DNS recursive server addresses and a DNS Search List to IPv6 hosts.
This document obsoletes RFC 6106 and allows a higher default value of This document obsoletes RFC 6106 and allows a higher default value of
the lifetime of the DNS RA options to avoid the frequent expiry of the lifetime of the DNS RA options to avoid the frequent expiry of
the options on links with a relatively high rate of packet loss. the options on links with a relatively high rate of packet loss.
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on November 29, 2016. This Internet-Draft will expire on December 16, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2016 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
(http://trustee.ietf.org/license-info) in effect on the date of (http://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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 2, line 43 skipping to change at page 2, line 43
6.1. DNS Repository Management . . . . . . . . . . . . . . . . 10 6.1. DNS Repository Management . . . . . . . . . . . . . . . . 10
6.2. Synchronization between DNS Server List and Resolver 6.2. Synchronization between DNS Server List and Resolver
Repository . . . . . . . . . . . . . . . . . . . . . . . . 10 Repository . . . . . . . . . . . . . . . . . . . . . . . . 10
6.3. Synchronization between DNS Search List and Resolver 6.3. Synchronization between DNS Search List and Resolver
Repository . . . . . . . . . . . . . . . . . . . . . . . . 11 Repository . . . . . . . . . . . . . . . . . . . . . . . . 11
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
7.1. Security Threats . . . . . . . . . . . . . . . . . . . . . 12 7.1. Security Threats . . . . . . . . . . . . . . . . . . . . . 12
7.2. Recommendations . . . . . . . . . . . . . . . . . . . . . 12 7.2. Recommendations . . . . . . . . . . . . . . . . . . . . . 12
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 13
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 13
10.1. Normative References . . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . . 13
10.2. Informative References . . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . . 14
Appendix A. Changes from RFC 6106 . . . . . . . . . . . . . . . . 15 Appendix A. Changes from RFC 6106 . . . . . . . . . . . . . . . . 15
1. Introduction 1. Introduction
The purpose of this document is to standardize IPv6 Router The purpose of this document is to standardize IPv6 Router
Advertisement (RA) options (DNS RA options) for DNS Recursive Server Advertisement (RA) options (DNS RA options) for DNS Recursive Server
Addresses used for the DNS name resolution in IPv6 hosts, and also Addresses used for the DNS name resolution in IPv6 hosts, and also
for a DNS Search List of domain suffixes. for a DNS Search List of domain suffixes.
skipping to change at page 12, line 8 skipping to change at page 12, line 8
6.3. Synchronization between DNS Search List and Resolver Repository 6.3. Synchronization between DNS Search List and Resolver Repository
When an IPv6 host receives the information of multiple DNSSL domain When an IPv6 host receives the information of multiple DNSSL domain
names within a network through an RA message with DNSSL option(s), it names within a network through an RA message with DNSSL option(s), it
stores the DNSSL domain names (in order) into both the DNS Search stores the DNSSL domain names (in order) into both the DNS Search
List and the Resolver Repository. The processing of the DNSSL List and the Resolver Repository. The processing of the DNSSL
consists of (i) the processing of DNSSL option(s) included in an RA consists of (i) the processing of DNSSL option(s) included in an RA
message and (ii) the handling of expired DNSSLs. The processing of message and (ii) the handling of expired DNSSLs. The processing of
DNSSL option(s) is the same with that of RDNSS option(s) in Section DNSSL option(s) is the same with that of RDNSS option(s) in Section
6.2 except Step (b). 6.2.
In Step (b), if the DNSSL domain name already exists in the DNS
Search List and the DNSSL option's Lifetime field is set to zero,
delete the corresponding DNSSL entry from both the DNS Search List
and the Resolver Repository in order to prevent the DNSSL domain name
from being used any more for certain reasons in network management,
e.g., the termination of the usage of the DNSSL domain name. That
is, the DNSSL domain name may not be used any more by the policy of
the network.
7. Security Considerations 7. Security Considerations
In this section, we analyze security threats related to DNS options In this section, we analyze security threats related to DNS options
and then suggest recommendations to cope with such security threats. and then suggest recommendations to cope with such security threats.
7.1. Security Threats 7.1. Security Threats
For the RDNSS option, an attacker could send an RA with a fraudulent For the RDNSS option, an attacker could send an RA with a fraudulent
RDNSS address, misleading IPv6 hosts into contacting an unintended RDNSS address, misleading IPv6 hosts into contacting an unintended
skipping to change at page 15, line 38 skipping to change at page 15, line 28
Provisioning Domains Problem Statement", RFC 6418, Provisioning Domains Problem Statement", RFC 6418,
November 2011. November 2011.
[RFC6419] Wasserman, M. and P. Seite, "Current Practices for [RFC6419] Wasserman, M. and P. Seite, "Current Practices for
Multiple-Interface Hosts", RFC 6419, November 2011. Multiple-Interface Hosts", RFC 6419, November 2011.
[RFC6731] Savolainen, T., Kato, J., and T. Lemon, "Improved [RFC6731] Savolainen, T., Kato, J., and T. Lemon, "Improved
Recursive DNS Server Selection for Multi-Interfaced Recursive DNS Server Selection for Multi-Interfaced
Nodes", RFC 6731, December 2012. Nodes", RFC 6731, December 2012.
[ICMPv6] ICMPv6 Parameters Registry, http://www.iana.org/ [ICMPv6] ICMPv6 Parameters Registry, "http://www.iana.org/
assignments/icmpv6-parameters/icmpv6-parameters. assignments/icmpv6-parameters/
xhtml#icmpv6-parameters-5 icmpv6-parameters.xhtml#icmpv6-parameters-5".
Appendix A. Changes from RFC 6106 Appendix A. Changes from RFC 6106
The following changes were made from RFC 6106 "IPv6 Router The following changes were made from RFC 6106 "IPv6 Router
Advertisement Options for DNS Configuration": Advertisement Options for DNS Configuration":
o This document allows a higher default value of the lifetime of the o This document allows a higher default value of the lifetime of the
DNS RA options than RFC 6106 in order to avoid the frequent expiry DNS RA options than RFC 6106 in order to avoid the frequent expiry
of the options on links with a relatively high rate of packet of the options on links with a relatively high rate of packet
loss, and also making additional clarifications. The lifetime's loss, and also making additional clarifications. The lifetime's
 End of changes. 7 change blocks. 
19 lines changed or deleted 10 lines changed or added

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