3 ms·

I leave it to other visitors to assess whether making disparaging statements about someone's emotional state, career, and competence, qualifies as "personal", a

I leave it to other visitors to assess whether making disparaging statements about someone's emotional state, career, and competence, qualifies as "personal", and I have not described my own feelings, except my disappointment with one facet of the development of HTTP. I'd have expected someone claiming to be in the loop regarding DNS developments to bring up the more substantial topic of the SVCB and HTTPS records, which are the topic of an ongoing draft¹, and which may go some way towards ameliorating the issues. But no; apparently, low-grade sledging it is. [1] https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https/10/ https://datatracker.ietf.org/doc/draft-ietf-dnsop-svcb-https..., for the curious.

ghoulish45 4y ago
You don’t understand DNS. I don’t understand how to make sushi. Acknowledging those things is not a personal attack. Your major failure here is assuming that observations of your emotional state and your career experiences, and how those pertain to your mastery of the domain you’re speaking to (wildly incorrectly), are observations about you. Given that you also assumed someone who was banned here sought out an opportunity to shut you down, again, I have to return to an unhealthy ego driving your interactions. You are nobody. I am nobody. You suck at DNS. That’s fine. You can get better. I have no idea who you are and I’ll forget you when I close this tab. It’s really important that you understand that, because your comment style leads me to believe that you don’t. Teaching DNS about application protocols is a mistake every time it happens. That’s why I didn’t bring them up. Nothing is missing in DNS. It’s been fine since the early 1980s. The Web has gotten along just fine without special RR types thus far. Personally, I want HTTP as far from DNS as possible, but that’s a side discussion having to do with my long term outlook on the Internet. The people who think DNS is broken for $L7 use case generally don’t understand DNS the way it’s meant to be understood, and this comment chain is holding that rule fast. The gethostbyname, receive content approach was elected for HTTP because it was already common practice for pretty much every protocol in existence by the time TimBL and friends wrote httpd. There was nothing wrong with it at the time and there remains nothing wrong with it today. Unless you have an argument for why HTTP is special, which you don’t, because it isn’t (not even HTTP/3 running atop UDP demands specialness).

ghoulish45 4y ago

You don’t understand DNS. I don’t understand how to make sushi. Acknowledging those things is not a personal attack. Your major failure here is assuming that observations of your emotional state and your career experiences, and how those pertain to your mastery of the domain you’re speaking to (wildly incorrectly), are observations about you. Given that you also assumed someone who was banned here sought out an opportunity to shut you down, again, I have to return to an unhealthy ego driving your interactions. You are nobody. I am nobody. You suck at DNS. That’s fine. You can get better. I have no idea who you are and I’ll forget you when I close this tab. It’s really important that you understand that, because your comment style leads me to believe that you don’t. Teaching DNS about application protocols is a mistake every time it happens. That’s why I didn’t bring them up. Nothing is missing in DNS. It’s been fine since the early 1980s. The Web has gotten along just fine without special RR types thus far. Personally, I want HTTP as far from DNS as possible, but that’s a side discussion having to do with my long term outlook on the Internet. The people who think DNS is broken for $L7 use case generally don’t understand DNS the way it’s meant to be understood, and this comment chain is holding that rule fast. The gethostbyname, receive content approach was elected for HTTP because it was already common practice for pretty much every protocol in existence by the time TimBL and friends wrote httpd. There was nothing wrong with it at the time and there remains nothing wrong with it today. Unless you have an argument for why HTTP is special, which you don’t, because it isn’t (not even HTTP/3 running atop UDP demands specialness).