From csb17053 at tezu.ac.in  Mon May  3 04:53:36 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Mon, 3 May 2021 17:23:36 +0530
Subject: [ndnSIM] Getting all PIT entries of a node.
Message-ID: <CAOhxRanXFwXXg4FC9rGw89Y7ZFpQHNjVX=b2tdZ2qvspB0xewA@mail.gmail.com>

Hello everybody,
I am trying to get all the entries in the PIT of a node whenever an
interest packet arrives at that node.

I am trying to tweak the code in the function onIncomingInterest(ingress,
interest) inside NFD/daemon/table/fw/forwarder.cpp.

Kindly help me with this, it would be really helpful if either one gives me
some hint about the objects i need to make or provide with some example
code.

Thanking you in advance
Prajjwal Singh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210503/719cedb0/attachment.html>

From csb17053 at tezu.ac.in  Mon May  3 09:37:23 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Mon, 3 May 2021 22:07:23 +0530
Subject: [ndnSIM] How to add a new field in Interest Packet.
Message-ID: <CAOhxRami+DvF9_Oyrtz-1SgZg7F90noWGZDJ=i51uRgnrcURtw@mail.gmail.com>

Hello all,
I am trying to add a new field, Priority, to interest Packets.

Till now I have followed this:

   1.  Add field in tlv.hpp
   2.  Add member and its getter and setter functions in interest.hpp
   3.  Implement the functions in interest.cpp
   4. Modify the encoding function wireEncode() and decoding function
   wireDecode() in interest.cpp

Then I added some code to set the Priority field for interest packets by
SetAttribute features of the ndnHelpers.

But now My problem is that the Priority field gets set to default after the
first hop.
Please help me make this work.

Thank you,
Prajjwal Singh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210503/4dd5925a/attachment.html>

From shijunxiao at email.arizona.edu  Mon May  3 10:42:12 2021
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Mon, 3 May 2021 13:42:12 -0400
Subject: [ndnSIM] [EXT] How to add a new field in Interest Packet.
In-Reply-To: <CAOhxRami+DvF9_Oyrtz-1SgZg7F90noWGZDJ=i51uRgnrcURtw@mail.gmail.com>
References: <CAOhxRami+DvF9_Oyrtz-1SgZg7F90noWGZDJ=i51uRgnrcURtw@mail.gmail.com>
Message-ID: <CAOFH+OY89DmmZx7s42jOMAt3mNb0UL-DGs41pCvDqGDrhJ_dcw@mail.gmail.com>

Hi Prajjwal

If forwarder cannot modify this field:
Put it as part of the Name or ApplicationParameters.

If forwarder can modify this field:
It should be added to the hop-by-hop header.
See
https://lo.calho.st/posts/ndnsim-custom-fields/ for specific steps.
Note that InterestLifetime, Nonce, and HopLimit are modifiable by the
forwarder so they technically belong to the hop-by-hop header; they are in
Interest due to historic reason.

Yours, Junxiao

On Mon, May 3, 2021 at 12:37 Prajjwal Singh <csb17053 at tezu.ac.in> wrote:

> *External Email*
> Hello all,
> I am trying to add a new field, Priority, to interest Packets.
>
> Till now I have followed this:
>
>    1.  Add field in tlv.hpp
>    2.  Add member and its getter and setter functions in interest.hpp
>    3.  Implement the functions in interest.cpp
>    4. Modify the encoding function wireEncode() and decoding function
>    wireDecode() in interest.cpp
>
> Then I added some code to set the Priority field for interest packets by
> SetAttribute features of the ndnHelpers.
>
> But now My problem is that the Priority field gets set to default after
> the first hop.
> Please help me make this work.
>
> Thank you,
> Prajjwal Singh
>
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210503/b4f1138b/attachment.html>

From shijunxiao at email.arizona.edu  Mon May  3 12:00:57 2021
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Mon, 3 May 2021 15:00:57 -0400
Subject: [ndnSIM] [EXT] Getting all PIT entries of a node.
In-Reply-To: <CAOhxRanXFwXXg4FC9rGw89Y7ZFpQHNjVX=b2tdZ2qvspB0xewA@mail.gmail.com>
References: <CAOhxRanXFwXXg4FC9rGw89Y7ZFpQHNjVX=b2tdZ2qvspB0xewA@mail.gmail.com>
Message-ID: <CAOFH+OZ77ouWDwb2+_dyq2A5OyvKY__uWPQJeKtc+HgKr3SVCg@mail.gmail.com>

Hi Prajjwal

Forwarder::onIncomingInterest function can access the PIT via m_pit member
field of the Forwarder class.
The PIT is iterable via standard begin() end() functions.

