IETF Logo Mail Archive

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

Jean Mahoney <jmahoney@amsl.com> Thu, 13 January 2022 23:26 UTC

Return-Path: <jmahoney@amsl.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 324613A0B38 for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 15:26:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.613
X-Spam-Level:
X-Spam-Status: No, score=-2.613 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.714, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 rc5-fyxcp9vh for <rfced-future@ietfa.amsl.com>; Thu, 13 Jan 2022 15:26:06 -0800 (PST)
Received: from c8a.amsl.com (c8a.amsl.com [4.31.198.40]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A9573A0B34 for <rfced-future@iab.org>; Thu, 13 Jan 2022 15:26:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by c8a.amsl.com (Postfix) with ESMTP id 01DAF425A344; Thu, 13 Jan 2022 15:26:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from c8a.amsl.com ([127.0.0.1]) by localhost (c8a.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id i-R3Ki7PGZB5; Thu, 13 Jan 2022 15:26:04 -0800 (PST)
Received: from [192.168.1.203] (unknown [47.186.34.206]) by c8a.amsl.com (Postfix) with ESMTPSA id B31AE424B435; Thu, 13 Jan 2022 15:26:04 -0800 (PST)
Message-ID: <d3429b9c-5880-e342-5b62-3b92e37129cf@amsl.com>
Date: Thu, 13 Jan 2022 17:26:03 -0600
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.5.0
Content-Language: en-US
To: Peter Saint-Andre <stpeter@stpeter.im>, Eric Rescorla <ekr@rtfm.com>, Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: rfced-future@iab.org
References: <CABcZeBO3-q+SMTFNZyeC50eghFs1CJNSLojmr1Zip1g_nsGZHQ@mail.gmail.com> <d7ce7879-2324-69d1-0770-e104aff6c68c@stpeter.im> <CABcZeBMtZUa9cdr6a7znjdMY3UwNPpg2d0d4KwosfmzE1KqmxQ@mail.gmail.com> <06414ab1-c53f-e542-52ff-800b99c23ef1@gmail.com> <CABcZeBPTPjRWBqkQzzOpTkOVj+yCQdup4rSWp=Ca+r653bicjg@mail.gmail.com> <48449fa5-16f1-e8e6-c498-54d3506d93a7@stpeter.im>
From: Jean Mahoney <jmahoney@amsl.com>
In-Reply-To: <48449fa5-16f1-e8e6-c498-54d3506d93a7@stpeter.im>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfced-future/jQQ5u1K7p7Munu7Xc2SRcU_aM3E>
Subject: Re: [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: Thu, 13 Jan 2022 23:26:12 -0000

(with my RPC hat on)

Hi all,

On 1/6/22 8:10 PM, Peter Saint-Andre wrote:
> On 1/3/22 7:36 PM, Eric Rescorla wrote:
>>
>>
>> On Mon, Jan 3, 2022 at 5:26 PM Brian E Carpenter 
>> <brian.e.carpenter@gmail.com <mailto:brian.e.carpenter@gmail.com>> 
>> wrote:
>>
>>     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>
>>     <mailto: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>>
>>      >      >
>> <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?

[JM] Yes. Per their contract, the RPC keeps records of edits and author 
interactions. These records are not public.

Best regards,

Jean


>>
>>
>>     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.
>>
>>
>> Agreed. I don't actually have strong feelings about any of this and 
>> would
>> be fine if we struck this text. I'm just trying to review it from the 
>> perspective
>> of "does this say what we want" and "can it be executed"?
>
> Before we settle this issue, I'd like to hear from Jay (who is on 
> vacation) or RPC folks.
>
> Peter
>

v2.23.0 | Report a Bug | By Email