<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">I'm on the flight to Boston and catching up my notes from yesterday: we spent time on this issue of how to handle the relation between FIB and feedback from (un)successful Interests, and I just want put down my view (at this time) in words, in case I did not express it clearly during the call <div class=""><br class=""></div><div class="">1/ we keep different things separately: FIB state is FIB state, interest feedback is recorded somewhere else (I dont know exactly where it is now)</div><div class=""><br class=""></div><div class="">2/ strategy looks all the info available to it and makes forwarding decisions for future interests</div><div class=""><br class=""></div><div class="">3/ So we just need a clear design of the following:</div><div class="">a) the prefix granularity of the impact from (un)successful interest, and</div><div class="">b) the time scale of this impact (i.e. how long to remember this)</div><div class=""><br class=""></div><div class="">3.a: if we take a "slow-start" spirit, i.e. being conservative until we learn better, a simple way to decide the prefix granularity is just take the name of successful/unsuccessful interest minus last components.</div><blockquote style="margin: 0 0 0 40px; border: none; padding: 0px;" class=""><div class="">e.g. this makes sense in streaming data (supposedly the last component is sequence number)</div></blockquote><div class="">for continued success, we dont change the prefix; </div><div class="">for continued failure: we need to understand what are the shared prefixes between those failed interests to decide whether we want to extract out more components from the end of the prefix.</div><div class=""><br class=""></div><div class="">3.b: maybe we can just follow standard soft state design, i.e. continued use of the information (which prefix succeeds/failed using which face) will rest the timeout, otherwise the information times out and get removed.</div><div class=""><br class=""></div><div class="">Thoughts?</div><div class=""><br class=""></div><div class="">Feel free to share with whoever interested, but I dont think this is ready to go nfd-dev list at this time (Junxiao, I will archive this msg)</div><div class=""><br class=""></div><div class="">Lixia</div><div class=""><br class=""></div></body></html>