Seeking Presentations on These Topics

Call for Presentations

There are topics where we are seeking a knowledgeable person to make slides and present to people who are trying to understand the topic:

• DHT
• secio
• libp2p connection flow
• IPNS

If you can tackle on these, open a new issue describing your presentation (use the issue template) and then check it off here.

/cc @hsanjuan

@whyrusleeping @Stebalien @Kubuxu @lgierth @diasdavid @vasco-santos @jacobheun You all are knowledgeable people on libp2p topics. Can you help here?

[vasco-santos]

Hello @mgoelzer ,

I am available for creating a presentation regarding the IPNS topic. I will create an issue during this week.

[hsanjuan]

To follow up on ipfs-inactive/conf#43 (comment) . I'd expect these to be presentations (as long as needed by the presenter), going deep on the current and planned implementations of these topics. The questions to be answered:

• Where is it implemented? On what pieces does it build on?
• Who's made the major contributions to this code and when?
• How does it work? Where is the trickiest logic in it and what does it do?
• Where is it used, how is it used in the IPFS ecosystem?
• What problems does it currently have and why? What major problems did it have in the past that were fixed and how did they affect us?
• What things are we planning to fix, change, improve in the short term? and in the long term?
• What do the proposed solutions look like and how will the improve it?

Depending on the topic, these questions will be addressed differently (using more or less time).

To the list, we can add:

• Pubsub
• Consensus/Raft (if interested)
• Unsure if deserves a full separate space or can go in "connection flow": libp2p multiplexing and muxers
• Would be interesting to dedicate some time to libp2p transports, how they plug into the stack, and where we are in things like Quic or Bluetooth
• Routing (maybe with DHT)

@vasco-santos Thank you! I already created a placeholder issue for IPNS. But @lgierth raised a good point -- is this more of an IPFS Dev Meeting topic than libp2p?

If yes, can you think of a different libp2p topic to present on? (See @hsanjuan's list above, or propose your own.)

You can still do an IPFS talk, but it should be submitted through the IPFS Dev Meeting submission process here.

[jacobheun]

@mgoelzer I can present on libp2p connection flows

@jacobheun Thank you! I assigned the placeholder #12 to you. Can you take a second to fill it in? (length of presentation, title, a couple sentence abstract for the Sched.com description)

[jacobheun]

I've updated the issue, feedback on the abstract is welcomed :)

[vasco-santos]

@mgoelzer I consider IPNS a separate piece of ipfs, since it uses libp2p as ipfs does, that is, it uses it as its building blocks.

We have been discussing that topic here. Can you provide feedback there?

@vasco-santos I read the other issue; thanks for pointing it out. I see both sides and I didn't feel I had much to contribute to the IPFS vs libp2p discussion there, so I didn't comment.

Given that there is debate on both sides, I propose that you go ahead with IPNS as a topic for libp2p. I assigned topic #15 for you to fill in a few more details.

[daviddias]

Independently on where IPNS falls (IPFS/libp2p) it is still good to discuss it in libp2p context because it is at minimum a user of libp2p (PubSub + DHT + IPRS) and libp2p should provide the primitives for it.