webkey service: caching/robot policy statements?

[Bernhard Reiter]

Am Dienstag 09 Juli 2019 05:08:57 schrieb Phil Pennock via Gnupg-devel:
> Does this seem a reasonable location for a "caching keyserver" to check
> for directives on policy controls, too?

What is a "caching keyserver" in this context?
What purpose would it serve?

A WKD request would only be served by the TLS certificate of the 
webserver of the original domain. This cannot be cached, otherwise the check 
would not be working.

Also, a third party server would not know the email address to ask for.
(Unless given by some application.) So why would this application prefer the 
third party server when it could ask the real WKD server?

Best Regards,
Bernhard

-- 
www.intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: This is a digitally signed message part.
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20190709/c3ae7bf2/attachment.sig>