DTCP: Dynamic Tasking Control Protocol

Document Type Expired Internet-Draft (individual)
Last updated 2017-12-29 (latest revision 2017-06-27)
Replaces draft-cavuto-dtcp
Stream ISE
Intended RFC status Informational
Expired & archived
plain text pdf html bibtex
Stream ISE state In ISE Review
Revised I-D Needed
Consensus Boilerplate Unknown
Document shepherd No shepherd assigned
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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.


Sumit kala (sumitk@juniper.net)
David Cavuto (cavuto@att.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)