IETF Logo Mail Archive

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

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Mon, 16 March 2020 09:19 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
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 828F73A21A2 for <tsvwg@ietfa.amsl.com>; Mon, 16 Mar 2020 02:19:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 BNt33IZ5ppt3 for <tsvwg@ietfa.amsl.com>; Mon, 16 Mar 2020 02:19:18 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 07D063A21AA for <tsvwg@ietf.org>; Mon, 16 Mar 2020 02:19:17 -0700 (PDT)
Received: from GF-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id EAFCE1B00082; Mon, 16 Mar 2020 09:19:11 +0000 (GMT)
To: Eric Rescorla <ekr@rtfm.com>, David Schinazi <dschinazi.ietf@gmail.com>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>
References: <158279435525.6196.11790581771168846041.idtracker@ietfa.amsl.com> <3c7f9e3c-d4f6-b002-5e16-6611d654c8eb@erg.abdn.ac.uk> <CAPDSy+5e0HYhBJdQm-ZhBcqmqwKGkpaKU8t_9R2_P=nAOs9s2w@mail.gmail.com> <CABcZeBOdDU0zQ+ZNQqu1vDWxQuLUzGqi9MMXPDUs-izZEgVQsg@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <1f15faeb-dc6f-1402-db55-940666c9f913@erg.abdn.ac.uk>
Date: Mon, 16 Mar 2020 09:19:11 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.5.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOdDU0zQ+ZNQqu1vDWxQuLUzGqi9MMXPDUs-izZEgVQsg@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/I8rlE5qZSlQ9G2PlehvmjsirBHQ>
Subject: Re: [tsvwg] New Version of draft-ietf-tsvwg-transport-encrypt (12)
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: Mon, 16 Mar 2020 09:19:20 -0000

Catching-up just on the following: We could strongly agree that 
ossification is an impediment about which there has been a general 
growing awareness. I do not mind changing the words here at all:

On 13/03/2020 16:20, Eric Rescorla wrote:
> In the first passage, the use "in response to perceptions" creates
> the impression that ossification is just some people's opinion,
> whereas it seems to me that it is a commonly understood fact of


e.g.:

OLD:

       One motive to encrypt transport headers is in response to
       perceptions that the network has become ossified, since traffic
       inspecting middleboxes prevent new protocols and mechanisms from
       being deployed.

NEW:

       One motive to encrypt transport headers is in response to
       growing awareness of the implications of network ossification 
from traffic
       inspecting middleboxes that prevent new protocols and mechanisms from
       being deployed.

... or make a suggestion?

Gorry

v2.23.0 | Report a Bug | By Email