Path signals
draft-hardie-path-signals-00

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2017-05-01 (latest revision 2016-10-28)
Replaced by draft-iab-path-signals
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Additional URLs
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-hardie-path-signals-00.txt

Abstract

TCP's state mechanics uses a series of well-known messages that are exchanged in the clear. Because these are visible to network elements on the path between the two nodes setting up the transport connection, they are often used as signals by those network elements. In transports that do not exchange these messages in the clear, on- path network elements lack those signals. This document discusses the nature of the signals as they are seen by on-path elements and reflects on best practices for transports which encrypt their state mechanics.

Authors

Ted Hardie (ted.ietf@gmail.com)

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