[rfc-i] Table of conformance requirements.

Phillip Hallam-Baker <phill@hallambaker.com> Thu, 18 June 2020 03:49 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CAAA53A0E04; Wed, 17 Jun 2020 20:49:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.65
X-Spam-Level:
X-Spam-Status: No, score=-2.65 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 QEp3UQkYYOOk; Wed, 17 Jun 2020 20:49:25 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FFFF3A0E05; Wed, 17 Jun 2020 20:49:25 -0700 (PDT)
Received: from rfcpa.amsl.com (localhost [IPv6:::1]) by rfc-editor.org (Postfix) with ESMTP id 35FE2F40711; Wed, 17 Jun 2020 20:49:20 -0700 (PDT)
X-Original-To: rfc-interest@rfc-editor.org
Delivered-To: rfc-interest@rfc-editor.org
Received: from localhost (localhost [127.0.0.1]) by rfc-editor.org (Postfix) with ESMTP id 2C8D0F40711 for <rfc-interest@rfc-editor.org>; Wed, 17 Jun 2020 20:49:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at rfc-editor.org
Received: from rfc-editor.org ([127.0.0.1]) by localhost (rfcpa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8aBp4CnYRBWl for <rfc-interest@rfc-editor.org>; Wed, 17 Jun 2020 20:49:18 -0700 (PDT)
Received: from mail-ot1-f44.google.com (mail-ot1-f44.google.com [209.85.210.44]) by rfc-editor.org (Postfix) with ESMTPS id E0137F406C4 for <rfc-interest@rfc-editor.org>; Wed, 17 Jun 2020 20:49:17 -0700 (PDT)
Received: by mail-ot1-f44.google.com with SMTP id m2so3430903otr.12 for <rfc-interest@rfc-editor.org>; Wed, 17 Jun 2020 20:49:22 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=aZ2NEK1ODDQZMXVrSIK33BtuHnRP/6eZlxsVHzgt1M4=; b=s0Ms7DY7SRzt2I2oQ96XX2H4p3d+/CGP7lEg/kqKQK6xk8XijXDhUWagOf7bEoXJZ4 hqgibcdK1r4+4A8CiT5AbmEHHxyLcN6YMTOrRcnR76kR26w8AnA5S9Z4qOfXXNQRsnla pwV6VuXPdfEjF+MUrOQ3MX5OotbhTWZbxvQwQbNpBL2HzjtQrpEfOGNOlSGOp66rDUtz I+mM2ct6tCPEiTJ2IJep4feVYBLJzppIzC4dKdpMoXo6z8KM61Gui+0ymwyajC9nzz7Z xSFKNbxXsbo+8AmTBQRlJIlIt188I1+5mXqdb6fyTIGM9EhLHbvdKN2nDfdlWJoPkIWU FiKA==
X-Gm-Message-State: AOAM531PsZinO5hr98V89d0PJ/SRqTx465ZLSVVUG/ODOlNZ6gBn3sgo Jm9e+zGy4xAMOqttxrwhGdpUWX6GO0PeV35OuyAdTJuw
X-Google-Smtp-Source: ABdhPJwH+Nd+di7eQ+y9isWXjTtBlkjo0raDHDkslidjlXpIbRoHV7nQN2/06a9klfsP1OIFSfkcU17hKbNqWXs7Faw=
X-Received: by 2002:a9d:104:: with SMTP id 4mr1701471otu.124.1592452161836; Wed, 17 Jun 2020 20:49:21 -0700 (PDT)
MIME-Version: 1.0
From: Phillip Hallam-Baker <phill@hallambaker.com>
Date: Wed, 17 Jun 2020 23:49:10 -0400
Message-ID: <CAMm+LwiMOHMWcxFCYMdW_fsWsPpkC0vTt_0=+MzQfCm4qy=PTw@mail.gmail.com>
To: RFC Interest <rfc-interest@rfc-editor.org>
Subject: [rfc-i] Table of conformance requirements.
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://www.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <http://www.rfc-editor.org/pipermail/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://www.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2030797451822237859=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: "rfc-interest" <rfc-interest-bounces@rfc-editor.org>

All,

I would like to propose an indexed table of all MUST/SHOULD/MAY normative
language for RFCs with labels for each requirement.

I already have code to do this but I have realized I need to go further to
really bind specification and implementation together properly.

Each MUST in a specification should have at least one corresponding unit
test to check compliance. And there should be a mechanism which allows the
test set to be audited against the specification. Which means that I need
to be able to label each requirement.

So in the text the requirement would be 'clients MUST send round pegs' and
in the list this would be something like

MUST-2: Round Pegs

And this needs to be expressible somehow in XML.

Comments?
_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://www.rfc-editor.org/mailman/listinfo/rfc-interest