Using PCP to update dynamic DNS
draft-deng-pcp-ddns-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-07-10
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
IETF conflict review conflict-review-deng-pcp-ddns
Additional URLs
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)
Internet Engineering Task Force                                   X.Deng             
Internet Draft                                               M.Boucadair     
Intended status: Informational                            France Telecom 
Expires: January 10, 2013                                         X.Wang 
                                                                    BUPT             
                                                            July 9, 2012 
                                     
                                     
                                     
                     Using PCP to update dynamic DNS 
                       draft-deng-pcp-ddns-01.txt 

Abstract 

    

  This document focuses on the problems encountered when using dynamic 
  DNS in address sharing contexts (e.g., DS-Lite, NAT64, A+P)during 
  IPv6 transition. Issues, possible solutions and preliminary  
  implementation and validation of one of the 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 January 10, 2013. 

Copyright Notice 

  Copyright (c) 2012 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 
  carefully, as they describe your rights and restrictions with respect 

 
Deng, et al.           Expires January 10, 2013               [Page 1] 

 
Internet-Draft            PCP DDNS updates                   July 2012 
 
 
  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. Problem statement ........................................... 2 
  2. Solution Space .............................................. 3 
     2.1. Locate a service port................................... 3 
     2.2. Detect the changes ..................................... 4 
  3. Implementation & Validation ................................. 7 
  4. References .................................................. 8 
     4.1. Normative References.................................... 8 
     4.2. Informative References.................................. 8 
  5. Authors' Addresses .......................................... 9 
   
1. Problem statement 

    

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

  When the network architecture evolves towards an IPv4 sharing 
  architecture during IPv6 transition, the DDNS Client will have to not 
  only inform the IP address updates if any, but also to notify the 
  changes of external port on which the service is listening, because a 
  well know port numbers, e.g. port 80 will no longer be available to 
  every web server. It will also require the ability to configuring 
  corresponding port forwarding on CGN devices, so that incoming 
  communications initiated from outside can be routed to the 
  appropriate server behind the CGN.  

  This document focuses on the problems encountered when using dynamic 
  DNS in address sharing contexts (e.g., DS-Lite, NAT64, A+P). Below 
  are listed the main challenges to us:  

 
 
Deng, et al.           Expires January 10, 2013               [Page 2] 

 
Internet-Draft            PCP DDNS updates                   July 2012 
 
 
  (1) 
     The DDNS service MUST be able to maintain an alternative port 
Show full document text