APIs To Expose SCONE Metadata to Applications
draft-eddy-scone-api-00
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|
|
|---|---|---|---|
| Authors | Wesley Eddy , Abhishek Tiwari , Alan Frindell | ||
| Last updated | 2025-05-07 (Latest revision 2024-11-03) | ||
| Replaces | draft-eddy-sconepro-api | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document describes API considerations to provide applications with network-supplied information about acceptable network flow rates. Since this information is expected to be signalled from the network within the stack below the application using the SCONE protocol (to be defined by the IETF), it needs to be made accessible to applications in order for them to pick proper video rates, or to otherwise confine the application behavior within network-defined limits.
Authors
Wesley Eddy
Abhishek Tiwari
Alan Frindell
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)