Re: [tsvwg] New Version of draft-ietf-tsvwg-transport-encrypt (12)

[Eric Rescorla <[e-mail]>]

On Mon, Mar 16, 2020 at 2:36 AM Gorry Fairhurst <[e-mail]>
wrote:

> Ekr,
> On 15/03/2020 13:19, Eric Rescorla wrote:
>
> Let me try to expand my point a bit.
>
> Longstanding practice is for entities in the middle of the network to
> use signals that were intended for the endpoint for their own
> purposes.  With QUIC (and a lesser extent SCTP/DTLS), those signals
> are being encrypted and thus unavailable to those non-endpoint
> entities; this draft is mostly devoted to documenting the negative
> impact of that change on the operations of those entities.
>
> I disagree that this is "documenting the negative impact of that change".
>
> The draft is about how this protocol information has and is being used. As
> long as I can remember, there has been devices that utilise some of this
> information, at the edge of an enterprise there is often at least one
> device with this role; within a managed network there are devices; etc. If
> the trend to use encrypted methods continues, some of these practices need
> to be re-assessed, and the functions more widely understood than in an era
> when nearly everything was thought to be TCP or "multimedia".
>

I'm not sure what you're arguing here. What I said above is that
this draft was "mostly devoted to documenting the negative
impact of that change on the operations of those entities."
In other words, it lists a bunch of things that people do now
that will stop working. Do you not think that much of the
material in this draft is of that form?

-Ekr