IETF Logo Mail Archive

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

Ted Lemon <mellon@fugue.com> Thu, 02 April 2020 16:55 UTC

Return-Path: <mellon@fugue.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 244FF3A0C22 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 09:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 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_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=fugue-com.20150623.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 3MMIcGEDCaZA for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 09:55:33 -0700 (PDT)
Received: from mail-qk1-x742.google.com (mail-qk1-x742.google.com [IPv6:2607:f8b0:4864:20::742]) (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 6F3CF3A0966 for <rfced-future@iab.org>; Thu, 2 Apr 2020 09:55:24 -0700 (PDT)
Received: by mail-qk1-x742.google.com with SMTP id u4so4658697qkj.13 for <rfced-future@iab.org>; Thu, 02 Apr 2020 09:55:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=Gi1BNn7gGa+w6RTmIE73Nz+oxqV8P4/cj74t/auO0VQ=; b=wc/KcvDU+AIw0vPZcb9AKQxX3zfIfdzfbU21pLScOGL4bKZgVVF0nM0zKPmoxxvsKO HKI5FPFrROHm8hct+x8f8GO882rDgGazqEw9S2HTgeSEhnvuv6swbGngT/CvyABVGXsA zCpnz3brwg0AT9h4iCxFmsT04vAI7/+0RP5jSrDdwWZPcc/BoASnUCVEbmW1EAEWIcgo 6CKwjwf0uM1uSz2S7T6EMBfevT3PpScKwt9J206JEV4d1o/9suLSpQSocB9SajKSBpTr 5mpf8o/yxF/VLWoh1eGTi+so4YbpIN5iNjNwBefdWwPAWX3A9sg3EBCKdXXwrrCe87lW Ghaw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=Gi1BNn7gGa+w6RTmIE73Nz+oxqV8P4/cj74t/auO0VQ=; b=OlTurVPj0/i1JoFyMN7g4E1rahqTcvrbvcWjluK1e+kIAsH/j2OoKTgLkEwKs+sPQM lShHJyWsLzLuo3o9srzv/VtfQ86Nez0zQNmLlRJlFCLkqdSCt3rTedcrB4f0SuK4tnWa eYSKCCe6ZLOFIO9x33I/Lyc6kSQtjrYT2Ew1CPAcLZTjYavLntfwbDElXED+k0vyS5c0 wbLDShvQQpqJILWVA9QjGNAqNg9yVLeIGXT95v++yqLkqIe3kBflr+tDzpHGGpXqx3Dc 3YHWh5GNyepSMD0H2K/cZOLpxq5IUhAjygyXm6Rk2fYZvyPiaqyI5XIMpB83ys+MZGzn j4qw==
X-Gm-Message-State: AGi0Pubab7YVHsEyLKHmxGQGEM//uSvLFXxyGJRVeNnihFWnICDR+/2F W7GmfnSyFnf9pdhiuoGQSjL14g==
X-Google-Smtp-Source: APiQypL6rTbOnGuSZ9sH+oMDS189MJjwZzhRmJEKceL6OeKyheJVaRbUbRxVM26RkV2iPw80jAkb6w==
X-Received: by 2002:a37:a151:: with SMTP id k78mr4548055qke.62.1585846523440; Thu, 02 Apr 2020 09:55:23 -0700 (PDT)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.ma.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id f7sm1074834qtq.33.2020.04.02.09.55.22 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2020 09:55:22 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <B4BC8DD4-848A-4192-B1C5-7A66A7963976@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3C96EF9D-BD33-4262-B94D-DE4CAA202D14"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3622.0.6\))
Date: Thu, 02 Apr 2020 12:55:21 -0400
In-Reply-To: <BB1A84EB-2C05-42A6-A1B8-E0830695AC95@vigilsec.com>
Cc: John C Klensin <john-ietf@jck.com>, Christian Huitema <huitema@huitema.net>, rfced-future@iab.org
To: Russ Housley <housley@vigilsec.com>
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>
X-Mailer: Apple Mail (2.3622.0.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/7KHFNlqIi0s5ixMn0czUQiidUak>
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 16:55:43 -0000

On Apr 2, 2020, at 12:51 PM, Russ Housley <housley@vigilsec.com> wrote:
> This is very rare, but it does happen.  When it does, the AD needs to decide if the fix is obvious or if the fix need to go back to a WG or IETF Last Call.

I agree.  Just saying, there could be a more detailed policy written if someone wants it, and there is no way to make this problem go away that doesn’t guarantee worse outcomes.

v2.23.0 | Report a Bug | By Email