Weekly github digest (QUIC Activity Summary)

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 24 March 2024 07:38 UTC

Return-Path: <do_not_reply@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1474CC14CE42 for <quic@ietfa.amsl.com>; Sun, 24 Mar 2024 00:38:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.706
X-Spam-Level:
X-Spam-Status: No, score=-6.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_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=ham 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="Z7k6FpWm"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b="kVKWsfc0"
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 y6S4apGYJI0I for <quic@ietfa.amsl.com>; Sun, 24 Mar 2024 00:38:35 -0700 (PDT)
Received: from wflow6-smtp.messagingengine.com (wflow6-smtp.messagingengine.com [64.147.123.141]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A0A6C14F6E3 for <quic@ietf.org>; Sun, 24 Mar 2024 00:38:35 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailflow.west.internal (Postfix) with ESMTP id B36302CC0459 for <quic@ietf.org>; Sun, 24 Mar 2024 03:38:30 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute2.internal (MEProxy); Sun, 24 Mar 2024 03:38:30 -0400
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=fm3; t= 1711265910; x=1711273110; bh=X7rHubXzY+Tvr+ASwc5sLtPvGzHiubbO4xu MiBdMMVg=; b=Z7k6FpWmJ2e8y9IwYyh787DnIH4wDO6vgXjGkUUrPvVGPXOQfih me91mAeCFGJahTfi6wyKFXRQi3lswy//WfqYnCaK/3a/tLLCNOMaFjxfJVn8burd 51XEHQN5ldO69d1CpdZ9hya8n4hu091fNQW22gLapdJcki3qpx+whMpINjK+bcNb WDJGMSQP4Vm/fd7TBOEaZ6hJ4wiYnsf2wKxJNuc3mgHb8o0bWuTAgVI5/3xEQw1d naBb1OLdMTLx3J7lItGXaAuBQeYY68q4p39ftbUu+F5sWDTpKLvIaMpfX2PJPcUw Lhtx8a3Oo04b9J4rJ0SBXJ4CadEA92xzf8w==
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-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; t=1711265910; x= 1711273110; bh=X7rHubXzY+Tvr+ASwc5sLtPvGzHiubbO4xuMiBdMMVg=; b=k VKWsfc0++Aiuer5bUn4WMNCkcv/oiwpgtHQxVB6txH5xTSsvNyYzzrw1gJxzxJ6/ Q2yAvF0DtTxvAh9AbAl1Q5ltwQneSJ/tuAI1U3vC5QiFThbFn7XAhYc63tjKIV34 OXVT1oajdOfgAZYmR8uli8pBLeDylaUNThEnK7QcbeE9tdnYCclFE2LzdTlLHkxi tuHdQC1/W+xBFjQMCncx0z80MmAA/HUj37KpWVJTiqur5+A4UyIxFMbBxeq6i0kr ddpNLdY3wjqvlDIYXzKNZ/fs7uIrM+pZGX5pk8EyEQw75C5eawdU5LFhLWXm2hCE if28cn66VZJ6unjjpFcqg==
X-ME-Sender: <xms:dtj_ZWxCp8eZdb7FUisJQMHFYMc1ulf1V6_-DiyzO4jPQi0-BzVIww> <xme:dtj_ZSRsanNC1wD4wrxc6K0AYuXhjwUDTmofbaaqweOegOwn3d-eEkwVF8hm1p68S q4qKFHfZ_lE1KelSQ>
X-ME-Received: <xmr:dtj_ZYW7CKKqEqtXd9Y_GzYondFt7z_2jKJavsL92ci_8et5vTovxiDgHcsy>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledruddtiedgtdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenog frhhhishhhihhnghdqifegvdehqdduuddtucdlfedttddmnecujfgurheptggghffvufes rgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuuf humhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeen ucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffe etffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepughopghnohhtpghrvghplh ihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:dtj_ZcjBsE_8Xx3NRkrhb2u8dXm_U8kXk7hszEMgRtmYXctzwQuB3A> <xmx:dtj_ZYD2_wzd2CnRh_6FbV61r-zAZS7R9T6tnYzP2x5PrMetAvL19w> <xmx:dtj_ZdKQWT-MCFLsXzbPsyYnU18qUdyBdFoyj3r-PQ3la9cn2aavtQ> <xmx:dtj_ZfDmdIEXrbrCJH5TVKLZoNNEaAJI5AaSrwoOwMJzFoAg1A0Zhw> <xmx:dtj_ZR4-Y2PzBW6fp3Xg_EYOCi8wjqPnC1ofuz1geqN4oliP7N_4CeUr99cEi26M>
Feedback-ID: i1c3946f2:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <quic@ietf.org>; Sun, 24 Mar 2024 03:38:29 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============1859755594394410518=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Activity Summary)
Message-Id: <20240324073835.7A0A6C14F6E3@ietfa.amsl.com>
Date: Sun, 24 Mar 2024 00:38:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BGogMNC_y9dyAfM2riGRU-BFYBc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 24 Mar 2024 07:38:40 -0000



