Discouraging use of RFC7050 for Discovery of IPv6 Prefix Used for IPv6 Address Synthesis
draft-buraglio-deprecate7050-01
| Document | Type |
Replaced Internet-Draft
(v6ops WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Nick Buraglio , Tommy Jensen , Jen Linkova | ||
| Last updated | 2024-12-26 (Latest revision 2024-11-15) | ||
| Replaced by | draft-ietf-v6ops-prefer8781 | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-v6ops-prefer8781 | |
| 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
RFC7050 describes a method for detecting the presence of DNS64 and for learning the IPv6 prefix used for protocol translation (RFC7915). This methodology depends on the existence of a well-known IPv4-only fully qualified domain name "ipv4only.arpa.". Because newer methods exist that lack the requirement of a higher level protocol, instead using existing operations in the form of native router advertisements, discovery of the IPv6 prefix used for protocol translation using RFC7050 should be discouraged. RFC7050 MAY only be used if other methods (such as RFC8781]) can not be used.
Authors
Nick Buraglio
Tommy Jensen
Jen Linkova
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)