<div><div dir="auto">I plan to finish the ICN paper (only two weeks before the deadline) first and then come back to work on the spec.</div></div><div dir="auto"><br></div><div dir="auto">Best,</div><div dir="auto">Zhiyi</div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Apr 30, 2020 at 4:14 AM Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto">Hi Zhiyi<div dir="auto"><br></div><div dir="auto">It's been 8 days. When do you expect to finish the challenges spec?</div><div dir="auto"><br></div><div dir="auto">Yours, Junxiao</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 21, 2020, 10:42 Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu" rel="noreferrer" target="_blank">shijunxiao@email.arizona.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Hi Zhiyi</div><div><br></div><div>Main protocol revision 8921b91 has one typo: SignatureNo<span style="background-color:rgb(255,255,0)">u</span>nce.</div><div>I don't see any other problems.<br></div><div><br></div><div>I started to review the challenges spec.<br></div><div><a href="https://github.com/named-data/ndncert/wiki/NDNCERT-Protocol-0.3-Challenges" rel="noreferrer noreferrer" target="_blank">https://github.com/named-data/ndncert/wiki/NDNCERT-Protocol-0.3-Challenges</a></div><div>For revision d9fc127, I found the following problems.</div><div><br></div><div><b>Notations</b></div><div><span style="font-family:monospace">IN</span> and <span style="font-family:monospace">DN</span> would be easier to read if you write as I<i>n</i> and D<i>n</i>.<br></div><div>Do not use fixed width font, because these are not strings or TLV-TYPE numbers.<br></div><div>
<div>The letter <i>n</i> is italic showing that it is a variable. In later sections when it's replaced by a number, use regular font.<br></div><div><br></div>
</div><div><span style="font-family:monospace">CSPRG</span> should be written as CSPRG.<br></div><div>
<div>Do not use fixed width font, because this is not string or TLV-TYPE number.<br></div>
</div><div><br></div><div><b>All challenges</b></div><div>The main protocol specifies: the CA will keep the state for the time as defined in remaining-time field defined by the challenge selected.</div><div>Thus, each challenge needs to define its time limit.</div><div><br></div><div>The main protocol specifies that selected-challenge element is required in all CHALLENGE Interests.</div><div>Thus, every I2 should contain the selected-challenge element.</div><div><br></div><div>What happens if the first CHALLENGE Interest selects one challenge, and the second CHALLENGE Interest selects a different challenge?</div><div>Which error code?<br></div><div><br></div><div><b>Email Challenge</b></div><div>Typo in D1: applicat<span style="background-color:rgb(255,255,0)">oi</span>n.<br></div><div><div><div><br></div><div>It's necessary to specify what elements should appear in the email. I think you'll need at least: ca-prefix, request-id, and S.</div><div>Without ca-prefix, one CA could cause the requester to reveal S generated by another CA.<br>Without request-id, malicious requesters could send the CA other requests that deliver similar emails to the legitimate requester, and the
legitimate
requester would have trouble identifying which S corresponds to the current request.</div><div><br></div><div><b>Proof of Credential Challenge</b><b><br></b></div><div>In the section title, "of" should not be capitalized. See <a href="https://www.bkacontent.com/how-to-correctly-use-apa-style-title-case/" rel="noreferrer noreferrer" target="_blank">https://www.bkacontent.com/how-to-correctly-use-apa-style-title-case/</a></div><div><br></div><div>Is the ordering between the two key-value pairs significant?</div><div>If reordering is an error, which error code?<br></div><div><br></div><div>Why does this challenge permit multiple tries? For PIN and email challenges, there's possibility of user typing error, so that permitting multiple tries makes sense. It doesn't make sense here.<br></div><div><br></div><div><b>
Proof of Private Key Challenge
</b></div><div>
<div>In the section title, "of" should not be capitalized. See <a href="https://www.bkacontent.com/how-to-correctly-use-apa-style-title-case/" rel="noreferrer noreferrer" target="_blank">https://www.bkacontent.com/how-to-correctly-use-apa-style-title-case/</a></div><div><br></div>Why does this challenge permit multiple tries? For PIN and email challenges, there's possibility of user typing error, so that permitting multiple tries makes sense. It doesn't make sense here.<br>
</div><div><br></div><div><br></div><div>Yours, Junxiao<br></div></div><div><br></div></div></div>
</blockquote></div>
</blockquote></div></div>