However, if your algorithm depends on PIT enumeration upon every Interest
receipt, it likely would not scale.

Yours, Junxiao

On Mon, May 3, 2021 at 7:54 AM Prajjwal Singh <csb17053 at tezu.ac.in> wrote:

> *External Email*
> Hello everybody,
> I am trying to get all the entries in the PIT of a node whenever an
> interest packet arrives at that node.
>
> I am trying to tweak the code in the function onIncomingInterest(ingress,
> interest) inside NFD/daemon/table/fw/forwarder.cpp.
>
> Kindly help me with this, it would be really helpful if either one gives
> me some hint about the objects i need to make or provide with some example
> code.
>
> Thanking you in advance
> Prajjwal Singh
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210503/f5863d79/attachment.html>

From csb17053 at tezu.ac.in  Mon May  3 12:06:03 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Tue, 4 May 2021 00:36:03 +0530
Subject: [ndnSIM] [EXT] Getting all PIT entries of a node.
In-Reply-To: <CAOFH+OZ77ouWDwb2+_dyq2A5OyvKY__uWPQJeKtc+HgKr3SVCg@mail.gmail.com>
References: <CAOhxRanXFwXXg4FC9rGw89Y7ZFpQHNjVX=b2tdZ2qvspB0xewA@mail.gmail.com>
 <CAOFH+OZ77ouWDwb2+_dyq2A5OyvKY__uWPQJeKtc+HgKr3SVCg@mail.gmail.com>
Message-ID: <CAOhxRanREBgFQMjGE8tAsGvYrGsnCMkpYRA7dboQzw9N82X9WA@mail.gmail.com>

Thank you for the information.
 Specially for the scaling part.
I Will try to create some small data structure to track the pit entries I
need, hopefully it will help.

On Tue, 4 May 2021, 00:31 Junxiao Shi, <shijunxiao at email.arizona.edu> wrote:

> Hi Prajjwal
>
> Forwarder::onIncomingInterest function can access the PIT via m_pit member
> field of the Forwarder class.
> The PIT is iterable via standard begin() end() functions.
>
> However, if your algorithm depends on PIT enumeration upon every Interest
> receipt, it likely would not scale.
>
> Yours, Junxiao
>
> On Mon, May 3, 2021 at 7:54 AM Prajjwal Singh <csb17053 at tezu.ac.in> wrote:
>
>> *External Email*
>> Hello everybody,
>> I am trying to get all the entries in the PIT of a node whenever an
>> interest packet arrives at that node.
>>
>> I am trying to tweak the code in the function onIncomingInterest(ingress,
>> interest) inside NFD/daemon/table/fw/forwarder.cpp.
>>
>> Kindly help me with this, it would be really helpful if either one gives
>> me some hint about the objects i need to make or provide with some example
>> code.
>>
>> Thanking you in advance
>> Prajjwal Singh
>> _______________________________________________
>> ndnSIM mailing list
>> ndnSIM at lists.cs.ucla.edu
>> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210504/3c235a25/attachment.html>

From csb17053 at tezu.ac.in  Mon May  3 21:44:12 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Tue, 4 May 2021 10:14:12 +0530
Subject: [ndnSIM] Adding new field in Interest Packet.
Message-ID: <CAOhxRam7-Z3MnynqspsOZs4VB48=kSF+oBq=g3Sm2WJA_F6teg@mail.gmail.com>

Hello everybody,
I am trying to add a new field in interest packet and I want this field to
persist throughout the network for each interest, (i.e. if a consumer sets
this custom field to X in the interest packet, then it should be forwarded
by all the routers to the producer with the custom field as X)

Previously I had used this tutorial to add the field in interest packet:
https://www.programmersought.com/article/14675398024/

Please point out what is lacking in this solution.

The main problem is that if i have the following topology
A--B--C--D
(Where A is the Consumer and D is the Producer, and B and C are routers)
Then by the solution given in the above link the custom field set in A's
generated Interest packet is reset to default value by B when it forwards
the interest to C.
How can I make it carry the value intended by A?

Thanking you in advance
Prajjwal Singh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210504/f833baa6/attachment.html>

From a_djemaa at esi.dz  Tue May  4 02:48:17 2021
From: a_djemaa at esi.dz (DJEMAA Adel)
Date: Tue, 4 May 2021 10:48:17 +0100
Subject: [ndnSIM] Adding new field in Interest Packet.
In-Reply-To: <CAOhxRam7-Z3MnynqspsOZs4VB48=kSF+oBq=g3Sm2WJA_F6teg@mail.gmail.com>
References: <CAOhxRam7-Z3MnynqspsOZs4VB48=kSF+oBq=g3Sm2WJA_F6teg@mail.gmail.com>
Message-ID: <CAKqeZG6AsovL5794pxMDHoR5zuY2VKr+EVaaVNsKbpHfUVcd8A@mail.gmail.com>

