Retrieving the Capabilities of a PCP-controlled Device
draft-boucadair-pcp-capability-02

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2013-05-30
Stream (None)
Intended RFC status (None)
Formats pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (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                                T. Reddy
Expires: December 01, 2013                                         Cisco
                                                            May 30, 2013

         Retrieving the Capabilities of a PCP-controlled Device
                   draft-boucadair-pcp-capability-02

Abstract

   This document extends Port Control Protocol (PCP) with the ability to
   retrieve the capabilities of PCP-controlled device: CAPABILITY
   Option.

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 December 01, 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

Boucadair & Reddy      Expires December 01, 2013                [Page 1]
Internet-Draft                 CAPABILITY                       May 2013

   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  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  CAPABILITY  . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  PCP Client/Server Behavior  . . . . . . . . . . . . . . . . .   3
   4.  Option Usage  . . . . . . . . . . . . . . . . . . . . . . . .   4
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   5
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   6
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   6
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   7

1.  Introduction

   This document extends the base PCP [RFC6887] with a new feature to
   discover the capabilities of a PCP-controlled device.  Retrieving the
   capabilities of a PCP-controlled device would allow to avoid error,
   provide a hint why some applications fails, help select the OpCode to
   issue, etc.

   This option can be elected to be defined as a new OpCode.

2.  CAPABILITY

   The CAPABILITY option (Code: TBA, Figure 1) is used by a PCP Server
   to indicate to a requesting PCP Client the capabilities it supports
   with regards to port forwarding operations.

   One single Capability option is conveyed in the same PCP response
   message even if several functions are co-located in the same PCP-
   controlled device (e.g., NAT44 and NAT64, NAT44 and ports set
   assignment capability, etc.).

   This option, when received from a PCP Server, is used by a PCP Client
   to constraint the content of its requests and therefore avoid errors.

       0                   1                   2                   3
       0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
      | CAPABILITY    |  Reserved     |            Length=16          |
      +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+

Boucadair & Reddy      Expires December 01, 2013                [Page 2]
Internet-Draft                 CAPABILITY                       May 2013

      |A|                           Capability                        |
      +-+                                                             |
      :                                                               :
Show full document text