Gary E. Miller via devel writes: >> Again, it supports it exactly the same way as the pool is currently >> working with DNS: You want another server, you ask another time. > > Exactly why it is broken. No crypto. Unless you mean having an NTS-KE > server manage a pool. in chich case there is zero support for that > in any proposal. So will take years and be a new and different animal.
Anything to do with NTS is managed through and by the NTS-KE. So if you set one up for a pool, guess what: it'll manage those associations. >> The open question was if any of this can be made more efficient now >> that we ask an NTS-KE instead of a DNS server. > > That changes the Proposed RFC. Out of scope. No it doesn't. Regards, Achim. -- +<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables _______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
