Martin Duke has entered the following ballot position for draft-ietf-opsawg-finding-geofeeds-08: 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/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/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- "Ideally, RPSL would be augmented to define a new RPSL geofeed: attribute in the inetnum: class. Until such time, this document defines the syntax of a Geofeed remarks: attribute which contains an HTTPS URL of a geofeed file." If the ideal solution is to produce a standards track document that creates a new RPSL attribute, I don't understand why the Working Group didn't simply do that, instead of messing with the remarks and then coming up with a transition plan for moving from this design to the future one. _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
