Subject: Re: [Sip] removing configuration from the SIP MIB

From: Kevin Lingle <[email-masked]>
Date: Wed, 29 Sep 2004 14:29:07 -0400

here are the proposed access level changes for mib objects
in SIP-COMMON-MIB and SIP-SERVER-MIB modules...

based on...
http://www.ietf.org/internet-drafts/draft-ietf-sip-mib-08.txt

SIP-COMMON-MIB
(currently 21 read-write objects)
OBJECT                     PROPOSED CHANGE
----------------------     ---------------
sipServiceAdminStatus      remove
sipOrganization            make read-only
sipServiceNotifEnable      no change (note 1)
sipCfgTimerA               make read-only
sipCfgTimerB               make read-only
sipCfgTimerC               make read-only
sipCfgTimerD               make read-only
sipCfgTimerE               make read-only
sipCfgTimerF               make read-only
sipCfgTimerG               make read-only
sipCfgTimerH               make read-only
sipCfgTimerI               make read-only
sipCfgTimerJ               make read-only
sipCfgTimerK               make read-only
sipCfgTimerT1              make read-only
sipCfgTimerT2              make read-only
sipCfgTimerT4              make read-only
sipStatusCodeNotifSend     no change (note 1)
sipStatusCodeNotifEmitMode no change (note 1)
sipStatusCodeNotifThresh   no change (note 1)
sipStatusCodeNotifInterval no change (note 1)

SIP-SERVER-MIB
  (9 read-write objects)
OBJECT                          PROPOSED CHANGE
----------------------          ---------------
sipServerHostAddrType           make read-only
sipServerHostAddr               make read-only
sipProxyRecursion               make read-only
sipProxyRecordRoute             make read-only
sipProxyAuthMethod              make read-only
sipProxyAuthRealm               make read-only
sipRegAllowThirdParty           make read-only
sipRegMaxContactExpiryDuration  make read-only
sipRegDfltRegActiveInterval     make read-only

note 1: read-write required to configure snmp notifications.

if there are no objections to this, we'll make it so in
rev -09 of the draft.

kevin

Rohan Mahy wrote:
> Hi Everyone,
> 
> The current SIP MIB  (-08) contains a handful of elements which are 
> related to configuration.  These elements are insufficient to usefully 
> configure a UA or a Proxy.   The SIP community already has a framework 
> for UA Profile configuration, and we have not identified anyone who is 
> planning to implement the SIP MIB for configuration. In addition, the 
> configuration issues directly affects 3 of the 4 open issues (#1, #46, 
> and #79) with the MIB. Finally, the IETF has de-emphasized using MIBs 
> for configuration since last year.
> 
> Unless someone objects (and volunteers to help), the chairs propose that 
> we do not provide  elements for configuration use, and don't make 
> elements write or create enabled which would only use this attribute for 
> configuration.  We would keep many of these same elements for monitoring 
> the actual configuration of elements relevant for monitoring, debugging, 
> or troubleshooting purposes.  If the group does not object, the authors 
> will propose specific changes to the list, edit the document 
> appropriately, and we can send the document to the Area Director.
> 
> Please send mail right away if you disagree with this approach.
> 
> If the group agrees with this proposal, this still leaves issue #87 as 
> an open issue, plus the issue that Bob Penfield recently brought  up on 
> the list. Most issues with the MIB are discussed here:
> 
> http://www1.ietf.org/mail-archive/web/sip/current/msg10184.html
> 
> many thanks,
> -rohan
> 
> 
> _______________________________________________
> Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
> This list is for NEW development of the core SIP Protocol
> Use [email-masked] for questions on current sip
> Use [email-masked] for new developments on the application of sip
> 

_______________________________________________
Sip mailing list  https://www1.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use [email-masked] for questions on current sip
Use [email-masked] for new developments on the application of sip