The following errata report has been rejected for RFC5706, "Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions".
-------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid8315 -------------------------------------- Status: Rejected Type: Technical Reported by: Donald Eastlake <d3e...@gmail.com> Date Reported: 2025-02-26 Rejected by: Mahesh Jethanandani (IESG) Section: 3.6.1 Original Text ------------- The protocol document should make clear the limitations implicit within the protocol and the behavior when limits are exceeded. This should be considered in a data-modeling-independent manner -- what makes managed-protocol sense, not what makes management-protocol- sense. Corrected Text -------------- The protocol document should make clear the limitations implicit within the protocol and the behavior when limits are exceeded. This should be considered in a data-modeling-independent manner -- what makes managed-protocol sense, not what makes data model sense. Notes ----- I am not sure what correct wording would be. The existing wording is self contradictory. The above "corrected" text is just a guess. --VERIFIER NOTES-- The play on words can be confusing, but there is nothing wrong with it as written. In addition, the suggested wording does not help clarify it any better. -------------------------------------- RFC5706 (draft-ietf-opsawg-operations-and-management-09) -------------------------------------- Title : Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions Publication Date : November 2009 Author(s) : D. Harrington Category : INFORMATIONAL Source : Operations and Management Area Working Group Stream : IETF Verifying Party : IESG _______________________________________________ OPSAWG mailing list -- opsawg@ietf.org To unsubscribe send an email to opsawg-le...@ietf.org
