<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Title" content="">
<meta name="Keywords" content="">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:"Helvetica Neue";
panose-1:2 0 5 3 0 0 0 2 0 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body bgcolor="white" lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal">iGov, among many goals, will serve as a single interop baseline for cross-border federation. It can do that without VOT. What it can’t do, is carry an interoperable assertion of assurance in it’s payload WITHOUT VOT. So, since iGov is not
experimental, and needs VOT, I assert that VOT has graduated from experimental.<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Openid-specs-igov <openid-specs-igov-bounces@lists.openid.net> on behalf of "Phil Hunt (IDM) via Openid-specs-igov" <openid-specs-igov@lists.openid.net><br>
<b>Reply-To: </b>"Phil Hunt (IDM)" <phil.hunt@oracle.com><br>
<b>Date: </b>Monday, September 11, 2017 at 11:07 AM<br>
<b>To: </b>John Bradley <ve7jtb@ve7jtb.com><br>
<b>Cc: </b>"openid-specs-igov@lists.openid.net" <openid-specs-igov@lists.openid.net><br>
<b>Subject: </b>Re: [Openid-specs-igov] Fwd: Regarding the vote on Implementer’s Drafts of Two iGov Specifications<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The VoT spec is also experimental.<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal">Having a normative dependence on an experimental spec creates instability and devalues this spec. Or is the intent that igov be experimental?<o:p></o:p></p>
</div>
<div id="AppleMailSignature">
<p class="MsoNormal"><br>
Phil<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
On Sep 11, 2017, at 4:48 AM, John Bradley via Openid-specs-igov <<a href="mailto:openid-specs-igov@lists.openid.net">openid-specs-igov@lists.openid.net</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal">Forwarding a comment on the vote. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">It is not uncommon for OIDF implimentors drafts to have dependencies on ID. As it is not uncommon for IETF WG specs to reference other drafts. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Strictly speaking vot is a AD sponsors draft so not the same status as a Individual Draft. Yes the IETF has mysterious ways. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">To discuss the IETF process and that document the SAG list is best.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The iGov WG has had extensive conversations with NIST and the UK and included VOT at there request. NIST is working on a profile of VOT.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">People interested in the iGov discussion with NIST should join the WG. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">As document Sheppard I have been talking to NIST and others about there ability to profile VOT. Getting feedback on that is one of the reasons vot has not been progressed to the IESG yet. That will however happening soon, unless more
feedback is received in the IETF process. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Honestly the more feedback the better. Sometimes it takes specs referencing important work like VOT before people become aware of them. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">I don't think we have a issue with the iGov implimentors draft, but others can differ.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">John B. <o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal">---------- Forwarded message ----------<br>
From: "Prateek Mishra" <<a href="mailto:Prateek.Mishra@oracle.com">Prateek.Mishra@oracle.com</a>><br>
Date: Sep 11, 2017 00:44<br>
Subject: Fwd: Regarding the vote on Implementer’s Drafts of Two iGov Specifications<br>
To: "John Bradley" <<a href="mailto:ve7jtb@ve7jtb.com">ve7jtb@ve7jtb.com</a>>, "Phil Hunt (IDM)" <<a href="mailto:phil.hunt@oracle.com">phil.hunt@oracle.com</a>><br>
Cc: <br>
<br>
<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><br>
<br>
<o:p></o:p></p>
<blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<p class="MsoNormal">Begin forwarded message:<o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica Neue",sans-serif">From:
</span></b><span style="font-family:"Helvetica Neue",sans-serif">Prateek Mishra <<a href="mailto:Prateek.Mishra@oracle.com" target="_blank">Prateek.Mishra@oracle.com</a>></span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica Neue",sans-serif">Subject: Regarding the vote on Implementer’s Drafts of Two iGov Specifications</span></b><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica Neue",sans-serif">Date:
</span></b><span style="font-family:"Helvetica Neue",sans-serif">September 10, 2017 at 10:42:35 PM PDT</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><b><span style="font-family:"Helvetica Neue",sans-serif">To:
</span></b><span style="font-family:"Helvetica Neue",sans-serif"><a href="mailto:openid-specs-igov@lists.openid.net" target="_blank">openid-specs-igov@lists.openid.net</a></span><o:p></o:p></p>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">The document has a normative reference to a Vectors of Trust “standard”. The so called normative reference is an individual draft and has no standing at this time.
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The draft <a href="https://tools.ietf.org/html/draft-richer-vectors-of-trust-05" target="_blank">https://tools.ietf.org/html/draft-richer-vectors-of-trust-05</a> has been somewhat updated to reflect NIST 800-63-3’s new components, but does
not align.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We have voted “OBJECT” on this draft and would like to see this worked through first.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">— prateek<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</body>
</html>