On Fri, Jan 19, 2024 at 11:55 AM Jenny Ramseyer <[email protected]> wrote: > > Thank you, I have joined the list now. > > > > I look forward to discussing with you all—please do let me know if anyone has > any feedback or questions on the draft. I’ll be at the IETF 119 meeting, and > hope to meet some of you there. > >
I was corrected off list by a different reader/wg-member... howdy this is JENNY not JEREMY. I hope to have new glasses (srsly) before the next meeting ;( <shamecube> > > Thanks! > > > > Jenny > > > > From: GROW <[email protected]> on behalf of Christopher Morrow > <[email protected]> > Date: Thursday, January 18, 2024 at 11:34 PM > To: Jenny Ramseyer <[email protected]> > Cc: [email protected] <[email protected]>, Matt Joras <[email protected]> > Subject: Re: [GROW] Peering API: Internet Draft submission > > !-------------------------------------------------------------------| > This Message Is From an Untrusted Sender > You have not previously corresponded with this sender. > |-------------------------------------------------------------------! > > Jeremy, you'll want to take a moment to join the mailing-list... else > someone will have to keep accepting your mails in the mailman > interface :) > (delaying and unnecessarily gatekeeping your part of the conversation) > > thanks! > -chris > (also, thanks for the submission!) > > On Thu, Jan 18, 2024 at 11:32 PM Jenny Ramseyer > <[email protected]> wrote: > > > > Hello GROW chairs, > > > > > > > > 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/ > > > > > > > > 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 . Out of that > > presentation, we established a discussion group, and presented an early > > proposal at NANOG88: 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 > > _______________________________________________ > GROW mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
