[Chirp] getting started chirpily

[Stephen Farrell <[e-mail]>]

Hiya,

So we currently have 17 subscribers to this list, which
isn't huge, but maybe that'll be good too:-)

How's about we get started anyway - I think the first
thing I'd be interested in knowing is what folks would
do work on in this space. Once we have a better idea
of that we can chat about how to go forward. So,
what'd you suggest? Please reply to this or start a
new thread on whatever topic you think may be a good
one for this list...

In case it helps get the juices flowing, one resilience
topic where I could see possible improvement relates
to PKI and, specifically, to letsencrypt. I think LE
have done a fantastic job with helping https deployment
(and esp cert renewals) over the last 4ish years, but
it'd likely be a pretty bad day for the Internet if they
had to go away for some reason. (There are commercial CAs
as alternatives, but it'd still be quite a day if LE had
to cease operations.)

I don't have any specific protocol suggestions to make
related to that at the moment (though maybe one could look
at acme and client implementations to see if they'd fall
over during a transition period) so for now am mostly
wondering if there are other fine services (like LE) that
use IETF developed protocols, on which we're fairly
dependent, and where the impact of our protocol designs
in the face of external changes might not be obvious.

Cheers,
S.

PS: I'm not making a claim that the LE issue above is
the most important or something I think we must examine,
it's just to try help get people thinking. (And if we
really were gonna consider that topic, the first thing
to do might be to chat with acme/LE folks, which I've
not done:-)