draft-ietf-6man-dns-options-bis-04.txt   draft-ietf-6man-dns-options-bis-05.txt 
Network Working Group J. Jeong Network Working Group J. Jeong
Internet-Draft Brocade/ETRI Internet-Draft Brocade/ETRI
Obsoletes: 5006 (if approved) S. Park Obsoletes: 5006 (if approved) S. Park
Intended status: Standards Track SAMSUNG Electronics Intended status: Standards Track SAMSUNG Electronics
Expires: December 30, 2010 L. Beloeil Expires: January 1, 2011 L. Beloeil
France Telecom R&D France Telecom R&D
S. Madanapalli S. Madanapalli
Ordyn Technologies Ordyn Technologies
June 28, 2010 June 30, 2010
IPv6 Router Advertisement Options for DNS Configuration RFC 5006-bis IPv6 Router Advertisement Options for DNS Configuration
draft-ietf-6man-dns-options-bis-04 draft-ietf-6man-dns-options-bis-05
Abstract Abstract
This document specifies IPv6 Router Advertisement options to allow This document specifies IPv6 Router Advertisement options to allow
IPv6 routers to advertise a list of DNS recursive server addresses IPv6 routers to advertise a list of DNS recursive server addresses
and a DNS search list to IPv6 hosts. and a DNS search list to IPv6 hosts.
Status of This Memo Status of This Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
skipping to change at page 1, line 43 skipping to change at page 1, line 43
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 December 30, 2010. This Internet-Draft will expire on January 1, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2010 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
skipping to change at page 2, line 34 skipping to change at page 2, line 34
5. Neighbor Discovery Extension . . . . . . . . . . . . . . . . . 5 5. Neighbor Discovery Extension . . . . . . . . . . . . . . . . . 5
5.1. Recursive DNS Server Option . . . . . . . . . . . . . . . 5 5.1. Recursive DNS Server Option . . . . . . . . . . . . . . . 5
5.2. DNS Search List Option . . . . . . . . . . . . . . . . . . 7 5.2. DNS Search List Option . . . . . . . . . . . . . . . . . . 7
5.3. Procedure of DNS Configuration . . . . . . . . . . . . . . 8 5.3. Procedure of DNS Configuration . . . . . . . . . . . . . . 8
5.3.1. Procedure in IPv6 Host . . . . . . . . . . . . . . . . 8 5.3.1. Procedure in IPv6 Host . . . . . . . . . . . . . . . . 8
6. Implementation Considerations . . . . . . . . . . . . . . . . 9 6. Implementation Considerations . . . . . . . . . . . . . . . . 9
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 . . . . . . . . . . . . . . . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 13 7. Security Considerations . . . . . . . . . . . . . . . . . . . 13
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 14
10.1. Normative References . . . . . . . . . . . . . . . . . . . 14 10.1. Normative References . . . . . . . . . . . . . . . . . . . 14
10.2. Informative References . . . . . . . . . . . . . . . . . . 14 10.2. Informative References . . . . . . . . . . . . . . . . . . 15
Appendix A. Changes from RFC 5006 . . . . . . . . . . . . . . . . 15 Appendix A. Changes from RFC 5006 . . . . . . . . . . . . . . . . 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) option for DNS configuration in IPv6 hosts Advertisement (RA) option for DNS configuration in IPv6 hosts
specified in an earlier experimental specification [RFC5006] and also specified in an earlier experimental specification [RFC5006] and also
to define a new RA option for Domain Name Search lists. to define a new RA option for Domain Name Search lists.
Neighbor Discovery (ND) for IP Version 6 and IPv6 Stateless Address Neighbor Discovery (ND) for IP Version 6 and IPv6 Stateless Address
skipping to change at page 11, line 14 skipping to change at page 11, line 14
Step (a): Receive and parse the RDNSS option(s). For the RDNSS Step (a): Receive and parse the RDNSS option(s). For the RDNSS
addresses in each RDNSS option, perform Step (b) through Step (d). addresses in each RDNSS option, perform Step (b) through Step (d).
Step (b): For each RDNSS address, check the following: If the Step (b): For each RDNSS address, check the following: If the
RDNSS address already exists in the DNS Server List and the RDNSS RDNSS address already exists in the DNS Server List and the RDNSS
option's Lifetime field is set to zero, delete the corresponding option's Lifetime field is set to zero, delete the corresponding
RDNSS entry from both the DNS Server List and the Resolver RDNSS entry from both the DNS Server List and the Resolver
Repository in order to prevent the RDNSS address from being used Repository in order to prevent the RDNSS address from being used
any more for certain reasons in network management, e.g., the any more for certain reasons in network management, e.g., the
termination of the RDNSS or a renumbering situation. The termination of the RDNSS or a renumbering situation. That is, the
processing of this RDNSS address is finished here. Otherwise, go RDNSS can resign from its DNS service because the machine running
to Step (c). the RDNSS is out of service intentionally or unintentionally.
Also, under the renumbering situation, the RDNSS's IPv6 address
will be changed, so the previous RDNSS address should not be used
any more. The processing of this RDNSS address is finished here.
Otherwise, go to Step (c).
Step (c): For each RDNSS address, if it already exists in the DNS Step (c): For each RDNSS address, if it already exists in the DNS
Server List, then just update the value of the Expiration-time Server List, then just update the value of the Expiration-time
field according to the procedure specified in the third bullet of field according to the procedure specified in the third bullet of
Section 6.1. Otherwise, go to Step (d). Section 6.1. Otherwise, go to Step (d).
Step (d): For each RDNSS address, if it does not exist in the DNS Step (d): For each RDNSS address, if it does not exist in the DNS
Server List, register the RDNSS address and lifetime with the DNS Server List, register the RDNSS address and lifetime with the DNS
Server List and then insert the RDNSS address in front of the Server List and then insert the RDNSS address in front of the
Resolver Repository. In the case where the data structure for the Resolver Repository. In the case where the data structure for the
skipping to change at page 12, line 18 skipping to change at page 12, line 26
Step (a): Receive and parse the DNSSL option(s). For the DNSSL Step (a): Receive and parse the DNSSL option(s). For the DNSSL
domain names in each DNSSL option, perform Step (b) through Step domain names in each DNSSL option, perform Step (b) through Step
(d). (d).
Step (b): For each DNSSL domain name, check the following: If the Step (b): For each DNSSL domain name, check the following: If the
DNSSL domain name already exists in the DNS Search List and the DNSSL domain name already exists in the DNS Search List and the
DNSSL option's Lifetime field is set to zero, delete the DNSSL option's Lifetime field is set to zero, delete the
corresponding DNSSL entry from both the DNS Search List and the corresponding DNSSL entry from both the DNS Search List and the
Resolver Repository in order to prevent the DNSSL domain name from Resolver Repository in order to prevent the DNSSL domain name from
being used any more for certain reasons in network management, being used any more for certain reasons in network management,
e.g., the termination of the RDNSS or a renaming situation. The e.g., the termination of the RDNSS or a renaming situation. That
processing of this DNSSL domain name is finished here. Otherwise, is, the RDNSS can resign from its DNS service because the machine
go to Step (c). running the RDNSS is out of service intentionally or
unintentionally. Also, under the renaming situation, the DNSSL
domain names will be changed, so the previous domain names should
not be used any more. The processing of this DNSSL domain name is
finished here. Otherwise, go to Step (c).
Step (c): For each DNSSL domain name, if it already exists in the Step (c): For each DNSSL domain name, if it already exists in the
DNS Server List, then just update the value of the Expiration-time DNS Server List, then just update the value of the Expiration-time
field according to the procedure specified in the third bullet of field according to the procedure specified in the third bullet of
Section 6.1. Otherwise, go to Step (d). Section 6.1. Otherwise, go to Step (d).
Step (d): For each DNSSL domain name, if it does not exist in the Step (d): For each DNSSL domain name, if it does not exist in the
DNS Search List, register the DNSSL domain name and lifetime with DNS Search List, register the DNSSL domain name and lifetime with
the DNS Search List and then insert the DNSSL domain name in front the DNS Search List and then insert the DNSSL domain name in front
of the Resolver Repository. In the case where the data structure of the Resolver Repository. In the case where the data structure
skipping to change at page 16, line 31 skipping to change at page 16, line 38
Discovery Option type for DNSSL option. Discovery Option type for DNSSL option.
Authors' Addresses Authors' Addresses
Jaehoon Paul Jeong Jaehoon Paul Jeong
Brocade Communications Systems/ETRI Brocade Communications Systems/ETRI
6000 Nathan Ln N 6000 Nathan Ln N
Plymouth, MN 55442 Plymouth, MN 55442
USA USA
Phone: +1 763 268 7173 +1 763 268 7173 Phone: +1 763 268 7173
Fax: +1 763 268 6800 Fax: +1 763 268 6800
EMail: pjeong@brocade.com EMail: pjeong@brocade.com
URI: http://www.cs.umn.edu/~jjeong/ URI: http://www.cs.umn.edu/~jjeong/
Soohong Daniel Park Soohong Daniel Park
Mobile Platform Laboratory Mobile Platform Laboratory
SAMSUNG Electronics SAMSUNG Electronics
416 Maetan-3dong, Yeongtong-Gu 416 Maetan-3dong, Yeongtong-Gu
Suwon, Gyeonggi-Do 443-742 Suwon, Gyeonggi-Do 443-742
Korea Korea
Phone: +82 31 200 4508 +82 31 200 4508 Phone: +82 31 200 4508
EMail: soohong.park@samsung.com EMail: soohong.park@samsung.com
Luc Beloeil Luc Beloeil
France Telecom R&D France Telecom R&D
42, rue des coutures 42, rue des coutures
BP 6243 BP 6243
14066 CAEN Cedex 4 14066 CAEN Cedex 4
France France
Phone: +33 2 40 44 97 40 +33 2 40 44 97 40 Phone: +33 2 40 44 97 40
EMail: luc.beloeil@orange-ftgroup.com EMail: luc.beloeil@orange-ftgroup.com
Syam Madanapalli Syam Madanapalli
Ordyn Technologies Ordyn Technologies
1st Floor, Creator Building, ITPL 1st Floor, Creator Building, ITPL
Bangalore - 560066 Bangalore - 560066
India India
Phone: +91-80-40383000 +91-80-40383000 Phone: +91-80-40383000
EMail: smadanapalli@gmail.com EMail: smadanapalli@gmail.com
 End of changes. 14 change blocks. 
18 lines changed or deleted 26 lines changed or added

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