Re: Network Tokens and WebRTC QoS (#13)

The IETF created the relevant mailing list June 20 (TSV area). Not much
traffic yet.
There's no BOF scheduled for virtual Madrid (end of July).

Apparently there has been some discussion on the IETF TLS mailing list, but
nothing that looks like adoption.

The IETF has a long history of having "mark the outside of the secured
envelope" proposals go down in flames (some people will remember the PLUS
BOF of a few years back); this is not an area where I would bet on fast
adoption of any proposal.

Harald

On Thu, Jul 2, 2020 at 10:48 AM Dominique Hazael-Massieux <dom@w3.org>
wrote:

> The following was posted recently on one of the WebRTC repository,
> highlighting some possible new work at IETF on "an open and secure
> method for end users and application providers to coordinate with the
> network about how their traffic is treated ( e.g., to access a 5G slice,
> a firewall whitelist, a zero-rating, or a QoS service )"
>   https://networktokens.org
>
> This sounds potentially very relevant to our group's explorations - has
> anyone more insights on this, or contacts with relevant people?
>
> Dom
>
>
> -------- Message transféré --------
> Sujet : [webrtc-priority] Network Tokens and WebRTC QoS (#13)
> Date de renvoi : Mon, 29 Jun 2020 22:14:21 +0000
> De (renvoi) : public-webrtc@w3.org
> Date : Mon, 29 Jun 2020 22:14:18 +0000
> De : Yiannis via GitHub <sysbot+gh@w3.org>
> Pour : public-webrtc@w3.org
>
> yiannisy has just created a new issue for
> https://github.com/w3c/webrtc-priority:
>
> == Network Tokens and WebRTC QoS ==
> Hi,
>
> Not sure if this is the right place, but wanted to bring into your
> attention network tokens (https://networktokens.org), a new project/IETF
> I-D that might be relevant with WebRTC and QoS.
> In a nutshell: Network tokens are an open and secure method for end
> users and application providers to coordinate with the network about how
> their traffic is treated ( e.g., to access a 5G slice, a firewall
> whitelist, a zero-rating, or a QoS service ). Network Tokens replace
> complex, insecure, and privacy-invasive DPI application signatures with
> a deterministic and unifiedmechanism to build network services, and
> complement DSCP codepoints acrossnetwork boundaries.
>
> We have a prototype implementation using network tokens as part of
> WebRTC, and I'd be very interested to understand what's the best way to
> engage withthe WebRTC group and get feedback/guidance on next steps.
>
> Please view or discuss this issue at
> https://github.com/w3c/webrtc-priority/issues/13 using your GitHub account
>
>
>