On Mon, 2009-02-02 at 19:21 -0500, David Shaw wrote: > No. You should have a document specifying what the port actually is > and the protocol that is used on the port before you claim it. There > is a spec for 11371. You need a spec for 11370.
I was aware of that process :-) > Also, isn't the port changeable on a per-peer basis in SKS? If so, > there is no point in registering the port at all, as setting up a new > peer is a manual operation. Well but this is also the case with the 11371 port, and basically with most other protocols, too, isn't it? > A SKS instance doesn't need to know a > well-known port to become a peer. Well it was just an idea, when I saw that probably most keyservers sticked with the default (11370) and this was still unassigned. I didn't intend to step on someones feet :) btw: I was not about to register a port number in the well-known range ;) Best wishes, -- Christoph Anton Mitterer Ludwig-Maximilians-Universität München christoph.anton.mitte...@physik.uni-muenchen.de m...@christoph.anton.mitterer.name
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
