draft-ietf-sip-mib-10.txt   draft-ietf-sip-mib-11.txt 
SIP Working Group K. Lingle SIP Working Group K. Lingle
Internet-Draft Cisco Systems, Inc. Internet-Draft Cisco Systems, Inc.
Expires: September 4, 2006 J. Mule Expires: November 18, 2006 J-F. Mule
CableLabs CableLabs
J. Maeng J. Maeng
D. Walker D. Walker
March 3, 2006 May 17, 2006
Management Information Base for the Session Initiation Protocol (SIP) Management Information Base for the Session Initiation Protocol (SIP)
draft-ietf-sip-mib-10.txt draft-ietf-sip-mib-11.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 37 skipping to change at page 1, line 37
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 4, 2006. This Internet-Draft will expire on November 18, 2006.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it describes a set of managed objects that are used to In particular, it describes a set of managed objects that are used to
skipping to change at page 2, line 21 skipping to change at page 2, line 21
5. Structure of the SIP MIB . . . . . . . . . . . . . . . . . . . 4 5. Structure of the SIP MIB . . . . . . . . . . . . . . . . . . . 4
5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6 5.1. Textual Conventions . . . . . . . . . . . . . . . . . . . 6
5.2. Relationship to the Network Services MIB . . . . . . . . . 6 5.2. Relationship to the Network Services MIB . . . . . . . . . 6
5.3. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . 10 5.3. IMPORTed MIB Modules and REFERENCE Clauses . . . . . . . . 10
6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 10 6. Accommodating SIP Extension Methods . . . . . . . . . . . . . 10
7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11 7. Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 11
7.1. SIP Textual Conventions . . . . . . . . . . . . . . . . . 11 7.1. SIP Textual Conventions . . . . . . . . . . . . . . . . . 11
7.2. SIP Common MIB Module . . . . . . . . . . . . . . . . . . 14 7.2. SIP Common MIB Module . . . . . . . . . . . . . . . . . . 14
7.3. SIP User Agent MIB Module . . . . . . . . . . . . . . . . 53 7.3. SIP User Agent MIB Module . . . . . . . . . . . . . . . . 53
7.4. SIP Server MIB Module (Proxy, Redirect and Registrar 7.4. SIP Server MIB Module (Proxy, Redirect and Registrar
Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 57 Servers) . . . . . . . . . . . . . . . . . . . . . . . . . 58
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 76
9. Security Considerations . . . . . . . . . . . . . . . . . . . 76 9. Security Considerations . . . . . . . . . . . . . . . . . . . 76
10. Contributor Acknowledgments . . . . . . . . . . . . . . . . . 78 10. Contributor Acknowledgments . . . . . . . . . . . . . . . . . 78
11. Changes from Previous Draft Revisions . . . . . . . . . . . . 78 11. Changes from Previous Draft Revisions . . . . . . . . . . . . 78
12. Normative References . . . . . . . . . . . . . . . . . . . . . 90 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 90 12.1. Normative References . . . . . . . . . . . . . . . . . . . 90
Intellectual Property and Copyright Statements . . . . . . . . . . 91 12.2. Informative References . . . . . . . . . . . . . . . . . . 91
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 91
Intellectual Property and Copyright Statements . . . . . . . . . . 92
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119 [RFC2119]. document are to be interpreted as described in RFC 2119 [RFC2119].
2. Introduction 2. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
skipping to change at page 10, line 15 skipping to change at page 10, line 15
5.3. IMPORTed MIB Modules and REFERENCE Clauses 5.3. IMPORTed MIB Modules and REFERENCE Clauses
The SIP MIB modules defined in this document IMPORT definitions The SIP MIB modules defined in this document IMPORT definitions
normatively from the following MIB modules, beyond [RFC2578], normatively from the following MIB modules, beyond [RFC2578],
[RFC2579] and [RFC2580]: INET-ADDRESS-MIB [RFC4001], NETWORK- [RFC2579] and [RFC2580]: INET-ADDRESS-MIB [RFC4001], NETWORK-
SERVICES-MIB [RFC2788], SNMP-FRAMEWORK-MIB [RFC3411]. SERVICES-MIB [RFC2788], SNMP-FRAMEWORK-MIB [RFC3411].
This MIB module also includes REFERENCE clauses that normatively This MIB module also includes REFERENCE clauses that normatively
refer to SIP [RFC3261], and INET-ADDRESS-MIB [RFC4001]. refer to SIP [RFC3261], and INET-ADDRESS-MIB [RFC4001].
Finally, this MIB module makes informative references to several RFCs
in some of the examples described in the DESCRIPTION clauses,
including Reliability of Provisional Responses in SIP [RFC3262], and
SIP over SCTP [RFC4168].
6. Accommodating SIP Extension Methods 6. Accommodating SIP Extension Methods
The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other The core set of SIP methods is defined in RFC 3261 [RFC3261]. Other
IETF RFCs define additional methods. In the future, additional IETF RFCs define additional methods. In the future, additional
methods may be defined. In order to avoid having to update the SIP- methods may be defined. In order to avoid having to update the SIP-
COMMON-MIB module to accommodate these extension methods, we use a COMMON-MIB module to accommodate these extension methods, we use a
method identifier name (SipMethodName textual-convention) to method identifier name (SipMethodName textual-convention) to
represent all SIP methods registered with IANA. See IANA represent all SIP methods registered with IANA. See IANA
Consideration section. Consideration section.
skipping to change at page 10, line 38 skipping to change at page 10, line 43
registered with IANA. The table is informational in nature and registered with IANA. The table is informational in nature and
populated by the system. Entries cannot be added or deleted by a populated by the system. Entries cannot be added or deleted by a
SNMP manager. SNMP manager.
The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the The SIP specification RFC 3261 [RFC3261] section 27.4 establishes the
sub-registries for SIP Methods and Response Codes under sub-registries for SIP Methods and Response Codes under
http://www.iana.org/assignments/sip-parameters. This document uses http://www.iana.org/assignments/sip-parameters. This document uses
the existing sub-registry for the names of registered SIP method. the existing sub-registry for the names of registered SIP method.
For example, in the sipSupportedMethodTable of SIP-COMMON-MIB, the For example, in the sipSupportedMethodTable of SIP-COMMON-MIB, the
sipMethodName values can be represented as as follows: sipMethodName values can be represented as follows:
+------------------------+ +------------------------+
| sipMethodSupportedName | | sipMethodName |
+------------------------+ +------------------------+
| "ACK" | | "ACK" |
| "BYE" | | "BYE" |
| "CANCEL" | | "CANCEL" |
| "INVITE" | | "INVITE" |
| "OPTIONS" | | "OPTIONS" |
+------------------------+ +------------------------+
7. Definitions 7. Definitions
skipping to change at page 11, line 20 skipping to change at page 11, line 30
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
mib-2 mib-2
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
sipTC MODULE-IDENTITY sipTC MODULE-IDENTITY
LAST-UPDATED "200603021700Z" LAST-UPDATED "200605171700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
skipping to change at page 12, line 7 skipping to change at page 12, line 19
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) MIB Textual "Session Initiation Protocol (SIP) MIB Textual
Conventions module used by other SIP-related Conventions module used by other SIP-related
MIB Modules. MIB Modules.
Copyright (C) The Internet Society (2006). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200603021700Z" REVISION "200605171700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-TC module. "Initial version of the IETF SIP-TC module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX1 } ::= { mib-2 XXX1 }
-- RFC Ed: replace XXX1 with actual IANA assigned number for this -- RFC Ed: replace XXX1 with actual IANA assigned number for this
-- sipTC mib module and remove this note -- sipTC mib module and remove this note
-- --
-- Textual Conventions -- Textual Conventions
skipping to change at page 12, line 31 skipping to change at page 12, line 43
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention is a bit map. Each bit represents a "This convention is a bit map. Each bit represents a
transport protocol. If a bit has value 1, then that transport protocol. If a bit has value 1, then that
selected transport protocol is in some way dependent selected transport protocol is in some way dependent
on the context of the object using this convention. on the context of the object using this convention.
If a bit has value 0, then that transport protocol If a bit has value 0, then that transport protocol
is not selected. Combinations of bits can be is not selected. Combinations of bits can be
set when multiple transport protocols are selected. set when multiple transport protocols are selected.
bit 0 : a protocol other than those defined here. bit 0 : a protocol other than those defined here
bit 1 : User Datagram Protocol. bit 1 : User Datagram Protocol
bit 2 : Transmission Control Protocol. bit 2 : Transmission Control Protocol
bit 3 : Stream Control Transmission Protocol. bit 3 : Stream Control Transmission Protocol
bit 4 : Transport Layer Security Protocol." bit 4 : Transport Layer Security Protocol over TCP
bit 5 : Transport Layer Security Protocol over SCTP"
SYNTAX BITS { SYNTAX BITS {
other(0), -- none of the following other(0), -- none of the following
udp(1), udp(1),
tcp(2), tcp(2),
sctp(3), sctp(3), -- RFC4168
tls(4) tlsTcp(4),
tlsSctp(5) -- RFC 4168
} }
-- REFERENCE "RFC 3261, Section 18" -- REFERENCE "RFC 3261, Section 18"
-- REFERENCE "RFC 4168"
SipEntityRole ::= TEXTUAL-CONVENTION SipEntityRole ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This convention defines the role of a SIP entity. "This convention defines the role of a SIP entity.
Examples of SIP entities are proxies, user agents, Examples of SIP entities are proxies, user agents,
redirect servers, registrars or combinations of redirect servers, registrars or combinations of
the above." the above."
SYNTAX BITS { SYNTAX BITS {
other(0), other(0),
skipping to change at page 13, line 37 skipping to change at page 14, line 4
-- REFERENCE "RFC 3261, Section 19.2" -- REFERENCE "RFC 3261, Section 19.2"
SipMethodName ::= TEXTUAL-CONVENTION SipMethodName ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention is a string that uniquely "This textual convention is a string that uniquely
identifies a SIP method. The scope of uniqueness identifies a SIP method. The scope of uniqueness
is the context of all defined SIP methods. is the context of all defined SIP methods.
Experimental support of extension methods is Experimental support of extension methods is
acceptable and expected. Extention methods are acceptable and expected. Extension methods are
those defined in Internet-Draft documents but those defined in Internet-Draft documents but
not yet allocated an official sanctioned by IANA. not yet allocated an official sanctioned by IANA.
To support experimental extension methods, any To support experimental extension methods, any
object using this textual convention as syntax object using this textual convention as syntax
MAY return/accept a method identifier value other MAY return/accept a method identifier value other
than those sanctioned by IANA. That system MUST than those sanctioned by IANA. That system MUST
ensure no collisions with officially assigned ensure no collisions with officially assigned
method names." method names."
SYNTAX OCTET STRING (SIZE (1..128)) SYNTAX OCTET STRING (SIZE (1..128))
skipping to change at page 14, line 37 skipping to change at page 15, line 4
FROM SNMPv2-CONF -- RFC 2580 FROM SNMPv2-CONF -- RFC 2580
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
SipTransportProtocol, SipTransportProtocol,
SipMethodName, SipMethodName,
SipEntityRole, SipEntityRole,
SipOptionTagHeaders SipOptionTagHeaders
FROM SIP-TC FROM SIP-TC
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetPortNumber InetPortNumber
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
sipCommonMIB MODULE-IDENTITY sipCommonMIB MODULE-IDENTITY
LAST-UPDATED "200603031700Z" LAST-UPDATED "200605171700Z"
ORGANIZATION "IETF Session Initiation Protocol Working Group" ORGANIZATION "IETF Session Initiation Protocol Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
USA USA
skipping to change at page 15, line 28 skipping to change at page 15, line 43
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 9100 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) Common MIB module. "Session Initiation Protocol (SIP) Common MIB module.
This module defines objects which MAY be common to all This module defines objects which MAY be common to all
SIP entities. SIP entities.
SIP is an application-layer signalling protocol for SIP is an application-layer signaling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 3261 (June telephone calls. SIP is defined in RFC 3261 (June
2002). 2002).
This MIB is defined for managing objects which are This MIB is defined for managing objects which are
common to SIP User Agents (UAs), Proxy, Redirect common to SIP User Agents (UAs), Proxy, Redirect
and Registrar servers. Objects specific to each of and Registrar servers. Objects specific to each of
these entities MAY be managed using entity specific these entities MAY be managed using entity specific
skipping to change at page 16, line 41 skipping to change at page 17, line 7
Registrar: A registrar is a server that accepts Registrar: A registrar is a server that accepts
REGISTER requests and places the information it REGISTER requests and places the information it
receives in those requests into the location service receives in those requests into the location service
for the domain it handles. for the domain it handles.
Copyright (C) The Internet Society (2006). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and -- RFC Ed: replace XXXX with actual RFC number and
-- remove this note -- remove this note
REVISION "200603031700Z" REVISION "200605171700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-COMMON-MIB module. "Initial version of the IETF SIP-COMMON-MIB module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX2 } ::= { mib-2 XXX2 }
-- RFC Ed: replace XXX2 with actual IANA assigned number and -- RFC Ed: replace XXX2 with actual IANA assigned number and
-- remove this note -- remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 } sipCommonMIBNotifs OBJECT IDENTIFIER ::= { sipCommonMIB 0 }
skipping to change at page 19, line 36 skipping to change at page 19, line 50
process SIP messages. process SIP messages.
congested : The application is operational but no congested : The application is operational but no
additional inbound transactions can be additional inbound transactions can be
accommodated at the moment. accommodated at the moment.
restarting : The application is currently unavailable restarting : The application is currently unavailable
but it is in the process of restarting and but it is in the process of restarting and
will, presumably, soon be able to process will, presumably, soon be able to process
SIP messages. SIP messages.
quiescing : The application is currently operational quiescing : The application is currently operational
but has been administratively put into but has been administratively put into
quiesce mode. Additional inbound quiescence mode. Additional inbound
transactions MAY be rejected. transactions MAY be rejected.
testing : The application is currently in test mode testing : The application is currently in test mode
and MAY not be able to process SIP and MAY not be able to process SIP
messages. messages.
The operational status values defined for this object The operational status values defined for this object
are not based on any specific information contained in are not based on any specific information contained in
the SIP standard." the SIP standard."
::= { sipCommonCfgEntry 2 } ::= { sipCommonCfgEntry 2 }
sipServiceStartTime OBJECT-TYPE sipServiceStartTime OBJECT-TYPE
skipping to change at page 20, line 41 skipping to change at page 21, line 7
REFERENCE REFERENCE
"RFC 3261, Section 20.25" "RFC 3261, Section 20.25"
::= { sipCommonCfgEntry 5 } ::= { sipCommonCfgEntry 5 }
sipMaxTransactions OBJECT-TYPE sipMaxTransactions OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the maximum number of simultaneous "This object indicates the maximum number of simultaneous
transactions that the SIP entity can manage. In general transactions per second that the SIP entity can manage.
the value of this object SHOULD reflect a level of In general, the value of this object SHOULD reflect a
transaction processing that is considered high enough level of transaction processing per second that is
to impact the systems CPU and/or memory resources to considered high enough to impact the system's CPU and/or
the point of deteriorating SIP call processing but not memory resources to the point of deteriorating SIP call
high enough to cause catastrophic system failure." processing but not high enough to cause catastrophic
system failure."
::= { sipCommonCfgEntry 6 } ::= { sipCommonCfgEntry 6 }
sipServiceNotifEnable OBJECT-TYPE sipServiceNotifEnable OBJECT-TYPE
SYNTAX BITS { SYNTAX BITS {
sipServiceColdStart(0), sipServiceColdStart(0),
sipServiceWarmStart(1), sipServiceWarmStart(1),
sipServiceStatusChanged(2) sipServiceStatusChanged(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies which SIP service related "This object specifies which SIP service related
notifications are enabled. Each bit represents notifications are enabled. Each bit represents
a specific notification. If a bit has a value 1, a specific notification. If a bit has a value 1,
the associated notification is enabled and will the associated notification is enabled and will
be generated by the SIP entity at the approriate be generated by the SIP entity at the appropriate
time. The notifications are OPTIONAL, and if they time. The notifications are OPTIONAL, and if they
are not implemented this object's value has no are not implemented this object's value has no
meaning and MUST be 0. Setting this object in that meaning and MUST be 0. Setting this object in that
circumstance SHOULD result in a badValue error. circumstance SHOULD result in a badValue error.
If notifications are supported, this object's default If notifications are supported, this object's default
value SHOULD reflect sipServiceColdStart and value SHOULD reflect sipServiceColdStart and
sipServiceWarmStart enabled and sipServiceStatusChanged sipServiceWarmStart enabled and sipServiceStatusChanged
disabled." disabled."
::= { sipCommonCfgEntry 7 } ::= { sipCommonCfgEntry 7 }
skipping to change at page 23, line 21 skipping to change at page 23, line 36
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains a list of the SIP option tags "This table contains a list of the SIP option tags
(SIP extensions) that either required, supported, or (SIP extensions) that either required, supported, or
unsupported by the SIP entity. unsupported by the SIP entity.
These option tags are used in the Require, These option tags are used in the Require,
Proxy-Require, Supported and Unsupported header fields. Proxy-Require, Supported and Unsupported header fields.
Example: if a user agent client supports and requires Example: if a user agent client supports and requires
the server to support reliability of provisional the server to support reliability of provisional
responses, this table contains a row with the string responses (IETF RFC 3262), this table contains a
'100rel' in sipOptionTag and the value 0xA0 in row with the option tag string '100rel' in sipOptionTag
and the OCTET STRING value of '1010 0000' or '0xA0' in
sipOptionTagHeaderField. sipOptionTagHeaderField.
If a server does not support the required feature If a server does not support the required feature
(indicated in a Require header to a UAS, or in a (indicated in a Require header to a UAS, or in a
Proxy-Require to a Proxy Server), the server returns a Proxy-Require to a Proxy Server), the server returns a
420 Bad Extension listing the feature in an Unsupported 420 Bad Extension listing the feature in an Unsupported
header. header.
Normally the list of such features supported by an Normally the list of such features supported by an
entity is static (i.e. will not change over time)." entity is static (i.e. will not change over time)."
skipping to change at page 26, line 20 skipping to change at page 26, line 36
associated method throughout this and other MIBs associated method throughout this and other MIBs
supported by this managed system." supported by this managed system."
::= { sipMethodSupportedEntry 1 } ::= { sipMethodSupportedEntry 1 }
sipMethodName OBJECT-TYPE sipMethodName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the supported method's name. "This object reflects the supported method's name.
The method name MUST be all upper case (eg, 'FOO')." The method name MUST be all upper case
(e.g, 'INVITE')."
::= { sipMethodSupportedEntry 2 } ::= { sipMethodSupportedEntry 2 }
-- --
-- SIP Timer Configuration -- SIP Timer Configuration
-- --
sipCommonCfgTimerTable OBJECT-TYPE sipCommonCfgTimerTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipCommonCfgTimerEntry SYNTAX SEQUENCE OF SipCommonCfgTimerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 38, line 40 skipping to change at page 39, line 9
related to particular status codes each SIP entity in related to particular status codes each SIP entity in
this system has been requested to monitor. this system has been requested to monitor.
There is an entry in this table corresponding to each There is an entry in this table corresponding to each
entry in sipStatusCodesTable. Therefore, this entry in sipStatusCodesTable. Therefore, this
table augments that table and utilizes the same index table augments that table and utilizes the same index
methodology. methodology.
The objects in this table are not included directly The objects in this table are not included directly
in the sipStatusCodesTable simply to keep the in the sipStatusCodesTable simply to keep the
status code notification control objects seperate from status code notification control objects separate from
the actual status code statistics." the actual status code statistics."
::= { sipCommonStatusCode 3 } ::= { sipCommonStatusCode 3 }
sipStatusCodeNotifEntry OBJECT-TYPE sipStatusCodeNotifEntry OBJECT-TYPE
SYNTAX SipStatusCodeNotifEntry SYNTAX SipStatusCodeNotifEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This row contains information controlling notifications "This row contains information controlling notifications
for a particular SIP status code that the SIP entity has for a particular SIP status code that the SIP entity has
skipping to change at page 40, line 51 skipping to change at page 41, line 20
sipStatusCodeNotifThresh OBJECT-TYPE sipStatusCodeNotifThresh OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the number of response messages "This object specifies the number of response messages
sent or received by this system that are considered sent or received by this system that are considered
excessive. Based on crossing that threshold, a excessive. Based on crossing that threshold, a
sipStatusCodeThreshExceededInNotif notification or a sipStatusCodeThreshExceededInNotif notification or a
sipStatusCodeThreshExceededOutNotif will be sent. sipStatusCodeThreshExceededOutNotif will be sent.
The sipStatusCodeThreshExceededIn/OutNotif can be The sipStatusCodeThreshExceededInNotif and
used as an early warning mechanism in lieu of using sipStatusCodeThreshExceededOutNotif notifications can
sipStatusCodeNotif. be used as an early warning mechanism in lieu of
using sipStatusCodeNotif.
Note that the configuration applied by this object Note that the configuration applied by this object
will be applied equally to inbound and outbound will be applied equally to inbound and outbound
response messages." response messages."
DEFVAL { 500 } DEFVAL { 500 }
::= { sipStatusCodeNotifEntry 3 } ::= { sipStatusCodeNotifEntry 3 }
sipStatusCodeNotifInterval OBJECT-TYPE sipStatusCodeNotifInterval OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object specifies the time interval over which "This object specifies the time interval over which
if sipCommonStatusCodeThresh is exceeded, with if sipCommonStatusCodeThresh is exceeded, with
respect to sent or received messages, a respect to sent or received messages, a
sipStatusCodeThreshExceededIn/Out notification will sipStatusCodeThreshExceededInNotif or
sipStatusCodeThreshExceededOutNotif notification will
be sent. be sent.
Note that the configuration applied by this object Note that the configuration applied by this object
will be applied equally to inbound and outbound will be applied equally to inbound and outbound
response messages." response messages."
DEFVAL { 60 } DEFVAL { 60 }
::= { sipStatusCodeNotifEntry 4 } ::= { sipStatusCodeNotifEntry 4 }
-- --
-- Transaction Statistics -- Transaction Statistics
skipping to change at page 45, line 49 skipping to change at page 46, line 19
-- --
sipStatusCodeNotifTo OBJECT-TYPE sipStatusCodeNotifTo OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the To header in the "This object contains the value of the To header in the
message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of
this object value. this object value.
For example, 'To: Watson ." For example, 'To: Watson '."
::= { sipCommonNotifObjects 1 } ::= { sipCommonNotifObjects 1 }
sipStatusCodeNotifFrom OBJECT-TYPE sipStatusCodeNotifFrom OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the From header in the "This object contains the value of the From header in the
message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of
this object value. this object value.
For example, 'From: Watson '." For example, 'From: Watson '."
skipping to change at page 46, line 25 skipping to change at page 46, line 43
sipStatusCodeNotifCallId OBJECT-TYPE sipStatusCodeNotifCallId OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the value of the CallId in the "This object contains the value of the CallId in the
message containing the status code that caused the message containing the status code that caused the
notification. The header name will be part of notification. The header name will be part of
this object value. this object value.
For example, 'Call-ID: 5551212@information.com'." For example, 'Call-ID: 5551212@example.com'."
::= { sipCommonNotifObjects 3 } ::= { sipCommonNotifObjects 3 }
sipStatusCodeNotifCSeq OBJECT-TYPE sipStatusCodeNotifCSeq OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object contains the CSeq value in the message "This object contains the CSeq value in the message
containing the status code that caused the notification. containing the status code that caused the notification.
The header name will be part of this object value. The header name will be part of this object value.
skipping to change at page 48, line 48 skipping to change at page 49, line 19
sipServiceWarmStart NOTIFICATION-TYPE sipServiceWarmStart NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipNotifSequenceNumber,
sipNotifApplIndex, sipNotifApplIndex,
sipServiceLastChange sipServiceLastChange
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that the SIP service has reinitialized "Signifies that the SIP service has reinitialized
itself and is restarting after an adminstrative itself and is restarting after an administrative
'reset'. The configuration or behavior of the service 'reset'. The configuration or behavior of the service
MAY be altered." MAY be altered."
::= { sipCommonMIBNotifs 5 } ::= { sipCommonMIBNotifs 5 }
sipServiceStatusChanged NOTIFICATION-TYPE sipServiceStatusChanged NOTIFICATION-TYPE
OBJECTS { OBJECTS {
sipNotifSequenceNumber, sipNotifSequenceNumber,
sipNotifApplIndex, sipNotifApplIndex,
sipServiceLastChange, sipServiceLastChange,
sipServiceOperStatus sipServiceOperStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Signifies that the SIP service operational status "Signifies that the SIP service operational status
skipping to change at page 49, line 37 skipping to change at page 50, line 12
-- --
sipCommonCompliance MODULE-COMPLIANCE sipCommonCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SIP entities." "The compliance statement for SIP entities."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { sipCommonConfigGroup, MANDATORY-GROUPS { sipCommonConfigGroup,
sipCommonStatsGroup } sipCommonStatsGroup }
GROUP sipCommonInformationalGroup
DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to
not provide any support for these objects as they
provide optional information."
GROUP sipCommonConfigTimerGroup GROUP sipCommonConfigTimerGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any timer configuration." not provide any timer configuration."
GROUP sipCommonStatsRetryGroup GROUP sipCommonStatsRetryGroup
DESCRIPTION DESCRIPTION
"This group is OPTIONAL. A SIP entity can elect to "This group is OPTIONAL. A SIP entity can elect to
not provide any retry statistics." not provide any retry statistics."
skipping to change at page 50, line 37 skipping to change at page 51, line 15
-- --
sipCommonConfigGroup OBJECT-GROUP sipCommonConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipProtocolVersion, sipProtocolVersion,
sipServiceOperStatus, sipServiceOperStatus,
sipServiceStartTime, sipServiceStartTime,
sipServiceLastChange, sipServiceLastChange,
sipTransportRcv, sipTransportRcv,
sipOptionTag, sipOptionTag,
sipOptionTagHeaderField, sipOptionTagHeaderField,
sipOrganization,
sipMaxTransactions, sipMaxTransactions,
sipServiceNotifEnable, sipServiceNotifEnable,
sipEntityType, sipEntityType,
sipMethodName sipMethodName
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration common "A collection of objects providing configuration common
to all SIP enities." to all SIP entities."
::= { sipCommonMIBGroups 1 } ::= { sipCommonMIBGroups 1 }
sipCommonInformationalGroup OBJECT-GROUP
OBJECTS {
sipOrganization
}
STATUS current
DESCRIPTION
"A collection of objects providing configuration
common to all SIP entities."
::= { sipCommonMIBGroups 2 }
sipCommonConfigTimerGroup OBJECT-GROUP sipCommonConfigTimerGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipCfgTimerA, sipCfgTimerA,
sipCfgTimerB, sipCfgTimerB,
sipCfgTimerC, sipCfgTimerC,
sipCfgTimerD, sipCfgTimerD,
sipCfgTimerE, sipCfgTimerE,
sipCfgTimerF, sipCfgTimerF,
sipCfgTimerG, sipCfgTimerG,
sipCfgTimerH, sipCfgTimerH,
sipCfgTimerI, sipCfgTimerI,
sipCfgTimerJ, sipCfgTimerJ,
sipCfgTimerK, sipCfgTimerK,
sipCfgTimerT1, sipCfgTimerT1,
sipCfgTimerT2, sipCfgTimerT2,
sipCfgTimerT4 sipCfgTimerT4
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing timer configuration "A collection of objects providing timer configuration
common to all SIP enities." common to all SIP entities."
::= { sipCommonMIBGroups 2 } ::= { sipCommonMIBGroups 3 }
sipCommonStatsGroup OBJECT-GROUP sipCommonStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipSummaryInRequests, sipSummaryInRequests,
sipSummaryOutRequests, sipSummaryOutRequests,
sipSummaryInResponses, sipSummaryInResponses,
sipSummaryOutResponses, sipSummaryOutResponses,
sipSummaryTotalTransactions, sipSummaryTotalTransactions,
sipStatsOutbounds, sipStatsOutbounds,
sipStatsInbounds, sipStatsInbounds,
skipping to change at page 51, line 45 skipping to change at page 52, line 34
sipStatusCodeRowStatus, sipStatusCodeRowStatus,
sipCurrentTransactions, sipCurrentTransactions,
sipNumUnsupportedUris, sipNumUnsupportedUris,
sipNumUnsupportedMethods, sipNumUnsupportedMethods,
sipOtherwiseDiscardedMsgs sipOtherwiseDiscardedMsgs
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics common "A collection of objects providing statistics common
to all SIP entities." to all SIP entities."
::= { sipCommonMIBGroups 3 } ::= { sipCommonMIBGroups 4 }
sipCommonStatsRetryGroup OBJECT-GROUP sipCommonStatsRetryGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatsRetries, sipStatsRetries,
sipStatsRetryFinalResponses, sipStatsRetryFinalResponses,
sipStatsRetryNonFinalResponses sipStatsRetryNonFinalResponses
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing retry statistics." "A collection of objects providing retry statistics."
::= { sipCommonMIBGroups 4 } ::= { sipCommonMIBGroups 5 }
sipCommonNotifGroup NOTIFICATION-GROUP sipCommonNotifGroup NOTIFICATION-GROUP
NOTIFICATIONS { NOTIFICATIONS {
sipStatusCodeNotif, sipStatusCodeNotif,
sipStatusCodeThreshExceededInNotif, sipStatusCodeThreshExceededInNotif,
sipStatusCodeThreshExceededOutNotif, sipStatusCodeThreshExceededOutNotif,
sipServiceColdStart, sipServiceColdStart,
sipServiceWarmStart, sipServiceWarmStart,
sipServiceStatusChanged sipServiceStatusChanged
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of notifications common to all SIP "A collection of notifications common to all SIP
entities." entities."
::= { sipCommonMIBGroups 5 } ::= { sipCommonMIBGroups 6 }
sipCommonStatusCodeNotifGroup OBJECT-GROUP sipCommonStatusCodeNotifGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifSend, sipStatusCodeNotifSend,
sipStatusCodeNotifEmitMode, sipStatusCodeNotifEmitMode,
sipStatusCodeNotifThresh, sipStatusCodeNotifThresh,
sipStatusCodeNotifInterval sipStatusCodeNotifInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects related to controlling and "A collection of objects related to controlling and
attribution of notifications common to all SIP attribution of notifications common to all SIP
entities." entities."
::= { sipCommonMIBGroups 6 } ::= { sipCommonMIBGroups 7 }
sipCommonNotifObjectsGroup OBJECT-GROUP sipCommonNotifObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipStatusCodeNotifTo, sipStatusCodeNotifTo,
sipStatusCodeNotifFrom, sipStatusCodeNotifFrom,
sipStatusCodeNotifCallId, sipStatusCodeNotifCallId,
sipStatusCodeNotifCSeq, sipStatusCodeNotifCSeq,
sipNotifApplIndex, sipNotifApplIndex,
sipNotifSequenceNumber sipNotifSequenceNumber
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of accessible-for-notify objects "A collection of accessible-for-notify objects
related to the notification defined in this related to the notification defined in this
MIB module." MIB module."
::= { sipCommonMIBGroups 7 } ::= { sipCommonMIBGroups 8 }
END END
7.3. SIP User Agent MIB Module 7.3. SIP User Agent MIB Module
SIP-UA-MIB DEFINITIONS ::= BEGIN SIP-UA-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
skipping to change at page 53, line 35 skipping to change at page 54, line 24
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB -- RFC 4001 FROM INET-ADDRESS-MIB -- RFC 4001
SipEntityRole SipEntityRole
FROM SIP-TC; FROM SIP-TC;
sipUAMIB MODULE-IDENTITY sipUAMIB MODULE-IDENTITY
LAST-UPDATED "200603021700Z" LAST-UPDATED "200605171700Z"
ORGANIZATION "IETF Session Initiation Protocol ORGANIZATION "IETF Session Initiation Protocol
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
skipping to change at page 54, line 13 skipping to change at page 54, line 49
Co-editor Joon Maeng Co-editor Joon Maeng
email: jmaeng@austin.rr.com email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule Co-editor Jean-Francois Mule
CableLabs CableLabs
postal: 858 Coal Creek Circle postal: 858 Coal Creek Circle
Louisville, CO 80027 Louisville, CO 80027
USA USA
email: jf.mule@cablelabs.com email: jf.mule@cablelabs.com
phone: +1 303 661 9100 phone: +1 303 661 9100
Co-editor Dave Walker Co-editor Dave Walker
email: drwalker@rogers.com" email: drwalker@rogers.com"
DESCRIPTION DESCRIPTION
"Session Initiation Protocol (SIP) User Agent (UA) "Session Initiation Protocol (SIP) User Agent (UA)
MIB module. MIB module.
SIP is an application-layer signalling protocol for SIP is an application-layer signaling protocol for
creating, modifying and terminating multimedia creating, modifying and terminating multimedia
sessions with one or more participants. These sessions sessions with one or more participants. These sessions
include Internet multimedia conferences and Internet include Internet multimedia conferences and Internet
telephone calls. SIP is defined in RFC 3261 (June telephone calls. SIP is defined in RFC 3261 (June
2002). 2002).
A User Agent is an application that contains both a A User Agent is an application that contains both a
User Agent Client (UAC) and a User Agent Server (UAS). User Agent Client (UAC) and a User Agent Server (UAS).
A UAC is an application that initiates a SIP request. A UAC is an application that initiates a SIP request.
A UAS is an application that contacts the user when a A UAS is an application that contacts the user when a
SIP request is received and that returns a response on SIP request is received and that returns a response on
behalf of the user. The response accepts, rejects, or behalf of the user. The response accepts, rejects, or
redirects the request. redirects the request.
Copyright (C) The Internet Society (2006). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of RFC XXXX; see the RFC of this MIB module is part of RFC XXXX; see the RFC
itself for full legal notices." itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200603021700Z" REVISION "200605171700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-UA-MIB module. "Initial version of the IETF SIP-UA-MIB module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX3 } ::= { mib-2 XXX3 }
-- RFC Ed: replace XXX3 with actual IANA assigned number -- RFC Ed: replace XXX3 with actual IANA assigned number
-- RFC Ed: and remove these notes -- RFC Ed: and remove these notes
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
skipping to change at page 58, line 14 skipping to change at page 59, line 4
FROM SNMP-FRAMEWORK-MIB -- RFC 3411 FROM SNMP-FRAMEWORK-MIB -- RFC 3411
applIndex applIndex
FROM NETWORK-SERVICES-MIB -- RFC 2788 FROM NETWORK-SERVICES-MIB -- RFC 2788
InetAddressType, InetAddressType,
InetAddress InetAddress
FROM INET-ADDRESS-MIB; -- RFC 4001 FROM INET-ADDRESS-MIB; -- RFC 4001
sipServerMIB MODULE-IDENTITY sipServerMIB MODULE-IDENTITY
LAST-UPDATED "200603021700Z" LAST-UPDATED "200605171700Z"
ORGANIZATION "IETF Session Initiation Protocol ORGANIZATION "IETF Session Initiation Protocol
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"SIP WG email: sip@ietf.org "SIP WG email: sip@ietf.org
Co-editor Kevin Lingle Co-editor Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
postal: 7025 Kit Creek Road postal: 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
skipping to change at page 59, line 23 skipping to change at page 60, line 13
Unlike a User Agent Server it does not accept calls. Unlike a User Agent Server it does not accept calls.
A Registrar is a server that accepts REGISTER A Registrar is a server that accepts REGISTER
requests. A Registrar is typically co-located with requests. A Registrar is typically co-located with
a Proxy or Redirect Server. a Proxy or Redirect Server.
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
This version of this MIB module is part of RFC XXXX; This version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices." see the RFC itself for full legal notices."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
REVISION "200603021700Z" REVISION "200605171700Z"
DESCRIPTION DESCRIPTION
"Initial version of the IETF SIP-SERVER-MIB module. "Initial version of the IETF SIP-SERVER-MIB module.
This version published as part of RFC XXXX." This version published as part of RFC XXXX."
-- RFC Ed: replace XXXX with actual RFC number and remove this note -- RFC Ed: replace XXXX with actual RFC number and remove this note
::= { mib-2 XXX4 } ::= { mib-2 XXX4 }
-- RFC Ed: replace XXX4 with actual IANA assigned number -- RFC Ed: replace XXX4 with actual IANA assigned number
-- and remove this note -- and remove this note
-- Top-Level Components of this MIB. -- Top-Level Components of this MIB.
sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 } sipServerMIBObjects OBJECT IDENTIFIER ::= { sipServerMIB 1 }
skipping to change at page 61, line 4 skipping to change at page 61, line 42
SYNTAX InetAddress SYNTAX InetAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the host portion of a SIP URI that is "This is the host portion of a SIP URI that is
assigned to the SIP server. It MAY contain a fully assigned to the SIP server. It MAY contain a fully
qualified domain name, or an IP address. The length qualified domain name, or an IP address. The length
of the value will depend on the type of address of the value will depend on the type of address
specified. specified.
sipServerHostAddrType formalizes the type of address sipServerHostAddrType formalizes the type of address
given by this object. It is the users responsibility given by this object. It is the user's
to maintain consistency between this object and the responsibility to maintain consistency between this
type specified by sipServerHostAddrType." object and the type specified by
sipServerHostAddrType."
REFERENCE REFERENCE
"RFC 3261, Section 19.1.1" "RFC 3261, Section 19.1.1"
::= { sipServerCfgEntry 2 } ::= { sipServerCfgEntry 2 }
-- --
-- This group contains MIB objects -- This group contains MIB objects
-- related to SIP Proxy Servers. -- related to SIP Proxy Servers.
-- --
sipProxyCfg OBJECT IDENTIFIER ::= sipProxyCfg OBJECT IDENTIFIER ::=
{ sipServerMIBObjects 3 } { sipServerMIBObjects 3 }
skipping to change at page 64, line 22 skipping to change at page 65, line 13
bit 2 HTTP Digest is used." bit 2 HTTP Digest is used."
REFERENCE REFERENCE
"RFC 3261 Sections 22, 23, 26, 26.2.3" "RFC 3261 Sections 22, 23, 26, 26.2.3"
::= { sipProxyCfgEntry 4 } ::= { sipProxyCfgEntry 4 }
sipProxyAuthRealm OBJECT-TYPE sipProxyAuthRealm OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the realm used in "This object reflects the default realm value used in
Proxy-Authenticate headers. Note that this MAY need Proxy-Authenticate headers. Note that this MAY need
to be stored per user." to be stored per user, in which case, this default
value is ignored."
REFERENCE REFERENCE
"RFC 3261, Section 22.1" "RFC 3261, Section 22.1"
::= { sipProxyCfgEntry 5 } ::= { sipProxyCfgEntry 5 }
-- --
-- Proxy Server Statistics -- Proxy Server Statistics
-- --
sipProxyStatsTable OBJECT-TYPE sipProxyStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipProxyStatsEntry SYNTAX SEQUENCE OF SipProxyStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 66, line 19 skipping to change at page 67, line 11
to uniquely identify these instances of SIP servers to uniquely identify these instances of SIP servers
and correlate them through the common framework of and correlate them through the common framework of
the NETWORK-SERVICES-MIB (RFC 2788). The same value the NETWORK-SERVICES-MIB (RFC 2788). The same value
of applIndex used in the corresponding SIP-COMMON-MIB of applIndex used in the corresponding SIP-COMMON-MIB
is used here." is used here."
INDEX { applIndex } INDEX { applIndex }
::= { sipRegCfgTable 1 } ::= { sipRegCfgTable 1 }
SipRegCfgEntry ::= SipRegCfgEntry ::=
SEQUENCE { SEQUENCE {
sipRegAllowThirdParty TruthValue,
sipRegMaxContactExpiryDuration Unsigned32, sipRegMaxContactExpiryDuration Unsigned32,
sipRegMaxUsers Unsigned32, sipRegMaxUsers Unsigned32,
sipRegCurrentUsers Gauge32, sipRegCurrentUsers Gauge32,
sipRegDfltRegActiveInterval Unsigned32 sipRegDfltRegActiveInterval Unsigned32
} }
sipRegAllowThirdParty OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects whether or not the Registrar
SHOULD allow third party registrations. In third-party
registration, the entity issuing the request (in the
From header) is different from the entity being
registered (in the To header) to whom the provided
Contact information applies.
If the value of this object is 'true', the Registrar
allows third-party registrations. If the value is
'false', third-party registrations are rejected: a
403 (Forbidden) status code is returned to the
requester.
This object SHOULD be non-volatile and its value
SHOULD be kept at reboot."
REFERENCE
"RFC 3261, Section 10.2"
::= { sipRegCfgEntry 1 }
sipRegMaxContactExpiryDuration OBJECT-TYPE sipRegMaxContactExpiryDuration OBJECT-TYPE
SYNTAX Unsigned32 (0..4294967295) SYNTAX Unsigned32 (0..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum expiry that may be "This object reflects the maximum expiry that may be
requested by a User Agent for a particular Contact. requested by a User Agent for a particular Contact.
User Agents can specify expiry using either an Expiry User Agents can specify expiry using either an Expiry
header in a REGISTER request, or using an Expires header in a REGISTER request, or using an Expires
parameter in a Contact header in a REGISTER request. parameter in a Contact header in a REGISTER request.
If the value requested by the User Agent is greater If the value requested by the User Agent is greater
than the value of this object, then the contact than the value of this object, then the contact
information is given the duration specified by this information is given the duration specified by this
object, and that duration is indicated to the User object, and that duration is indicated to the User
Agent in the response." Agent in the response."
::= { sipRegCfgEntry 2 } ::= { sipRegCfgEntry 1 }
sipRegMaxUsers OBJECT-TYPE sipRegMaxUsers OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the maximum number of users that "This object reflects the maximum number of users that
the Registrar supports. The current number of users the Registrar supports. The current number of users
is reflected by sipRegCurrentUsers." is reflected by sipRegCurrentUsers."
::= { sipRegCfgEntry 3 } ::= { sipRegCfgEntry 2 }
sipRegCurrentUsers OBJECT-TYPE sipRegCurrentUsers OBJECT-TYPE
SYNTAX Gauge32 (0..4294967295) SYNTAX Gauge32 (0..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the number of users currently "This object reflects the number of users currently
registered with the Registrar." registered with the Registrar."
::= { sipRegCfgEntry 4 } ::= { sipRegCfgEntry 3 }
sipRegDfltRegActiveInterval OBJECT-TYPE sipRegDfltRegActiveInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object reflects the default time interval the "This object reflects the default time interval the
Registrar considers registrations to be active. The Registrar considers registrations to be active. The
value is used to compute the Expires header in the value is used to compute the Expires header in the
skipping to change at page 68, line 10 skipping to change at page 68, line 26
interval shorter than specified by this object, the interval shorter than specified by this object, the
Registrar SHOULD honor that request. If a Contact Registrar SHOULD honor that request. If a Contact
entry does not have an 'expires' parameter, the value entry does not have an 'expires' parameter, the value
of the Expires header field is used instead. If a of the Expires header field is used instead. If a
Contact entry has no 'expires' parameter and no the Contact entry has no 'expires' parameter and no the
Expires header field is present, the value of this Expires header field is present, the value of this
object is used as the default value. object is used as the default value.
This object SHOULD be non-volatile and its value This object SHOULD be non-volatile and its value
SHOULD be kept at reboot." SHOULD be kept at reboot."
REFERENCE "RFC 3261, Section 10.2" REFERENCE "RFC 3261, Section 10.2"
::= { sipRegCfgEntry 5 } ::= { sipRegCfgEntry 4 }
-- --
-- Per User Information -- Per User Information
-- --
sipRegUserTable OBJECT-TYPE sipRegUserTable OBJECT-TYPE
SYNTAX SEQUENCE OF SipRegUserEntry SYNTAX SEQUENCE OF SipRegUserEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table contains information on all users "This table contains information on all users
skipping to change at page 75, line 4 skipping to change at page 75, line 19
sipProxyStatsGroup OBJECT-GROUP sipProxyStatsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipNumProxyRequireFailures sipNumProxyRequireFailures
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing statistics for "A collection of objects providing statistics for
SIP Proxy servers." SIP Proxy servers."
::= { sipServerMIBGroups 3 } ::= { sipServerMIBGroups 3 }
sipRegistrarConfigGroup OBJECT-GROUP sipRegistrarConfigGroup OBJECT-GROUP
OBJECTS { OBJECTS {
sipRegAllowThirdParty,
sipRegMaxContactExpiryDuration, sipRegMaxContactExpiryDuration,
sipRegMaxUsers, sipRegMaxUsers,
sipRegCurrentUsers, sipRegCurrentUsers,
sipRegDfltRegActiveInterval sipRegDfltRegActiveInterval
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects providing configuration for "A collection of objects providing configuration for
SIP Registrars." SIP Registrars."
::= { sipServerMIBGroups 4 } ::= { sipServerMIBGroups 4 }
skipping to change at page 78, line 21 skipping to change at page 78, line 32
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
10. Contributor Acknowledgments 10. Contributor Acknowledgments
We wish to thank the members of the IETF SIP and SIPPING working We wish to thank the members of the IETF SIP and SIPPING working
groups, and the SIP-MIB Design team for their comments and groups, and the SIP-MIB Design team for their comments and
suggestions. Detailed comments were provided by Tom Taylor, Kavitha suggestions. Detailed comments were provided by Tom Taylor, Kavitha
Patchayappan, Dan Romascanu, Cullen Jennins, Orit Levin, AC Patchayappan, Dan Romascanu, Cullen Jennings, Orit Levin, AC
Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and Mahendran, Mary Barnes, Rohan Mahy, Bob Penfield, Charles Eckel and
Dean Willis. Dean Willis.
11. Changes from Previous Draft Revisions 11. Changes from Previous Draft Revisions
-- RFC Ed: this entire section to be removed by RFC Editor before -- RFC Ed: this entire section to be removed by RFC Editor before
publication. publication.
Changes from draft-ietf-sip-mib-10.
The changes were mainly due to Last Call comments. The list of
changes includes:
o minor editorial nits including updates of all examples to use the
example.com domain name;
o technical changes and updates to SipTransportProtocol to clarify
the use of TLS over TCP and TLS over SCTP;
o changed sipMaxTransactions to reflect that it is max transactions
per second;
o removed sipOrganization from mandatory sipCommonConfigGroup in
MODULE-COMPLIANCE and created a new (opitonal) object group
sipCommonInformationalGroup;
o updated DESCRIPTION of sipProxyAuthRealm to indicate that this
object is the *default* realm value used by the proxy in Proxy-
Authenticate headers and, added a note to say that in case of per
user storage, the default value is ignored by the proxy.
o removed sipRegAllowThirdParty because no registrar implementer
seems to track them differently internally (no comment on the
list), and a registrar would have to implement new logic in order
to be able to exercise this part of the mib.
o added a couple of references like RFC 3262 and RFC 4168.
Changes from draft-ietf-sip-mib-09. Changes from draft-ietf-sip-mib-09.
The changes were minimal and mostly done to address MIB doctor The changes were minimal and mostly done to address MIB doctor
comments on SipMethodIdentifier. The list of changes includes: comments on SipMethodIdentifier. The list of changes includes:
o removal of SipMethodIdentifier textual convention per MIB doctor o removal of SipMethodIdentifier textual convention per MIB doctor
feedback feedback
o updates of normative references (e.g. RFC 3291 --> RFC 4001) o updates of normative references (e.g. RFC 3291 --> RFC 4001)
o added a new section to provide a citation to IMPORTed RFCs as they o added a new section to provide a citation to IMPORTed RFCs as they
are norm. references are norm. references
skipping to change at page 79, line 4 skipping to change at page 79, line 38
Changes from draft-ietf-sip-mib-08. Changes from draft-ietf-sip-mib-08.
The majority of changes are in response to additional SIP Working The majority of changes are in response to additional SIP Working
Group comments. Group comments.
o General o General
* The IANA Consideration section was updated and a new section * The IANA Consideration section was updated and a new section
9.2 was added to conform with the Guidelines for Authors and 9.2 was added to conform with the Guidelines for Authors and
Reviewers of MIB Documents, Reviewers of MIB Documents,
draft-ietf-ops-mib-review-guidelines-03.txt, section 3.7. draft-ietf-ops-mib-review-guidelines-03.txt, section 3.7.
* In general the ability to configure SIP entities via read- * In general the ability to configure SIP entities via read-
create or read-write objects was removed and those objects MAX- create or read-write objects was removed and those objects MAX-
ACCESS constrained to read-only. This change was made based on ACCESS constrained to read-only. This change was made based on
general consensus that SNMP should be limited to monitoring general consensus that SNMP should be limited to monitoring
rather than configuring/provisoning. rather than configuring/provisioning.
* The section 5.2 (Relationship to the Network Services MIB) was * The section 5.2 (Relationship to the Network Services MIB) was
updated to allow each instance of a SIP entity to have its own updated to allow each instance of a SIP entity to have its own
row in the applTable (a unique aplication identifier should now row in the applTable (a unique application identifier should
be appended to the "sip_xxx" entity-name). We also lowered the now be appended to the "sip_xxx" entity-name). We also lowered
level of requirement on the naming convention to a SHOULD the level of requirement on the naming convention to a SHOULD
instead of a MUST per wg input. instead of a MUST per wg input.
* Updated the ORGANISATION clause of all MIB modules to include * Updated the ORGANISATION clause of all MIB modules to include
the full SIP working group name. the full SIP working group name.
* Minor other editorial changes were made to the document. * Minor other editorial changes were made to the document.
* Updated Security consideration section. * Updated Security consideration section.
o SIP-COMMON-MIB o SIP-COMMON-MIB
* Module description of various SIP entities enhanced. * Module description of various SIP entities enhanced.
* sipServiceAdminStatus removed from the MIB due to general * sipServiceAdminStatus removed from the MIB due to general
removal of configuration capability. Resulting OID value removal of configuration capability. Resulting OID value
changes to succeeding entry objects. changes to succeeding entry objects.
* sipOrganization MAX-ACCESS changed to read-only. * sipOrganization MAX-ACCESS changed to read-only.
* sipCfgTimerA MAX-ACCESS changed to read-only. * sipCfgTimerA MAX-ACCESS changed to read-only.
* sipCfgTimerB MAX-ACCESS changed to read-only. * sipCfgTimerB MAX-ACCESS changed to read-only.
skipping to change at page 80, line 4 skipping to change at page 80, line 40
value changes to succeeding entry objects. value changes to succeeding entry objects.
* sipCfgTimer* OBJECT clauses regarding MIN-ACCESS levels in the * sipCfgTimer* OBJECT clauses regarding MIN-ACCESS levels in the
MODULE-COMPLIANCE were no longer needed due to MAX-ACCESS MODULE-COMPLIANCE were no longer needed due to MAX-ACCESS
changes for those objects. changes for those objects.
* The description clause of sipStatsInbounds was changed to state * The description clause of sipStatsInbounds was changed to state
that retransmissions are not counted. that retransmissions are not counted.
* The description clause of sipStatsRetries was changed to * The description clause of sipStatsRetries was changed to
indicate there could be multiple retries per request (we also indicate there could be multiple retries per request (we also
corrected a typo by removing the specific mention to INVITE corrected a typo by removing the specific mention to INVITE
requests). requests).
* The description clause of sipStatsRetryFinalResponses was * The description clause of sipStatsRetryFinalResponses was
changed to indicate there could be multiple retries per changed to indicate there could be multiple retries per
response. response.
o SIP-SERVER-MIB o SIP-SERVER-MIB
* Removed sipCommonCfgExpires OID declaration as this object * Removed sipCommonCfgExpires OID declaration as this object
group no longer exists since draft08. group no longer exists since draft08.
* sipUserTableRowStatus removed from the MIB due to general * sipUserTableRowStatus removed from the MIB due to general
removal of configuration capability. In conjuction, RowStatus removal of configuration capability. In conjunction, RowStatus
textual convention is no longer imported. textual convention is no longer imported.
* sipServerHostAddrType MAX-ACCESS changed to read-only. * sipServerHostAddrType MAX-ACCESS changed to read-only.
* sipServerHostAddr MAX-ACCESS changed to read-only. * sipServerHostAddr MAX-ACCESS changed to read-only.
* sipProxyRecursion MAX-ACCESS changed to read-only. * sipProxyRecursion MAX-ACCESS changed to read-only.
* sipProxyRecordRoute MAX-ACCESS changed to read-only. * sipProxyRecordRoute MAX-ACCESS changed to read-only.
* sipProxyAuthMethod MAX-ACCESS changed to read-only. * sipProxyAuthMethod MAX-ACCESS changed to read-only.
* sipRegAllowThirdParty MAX-ACCESS changed to read-only. * sipRegAllowThirdParty MAX-ACCESS changed to read-only.
* sipRegMaxContactExpiryDuration MAX-ACCESS changed to read-only. * sipRegMaxContactExpiryDuration MAX-ACCESS changed to read-only.
* sipRegDfltRegActiveInterval MAX-ACCESS changed to read-only. * sipRegDfltRegActiveInterval MAX-ACCESS changed to read-only.
* sipUserUri MAX-ACCESS changed to read-only. * sipUserUri MAX-ACCESS changed to read-only.
* 'smime' removed as a possible value for sipProxyAuthMethod. * 'smime' removed as a possible value for sipProxyAuthMethod.
o SIP-UA-MIB o SIP-UA-MIB
* sipUACfgServerStatus removed from the MIB due to general * sipUACfgServerStatus removed from the MIB due to general
skipping to change at page 80, line 26 skipping to change at page 81, line 15
* sipProxyRecursion MAX-ACCESS changed to read-only. * sipProxyRecursion MAX-ACCESS changed to read-only.
* sipProxyRecordRoute MAX-ACCESS changed to read-only. * sipProxyRecordRoute MAX-ACCESS changed to read-only.
* sipProxyAuthMethod MAX-ACCESS changed to read-only. * sipProxyAuthMethod MAX-ACCESS changed to read-only.
* sipRegAllowThirdParty MAX-ACCESS changed to read-only. * sipRegAllowThirdParty MAX-ACCESS changed to read-only.
* sipRegMaxContactExpiryDuration MAX-ACCESS changed to read-only. * sipRegMaxContactExpiryDuration MAX-ACCESS changed to read-only.
* sipRegDfltRegActiveInterval MAX-ACCESS changed to read-only. * sipRegDfltRegActiveInterval MAX-ACCESS changed to read-only.
* sipUserUri MAX-ACCESS changed to read-only. * sipUserUri MAX-ACCESS changed to read-only.
* 'smime' removed as a possible value for sipProxyAuthMethod. * 'smime' removed as a possible value for sipProxyAuthMethod.
o SIP-UA-MIB o SIP-UA-MIB
* sipUACfgServerStatus removed from the MIB due to general * sipUACfgServerStatus removed from the MIB due to general
removal of configuration capability. In conjuction, RowStatus removal of configuration capability. In conjunction, RowStatus
textual convention is no longer imported. textual convention is no longer imported.
* sipUACfgServerAddrType MAX-ACCESS changed to read-only. * sipUACfgServerAddrType MAX-ACCESS changed to read-only.
* sipUACfgServerAddr MAX-ACCESS changed to read-only. * sipUACfgServerAddr MAX-ACCESS changed to read-only.
* sipUACfgServerFunction MAX-ACCESS changed to read-only. * sipUACfgServerFunction MAX-ACCESS changed to read-only.
Changes from draft-ietf-sip-mib-07. Changes from draft-ietf-sip-mib-07.
The vast majority of changes are in response to the Working Group The vast majority of changes are in response to the Working Group
Last Call and expert review comments. Last Call and expert review comments.
o General o General
skipping to change at page 90, line 4 skipping to change at page 90, line 40
INVITE. INVITE.
* Gauge32 was not being IMPORTed. * Gauge32 was not being IMPORTed.
* sipServerContactDfltAction showed up in conformance and other * sipServerContactDfltAction showed up in conformance and other
object descriptions in an older form. object descriptions in an older form.
* sipServerHost replaced with InetAddressType/InetAddress object * sipServerHost replaced with InetAddressType/InetAddress object
pair (sipServerHostAddrType and sipServerHostAddr). pair (sipServerHostAddrType and sipServerHostAddr).
o SIP-UA-MIB o SIP-UA-MIB
* IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex. * IMPORTed Unsigned32 to support sipUACfgSipServerAddrIndex.
* sipUACfgSipServerEntry was referencing the wrong auxiliary * sipUACfgSipServerEntry was referencing the wrong auxiliary
object and listing that object in the conformance section. object and listing that object in the conformance section.
* sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it * sipUACfgSipServerEntry listed sipUACfgSipServerStatus when it
should have been listing sipUACfgSipServerAddrStatus. should have been listing sipUACfgSipServerAddrStatus.
* SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the * SIP-UA-MIB IMPORTed Counter32, but never used it. Removed the
IMPORT of Counter32. IMPORT of Counter32.
12. Normative References 12. References
12.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
A., Peterson, J., Sparks, R., Handley, M., and E. A., Peterson, J., Sparks, R., Handley, M., and E.
Schooler, "SIP: Session Initiation Protocol", RFC 3261, Schooler, "SIP: Session Initiation Protocol", RFC 3261,
June 2002. June 2002.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
"Conformance Statements for SMIv2", STD 58, RFC 2580, "Conformance Statements for SMIv2", STD 58, RFC 2580,
skipping to change at page 91, line 5 skipping to change at page 91, line 34
[RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC3411] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing Simple Network Management Architecture for Describing Simple Network Management
Protocol (SNMP) Management Frameworks", STD 62, RFC 3411, Protocol (SNMP) Management Frameworks", STD 62, RFC 3411,
December 2002. December 2002.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Network Schoenwaelder, "Textual Conventions for Internet Network
Addresses", RFC 4001, February 2005. Addresses", RFC 4001, February 2005.
12.2. Informative References
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002.
[RFC3262] Rosenberg, J. and H. Schulzrinne, "Reliability of
Provisional Responses in Session Initiation Protocol
(SIP)", RFC 3262, June 2002.
[RFC4168] Rosenberg, J., Schulzrinne, H., and G. Camarillo, "The
Stream Control Transmission Protocol (SCTP) as a Transport
for the Session Initiation Protocol (SIP)", RFC 4168,
October 2005.
Authors' Addresses Authors' Addresses
Kevin Lingle Kevin Lingle
Cisco Systems, Inc. Cisco Systems, Inc.
7025 Kit Creek Road 7025 Kit Creek Road
P.O. Box 14987 P.O. Box 14987
Research Triangle Park, NC 27709 Research Triangle Park, NC 27709
US US
Phone: +1 919 392 2029 Phone: +1 919 392 2029
 End of changes. 74 change blocks. 
106 lines changed or deleted 152 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/