I have reviewed this document as part of the Operational directorate’s ongoing effort to review all IETF documents being processed by the IESG.  These comments were written with the intent of improving the operational aspects of the IETF drafts. Comments that are not addressed in last call may be included in AD reviews during the IESG review.  Document editors and WG chairs should treat these comments just like any other last call comments. Document reviewed:  draft-ietf-i2rs-protocol-security-requirements-06 Summary:  The abstract of the document says “ This presents security-related requirements for the I2RS protocol for mutual authentication, transport protocols, data transfer and transactions” . This document is on a informational track. The document defines security requirements and as such does not discuss how the requirements are met. Because the document is about requirements and does not define how the requirements should/are to be met, there are no management or operational considerations that need to be discussed about the document.  A run of idnits reveals a few warnings, which will probably be fixed as the document progresses towards a RFC.   ----------------------------------------------------------------------------   == Missing Reference: 'I7498-2' is mentioned on line 166, but not defined   == Outdated reference: draft-ietf-i2rs-architecture has been published as      RFC 7921   == Outdated reference: draft-ietf-i2rs-problem-statement has been published      as RFC 7920   == Outdated reference: A later version (-15) exists of      draft-ietf-i2rs-ephemeral-state-06   == Outdated reference: draft-ietf-i2rs-pub-sub-requirements has been      published as RFC 7923   == Outdated reference: draft-ietf-i2rs-traceability has been published as      RFC 7922 Thanks. Mahesh Jethanandani mjethanandani at gmail.com