Port Control Protocol (PCP) Failure Scenarios
draft-boucadair-pcp-failure-04

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2012-08-20
Stream (None)
Intended RFC status (None)
Formats plain text pdf html
Stream Stream state (No stream defined)
Document shepherd None
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
PCP Working Group                                           M. Boucadair
Internet-Draft                                            France Telecom
Intended status: Standards Track                               F. Dupont
Expires: February 21, 2013                   Internet Systems Consortium
                                                                R. Penno
                                                                   Cisco
                                                         August 20, 2012

             Port Control Protocol (PCP) Failure Scenarios
                     draft-boucadair-pcp-failure-04

Abstract

   This document identifies and analyzes several PCP failure scenarios.
   A procedure to retrieve the explicit dynamic mapping(s) from the PCP
   Server is proposed.  This procedure relies upon the use of a new PCP
   OpCode and Option: GET/NEXT.

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].

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 February 21, 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

Boucadair, et al.       Expires February 21, 2013               [Page 1]
Internet-Draft            PCP Failure Scenarios              August 2012

   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
   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 . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  PCP Failure Scenarios  . . . . . . . . . . . . . . . . . . . .  3
     2.1.  Change of the IP Address of The PCP Server . . . . . . . .  3
     2.2.  Application Crash  . . . . . . . . . . . . . . . . . . . .  3
     2.3.  PCP Client Crash . . . . . . . . . . . . . . . . . . . . .  4
     2.4.  Change of the Internal IP Address  . . . . . . . . . . . .  4
     2.5.  Change of the CPE WAN IP Address . . . . . . . . . . . . .  5
     2.6.  UPnP IGD/PCP IWF . . . . . . . . . . . . . . . . . . . . .  6
     2.7.  Restart or Failure of the PCP Server . . . . . . . . . . .  6
       2.7.1.  Basic Rule . . . . . . . . . . . . . . . . . . . . . .  6
       2.7.2.  Clear PCP Mappings . . . . . . . . . . . . . . . . . .  6
       2.7.3.  State Redundancy is Enabled  . . . . . . . . . . . . .  7
       2.7.4.  Cold-Standby without State Redundancy  . . . . . . . .  7
       2.7.5.  Anycast Redundancy Mode  . . . . . . . . . . . . . . .  7
       2.7.6.  Mapping Repair Procedure . . . . . . . . . . . . . . .  7
   3.  PCP State Synchronization: Overview  . . . . . . . . . . . . .  8
   4.  GET/NEXT Operation . . . . . . . . . . . . . . . . . . . . . .  8
     4.1.  OpCode Format  . . . . . . . . . . . . . . . . . . . . . .  9
     4.2.  OpCode-Specific Result Code  . . . . . . . . . . . . . . . 10
     4.3.  Ordering and Equality  . . . . . . . . . . . . . . . . . . 10
     4.4.  NEXT Option  . . . . . . . . . . . . . . . . . . . . . . . 11
     4.5.  GET/NEXT PCP Client Theory of Operation  . . . . . . . . . 14
     4.6.  GET/NEXT PCP Server Theory of Operation  . . . . . . . . . 14
   5.  Flow Examples  . . . . . . . . . . . . . . . . . . . . . . . . 15
   6.  Security Considerations  . . . . . . . . . . . . . . . . . . . 19
   7.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 20
   8.  References . . . . . . . . . . . . . . . . . . . . . . . . . . 20
     8.1.  Normative References . . . . . . . . . . . . . . . . . . . 20
Show full document text