Erik Kline has entered the following ballot position for draft-ietf-rtgwg-net2cloud-problem-statement-41: 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-rtgwg-net2cloud-problem-statement/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- # Internet AD comments for draft-ietf-rtgwg-net2cloud-problem-statement-41 CC @ekline * comment syntax: - https://github.com/mnot/ietf-comments/blob/main/format.md * "Handling Ballot Positions": - https://ietf.org/about/groups/iesg/statements/handling-ballot-positions/ ## Comments ### S2 * Based on a quick search for the various keywords, and the fact that this is an Informational doc, I think you delete the keywords text and the associated bibliographic entries. ### S3.* * Should there be some text about managing end-to-end connectivity when NAT is not being used? For IPv6 in particular, it can be surprising to some that nodes might be reachable. Broadly, the issue of managing firewalls and permitted/denied communications might be an area of concern on its own. Developing proper text, though, probably requires going back to the working group and/or through IETF LC (which I assume folks don't want to do). ### S3.7 * Any solution that involves attaching metadata must also specify how that metadata can be authenticated/validated. I would suggest just saying that there's a security requirement for this for any solution in this area. _______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org
