Minor fixes to documents

[Keith McCloghrie <[e-mail]>]

As I mentioned at the NM area open meeting earlier this week, I have
compiled a list of minor fixes/typos to the 19 March documents.  The
list is below.  As you will notice, many of them are in the SCM document.
This is due to implementation feedback from Andrew Pearson (SNMP
Research) who deserves our thanks.

Keith.
------------------

In draft-ietf-snmpv2-scm-ds-00.txt

1. Since the SMI prohibits the use of IMPLIED with variables which can have
zero-length, delete IMPLIED in:

     INDEX       { scmCapIndex, scmCapCtxLocalTime,
                  IMPLIED scmCapCtxLocalEntity }

2. Add DEFVAL clauses.

3. In the instance of userMaintCreate, the mLinger should be encoded as
four subidentifiers, and <mMMS> as 2 sub-identifiers.  Fix DESCRIPTION
of userMaintIndex (i.e., it's not BER-encoded.)  Add a size constraint
to userMaintIndex.

4. Make scmCapXxxXxxxView consistent with acXxxViewIndex, as follows:

            The identified MIB view is that                               |
            for which viewIndex has the same value as the instance of     |
            this object; if the value is zero or there are no active      |
            view subtrees for that value, then the identified MIB view    |
            is the empty set of view subtrees.                            |

5. When an scmCapTable entry pointed to by an scmUserTable entry is destroyed
or made notInService, the corresponding row(s) in the scmUserTable are also
destroyed or made notInService.
 
6. In SCM, to be consistent with BCM, change 

                     <localTime>   -> <clt> 
                     <localEntity> -> <cle> 

7. In SCM section 4a, remove "View" from list of context's attributes.

8. In SCM section 4.5, "Step 5: Agent Responds," the text doesn't mention
that only a single octet is returned if there was a problem.  It tells you
only that the pPad is not returned unless a privacy algorithm is used.

9. Change SCM 4.2 to say that if error occurs, skip to section 4.5.
In section 4.5, say that a Response is sent with the varbind's value
being either a one-byte non-zero result-code (and list the codes),
or N-bytes where the first byte is zero indicating success and the
remainder have the meaning currently listed in 4.5.  Also add a "genErr"
error code for unable to create session at this time.

10. Add to end of SCM section 3: 

   userMaintContext is local to any SNMPv2 entity acting in an agent
   role, and has these characteristics:

     contextIdentity         0.1
     contextType             local  (to agent)

  Note that userMaintContext, and its associated pseudo-ACL and
  pseudo-view all have a StorageType of "readOnly" [4], in that they
  always exist and cannot be modified.  Further, userMaintContext MUST
  NOT be accessible to entities outside of an SNMPv2 entity itself.
  Consequently, even though it is conceptually represented in the LPD,
  userMaintContext is not visible through the SNMPv2 Party MIB [4],
  neither are the pseudo-ACL and pseudo-view that it uses.

  It should be noted that the use of a fixed context-identity
  (userMaintContext) is contrary to the architectural principles of the
  SNMPv2 administrative framework: in SNMPv2, management information is
  always uniquely identified by a combination of context local-entity,
  context local-time, object type, and object instance.  However, in the
  interests of both simplicity and the reuse of infrastructure,
  maintenance functions are provided "outside" of the administrative
  infrastructure available to applications which make use of an SNMPv2
  entity.  It must be emphasized that a management communication using
  userMaintContext belongs to a logically different protocol than SNMP,
  just as the ICMP is logically a different protocol from the IP.  Thus,
  use of userMaintContext, except for the purpose of performing
  user-based maintenance functions, is prohibited.

11. In SCM, add note on encoding to sect 4.1 pointing the user to the
DESCRIPTION clause of userMaintIndex.  Add example to DESCRIPTION clause
of userMaintIndex.

12. Change SCM and BCM to call MD5 using RFC 1321's calls,
 

In draft-ietf-snmpv2-party-ds-01.txt

1. In snmpV2-party.txt, for both partyAuthChange and partyPrivChange,
it says:

              keyIntermediate = md5(keyold XOR randomComponent)       +
              keynew = deltaComponent XOR keyIntermediate             +


2. Add to partyAuthPrivate and partyPrivPrivate:

   if transmitted value is shorter than old key, validate that the
   transmitted value is of sufficient length for the new key, and if so,
   truncate the old value prior to XOR.
the first XOR should be concatenate ("||")

In draft-ietf-snmpv2-smi-ds-01.txt

1. In the SMI document, the ApplicationSyntax CHOICE can not have both
Gauge32 and Unsigned32 because they have identical tags. i.e.,

    1. Remove
                gauge-value
                    Gauge32,
    2. Change
                unsigned-integer-value
       to
                unsigned-integer-value  -- includes Gauge32

In draft-ietf-snmpv2-mib-ds-01.txt

1. Add sysORUpTime to systemGroup in snmpV2-mib.txt.

In draft-ietf-snmpv2-conf-ds-01.txt

1. Change all snmpORxxx to sysORxxx 

In draft-ietf-snmpv2-tm-ds-01.txt

1. Fix formating of SnmpNBPAddress 

In draft-ietf-snmpv2-sec-ds-01.txt

1. Clarify that the secret-update maintenance function messages sent
using agentParty and mgrParty use the auth/priv protocols as per any
other messages using those parties.

In draft-ietf-snmpv2-coex-ds-01.txt

1. Append to section 2.2, step 5:

  (5)  The value of an invocation of the NOTIFICATION-TYPE macro is an
       OBJECT IDENTIFIER, not an INTEGER, and must be changed accordingly.
->     Specifically, if the value of the ENTERPRISE clause is not 'snmp'
->     then the value of the invocation is the value of the ENTERPRISE
->     clause extended with two sub-identifiers, the first of which has
->     the value 0, and the second has the value of the invocation of
->     the TRAP-TYPE.