| 1 |
On Wed, Aug 26, 2020 at 2:51 PM Grant Taylor |
| 2 |
<gtaylor@×××××××××××××××××××××.net> wrote: |
| 3 |
> |
| 4 |
> On 8/21/20 5:58 PM, Rich Freeman wrote: |
| 5 |
> > It is what just about every other modern application in existence uses. |
| 6 |
> |
| 7 |
> VoIP does not. |
| 8 |
|
| 9 |
Yes, but VoIP isn't just implementing a simple data-exchange API. It |
| 10 |
is a streaming protocol. |
| 11 |
|
| 12 |
> No RDBMSs that I'm aware of use it as their primary protocol. (Some may |
| 13 |
> be able to use HTTP(S) as an alternative.) |
| 14 |
|
| 15 |
These pre-date webservices in general. They aren't modern. |
| 16 |
|
| 17 |
> Outlook to Exchange does (did?) not use it. |
| 18 |
|
| 19 |
Again, not modern. |
| 20 |
|
| 21 |
> I'm not aware of any self hosted enterprise grade remote desktop |
| 22 |
> solution that uses HTTP(S) as it's native transport. |
| 23 |
|
| 24 |
Also streaming. |
| 25 |
|
| 26 |
> > DNSSEC is: |
| 27 |
> > |
| 28 |
> > 1. Still poorly supported even where it makes sense. |
| 29 |
> |
| 30 |
> Yet another example of ignorance and / or laziness. |
| 31 |
> |
| 32 |
> I have found DNSSEC to be relatively easy to implement, and trivial to |
| 33 |
> enable on my recursive resolvers. |
| 34 |
> |
| 35 |
> The ignorance portion is relatively easy to resolve if people want to. |
| 36 |
> I highly recommend DNSSEC Mastery by Michael W. Lucas. That $20 (?) |
| 37 |
> book and moderate amounts of motivation is all anybody that wants to |
| 38 |
> implement DNSSEC /needs/. |
| 39 |
|
| 40 |
Well, maybe check back when you get everybody who sends email to read |
| 41 |
that book. You can start with my mother. |
| 42 |
|
| 43 |
-- |
| 44 |
Rich |
Archives