Events without label "editorial"

Issues
------
* quicwg/load-balancers (+1/-0/💬0)
  1 issues created:
  - There is an error in the encryption example . (by nandsky)
    https://github.com/quicwg/load-balancers/issues/227 

* quicwg/qlog (+1/-2/💬2)
  1 issues created:
  - Discuss extensibility of extension points through type or group sockets (by rmarx)
    https://github.com/quicwg/qlog/issues/416 

  2 issues received 2 new comments:
  - #134 Multipath support (1 by rmarx)
    https://github.com/quicwg/qlog/issues/134 [design] [quic-http3-fields] [future-versions] 
  - #57 Add IP addresses to datagram_* events (1 by rmarx)
    https://github.com/quicwg/qlog/issues/57 [design] [current-version] [privacy] 

  2 issues closed:
  - Add IP addresses to datagram_* events https://github.com/quicwg/qlog/issues/57 [design] [current-version] [privacy] 
  - Multipath support https://github.com/quicwg/qlog/issues/134 [design] [quic-http3-fields] [future-versions] 

* quicwg/multipath (+9/-0/💬35)
  9 issues created:
  - CID allocation strategy (by Yanmei-Liu)
    https://github.com/quicwg/multipath/issues/325 
  - Rename "initial_max_paths / MAX_PATHS" to "intial_max_path_id / MAX_PATH_ID" ? (by Yanmei-Liu)
    https://github.com/quicwg/multipath/issues/324 
  - Alternative to defining a bunch of MP-specific frames (by martinthomson)
    https://github.com/quicwg/multipath/issues/323 
  - MAX_PATH, sender initiated streams, and CID allocation. (by huitema)
    https://github.com/quicwg/multipath/issues/322 
  - Static path IDs? (by kazuho)
    https://github.com/quicwg/multipath/issues/321 
  - Sending NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames when multipath has been negotiated (by michael-eriksson)
    https://github.com/quicwg/multipath/issues/320 
  - What happen if a client falsely links two paths using CIDs associated with the same path ID (by yfmascgy)
    https://github.com/quicwg/multipath/issues/319 
  - Should path numbers be continuous? (by huitema)
    https://github.com/quicwg/multipath/issues/318 
  - explicit path IDs: Should server preferred address have its own path ID? (by marten-seemann)
    https://github.com/quicwg/multipath/issues/317 

  14 issues received 35 new comments:
  - #323 Alternative to defining a bunch of MP-specific frames (2 by marten-seemann, qdeconinck)
    https://github.com/quicwg/multipath/issues/323 
  - #320 Sending NEW_CONNECTION_ID and RETIRE_CONNECTION_ID frames when multipath has been negotiated (1 by mirjak)
    https://github.com/quicwg/multipath/issues/320 [explicit path ID] 
  - #319 What if a client falsely links two paths using CIDs associated with the same path ID (7 by gloinul, huitema, kazuho, mirjak, yfmascgy)
    https://github.com/quicwg/multipath/issues/319 [explicit path ID] 
  - #318 Should path numbers be continuous? (6 by huitema, marten-seemann)
    https://github.com/quicwg/multipath/issues/318 
  - #317 explicit path IDs: Should server preferred address have its own path ID? (1 by huitema)
    https://github.com/quicwg/multipath/issues/317 
  - #313 When to CID expire if using Unique Path ID? (2 by Yanmei-Liu, huitema)
    https://github.com/quicwg/multipath/issues/313 [explicit path ID] 
  - #312 PATH_STANDBY PATH_AVAILABLE Sequence number spaces (1 by mirjak)
    https://github.com/quicwg/multipath/issues/312 
  - #311 Simplify reference to whose sequence number space. (2 by gloinul, mirjak)
    https://github.com/quicwg/multipath/issues/311 
  - #309 Clarify refragmenting of stream data when MTU is different and retransmission happens on other path.  (6 by gloinul, huitema, mirjak)
    https://github.com/quicwg/multipath/issues/309 
  - #307 Clarify requirement to avoid wrapping CID seqenunce number (1 by Yanmei-Liu)
    https://github.com/quicwg/multipath/issues/307 [design] 
  - #306 In some situations the ACK frames will be for CID with sequence number 1 (2 by huitema)
    https://github.com/quicwg/multipath/issues/306 [design] 
  - #303 Recommendation on token ambiguity issue is violating RFC 9000 (2 by huitema, mirjak)
    https://github.com/quicwg/multipath/issues/303 
  - #297 Path IDs should not be reused (1 by kazuho)
    https://github.com/quicwg/multipath/issues/297 [has PR] [design] [explicit path ID] 
  - #291 Do we actually have an established consensus on path definition? (1 by Yanmei-Liu)
    https://github.com/quicwg/multipath/issues/291 



