On Wed, Aug 26, 2020 at 2:51 PM Grant Taylor <gtay...@gentoo.tnetconsulting.net> wrote: > > On 8/21/20 5:58 PM, Rich Freeman wrote: > > It is what just about every other modern application in existence uses. > > VoIP does not.
Yes, but VoIP isn't just implementing a simple data-exchange API. It is a streaming protocol. > No RDBMSs that I'm aware of use it as their primary protocol. (Some may > be able to use HTTP(S) as an alternative.) These pre-date webservices in general. They aren't modern. > Outlook to Exchange does (did?) not use it. Again, not modern. > I'm not aware of any self hosted enterprise grade remote desktop > solution that uses HTTP(S) as it's native transport. Also streaming. > > DNSSEC is: > > > > 1. Still poorly supported even where it makes sense. > > Yet another example of ignorance and / or laziness. > > I have found DNSSEC to be relatively easy to implement, and trivial to > enable on my recursive resolvers. > > The ignorance portion is relatively easy to resolve if people want to. > I highly recommend DNSSEC Mastery by Michael W. Lucas. That $20 (?) > book and moderate amounts of motivation is all anybody that wants to > implement DNSSEC /needs/. Well, maybe check back when you get everybody who sends email to read that book. You can start with my mother. -- Rich
