Murray Kucherawy has entered the following ballot position for draft-ietf-opsawg-finding-geofeeds-12: Discuss
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/iesg/statement/discuss-criteria.html for more information about DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-opsawg-finding-geofeeds/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I may have missed something, but why does Section 5 advocate for use of HTTPS to fetch geofeed files in the second paragraph, and then FTP in the seventh? Which is right? Or perhaps both are right, but there's some context being assumed here that I don't have. In any case, please clarify. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Nice job on the shepherd writeup. In Section 5, "https" should be "HTTPS" since you're describing a protocol and not a URI scheme (or if you meant to do the latter, please say so). _______________________________________________ OPSAWG mailing list OPSAWG@ietf.org https://www.ietf.org/mailman/listinfo/opsawg
