[Rfced-future] Issue 147 [WGLC Review of the draft]

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 04 January 2022 01:26 UTC

Return-Path: <brian.e.carpenter@gmail.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 83B633A1397 for <rfced-future@ietfa.amsl.com>; Mon, 3 Jan 2022 17:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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 DjxN3sRnM5yF for <rfced-future@ietfa.amsl.com>; Mon, 3 Jan 2022 17:26:09 -0800 (PST)
Received: from mail-pj1-x1031.google.com (mail-pj1-x1031.google.com [IPv6:2607:f8b0:4864:20::1031]) (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 34F0D3A1396 for <rfced-future@iab.org>; Mon, 3 Jan 2022 17:26:09 -0800 (PST)
Received: by mail-pj1-x1031.google.com with SMTP id v16so30082762pjn.1 for <rfced-future@iab.org>; Mon, 03 Jan 2022 17:26:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=bFvQ4QBwwPIUoqgHJ8Sr/Bz9n3+zPFTXZCEFnNXlY1Q=; b=jJGXUIWbTA1F3Bk5WCVZ0xyfCuERHe2YiHtnC5hvwqVHkgZ6Yp31icaHAqxtoU4CwK U5f05aK0KLlHr6HLW/AlfnFJHP6fxjJ0hvgJteA2aqRl641bQK4jkNshs3PIBs89BMiE SnlyRJOZS2H34q+hkXhnS+A4NU6OEI2UTpXRe2fNGSI8d6QQ/zisfJEXclG+0R7L5YSq o5U/F4qc/R79wDF09qTwOpwc4x71OupSR9r8GtDZbHKedHloNKLzOZJHCg3F3o7yNGum 4pbhSC9a9j/MUinMWKVnOXHq9fOgDuMa3/Ola/imppOyLqGDNQs8/n9R9jHR76CfQr6N F2XA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=bFvQ4QBwwPIUoqgHJ8Sr/Bz9n3+zPFTXZCEFnNXlY1Q=; b=FayIccEu/wiPoKC0d/gOTyUm5TMtEXwGEJTyS75lEi3wggIbVkUqyriJxarW1eEOV/ x1r+p2flW8A9h1ricAu8OSduPTc1bXKlnSikrlWz3ei918vzWVZYD5lMoldxxfStuH5f BBwslRqRxv8W4+9hNW2FWlgSDg/cGWCka4xdbnPXNYEkTkFJty8yMoY1m/Dryla+DewK tCJyRCVPVzedwyeFQQ1dZeX7lCBT5GVIn9Bxk4egeT6KfVjUn/mH5ktcFAy+rTmU8Aeb BnYuVjh7Yt3Hf9Thq0PRvl6Guj1wUviWJIfkRgtTul+tbOyL8aKK32pdtnccbDZta3Ev HDLw==
X-Gm-Message-State: AOAM533VLFJWuXekY+WhUJvCv+Pwc8hP+xQNzCyZ05McLdd0Qyh4ImKT ABERFEgdI4Q2aLLkjN6dARR5IyaeMItRVQ==
X-Google-Smtp-Source: ABdhPJxCiD8iBbIy3gYQnfrF40woUTbk983DY9DmTMDnEewMpKRMzB8pCc/80+L3FFONYHkwZLagYA==
X-Received: by 2002:a17:90b:384e:: with SMTP id nl14mr58894628pjb.243.1641259567316; Mon, 03 Jan 2022 17:26:07 -0800 (PST)
Received: from ?IPv6:2406:e003:1071:1701:db7:d041:a2d:ce65? ([2406:e003:1071:1701:db7:d041:a2d:ce65]) by smtp.gmail.com with ESMTPSA id h3sm31926320pjk.48.2022.01.03.17.26.05 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 03 Jan 2022 17:26:06 -0800 (PST)
To: Eric Rescorla <ekr@rtfm.com>, Peter Saint-Andre <stpeter@stpeter.im>
Cc: rfced-future@iab.org
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <CABcZeBMtZUa9cdr6a7znjdMY3UwNPpg2d0d4KwosfmzE1KqmxQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <06414ab1-c53f-e542-52ff-800b99c23ef1@gmail.com>
Date: Tue, 04 Jan 2022 14:26:02 +1300
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBMtZUa9cdr6a7znjdMY3UwNPpg2d0d4KwosfmzE1KqmxQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/-Mvb7EsUswrdBt3rA3UolthxdYQ>
Subject: [Rfced-future] Issue 147 [WGLC Review of the draft]
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: Tue, 04 Jan 2022 01:26:14 -0000

On 04-Jan-22 13:43, Eric Rescorla wrote:

On one point only:

> 
> 
> On Mon, Jan 3, 2022 at 4:39 PM Peter Saint-Andre <stpeter@stpeter.im <mailto:stpeter@stpeter.im>> wrote:
> 
>     On 1/3/22 5:19 PM, Eric Rescorla wrote:

...
>      > Issue 147: This requires the RPC to keep certain records,
>      > e.g., of dialogue with document authors. Does that formally
>      > happen now, or is it just in people's e-mail folders?
>      > Do these records need to be public?
>      > https://github.com/intarchboard/program-rfced-future/issues/147 <https://github.com/intarchboard/program-rfced-future/issues/147>
>      > <https://github.com/intarchboard/program-rfced-future/issues/147 <https://github.com/intarchboard/program-rfced-future/issues/147>>
> 
>     It's not clear to me whether all record-keeping needs to be public. It
>     might be acceptable that records are kept and available on request if
>     needed (e.g., in case of an appeal).
> 
> 
> I think that would be OK. But do they keep records at all?


I can't answer that. But I suspect that there might, rarely, be matters
that would be considered private, especially for the Independent Stream
if publishing a proprietary spec. So any policy for making the records
public would need to allow privacy exceptions.

However, I just glanced over the messages in my archive about AUTH48,
and I can't see any case that seems private. Even in a couple of cases
where advice was sought from the (former) RSAG, I don't see anything
sensitive.

One small point: if we add text stating that future records will be
public, or available on request, we'd better state that this is
not automatically retroactive for previous records.

    Brian