Re: [Edm] s2n-quic compliance
Mirja Kuehlewind <ietf@kuehlewind.net> Wed, 23 February 2022 13:54 UTC
Return-Path: <ietf@kuehlewind.net>
X-Original-To: edm@ietfa.amsl.com
Delivered-To: edm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6964A3A0D8F for <edm@ietfa.amsl.com>; Wed, 23 Feb 2022 05:54:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.397
X-Spam-Level:
X-Spam-Status: No, score=-1.397 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001, URI_NOVOWEL=0.5] autolearn=ham autolearn_force=no
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 CO3isbGq4m5d for <edm@ietfa.amsl.com>; Wed, 23 Feb 2022 05:54:42 -0800 (PST)
Received: from wp513.webpack.hosteurope.de (wp513.webpack.hosteurope.de [IPv6:2a01:488:42:1000:50ed:8223::]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7FE63A0D94 for <edm@iab.org>; Wed, 23 Feb 2022 05:54:42 -0800 (PST)
Received: from p200300dee70d9900a1598d4aa8a8a607.dip0.t-ipconnect.de ([2003:de:e70d:9900:a159:8d4a:a8a8:a607]); authenticated by wp513.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) id 1nMs6I-0004kQ-HK; Wed, 23 Feb 2022 14:54:38 +0100
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Mirja Kuehlewind <ietf@kuehlewind.net>
In-Reply-To: <bcd88aba-3532-49a2-8095-20013c74512c@www.fastmail.com>
Date: Wed, 23 Feb 2022 14:54:35 +0100
Cc: edm@iab.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <549A7328-C88B-42E3-BFD9-C1813973CC0A@kuehlewind.net>
References: <bcd88aba-3532-49a2-8095-20013c74512c@www.fastmail.com>
To: Christopher Wood <caw@heapingbits.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-bounce-key: webpack.hosteurope.de;ietf@kuehlewind.net;1645624482;07688ea1;
X-HE-SMSGID: 1nMs6I-0004kQ-HK
Archived-At: <https://mailarchive.ietf.org/arch/msg/edm/f1GtK1nbL5Njh8g5iCT4XFvlmp0>
Subject: Re: [Edm] s2n-quic compliance
X-BeenThere: edm@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Evolvability, Deployability, & Maintainability \(Proposed\) Program" <edm.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/edm>, <mailto:edm-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/edm/>
List-Post: <mailto:edm@iab.org>
List-Help: <mailto:edm-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/edm>, <mailto:edm-request@iab.org?subject=subscribe>
X-List-Received-Date: Wed, 23 Feb 2022 13:54:48 -0000
This is quite interesting. Thanks for sharing! I guess, while all MUST/SHOULD/MAY clearly indicate a normative requirement, I don’t think that necessarily all normative requirements are indicted by one of these keywords. So this is a nice compliance check but probably not complete. > On 20. Feb 2022, at 00:15, Christopher Wood <caw@heapingbits.net> wrote: > > Hi folks, > > In case you haven’t seen it yet, Amazon’s QUIC implementation (s2n-quic) comes with a very clever way of tracking compliance between the code and various specifications. Check it out here: > > https://dnglbrstg7yg.cloudfront.net/08c33571ee8679775e810303f65c96c1d48e270d/compliance.html#/ > > I’m sharing here because I think it’s useful input to the program, especially as we consider how to track implementations for various specifications. > > Best, > Chris > > -- > Edm mailing list > Edm@iab.org > https://www.iab.org/mailman/listinfo/edm
- [Edm] s2n-quic compliance Christopher Wood
- Re: [Edm] s2n-quic compliance Mirja Kuehlewind
- Re: [Edm] s2n-quic compliance Bytheway, Cameron