Re: WG last call: Coex draft -- proposed "Changes since RFC 2576" section

On Fri, 27 Dec 2002, C. M. Heard wrote:
> c.)  The document change log does not document the changes since
> RFC 2576, such as the one described in REVISION clause above.

After reviewing all the substantive changes in the coex draft
draft-ietf-snmpv3-coex-v2-02.txt relative to RFC 2576 I found
that I agreed with all but one, which was discussed in a previous
message.  Below is a proposed update to the "Change Log" section
that includes all the changes in the current draft except the
controversial one, plus a few routine editorial fixes (e.g., split
references) that I think we can safely assume will appear in the
next draft.  It does not, however, include my recently-posted
suggestions for changes to Section 2.

The authors should, of course, list all of the MIB module changes
mentioned below in the MODULE-IDENTITY invocation's most recent
REVISION clause (note that two of them were NOT included in my
previous proposals for fixes to the MIB module).  Having done
that, they may then prefer just to have a pointer to that clause
instead of listing them individually in the Change Log section.

//cmh

*** draft-ietf-snmpv3-coex-v2-02.txt	Mon Dec 16 06:51:58 2002
--- draft-ietf-snmpv3-coex-v2-xx.txt	Mon Jan  6 13:46:56 2003
***************
*** 3061,3063 ****
  
!    B.  Changes From RFC1908
  
--- 3061,3121 ----
  
!    B.  Change Log
  
+    B.1.  Changes since RFC 2576
+ 
+        -  Changed "SHOULD" to "MUST" in item (13) of the first list in
+           Section 2.1.1 to clarify that collecting related objects into
+           groups is required when translating a MIB module from SMIv1 to
+           SMIv2.
+ 
+        -  Changed "SHOULD" to "MUST" in items (1) and (2) of Section 2.3
+           since those updates are indeed required when translating a
+           capabilities statement from the language defined by RFC 1303
+           into SMIv2.
+ 
+        -  In the second bullet of the last part of Section 3 listing the
+           SNMPv2 notification parameters, clarified that the snmpTrapOID
+           parameter refers to the value portion (not the name portion)
+           of the second variable-binding, and changed the wording in the
+           text under bullet (1) of Section 3.2 from "the snmpTrapOID" to
+           "the snmpTrapOID value" to emphasize this point.
+ 
+        -  In Section 4.2 clarified that the 'Upstream Version' refers to
+           the version used between the command generator or notification
+           receiver and the proxy, and the 'Downstream Version' refers to
+           the version used between the proxy and the command responder
+           or notification originator.  RFC 2576 neglected to mention the
+           notification receiver and notification originator.
+ 
+        -  In Section 4.2.1 clarified that the error-index field must be
+           set to zero in a translated GetResponse-PDU with an error-
+           status of 'tooBig'.
+ 
+        -  In Section 5.2.1 clarified that the scopedPDU's
+           contextSnmpEngineID and contextName values come
+           from the selected entry in the snmpCommunityTable.
+ 
+        -  Added Section 5.2.4 on Proxy Forwarding Of Requests.
+ 
+        -  Updated the LAST-UPDATED, CONTACT-INFO, and REVISION clauses
+           and added a copyright notice to the DESCRIPTION clause of the
+           MIB module's MODULE-IDENTITY invocation.
+ 
+        -  Updated the description of snmpCommunityTransportTag to make
+           it consistent with the rest of the document.
+ 
+        -  Updated the description of `snmpTargetAddrMMS' to clarify that
+           a value of 0 means that the maximum message size is unknown.
+ 
+        -  Changed the name of 'snmpCommunityGroup' to
+           'snmpCommunityTableGroup' in order to resolve
+           a name conflict with the SNMPv2-MIB.
+ 
+        -  Divided references into Normative References and Informative
+           Reference and updated them to point to current documents.
+ 
+        -  Inserted current year into all copyright notices.
+ 
+        -  Corrected various typographical and grammatical errors.
+ 
+    B.2.  Changes between RFC 1908 and RFC 2576