[Nfd-dev] [Ndn-interest] NDN link protocol

[Junxiao Shi]

Hi Dave

The scenario is: switches understand Names, NICs understand Names.

When an Interest / Data arrives at a NIC but the host is not listening to
this Name prefix, the NIC should drop or NACK the packet, without waking up
rest of the PC.

We have high-end home routers running NFD. They have enough memory to keep
a PIT.


Wireless is a scenario I haven't studied much about. I'll be sure to look
up the terms you mentioned.

Yours, Junxiao

On Thu, Oct 9, 2014 at 12:38 PM, Dave Oran (oran) <oran at cisco.com> wrote:

>
> On Oct 8, 2014, at 9:28 PM, Junxiao Shi <shijunxiao at email.arizona.edu>
> wrote:
>
> > Dear folks
> >
> > If a local area network is using regular Ethernet (learn paths from
> source MAC address) today, self-learning can work on it.
> > Self-learning idea also has been tested on a 16-server fat tree topology.
> >
> > It's not crazy to multicast every packet.
> I beg to differ. Waking up 10,000 hosts on an extended LAN with a data
> packet when only one of them sent an interest, is, I’m afraid, actually
> crazy.
>
> > Switches are expected to understand NDN Names and act as NDN forwarders;
> good luck with that. No switches I’ve met in the last 10 years have enough
> memory to keep a PIT.
>
> > at physical layer there's no difference between multicast and unicast.
> >
> Also not true for pt-multipoint radios with hidden terminals.
> Not to mention the rate minimization pathologies of wireless LANs like
> 802.11.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/nfd-dev/attachments/20141010/f1d7c331/attachment.html>