Hi,
If the packet length doesn't matter in your configuration, I advise you to
add a Tag instead of a new Field to your packet, since according to ndnSIM
design, the tag resides only in the memory.
Also, a Tag can be easily managed directly in the NFD machinery (forwarder
class), contrary to a new field in either Interest or Data packets which
are generally static objects.
Below references showing how to add a new Tag in the packet (HopCountTag
which is already implemented in ndnSIM), and it works 100%:
   - https://www.lists.cs.ucla.edu/pipermail/ndnsim/2018-August/004913.html
   -
https://github.com/named-data-ndnSIM/NFD/commit/0a30676920b9d3f2b2c8bc68e583befc415210cc
   -
https://github.com/named-data-ndnSIM/ndn-cxx/commit/d31b8ef523f4a5b152da88e3d5f47d5697d60772
Hope this helps.
Regards.


Le mar. 4 mai 2021 ? 05:44, Prajjwal Singh <csb17053 at tezu.ac.in> a ?crit :

> Hello everybody,
> I am trying to add a new field in interest packet and I want this field to
> persist throughout the network for each interest, (i.e. if a consumer sets
> this custom field to X in the interest packet, then it should be forwarded
> by all the routers to the producer with the custom field as X)
>
> Previously I had used this tutorial to add the field in interest packet:
> https://www.programmersought.com/article/14675398024/
>
> Please point out what is lacking in this solution.
>
> The main problem is that if i have the following topology
> A--B--C--D
> (Where A is the Consumer and D is the Producer, and B and C are routers)
> Then by the solution given in the above link the custom field set in A's
> generated Interest packet is reset to default value by B when it forwards
> the interest to C.
> How can I make it carry the value intended by A?
>
> Thanking you in advance
> Prajjwal Singh
> _______________________________________________
> ndnSIM mailing list
> ndnSIM at lists.cs.ucla.edu
> http://www.lists.cs.ucla.edu/mailman/listinfo/ndnsim
>


-- 
Mr DJAMA Adel
Phd student
Ecole Militaire Polytechnique
Algiers 16046, ALGERIA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210504/1ad78d5b/attachment-0001.html>

From shijunxiao at email.arizona.edu  Tue May  4 17:58:36 2021
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Tue, 4 May 2021 20:58:36 -0400
Subject: [ndnSIM] [EXT]Re:  Adding new field in Interest Packet.
In-Reply-To: <CAKqeZG6AsovL5794pxMDHoR5zuY2VKr+EVaaVNsKbpHfUVcd8A@mail.gmail.com>
References: <CAOhxRam7-Z3MnynqspsOZs4VB48=kSF+oBq=g3Sm2WJA_F6teg@mail.gmail.com>
 <CAKqeZG6AsovL5794pxMDHoR5zuY2VKr+EVaaVNsKbpHfUVcd8A@mail.gmail.com>
Message-ID: <CAOFH+OZqJe-T-4KWEgU8+1cbiYt1LnYLzSWhHwY=QAJjNfnHiw@mail.gmail.com>

Hi DJEMAA


If the packet length doesn't matter in your configuration, I advise you to
> add a Tag instead of a new Field to your packet, since according to ndnSIM
> design, the tag resides only in the memory.
> Also, a Tag can be easily managed directly in the NFD machinery (forwarder
> class), contrary to a new field in either Interest or Data packets which
> are generally static objects.
>

ndnSIM doesn't support ns3::Tag (the kind described in ns-3 model library
https://www.nsnam.org/docs/release/3.33/models/html/packets.html#adding-and-removing-tags
).
Subclasses of ndn::Tag are completely different from ns3::Tag. This
includes the HopCountTag. They must be encoded into the packet buffer to
have any effect.


>> The main problem is that if i have the following topology
>> A--B--C--D
>> (Where A is the Consumer and D is the Producer, and B and C are routers)
>> Then by the solution given in the above link the custom field set in A's
>> generated Interest packet is reset to default value by B when it forwards
>> the interest to C.
>> How can I make it carry the value intended by A?
>>
>
A *forwarded* Interest is actually a different packet from the original:
Name, CanBePrefix, MustBeFresh, ApplicationParameters are copied over,
InterestLifetime, Nonce, HopLimit are modified, and other fields may be
discarded.

As I said previously, it's best to include the information as part of the
Name or ApplicationParameters, which is supported universally.

While NDN protocol allows having unrecognized non-critical fields in the
Interest packet, the protocol is vague on whether and what to preserve
during forwarding.
So far, as long as Name, CanBePrefix, MustBeFresh, ApplicationParameters,
and any fields that appear after ApplicationParameters are preserved, the
forwarder implementation would be interoperable.

