IETF Logo Mail Archive

[httpapi] Weekly github digest (HTTPAPI WG Activity Summary)

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 10 November 2024 08:16 UTC

Return-Path: <do_not_reply@mnot.net>
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 1ABAAC14F707 for <httpapi@ietfa.amsl.com>; Sun, 10 Nov 2024 00:16:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.706
X-Spam-Level:
X-Spam-Status: No, score=-1.706 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=mnot.net header.b="IV8ZpCj2"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b="dhWkJlke"
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BSo-Bp9qmp3b for <httpapi@ietfa.amsl.com>; Sun, 10 Nov 2024 00:16:05 -0800 (PST)
Received: from fout-b4-smtp.messagingengine.com (fout-b4-smtp.messagingengine.com [202.12.124.147]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90560C14F69F for <httpapi@ietf.org>; Sun, 10 Nov 2024 00:16:05 -0800 (PST)
Received: from phl-compute-12.internal (phl-compute-12.phl.internal [10.202.2.52]) by mailfout.stl.internal (Postfix) with ESMTP id 2FC2A1140123 for <httpapi@ietf.org>; Sun, 10 Nov 2024 02:39:12 -0500 (EST)
Received: from phl-mailfrontend-01 ([10.202.2.162]) by phl-compute-12.internal (MEProxy); Sun, 10 Nov 2024 02:39:12 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-type:content-type:date:from:from:in-reply-to :mime-version:reply-to:subject:subject:to:to; s=fm1; t= 1731224352; x=1731310752; bh=0xd/xTxxm84g9D84oSoxCliez6cs6MkDVU6 YdCBVRQ0=; b=IV8ZpCj2vc8KB+XX1W0sWuD0rB4f8cMjTuIr1fdiCvTmAbsOghP KQQGqBHVyKMoHg/yxabGfc2mu1RFX16Y4pB8UNvF8IX4lli+u3QaS8SbpBepVMcM UcA2qM7XaQU/WD63aplTdz8Wva8EcKyOe2oOoB99eMA1gC3ULpYB5cWTW8LuF1eG Gy4IGg4L/xGJgDsrRwGPhvgHKlXhsquLgNWuLpVP2wFs5z1kOQ5G/BucERr4ZGF0 mqWASTcn9HEdXwPe/oobHv4QKs7ZhjUOqjWdz/WbVGR61ty+FLJfAGwg415ijASr aH6nm1irfmruqzYoql2roDow0NfrO2Sz2nQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date :feedback-id:feedback-id:from:from:in-reply-to:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; t=1731224352; x=1731310752; bh=0 xd/xTxxm84g9D84oSoxCliez6cs6MkDVU6YdCBVRQ0=; b=dhWkJlke17BNhW1cL GLwiJzVaxm26Xu++KZfBpd34bDg9IpvN6JI4HTtYbG52KkhbDz5ZYzX6QjeEa5Ca VAQKh3rZPxn9Ccc10qFGGH7bJrVag8hp/XvPS7UzGvvV8LZT+iEMmEoUODodMlUZ 8msP2eranx7CkGq4/45XcmtXz8bN9RQ3QrdCXamx0lfO8xGQj0H7Uxgdyb3FJFP0 ty1AnFVxr5Kbx8Ohly+V2PQYffRHz5rqAqXIHZbUvFO+HnWW/Hc/2tMOu18FnHb4 TGO9JahnZsl+bpBENMxTEsT0TxR9QhxLsFR/IpOHgA1bHVZtmxX90q3dAC7B0Rde LHLhA==
X-ME-Sender: <xms:H2MwZxQVQS6K7d_aa1Rof1BsBgXjW6CGyOYrvEwPhUhALrHc59w0NQ> <xme:H2MwZ6wNDDkHtf8_fH6kKKP5XPECv0P-evd3C_-doUteEp5uh8ni6CIMoMIg31UVO eQ3hFbhhiU2ssUENg>
X-ME-Received: <xmr:H2MwZ22yWtgl8kp1qmgc6hLEX837IppedLvdNFigG81z8oMcUl7cnKwZzu_CXRnxQ1GPJpUExSs28LjgdCnLMo9ZMHtJli3gsiIxFQKnsJssaHdvYUK5dgdAzV9PPd0wQgiFz8A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefuddrtdelgddutdelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvpdfu rfetoffkrfgpnffqhgenuceurghilhhouhhtmecufedttdenucgoufhushhpvggtthffoh hmrghinhculdegledmnefpohcuuggrthgvuchfihgvlhguucdlgeelmdenucfjughrpegt ggfhvffusegrtddtredttdejnecuhfhrohhmpeftvghpohhsihhtohhrhicutegtthhivh hithihucfuuhhmmhgrrhihuceuohhtuceoughopghnohhtpghrvghplhihsehmnhhothdr nhgvtheqnecuggftrfgrthhtvghrnheplefghfelveetjedtgefhtdfffeelgfelgfetud ehhfeguefgteduudduffdvieeknecuffhomhgrihhnpehgihhthhhusgdrtghomhdpghhi thhhuhgsrdhiohenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfh hrohhmpeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtpdhnsggprhgtphhtthho pedupdhmohguvgepshhmthhpohhuthdprhgtphhtthhopehhthhtphgrphhisehivghtfh drohhrgh
X-ME-Proxy: <xmx:H2MwZ5BSS-L3wZxxIs2g7W_gyCvsw1qMwEFl7ML4V_2JYzD7wOFq9w> <xmx:H2MwZ6hLQz94rnWduB9SbKeIf-LDWuSrsBB0vBdUnvmK6a5Y7rc4SA> <xmx:H2MwZ9rCZlVNJA0uvw5hgooxgyiTLK35Aayicu2EHVCzKJ6CX68_7g> <xmx:H2MwZ1hkZs_61eugVFsDpooCTPf6MKP_EthoUihHugRQPnRHnFdVLQ> <xmx:IGMwZ9slvff6gV-g427FA8WDIyO7-DADhbWHrJ3slUK0WjNPHrem5mPp>
Feedback-ID: i1c3946f2:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <httpapi@ietf.org>; Sun, 10 Nov 2024 02:39:11 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============6789324271939981611=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: httpapi@ietf.org
Message-Id: <20241110081605.90560C14F69F@ietfa.amsl.com>
Date: Sun, 10 Nov 2024 00:16:05 -0800
Message-ID-Hash: CWSUUFFY7PV2KBOMMYF6JB6ELCOJDLHN
X-Message-ID-Hash: CWSUUFFY7PV2KBOMMYF6JB6ELCOJDLHN
X-MailFrom: do_not_reply@mnot.net
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [httpapi] Weekly github digest (HTTPAPI WG Activity Summary)
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/C1x09mLGA0ZN1kC0CTwerx4ELNs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Owner: <mailto:httpapi-owner@ietf.org>
List-Post: <mailto:httpapi@ietf.org>
List-Subscribe: <mailto:httpapi-join@ietf.org>
List-Unsubscribe: <mailto:httpapi-leave@ietf.org>



Events without label "editorial"

Issues
------
* ietf-wg-httpapi/ratelimit-headers (+4/-0/💬10)
  4 issues created:
  - Can the window parameter be 0? (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/141 
  - Consistency during a connection (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/140 
  - Problem type for exhausted rate limits (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/139 
  - Replacing API documentation is not desirable (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/138 

  5 issues received 10 new comments:
  - #141 Can the window parameter be 0? (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/141 
  - #140 Consistency during a connection (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/140 
  - #139 Problem type for exhausted rate limits (2 by Acconut, ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/139 
  - #138 Replacing API documentation is not desirable (2 by Kevsy, ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/138 
  - #137 Handling multiple RateLimit-Policy and RateLimit headers (4 by Acconut, darrelmiller, kevinswiber, nfriedly)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/137 

* ietf-wg-httpapi/deprecation-header (+0/-2/💬2)
  2 issues received 2 new comments:
  - #24 intro to header field inprecise (1 by darrelmiller)
    https://github.com/ietf-wg-httpapi/deprecation-header/issues/24 
  - #6 proposed example: redirect to new location (1 by darrelmiller)
    https://github.com/ietf-wg-httpapi/deprecation-header/issues/6 

  2 issues closed:
  - intro to header field inprecise https://github.com/ietf-wg-httpapi/deprecation-header/issues/24 
  - proposed example: redirect to new location https://github.com/ietf-wg-httpapi/deprecation-header/issues/6 

* ietf-wg-httpapi/digest-fields-problem-types (+2/-0/💬1)
  2 issues created:
  - Interactions with Signatures problem types (by ioggstream)
    https://github.com/ietf-wg-httpapi/digest-fields-problem-types/issues/2 
  - Guidance for adding more digest-specific problem types (by ioggstream)
    https://github.com/ietf-wg-httpapi/digest-fields-problem-types/issues/1 

  1 issues received 1 new comments:
  - #1 Guidance for adding more digest-specific problem types (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/digest-fields-problem-types/issues/1 

* ietf-wg-httpapi/ratelimit-headers (+4/-0/💬10)
  4 issues created:
  - Can the window parameter be 0? (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/141 
  - Consistency during a connection (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/140 
  - Problem type for exhausted rate limits (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/139 
  - Replacing API documentation is not desirable (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/138 

  5 issues received 10 new comments:
  - #141 Can the window parameter be 0? (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/141 
  - #140 Consistency during a connection (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/140 
  - #139 Problem type for exhausted rate limits (2 by Acconut, ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/139 
  - #138 Replacing API documentation is not desirable (2 by Kevsy, ioggstream)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/138 
  - #137 Handling multiple RateLimit-Policy and RateLimit headers (4 by Acconut, darrelmiller, kevinswiber, nfriedly)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/issues/137 

* ietf-wg-httpapi/idempotency (+1/-3/💬11)
  1 issues created:
  - Clarify "resource server SHOULD respond with the result of the previously completed operation" (by darrelmiller)
    https://github.com/ietf-wg-httpapi/idempotency/issues/48 

  8 issues received 11 new comments:
  - #48 Clarify "resource server SHOULD respond with the result of the previously completed operation" (1 by Acconut)
    https://github.com/ietf-wg-httpapi/idempotency/issues/48 
  - #46 Identifying a replayed response (1 by darrelmiller)
    https://github.com/ietf-wg-httpapi/idempotency/issues/46 
  - #44 Reconsider handling of DELETE (and possibly PUT)? (1 by richsalz)
    https://github.com/ietf-wg-httpapi/idempotency/issues/44 
  - #43 Make explicit the goal of being able to offer idempotency as a standalone intermediary service? (1 by richsalz)
    https://github.com/ietf-wg-httpapi/idempotency/issues/43 
  - #41 Clarify whether the idempotency service should record requests for which the backing service returns error (3 by darrelmiller, jmileham, richsalz)
    https://github.com/ietf-wg-httpapi/idempotency/issues/41 
  - #40 Would additional security risk and mitigation discussion be valuable? (1 by richsalz)
    https://github.com/ietf-wg-httpapi/idempotency/issues/40 
  - #36 What value does Idempotency Fingerprint add? (2 by darrelmiller, sdatspun2)
    https://github.com/ietf-wg-httpapi/idempotency/issues/36 
  - #34 What does "Uniqueness of the key MUST be defined by the resource owner" mean? (1 by sdatspun2)
    https://github.com/ietf-wg-httpapi/idempotency/issues/34 

  3 issues closed:
  - Would additional security risk and mitigation discussion be valuable? https://github.com/ietf-wg-httpapi/idempotency/issues/40 
  - Make explicit the goal of being able to offer idempotency as a standalone intermediary service? https://github.com/ietf-wg-httpapi/idempotency/issues/43 
  - Reconsider handling of DELETE (and possibly PUT)? https://github.com/ietf-wg-httpapi/idempotency/issues/44 

* ietf-wg-httpapi/mediatypes (+1/-1/💬6)
  1 issues created:
  - OAS: track obsolete media types (by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/issues/115 

  2 issues received 6 new comments:
  - #112 move yaml stuff in archive. (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/issues/112 
  - #110 Object Type parameter for OAS media type (5 by handrews, ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/issues/110 [rest-api] 

  1 issues closed:
  - move yaml stuff in archive. https://github.com/ietf-wg-httpapi/mediatypes/issues/112 

* ietf-wg-httpapi/link-rel-auth (+2/-0/💬0)
  2 issues created:
  - Because browser extensions can leverage page content, should that constrain support for generic clients? (by darrelmiller)
    https://github.com/ietf-wg-httpapi/link-rel-auth/issues/2 
  - Should link relations define the behaviour of the user agent following a link? (by darrelmiller)
    https://github.com/ietf-wg-httpapi/link-rel-auth/issues/1 



Pull requests
-------------
* ietf-wg-httpapi/ratelimit-headers (+3/-0/💬0)
  3 pull requests submitted:
  - Add missing quota unit to registry (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/pull/144 
  - Move trailer restriction out of example section (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/pull/143 
  - Require `r` parameter in RateLimit field (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/pull/142 

* ietf-wg-httpapi/ratelimit-headers (+3/-0/💬0)
  3 pull requests submitted:
  - Add missing quota unit to registry (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/pull/144 
  - Move trailer restriction out of example section (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/pull/143 
  - Require `r` parameter in RateLimit field (by Acconut)
    https://github.com/ietf-wg-httpapi/ratelimit-headers/pull/142 

* ietf-wg-httpapi/mediatypes (+4/-3/💬2)
  4 pull requests submitted:
  - Fix: #110. Schema Object parameter (by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/pull/118 
  - Fix: #115. Mention deprecated alias names. (by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/pull/117 
  - Update ioggstream's org. (by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/pull/116 
  - Bump: upload-artifact v4 (by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/pull/114 

  2 pull requests received 2 new comments:
  - #118 Fix: #110. Schema Object parameter (1 by handrews)
    https://github.com/ietf-wg-httpapi/mediatypes/pull/118 
  - #26 Don't override external specifications. See #20. (1 by ioggstream)
    https://github.com/ietf-wg-httpapi/mediatypes/pull/26 [rest-api] 

  3 pull requests merged:
  - Update ioggstream's org.
    https://github.com/ietf-wg-httpapi/mediatypes/pull/116 
  - Fix: #122. YAML is RFC now. Move its stuff in archive/.
    https://github.com/ietf-wg-httpapi/mediatypes/pull/113 
  - Bump: upload-artifact v4
    https://github.com/ietf-wg-httpapi/mediatypes/pull/114 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/ietf-wg-httpapi/ratelimit-headers
* https://github.com/ietf-wg-httpapi/link-hint
* https://github.com/ietf-wg-httpapi/deprecation-header
* https://github.com/ietf-wg-httpapi/http-privacy
* https://github.com/ietf-wg-httpapi/digest-fields-problem-types
* https://github.com/ietf-wg-httpapi/ietf-wg-httpapi.github.io
* https://github.com/ietf-wg-httpapi/patch-byterange
* https://github.com/ietf-wg-httpapi/ratelimit-headers
* https://github.com/ietf-wg-httpapi/api-catalog
* https://github.com/ietf-wg-httpapi/idempotency
* https://github.com/ietf-wg-httpapi/link-template
* https://github.com/ietf-wg-httpapi/mediatypes
* https://github.com/ietf-wg-httpapi/rfc7807bis
* https://github.com/ietf-wg-httpapi/link-rel-auth
* https://github.com/ietf-wg-httpapi/linkset
* https://github.com/ietf-wg-httpapi/discussion
* https://github.com/ietf-wg-httpapi/wg-materials

v2.39.1 | Report a Bug | By Email | System Status