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

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-02-15
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                                R. Penno
Expires: August 19, 2013                                           Cisco
                                                       February 15, 2013

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

Abstract

   This document identifies and analyzes several PCP failure scenarios.
   Identifying these failure scenarios are useful to assess the
   efficiency of the protocol and also to decide whether new extensions
   are needed to the base PCP.

   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 August 19, 2013.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Boucadair & Penno        Expires August 19, 2013                [Page 1]
Internet-Draft            PCP Failure Scenarios            February 2013

   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
   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 Client 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  . . . . . . . . . . . .  5
     2.5.  Change of the CPE WAN IP Address . . . . . . . . . . . . .  5
     2.6.  UPnP IGD/PCP IWF . . . . . . . . . . . . . . . . . . . . .  6
   3.  Restart or Failure of the PCP Server . . . . . . . . . . . . .  6
     3.1.  Basic Rule . . . . . . . . . . . . . . . . . . . . . . . .  6
     3.2.  Clear PCP Mappings . . . . . . . . . . . . . . . . . . . .  7
     3.3.  State Redundancy is Enabled  . . . . . . . . . . . . . . .  7
     3.4.  Cold-Standby without State Redundancy  . . . . . . . . . .  7
     3.5.  Anycast Redundancy Mode  . . . . . . . . . . . . . . . . .  7
     3.6.  Mapping Repair Procedure . . . . . . . . . . . . . . . . .  7
       3.6.1.  PCP Client Behaviour . . . . . . . . . . . . . . . . .  7
       3.6.2.  PCP Proxy Behaviour  . . . . . . . . . . . . . . . . .  8
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  8
   6.  Acknowledgements . . . . . . . . . . . . . . . . . . . . . . .  9
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  9
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  9
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  9
   Appendix A.  PCP State Synchronization: Overview . . . . . . . . . 10
   Appendix B.  GET/NEXT Operation  . . . . . . . . . . . . . . . . . 10
     B.1.  OpCode Format  . . . . . . . . . . . . . . . . . . . . . . 10
     B.2.  OpCode-Specific Result Code  . . . . . . . . . . . . . . . 12
     B.3.  Ordering and Equality  . . . . . . . . . . . . . . . . . . 12
Show full document text