Skip to main content

A Minimal Set of Transport Services for TAPS Systems

The information below is for an old version of the document.
Document Type
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
Authors Stein Gjessing , Michael Welzl
Last updated 2015-12-24 (Latest revision 2015-06-22)
Replaced by draft-ietf-taps-minset, draft-ietf-taps-minset, RFC 8923
RFC stream (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:


This draft will eventually recommend a minimal set of IETF Transport Services offered by end systems supporting TAPS, and give guidance on choosing among the available mechanisms and protocols. As a starting point for discussion, it currently only gives an overview of some ways to categorize the set of transport services in the first TAPS document (version 4: draft-ietf-taps-transports-04), assuming that the eventual minimal set of transport services will be based on a similar form of categorization.


Stein Gjessing
Michael Welzl

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