File formats:

Also available: XML file for editing

 

Status:

INFORMATIONAL

Authors:

J. Arkko
T. Hardie
T. Pauly
M. Kühlewind

Stream:

IAB

Cite this RFC: TXT  |  XML  |   BibTeX

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

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

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

Abstract

This document discusses principles for designing mechanisms that use or provide path signals and calls for standards action in specific valuable cases. RFC 8558 describes path signals as messages to or from on-path elements and points out that visible information will be used whether or not it is intended as a signal. The principles in this document are intended as guidance for the design of explicit path signals, which are encouraged to be authenticated and include a minimal set of parties to minimize information sharing. These principles can be achieved through mechanisms like encryption of information and establishing trust relationships between entities on a path.

For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 8729.