Discovering PREF64 in Router Advertisements
draft-pref64folks-6man-ra-pref64-02
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-10-01
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
IPv6 Maintenance L. Colitti
Internet-Draft E. Kline
Intended status: Standards Track J. Linkova
Expires: April 4, 2019 Google
October 1, 2018
Discovering PREF64 in Router Advertisements
draft-pref64folks-6man-ra-pref64-02
Abstract
This document specifies a Router Advertisement option to communicate
NAT64 prefixes to clients.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 4, 2019.
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Colitti, et al. Expires April 4, 2019 [Page 1]
Internet-Draft Discovering PREF64 in Router Advertisements October 2018
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
1.1. Requirements Language . . . . . . . . . . . . . . . . . . 2
1.2. Terminology . . . . . . . . . . . . . . . . . . . . . . . 2
2. Why include the NAT64 prefix in Router Advertisements . . . . 3
3. Semantics . . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. Option format . . . . . . . . . . . . . . . . . . . . . . . . 4
5. Handling Multiple NAT64 Prefixes . . . . . . . . . . . . . . 4
6. Multihoming . . . . . . . . . . . . . . . . . . . . . . . . . 5
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
8. Security Considerations . . . . . . . . . . . . . . . . . . . 6
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
10.1. Normative References . . . . . . . . . . . . . . . . . . 6
10.2. Informative References . . . . . . . . . . . . . . . . . 7
10.3. URIs . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
NAT64 [RFC6146] with DNS64 [RFC6147] is a widely-deployed mechanism
to provide IPv4 access on IPv6-only networks. In order to support
functions such as local validation of DNSSEC [RFC4033] responses,
464xlat [RFC6877], and local IPv4 address synthesis [RFC8305], the
host must be aware of the NAT64 prefix in use by the network. This
document specifies a Router Advertisement [RFC4861] option to
communicate the NAT64 prefix to hosts.
1.1. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119].
1.2. Terminology
Pref64: an IPv6 prefix used for IPv6 address synthesis [RFC6146];
RA Router Advertisement, a message used by IPv6 routers to advertise
their presence together with various link and Internet parameters
([RFC4861]);
PvD-aware host A host that supports the association of network
configuration information into PvDs and the use of these PvDs. Also
named PvD-aware node in [RFC7556].
Colitti, et al. Expires April 4, 2019 [Page 2]
Internet-Draft Discovering PREF64 in Router Advertisements October 2018
2. Why include the NAT64 prefix in Router Advertisements
Fate sharing: NAT64 requires a routing to be configured. IPv6
routing configuration requires receiving an IPv6 Router Advertisement
[RFC4861]. Compared to currently-deployed NAT64 prefix discovery
methods such as [RFC7050], including the NAT64 prefix in the Router
Advertisement minimizes the number of packets required to configure a
Show full document text