[OPSEC] TSVWG: 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Tue, 16 June 2020 10:57 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: opsec@ietfa.amsl.com
Delivered-To: opsec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9953A14F2 for <opsec@ietfa.amsl.com>; Tue, 16 Jun 2020 03:57:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level:
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=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 YLQSeN7OVf_X for <opsec@ietfa.amsl.com>; Tue, 16 Jun 2020 03:57:05 -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 25B483A14F4 for <opsec@ietf.org>; Tue, 16 Jun 2020 03:57:04 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 4E6FC1B001BF for <opsec@ietf.org>; Tue, 16 Jun 2020 11:57:00 +0100 (BST)
References: <338d2b89-ce85-9de9-3141-136ef98285fb@erg.abdn.ac.uk>
To: opsec@ietf.org
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Forwarded-Message-Id: <338d2b89-ce85-9de9-3141-136ef98285fb@erg.abdn.ac.uk>
Message-ID: <24bdd3f3-ce0d-555e-abe9-bf5d391f4cdb@erg.abdn.ac.uk>
Date: Tue, 16 Jun 2020 11:56:59 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <338d2b89-ce85-9de9-3141-136ef98285fb@erg.abdn.ac.uk>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsec/ko2dxPs13xRFeHtXwdig16vlhqc>
Subject: [OPSEC] TSVWG: 3rd WGLC (limited-scope): draft-ietf-tsvwg-transport-encrypt-15, closes 29 June 2020
X-BeenThere: opsec@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: opsec wg mailing list <opsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsec>, <mailto:opsec-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsec/>
List-Post: <mailto:opsec@ietf.org>
List-Help: <mailto:opsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsec>, <mailto:opsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Jun 2020 10:57:07 -0000

I'm sorry for this additional email, I have presented this within OPSEC 
when looking for material, and received great feedback. I am now trying 
to reach-out again to the people who contributed to our thinking behind 
the TSVWG transport encryption draft.

https://datatracker.ietf.org/doc/draft-ietf-tsvwg-transport-encrypt/

The document has now completed a WGLC as INFO based on the content being 
ready. But, some people have asserted the document should not be 
published, because they did not see support for publishing this type of 
document. So, I wanted to check-in whether people think a document on 
this topic should be published by TSVWG?

If you're able to comment to TSVWG (or tell us what we got wrong), we'd 
appreciate your inputs.

Gorry