From nobody Mon May 3 11:18:54 2021 Return-Path: X-Original-To: httpapi@ietfa.amsl.com Delivered-To: httpapi@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 604263A1F3C for ; Mon, 3 May 2021 11:18:52 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.896 X-Spam-Level: X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=amundsen-com.20150623.gappssmtp.com Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4kAnKXJcP-3s for ; Mon, 3 May 2021 11:18:47 -0700 (PDT) Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52E1C3A1F3A for ; Mon, 3 May 2021 11:18:47 -0700 (PDT) Received: by mail-oi1-x22d.google.com with SMTP id l6so6299104oii.1 for ; Mon, 03 May 2021 11:18:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amundsen-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b0lRn80bJWUSYf0tgNy7XL9ds0ahCmH4I4Thii146Zw=; b=eYE2lQZ1+ijk0HZxR/7qP+0K213+GqREvzgKNnbYyzmNWKvSyqyfqZl/HfZ/SChIsa /Pi8TYIygAnFXgbLYpt1fSJzPR0Fq3QSqLrofnir7dcN/U6RQP/zoCc9Jh4Cv00/3Czz GFizICtGQo2a5EJGBVgLMy8O0eR2smwVOn1CUgBupm76ZFoA/oSAWE8vljJQJppnOnzO bAEvZ+hrfiAtfyQoPi88dJn8C+vXi/1UgnAiEbQp4cV805ZG0GmQAHF38NKghrK5hPfV PCKe/wBNTQJJ8LuJq9Liid3jsM7nAFddGemp2F2F9MU9/olJ4hHlr3/+psLx+s/6n0E/ 3Bbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b0lRn80bJWUSYf0tgNy7XL9ds0ahCmH4I4Thii146Zw=; b=a01CLq/rtu8KNM+kP3ycoo8I1Au9tIOlQ+UNVsZ+u2wiTc9idK0Z9xLCeswNQ3cpH5 W3JhtWmvX6dFgWrEqpw5/cHb9ILDrGcVYoos7zKnAph095AN+DfIA3+750tjdQ4ko812 psWveYQogydTCkD71wKAMZIam0CXbafvew+N5xgDhp9JwC1/FOFfL/ois5FA5huh1zY1 SgU4Nlhf2fCikO2vCIYHAQBfzvydYm6/Oyu8bewTvRCWhh9C5SH+AB/zjef0uHey3hPq rYa3tZ7zAa1DiGeBuFZ46W4IWWjIZIs2ffzLitla/5TxitfmdwmGy+GdNaeBC9BflkUo EEoQ== X-Gm-Message-State: AOAM533NX9cnAMO6qmtuCHM9TXKk6yM+DlB3zSOZ4MyLLMvvNgGOm/zn LDfXJFXOXD7ku5ix5897d9tK5cmZrWJIKmAVpMkxBUIwSb5ZUDxe X-Google-Smtp-Source: ABdhPJwtQZAcONfDg2hP0cYk4Oaha8zpnIIyuLKrtLnV0PyPH3y4K2UN5lnrrcR5EPuMHOzZ0pk9wMK0NGtth7i8XT8= X-Received: by 2002:a05:6808:3c8:: with SMTP id o8mr21860908oie.94.1620065925724; Mon, 03 May 2021 11:18:45 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: mca Date: Mon, 3 May 2021 14:18:31 -0400 Message-ID: To: "Salz, Rich" Cc: "httpapi@ietf.org" Content-Type: multipart/alternative; boundary="0000000000000411a505c170fe52" Archived-At: Subject: Re: [httpapi] Call for topics X-BeenThere: httpapi@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Building Blocks for HTTP APIs List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 May 2021 18:18:52 -0000 --0000000000000411a505c170fe52 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I and a small group of folks have been working on a profile-related specification (and accompanying tooling) https://datatracker.ietf.org/doc/draft-amundsen-richardson-foster-alps/ would be happy to discuss if this looks like something the group would be interested in. Mike Amundsen *APIs, Microservices, and Digital Transformation* 7310 Turfway Rd. Suite 550, Florence, KY, 41042 *+1.859.372.6517* https://zoom.us/j/8593726715 http://linkedin.com/in/mamund http://g.mamund.com/meetme http://training.amundsen.com http://twitter.com/mamund On Mon, May 3, 2021 at 12:34 PM Salz, Rich wrote: > The next IETF meeting will be, no surprise, virtual. It=E2=80=99s schedul= ed for > the end of July. At this point the chairs have to request a meeting slot. > We have the option of one or two hours. We=E2=80=99re probably going to g= o for two > hours, but might end our session early. (That=E2=80=99s not asking peopl= e to not > talk, it=E2=80=99s just pointing out that if we run out of group discussi= on, we=E2=80=99ll > just stop. :) > > > > We have four documents in progress, https://github.com/ietf-wg-httpapi or > https://datatracker.ietf.org/wg/httpapi/documents/. There=E2=80=99s been = a flurry > of discussion recently. Let=E2=80=99s keep it going. And spread it across= all > documents. Are we done with any of them yet? (NO is a perfectly acceptabl= e > answer.) We have one suggestion for new work to consider, > https://github.com/ietf-wg-httpapi/discussion/discussions/1. Feel free to > suggest other items either in that discussion group or on the mailing lis= t. > > > > Do people have other topics they would like to discuss? We did have > https://datatracker.ietf.org/doc/draft-svensson-profiled-representations/ > presented at the dispatch group, where the decision was to keep discussio= n > (where to discuss wasn=E2=80=99t specified :) Anything else you want to = put on the > agenda? > > > > > -- > httpapi mailing list > httpapi@ietf.org > https://www.ietf.org/mailman/listinfo/httpapi > --0000000000000411a505c170fe52 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I and a small group of folks have been working on a profil= e-related specification (and accompanying tooling)
=
would be happy to discuss if this looks like something the g= roup would be interested in.



