Re: [Rfced-future] Fwd: New Version Notification for draft-iab-rfcefdp-rfced-model-08.txt

Eric Rescorla <ekr@rtfm.com> Sat, 08 January 2022 01:29 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: rfced-future@ietfa.amsl.com
Delivered-To: rfced-future@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F1413A1395 for <rfced-future@ietfa.amsl.com>; Fri, 7 Jan 2022 17:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level:
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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=rtfm-com.20210112.gappssmtp.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 s0zcy38R69JO for <rfced-future@ietfa.amsl.com>; Fri, 7 Jan 2022 17:29:39 -0800 (PST)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (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 D95713A1391 for <rfced-future@iab.org>; Fri, 7 Jan 2022 17:29:38 -0800 (PST)
Received: by mail-io1-xd2f.google.com with SMTP id y11so9323147iod.6 for <rfced-future@iab.org>; Fri, 07 Jan 2022 17:29:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bs5bxmswtygpyCPM7TwiXp9npPLvv6AeNOKIyJxBw+A=; b=pHCrGyzLQ/oeKo6o8I3mle1AXDQCujd9zE4zypRsiSFOkx9tkhMPGomxmb1JONqgaK FN/0JCpr9P0ILdVHaAolq29kCySBDPL67G0nqjOMpOSMh/gDNrYQn7XnswXdfn4CCynr PyDfrcUwW64yLgbIUAd7fQpXnVThAcrXcOJdqNM1GRYKQ2P7jK0JR5DG9RMhxBBG/muf D/+s3rH8jENkivZ+Rw824Ouja4+mHqx+zadWGNxFA7EmrLXT4RZgSTC124EBwE7H7Fxi 13N5c8pAdb7UqlOLS+SjC6lVybOcPMe7F8DaTIumSJKWuCusy6w18kpNR2FmZqONXybd ozVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bs5bxmswtygpyCPM7TwiXp9npPLvv6AeNOKIyJxBw+A=; b=hASxOwJ1q35sf/LsSHXeuWkp1bdcp95qm4iMsbG2Xe0dYyBc7kEjHgFQfOF5d+JX3l WNtumck+mgY5A15vmt8ihkhJ4Zw7mNa7SUTr2bkvjJvXj5JOi9NPd7Px6XujLvur8qyF wF6WonZWuJojnbkJWfOyzWEy7sTpk/RaM9C9v/kAbJlBVwn5CCnuxcBn8YvTQ1TYDamz Gw6NyCJ/ddHk4h4ooCIfN7c2/CMoaEC+3381CkZ1mj5yz7PdPa2fmAv/9SPTotGVtoQr f5/5TDGrQFoxaiD45cSK4KyR5N7iKrHcl2LLF2hOai/dUGAN6XyhzgSMCscvpHE899Yd uP/A==
X-Gm-Message-State: AOAM5320fnE7NP62qxH4gHMH3trkYuO9Cs+LtNf+YmbBh3Ta9asXt920 qKRhhyKNNAqcqRgrW3mJ8bGafYHXELxt6YdOwf6XvQ==
X-Google-Smtp-Source: ABdhPJwZJuUQpznYwLtiaDue3k73krVysLHFGX0bVp++StIovMtaG2/nxERysyqT7ucut3l4CqyNJ1PMPcqsuDsqu0A=
X-Received: by 2002:a05:6602:1641:: with SMTP id y1mr2100959iow.50.1641605377266; Fri, 07 Jan 2022 17:29:37 -0800 (PST)
MIME-Version: 1.0
References: <164159953944.5205.10517887235280838552@ietfa.amsl.com> <1e6664f9-f19d-a226-e709-d03fe6968497@stpeter.im> <4d5c48a8-97ae-a984-bb43-3728849bfc54@gmail.com>
In-Reply-To: <4d5c48a8-97ae-a984-bb43-3728849bfc54@gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 07 Jan 2022 17:29:01 -0800
Message-ID: <CABcZeBP1KR24_R7k2obs1VUc-L_YBgnJJ0Ex2D_sWpoWtpDajw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org
Content-Type: multipart/alternative; boundary="0000000000005fa80105d5080918"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/srqBAqLpf8svqQTaIRgTNJZX92k>
Subject: Re: [Rfced-future] Fwd: New Version Notification for draft-iab-rfcefdp-rfced-model-08.txt
X-BeenThere: rfced-future@iab.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: RFC Editor Future Development Program <rfced-future.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/rfced-future>, <mailto:rfced-future-request@iab.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfced-future/>
List-Post: <mailto:rfced-future@iab.org>
List-Help: <mailto:rfced-future-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/rfced-future>, <mailto:rfced-future-request@iab.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Jan 2022 01:29:44 -0000

Perhaps "not rough consensus" would be even more grammatical

On Fri, Jan 7, 2022 at 5:13 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> Looks pretty good to me. One thing:
>
> > The RSAB member believes, based on the results of the community call(s)
> for comment Section 3.2.3, that there is no consensus to advance the
> proposal.
>
> Should that be "no rough consensus" to avoid any doubt?
>
> Regards
>     Brian
>
> On 08-Jan-22 12:53, Peter Saint-Andre wrote:
> > As promised...
> >
> >
> > -------- Forwarded Message --------
> > Subject: New Version Notification for
> draft-iab-rfcefdp-rfced-model-08.txt
> > Date: Fri, 07 Jan 2022 15:52:19 -0800
> > From: internet-drafts@ietf.org
> > To: Peter Saint-Andre <stpeter@stpeter.im>
> >
> >
> > A new version of I-D, draft-iab-rfcefdp-rfced-model-08.txt
> > has been successfully submitted by Peter Saint-Andre and posted to the
> > IETF repository.
> >
> > Name:         draft-iab-rfcefdp-rfced-model
> > Revision:     08
> > Title:                RFC Editor Model (Version 3)
> > Document date:        2022-01-07
> > Group:                iab
> > Pages:                31
> > URL:
> > https://www.ietf.org/archive/id/draft-iab-rfcefdp-rfced-model-08.txt
> > Status:
> > https://datatracker.ietf.org/doc/draft-iab-rfcefdp-rfced-model/
> > Htmlized:
> > https://datatracker.ietf.org/doc/html/draft-iab-rfcefdp-rfced-model
> > Diff:
> > https://www.ietf.org/rfcdiff?url2=draft-iab-rfcefdp-rfced-model-08
> >
> > Abstract:
> >      This document specifies version 3 of the RFC Editor Model.  The
> model
> >      defines two high-level tasks related to the RFC Series.  First,
> >      policy definition is the joint responsibility of the RFC Series
> >      Working Group (RSWG), which produces policy proposals, and the RFC
> >      Series Approval Board (RSAB), which approves such proposals.
> Second,
> >      policy implementation is primarily the responsibility of the RFC
> >      Production Center (RPC) as contractually overseen by the IETF
> >      Administration Limited Liability Company (IETF LLC).
> >
> >      This document obsoletes RFC 8728.  This document updates RFC 7841,
> >      RFC 8729, and RFC 8730.
> >
> >
> >
> >
> > The IETF Secretariat
> >
> >
>
> --
> Rfced-future mailing list
> Rfced-future@iab.org
> https://www.iab.org/mailman/listinfo/rfced-future
>