Gorry Fairhurst has entered the following ballot position for draft-ietf-dmm-tn-aware-mobility-26: 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-dmm-tn-aware-mobility/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you for writing this document. I note that "IP transport" in this context means transport of IP over UDP over IP, although I see only one transport-related concern;-): ## The way in which the UDP source port number is used appears to prevent the use of source port randomisation, a useful technique to mitigate vulnerability to off-path attack. This is expected to be acceptable use. The concern maybe was intended to be included within "To avoid spoofing..", although I'd encourage this to be explicitly stated to note this as a security consideration (perhaps cross-referencing Sect 5.1.1. of 5.1.1) and to link this to mitigations to such attack, where I see IPsec and ACLs suggested as viable possible approaches. ## I do wonder if RFC 9543 is normative background (f not, what provides the normative basis for the technologies?). _______________________________________________ dmm mailing list -- [email protected] To unsubscribe send an email to [email protected]
