Considerations on Application - Network Collaboration Using Path Signals
draft-arkko-iab-path-signals-collaboration-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jari Arkko , Ted Hardie , Tommy Pauly | ||
| Last updated | 2021-11-22 (Latest revision 2021-10-25) | ||
| Replaced by | draft-iab-path-signals-collaboration | ||
| RFC stream | Internet Architecture Board (IAB) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | IAB state | Replaced | |
| Consensus boilerplate | Unknown | ||
| IAB shepherd | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Encryption and other security mechanisms are on the rise on all layers of the stack, protecting user data and making network operations more secured. Further, encryption is also a tool to address ossification that has been observed over time. Separation of functions into layers and enforcement of layer boundaries based on encryption supports selected exposure to those entities that are addressed by a function on a certain layer. A clear separation supports innovation and also enables new opportunities for collaborative functions. RFC 8558 describes path signals as messages to or from on-path elements. This document states principles for designing mechanisms that use or provide path signals and calls for actions on specific valuable cases.
Authors
Jari Arkko
Ted Hardie
Tommy Pauly
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)