Re: [tsvwg] I-D Action: draft-ietf-tsvwg-transport-encrypt-04.txt

[Tom Herbert <[e-mail]>]

Hello,

I am still having a hard time believing that need for operators to
inspect and process transport layer information in ad hoc ways
remotely outweighs the need for users' security and privacy and to
impede protocol ossification. Regardless of the arguments in the
draft, I believe that the trend will be more use of encryption even in
the transport layer. Consequently, it would be nice if the draft had
more discussion about alternative means for network devices to get the
information about the transport layer that they need. In particular, I
still think possibility of using extension headers is far too easily
dismissed by the draft (please see my previous comments about that).

Tom

On Mon, Feb 18, 2019 at 12:38 PM <[e-mail]> wrote:
>
>
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Transport Area Working Group WG of the IETF.
>
>         Title           : The Impact of Transport Header Confidentiality on Network Operation and Evolution of the Internet
>         Authors         : Godred Fairhurst
>                           Colin Perkins
>         Filename        : draft-ietf-tsvwg-transport-encrypt-04.txt
>         Pages           : 43
>         Date            : 2019-02-18
>
> Abstract:
>    This document describes implications of applying end-to-end
>    encryption at the transport layer.  It identifies in-network uses of
>    transport layer header information.  It then reviews the implications
>    of developing end-to-end transport protocols that use authentication
>    to protect the integrity of transport information or encryption to
>    provide confidentiality of the transport protocol header and expected
>    implications of transport protocol design and network operation.
>    Since transport measurement and analysis of the impact of network
>    characteristics have been important to the design of current
>    transport protocols, it also considers the impact on transport and
>    application evolution.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-transport-encrypt/
>
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-tsvwg-transport-encrypt-04
> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-transport-encrypt-04
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-transport-encrypt-04
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>