A Minimal Set of Transport Services for TAPS Systems
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|Stein Gjessing , Michael Welzl
|2015-12-24 (Latest revision 2015-06-22)
|draft-ietf-taps-minset, draft-ietf-taps-minset, RFC 8923
|(No stream defined)
|RFC Editor Note
|Send notices to
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.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)