[Nfd-dev] review request: NDNLPv2 NACK, Fragmentation, LocalControlHeader

[Junxiao Shi]

Hi Ilya

The full name for "reliability" feature is "reliability improvement".
Since any NDNLPv2 feature is swappable, nothing prevents one to design a
reliability feature that can have guaranteed delivery (whether it's useful
is a different question).
"partial reliability" isn't correct.


CongestionNack is in the roadmap but not yet approved.


NDNLPv2 can be used on application-forwarder connection as well.
To send an Interest NACK from application, simply send a NDNLPv2 packet
with NdnlpNack header field.

Yours, Junxiao

On Tue, May 26, 2015 at 3:39 PM, Ilya Moiseenko <iliamo at cs.ucla.edu> wrote:

> Hi Junxiao,
> 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.
>
> 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?
>
> 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.
>
> Ilya
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20150527/921bbbec/attachment.html>