<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;" class=""><div apple-content-edited="true" class=""><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; " class=""><div class=""><br class=""></div></div></span></span></div><div><blockquote type="cite" class=""><div class="">On Feb 23, 2015, at 10:15 AM, Burke, Jeff <<a href="mailto:jburke@remap.ucla.edu" class="">jburke@remap.ucla.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=Windows-1252" class="">
<div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">
<div class=""><br class="">
</div>
<div class="">As part of early lighting control work, we had already proposed an authenticated interest approach that includes sequence #, timestamp, and RTT estimator as state to avoid replay attacks:</div>
<div class=""><a href="http://named-data.net/wp-content/uploads/nomen13.pdf" class="">http://named-data.net/publications/nomen13/</a></div>
<div class=""><span style="font-family: Calibri, sans-serif; font-size: 14px;" class="">(see p4).</span></div>
<div style="font-family: Calibri, sans-serif; font-size: 14px;" class="">
<br class="">
</div>
<div style="font-family: Calibri, sans-serif; font-size: 14px;" class="">
(I am not sure why SignedInterest doesn't provide at least an optional sequence number.... Can the ndn-cxx/architecture folks comment on why this was removed from the design?)</div>
</div></div></blockquote><br class=""></div><div>I think, ideally, signed interest should be just “signed” interest, that is, it does not add any semantics other than signature info and signature value. The sequencing, timestamp, and nonce are not related to signature, they are attributes of command. In an early version of ndn-cxx, there was a command interest which is a signed interest but with more information about timestamp and nonce. And at time, the command interest is designed for local NFD control where interests are rarely out-of-order, so sequencing is not added into the command interest. The original idea is that one can always develop a helper for a specific command interest based on signed interest by introducing any necessary command attribute. But why command interest is later merged into signed interest is another story…</div><div><br class=""></div><div>Yingdi</div><br class=""></body></html>