Weekly github digest (QUIC Activity Summary)

Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 17 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 E8504C151991 for <quic@ietfa.amsl.com>; Sun, 17 Mar 2024 00:38:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.705
X-Spam-Level:
X-Spam-Status: No, score=-1.705 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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="oB7f9HKm"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b="m+/vEVX7"
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 iiVxMXB7CmTB for <quic@ietfa.amsl.com>; Sun, 17 Mar 2024 00:38:34 -0700 (PDT)
Received: from flow2-smtp.messagingengine.com (flow2-smtp.messagingengine.com [103.168.172.137]) (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 A0A98C14F60C for <quic@ietf.org>; Sun, 17 Mar 2024 00:38:34 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.48]) by mailflow.nyi.internal (Postfix) with ESMTP id 8F5D320022E for <quic@ietf.org>; Sun, 17 Mar 2024 03:38:33 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Sun, 17 Mar 2024 03:38:33 -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= 1710661113; x=1710668313; bh=M2fKK8vlW+3MVdtAwTl+BNxFnikMZvjlEvT 3eHKiMyQ=; b=oB7f9HKmdI4XWvl2W37yiDw+D/KJvgmDqMzlN1dbgbYCX1NoqRZ JbZo3lCYZ73BmU7eUDv36ulZAhtqo4/XrN+Ws7Ya7nsWSxcczmTxa58M37H6iyYr Ig0tb7dFpah8+hlVx89wJIYdZ1yt5ovJVteCQNYjSep4zRB/9wcqALjzgWn0D/v+ K3MxOUPIWKF54FbECgnvBf/1xGYsftgqp8zYeIaECptXi6UHzwmzE+I8YQqZ0r1q PQEEOtlELhn620CtTkVwCfhhYib1Njbw4qUNt0AhSnGtFt3FqqojGZChdTjo5/Uu 2HixZBFadebyIequufzp6e7XC4pfe+JGKmg==
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=1710661113; x= 1710668313; bh=M2fKK8vlW+3MVdtAwTl+BNxFnikMZvjlEvT3eHKiMyQ=; b=m +/vEVX7yWl+DlkpzI6L4FVNIsw4JrBFYZYLJCK5Zv2d/De+JV8WgXwCRyIjLRRNp PtAlqUTDLtU+fDemq2X2yEB+qQH5o6uXLu+IiXCloRiCgrv/xMLrQMWAo+qiv1i5 xLBGDEr7NtamT1BmAHxeuF08YOhkVcRn3NbC9jtHGBRUG4WNn0frkB80apv6bL/W Nys5+RNKIvx4lCOS8UHE72lHbg2Wg5I4e1k0HJOGwgvf0OEvKZoal/w9d1MfLrHX XboVYL//F6RFNs9NPt/CCmyClWLBHWcdjzbu+PBDtUg0Vmx7sW/MlndIJsBUlh/O qmY/jJy/OxZ71C+rqoQgw==
X-ME-Sender: <xms:-Z32Za5jNjvBeuv8UHQICjbUaJfg7k8bH_DEB_bWyVp9azuHRWlonQ> <xme:-Z32ZT7hFCQ-1jvoYJy9afKxvxmsEi3V-cjprdBvrX4iuVQItXIKM2B3OihZA176h UokraS6zwYfOhNx2g>
X-ME-Received: <xmr:-Z32ZZfzyX_1_g6_XIoguBXvrT948xTxFvpl3Orjlutc9R6B_y80_lNFeLiKkA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrkeefgdduuddvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucfpohcuuggrthgvuchfihgvlhguucdlgeelmdenog frhhhishhhihhnghdqifegvdehqdduuddtucdlfedttddmnecujfgurheptggghffvufes rgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuuf humhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeen ucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffe etffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrdgtohhmnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepughopghnohhtpghrvghplh ihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:-Z32ZXLN7Z_CoZAsacsXIyJKlFztyxUyHf3JmifgWtQQYt-Unyid_w> <xmx:-Z32ZeKpMDz8M9EjP7co88tzJ5r2euRM_agpGYgS-C7ZY7rJwQ8JDw> <xmx:-Z32ZYz9l3IF2CYXTwNbl9OMsmiRNvGl8O9PH6IuldH14zhRnB3Vmw> <xmx:-Z32ZSJOMPCJUFirca-MumJOUrr4p88sz6b7f0MeCZUDPe0FrPXkVQ> <xmx:-Z32ZQhVEutGOoofKvMhbcUVI82WA997k3IH9RjPV5x_L53Jp2Gpp7qojyM>
Feedback-ID: i1c3946f2:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <quic@ietf.org>; Sun, 17 Mar 2024 03:38:32 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============2664623768282790920=="
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: <20240317073834.A0A98C14F60C@ietfa.amsl.com>
Date: Sun, 17 Mar 2024 00:38:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/36sL3g6C7sH9rl6IgNmFMzaODxE>
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, 17 Mar 2024 07:38:40 -0000



Events without label "editorial"

Issues
------
* quicwg/qlog (+2/-1/💬2)
  2 issues created:
  - Logging of HTTP field names or values that contain illegal bytes (by LPardue)
    https://github.com/quicwg/qlog/issues/413 
  - Logging non-UTF-8 reasons (by hlandau)
    https://github.com/quicwg/qlog/issues/411 

  1 issues received 2 new comments:
  - #411 Logging non-UTF-8 reasons (2 by LPardue, hlandau)
    https://github.com/quicwg/qlog/issues/411 

  1 issues closed:
  - Migration-related events https://github.com/quicwg/qlog/issues/318 

