RE: Updating the MIB security guidelines

["Wijnen, Bert (Bert)" <bwijnen@lucent.com>]

Suggested fixes/changes are now in my 'final draft'
Waiting for potential more comments after the holidays

Thanks,
Bert 

> -----Original Message-----
> From: C. M. Heard [mailto:heard@pobox.com]
> Sent: dinsdag 31 december 2002 20:07
> To: mibs@ops.ietf.org
> Subject: RE: Updating the MIB security guidelines
> 
> 
> One more minor fix for the last paragraph:
> 
> >>> Further, deployment of SNMP versions prior to SNMPv3 is NOT 
> >>> RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
> >>> enable cryptographic security.  It is a customer/operator
>                                          ^
> -------------------------------------- then
> 
> >>> responsibility to ensure that the SNMP entity giving access to
> >>> an instance of this MIB module, is properly configured to give
> >>--------------------------------^
> >>I think that comma does not belong here.
> >>> access to the objects only to those principals (users) that have
> >>> legitimate rights to indeed GET or SET 
> (change/create/delete) them.
> >>
> >>Sorry for not catching this before.  The rest looks quite good.
> >>
> >OK, fixed.
> 
> This got dropped from the existing language.  I didn't notice it
> before.  It sure is hard to read what's really there instead of
> what you think is there :-(
> 
> //cmh
> 
>