A recommendation for filtering address records in stub resolvers
draft-caletka-aaaa-filtering-01
| Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Ondřej Caletka | ||
| Last updated | 2025-08-13 (Latest revision 2025-07-06) | ||
| Replaced by | draft-ietf-v6ops-aaaa-filtering | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources |
GitHub Repository
Mailing list discussion |
||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-aaaa-filtering | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Since IPv4 and IPv6 addresses are represented by different resource records in the Domain Name System, operating systems capable of running both IPv4 and IPv6 need to execute two queries when resolving a host name. This document discusses the conditions under which a stub resolver can optimize the process by not sending one of the queries if the host is connected to a single-stack network.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)