Robert Wilton has entered the following ballot position for draft-ietf-nvo3-encap-11: Yes
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-nvo3-encap/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- I think that some questions have been raised as to whether this sort of draft about a design team's reasoning and discussions should be published as an RFC. To me, I read this document as the supporting justification as to the path taken vs the paths not taken, and I suspect that this reasoning could potentially be useful for other engineers considering similar issues. Hence, writing it down and publishing it somewhere accessible is potentially useful, and as Informational RFC seems like a reasonable place, and better than, e.g., a wiki page that would likely suffer from bit rot. Thanks for spending the time to write it and run it through the process. Regards, Rob _______________________________________________ nvo3 mailing list nvo3@ietf.org https://www.ietf.org/mailman/listinfo/nvo3
