Martin Duke has entered the following ballot position for draft-ietf-opsawg-mud-iot-dns-considerations-12: No Objection
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud-iot-dns-considerations/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- (4.1) There's an editorial error here. "An authoritative server might be tempted to provide an IP address literal inside the protocol: there are two arguments (anti-patterns) for doing this." I'm expecting two reasons someone might use an IP literal. "The first is that it eliminates problems with firmware updates that might be caused by lack of DNS..." Yep, that tracks. "The second reason to avoid a IP address literal in the URL is when an inhouse content-distribution system is involved..." But this is making the opposite point! It appears that this section is actually presenting ONE (not two) reason to use IP literals, and then several reasons that's a bad idea. So say that! _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
