Skip to main content

TAPS Transport Discovery

Document Type Expired Internet-Draft (individual)
Expired & archived
Author Martin Duke
Last updated 2022-04-28 (Latest revision 2021-10-25)
RFC stream (None)
Intended RFC status (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:


The Transport Services architecture decouples applications from the protocol implementations that transport their data. While it is often straightforward to connect applications with transports that are present in the host operating system, providing a means of discovering user-installed implementations dramatically enlarges the use cases. This document discusses considerations for the design of a discovery mechanism and an example of such a design. Discussion of this work is encouraged to happen on the TAPS IETF mailing list or on the GitHub repository which contains the draft: discovery.


Martin Duke

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