[Protocol Design] libp2p testbed and network simulations

[ghost]

libp2p simulations

Name: @b5

Length (choose one): 1 hour discussion meeting

Title (~1-7 words): Exploring P2P Through simulation

Abstract (1 sentence up to a couple paragraphs, as you prefer): In this session I'll present a 10 minute overview of our technique for using lib-p2p network simulations at qri to build & iterate on p2p concepts using request tracing in conjunction with local networking. We'll use this as a starting point for discussing best practices for presenting & iterating on networking solutions, with the goal of refining a document that attempts to distinguish, enumerate, and label different approaches to p2p network simulation, outlining strengths, weakness, and examples.

Point of context for this discussion may include:

• machine-local simulation
• the intersection of testing and simulations
• container-based network simulations
• cryptocurrency test networks
• language-agnostic & multi-language enviornments
• how the different layers of libp2p map to each approach

[daviddias]

Description of the intended format here ipfs-inactive/conf#43

[b5]

I'd be happy to take this one if noe one else is interested! Might be a good excuse to put some more time into making this example repo usable for others.

[ghost]

@b5 You own it! Just fill in the original issue. Title, abstract. Also, can you make this 90 minutes (40 + break + 40). Most people are saying that you need at least 90 min to really get deep into a protocol.

As moderator of this discussion, bring code is way beyond your moderator responsibilities (which are just to lead the discussion and get the group to produce an RFC output doc), but it's awesome if you can bring 💥working code 💥!

[ghost]

(In case it's not clear, we need title and abstract mainly for Sched. So, nothing fancy required, just give me a paragraph I can put in the Sched schedule so people have a general idea of what this group will discuss. Thanks!)

[b5]

Sure thing. I'm getting a better grasp of what this session is intended for. I'll work out title & abstract in the next few hours, and try to work up an outline this weekend.

[daviddias]

❤️ @b5

[ghost]

@b5 Can you take just a moment to fill in a sentence or two of text in the issue description? Then I can mark this ready-to-schedule and get it onto the calendar!

[b5]

so sorry for the delay on this. I'm just getting back from some 🇨🇦 day time off.

Length (choose one): 1 hour discussion meeting

Title (~1-7 words): Exploring P2P Through simulation

Abstract (1 sentence up to a couple paragraphs, as you prefer): In this session I'll present a 10 minute overview of our technique for using lib-p2p network simulations at qri to build & iterate on p2p concepts using request tracing in conjunction with local networking. We'll use this as a starting point for discussing best practices for presenting & iterating on networking solutions, with the goal of refining a document that attempts to distinguish, enumerate, and label different approaches to p2p network simulation, outlining strengths, weakness, and examples.

Point of context for this discussion may include:

• machine-local simulation
• the intersection of testing and simulations
• container-based network simulations
• cryptocurrency test networks
• language-agnostic & multi-language enviornments
• how the different layers of libp2p map to each approach

[b5]

also, if I could put in a request to present either on Thursday or earlier on Friday, that'd be lovely. my schedule is a little up in the air on Friday afternoon. Thanks!

[ghost]

Thanks, I've marked it ready to schedule and updated the issue description.

Understood on the scheduling. It actually should work out by default, because I am trying to do most of these pre-planned sessions and presentations on Thursday and Friday morning, with Friday afternoon reserved as un-conference / spontaneous meetings.

[daviddias]

Please drop your notes to https://github.com/libp2p/developer-meetings/tree/master/notes