Yours, Junxiao
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210504/bb011a34/attachment.html>

From csb17053 at tezu.ac.in  Tue May  4 19:19:31 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Wed, 5 May 2021 07:49:31 +0530
Subject: [ndnSIM] [EXT]Re:  Adding new field in Interest Packet.
In-Reply-To: <CAOFH+OZqJe-T-4KWEgU8+1cbiYt1LnYLzSWhHwY=QAJjNfnHiw@mail.gmail.com>
References: <CAOhxRam7-Z3MnynqspsOZs4VB48=kSF+oBq=g3Sm2WJA_F6teg@mail.gmail.com>
 <CAKqeZG6AsovL5794pxMDHoR5zuY2VKr+EVaaVNsKbpHfUVcd8A@mail.gmail.com>
 <CAOFH+OZqJe-T-4KWEgU8+1cbiYt1LnYLzSWhHwY=QAJjNfnHiw@mail.gmail.com>
Message-ID: <CAOhxRanNLrUywXA3wV=4O9DVh7Of4QvqZMBHQhhvf6-4Cm=T2Q@mail.gmail.com>

Thanks to Junxiao and DJEMAA ,
Junxiao's suggestion is possibly the best, I tried and tested it and it
works very well.

I also tried the method provided in the aforesaid link
<https://www.programmersought.com/article/14675398024/>, and it works!
I had committed a few mistakes that led me into other results.
(Like:
Messing up wire en/decode methods.
And although I did tweak the consumer.cpp's sendPacket() method
(for initializing the field (whose value was added through SetAttribute
feature of helpers))
but I noticed later that ndn-consumer-zipf-mandelbrot.cpp overrides this
function and that was
creating all the confusion.)

For future reference if anyone struggles with this problem following are
the best ways:

   - Easiest is to (like Junxiao said)  put the field in Name or
   application parameter.
   - The tag method also works perfectly but it is too much efforts (Check
   this link <https://lo.calho.st/posts/ndnsim-custom-fields/>)
   - The proper method provided here
   <https://www.programmersought.com/article/14675398024/> also works
   perfectly (and is less hassle than tag method)

Thanking all of you again
Prajjwal Singh

On Wed, 5 May 2021, 06:28 Junxiao Shi, <shijunxiao at email.arizona.edu> wrote:

> Hi DJEMAA
>
>
> If the packet length doesn't matter in your configuration, I advise you to
>> add a Tag instead of a new Field to your packet, since according to ndnSIM
>> design, the tag resides only in the memory.
>> Also, a Tag can be easily managed directly in the NFD machinery
>> (forwarder class), contrary to a new field in either Interest or Data
>> packets which are generally static objects.
>>
>
> ndnSIM doesn't support ns3::Tag (the kind described in ns-3 model library
> https://www.nsnam.org/docs/release/3.33/models/html/packets.html#adding-and-removing-tags
> ).
> Subclasses of ndn::Tag are completely different from ns3::Tag. This
> includes the HopCountTag. They must be encoded into the packet buffer to
> have any effect.
>
>
>>> The main problem is that if i have the following topology
>>> A--B--C--D
>>> (Where A is the Consumer and D is the Producer, and B and C are routers)
>>> Then by the solution given in the above link the custom field set in A's
>>> generated Interest packet is reset to default value by B when it forwards
>>> the interest to C.
>>> How can I make it carry the value intended by A?
>>>
>>
> A *forwarded* Interest is actually a different packet from the original:
> Name, CanBePrefix, MustBeFresh, ApplicationParameters are copied over,
> InterestLifetime, Nonce, HopLimit are modified, and other fields may be
> discarded.
>
> As I said previously, it's best to include the information as part of the
> Name or ApplicationParameters, which is supported universally.
>
> While NDN protocol allows having unrecognized non-critical fields in the
> Interest packet, the protocol is vague on whether and what to preserve
> during forwarding.
> So far, as long as Name, CanBePrefix, MustBeFresh, ApplicationParameters,
> and any fields that appear after ApplicationParameters are preserved, the
> forwarder implementation would be interoperable.
>
> Yours, Junxiao
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210505/1f479e3d/attachment.html>

From csb17053 at tezu.ac.in  Wed May  5 07:15:00 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Wed, 5 May 2021 19:45:00 +0530
Subject: [ndnSIM] Safely removing Pit Entries on receiving new interest.
Message-ID: <CAOhxRamaRf2K6sbobHmAk5_422t9_RroJ9f5rVGNPXP-1uFOKg@mail.gmail.com>

Hello everybody,
I am trying to remove a few Pit Entries from the PIT on some basis when a
new interest packet arrives.

