Search RFCs

RFC Editor

File formats:

Status:

INFORMATIONAL

Author:

T. Hardie, Ed.

Stream:

IAB

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC8558

Discuss this RFC: Send questions or comments to the mailing listiab@iab.org

Other actions:View Errata  | Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 8558

Abstract

This document discusses the nature of signals seen by on-pathelements examining transport protocols, contrasting implicit andexplicit signals. For example, TCP's state machine uses a series ofwell-known messages that are exchanged in the clear. Because theseare visible to network elements on the path between the two nodessetting up the transport connection, they are often used as signalsby those network elements. In transports that do not exchange thesemessages in the clear, on-path network elements lack those signals.Often, the removal of those signals is intended by those moving themessages to confidential channels. Where the endpoints desire thatnetwork elements along the path receive these signals, this documentrecommends explicit signals be used.

For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.