Murray Kucherawy has entered the following ballot position for draft-ietf-alto-path-vector-19: 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/blog/handling-iesg-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-alto-path-vector/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Section 6.2.1 should be at least a sentence, perhaps: The Entity Domain Type is "ane". I think Section 7.2.1 would be better expressed as: The media type of the multipart Filtered Cost Map resource is "multipart/related" and the required "type" parameter MUST have a value of "application/alto-costmap+json". By constraining the type to be a specific string, you're removing the flexibility of a MIME parser to allow intervening whitespace, line wrapping, etc. Why are the RECOMMENDEDs in 7.2.6 and 7.3.6 not REQUIRED? Is there ever a reason to send them out-of-order? _______________________________________________ alto mailing list [email protected] https://www.ietf.org/mailman/listinfo/alto
