IETF Logo Mail Archive

Re: [Edm] s2n-quic compliance

"Bytheway, Cameron" <bythewc@amazon.com> Wed, 16 March 2022 18:17 UTC

Return-Path: <prvs=067e005a9=bythewc@amazon.com>
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 38C083A0780 for <edm@ietfa.amsl.com>; Wed, 16 Mar 2022 11:17:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.108
X-Spam-Level:
X-Spam-Status: No, score=-14.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URI_NOVOWEL=0.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.com
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 XKzw2GIcpr0f for <edm@ietfa.amsl.com>; Wed, 16 Mar 2022 11:17:22 -0700 (PDT)
Received: from smtp-fw-6001.amazon.com (smtp-fw-6001.amazon.com [52.95.48.154]) (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 459BB3A07A4 for <edm@iab.org>; Wed, 16 Mar 2022 11:17:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1647454636; x=1678990636; h=from:to:cc:subject:date:message-id:content-id: content-transfer-encoding:mime-version; bh=vRwfkhiB1+MHbxfF53yTEKLKnWKo7fkKvdl2wrwcvZw=; b=cR2SbNc+GcN8cVYeAZFD8uMDLGuXgrwLSNIP86rTUOHvv6+w/rF/Hi56 pYLcdx+uPXjArSXou5pQCVUqyh32TfqAQbxHW3Ia7/3VB0BYkdY5pIvcg mavB621lWESYdvihoDEVRdWbijB60aXmkaXOxw1dNhwDuaWGHWlD3YNj0 4=;
X-IronPort-AV: E=Sophos;i="5.90,187,1643673600"; d="scan'208";a="186576638"
Received: from iad12-co-svc-p1-lb1-vlan3.amazon.com (HELO email-inbound-relay-pdx-2a-ff3df2fe.us-west-2.amazon.com) ([10.43.8.6]) by smtp-border-fw-6001.iad6.amazon.com with ESMTP; 16 Mar 2022 18:17:14 +0000
Received: from EX13MTAUWB001.ant.amazon.com (pdx1-ws-svc-p6-lb9-vlan2.pdx.amazon.com [10.236.137.194]) by email-inbound-relay-pdx-2a-ff3df2fe.us-west-2.amazon.com (Postfix) with ESMTPS id 0C24C41F45; Wed, 16 Mar 2022 18:17:13 +0000 (UTC)
Received: from EX13D14UWB001.ant.amazon.com (10.43.161.158) by EX13MTAUWB001.ant.amazon.com (10.43.161.207) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Wed, 16 Mar 2022 18:17:12 +0000
Received: from EX13D14UWB003.ant.amazon.com (10.43.161.162) by EX13D14UWB001.ant.amazon.com (10.43.161.158) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Wed, 16 Mar 2022 18:17:12 +0000
Received: from EX13D14UWB003.ant.amazon.com ([10.43.161.162]) by EX13D14UWB003.ant.amazon.com ([10.43.161.162]) with mapi id 15.00.1497.033; Wed, 16 Mar 2022 18:17:12 +0000
From: "Bytheway, Cameron" <bythewc@amazon.com>
To: Christopher Wood <caw@heapingbits.net>, "ietf@kuehlewind.net" <ietf@kuehlewind.net>
CC: "edm@iab.org" <edm@iab.org>
Thread-Topic: [Edm] s2n-quic compliance
Thread-Index: AQHYOWIOXbUFauGClk2WbYxxyy3QkQ==
Date: Wed, 16 Mar 2022 18:17:12 +0000
Message-ID: <89319A06-90F8-4992-9F2C-B5AAB453E4BA@amazon.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.161.236]
Content-Type: text/plain; charset="utf-8"
Content-ID: <E252E7A7E9E58B4BBCD2CE4D6BBB2E0E@amazon.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/edm/x5IZ9maLBIJZHxjhkiEOfJl7W-E>
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, 16 Mar 2022 18:19:52 -0000

Glad to see some interest in our compliance tool! It's been incredibly useful in the development of s2n-quic.

You're correct: normative requirements definitely don't capture everything. As a convenience, we automatically extract requirements using the normative wording into spec files (for example: https://github.com/aws/s2n-quic/blob/main/specs/www.rfc-editor.org/rfc/rfc9000). However, the tool isn't entirely coupled to normative wording and allows for arbitrary requirements to be defined by adding or modifying the spec files.

> 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

v2.23.0 | Report a Bug | By Email