Skip to main content

OpenPGP
draft-ietf-openpgp-crypto-refresh-13

Yes

Roman Danyliw

No Objection

Erik Kline
Francesca Palombini
Jim Guichard
(Andrew Alston)
(Robert Wilton)

Recuse


Note: This ballot was opened for revision 12 and is now closed.

Roman Danyliw
Yes
Erik Kline
No Objection
Francesca Palombini
No Objection
Jim Guichard
No Objection
John Scudder
No Objection
Comment (2023-12-13 for -12) Sent
Like Éric I am a fan of FCFS, but I don’t know how it would work out in this community and application.
Warren Kumari
No Objection
Comment (2023-12-13 for -12) Sent
Thank you for writing it, I found it an interesting read...

I'd also like to thank David Blacka for the DNSDIR Review (which raises a bunch of interesting questions that would not have occurred to me). I'd also like to thank DKG for his response -- https://mailarchive.ietf.org/arch/msg/last-call/YQcgcGpgeveTTCqH7Mt_1Jypt4w/ ), and the pointer to https://datatracker.ietf.org/doc/draft-dkg-openpgp-userid-conventions/ which will address some of these.
Zaheduzzaman Sarker
No Objection
Comment (2023-12-12 for -12) Sent
I have given a good read of this specification, as this is outside my core expertise, I kept my perspective only related to the transport protocols and from that point of view I have no objection.

One comment though, in section 6.2.2 it says -

   Note that some transport methods are sensitive to line length

I believe examples of such "transport methods" would be great here as transport methods are not mentioned or explained anywhere else in this specification.
Éric Vyncke
No Objection
Comment (2023-12-13 for -12) Sent
# Éric Vyncke, INT AD, comments for draft-ietf-openpgp-crypto-refresh-12

Thank you for the work put into this document. The content is above my expertise, hence I only did a quick review (else I would have balloted YES). The reviewed content is usually easy to read.

Please find below some non-blocking COMMENT points (but replies would be appreciated even if only for my own education).

I hope that this review helps to improve the document,

Regards,

-éric

# COMMENTS (non-blocking)

## The most concise shepherd's write-up

The justification for the intended status is just "PS"... not even expanded...

## Abstract

Isn't the 2nd paragraph (especially the first sentence) applicable to all standards track document? I.e., why not removing it ? (and I have noted the very rough consensus about this I-D based on the shepherd write-up).

## Section 3.5

Should another time epoch be specified ? Using the 1970 Unix epoch will cause a problem in 2038, a not too distant future. Why didn't this revised OpenPGP propose alternative epoch ?

## IANA registries

Should this I-D be an opportunity to reserve some registry values for a FCFS allocation ?
Paul Wouters
Recuse
Comment (2023-12-07 for -12) Not sent
I’m an author
Andrew Alston Former IESG member
No Objection
No Objection (for -12) Not sent

                            
Martin Duke Former IESG member
No Objection
No Objection (2023-12-12 for -12) Sent
In S2.4, the Base64 section talks about "seven-bit, printable text". Do you mean "six-bit"?
Robert Wilton Former IESG member
No Objection
No Objection (for -12) Not sent