=

Mike Amundsen=

APIs, Microservices, and Digital Transformation=
7310 Turfway Rd. Suite 550, Florence, KY, 41042
<= /div>

=

On Mon, May 3, 2021 at 12:34 PM Salz, Rich <rsalz=3D40akamai.com@dmarc.ietf.org> wrote:=

The next IETF meeting= will be, no surprise, virtual. It=E2=80=99s scheduled for the end of July.= At this point the chairs have to request a meeting slot.=C2=A0 We have the= option of one or two hours. We=E2=80=99re probably going to go for two hours, but might end our session early.=C2=A0 (That=E2=80=99= s not asking people to not talk, it=E2=80=99s just pointing out that if we = run out of group discussion, we=E2=80=99ll just stop. :)

=C2=A0<= /span>

We have four document= s in progress, https://gi= thub.com/ietf-wg-httpapi or https://datatracker.ietf.org/wg/httpapi/documents/. There=E2=80= =99s been a flurry of discussion recently. Let=E2=80=99s keep it going. And= spread it across all documents. Are we done with any of them yet? (NO is a perfectly acceptable answer.)=C2=A0 We have one suggestion for new wo= rk to consider, https://github.com/ietf-wg-httpapi/discussion/discussions/1<= /a>. Feel free to suggest other items either in that discussion group or on= the mailing list.

=C2=A0<= /span>

Do people have other = topics they would like to discuss? We did have https://datatracker.ietf.org/doc/draft-svensson-profiled-representations/ presented at the dispatch group, where the decision was to keep discussi= on (where to discuss wasn=E2=80=99t specified :)=C2=A0 Anything else you wa= nt to put on the agenda?

=C2=A0<= /span>

=C2=A0<= /span>

--
httpapi mailing list
httpapi@ietf.org<= br> https://www.ietf.org/mailman/listinfo/httpapi
--0000000000000411a505c170fe52--