The following errata report has been submitted 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 -------------------------------------- Type: Technical Reported by: Donald Eastlake <d3e...@gmail.com> 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. Instructions: ------------- This erratum is currently posted as "Reported". (If it is spam, it will be removed shortly by the RFC Production Center.) Please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party will log in to change the status and edit the report, if necessary. -------------------------------------- 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
