Hi all, Thank you all for the feedback on the draft! After some discussion, we have published a new version of the draft: https://datatracker.ietf.org/doc/draft-ramseyer-grow-peering-api/04/.
I, along with some of my collaborators (cc’d), will be at the IETF 119 meeting in Brisbane this week. As proposed below, I believe this may fall under the GROW charter, and so, we will present at the group meeting on Wednesday. I look forward to the discussion there. We have also scheduled a side meeting on Thursday at 14:00-15:00 to discuss further—please join us if you are interested! It will be in Room M9, and I believe there will be a web link as well. Please let us know if you have any comments! I look forward to meeting some of you in Brisbane. Jenny From: GROW <[email protected]> on behalf of Jenny Ramseyer <[email protected]> Date: Friday, January 19, 2024 at 4:20 AM To: [email protected] <[email protected]> Cc: Matt Joras <[email protected]> Subject: [GROW] Peering API: Internet Draft submission Hello GROW, I’m Jenny Ramseyer, from Meta. I have just submitted an Internet Draft, which I would like to share for your review. I believe it falls under the GROW working group’s charter. Here is the draft: https: //datatracker. ietf. org/doc/draft-ramseyer-grow-peering-api/ ZjQcmQRYFpfptBannerStart This Message Is From an External Sender ZjQcmQRYFpfptBannerEnd Hello GROW, I’m Jenny Ramseyer, from Meta. I have just submitted an Internet Draft, which I would like to share for your review. I believe it falls under the GROW working group’s charter. Here is the draft: https://datatracker.ietf.org/doc/draft-ramseyer-grow-peering-api/<https://datatracker.ietf.org/doc/draft-ramseyer-grow-peering-api/> In this draft, I outline a proposed standard for programmatically configuring BGP peering connections through a machine-to-machine API. With this work, I and my collaborators hope to standardize and simplify peering automation, and encourage fast, reliable, and cost-effective interconnection for networks. This work started as an extension of an earlier NANOG85 presentation: https://youtu.be/Cko5-lWyN60?si=4w_ZicpGIgGoyaTR<https://youtu.be/Cko5-lWyN60?si=4w_ZicpGIgGoyaTR>. Out of that presentation, we established a discussion group, and presented an early proposal at NANOG88: https://youtu.be/kMxsoplROYs?si=nKvkkL9aXa8pjAGw<https://youtu.be/kMxsoplROYs?si=nKvkkL9aXa8pjAGw> This draft is built from the discussions through that group, and is joint work with my collaborators at AWS, Cloudflare, Google, and FullCtl. As we are proposing a standard way to automate BGP interconnections with the goal of simplifying and encouraging peering, I am hoping that it would fall under your charter’s second goal: “Document and suggest operational solutions to problematic aspects of the currently deployed routing system.” I would like to request a talking slot at the upcoming GROW meeting at IETF 119 to discuss the draft. Please let me know if you think this draft might meet your charter, and if it would be possible to discuss at the next GROW meeting. Thank you, Jenny Ramseyer
_______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
