DTCP: Dynamic Tasking Control Protocol
draft-kala-dtcp-00

Document Type Active Internet-Draft (individual)
Last updated 2016-11-24 (latest revision 2016-11-23)
Replaces draft-cavuto-dtcp
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html 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)
IP Performance Metrics Group                                 Sumit. Kala
Internet-Draft                                          Juniper Networks
Intended status: Standards Track                           David. Cavuto
Expires: May 27, 2017                                                ATT
                                                       November 23, 2016

                 DTCP: Dynamic Tasking Control Protocol
                           draft-kala-dtcp-00

Abstract

   Dynamic Tasking Control Protocol is a message-based interface by
   which an authorized client may connect to a server -- usually a
   network element (NE) or security policy enforcement point (PEP) --
   and issue dynamic requests for data.  These tasking requests contain,
   among other parameters, packet matching criteria that may apply to
   certain packets flowing through that network element.  The primary
   intent of the tasking request is to instruct that network element to
   send copies of packets matching those criteria to a destination
   (usually via tunneling) for further inspection or other action.  The
   protocol contains a security architecture to address client or server
   spoofing as well as replay prevention.  The protocol assumes that
   multiple clients may simultaneously control a single server.

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 May 27, 2017.

Copyright Notice

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

Kala & Cavuto             Expires May 27, 2017                  [Page 1]
Internet-Draft                    DTCP:                    November 2016

   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
     1.1.  Operational Modes . . . . . . . . . . . . . . . . . . . .   4
     1.2.  Performance Considerations  . . . . . . . . . . . . . . .   5
     1.3.  Conventions used in this document . . . . . . . . . . . .   5
   2.  Definitions . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.1.  Server  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     2.2.  Client  . . . . . . . . . . . . . . . . . . . . . . . . .   6
     2.3.  Control Source  . . . . . . . . . . . . . . . . . . . . .   6
     2.4.  Content Destination . . . . . . . . . . . . . . . . . . .   6
     2.5.  Criteria  . . . . . . . . . . . . . . . . . . . . . . . .   6
   3.  Overview of Operation . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Request-Response Paradigm . . . . . . . . . . . . . . . .   6
     3.2.  Asynchronous Notifications  . . . . . . . . . . . . . . .   8
     3.3.  Data Delivery Mechanism . . . . . . . . . . . . . . . . .   9
   4.  Security Model  . . . . . . . . . . . . . . . . . . . . . . .   9
     4.1.  No Information Exposure . . . . . . . . . . . . . . . . .   9
     4.2.  Independence of Control Sources . . . . . . . . . . . . .  10
     4.3.  Control Source to Content Destination Access Control  . .  10
     4.4.  Per-Message Security Mechanisms . . . . . . . . . . . . .  10
       4.4.1.  Sequence Number . . . . . . . . . . . . . . . . . . .  10
         4.4.1.1.  Sequence Number Negative Window . . . . . . . . .  11
       4.4.2.  Hashing Message Authentication Code (HMAC)  . . . . .  12
   5.  Application-Layer Message Formats . . . . . . . . . . . . . .  13
     5.1.  Request General Format  . . . . . . . . . . . . . . . . .  14
     5.2.  Response General Format . . . . . . . . . . . . . . . . .  14
     5.3.  Notification General Format . . . . . . . . . . . . . . .  15
     5.4.  Add Request . . . . . . . . . . . . . . . . . . . . . . .  15
Show full document text