RFC 7393: Using the Port Control Protocol (PCP) to Update Dynamic DNS

In plain English — editorial summary, not part of the RFC

This document focuses on the problems encountered when using dynamic DNS in address-sharing contexts (e.g., Dual-Stack Lite (DS-Lite) and Network Address and Protocol Translation from IPv6 Clients to IPv4 Servers (NAT64)) during IPv6 transition. Both issues and possible solutions are documented in this memo.

Document record

Document ID

RFC7393

Published

November 2014

Authors

X. Deng; M. Boucadair; Q. Zhao; J. Huang; C. Zhou

Status

INFORMATIONAL

Stream

INDEPENDENT

Area

—

Pages

14

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7393

Topics

• address sharing
• CGN
• service continuity
• service availability
• user-generated content
• address-sharing issues
• DS-Lite
• service delivery in CGN contexts

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7857Updates to Network Address Translation (NAT) Behavioral RequirementsCurrent

  April 2016

• RFC 7021Assessing the Impact of Carrier-Grade NAT on Network ApplicationsCurrent

  September 2013

• RFC 7785Recommendations for Prefix Binding in the Context of Softwire Dual-Stack LiteCurrent

  February 2016

• RFC 7596Lightweight 4over6: An Extension to the Dual-Stack Lite ArchitectureCurrent

  July 2015

• RFC 7648Port Control Protocol (PCP) Proxy FunctionCurrent

  September 2015

• RFC 8045RADIUS Extensions for IP Port Configuration and ReportingCurrent

  January 2017

• RFC 8114Delivery of IPv4 Multicast Services to IPv4 Clients over an IPv6 Multicast NetworkCurrent

  March 2017

• RFC 8513A YANG Data Model for Dual-Stack Lite (DS-Lite)Current

  January 2019

Also filed under

• INFORMATIONAL
• 2014
• INDEPENDENT stream