IETF Logo Mail Archive

Re: [Rfced-future] AUTH48 and editing before approval (was: Re: Welcome to the RFC Editor Future Development Program)

Eliot Lear <lear@cisco.com> Thu, 02 April 2020 17:26 UTC

Return-Path: <lear@cisco.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 C0A753A0D2D for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 10:26:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level:
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 ejtDzS2LWhZZ for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 10:26:25 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E8ED3A0BFB for <rfced-future@iab.org>; Thu, 2 Apr 2020 10:26:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1162; q=dns/txt; s=iport; t=1585848366; x=1587057966; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=zp9GwORJIHVqiVDUqaGWGacpJdNIj35z7j6xf+mxFbI=; b=g6bO/BWRi+fF8tAyFvrm1aoFOIoqnA1MMjd+OXropFz+m0ivviT7Q8eD 41abLC0m/ghyy46JgTRQwItoghYUe2+9YdJbxL4sXg3kiqG5mWmcIxbpT 8n5pxio2UZFVzHB+RvxhNqqlphBuC+Ch3KdXix7JpqXuDxfTl5Gpo/J5D o=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAQD/H4Ze/xbLJq1mGwEBAQEBAQEFAQEBEQEBAwMBAQGBe4NpASASjUaHaJNiiAoKAQEBDAEBLwQBAYREAoJlOBMCAwEBCwEBBQEBAQIBBQRthWKFZwoGeRALAwEKLQtXBoM5gn2vHIInhUuFKIE4jEuCAIE4DBSCHy4+iBKCLASHA5EVmGqCR4JdlD4dm3KoCYM2AgQGBQIVgWkigVczGggbFWUBgj89EhgNjlWOEj8Dj3cBAQ
X-IronPort-AV: E=Sophos; i="5.72,336,1580774400"; d="scan'208,217"; a="24939899"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 Apr 2020 17:25:59 +0000
Received: from ams3-vpn-dhcp3624.cisco.com (ams3-vpn-dhcp3624.cisco.com [10.61.78.40]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 032HPwrZ010359 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 2 Apr 2020 17:25:59 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <A5C7C919-4389-4D6E-82D0-6315456C8455@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_ED812DAE-2190-41E5-AD44-DED2B0BF0CD5"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Date: Thu, 02 Apr 2020 19:25:58 +0200
In-Reply-To: <BB09DB5B-4E79-4739-9D58-F1D0D49D9BDD@tzi.org>
Cc: Ted Lemon <mellon@fugue.com>, John C Klensin <john-ietf@jck.com>, rfced-future@iab.org, Christian Huitema <huitema@huitema.net>, Russ Housley <housley@vigilsec.com>
To: Carsten Bormann <cabo@tzi.org>
References: <d95d9ca5-77d4-490d-1fe7-35b20db01016@joelhalpern.com> <4BC58577-8CC7-48CB-803F-F4E6E080188B@huitema.net> <75FEFDC1BB902A9091739F47@PSB> <DF85BBBB-B9D3-4852-89FC-0B971548A905@vigilsec.com> <E7A94449-BBC7-407B-820A-32DA6FBD7BF8@fugue.com> <BB1A84EB-2C05-42A6-A1B8-E0830695AC95@vigilsec.com> <B4BC8DD4-848A-4192-B1C5-7A66A7963976@fugue.com> <BB09DB5B-4E79-4739-9D58-F1D0D49D9BDD@tzi.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
X-Outbound-SMTP-Client: 10.61.78.40, ams3-vpn-dhcp3624.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/nGWIiy65QY8wdvqWbSuc43aWTGA>
Subject: Re: [Rfced-future] AUTH48 and editing before approval (was: Re: Welcome to the RFC Editor Future Development Program)
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: Thu, 02 Apr 2020 17:26:33 -0000

All:

Can we distill the high level point that needs addressing in this process?

Are the touch points and flow the responsibility of the RFC Editor to define, or should that be this group?

Eliot

v2.23.0 | Report a Bug | By Email