Pull requests
-------------
* quicwg/qlog (+3/-0/💬7)
  3 pull requests submitted:
  - Clarify no-ordering expectation for qlog fields (by rmarx)
    https://github.com/quicwg/qlog/pull/418 
  - Add extensibility for all events and official extension points (by rmarx)
    https://github.com/quicwg/qlog/pull/417 
  - Define extension schema policy and registry (by LPardue)
    https://github.com/quicwg/qlog/pull/415 

  4 pull requests received 7 new comments:
  - #417 Add extensibility for all events and official extension points (1 by rmarx)
    https://github.com/quicwg/qlog/pull/417 
  - #415 Define extension schema policy and registry (3 by JonathanLennox, LPardue)
    https://github.com/quicwg/qlog/pull/415 
  - #412 Add raw bytes field support to CONNECTION_CLOSE. (1 by rmarx)
    https://github.com/quicwg/qlog/pull/412 
  - #329 additional_schema using URI/URN (2 by LPardue, rmarx)
    https://github.com/quicwg/qlog/pull/329 

* quicwg/multipath (+2/-0/💬0)
  2 pull requests submitted:
  - [+] Clarify use of MAX_PATHS (by Yanmei-Liu)
    https://github.com/quicwg/multipath/pull/316 
  - [+] Clarify that endpoints use the same Path ID in both directions. (by Yanmei-Liu)
    https://github.com/quicwg/multipath/pull/315 

* quicwg/ack-frequency (+0/-2/💬2)
  1 pull requests received 2 new comments:
  - #279 Add tables to describe each variables for out-of-order examples (2 by LPardue, tatsuhiro-t)
    https://github.com/quicwg/ack-frequency/pull/279 

  2 pull requests merged:
  - Add reviewers to acknowledgement section!
    https://github.com/quicwg/ack-frequency/pull/285 
  - remove empty change log appendix
    https://github.com/quicwg/ack-frequency/pull/286 


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts
* https://github.com/quicwg/ops-drafts
* https://github.com/quicwg/datagram
* https://github.com/quicwg/load-balancers
* https://github.com/quicwg/version-negotiation
* https://github.com/quicwg/quic-bit-grease
* https://github.com/quicwg/qlog
* https://github.com/quicwg/quic-v2
* https://github.com/quicwg/multipath
* https://github.com/quicwg/ack-frequency
* https://github.com/quicwg/reliable-stream-reset