Skip to main content

Minutes IETF115: icnrg: Tue 13:00
minutes-115-icnrg-202211081300-01

Meeting Minutes Information-Centric Networking (icnrg) RG
Date and time 2022-11-08 13:00
Title Minutes IETF115: icnrg: Tue 13:00
State Active
Other versions markdown
Last updated 2022-11-23

minutes-115-icnrg-202211081300-01

ICNRG Meeting at IETF-115 – 2022-11-08, 13:00 to 14:30 UTC

Notes: Matthias Wählisch

ICNRG Agenda
1 ICNRG Chairs’ Presentation: Status, Updates Chairs 10 min
2 FLIC Update Marc Mosko 20 min
3 Vessel Container Format Jens Finkhäuser 20 min
4 Cefore: CCNx-based Cloud-native Network Function for Deploying ICN as
a Service Yusaku Hayamizu 20 min
5 RESTful ICN Dirk Kutscher 15 min
6 Buffer, Wrap Up and Next Steps Chairs 05 min
Please remember that all sessions are being recorded.

Drafts
https://datatracker.ietf.org/doc/draft-irtf-icnrg-flic/
https://specs.interpeer.io/draft-jfinkhaeuser-vessel-container-format/

https://datatracker.ietf.org/doc/draft-irtf-icnrg-pathsteering/

Ping & Traceroute & Pathsteering
We should get Pathsteering to RG last call expeditiously. Please review
the current RG draft and let the chairs know if there are things needed
to be addressed before RG last call!

FLIC discussion:
Dirk Kutscher: emphasizes that this is an important mechanism. RG want
to
publish this soon.
Ken Calvert: Volunteered to review the Draft. Has a student who works on
an implementation, hopefully ready beginning of next year.
DK: @Marc, are you aware of any other implementations?
MM: There was one other implementation, but not sure about the current
state.
DK: Has a Clojure prototype. Happy to handover this implementation to
other
groups.

Vessel Container Format
Ryo Yanagida: Clarification question: The scope is to use container to
bring ICN functionalities to a system.
Jens Finkhäuser: We are building our own software stack that reads close
to an ICN-like solution, but there is potential for other use cases.
RY: How do you approach the right to forget data?
JF: We emphasize offline-first because constant connectivity is not a
requirement we want to rely on, since Internet connectivity is not
equally deployed in all countries. Asking a cache to delete content is
difficult because you don't know which caches store a copy of the
content.
Dave Oran: Not a problem because the cache doesn't have the key to
decrypt the cached data.
JF: As long as the cryptography is not broken, you are right.
DO: If the cryptography doesn't hold, you have other problems anyway.
Secure Scuttlebutt is related.

Cefore: CCNx-based Cloud-native Network Function for Deploying ICN as
a Service

Ryo Yanagida: What kind of sensor node did you use?
Yusaku Hayamizu: We used a Raspberry PI to run the docker image.
RY: How do you build your binaries: Do you use a single code base, which
you configure to build separate binaries, or do you have dedicated code
bases to create lightweight binaries?
YH: We have a single code base and create separate binaries based on
configure options.
Ayoub Messous: What was the difference between normal HTTP-like video
streaming and your use case?
YH: ICN acts hop-by-hop and provides in-network caching, which both ease
loss recovery and lead to better quality compared to HTTP streaming.

RESTful ICN
Questions postponed to mailing list.

Buffer, Wrap Up and Next Steps