Re: [openpgp] heads-up: re-chartering the OPENPGP WG

Derek Atkins <derek@ihtfp.com> Wed, 21 October 2020 12:36 UTC

Return-Path: <derek@ihtfp.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B504B3A0CD8 for <openpgp@ietfa.amsl.com>; Wed, 21 Oct 2020 05:36:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 (1024-bit key) header.d=ihtfp.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 f_nL9yXrJyfZ for <openpgp@ietfa.amsl.com>; Wed, 21 Oct 2020 05:36:29 -0700 (PDT)
Received: from mail2.ihtfp.org (MAIL2.IHTFP.ORG [204.107.200.7]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F1CA73A0CD6 for <openpgp@ietf.org>; Wed, 21 Oct 2020 05:36:28 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 3EC2EE203F; Wed, 21 Oct 2020 08:36:27 -0400 (EDT)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 10423-01; Wed, 21 Oct 2020 08:36:25 -0400 (EDT)
Received: by mail2.ihtfp.org (Postfix, from userid 48) id A74ACE2045; Wed, 21 Oct 2020 08:36:25 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1603283785; bh=vm4bsQZPP5Q8+bfVucmLLZVnOmfDTNXJ/EO468u0sdE=; h=In-Reply-To:References:Date:Subject:From:To:Cc; b=IGRf5rQbPOmS3zRvp94wBaE+9Ww3ppEKGAJPS0H8FrX9nqjFgaiMI6TvWW6XSbJvF O9S5IHYIDt5tbL/IieWkt2ySJV2kNtv57yQ+melRbWfsfru4ecvAh5L9bRHlnvkMRO 7SdawywV63iuKzs/0YxfyJ1QOh8Sx5BlYwQLNJCg=
Received: from 192.168.248.158 (SquirrelMail authenticated user warlord) by mail2.ihtfp.org with HTTP; Wed, 21 Oct 2020 08:36:25 -0400
Message-ID: <58d51c58b524765c9952a3502f70dbcb.squirrel@mail2.ihtfp.org>
In-Reply-To: <a97e03af-364b-d4ce-fab0-9b6fa184d1a0@cs.tcd.ie>
References: <20201020215929.GR39170@kduck.mit.edu> <260d532c97cfcf8285f68fa6080c809317646a76.camel@16bits.net> <73b6595fad9bd10d2772a5c6842adabc.squirrel@mail2.ihtfp.org> <0FC168CB-4394-4924-82B9-B40A15969FF0@ribose.com> <8e5fca53-4a3c-bb64-ef87-3a0f9d4bc11b@cs.tcd.ie> <c95cec411011a61ff99ea35d5eaa40b5.squirrel@mail2.ihtfp.org> <a97e03af-364b-d4ce-fab0-9b6fa184d1a0@cs.tcd.ie>
Date: Wed, 21 Oct 2020 08:36:25 -0400
From: "Derek Atkins" <derek@ihtfp.com>
To: "Stephen Farrell" <stephen.farrell@cs.tcd.ie>
Cc: "Derek Atkins" <derek@ihtfp.com>, "Ronald Tse" <tse=40ribose.com@dmarc.ietf.org>, "openpgp@ietf.org" <openpgp@ietf.org>, "Benjamin Kaduk" <kaduk@mit.edu>
User-Agent: SquirrelMail/1.4.22-14.fc20
MIME-Version: 1.0
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/kyChTUYf0ZGf5O7n8K09F34WjHg>
Subject: Re: [openpgp] heads-up: re-chartering the OPENPGP WG
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 12:36:31 -0000

HI,

On Wed, October 21, 2020 8:33 am, Stephen Farrell wrote:
>
> Hiya,
>
> On 21/10/2020 13:01, Derek Atkins wrote:
>> So... IF I read this right, the plan is to start from RFC4880 and then
>> re-hash all the discussions we've had in the past decade+ to
>> re-introduce
>> changes to it?
>
> Urgh, no:-)

