Weekly github digest (QUIC Activity Summary)
Repository Activity Summary Bot <do_not_reply@mnot.net> Sun, 05 November 2023 07:39 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 AAB50C1B033C for <quic@ietfa.amsl.com>; Sun, 5 Nov 2023 00:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.704
X-Spam-Level:
X-Spam-Status: No, score=-1.704 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=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="LUrAOd1L"; dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=messagingengine.com header.b="H7O4Nzlb"
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 Jl-9rKHZ4-ez for <quic@ietfa.amsl.com>; Sun, 5 Nov 2023 00:39:42 -0700 (PDT)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (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 D29FCC2FF2D3 for <quic@ietf.org>; Sun, 5 Nov 2023 00:38:47 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 793EC3200908 for <quic@ietf.org>; Sun, 5 Nov 2023 02:38:44 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 05 Nov 2023 02:38:44 -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:sender:subject:subject:to:to; s=fm1; t= 1699169923; x=1699256323; bh=0P7LBn+bPSh+s+CGifXNLeY+LEdlLMgz9ip uOmDRjt0=; b=LUrAOd1L2KR07+/+5D6YbFR1YPCOxYtvhHzridWhWmp7FRdJRJ/ aIZxEFY1CVJKyAUVAdB9wzNMGkJxCQ6xrPkYmlYjKJvCy3nukNhJZHFmheTQA4oW Qu4l1S3uh3RXOomD+ooOBnN3+ai+ge+Lkg+b+6MLsHxTpolxKqh8pFWbTTUKlu1D NQHW8HJBVoL3v13gOeBIcyKzJr07BHE7HiXp2IffIDQK3/EFpfQpMr5O8gtIr2pO L0xKggZFfAnNKi/bvIxGl/+kIyaM4p7Mg/9hK00XdV8OMYOcLonEHXA1zOxLX9wy WiL4+22TM4eedoQmldPZyCorqqBslE99B1Q==
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:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1699169923; x= 1699256323; bh=0P7LBn+bPSh+s+CGifXNLeY+LEdlLMgz9ipuOmDRjt0=; b=H 7O4NzlbvYRr2RvUtIc22S2mgyKER/2M399GsebIC2yMwmdATfvXvusgq049o+xT4 uhZUkJA60oJtCJx4x1bWTqnflEk+3BAYzfl+CHKjLV9eO0eWoT/wEaDKmc6n1BwK sxBzw/uiTssOETlz80p1iW4pePrDm/yqOBYA7PzFZka1Lhvh3mf0OTUPR4RfPloQ 9ukhkZPVLxcSa6FozUK9jBbU0N4d7gGvDYjGJDYffxAdUyhVyAlXduMApJcQxcS6 W75gdeqA3Kj0P2UydzcW9yOrbV/WDWZ85699b9GKjC2R6ap6E/2MF5cs8/5f16GP uzMaeGJ8cmSCYWYG9ODRQ==
X-ME-Sender: <xms:g0ZHZUcp3PeMN4wWx1Dftc-fPDaYzdFsf1HOak3wo6_-Yw6NH8JqUA> <xme:g0ZHZWN5PT0CrPOZ3O1Z6co098547ayU_dch-TX1Zx8PLWJbtNpOvVHs_DlZLZU6u 68861oMf87spQywYA>
X-ME-Received: <xmr:g0ZHZVj53wa2Z_WS2_OYawsb8xLKLg5Itis2P5B8tEM_vGhfNzx07ZN7M5Z0PA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvkedrudduuddguddtkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecupfhoucgurghtvgcufhhivghlugculdegledmne cujfgurheptggghffvufesrgdttdertddtjeenucfhrhhomheptfgvphhoshhithhorhih ucettghtihhvihhthicuufhumhhmrghrhicuuehothcuoeguohgpnhhothgprhgvphhlhi esmhhnohhtrdhnvghtqeenucggtffrrghtthgvrhhnpeekfedvudetjedvfeekheeiveeu gfefhfetteevgeffkefffeetffdvleehudeiteenucffohhmrghinhepghhithhhuhgsrd gtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:g0ZHZZ-mZZl6WhmBFTq3skR1lkw4PcyyqI0KYvzH6SmKpt1swRNMxg> <xmx:g0ZHZQuQ0lzhxvVDEeIcXEy0P851NPLmHw4vJigpJPhLxy68tM1M1Q> <xmx:g0ZHZQHTG4i5Dig6S4mx_hxwFMbYdeE4gfN1ElxQeAC3iHKmkMuyXQ> <xmx:g0ZHZZ5VZIsUa6yKrrh7lCyctxarkVEr-dbh8BxzbgT0DQ-ysdvexA>
Feedback-ID: i1c3946f2:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA for <quic@ietf.org>; Sun, 5 Nov 2023 02:38:43 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============0175217147476822535=="
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: <20231105073847.D29FCC2FF2D3@ietfa.amsl.com>
Date: Sun, 05 Nov 2023 00:38:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wp4IBjBQIAe8YS-oPZezsRDOcCg>
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, 05 Nov 2023 07:39:46 -0000
Events without label "editorial"
Issues
------
* quicwg/multipath (+4/-5/💬30)
4 issues created:
- Key Update and time to next possible update (by gloinul)
https://github.com/quicwg/multipath/issues/290
- PATH_AVAILABLE/STANDBY vs. local API preference (by Yanmei-Liu)
https://github.com/quicwg/multipath/issues/286
- Terminology clarification of "path" (by tzaeschke)
https://github.com/quicwg/multipath/issues/285
- working (by tzaeschke)
https://github.com/quicwg/multipath/issues/284
12 issues received 30 new comments:
- #290 Key Update and time to next possible update (1 by kazuho)
https://github.com/quicwg/multipath/issues/290
- #286 PATH_AVAILABLE/STANDBY vs. local API preference (2 by kazuho, mirjak)
https://github.com/quicwg/multipath/issues/286 [no-action-needed]
- #285 Terminology clarification of "path" (2 by LPardue, huitema)
https://github.com/quicwg/multipath/issues/285
- #283 Sending PATH_STANDBY before the connection ID is used is pointless (9 by huitema, kazuho, mirjak, yfmascgy)
https://github.com/quicwg/multipath/issues/283 [question] [no-action-needed]
- #282 Does the new draft (06) allow servers to create new paths by receiving pkts without PATH_CHALLENGE? (1 by mirjak)
https://github.com/quicwg/multipath/issues/282
- #281 Multipath Model Based on Nginx QUIC (1 by mirjak)
https://github.com/quicwg/multipath/issues/281
- #271 Discussion: Remove ACK_MP frame from draft-ietf-quic-multipath ？ (2 by iyangsj, mirjak)
https://github.com/quicwg/multipath/issues/271 [duplicate] [no-action-needed]
- #270 The definition of path (4 by LPardue, mirjak, nandsky)
https://github.com/quicwg/multipath/issues/270 [no-action-needed]
- #269 Do we allow the server to actively stop sending? (3 by mirjak, nandsky)
https://github.com/quicwg/multipath/issues/269 [no-action-needed]
- #253 Review error codes (3 by LPardue, marten-seemann, mirjak)
https://github.com/quicwg/multipath/issues/253 [design] [no-action-needed]
- #220 "SHOULD" use ACK_MP frames? (1 by mirjak)
https://github.com/quicwg/multipath/issues/220 [design] [needs-discussion]
- #215 alternative solution for the key update problem (1 by mirjak)
https://github.com/quicwg/multipath/issues/215 [design] [no-action-needed]
5 issues closed:
- The definition of path https://github.com/quicwg/multipath/issues/270 [no-action-needed]
- Do we allow the server to actively stop sending? https://github.com/quicwg/multipath/issues/269 [no-action-needed]
- Multipath Model Based on Nginx QUIC https://github.com/quicwg/multipath/issues/281
- alternative solution for the key update problem https://github.com/quicwg/multipath/issues/215 [design] [no-action-needed]
- working https://github.com/quicwg/multipath/issues/284
Pull requests
-------------
* quicwg/multipath (+3/-0/💬0)
3 pull requests submitted:
- token usage (by mirjak)
https://github.com/quicwg/multipath/pull/289
- clarify path validation on previously used paths (by mirjak)
https://github.com/quicwg/multipath/pull/288
- send PATH_ABANDON after time-out on another path (by mirjak)
https://github.com/quicwg/multipath/pull/287
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
- Weekly github digest (QUIC Activity Summary) Repository Activity Summary Bot