Port Control Protocol (PCP)
draft-ietf-pcp-base-27

The information below is for an old version of the document
Document Type Active Internet-Draft (pcp WG)
Last updated 2012-09-20
Replaces draft-wing-pcp-base
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Consensus Unknown
Document shepherd None
IESG IESG state IESG Evaluation::AD Followup
Telechat date
Needs 8 more YES or NO OBJECTION positions to pass.
Responsible AD Ralph Droms
IESG note Dave Thaler (dthaler@microsoft.com) is the document shepherd.
Send notices to pcp-chairs@tools.ietf.org, draft-ietf-pcp-base@tools.ietf.org
PCP working group                                           D. Wing, Ed.
Internet-Draft                                                     Cisco
Intended status: Standards Track                             S. Cheshire
Expires: March 24, 2013                                            Apple
                                                            M. Boucadair
                                                          France Telecom
                                                                R. Penno
                                                                   Cisco
                                                              P. Selkirk
                                                                     ISC
                                                      September 20, 2012

                      Port Control Protocol (PCP)
                         draft-ietf-pcp-base-27

Abstract

   The Port Control Protocol allows an IPv6 or IPv4 host to control how
   incoming IPv6 or IPv4 packets are translated and forwarded by a
   network address translator (NAT) or simple firewall, and also allows
   a host to optimize its outgoing NAT keepalive messages.

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 March 24, 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

Wing, et al.             Expires March 24, 2013                 [Page 1]
Internet-Draft         Port Control Protocol (PCP)        September 2012

   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  . . . . . . . . . . . . . . . . . . . . . . . .   5
   2.  Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.1.  Deployment Scenarios  . . . . . . . . . . . . . . . . . .   6
     2.2.  Supported Protocols . . . . . . . . . . . . . . . . . . .   6
     2.3.  Single-homed Customer Premises Network  . . . . . . . . .   6
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   7
   4.  Relationship between PCP Server and its NAT/firewall  . . . .  11
   5.  Note on Fixed-Size Addresses  . . . . . . . . . . . . . . . .  11
   6.  Protocol Design Note  . . . . . . . . . . . . . . . . . . . .  12
   7.  Common Request and Response Header Format . . . . . . . . . .  14
     7.1.  Request Header  . . . . . . . . . . . . . . . . . . . . .  15
     7.2.  Response Header . . . . . . . . . . . . . . . . . . . . .  16
     7.3.  Options . . . . . . . . . . . . . . . . . . . . . . . . .  17
     7.4.  Result Codes  . . . . . . . . . . . . . . . . . . . . . .  20
   8.  General PCP Operation . . . . . . . . . . . . . . . . . . . .  21
     8.1.  General PCP Client: Generating a Request  . . . . . . . .  22
       8.1.1.  PCP Client Retransmission . . . . . . . . . . . . . .  23
     8.2.  General PCP Server: Processing a Request  . . . . . . . .  25
     8.3.  General PCP Client: Processing a Response . . . . . . . .  27
     8.4.  Multi-Interface Issues  . . . . . . . . . . . . . . . . .  28
     8.5.  Epoch . . . . . . . . . . . . . . . . . . . . . . . . . .  28
   9.  Version Negotiation . . . . . . . . . . . . . . . . . . . . .  30
   10. Introduction to MAP and PEER Opcodes  . . . . . . . . . . . .  31
     10.1. For Operating a Server  . . . . . . . . . . . . . . . . .  33
     10.2. For Operating a Symmetric Client/Server . . . . . . . . .  36
     10.3. For Reducing NAT or Firewall Keepalive Messages . . . . .  38
     10.4. For Restoring Lost Implicit TCP Dynamic Mapping State . .  39
   11. MAP Opcode  . . . . . . . . . . . . . . . . . . . . . . . . .  40
     11.1. MAP Operation Packet Formats  . . . . . . . . . . . . . .  41
Show full document text