Lars Eggert has entered the following ballot position for draft-ietf-hip-dex-24: Discuss
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 IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-hip-dex/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I realize I'm missing a lot of history and context here. So apologies if this was discussed in the past. But this document seems to be completely outside of the current HIP charter. Why has the WG worked on this, and why should this be published? I'll note that the only IETF document referencing draft-ietf-hip-dex is draft-ietf-hip-rfc4423, and the reference is an appendix that basically summarizes -dex and is not normative. So not publishing this document will not block any other work. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- ------------------------------------------------------------------------------- All comments below are very minor change suggestions that you may choose to incorporate in some way (or ignore), as you see fit. There is no need to let me know what you did with these suggestions. Section 5.2.6, paragraph 4, nit: - the Responder in I2 which echos it back to the Initiator in R2. + the Responder in I2 which echoes it back to the Initiator in R2. + + _______________________________________________ Hipsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/hipsec
