Minutes IETF122: icnrg: Mon 10:00
minutes-122-icnrg-202503171000-01

Preechai from intERLab/AIT gave a talk on Offline content delivery ..

• using offline content delivery in remote area
• using Device to Device communication for content delivery. The
  prototype has been built using google nearby conn API
• distanace coverage upto 150 meters with maximum throughput xxx
• integrate NDN over D2D by using NDN for content discovery and
  retieval in multi-hop environment
• Present some limitations of D2D and proposed the solution of NDN
  with some modifiations
• Current implementation focusses on Andriod
• NDN over D2D architecure - propose Content Manager for content
  delivery , D2D Manager manages D2D faces abd forwarding NDN message
  over D2D
• present the proof of concept implementation NDN over D2D

• Key takeaways

  • showcasing the important of ICN for content delivery management

• Future plan- will have real-deployment in April -May 2025

  • App: virtual classroom , file exchange
  • Acknowlege to THNICF for research grant support

Q Thomas Schmidt: suggest that you look at lower layer connection
management capabilities to solve the problem
Q: How long for the Interest lifetime?
A: it could be 1-20 min depending on type of the contents and network
topology
Q: There are some implementation on RasPI why not we use them?
A: Phone is more available
Q: Why you choose ICN/NDN?
A: want to use some existing standards
Q: Is there are some complexity of D2D scenario, how to advertise the
content information? which device has which contnet.
A: We use NDN to broadcast the content availability
Comment [Lixia Zhang]: Have you considered Security? Important to do
so.

Marc Mosko - Update on FLIC

• highlights the updates on the Draft
• Clarification about non-tree FLICs, manifest brnach may have
  multiple parents
• ANNF updates more on security section
• KDF updates
• RSA updates - key wrapping session.
• Padding - use CCNx T_Pad field RFC..
• Security consideration - RSA
• Implementation status - ccnpy is in the pipeline

• Experiments on de-duplicaton:

  • every time you find the chunk has same content in the manifest
  • Emacs29 tar file 66% saving

• Sumamry The 07-draft is almost ready for final review
  Comment from [Dave Oran] : we have been working on FLIC for long
  time. We will be issuing RG last call to the mailing list next week

Marc Mosko - CCNx chunking protocol

• summary: preamble chumks not used for payload - use this for more
  control of how to find last chunk
• We believe that the draft is technically done but needs some a bit
  clean up

Marc Mosko CCNx Versioning protocol

• original CCNx used a timestamp version with a %FD
• define a T_version name segment type
• Consumer can query the current version (versioned name)
• Multiple versions - can add it in namespace

• Version discovery

  • Version request -
  • Version response

• CCNx Link rationale - consumer may only know the name of the content
  by producer will respond with version name

Dave : We will push people to carefully look at this draft.

Dave Oran - Reflexive Forwarding ...

• main work carried on by Hitoshi

• Why we need this ? there are important use cases for multi-way
  handshakes.

  • IoT sensor - polling to the node, IoT pushing the content
  • peer State synchronisation
  • We cannot do these conveniently through two-way handshakes

• Reflexive forwarding

• Current status

  • Draft 01 submitted on 16 March
  • learning how to implement via Cefore forwarder by NICT team

• Closed issues in v.01

  • what type of data that producer try to fetch from consumer
  • How to construct the reflexive Interest exchange ? try to
    clarify in the draft

• Trigger Interest there are two options

  • Use the Reflexive Name segment type used in the Reflexive
    Interest
  • define separate TLV
  • What are pros and cons of the provided options? Some discusion
    in thr draft - please review

• The draft needs wider reviews from the ICNRG. We need to see more
  implementations

Aijun - Progress of DMSC

• aims to solve the problem of service mesh.
• service mesh depends on ... proxy
• there are a lot performance Overhead.
• BoF WG - want to setup new WG?

• Scope of DMSC

  • coperate with network vendors

• Organize symposuim of DMSC in Beijing MArch 2025

• Final aim of this WG, emerge
• Plan - side Meetin/BoF in IETF 123 , established WG in 124
  Q (Dirk): Container is crucial element of your design?
  A : Also can be used for other objects
  Q Are you trying to replace existing Microservice or redesign the
  new architecture ?
  A: there will be a Gateway for translation.
  Q: Have you include genrative AI in your system>?
  A: (not clear)
  Q: How you interact DMSC WG to this ICNRG?

will be interesting how to porting the ICNRG to microservice

Q: DO you want to standardise content based routing ?

Wrap up

• NDN community meeting in April 2025
• NExt meeting in MAdrid July 2025