Re: [tsvwg] Rev 13 of : draft-ietf-tsvwg-transport-encrypt-13.txt

Eric Rescorla <ekr@rtfm.com> Sat, 21 March 2020 13:40 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6844E3A0C00 for <tsvwg@ietfa.amsl.com>; Sat, 21 Mar 2020 06:40:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eK3g3HmKVBHD for <tsvwg@ietfa.amsl.com>; Sat, 21 Mar 2020 06:40:04 -0700 (PDT)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BCFA3A0BFD for <tsvwg@ietf.org>; Sat, 21 Mar 2020 06:40:04 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id a2so9518050ljk.6 for <tsvwg@ietf.org>; Sat, 21 Mar 2020 06:40:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fMNREsPnA/ieCzeQ1ALEhKH9nA1PuCivfqt3qxdPl8k=; b=jplaz6yr1HPF/0zQhswKoqI6dEdQzmx0p1bkn/Nc7XyvcdPEmaWT3IynhTLdu8sgRg kg2WyHtu+WOKIzlzwvBjmG7b1ikLN4uDTPvjJbFfSC43EUn+QPF5FOxNrZy4D65ackiu Cv0D1L2kSiIlES1nXf/DLSpiU6m6Pp0gTjtCteVfFDF6HL7wwZYnUoVDULgep0lyRdFS P+X4iCa5kG9MwqqAGQGiVfno8gzEeWLeJ6DikdCUEaefc/bepFzJNSdeSgpCNHHWdcPN rmU6YEpHYK3W6t4zaVo/5Fvk12aXXU2aM+ZDXZRV6lBv8mdcASDepnuTL7ONUL48elTn umUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=fMNREsPnA/ieCzeQ1ALEhKH9nA1PuCivfqt3qxdPl8k=; b=PlRf64haONTYdhLRN+i4m4Fl/QDYi6Ywhpr7StsrDgLYoWSzz/9P1PzXFKxJIJjKw+ 0v5uDNYnoSuUk0odiQmmslPxx8QXOsg5iG0PBIlxLBhYfgSjasDruuu6+Yj9RU/T9Cs0 JUXltzG74FnVJjpQKunLEMNCcisQH1Mens/hLTFLxYA336lbqAgLUVkpq3yLnTLlpisr qBC+qv2SnBl8AdlAyNZzriVudVvZevjIXJgHNMZ2S1x2yUSqxHAdA/EZUQ7WC/K9J2gB pv9h/jCNWNoiFMV1u739wMzzrs7oLQbUxvZin0i0RUX8KKawCIdohCybTwrCG7JP9U6k ABRQ==
X-Gm-Message-State: ANhLgQ2UzH1rbF60brcnSo7T8xp1TDDrpBVAFSqiLHvw+H1/xWhIFfdf M7qzYgEpFiDwmMoYBNoP9uAuqPDhh9AC9Fpcnswi6VB3AbE=
X-Google-Smtp-Source: ADFU+vussnfM5JAyGKD8j5wmlopynoUCWOHFTtOFWUoohvBu+rmVMU1uGsd51WKxr8u8ZU5p1nLe+Kg1fcGNEaAtAvM=
X-Received: by 2002:a2e:780a:: with SMTP id t10mr150137ljc.83.1584798002181; Sat, 21 Mar 2020 06:40:02 -0700 (PDT)
MIME-Version: 1.0
References: <158478510771.22419.11787558217390691432@ietfa.amsl.com> <3D4BEB60-20BC-4BE5-B2E9-38C9B0FF025C@erg.abdn.ac.uk>
In-Reply-To: <3D4BEB60-20BC-4BE5-B2E9-38C9B0FF025C@erg.abdn.ac.uk>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sat, 21 Mar 2020 06:39:25 -0700
Message-ID: <CABcZeBN1N7R8kQa603p+U+HE2=qLnZ=fkYVw_S0buFDLqTHYYQ@mail.gmail.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: tsvwg IETF list <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f609f905a15d89b2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/KZEjG5KvqPfHIIbUVFzLEGkEMJs>
Subject: Re: [tsvwg] Rev 13 of : draft-ietf-tsvwg-transport-encrypt-13.txt
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 21 Mar 2020 13:40:07 -0000

I do not believe that this version of the document addresses my concerns.
The overall tonal issues remain unchanged.

-Ekr


On Sat, Mar 21, 2020 at 5:18 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
wrote:

> Thanks to all who provided comments on and off list, this document was
> improved by understanding the feedback. We worked with the document
> shepherd (David) to address the issues, and expect this revision is now in
> good shape to proceed.
>
> Gorry (as Co-Editor)
>
> Sent from my iPad
>
> > On 21 Mar 2020, at 10:07, internet-drafts@ietf.org 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           : Considerations around Transport Header
> Confidentiality, Network Operations, and the Evolution of Internet
> Transport Protocols
> >        Authors         : Godred Fairhurst
> >                          Colin Perkins
> >    Filename        : draft-ietf-tsvwg-transport-encrypt-13.txt
> >    Pages           : 50
> >    Date            : 2020-03-21
> >
> > Abstract:
> >   To protect user data and privacy, Internet transport protocols have
> >   supported payload encryption and authentication for some time.  Such
> >   encryption and authentication is now also starting to be applied to
> >   the transport protocol headers.  This helps avoid transport protocol
> >   ossification by middleboxes, while also protecting metadata about the
> >   communication.  Current operational practice in some networks inspect
> >   transport header information within the network, but this is no
> >   longer possible when those transport headers are encrypted.  This
> >   document discusses the possible impact when network traffic uses a
> >   protocol with an encrypted transport header.  It suggests issues to
> >   consider when designing new transport protocols or features.  These
> >   considerations arise from concerns such as network operations,
> >   prevention of network ossification, enabling transport protocol
> >   evolution and respect for user privacy.
> >
> >
> > 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-13
> >
> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-transport-encrypt-13
> >
> > A diff from the previous version is available at:
> > https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-transport-encrypt-13
> >
> >
> > 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/
> >
>
>