* quicwg/multipath (+19/-2/💬18)
  19 issues created:
  - When to CID expire if using Unique Path ID? (by huitema)
    https://github.com/quicwg/multipath/issues/313 
  - PATH_STANDBY PATH_AVAILABLE Sequence number spaces (by gloinul)
    https://github.com/quicwg/multipath/issues/312 
  - Simplify reference to whose sequence number space. (by gloinul)
    https://github.com/quicwg/multipath/issues/311 
  - Clarify which endpoints sequence number are referenced.  (by gloinul)
    https://github.com/quicwg/multipath/issues/310 
  - Clarify refragmenting of stream data when MTU is different and retransmission happens on other path.  (by gloinul)
    https://github.com/quicwg/multipath/issues/309 
  - Expand LIA (by gloinul)
    https://github.com/quicwg/multipath/issues/308 
  - Clarify requirement to avoid wrapping CID seqenunce number (by gloinul)
    https://github.com/quicwg/multipath/issues/307 
  - In some situations the ACK frames will be for CID with sequence number 1 (by gloinul)
    https://github.com/quicwg/multipath/issues/306 
  - Split State diagram based on role as sender on a path or receiver.  (by gloinul)
    https://github.com/quicwg/multipath/issues/305 
  - Unclear usage of direciton of Path in specifcation text (by gloinul)
    https://github.com/quicwg/multipath/issues/304 
  - Recommendation on token ambiguity issue is violating RFC 9000 (by gloinul)
    https://github.com/quicwg/multipath/issues/303 
  - Missing reference to sequence number for DCID (by gloinul)
    https://github.com/quicwg/multipath/issues/302 
  - Write Security Consideration section (by gloinul)
    https://github.com/quicwg/multipath/issues/301 
  - Clarify use of MAX_PATHS  and client created new paths (by mirjak)
    https://github.com/quicwg/multipath/issues/298 [design] [explicit path ID] 
  - Path IDs should not be reused (by mirjak)
    https://github.com/quicwg/multipath/issues/297 [design] [explicit path ID] 
  - Is MP_RETIRE_CONNECTION_ID needed? (by mirjak)
    https://github.com/quicwg/multipath/issues/296 [design] [explicit path ID] 
  - Is RETIRE_PATH_ID needed? (by mirjak)
    https://github.com/quicwg/multipath/issues/295 [design] [explicit path ID] 
  - "Path ID" needs to be clarified. Do both endpoints use the same path ID, or independently choose which path ID to use? (by mirjak)
    https://github.com/quicwg/multipath/issues/294 
  - Switch to standby path more tricky than expected (by huitema)
    https://github.com/quicwg/multipath/issues/293 

  6 issues received 18 new comments:
  - #313 When to CID expire if using Unique Path ID? (2 by gloinul)
    https://github.com/quicwg/multipath/issues/313 
  - #304 Unclear usage of direciton of Path in specifcation text (1 by gloinul)
    https://github.com/quicwg/multipath/issues/304 
  - #297 Path IDs should not be reused (2 by mirjak)
    https://github.com/quicwg/multipath/issues/297 [design] [explicit path ID] 
  - #296 Is MP_RETIRE_CONNECTION_ID needed? (5 by Yanmei-Liu, huitema, mirjak)
    https://github.com/quicwg/multipath/issues/296 [design] [explicit path ID] 
  - #295 Is RETIRE_PATH_ID needed? (2 by Yanmei-Liu, huitema)
    https://github.com/quicwg/multipath/issues/295 [design] [explicit path ID] 
  - #293 Switch to standby path more tricky than expected (6 by huitema, mirjak, qdeconinck)
    https://github.com/quicwg/multipath/issues/293 

  2 issues closed:
  - Is MP_RETIRE_CONNECTION_ID needed? https://github.com/quicwg/multipath/issues/296 [design] [explicit path ID] 
  - Is MP_RETIRE_CONNECTION_ID needed? https://github.com/quicwg/multipath/issues/296 [design] [explicit path ID] 



Pull requests
-------------
* quicwg/load-balancers (+1/-0/💬0)
  1 pull requests submitted:
  - fixed encryption example (by nandsky)
    https://github.com/quicwg/load-balancers/pull/226 

* quicwg/qlog (+2/-0/💬2)
  2 pull requests submitted:
  - Allow logging of header name and value bytes (by LPardue)
    https://github.com/quicwg/qlog/pull/414 
  - Add raw bytes field support to CONNECTION_CLOSE. (by LPardue)
    https://github.com/quicwg/qlog/pull/412 

  1 pull requests received 2 new comments:
  - #412 Add raw bytes field support to CONNECTION_CLOSE. (2 by LPardue, rmarx)
    https://github.com/quicwg/qlog/pull/412 

* quicwg/multipath (+3/-0/💬0)
  3 pull requests submitted:
  - [+] Explicit Path ID: solving issue #297 (by Yanmei-Liu)
    https://github.com/quicwg/multipath/pull/314 
  - [+] Explicit path identifier first shot(clean version / same commit)  (by Yanmei-Liu)
    https://github.com/quicwg/multipath/pull/300 
  - [+] Explicit path identifier first shot(clean version / same commit) (by Yanmei-Liu)
    https://github.com/quicwg/multipath/pull/299 

* quicwg/ack-frequency (+2/-0/💬0)
  2 pull requests submitted:
  - remove empty change log appendix (by mirjak)
    https://github.com/quicwg/ack-frequency/pull/286 
  - Add reviewers to acknowledgement section! (by mirjak)
    https://github.com/quicwg/ack-frequency/pull/285 


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