IETF Logo Mail Archive

[VoT] Clause 7 edgy on scope? (RE: Vectors of Trust I-D)

Colin Wallis <Colin.Wallis@dia.govt.nz> Mon, 29 June 2015 23:14 UTC

Return-Path: <Colin.Wallis@dia.govt.nz>
X-Original-To: vot@ietfa.amsl.com
Delivered-To: vot@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 817901B2F8A for <vot@ietfa.amsl.com>; Mon, 29 Jun 2015 16:14:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.383
X-Spam-Level: *
X-Spam-Status: No, score=1.383 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HELO_EQ_BIZ=0.288, HTML_MESSAGE=0.001, MSGID_FROM_MTA_HEADER=0.001, RCVD_IN_DNSWL_LOW=-0.7, RELAY_IS_203=0.994, SPF_HELO_PASS=-0.001] autolearn=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 JEcM-3xinesC for <vot@ietfa.amsl.com>; Mon, 29 Jun 2015 16:14:07 -0700 (PDT)
Received: from mx1.securemx.biz (mx1.securemx.biz [203.84.134.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 779E01B2F0A for <vot@ietf.org>; Mon, 29 Jun 2015 16:14:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=nz.smxemail.com; s=alpha; c=relaxed/relaxed; q=dns/txt; i=@nz.smxemail.com; t=1435619645; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc; bh=epT8IvfaodrDOful8std/FKQOxdU/xoeG8CQj9SI68s=; b=twLjwPBjmTRGvupVuioSlKV9D3qk4r9aEIVTRb7MfQg0XMPrJ76hhi7/OCP5aer6 C7WVBmvlFKBoy63TN5hoeKBU7ejYaEVjKKcnNHnSvpciHl7dvZGwThodxFLociDe nSgwnhjWR7HLMDi9dEZE7QI9OPvks7YLzQomhqiti/E=;
Received: from s111-0006-lnv01 ([131.203.48.73]) by omr.nz.smxemail.com with ESMTP (using TLSv1 with cipher AES256-SHA (256/256 bits)) id 5591D13D-28250DEE@mta1101.omr; Mon, 29 Jun 2015 23:14:05 +0000
MIME-Version: 1.0
Message-ID: <147EE18440E5AF44834B220ED35BA530014AB1AEC1@WLGPRDMBX02.dia.govt.nz>
X-MessageIsInfected: false
Received: from 161-65-142-21.ip.fx.net.nz (EHLO WLGPRDMM01.dia.govt.nz) ([161.65.142.21]) by s111-0006-lnv01 (JAMES SMTP Server ) with ESMTP ID 1872100071; Tue, 30 Jun 2015 11:14:02 +1200 (NZST)
Received: from WLGPRDCAS01.dia.govt.nz (Not Verified[172.29.0.93]) by WLGPRDMM01.dia.govt.nz with MailMarshal (v7, 1, 1, 5205) (using TLS: SSLv23) id <B5591d13a0000>; Tue, 30 Jun 2015 11:14:02 +1200
Received: from WLGPRDMBX02.dia.govt.nz ([fe80::d51f:14cf:8162:8a0b]) by WLGPRDCAS01.dia.govt.nz ([172.29.0.93]) with mapi id 14.03.0235.001; Tue, 30 Jun 2015 11:14:02 +1200
From: Colin Wallis <Colin.Wallis@dia.govt.nz>
To: 'Justin Richer' <jricher@MIT.EDU>, "vot@ietf.org" <vot@ietf.org>
Thread-Topic: Clause 7 edgy on scope? (RE: [VoT] Vectors of Trust I-D)
Thread-Index: AdCywAdxGV06rU/8R4OLexR95fMGDA==
Date: Mon, 29 Jun 2015 23:14:02 +0000
Accept-Language: en-US, en-NZ
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailadviser: Confirmation not required
x-originating-ip: [172.29.0.162]
Content-Type: multipart/alternative; boundary="_000_147EE18440E5AF44834B220ED35BA530014AB1AEC1WLGPRDMBX02di_"
Archived-At: <http://mailarchive.ietf.org/arch/msg/vot/RIBx7D95ckEqG2NYPgXb-kvZoI8>
Subject: [VoT] Clause 7 edgy on scope? (RE: Vectors of Trust I-D)
X-BeenThere: vot@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Vectors of Trust discussion list <vot.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vot>, <mailto:vot-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/vot/>
List-Post: <mailto:vot@ietf.org>
List-Help: <mailto:vot-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vot>, <mailto:vot-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 29 Jun 2015 23:14:09 -0000

Many thanks Justin and Leif

I’ve done a first pass/light read, and from that, I think it is a terrific first cut that gets us on the path to normalizing the discussions over the past 9 months.

Aside from a few tidy ups, I just have this slight concern whether all of Clause 7 (Discovery and Verification) is in scope for normative text?
I certainly appreciate that in most implementations and deployments, there would be a dependency on an operational trust framework and trustmark.
But is it too big a stretch to make that normative for this work?
Just a thought.. and more than happy to be proven wrong.. ☺.

Cheers
Colin


From: vot [mailto:vot-bounces@ietf.org] On Behalf Of Justin Richer
Sent: Saturday, 27 June 2015 3:15 p.m.
To: vot@ietf.org
Subject: [VoT] Vectors of Trust I-D

Hi Everyone,

I have taken the initial strawman proposal along with a substantial number of edits and inputs from several folks and have created an initial I-D of the document:

https://tools.ietf.org/id/draft-richer-vectors-of-trust-00

It’s still a very drafty draft, but hopefully it’s starting to make this a concrete thing. Please read it over and discuss it here on the list.

I would like to propose a bar-BoF in Prague for VoT for anyone who would like to discuss this. If you’re interested (and will be there in person), let me know!

 — Justin

v2.23.0 | Report a Bug | By Email