Please guide me which functions can I make use of to remove such entries.

Till now I have been doing the following:

I have added an extra data structure that keeps (Pit::Entry *) of pit
entries.
Then I am tweaking forwarder.cpp::onIncomingInterest() function to delete
entries.
I have tried to use the function m_pit.erase(pit_entry.get());
to delete entries.
But, at some point the simulation hangs when some other part of the code
tries
to delete the entry(which i have already deleted by my added code) and
gives me the error:
void nfd::pit::Pit::erase(nfd::pit::Entry*, bool): Assertion `nte !=
nullptr' failed.

Thanking you in advance,
Prajjwal Singh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210505/cb5d84ed/attachment.html>

From shijunxiao at email.arizona.edu  Wed May  5 07:23:01 2021
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Wed, 5 May 2021 10:23:01 -0400
Subject: [ndnSIM] [EXT] Safely removing Pit Entries on receiving new
 interest.
In-Reply-To: <CAOhxRamaRf2K6sbobHmAk5_422t9_RroJ9f5rVGNPXP-1uFOKg@mail.gmail.com>
References: <CAOhxRamaRf2K6sbobHmAk5_422t9_RroJ9f5rVGNPXP-1uFOKg@mail.gmail.com>
Message-ID: <CAOFH+OZXFK9SJnNHLBm0aNN3bRzMcXj4pdmToPgDdDRKHCZJfg@mail.gmail.com>

Hi Prajjwal

You may use Strategy::setExpiryTimer or Forwarder::setExpiryTimer, passing
zero as timer duration.
Strategy::rejectPendingInterest is a shorthand of this operation.
This would cause the PIT entry to be erased when the current packet
finishes processing.

Yours, Junxiao

On Wed, May 5, 2021 at 10:15 Prajjwal Singh <csb17053 at tezu.ac.in> wrote:

> *External Email*
> Hello everybody,
> I am trying to remove a few Pit Entries from the PIT on some basis when a
> new interest packet arrives.
>
> Please guide me which functions can I make use of to remove such entries.
>
> Till now I have been doing the following:
>
> I have added an extra data structure that keeps (Pit::Entry *) of pit
> entries.
> Then I am tweaking forwarder.cpp::onIncomingInterest() function to delete
> entries.
> I have tried to use the function m_pit.erase(pit_entry.get());
> to delete entries.
> But, at some point the simulation hangs when some other part of the code
> tries
> to delete the entry(which i have already deleted by my added code) and
> gives me the error:
> void nfd::pit::Pit::erase(nfd::pit::Entry*, bool): Assertion `nte !=
> nullptr' failed.
>
> Thanking you in advance,
> Prajjwal Singh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210505/51270849/attachment-0001.html>

From csb17053 at tezu.ac.in  Wed May  5 07:56:19 2021
From: csb17053 at tezu.ac.in (Prajjwal Singh)
Date: Wed, 5 May 2021 20:26:19 +0530
Subject: [ndnSIM] [EXT] Safely removing Pit Entries on receiving new
 interest.
In-Reply-To: <CAOFH+OZXFK9SJnNHLBm0aNN3bRzMcXj4pdmToPgDdDRKHCZJfg@mail.gmail.com>
References: <CAOhxRamaRf2K6sbobHmAk5_422t9_RroJ9f5rVGNPXP-1uFOKg@mail.gmail.com>
 <CAOFH+OZXFK9SJnNHLBm0aNN3bRzMcXj4pdmToPgDdDRKHCZJfg@mail.gmail.com>
Message-ID: <CAOhxRak4a7DEq2hX3LWaU4LZ+EiUUU+LS0jxpMm3_=vhrBVi9w@mail.gmail.com>

Dear Junxiao,
Thank you so much.
Forwarder::setExpiryTimer with 0ms worked like a charm.

Thanking you again,
Prajjwal Singh


