<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">John,<div class=""><br class=""></div><div class="">Since you mention it, this quote from RFC2026 is why I think iGov cannot move forward as written with a normative requirement on VoT:</div><div class=""><blockquote type="cite" class=""><pre class="newpage" style="font-size: 13.333333015441895px; margin-top: 0px; margin-bottom: 0px; break-before: page;"><span class="h4" style="line-height: 0pt; display: inline; font-size: 1em; font-weight: bold;"><h4 style="line-height: 0pt; display: inline; font-size: 1em;" class=""><a class="selflink" name="section-4.2.1" href="https://tools.ietf.org/html/rfc2026#section-4.2.1" style="color: black; text-decoration: none;">4.2.1</a> Experimental</h4></span>
The "Experimental" designation typically denotes a specification that
is part of some research or development effort. Such a specification
is published for the general information of the Internet technical
community and as an archival record of the work, subject only to
editorial considerations and to verification that there has been
adequate coordination with the standards process (see below). An
Experimental specification may be the output of an organized Internet
research effort (e.g., a Research Group of the IRTF), an IETF Working
Group, or it may be an individual contribution.</pre></blockquote><div class=""><br class=""></div><div class="">From the iGov specification:</div><div class=""><blockquote type="cite" class=""><h1 id="rfc.section.3.4" style="font-size: 14pt; line-height: 21pt; break-after: avoid-page; font-family: verdana, helvetica, arial, sans-serif;" class=""><a href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?Submit=Submit&format=ascii&mode=html&type=ascii&url=https://bitbucket.org/openid/igov/raw/master/openid-igov-profile.xml#rfc.section.3.4" style="text-decoration: none; color: rgb(51, 51, 51);" class="">3.4.</a> <a href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?Submit=Submit&format=ascii&mode=html&type=ascii&url=https://bitbucket.org/openid/igov/raw/master/openid-igov-profile.xml#vot" id="vot" style="text-decoration: none; color: rgb(51, 51, 51);" class="">Vectors of Trust</a></h1><p id="rfc.section.3.4.p.1" style="margin-left: 2em; margin-right: 2em; font-family: verdana, helvetica, arial, sans-serif; font-size: 13.333333015441895px;" class="">Servers MUST check for the presence of the <samp class="">vtr</samp> parameter before <samp class="">acr</samp> in Requests. If both parameters are present the server will default to <samp class="">vtr</samp> as the request to respond to. <samp class="">acr</samp> MUST then be ignored. </p><p id="rfc.section.3.4.p.2" style="margin-left: 2em; margin-right: 2em; font-family: verdana, helvetica, arial, sans-serif; font-size: 13.333333015441895px;" class="">OpenID Providers MAY provide the <samp class="">vot</samp> and contain valid values from the <a href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?Submit=Submit&format=ascii&mode=html&type=ascii&url=https://bitbucket.org/openid/igov/raw/master/openid-igov-profile.xml#I-D.richer-vectors-of-trust" class="xref" style="text-decoration: none;">Vectors of Trust</a> standard. </p><p id="rfc.section.3.4.p.3" style="margin-left: 2em; margin-right: 2em; font-family: verdana, helvetica, arial, sans-serif; font-size: 13.333333015441895px;" class="">The <samp class="">vtr</samp> and contain valid values from the <a href="https://xml2rfc.tools.ietf.org/cgi-bin/xml2rfc.cgi?Submit=Submit&format=ascii&mode=html&type=ascii&url=https://bitbucket.org/openid/igov/raw/master/openid-igov-profile.xml#I-D.richer-vectors-of-trust" class="xref" style="text-decoration: none;">Vectors of Trust</a> standard. </p><p id="rfc.section.3.4.p.4" style="margin-left: 2em; margin-right: 2em; font-family: verdana, helvetica, arial, sans-serif; font-size: 13.333333015441895px;" class="">It is out of scope of this document to determine how an organization maps their digital identity practices to valid VOT component values.</p></blockquote></div><div class="">Curious that the language “Vectors of Trust standard” is used.</div><div class=""><br class=""></div><div class="">Regarding the last sentence quoted above, I wonder what the point of section 3.4 and VoT is then. John, you mentioned that it was strongly profiled and mapped into the new 800-63-3 vectors (IAL, AAL, FAL). Where is this language?</div><div class=""><br class=""></div><div class="">The resolution is one of the following:</div><div class="">A. Under the IETF, see if the track can be changed back to standards with a WG (new or existing)</div><div class="">B. Develop an OIDF specification and publish it under this WG.</div><div class=""><br class=""></div><div class="">Finally I am not aware of any formal BoF announcements in either organization. I recall Justin’s presentation years ago at the OAuth WG and supported it in general. I was curious and still waiting to see how we achieve interop on LoA or the modern IAl, AAL, FAL. For example, does a federated assertion contain individual attribute IAL values as well as an authentication AAL? </div><div class=""><br class=""></div><div class="">—> FWIW — the new 800-63-3 has a much simpler model that is fairly easy to map. The fundamental problem with 800-63 is that there is no methodology for exchanging that information. It can only be used in policy based fixed relationships. IOW, without VoT, a single IDP cannot vary IAL or AAL values per person.</div><div class=""><br class=""></div><div class="">Phil</div><div class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div style="color: rgb(0, 0, 0); letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><span class="Apple-style-span" style="border-collapse: separate; line-height: normal; border-spacing: 0px;"><div class="" style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div class=""><div class=""><div class=""><br class=""></div><div class="">Oracle Corporation, Identity Cloud Services Architect</div><div class="">@independentid</div><div class=""><a href="http://www.independentid.com" class="">www.independentid.com</a></div></div></div></div></span><a href="mailto:phil.hunt@oracle.com" class="" style="orphans: 2; widows: 2;">phil.hunt@oracle.com</a></div></div></div></div></div></div></div></div></div></div></div></div>
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Sep 11, 2017, at 9:43 AM, John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" class="">ve7jtb@ve7jtb.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">I think Phil is referring to the IETF track that VOT is currently on per RFC2026<div class=""><a href="https://tools.ietf.org/html/rfc2026" class="">https://tools.ietf.org/html/rfc2026</a></div><div class=""><br class=""></div><div class="">VOT did have several BOFs as I recall but for whatever reason couldn’t justify a working group and no other working group was a good fit. The internet society was interested in it and a security AD agreed to sponsor it.</div><div class=""><br class=""></div><div class="">The guidelines for AD sponsors drafts are <a href="https://www.ietf.org/iesg/statement/ad-sponsoring-docs.html" class="">https://www.ietf.org/iesg/statement/ad-sponsoring-docs.html</a></div><div class=""><br class=""></div><div class="">The experimental status theoretically impacts the amount of review the IESG will do. In reality they all go through last call and IESG review.</div><div class=""><br class=""></div><div class="">AD sponsors docs can be standards track.</div><div class=""><br class=""></div><div class="">If I parse Phill correctly he would like the document to be standards track to provide the appropriate gravitas.</div><div class=""><br class=""></div><div class="">This is not a group that can make those sorts of decisions but this group can provide feedback to the document shepherd and responsible AD.</div><div class=""><br class=""></div><div class="">The current track is the fastest to get a RFC though makes as experimental. </div><div class="">Leif and I did discuss the Working group opption at the last IETF in Prague. </div><div class="">Doing that would slow things down perhaps by a year or more.</div><div class=""><br class=""></div><div class="">I suppose the middle road would be to get out an experimental one, and then take that to a WG for refinement on the standards track.</div><div class=""><br class=""></div><div class="">In Any event I get the feeling that Oracle would like more input.</div><div class=""><br class=""></div><div class="">John B.</div><div class=""><br class=""></div><div class=""><div class=""><blockquote type="cite" class=""><div class="">On Sep 11, 2017, at 12:00 PM, Grassi, Paul A. (Fed) <<a href="mailto:paul.grassi@nist.gov" class="">paul.grassi@nist.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="WordSection1" style="page: WordSection1; font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">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 class=""></o:p></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div style="border-style: solid none none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); padding: 3pt 0in 0in;" class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-size: 12pt;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-size: 12pt;" class="">Openid-specs-igov <<a href="mailto:openid-specs-igov-bounces@lists.openid.net" class="">openid-specs-igov-bounces@lists.openid.net</a>> on behalf of "Phil Hunt (IDM) via Openid-specs-igov" <<a href="mailto:openid-specs-igov@lists.openid.net" class="">openid-specs-igov@lists.openid.net</a>><br class=""><b class="">Reply-To:<span class="Apple-converted-space"> </span></b>"Phil Hunt (IDM)" <<a href="mailto:phil.hunt@oracle.com" class="">phil.hunt@oracle.com</a>><br class=""><b class="">Date:<span class="Apple-converted-space"> </span></b>Monday, September 11, 2017 at 11:07 AM<br class=""><b class="">To:<span class="Apple-converted-space"> </span></b>John Bradley <<a href="mailto:ve7jtb@ve7jtb.com" class="">ve7jtb@ve7jtb.com</a>><br class=""><b class="">Cc:<span class="Apple-converted-space"> </span></b>"<a href="mailto:openid-specs-igov@lists.openid.net" class="">openid-specs-igov@lists.openid.net</a>" <<a href="mailto:openid-specs-igov@lists.openid.net" class="">openid-specs-igov@lists.openid.net</a>><br class=""><b class="">Subject:<span class="Apple-converted-space"> </span></b>Re: [Openid-specs-igov] Fwd: Regarding the vote on Implementer’s Drafts of Two iGov Specifications<o:p class=""></o:p></span></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The VoT spec is also experimental.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Having a normative dependence on an experimental spec creates instability and devalues this spec. Or is the intent that igov be experimental?<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><br class="">Phil<o:p class=""></o:p></div></div><div class=""><p class="MsoNormal" style="margin: 0in 0in 12pt; font-size: 11pt; font-family: Calibri, sans-serif;"><br class="">On Sep 11, 2017, at 4:48 AM, John Bradley via Openid-specs-igov <<a href="mailto:openid-specs-igov@lists.openid.net" style="color: purple; text-decoration: underline;" class="">openid-specs-igov@lists.openid.net</a>> wrote:<o:p class=""></o:p></p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite"><div class=""><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Forwarding a comment on the vote. <span class="Apple-converted-space"> </span><o:p class=""></o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">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 class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">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 class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">To discuss the IETF process and that document the SAG list is best.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">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 class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">People interested in the iGov discussion with NIST should join the WG. <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">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 class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Honestly the more feedback the better. Sometimes it takes specs referencing important work like VOT before people become aware of them. <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">I don't think we have a issue with the iGov implimentors draft, but others can differ.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Regards <o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">John B. <o:p class=""></o:p></div></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">---------- Forwarded message ----------<br class="">From: "Prateek Mishra" <<a href="mailto:Prateek.Mishra@oracle.com" style="color: purple; text-decoration: underline;" class="">Prateek.Mishra@oracle.com</a>><br class="">Date: Sep 11, 2017 00:44<br class="">Subject: Fwd: Regarding the vote on Implementer’s Drafts of Two iGov Specifications<br class="">To: "John Bradley" <<a href="mailto:ve7jtb@ve7jtb.com" style="color: purple; text-decoration: underline;" class="">ve7jtb@ve7jtb.com</a>>, "Phil Hunt (IDM)" <<a href="mailto:phil.hunt@oracle.com" style="color: purple; text-decoration: underline;" class="">phil.hunt@oracle.com</a>><br class="">Cc:<span class="Apple-converted-space"> </span><br class=""><br class=""><o:p class=""></o:p></div><blockquote style="border-style: none none none solid; border-left-width: 1pt; border-left-color: rgb(204, 204, 204); padding: 0in 0in 0in 6pt; margin-left: 4.8pt; margin-right: 0in;" class="" type="cite"><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><br class=""><br class=""><o:p class=""></o:p></div><blockquote style="margin-top: 5pt; margin-bottom: 5pt;" class="" type="cite"><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">Begin forwarded message:<o:p class=""></o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-family: 'Helvetica Neue', sans-serif;" class="">From:<span class="Apple-converted-space"> </span></span></b><span style="font-family: 'Helvetica Neue', sans-serif;" class="">Prateek Mishra <<a href="mailto:Prateek.Mishra@oracle.com" target="_blank" style="color: purple; text-decoration: underline;" class="">Prateek.Mishra@oracle.com</a>></span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-family: 'Helvetica Neue', sans-serif;" class="">Subject: Regarding the vote on Implementer’s Drafts of Two iGov Specifications</span></b><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-family: 'Helvetica Neue', sans-serif;" class="">Date:<span class="Apple-converted-space"> </span></span></b><span style="font-family: 'Helvetica Neue', sans-serif;" class="">September 10, 2017 at 10:42:35 PM PDT</span><o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><b class=""><span style="font-family: 'Helvetica Neue', sans-serif;" class="">To:<span class="Apple-converted-space"> </span></span></b><span style="font-family: 'Helvetica Neue', sans-serif;" class=""><a href="mailto:openid-specs-igov@lists.openid.net" target="_blank" style="color: purple; text-decoration: underline;" class="">openid-specs-igov@lists.openid.net</a></span><o:p class=""></o:p></div></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div><div class=""><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">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 class=""></o:p></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">The draft <a href="https://tools.ietf.org/html/draft-richer-vectors-of-trust-05" target="_blank" style="color: purple; text-decoration: underline;" class="">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 class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">We have voted “OBJECT” on this draft and would like to see this worked through first.<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class="">— prateek<o:p class=""></o:p></div></div><div class=""><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div></div></div></blockquote></div><div style="margin: 0in 0in 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif;" class=""><o:p class=""> </o:p></div></div></blockquote></div></div></blockquote></div></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>