Re: [VoT] Notes: VoT BoF 22-July-2015 (@IETF93, Prague)

Karen O'Donoghue <> Tue, 04 August 2015 13:55 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 029531ACC83 for <>; Tue, 4 Aug 2015 06:55:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.402
X-Spam-Status: No, score=-1.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_BAD_LINEBREAK=0.5, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id GIvgRXs16REj for <>; Tue, 4 Aug 2015 06:55:42 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 33F081B3844 for <>; Tue, 4 Aug 2015 06:51:18 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id; Tue, 4 Aug 2015 13:51:15 +0000
Received: from ([]) by ([]) with mapi id 15.01.0225.018; Tue, 4 Aug 2015 13:51:15 +0000
From: Karen O'Donoghue <>
To: Steve Olshansky <>
Thread-Topic: [VoT] Notes: VoT BoF 22-July-2015 (@IETF93, Prague)
Thread-Index: AQHQzrOP4QkuhYTRVES4C9PXihEkJJ3729oA
Date: Tue, 4 Aug 2015 13:51:15 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
authentication-results: spf=none (sender IP is );
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: []
x-microsoft-exchange-diagnostics: 1; BY2PR0601MB1670; 5:D1A1RqTcEs8GVP4BLbYMsAUDfcB17jo35qsifHtV0vAj4aIo6QEeLCooo9tCv35wKaQcKgwaZRkzIhuMz+1/erx/xIqG1ZgCWM/dNcnRWQdRtD7QJ/ap+nJV7IxGaPHx0iB68D2O4zKdyOQIjjRBpg==; 24:gocbgPwn5pTBhrE47UXB9T8eAPhmtPuYFw2tL6XJa+zwfm5xcdI0V2xKtFr3RTtVi8x5j3e5gSBHRTcgS457tVFHQzZu/T3D1jMR2lCXFpk=; 20:62VCHYs1lIWv0RkQxJ63gdnj3T5a9sO5YRO4lqvjzoV5HzCMaLy0b6onW4VJKry9zQlkp2xwMio96IF3VIuPYg==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0601MB1670;
x-microsoft-antispam-prvs: <>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:BY2PR0601MB1670; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0601MB1670;
x-forefront-prvs: 0658BAF71F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(189002)(199003)(87936001)(5001830100001)(110136002)(5001960100002)(4001540100001)(2656002)(5001860100001)(97736004)(99286002)(86362001)(33656002)(2900100001)(81156007)(40100003)(105586002)(62966003)(36756003)(46102003)(101416001)(106356001)(106116001)(450100001)(76176999)(83716003)(50986999)(77156002)(122556002)(4001450100002)(99936001)(54356999)(68736005)(189998001)(230783001)(102836002)(66066001)(2950100001)(92566002)(5002640100001)(19580405001)(19580395003)(77096005)(5890100001)(15975445007)(64706001)(82746002)(104396002); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR0601MB1670;; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None ( does not designate permitted sender hosts)
Content-Type: multipart/mixed; boundary="_003_B336F219928D45F7AB2851E3AA7BEF75isocorg_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Aug 2015 13:51:15.1576 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0601MB1670
Archived-At: <>
Cc: "" <>
Subject: Re: [VoT] Notes: VoT BoF 22-July-2015 (@IETF93, Prague)
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Vectors of Trust discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 04 Aug 2015 13:55:45 -0000


My apologies… I was editing the draft notes, and our emails crossed in the ether… 

The big changes I made were correcting the actual attendance…
Attending: Leif Johansson, Steve Olshansky, Justin Richer, Robin Wilton, Karen 
O’Donoghue, Nat Sakimura, Wendy Seltzer, Stephanie Gedes, and Steve Moore
Remote: Jim Fenton and Colin Wallis 

And specifying the next steps at the end. The action items you specified below were 
not in the draft minutes and are not quite accurate. The issue tracker item is quite important,
and we were not pursuing formal liaison relationships until there was a working group to
liaise with (if it should come to that). 

Next Steps:

To wrap up the meeting, we discussed next steps for this work. They 
include the following: 

1. Justin will produce the next edition of the document. Comments 
can be sent either via pull requests on GitHub or to the mailing list 
( General discussion should take place on the mailing 

2. We need to ensure that we are tracking and properly addressing all 
issues raised. We need to ensure that we are clear and transparent in 
this effort especially as we try to coordinate with groups and 
individuals who are not as familiar with the IETF process and 
shorthand. We will use the existing GitHub issue tracker:
We need to ensure all existing issues get added to the tracker. 

3. We need to ensure coordination with other SDOs working in this 
space. A recurring question was where this work should take place. 
The IETF does not seem to have quite the right expertise, but it is not 
clear there is a better forum. In order to be successful, this work will 
require close coordination with a number of other SDOs engaged in 
related work. We need to ensure that there is coordination with those 
SDOs (like ISO and ITU-T) so that we can leverage their expertise in 
this work. If we end up establishing an IETF working group, there will 
probably be official liaisons established with these SDOs. Until then, it 
will be up to us to coordinate leveraging on our existing connections 
and relationships. 

I have attached my edited notes for reference. My apologies for the delay, but I
was on vacation and just didn’t get to it.