RFC 7225: Discovering NAT64 IPv6 Prefixes Using the Port Control Protocol (PCP)
In plain English — editorial summary, not part of the RFC
This document defines a new Port Control Protocol (PCP) option to learn the IPv6 prefix(es) used by a PCP-controlled NAT64 device to build IPv4-converted IPv6 addresses. This option is needed for successful communications when IPv4 addresses are used in referrals.
Document record
- Document ID
- RFC7225
- Published
- May 2014
- Authors
- M. Boucadair
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 17
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7227Guidelines for Creating New DHCPv6 OptionsCurrent
May 2014
- RFC 7222Quality-of-Service Option for Proxy Mobile IPv6Current
May 2014
- RFC 7228Terminology for Constrained-Node NetworksCurrent
May 2014
- RFC 7220Description Option for the Port Control Protocol (PCP)Current
May 2014
- RFC 7219SEcure Neighbor Discovery (SEND) Source Address Validation Improvement (SAVI)Current
May 2014
- RFC 7217A Method for Generating Semantically Opaque Interface Identifiers with IPv6 Stateless Address Autoconfiguration (SLAAC)Current
April 2014
- RFC 7256Multicast Control Extensions for the Access Node Control Protocol (ANCP)Current
July 2014
- RFC 7283Handling Unknown DHCPv6 MessagesObsoleted
July 2014
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?