cghali at uci.edu
Thu Jun 30 14:29:50 PDT 2016
I just want to highlight that interest NACKs that Lixia mentioned are
studied as two types of NACK messages in the paper that Gene shared earlier:
On Wednesday, June 29, 2016, Lixia Zhang <lixia at cs.ucla.edu> wrote:
> one detail that I have not seen mentioned so far: interest NACK versus
> data packet NACK.
> It seems to me that interest NACK is relatively well understood: a
> forwarding node failed to forward a received interest hence generates a
> NACK to its previous hop.
> data NACK seems to me not understood as fully:
> a) if a consumer gets a data packet that's not what it wants, it'd retry
> the interest in some way;
> b) any other forwarding node could drop an incorrect data packet, it can;
> whether it should generate a NACK on behalf of the consumer seems a
> separable question.
> > On Jun 28, 2016, at 1:47 AM, Tanusree Chatterjee <
> > If a data packet is modified and detected during verification, can
> forwarder send a NACK. How the data can be resend in this case? If consumer
> is not satisfied it has to send the same interest again, is there any other
> way out to get the data which may not been correctly received due to some
> > -- Regards,
> > Tanusree Chatterjee
> > _______________________________________________
> > Ndn-interest mailing list
> > http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
> Ndn-interest mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Ndn-interest