[Ndn-interest] Selector Protocol over exact matching

Ignacio.Solis at parc.com Ignacio.Solis at parc.com
Fri Sep 26 01:34:30 PDT 2014


I’m not sure what you mean here.

The FIB is a regular FIB, it does longest prefix match.

The PIT needs an entry for every interest that can’t be aggregated.  This
is true for selectors as well (even though you might optimize this by
having only 1 name entry and a bunch of selector entries branched off of
this one).

Nacho

--
Nacho (Ignacio) Solis
Protocol Architect
Principal Scientist
Palo Alto Research Center (PARC)
+1(650)812-4458
Ignacio.Solis at parc.com





On 9/26/14, 9:42 AM, "Tai-Lin Chu" <tailinchu at gmail.com> wrote:

>How will fib work under exact matching? that implies #routable
>interest name = #fib name.
>After you mention selectors in name and key hash, I see a huge number
>of fib entries to be created.
>
>I am worried about those dummy nodes.
>
>On Thu, Sep 25, 2014 at 4:17 PM,  <Ignacio.Solis at parc.com> wrote:
>> On 9/25/14, 10:35 PM, "Lan Wang (lanwang)" <lanwang at memphis.edu> wrote:
>>
>>>In NDN, if a router wants to check the signature, then it can check.  If
>>>it wants to skip the checking, that's fine too.  If the design doesn't
>>>allow the router to verify the signature, then that's a problem.  In the
>>>above description, the cache signs a data packet with a name owned by
>>>someone else, it seems problematic for a design to advocate this.
>>
>> Routers that support the Selector Protocol could check signatures.
>>
>>>
>>>One difference is that here the returned data can satisfy only that
>>>interest.  In the original selector design, the returned data can
>>>satisfy
>>>other Interests with the same name but different selectors (e.g., > 50).
>>
>> Interests with the same selector would be exact matched throughout the
>> network at any node.
>>
>> Interests with different selectors would not match on all routers, but
>> they would match just fine on routers that supported the Selector
>>Protocol.
>>
>> Basically, everything you want works on routers that support the
>>Selector
>> Protocol, but routers that don¹t want to support it, don¹t have to.
>>
>>
>> Nacho
>>
>>
>>
>>>>
>>>>
>>>>
>>>> --
>>>> Nacho (Ignacio) Solis
>>>> Protocol Architect
>>>> Principal Scientist
>>>> Palo Alto Research Center (PARC)
>>>> +1(650)812-4458
>>>> Ignacio.Solis at parc.com
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> Ndn-interest mailing list
>>>> Ndn-interest at lists.cs.ucla.edu
>>>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>>
>>>
>>>_______________________________________________
>>>Ndn-interest mailing list
>>>Ndn-interest at lists.cs.ucla.edu
>>>http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest
>>
>>
>> _______________________________________________
>> Ndn-interest mailing list
>> Ndn-interest at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndn-interest





More information about the Ndn-interest mailing list