It appears that Stephane Bortzmeyer <bortzme...@nic.fr> said: >On Wed, Apr 14, 2021 at 11:01:42AM +0200, > Stephane Bortzmeyer <bortzme...@nic.fr> wrote > a message of 10 lines which said: > >> The Name:Wreck compression pointer issue
I skimmed his very wordy paper and saw that all of the bugs he reported that affect software I use were fixed a year ago. We find that IoT stuff is crud. This is not news and I don't think it's something that RFCs either caused or could fix. On the other hand, all of the sloppy coding people use to handle compressed names is embarassing. >Also ><https://www.scmagazine.com/home/security-news/vulnerabilities/namewreck-is-the-latest-collision-between-tcp-ip-and-the-standards-process/> >talks about what IETF should do. (The article contains several errors >about the RFC process.) > >> “I mean I don’t want to be the one telling the [Internet Engineering >> Task Force] how to do their work. Things have worked for more than >> 40 years on the internet because of the RFC systems,” he said. “But >> indeed, I do believe that it’s time that we think of an >> alternative.” > _______________________________________________ DNSOP mailing list DNSOP@ietf.org https://www.ietf.org/mailman/listinfo/dnsop
