[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Sip] removing configuration from the SIP MIB



Clarification question - does this proposal also covers the objects that control SNMP notifications? )sipServiceNotifEnable, sipStatusCodeNotifSend, sipStatusCodeNotifEmitMode, sipStatusCodeNotifThresh, sipStatusCodeNotifInterval)

Thanks and Regards,

Dan



> -----Original Message-----
> From: sip-bounces at ietf.org [mailto:sip-bounces at ietf.org]On 
> Behalf Of Rohan Mahy
> Sent: 06 August, 2004 12:41 AM
> To: sip at ietf.org WG
> Cc: Rohan Mahy; Dean Willis
> Subject: [Sip] removing configuration from the SIP MIB
> 
> 
> 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 sip-implementors at cs.columbia.edu for questions on current sip
> Use sipping at ietf.org 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 sip-implementors at cs.columbia.edu for questions on current sip
Use sipping at ietf.org for new developments on the application of sip