[Mini-NDN] Follow-up: Successful Python-NDN Integration in Mini-NDN & Offer to Contribute Examples (Ref: GitHub Issue #80)

Wed Dec 17 13:27:02 PST 2025

Apologies on the slight delay. I have also sent some initial comments
regarding your initial submission. Thank you for following up with us.
-Alex

On Wed, Dec 17, 2025 at 1:48 PM Lan Wang (lanwang) via Mini-NDN <
mini-ndn at lists.cs.ucla.edu> wrote:

> Hi Yulong,
>
> Thank you for your contribution.  Ashlesh Gawande will review your patch.
>
> Lan
>
> On Dec 16, 2025, at 10:24, Yulong ZHANG <yzhang893 at connect.hkust-gz.edu.cn>
> wrote:
>
> Hi Mini-NDN Team,
> I have submitted a patch that adds a new example to the examples/
>  directory: *python-ndn Application-Layer Forwarding*.
> *Motivation:*
> While NFD handles network-layer forwarding, many researchers need to
> implement logic at the application layer (e.g., Interest interception, Name
> rewriting, or middlebox services).
> *What this example does:*
> It provides a clean, standalone implementation of a *Forwarder* node using
>  python-ndn that:
>
>    1. Intercepts traffic on a prefix.
>    2. Modifies the Name (Namespace mapping).
>    3. Proxies the request to a backend Producer and relays the Data back.
>
> *Technical Details:*
> The scripts are written to be *transport-agnostic*. They default to TCP
> (localhost:6363) for easy manual testing on a host machine but fully
> support Unix Sockets via the NDN_CLIENT_TRANSPORT environment variable
> for Mininet integration.
> Documentation and a README are included. I believe this will be helpful
> for users looking to integrate custom Python logic with Mini-NDN.
> Best regards,
> Yulong
>
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Lan
> Wang (lanwang) via Mini-NDN <mini-ndn at lists.cs.ucla.edu>
> *Sent:* Monday, October 27, 2025 7:41 PM
> *To:* mini-ndn at lists.cs.ucla.edu <mini-ndn at lists.cs.ucla.edu>
> *Subject:* [Mini-NDN] Fwd: Follow-up: Successful Python-NDN Integration
> in Mini-NDN & Offer to Contribute Examples (Ref: GitHub Issue #80)
>
>
> Begin forwarded message:
>
> *From:* "Alexander Wilhelm Lane (awlane)" <awlane at memphis.edu>
> *Date:* October 26, 2025 at 16:05:57 CDT
> *To:* Yulong ZHANG <yzhang893 at connect.hkust-gz.edu.cn>, "Lan Wang
> (lanwang)" <lanwang at memphis.edu>, "mini-ndn at lists.cs.ucla.edu" <
> mini-ndn at lists.cs.ucla.edu>
> *Subject:* *Re: Follow-up: Successful Python-NDN Integration in Mini-NDN
> & Offer to Contribute Examples (Ref: GitHub Issue #80)*
>
> 
> Hi Yulong,
>
> That is perfectly acceptable. I will try and make sure that myself or
> someone else is able to promptly give feedback and merge this into Mini-NDN
> at that time.
>
> Thanks,
> Alex Lane
>
> Get Outlook for Mac  <https://aka.ms/GetOutlookForMac>
> *From: *Yulong ZHANG <yzhang893 at connect.hkust-gz.edu.cn>
> *Date: *Sunday, October 26, 2025 at 3:10 AM
> *To: *Lan Wang (lanwang) <lanwang at memphis.edu>, mini-ndn at lists.cs.ucla.edu
>  <mini-ndn at lists.cs.ucla.edu>, Alexander Wilhelm Lane (awlane) <
> awlane at memphis.edu>
> *Subject: *Re: Follow-up: Successful Python-NDN Integration in Mini-NDN &
> Offer to Contribute Examples (Ref: GitHub Issue #80)
>
> Dear Alex,
> Thank you very much for your kind response and for providing the
> contribution guidelines. I’d be very happy to contribute and prepare the
> RST-formatted document as suggested.
> However, I currently have two urgent deadlines for meetings before
> November 21, so I may not be able to organize everything properly until
> then. Would it be okay if I send you the finalized version after that date?
> Thank you again for your time and for offering to help. I really
> appreciate it and look forward to contributing to Mini-NDN.
> Best regards,
> Yulong Zhang
>
> ------------------------------
> *From:* Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of
> Alexander Wilhelm Lane (awlane) via Mini-NDN <mini-ndn at lists.cs.ucla.edu>
> *Sent:* Saturday, October 25, 2025 12:20 AM
> *To:* Lan Wang (lanwang) <lanwang at memphis.edu>; mini-ndn at lists.cs.ucla.edu
>  <mini-ndn at lists.cs.ucla.edu>
> *Subject:* Re: [Mini-NDN] Follow-up: Successful Python-NDN Integration in
> Mini-NDN & Offer to Contribute Examples (Ref: GitHub Issue #80)
>
> You don't often get email from mini-ndn at lists.cs.ucla.edu. Learn why this
> is important <https://aka.ms/LearnAboutSenderIdentification>
> Hi Yulong,
>
> I appreciate the follow up. This document gives the general flow of
> contributing to Mini-NDN; we do not include unit tests in Mini-NDN.
> https://github.com/named-data/.github/blob/main/CONTRIBUTING.md
>
> Our Gerrit is located here:
> https://gerrit.named-data.net/admin/repos/mini-ndn,general
> And Redmine is located here:
> https://redmine.named-data.net/projects/mini-ndn
>
> If you can write this up and format as an RST file (
> https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html)
> and submit as a patch, I would be happy to have you added to the
> contributors file which should list you as a contributor (and can label
> this specific contribution if you would like). I am somewhat tight on time
> for the next week, but I will try my best to answer any questions or help
> with any issues you run into in a timely manner.
>
> Thanks,
> Alex Lane
>
> Get Outlook for Mac <https://aka.ms/GetOutlookForMac>
> *From: *Mini-NDN <mini-ndn-bounces at lists.cs.ucla.edu> on behalf of Lan
> Wang (lanwang) via Mini-NDN <mini-ndn at lists.cs.ucla.edu>
> *Date: *Friday, October 24, 2025 at 11:09 AM
> *To: *mini-ndn at lists.cs.ucla.edu <mini-ndn at lists.cs.ucla.edu>
> *Subject: *Re: [Mini-NDN] Follow-up: Successful Python-NDN Integration in
> Mini-NDN & Offer to Contribute Examples (Ref: GitHub Issue #80)
>
> *CAUTION: This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and trust
> the content is safe.*
>
> Yulong,
>
> Your contribution to Mini-NDN is very welcome.  I hope Alex Lane and
> others can help you include the python-NDN examples into the MIni-NDN
> repository.
>
> Lan
>
> On Oct 24, 2025, at 11:01, Lan Wang (lanwang) <lanwang at memphis.edu> wrote:
>
> This email was previously discarded as the sender was not a subscriber.
> I’ve added the sender to the mailing list and am forwarding the email to
> the mailing list.
>
> Lan
>
> Begin forwarded message:
>
> *From: *mini-ndn-bounces at lists.cs.ucla.edu
> *Subject: Auto-discard notification*
>
> *From: *Yulong ZHANG <yzhang893 at connect.hkust-gz.edu.cn>
> *Subject: **Follow-up: Successful Python-NDN Integration in Mini-NDN &
> Offer to Contribute Examples (Ref: GitHub Issue #80)*
> *Date: *April 14, 2025 at 08:28:06 CDT
> *To: *"mini-ndn at lists.cs.ucla.edu" <mini-ndn at lists.cs.ucla.edu>
>
>
> Dear Mini-NDN developers and community,
> My name is Yulong Zhang,  a third-year PhD student from The Hong Kong
> University of Science of Technology (HKUST) under the supervision of Prof.
> Dirk Kutscher.
> I'm writing to follow up on a discussion initiated in GitHub Issue #80 ([
> https://github.com/named-data/mini-ndn/issues/80]). In that issue, I
> inquired about the support for python-ndn (
> https://python-ndn.readthedocs.io/) within the Mini-NDN environment.
> Awlane kindly responded, clarifying that while python-ndn applications
> are generally supported, direct wrappers or integration examples at the
> Mini-NDN layer were not currently available, and contributions in this
> direction would be appreciated. Awlane also recommended using this mailing
> list for further discussions.
> I'm pleased to report that, following that exchange, I have dedicated some
> time to this and have successfully managed to set up and run NDN
> applications developed using python-ndn within Mini-NDN experiments. I've
> worked through the practical steps required to integrate and execute these
> applications effectively in the simulated environment.
> Recognizing that others in the community might also be interested in
> leveraging python-ndn with Mini-NDN, I believe sharing concrete examples
> and perhaps a brief guide could be quite valuable. These examples could
> demonstrate how to:
>
>    1. Structure a python-ndn application for use within Mini-NDN.
>    2. Potentially handle dependencies or environment setup within the
>    Mini-NDN nodes.
>
> Therefore, I would be very happy to prepare and share these implementation
> details and practical examples. My hope is that they could potentially be
> refined and incorporated into the official Mini-NDN documentation, perhaps
> as a tutorial or a dedicated section on using different NDN application
> libraries.
> If these examples and potential documentation updates are found useful by
> the project and are incorporated,*would it be possible for me to be
> acknowledged as a contributor to the Mini-NDN project for this specific
> work?*
> Thank you for your time, consideration, and the excellent work on
> Mini-NDN. I look forward to hearing from you regarding this proposal.
> Best regards,
> Yulong
>
>
> _______________________________________________
> Mini-NDN mailing list
> Mini-NDN at lists.cs.ucla.edu
> https://www.lists.cs.ucla.edu/mailman/listinfo/mini-ndn
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.lists.cs.ucla.edu/pipermail/mini-ndn/attachments/20251217/5d6a2501/attachment-0001.htm>