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 17:39 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 D215B3A0C14 for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 10:39:24 -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 IlJVFFWn1btd for <rfced-future@ietfa.amsl.com>; Thu, 2 Apr 2020 10:39:23 -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 8A1F03A0C13 for <rfced-future@iab.org>; Thu, 2 Apr 2020 10:39:23 -0700 (PDT)
Received: by mail-qk1-x742.google.com with SMTP id l25so4913496qki.7 for <rfced-future@iab.org>; Thu, 02 Apr 2020 10:39:23 -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=7MvABQrN0xgQmfncvJIcIu4PfyNgbPveux3O4Ha2YBU=; b=rhZv3drVVIXa+HwKnfW7afKX0hiaEXry69LNe8kIOJmS3w7vdo1mb3nAkiMEMn69YU IXePTllOCRVKT3UFwcRdcOjYS9sUKo+TiYng18eF8SYdnwR7aR8nb6psl+qrNOVavl8C paAiy0WZse0NbXuRYE/OyIsBVi1osjbpqVsyZ8lOjcHTsqvzypbXM7IICc+3rBbKMpfG IwLMPPCTMDx6NUOJ8g+tjxN5ylaHD1XagjrHJcbtm0Naok93AVyR2A//MdDOlw+4up6q G1+lFhlNLGJAHUtWgBFDfyuQIbrt1D0/qhdMKtUzGaz4dMg2vpeYCYn0ZPTWkyL7sLnr bslw==
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=7MvABQrN0xgQmfncvJIcIu4PfyNgbPveux3O4Ha2YBU=; b=Avodx33rfNX3GAho3SZhc9LK+r+TAgUsYYjlLR6Evi+EVBWHS0CcNkq6OLY52gyxvO s2/FnUaU1jYc/oktQnTJrN3QVjRUzIpCK3HU93tQ4BVDP5jcEhmiqnczdGkzmbloLUkj NQGMpqaS5F9cLM7qCH0QBq4EpRDnmdGAdWMqwTNXh9mSovQJVgw+xGBEUhhKDum4zirq dRX1zFA1tEU7xb3L+MlinxKUuGuT+MeZfwFpaDGBR/eFbEVvRUMibO5wRpO+0GN3NuvC n7l8D+EqJ8DOe3+MLcG2awsqeq4yg4oVDc8++lY8rImn1WSFYOC/hluGC8y1LYDg4tJQ GUsw==
X-Gm-Message-State: AGi0PuZFAY+pmj077SKhVeqDHITZfiV6ylATDwWfAtuj94j59Ocx9GvK BIRCuWo9CvKJ1aSgNzFEJ260CQ==
X-Google-Smtp-Source: APiQypL3jh3v3ldlFYiHZTasVIRFkYwLxQ+tWKecr4spu9xk6h2df4lkof6sTwgXnQY75b6jKbalZg==
X-Received: by 2002:ae9:e210:: with SMTP id c16mr96241qkc.179.1585849162462; Thu, 02 Apr 2020 10:39:22 -0700 (PDT)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id v75sm4092158qkb.22.2020.04.02.10.39.21 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 02 Apr 2020 10:39:21 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <10C6D11D-69C8-4913-A48A-CF5EEBCDE590@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_BD6CAA88-0652-4CFD-9CF8-62CDAF1F0CBC"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3622.0.6\))
Date: Thu, 02 Apr 2020 13:39:20 -0400
In-Reply-To: <A5C7C919-4389-4D6E-82D0-6315456C8455@cisco.com>
Cc: Carsten Bormann <cabo@tzi.org>, John C Klensin <john-ietf@jck.com>, rfced-future@iab.org, Christian Huitema <huitema@huitema.net>, Russ Housley <housley@vigilsec.com>
To: Eliot Lear <lear@cisco.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> <B4BC8DD4-848A-4192-B1C5-7A66A7963976@fugue.com> <BB09DB5B-4E79-4739-9D58-F1D0D49D9BDD@tzi.org> <A5C7C919-4389-4D6E-82D0-6315456C8455@cisco.com>
X-Mailer: Apple Mail (2.3622.0.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/dUhPR3InzDxwhXrNsYrFZRNYh5c>
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:39:25 -0000

On Apr 2, 2020, at 1:25 PM, Eliot Lear <lear@cisco.com> wrote:
> Are the touch points and flow the responsibility of the RFC Editor to define, or should that be this group?

My conclusion from this discussion is that the AUTH48 question is out of scope for this group.

v2.23.0 | Report a Bug | By Email