IETF Logo Mail Archive

Re: [fdt] Proposed charter text & meeting

David Kemp <dk190a@gmail.com> Mon, 07 September 2020 11:44 UTC

Return-Path: <dk190a@gmail.com>
X-Original-To: fdt@ietfa.amsl.com
Delivered-To: fdt@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931443A0C23 for <fdt@ietfa.amsl.com>; Mon, 7 Sep 2020 04:44:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 KzoIu7Id3tgq for <fdt@ietfa.amsl.com>; Mon, 7 Sep 2020 04:44:22 -0700 (PDT)
Received: from mail-oi1-x22a.google.com (mail-oi1-x22a.google.com [IPv6:2607:f8b0:4864:20::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 227533A0C0A for <fdt@ietf.org>; Mon, 7 Sep 2020 04:44:22 -0700 (PDT)
Received: by mail-oi1-x22a.google.com with SMTP id 3so13379949oih.0 for <fdt@ietf.org>; Mon, 07 Sep 2020 04:44:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=8xyjvyHnPg3fFgaE4zf+A7LpE+PkTxJsamj4kIeXHC0=; b=YJanuKlZDVlAbrN4yA654OhjtG3O+r4s3bdPADz3wKDxQ28sXra6CPoFKwQLu2vBrv w3hUxOUd5T8KRmUxZZOxpNcHLhWsp+xWHIBAcA9eKSQsnWFAhuWgGgiYQCs8MgLSx3TJ XJFtdJLcLFq16+yKV+ezZRAaRJHC89XdfRgaV4U0yZBUUODywFnjjPbZHmX4rccAGYRN X9gEgHf1T70YlLAzha16NTRjdqqb4hMIDZxwXFfh1SElFn3YEBsxTy8EYcBTBxY1t9DE LLG1MB9Q9Rod2eI3KNZt0NMjIOpCtnbHAwFWk+o4Z1bqHlC91idqb8tfFLnIXvyZkzHW uygQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=8xyjvyHnPg3fFgaE4zf+A7LpE+PkTxJsamj4kIeXHC0=; b=UQW4pGcDvQDBXxZwUk1ys60n3Yt8tugpW6t5qgD9CqUeO27XLI1Lfa1UAxXJ3lXUx/ qkn2bX2x1KMnw5WEqJfFGDIMoCx409eK5093OPussMo0/rknHBv6jqhJuN1VrBcX5di6 RADFSL8UFYaxdtKBuuy0UnhtxqG3qTy9PqRIs0lyVJVRcVqZmHuo+zwPfArTGGHhbssf rxr9393r2RqOqNiHqimdPyZR+CZFyvix8N+h2INRm0xJsFFPBfvkLqOq3tXSTeyWYV8L NJ16dyeHFa9IhOrqM/ifGW2fGaBAElsHw/SbUjW+eYpTabXa7T0IXASPj11PCMAvyMZW nECA==
X-Gm-Message-State: AOAM532TIBx9tvvp2jVUIbAqjGZOzEE9GFHVJZpzW0QlR3NWYVg1R2M3 Gjl6hgV/xuj6/zr0TFFWApTkabt03+P/7OWOLua9JnHQXHxiZg==
X-Google-Smtp-Source: ABdhPJxO4+2qOgo1+0NjE0TwmYnAquoeL/GwKfslDRm6wZhxE0DgITi16UdoHfqnRbLbVoYncrC7NsH3068gvvw8BGM=
X-Received: by 2002:aca:c46:: with SMTP id i6mr11674160oiy.114.1599479060600; Mon, 07 Sep 2020 04:44:20 -0700 (PDT)
MIME-Version: 1.0
References: <16D9B498-78F0-41AB-BAFC-77250C084A33@smcquistin.uk> <20200906132332.GA29463@nic.fr> <03ADDAB1-2298-49E5-ABA8-3A0241663D39@smcquistin.uk>
In-Reply-To: <03ADDAB1-2298-49E5-ABA8-3A0241663D39@smcquistin.uk>
From: David Kemp <dk190a@gmail.com>
Date: Mon, 07 Sep 2020 07:44:09 -0400
Message-ID: <CAE5tNmoF82tZm0-0ZMv8Jk5sALc=vLwsGudHkKPjaNPU6Kkf=g@mail.gmail.com>
To: fdt@ietf.org
Content-Type: multipart/alternative; boundary="0000000000003b9b2e05aeb7bd2d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/fdt/H9LDO4Vi6U1Sz4ITcBODWMY8Ds4>
Subject: Re: [fdt] Proposed charter text & meeting
X-BeenThere: fdt@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Mailing list for the discussion of the use of formal description techniques in IETF documents <fdt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fdt>, <mailto:fdt-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/fdt/>
List-Post: <mailto:fdt@ietf.org>
List-Help: <mailto:fdt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fdt>, <mailto:fdt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Sep 2020 11:44:24 -0000

>
> The use of natural language and unstructured diagrams to describe
> protocols, both in the development process, and in the documents
> themselves, can lead to standards documents that contain inconsistencies
> and ambiguities.
>

Is this situation more likely to occur, or less likely to be corrected,
when applied in "The incremental, distributed, and consensus-driven
standards development process adopted by the IETF"?

I don't know the answer, it's something to consider.

On Mon, Sep 7, 2020 at 3:54 AM Stephen McQuistin <sm@smcquistin.uk> wrote:

> Hi,
>
> > On 6 Sep 2020, at 14:23, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> >
> > On Mon, Aug 17, 2020 at 09:00:25AM +0100,
> > Stephen McQuistin <sm@smcquistin.uk> wrote
> > a message of 88 lines which said:
> >
> >> I've produced draft charter text:
> >>
> >>    https://hackmd.io/@fdt/S1wTyI-fv <https://hackmd.io/@fdt/S1wTyI-fv>
> >
> > I would delete the "The incremental, distributed, and consensus-driven
> > standards development process adopted by the IETF can lead to" because
> > there is no proof (or even hint) that the problem of "inconsistencies
> > and ambiguities" would be solved by a more formal and bureaucratic
> > top-down process.
>
> It wasn’t intended to imply that the incremental, distributed, and
> consensus-drive elements of the standards process are, on their own, causes
> of inconsistencies and ambiguities. I meant it to be taken to with the next
> sentence, to imply that:
>
> incremental, distributed, consensus-driven approach → use of natural
> language → inconsistencies and ambiguities
>
> Will bash on these two sentences.
>
> > Also, may be we could add in the charter references to relevant RFC
> > (RFC 4977) and existing work
> > such as draft-mcquistin-augmented-ascii-diagrams or to past work such
> > as the FSM BoF at IETF 68 in Prague
> > <https://www.ietf.org/proceedings/68/fsm.html>?
>
> Agreed.
>
> Thanks,
>
> Stephen
> --
> FDT mailing list
> FDT@ietf.org
> https://www.ietf.org/mailman/listinfo/fdt
>

v2.23.0 | Report a Bug | By Email