Current issues with DNS Configuration Options for SLAAC
draft-gont-6man-slaac-dns-config-issues-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2015-08-30 (latest revision 2015-02-26) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
pdf
html
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-gont-6man-slaac-dns-config-issues-01.txt
Abstract
RFC 6106 specifies two Neighbor Discovery options that can be included in Router Advertisement messages to convey information about DNS recursive servers and DNS Search Lists. Small lifetime values for the aforementioned options have been found to cause interoperability problems in those network scenarios in which these options are used to convey DNS-related information. This document analyzes the aforementioned problem, and formally updates RFC 6106 such that these issues are mitigated.
Authors
Fernando Gont
(fgont@si6networks.com)
Pavel Simerda
(pavlix@pavlix.net)
Shucheng LIU
(liushucheng@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)