datatracker.ietf.org
Sign in
Version 5.6.3.p2, 2014-09-29
Report a bug

Using Port Control Protocol (PCP) to update dynamic DNS
draft-deng-pcp-ddns-06

Document type: Active Internet-Draft (individual)
Document stream: ISE
Last updated: 2014-09-22 (latest revision 2014-06-11)
Intended RFC status: Informational
Other versions: plain text, xml, pdf, html
IETF Conflict Review: conflict-review-deng-pcp-ddns

ISE State: Sent to the RFC Editor
Document shepherd: Nevil Brownlee
Shepherd Write-Up: Last changed 2014-09-01

IESG State: I-D Exists
IANA Review State: IANA OK - No Actions Needed
IANA Action State: No IC
RFC Editor State: EDIT
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                            X. Deng
Internet-Draft
Intended status: Informational                              M. Boucadair
Expires: December 13, 2014                                France Telecom
                                                                 Q. Zhao
                      Beijing University of Posts and Telecommunications
                                                                J. Huang
                                                                 C. Zhou
                                                     Huawei Technologies
                                                           June 11, 2014

        Using Port Control Protocol (PCP) to update dynamic DNS
                         draft-deng-pcp-ddns-06

Abstract

   This document focuses on the problems encountered when using dynamic
   DNS in address sharing contexts (e.g., DS-Lite, NAT64) during IPv6
   transition.  Both issues and possible solutions are documented in
   this memo.

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 http://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 December 13, 2014.

Copyright Notice

   Copyright (c) 2014 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
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents

Deng, et al.            Expires December 13, 2014               [Page 1]
Internet-Draft              PCP DDNS updates                   June 2014

   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.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Problem Statement . . . . . . . . . . . . . . . . . . . .   2
     1.2.  Scope and Goals . . . . . . . . . . . . . . . . . . . . .   3
   2.  Solution Space  . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Locate a Service Port . . . . . . . . . . . . . . . . . .   4
     2.2.  Create Explicit Mappings for Incoming Connections . . . .   5
     2.3.  Detect Changes  . . . . . . . . . . . . . . . . . . . . .   5
   3.  Some Deployment Solutions . . . . . . . . . . . . . . . . . .   6
     3.1.  Reference Topology  . . . . . . . . . . . . . . . . . . .   6
     3.2.  For Web Service . . . . . . . . . . . . . . . . . . . . .   7
     3.3.  For Non-web Service . . . . . . . . . . . . . . . . . . .   8
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .  10
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   6.  Contributors  . . . . . . . . . . . . . . . . . . . . . . . .  11
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  11
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .  11
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  11
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  12

1.  Introduction

1.1.  Problem Statement

   Dynamic DNS (DDNS) is a widely deployed service to facilitate hosting
   servers (e.g., access to a webcam, HTTP server, FTP server, etc.) at
   customers' premises.  There are a number of providers which offer a
   DDNS service, working in a client and server mode, which mostly use a
   web-form based communication.  DDNS clients are generally implemented
   in the user's router or computer, which once detects changes to its
   assigned IP address it automatically sends an update message to the
   DDNS server.  The communication between the DDNS client and the DDNS
   server is not standardized, varying from one provider to another,
   although a few standard web-based methods of updating emerged over
   time.

   When the network architecture evolves towards an IPv4 sharing

[include full document text]