PCP Deployment Models
draft-boucadair-pcp-deployment-cases-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-12-02
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: Informational                         December 02, 2013
Expires: June 5, 2014

                         PCP Deployment Models
                draft-boucadair-pcp-deployment-cases-01

Abstract

   This document lists a set of PCP deployment models.

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 June 5, 2014.

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

Boucadair                 Expires June 5, 2014                  [Page 1]
Internet-Draft            PCP Deployment Cases             December 2013

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Single Homed CPE Model: Local PCP Server  . . . . . . . . . .   2
   4.  Single Homed CPE Model: Multiple PCP Servers  . . . . . . . .   3
   5.  Hide PCP Servers Model  . . . . . . . . . . . . . . . . . . .   4
     5.1.  PCP Proxy Model . . . . . . . . . . . . . . . . . . . . .   4
     5.2.  HTTP-Triggered PCP Client Model . . . . . . . . . . . . .   5
   6.  Separated PCP Server & PCP-controlled Device Model  . . . . .   6
   7.  Cascaded PCP-controlled Nodes Model . . . . . . . . . . . . .   6
     7.1.  Single Homed CPE Model: PCP Proxy Model . . . . . . . . .   8
     7.2.  UPnP IGD-PCP Interworking Model . . . . . . . . . . . . .   8
   8.  Multi-Homed CPE Model: One Single PCP Server  . . . . . . . .   9
   9.  Multi-Homed CPE Model: Multiple PCP Servers . . . . . . . . .  10
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  10
   11. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  10
   12. Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .  10
   13. References  . . . . . . . . . . . . . . . . . . . . . . . . .  11
     13.1.  Normative References . . . . . . . . . . . . . . . . . .  11
     13.2.  Informative References . . . . . . . . . . . . . . . . .  11
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  11

1.  Introduction

   This document lists a set of PCP [RFC6887] deployment models.

2.  Terminology

   This document makes use of the following terms:

   o  PCP server denotes a functional element that receives and
      processes PCP requests from a PCP client.  A PCP server can be co-
      located with or be separated from the function (e.g., NAT,
      Firewall) it controls.  Refer to [RFC6887].
   o  PCP client denotes a PCP software instance responsible for issuing
      PCP requests to a PCP server.  Refer to [RFC6887].

3.  Single Homed CPE Model: Local PCP Server

   This model assumes PCP is enabled in the LAN side to control
   functions located in the CPE.  The PCP server is reachable with the
   IP address of the private-faced interface.

Boucadair                 Expires June 5, 2014                  [Page 2]
Internet-Draft            PCP Deployment Cases             December 2013
Show full document text