not sending confirmation email

Werner Koch wk at
Tue Sep 17 20:04:38 CEST 2019

On Tue, 17 Sep 2019 17:35, look at said:

> convention or otherwise.  The spec is factually wrong and misleading for
> implementors in this aspect, and should be updated to reflect reality.

The specs are not wrong if you would read them:

| the name and email address of the key holder.  *By convention*, it
| includes an RFC 2822 [](#RFC2822) mail name-addr, but there are no

 Convention \Con*ven"tion\, n. [L. conventio: cf. F. convention.

     5. An agreement or contract less formal than, or preliminary
        to, a treaty; an informal compact, as between commanders
        of armies in respect to suspension of hostilities, or
        between states; also, a formal agreement between
        governments or sovereign powers; as, a postal convention
        between two governments.
        [1913 Webster]

In German "Sitte" oder "Brauch".  In contrast:

 specification \spec`i*fi*ca"tion\

     4. A detailed listing or description of the required
        properties of some object proposed to be built or bought;
        -- usually used in the plural; as, the building
        specifications require that it withstand an earthquake of
        magnitude 8; the program specifications require an option
        to change the menus.

Instead of finalizing RFC4880bis, which has all its goals already
implemented, some members of the WG kept on raising new items for what
the WG has never been chartered.  The outcome of all that mess is that
implementers will simply ignore the fact that there won't be an RFC and
implement the current I-D.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 227 bytes
Desc: not available
URL: <>

More information about the Gnupg-users mailing list