<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hi Junxiao,<div>I think that even the reliability is not yet approved you should rename it to “partial reliability” throughout the spec, because I guess that you are not going to provide persistent retransmissions on the link layer.</div><div><br></div><div>Another thing is NACK. Ok, if I’m a server-side application getting lots of Interests that I cannot process, do I provide a GiveUpNack to my local NFD ? I expected something like a CongestionNACK. Or congestion goes to the reason field?</div><div><br></div><div>Final question, is there a way to make Interest NACK from the application today or in near future? It’s alright if NFD doesn’t understand it yet.</div><div><br></div><div>Ilya</div><div><br><div><div>On May 25, 2015, at 9:23 PM, Junxiao Shi <<a href="mailto:shijunxiao@email.arizona.edu">shijunxiao@email.arizona.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><p>Dear folks</p><p>I have written the protocol spec of first batch of features in NDNLPv2, and I need someone to review the design.</p><p><a href="http://redmine.named-data.net/projects/nfd/wiki/NDNLPv2">http://redmine.named-data.net/projects/nfd/wiki/NDNLPv2</a></p><p>If you don't know what this is about, see #2520, #2763, and <a href="http://redmine.named-data.net/attachments/download/301/NDNLPv2_20150417.pptx">http://redmine.named-data.net/attachments/download/301/NDNLPv2_20150417.pptx</a></p><p>I'll appreciate all review comments.<br>
You don't have to be an expert in order to do a design review.</p><p>Yours, Junxiao</p>
_______________________________________________<br>Nfd-dev mailing list<br><a href="mailto:Nfd-dev@lists.cs.ucla.edu">Nfd-dev@lists.cs.ucla.edu</a><br>http://www.lists.cs.ucla.edu/mailman/listinfo/nfd-dev<br></blockquote></div><br></div></body></html>