On Wed, May 5, 2021 at 7:53 PM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Prajjwal
>
> You may use Strategy::setExpiryTimer or Forwarder::setExpiryTimer, passing
> zero as timer duration.
> Strategy::rejectPendingInterest is a shorthand of this operation.
> This would cause the PIT entry to be erased when the current packet
> finishes processing.
>
> Yours, Junxiao
>
> On Wed, May 5, 2021 at 10:15 Prajjwal Singh <csb17053 at tezu.ac.in> wrote:
>
>> *External Email*
>> Hello everybody,
>> I am trying to remove a few Pit Entries from the PIT on some basis when a
>> new interest packet arrives.
>>
>> Please guide me which functions can I make use of to remove such entries.
>>
>> Till now I have been doing the following:
>>
>> I have added an extra data structure that keeps (Pit::Entry *) of pit
>> entries.
>> Then I am tweaking forwarder.cpp::onIncomingInterest() function to delete
>> entries.
>> I have tried to use the function m_pit.erase(pit_entry.get());
>> to delete entries.
>> But, at some point the simulation hangs when some other part of the code
>> tries
>> to delete the entry(which i have already deleted by my added code) and
>> gives me the error:
>> void nfd::pit::Pit::erase(nfd::pit::Entry*, bool): Assertion `nte !=
>> nullptr' failed.
>>
>> Thanking you in advance,
>> Prajjwal Singh
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210505/bd5d65ac/attachment.html>

From a_djemaa at esi.dz  Wed May  5 15:46:04 2021
From: a_djemaa at esi.dz (DJEMAA Adel)
Date: Wed, 5 May 2021 23:46:04 +0100
Subject: [ndnSIM] [EXT]Re:  Adding new field in Interest Packet.
In-Reply-To: <CAOhxRanNLrUywXA3wV=4O9DVh7Of4QvqZMBHQhhvf6-4Cm=T2Q@mail.gmail.com>
References: <CAOhxRam7-Z3MnynqspsOZs4VB48=kSF+oBq=g3Sm2WJA_F6teg@mail.gmail.com>
 <CAKqeZG6AsovL5794pxMDHoR5zuY2VKr+EVaaVNsKbpHfUVcd8A@mail.gmail.com>
 <CAOFH+OZqJe-T-4KWEgU8+1cbiYt1LnYLzSWhHwY=QAJjNfnHiw@mail.gmail.com>
 <CAOhxRanNLrUywXA3wV=4O9DVh7Of4QvqZMBHQhhvf6-4Cm=T2Q@mail.gmail.com>
Message-ID: <CAKqeZG7BeE8X-RfOfLOKNQz7HRsmFAsZWYeBZZ4BWQxGf7Qfog@mail.gmail.com>

Dear Junxiao, thank you for the valuable clarification,
Hopefully, this helps ndnSIM community.
Yours, Djemaa

Le mer. 5 mai 2021 ? 03:19, Prajjwal Singh <csb17053 at tezu.ac.in> a ?crit :

> Thanks to Junxiao and DJEMAA ,
> Junxiao's suggestion is possibly the best, I tried and tested it and it
> works very well.
>
> I also tried the method provided in the aforesaid link
> <https://www.programmersought.com/article/14675398024/>, and it works!
> I had committed a few mistakes that led me into other results.
> (Like:
> Messing up wire en/decode methods.
> And although I did tweak the consumer.cpp's sendPacket() method
> (for initializing the field (whose value was added through SetAttribute
> feature of helpers))
> but I noticed later that ndn-consumer-zipf-mandelbrot.cpp overrides this
> function and that was
> creating all the confusion.)
>
> For future reference if anyone struggles with this problem following are
> the best ways:
>
>    - Easiest is to (like Junxiao said)  put the field in Name or
>    application parameter.
>    - The tag method also works perfectly but it is too much efforts
>    (Check this link <https://lo.calho.st/posts/ndnsim-custom-fields/>)
>    - The proper method provided here
>    <https://www.programmersought.com/article/14675398024/> also works
>    perfectly (and is less hassle than tag method)
>
> Thanking all of you again
> Prajjwal Singh
>
> On Wed, 5 May 2021, 06:28 Junxiao Shi, <shijunxiao at email.arizona.edu>
> wrote:
>
>> Hi DJEMAA
>>
>>
>> If the packet length doesn't matter in your configuration, I advise you
>>> to add a Tag instead of a new Field to your packet, since according to
>>> ndnSIM design, the tag resides only in the memory.
>>> Also, a Tag can be easily managed directly in the NFD machinery
>>> (forwarder class), contrary to a new field in either Interest or Data
>>> packets which are generally static objects.
>>>
>>
>> ndnSIM doesn't support ns3::Tag (the kind described in ns-3 model library
>> https://www.nsnam.org/docs/release/3.33/models/html/packets.html#adding-and-removing-tags
>> ).
>> Subclasses of ndn::Tag are completely different from ns3::Tag. This
>> includes the HopCountTag. They must be encoded into the packet buffer to
>> have any effect.
>>
>>
>>>> The main problem is that if i have the following topology
>>>> A--B--C--D
>>>> (Where A is the Consumer and D is the Producer, and B and C are routers)
>>>> Then by the solution given in the above link the custom field set in
>>>> A's generated Interest packet is reset to default value by B when it
>>>> forwards the interest to C.
>>>> How can I make it carry the value intended by A?
>>>>
>>>
>> A *forwarded* Interest is actually a different packet from the original:
>> Name, CanBePrefix, MustBeFresh, ApplicationParameters are copied over,
>> InterestLifetime, Nonce, HopLimit are modified, and other fields may be
>> discarded.
>>
>> As I said previously, it's best to include the information as part of the
>> Name or ApplicationParameters, which is supported universally.
>>
>> While NDN protocol allows having unrecognized non-critical fields in the
>> Interest packet, the protocol is vague on whether and what to preserve
>> during forwarding.
>> So far, as long as Name, CanBePrefix, MustBeFresh, ApplicationParameters,
>> and any fields that appear after ApplicationParameters are preserved, the
>> forwarder implementation would be interoperable.
>>
>> Yours, Junxiao
>>
>

-- 
Mr DJAMA Adel
Phd student
Ecole Militaire Polytechnique
Algiers 16046, ALGERIA
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210505/27f12cb8/attachment.html>

From zohanoor67 at gmail.com  Wed May  5 21:42:50 2021
From: zohanoor67 at gmail.com (Sonia)
Date: Thu, 6 May 2021 13:42:50 +0900
Subject: [ndnSIM] [EXT] Redundant code in Forwarder::onIncomingData
 pipeline?
In-Reply-To: <CAOFH+OY2CVhx_iv3z6LGiwD__5oZ8tgBtDc5AF2sZ9Mg5zYsBw@mail.gmail.com>
References: <CALzsXw7KrtyVFPbXM6z4OuaKkYphPoNAb+2RtVztQszCx2rigQ@mail.gmail.com>
 <CAOFH+OY2CVhx_iv3z6LGiwD__5oZ8tgBtDc5AF2sZ9Mg5zYsBw@mail.gmail.com>
Message-ID: <CALzsXw4Dvdj-qSfnUtEn0BUpZDa-YGKVUsEUfB2MSfLhVn6Fbw@mail.gmail.com>

Hi Junxiao,

I understand it now.

Thank you




On Fri, Apr 23, 2021 at 7:06 PM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Sonia
>
> The condition is testing whether there are more than one *PIT entry*, not
> downstream face.
> Strategy::afterReceiveData can be overridden in subclass, so it's not an
> exact duplicate.
> See https://redmine.named-data.net/issues/4290 for reasoning.
>
> Yours, Junxiao
>
> On Fri, Apr 23, 2021, 03:43 Sonia via ndnSIM <ndnsim at lists.cs.ucla.edu>
> wrote:
>
>> Hi,
>>
>> Please guide me if I am missing something.
>>
>> In onIncomingData pipeline when there is at least one PIT entry match (
>> if (pitMatches.size() == 1) { ....... )  it calls
>> Strategy.afterReceiveData() method and this method sends data to all
>> pending down streams via its this->sendDataToAll(pitEntry, inFace,
>> data); method.
>>
>> My question is then why the else statement (for multiple
>> downstream faces) is there in Forwarder::onIncomingData pipeline. Isn't
>> this code redundant as the  Strategy.afterReceiveData() method already have
>> implemented the same logic?
>>
>> My second concern is that I have run many scenarios (both p2p and adhoc)
>> and multiple strategies (including multicast and broadcast), but I always
>> get only one downstream face never got more than 1 pending downstream face.
>> I checked it in Forwarder log.
>>
>> Any quidance will be highly appreciated.
>>
>> Thanks
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210506/bbc2ad40/attachment.html>

From eric.binnendyk at student.nmt.edu  Fri May  7 21:11:55 2021
From: eric.binnendyk at student.nmt.edu (Eric Binnendyk)
Date: Fri, 7 May 2021 22:11:55 -0600
Subject: [ndnSIM] Neural networks in ndnSIM
Message-ID: <CA+YKtvJyRpTXTJ6aLbuTOFFjWz6rtohhTyaBo4nS+3aGzLQNxQ@mail.gmail.com>

Hi,

I'm trying to implement a neural network to do forwarding in ndnSIM. I know
this is possible to do in ndnSIM because these papers do it:
https://www.mdpi.com/1424-8220/18/10/3354/htm,
https://dl.acm.org/doi/pdf/10.1145/3229543.3229547.

Does anyone have any recommendations on how to implement a neural network?
If possible, I would like to do it in Python even though most of the ndnSIM
code is in C++. Is it possible to use the Python bindings to write a
forwarding strategy in Python, so that I can use a neural network library
like keras?

Eric
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210507/6d26f73f/attachment.html>

From shijunxiao at email.arizona.edu  Sat May  8 06:24:19 2021
From: shijunxiao at email.arizona.edu (Junxiao Shi)
Date: Sat, 8 May 2021 09:24:19 -0400
Subject: [ndnSIM] [EXT] Neural networks in ndnSIM
In-Reply-To: <CA+YKtvJyRpTXTJ6aLbuTOFFjWz6rtohhTyaBo4nS+3aGzLQNxQ@mail.gmail.com>
References: <CA+YKtvJyRpTXTJ6aLbuTOFFjWz6rtohhTyaBo4nS+3aGzLQNxQ@mail.gmail.com>
Message-ID: <CAOFH+ObzjZbMu8P9d2y=JiTMBMtFet4FHYw64vLFQn_5m1=K0A@mail.gmail.com>

Hi Eric


> I'm trying to implement a neural network to do forwarding in ndnSIM. I
> know this is possible to do in ndnSIM because these papers do it:
> https://www.mdpi.com/1424-8220/18/10/3354/htm,
> https://dl.acm.org/doi/pdf/10.1145/3229543.3229547.
>
> Does anyone have any recommendations on how to implement a neural network?
> If possible, I would like to do it in Python even though most of the ndnSIM
> code is in C++. Is it possible to use the Python bindings to write a
> forwarding strategy in Python, so that I can use a neural network library
> like keras?
>

Forwarding strategy is normally a C++ class that is called synchronously.
C++ code can invoke Python synchronously.
Implementing part of the forwarding strategy logic in Python wouldn't be
easy or performant, but I don't see major roadblock.
It would not be a "binding" though, because a "binding" typically refers to
calling C++ code from Python, not the other way around.

Another possibility is performing machine learning asynchronously.
In this approach, the forwarding strategy (C++) and the neural network
(Python) share a common data structure, but do not interact with each other
on a per packet basis.
The forwarding strategy makes immediate decisions based on what's already
in the data structure, and stores the outcome (e.g. satisfy ratio and RTT)
into the data structure.
The neural network periodically reads from the date structure, does its
magic, and writes to the data structure to influence future forwarding
decisions.

Yours, Junxiao

>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210508/10acd8f6/attachment.html>

From eric.binnendyk at student.nmt.edu  Sat May  8 12:52:43 2021
From: eric.binnendyk at student.nmt.edu (Eric Binnendyk)
Date: Sat, 8 May 2021 13:52:43 -0600
Subject: [ndnSIM] [EXT] Neural networks in ndnSIM
In-Reply-To: <CAOFH+ObzjZbMu8P9d2y=JiTMBMtFet4FHYw64vLFQn_5m1=K0A@mail.gmail.com>
References: <CA+YKtvJyRpTXTJ6aLbuTOFFjWz6rtohhTyaBo4nS+3aGzLQNxQ@mail.gmail.com>
 <CAOFH+ObzjZbMu8P9d2y=JiTMBMtFet4FHYw64vLFQn_5m1=K0A@mail.gmail.com>
Message-ID: <CA+YKtv+K3cfP9KRgZ8rrGH-E1QsW4ogoKjAQosZ_HFc0n2UnZA@mail.gmail.com>

Hi Junxiao,

Thanks so much for the reply. It really clears up some questions I had
about how to use ndnSIM. I'll probably implement it the asynchronous way
and have the C++ and Python code communicate using files.

Eric

On Sat, May 8, 2021 at 7:24 AM Junxiao Shi <shijunxiao at email.arizona.edu>
wrote:

> Hi Eric
>
>
>> I'm trying to implement a neural network to do forwarding in ndnSIM. I
>> know this is possible to do in ndnSIM because these papers do it:
>> https://www.mdpi.com/1424-8220/18/10/3354/htm,
>> https://dl.acm.org/doi/pdf/10.1145/3229543.3229547.
>>
>> Does anyone have any recommendations on how to implement a neural
>> network? If possible, I would like to do it in Python even though most of
>> the ndnSIM code is in C++. Is it possible to use the Python bindings to
>> write a forwarding strategy in Python, so that I can use a neural network
>> library like keras?
>>
>
> Forwarding strategy is normally a C++ class that is called synchronously.
> C++ code can invoke Python synchronously.
> Implementing part of the forwarding strategy logic in Python wouldn't be
> easy or performant, but I don't see major roadblock.
> It would not be a "binding" though, because a "binding" typically refers
> to calling C++ code from Python, not the other way around.
>
> Another possibility is performing machine learning asynchronously.
> In this approach, the forwarding strategy (C++) and the neural network
> (Python) share a common data structure, but do not interact with each other
> on a per packet basis.
> The forwarding strategy makes immediate decisions based on what's already
> in the data structure, and stores the outcome (e.g. satisfy ratio and RTT)
> into the data structure.
> The neural network periodically reads from the date structure, does its
> magic, and writes to the data structure to influence future forwarding
> decisions.
>
> Yours, Junxiao
>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/ndnsim/attachments/20210508/8b1c34cf/attachment.html>