Good to hear.

>>
>> Or is the plan to start from the current rfc4880bis draft and work from
>> there to get it across the finish line?
>
> More or less.
>
> There will of course need to be a discussion about WG
> adoption of a draft but IIUC the goal will be for that to
> basically start from the current bis draft. What I don't
> know is whether or not there are parts in the current draft
> that a WG would rather not have and how that might affect
> people's opinions on adoption. I do believe a WG would want
> almost all of the bis text so starting from testing that
> (via a WG adoption discussion) seems like a plan to me.
> But again, that's getting a bit ahead of ourselves.
>
>> The current wording in the charter leads me to the former and not the
>> latter process.  Can you please confirm?
>
> Feel free to suggest some words pointing out it's the
> latter. (Or I can try later on, if that's better.)

Maybe the simplest way would be to change:

The Working Group will perform the following work:

- Revise RFC4880

to read:

- Revise RFC4880.  The intent is to start from the current rfc4880bis draft.


> Cheers,
> S.

-derek

>
>>
>> Thanks,
>>
>> -derek
>>
>> On Tue, October 20, 2020 9:20 pm, Stephen Farrell wrote:
>>>
>>> Hiya,
>>>
>>> The draft charter is at [1].
>>>
>>> Comments and discussion of that are more than welcome.
>>>
>>> From my POV, I'm happy to try help out to get a fairly
>>> minimal bit of progress progressed (as an RFC) - if we can
>>> usefully succeed in that (which isn't a given).
>>>
>>> FWIW, I do think starting with a very modest goal is
>>> likely a good plan for now. A bit of success (in terms
>>> of an RFC that is implemented, deployed and more up to
>>> date) is already not that easy, but success does
>>> breed success so if we got that done, then extending
>>> the charter based on success is not so hard.
>>>
>>> Cheers,
>>> S.
>>>
>>> [1] https://datatracker.ietf.org/doc/charter-ietf-openpgp/
>>>
>>> On 21/10/2020 01:59, Ronald Tse wrote:
>>>> I second Derek’s message here, haven’t seen a proposed charter at the
>>>> mailing list?
>>>>
>>>> _____________________________________
>>>>
>>>> Ronald Tse
>>>> Ribose Inc.
>>>>
>>>>> On Oct 21, 2020, at 8:55 AM, Derek Atkins <derek@ihtfp.com> wrote:
>>>>>
>>>>> 
>>>>>> On Tue, October 20, 2020 8:44 pm, Ángel wrote:
>>>>>>> On 2020-10-20 at 14:59 -0700, Benjamin Kaduk wrote:
>>>>>>> Please welcome the chairs for the now-in-proposed-state WG,
>>>>>>> Daniel Kahn Gillmor and Stephen Farrell!
>>>>>>>
>>>>>>> Looking forward to many successful RFCs :)
>>>>>>>
>>>>>>> -Ben
>>>>>>
>>>>>> Nice to hear! Although I would be happy to see just a few for now
>>>>>> :-)
>>>>>
>>>>> This is complete news to me; I have seen no proposed charter sent to
>>>>> this
>>>>> mailing list.
>>>>> Did I miss it?
>>>>>
>>>>> -derek
>>>>> --
>>>>>       Derek Atkins                 617-623-3745
>>>>>       derek@ihtfp.com             www.ihtfp.com
>>>>>       Computer and Internet Security Consultant
>>>>>
>>>>> _______________________________________________
>>>>> openpgp mailing list
>>>>> openpgp@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/openpgp
>>>> _______________________________________________
>>>> openpgp mailing list
>>>> openpgp@ietf.org
>>>> https://www.ietf.org/mailman/listinfo/openpgp
>>>>
>>> _______________________________________________
>>> openpgp mailing list
>>> openpgp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/openpgp
>>>
>>
>>
>


-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant