Subject: Re: [httpapi] Getting ready for our first meeting at IETF 109

From: "Salz, Rich" <[email-masked]>
Date: Fri, 20 Nov 2020 22:02:23 +0000

Thanks everyone for a highly useful meeting!

Please take a minute to review the minutes at https://codimd.ietf.org/notes-ietf-109-httpapi# and post corrections to the list.  Thanks again to Bron who multitasked by listening, taking detailed notes, and participating in the Jabber stream.

The GitHub stuff is being set up; Mark will send email when it’s ready.  He’s now officially our group Secretary.

About one-third of the people were new to the IETF. Let’s grow that percentage :)  Reach out to your colleages in the API space and encourage them to join the mailing list and look at the links.

I’ll followup with some of my action items in separate email threads next week.  Stay safe and healthy everyone!

Rich, for the Chairs.

From: "Salz, Rich" <rsalz=[email-masked]>
Date: Thursday, November 12, 2020 at 10:56 AM
To: "[email-masked]" <[email-masked]>
Subject: [httpapi] Getting ready for our first meeting at IETF 109

Welcome to the HTTP-API working group!

This is an IETF Working Group (WG) that operates under the IETF rules. If you are familiar with them, skip to the next paragraph. A good overview of how a WG works can be found at https://www.ietf.org/about/participate/tao/#wgs  The IETF operates under a set of rules called the "Note Well" which can be found at https://www.ietf.org/about/note-well/  That basically says "no hidden patents" and "treat everyone respectfully." The official WG "home" is at https://datatracker.ietf.org/wg/httpapi and that will have links (under the meetings or documents tab) to most of the useful stuff.

We have a charter which identifies our scope of work. It is at https://datatracker.ietf.org/doc/charter-ietf-httpapi/  It's worth reviewing.

The agenda has been uploaded and is at https://datatracker.ietf.org/meeting/109/materials/agenda-109-httpapi-00  Note that the first item of business will be: to what extent (if any) do we want to conduct business on GitHub?  There was a WG that came up with several modes of operation; please see https://www.rfc-editor.org/rfc/rfc8874.html  Other valid responses include "all in, like QUIC" or "partial like TLS"

If anyone is interested in helping take minutes or being the Jabber scribe, please post. If you are not familiar with the videoconf tool the IETF uses, take a look at https://www.ietf.org/media/documents/IETF109-Meetecho_Documentation.pdf<https://urldefense.com/v3/__https:/www.ietf.org/media/documents/IETF109-Meetecho_Documentation.pdf__;!!GjvTz_vk!F8n7W1GDslO-E3x-whURGi25kROwsp7i8o-f16StD00rHyVB3a95qInQGE-3$>

At the meeting we'll review some candidate documents and make preliminary decisions about which one(s) to adopt. Other documents can also be brought up on the mailing list. The chairs will probably solicit submissions to cover other items in our charter if there's no candidates.