1 SIP-TC-MIB DEFINITIONS ::= BEGIN
6 FROM SNMPv2-SMI -- RFC 2578
9 FROM SNMPv2-TC; -- RFC 2579
12 LAST-UPDATED "200704200000Z"
13 ORGANIZATION "IETF Session Initiation Protocol Working Group"
15 "SIP WG email: sip@ietf.org
17 Co-editor Kevin Lingle
19 postal: 7025 Kit Creek Road
21 Research Triangle Park, NC 27709
23 email: klingle@cisco.com
24 phone: +1 919 476 2029
27 email: jmaeng@austin.rr.com
29 Co-editor Jean-Francois Mule
31 postal: 858 Coal Creek Circle
34 email: jf.mule@cablelabs.com
35 phone: +1 303 661 9100
38 email: drwalker@rogers.com"
40 "Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION
41 module used by other SIP-related MIB Modules.
43 Copyright (C) The IETF Trust (2007). This version of
44 this MIB module is part of RFC 4780; see the RFC itself for
49 REVISION "200704200000Z"
51 "Initial version of the IETF SIP-TC-MIB module. This version
52 published as part of RFC 4780."
56 -- Textual Conventions
59 SipTCTransportProtocol ::= TEXTUAL-CONVENTION
62 "This convention is a bit map. Each bit represents a transport
63 protocol. If a bit has value 1, then that selected transport
64 protocol is in some way dependent on the context of the object
65 using this convention. If a bit has value 0, then that
66 transport protocol is not selected. Combinations of bits can
67 be set when multiple transport protocols are selected.
69 bit 0: a protocol other than those defined here
70 bit 1: User Datagram Protocol
71 bit 2: Transmission Control Protocol
72 bit 3: Stream Control Transmission Protocol
73 bit 4: Transport Layer Security Protocol over TCP
74 bit 5: Transport Layer Security Protocol over SCTP
76 REFERENCE "RFC 3261, Section 18 and RFC 4168"
78 other(0), -- none of the following
83 tlsSctp(5) -- RFC 4168
86 SipTCEntityRole ::= TEXTUAL-CONVENTION
89 "This convention defines the role of a SIP entity. Examples of
90 SIP entities are proxies, user agents, redirect servers,
91 registrars, or combinations of the above.
93 User Agent (UA): A logical entity that can act as both a user
94 agent client and user agent server.
99 User Agent Client (UAC): A logical entity that creates a new
100 request, and then uses the client transaction state machinery
101 to send it. The role of UAC lasts only for the duration of
102 that transaction. In other words, if a piece of software
103 initiates a request, it acts as a UAC for the duration of that
104 transaction. If it receives a request later, it assumes the
105 role of a user agent server for the processing of that
108 User Agent Server (UAS): A logical entity that generates a
109 response to a SIP request. The response accepts, rejects,
110 or redirects the request. This role lasts only for the
111 duration of that transaction. In other words, if a piece of
112 software responds to a request, it acts as a UAS for the
113 duration of that transaction. If it generates a request
114 later, it assumes the role of a user agent client for the
115 processing of that transaction.
117 Proxy, Proxy Server: An intermediary entity that acts as both
118 a server and a client for the purpose of making requests on
119 behalf of other clients. A proxy server primarily plays the
120 role of routing, which means its job is to ensure that a
121 request is sent to another entity 'closer' to the targeted
122 user. Proxies are also useful for enforcing policy. A proxy
123 interprets and, if necessary, rewrites specific parts of a
124 request message before forwarding it.
126 Redirect Server: A redirect server is a user agent server that
127 generates 3xx responses to requests it receives, directing the
128 client to contact an alternate set of URIs.
130 Registrar: A registrar is a server that accepts REGISTER
131 requests and places the information it receives in those
132 requests into the location service for the domain it handles."
134 "RFC 3261, Section 6"
143 SipTCOptionTagHeaders ::= TEXTUAL-CONVENTION
146 "This convention defines the header fields that use the option
150 tags per Section 19.2 of RFC 3261. These tags are used in
151 Require (Section 20.32), Proxy-Require (Section 20.29),
152 Supported (Section 20.37), and Unsupported (Section 20.40)
155 "RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40"
157 require(0), -- Require header
158 proxyRequire(1), -- Proxy-Require header
159 supported(2), -- Supported header
160 unsupported(3) -- Unsupported header
163 SipTCMethodName ::= TEXTUAL-CONVENTION
166 "This TEXTUAL-CONVENTION is a string that uniquely identifies a
167 SIP method. The scope of uniqueness is the context of all
170 Experimental support of extension methods is acceptable and
171 expected. Extension methods are those defined in
172 officially sanctioned by IANA.
174 To support experimental extension methods, any object using
175 this TEXTUAL-CONVENTION as syntax MAY return/accept a method
176 identifier value other than those sanctioned by IANA. That
177 system MUST ensure no collisions with officially assigned
180 "RFC 3261, Section 27.4"
181 SYNTAX OCTET STRING (SIZE (1..100))