TSVWG and QUIC WG, We completed updates to CIDFI for host-to-network and network-to-host signaling. Clients can learn network constraints (such as suggested bandwidth for streaming media), without any server support -- useful for streaming media.
With optional CIDFI server support, individual packets can receive differentiated service within a UDP 4-tuple based -- useful with unreliable QUIC. The mapping of the QUIC CID(s) to their metadata is communicated to the access network(s) by the client. CIDFI does not add a tunnel or encryption layer to the data between the QUIC client and server. Reviews and feedback are welcomed. -Dan, Tirumaleswar, and Mohamed ----- Name: draft-wing-cidfi Revision: 04 Title: Framework for CID Flow Indicator (CIDFI) Date: 2023-12-15 Group: Individual Submission Pages: 41 URL: https://www.ietf.org/archive/id/draft-wing-cidfi-04.txt Status: https://datatracker.ietf.org/doc/draft-wing-cidfi/ HTML: https://www.ietf.org/archive/id/draft-wing-cidfi-04.html HTMLized: https://datatracker.ietf.org/doc/html/draft-wing-cidfi Diff: https://author-tools.ietf.org/iddiff?url2=draft-wing-cidfi-04 Abstract: Host-to-network signaling and network-to-host signaling can improve the user experience to adapt to network's constraints and share expected application needs, and thus to provide differentiated service to a flow and to packets within a flow. The differentiated service may be provided at the network (e.g., packet prioritization), the server (e.g., adaptive transmission), or both. This document describes how clients can communicate with their nearby network elements so they can learn network constraints. Optionally, with QUIC server support their incoming QUIC packets can be mapped to metadata about their contents so packet importance can influence both intentional and reactive management policies. The framework handles both directions of a flow.
