Found 1 record.
Status: Rejected (1) RFC 5706, "Guidelines for Considering Operations and Management of New Protocols and Protocol Extensions", November 2009Source of RFC: opsawg (ops)
Errata ID: 8315
Status: Rejected
Type: Technical
Publication Format(s) : TEXT
Reported By: Donald Eastlake
Date Reported: 2025-02-26
Rejected by: Mahesh Jethanandani
Date Rejected: 2025-02-28
Section 3.6.1 says:
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.
It should say:
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.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4