A Minimal Set of Transport Services for TAPS Systems
draft-gjessing-taps-minset-05
| Document | Type |
Replaced Internet-Draft
(taps WG)
Expired & archived
|
|
|---|---|---|---|
| Authors | Stein Gjessing , Michael Welzl | ||
| Last updated | 2017-10-18 (Latest revision 2017-06-20) | ||
| Replaced by | draft-ietf-taps-minset | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | Adopted by a WG | |
| Document shepherd | (None) | ||
| IESG | IESG state | Replaced by draft-ietf-taps-minset | |
| Consensus boilerplate | Unknown | ||
| 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:
Abstract
This draft recommends a minimal set of IETF Transport Services offered by end systems supporting TAPS, and gives guidance on choosing among the available mechanisms and protocols. It is based on the set of transport features given in the TAPS document draft-ietf-taps-transports-usage-05.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)