Guidelines for Racing During Connection Establishment
draft-pauly-taps-guidelines-01

Document Type Expired Internet-Draft (individual)
Last updated 2018-04-27 (latest revision 2017-10-24)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
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
https://www.ietf.org/archive/id/draft-pauly-taps-guidelines-01.txt

Abstract

Often, connections created across the Internet have multiple options of how to communicate: address families, specific IP addresses, network attachments, and application and transport protocols. This document describes how an implementation can race multiple options during connection establishment, and expose this functionality through an API.

Authors

Tommy Pauly (tpauly@apple.com)

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