APIs To Expose SCONEPRO Metadata to Applications
draft-eddy-sconepro-api-03
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Wesley Eddy , Abhishek Tiwari , Alan Frindell | ||
| Last updated | 2024-07-05 | ||
| Replaced by | draft-eddy-scone-api | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Replaced by draft-eddy-scone-api | |
| 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 SCONEPRO 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.)