Re: [openpgp] Using Git for RFC 4880bis

Daniel Kahn Gillmor <> Mon, 27 June 2016 17:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7C32912D0ED for <>; Mon, 27 Jun 2016 10:53:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id lgeOqWisro8o for <>; Mon, 27 Jun 2016 10:53:13 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 19F4312D17B for <>; Mon, 27 Jun 2016 10:53:09 -0700 (PDT)
Received: from (unknown []) by (Postfix) with ESMTPSA id A3B06F98B; Mon, 27 Jun 2016 13:53:07 -0400 (EDT)
Received: by (Postfix, from userid 1000) id 6A9F1200CC; Mon, 27 Jun 2016 13:53:07 -0400 (EDT)
From: Daniel Kahn Gillmor <>
To: Tom Ritter <>
In-Reply-To: <>
References: <> <>
User-Agent: Notmuch/0.22+69~gd812194 ( Emacs/24.5.1 (x86_64-pc-linux-gnu)
Date: Mon, 27 Jun 2016 13:53:07 -0400
Message-ID: <>
MIME-Version: 1.0
Content-Type: text/plain
Archived-At: <>
Cc: IETF OpenPGP <>
Subject: Re: [openpgp] Using Git for RFC 4880bis
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 27 Jun 2016 17:53:14 -0000

Hi Tom--

On Sun 2016-06-26 22:36:03 -0400, Tom Ritter wrote:
> Can we use the Issues tracker (either in Gitlab or the IETF tools, but
> not both) to note what changes are outstanding (but encourage people
> to send the text proposals to the list)?

Yes.  I think we should use the gitlab issues tracker, not the IETF
tools, for the sake of simplicity.  I'll see what i can do about
adjusting the IETF tools issue tracker to indicate that the gitlab
issues tracker is the place to use.

As you say, actual discussion should take place on this list.

> It would be helpful to have some sort of list of outstanding changes
> we have rough consensus to make but lack text proposals.  For example,
> using a real authenticated mode instead of the MDC is a definite.  I'm
> not sure if a streaming-friendly mode there is consensus for, but it
> could be noted as 'under discussion' or something.

agreed.  If folks want to document specific outstanding changes please
feel free to open them as gitlab issues.  If the chairs judge there is
no consensus for a specific outstanding change after discussion, we
might go ahead and close the corresponding issue.