Re: [tsvwg] Connection Identifier Flow Indicator (CIDFI)

On Thu, Aug 17, 2023, 10:45 AM Dan Wing <[email protected]> wrote:

> Reply-To: [email protected]
>
> We have a new proposal for using Connection Identifiers to signal
> host-to-network and network-to-host.  The CIDs can be QUIC CIDs or DTLS
> CIDs.
>

> The CIDFI proposal has commonality with the I-D's in the CC line, most of
> which were presented at IETF117 in TSVAREA, QUIC, DISCUSS, and V6OPS.
> CIDFI takes a different approach.  CIDFI does not use UDP trailers, allows
> the client and server to choose their Connection IDs however they wish,
> works on IPv4 and IPv6 (including through NATs and IPv6/IPv4 translators),
> and avoids the network operator's equipment connecting to the content
> server (which would identify the server to the network operator).
>

Hi Dan,

Thanks for the draft. Offhand it looks this solution provides signaling
specifically for QUIC. Is there a route here for a general solution that
could be used across different transport protocols or applications (TCP,
SCTP, RTP, custom app protocols in UDP, etc.)? Could the host to network
signaling part be a use case of FAST (draft-herbert-fast-06)?

Tom


> Abstract:
>
>   This document describes how clients and servers can cooperate with
>   network elements so their QUIC and DTLS streams can be augmented with
>   information about network conditions and packet importance.
>
> As Matt's SADCDN was DISPATCH'd to ART area, I set reply-to to
> [email protected]
>
> editor's copy, https://danwing.github.io/cidfi/draft-wing-cidfi.html
> published -00,  https://www.ietf.org/archive/id/draft-wing-cidfi-00.html
>
> -d
>
>

_______________________________________________
art mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/art