Re: [Sks-devel] sks pool membership registration

[Phil Pennock]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On 2013-06-26 at 22:24 +0200, Kristian Fiskerstrand wrote:
> On 06/26/2013 10:15 PM, Daniel Kahn Gillmor wrote:
> > i'd change "monitoruid" to just "notify" (no arguments needed, this
> > is a boolean) and have any notifications get sent to the
> > most-recent valid primary User ID of the associated server_contact.
> > if a server operator can't receive mail at their primary User ID,
> > they have other problems :) I don't think introducing "the
> > nth-oldest" is a useful complexity/feature tradeoff.
> 
> Indeed, when I've been pondering this it has always been the intention
> to the the primary / first UID.

That's two distinct proposals.

Newest fails when I add a uid for a specific open-source project email
address and route that mail away from my normal inbox.

Oldest fails unless revocation is handled, since folks move around but
keep their key and the trust web it has accrued, asking existing signers
to re-sign.

I'm not remembering anything in the spec about a "primary" UID; last I
recall, all UIDs are equal sub-packets, right?  Or is it time for me to
go re-read the OpenPGP specs?

- -Phil
-----BEGIN PGP SIGNATURE-----

iEUEAREDAAYFAlHLU50ACgkQQDBDFTkDY3+ABgCcDLvkZCnRXb+0KXIxp5JqaTDh
jPEAmKDRE7yA9sICphcU/la3Z1jKXJo=
=uXql
-----END PGP SIGNATURE-----