PCP Working Group M. Boucadair
Internet-Draft France Telecom
Intended status: Informational R. Penno
Expires: November 17, 2013 Cisco
May 16, 2013
Analysis of Port Control Protocol (PCP) Failure Scenarios
draft-boucadair-pcp-failure-06
Abstract
This document identifies and analyzes several PCP failure scenarios.
Identifying these failure scenarios is useful to assess the
efficiency of the protocol and also to decide whether new PCP
extensions are needed.
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 November 17, 2013.
Copyright Notice
Copyright (c) 2013 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
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.
Boucadair & Penno Expires November 17, 2013 [Page 1]
Internet-Draft PCP Failure Scenarios May 2013
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. PCP Client Failure Scenarios . . . . . . . . . . . . . . . . 2
2.1. Change of the IP Address of The PCP Server . . . . . . . 2
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
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
4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 8
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
7.1. Normative References . . . . . . . . . . . . . . . . . . 8
7.2. Informative References . . . . . . . . . . . . . . . . . 8
Appendix A. PCP State Synchronization: Overview . . . . . . . . 9
Appendix B. GET/NEXT Operation . . . . . . . . . . . . . . . . . 9
B.1. OpCode Format . . . . . . . . . . . . . . . . . . . . . . 9
B.2. OpCode-Specific Result Code . . . . . . . . . . . . . . . 11
B.3. Ordering and Equality . . . . . . . . . . . . . . . . . . 11
B.4. NEXT Option . . . . . . . . . . . . . . . . . . . . . . . 11
B.5. GET/NEXT PCP Client Theory of Operation . . . . . . . . . 14
B.6. GET/NEXT PCP Server Theory of Operation . . . . . . . . . 14
B.7. Flow Examples . . . . . . . . . . . . . . . . . . . . . . 15
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 18
1. Introduction
This document discusses several failure scenarios that may occur when
deploying PCP [RFC6887].
2. PCP Client Failure Scenarios
2.1. Change of the IP Address of The PCP Server
When a new IP address is used to reach its PCP Server, the PCP Client
datatracker.ietf.org