# python version 1.0 DO NOT EDIT
#
# This python file has been generated by smidump version 0.5.0:
#
# smidump -f python SIP-TC-MIB
FILENAME = "./libsmi-0.5.0/mibs/ietf/SIP-TC-MIB"
MIB = {
"moduleName" : "SIP-TC-MIB",
"SIP-TC-MIB" : {
"nodetype" : "module",
"language" : "SMIv2",
"organization" :
"""IETF Session Initiation Protocol Working Group""",
"contact" :
"""SIP WG email: sip@ietf.org
Co-editor Kevin Lingle
Cisco Systems, Inc.
postal: 7025 Kit Creek Road
P.O. Box 14987
Research Triangle Park, NC 27709
USA
email: klingle@cisco.com
phone: +1 919 476 2029
Co-editor Joon Maeng
email: jmaeng@austin.rr.com
Co-editor Jean-Francois Mule
CableLabs
postal: 858 Coal Creek Circle
Louisville, CO 80027
USA
email: jf.mule@cablelabs.com
phone: +1 303 661 9100
Co-editor Dave Walker
email: drwalker@rogers.com""",
"description" :
"""Session Initiation Protocol (SIP) MIB TEXTUAL-CONVENTION
module used by other SIP-related MIB Modules.
Copyright (C) The IETF Trust (2007). This version of
this MIB module is part of RFC 4780; see the RFC itself for
full legal notices.""",
"revisions" : (
{
"date" : "2007-04-20 00:00",
"description" :
"""Initial version of the IETF SIP-TC-MIB module. This version
published as part of RFC 4780.""",
},
),
"identity node" : "sipTC",
},
"imports" : (
{"module" : "SNMPv2-SMI", "name" : "MODULE-IDENTITY"},
{"module" : "SNMPv2-SMI", "name" : "mib-2"},
{"module" : "SNMPv2-TC", "name" : "TEXTUAL-CONVENTION"},
),
"typedefs" : {
"SipTCTransportProtocol" : {
"basetype" : "Bits",
"status" : "current",
"other" : {
"nodetype" : "namednumber",
"number" : "0"
},
"udp" : {
"nodetype" : "namednumber",
"number" : "1"
},
"tcp" : {
"nodetype" : "namednumber",
"number" : "2"
},
"sctp" : {
"nodetype" : "namednumber",
"number" : "3"
},
"tlsTcp" : {
"nodetype" : "namednumber",
"number" : "4"
},
"tlsSctp" : {
"nodetype" : "namednumber",
"number" : "5"
},
"description" :
"""This convention is a bit map. Each bit represents a transport
protocol. If a bit has value 1, then that selected transport
protocol is in some way dependent on the context of the object
using this convention. If a bit has value 0, then that
transport protocol is not selected. Combinations of bits can
be set when multiple transport protocols are selected.
bit 0: a protocol other than those defined here
bit 1: User Datagram Protocol
bit 2: Transmission Control Protocol
bit 3: Stream Control Transmission Protocol
bit 4: Transport Layer Security Protocol over TCP
bit 5: Transport Layer Security Protocol over SCTP""",
"reference" :
"""RFC 3261, Section 18 and RFC 4168""",
},
"SipTCEntityRole" : {
"basetype" : "Bits",
"status" : "current",
"other" : {
"nodetype" : "namednumber",
"number" : "0"
},
"userAgent" : {
"nodetype" : "namednumber",
"number" : "1"
},
"proxyServer" : {
"nodetype" : "namednumber",
"number" : "2"
},
"redirectServer" : {
"nodetype" : "namednumber",
"number" : "3"
},
"registrarServer" : {
"nodetype" : "namednumber",
"number" : "4"
},
"description" :
"""This convention defines the role of a SIP entity. Examples of
SIP entities are proxies, user agents, redirect servers,
registrars, or combinations of the above.
User Agent (UA): A logical entity that can act as both a user
agent client and user agent server.
User Agent Client (UAC): A logical entity that creates a new
request, and then uses the client transaction state machinery
to send it. The role of UAC lasts only for the duration of
that transaction. In other words, if a piece of software
initiates a request, it acts as a UAC for the duration of that
transaction. If it receives a request later, it assumes the
role of a user agent server for the processing of that
transaction.
User Agent Server (UAS): A logical entity that generates a
response to a SIP request. The response accepts, rejects,
or redirects the request. This role lasts only for the
duration of that transaction. In other words, if a piece of
software responds to a request, it acts as a UAS for the
duration of that transaction. If it generates a request
later, it assumes the role of a user agent client for the
processing of that transaction.
Proxy, Proxy Server: An intermediary entity that acts as both
a server and a client for the purpose of making requests on
behalf of other clients. A proxy server primarily plays the
role of routing, which means its job is to ensure that a
request is sent to another entity 'closer' to the targeted
user. Proxies are also useful for enforcing policy. A proxy
interprets and, if necessary, rewrites specific parts of a
request message before forwarding it.
Redirect Server: A redirect server is a user agent server that
generates 3xx responses to requests it receives, directing the
client to contact an alternate set of URIs.
Registrar: A registrar is a server that accepts REGISTER
requests and places the information it receives in those
requests into the location service for the domain it handles.""",
"reference" :
"""RFC 3261, Section 6""",
},
"SipTCOptionTagHeaders" : {
"basetype" : "Bits",
"status" : "current",
"require" : {
"nodetype" : "namednumber",
"number" : "0"
},
"proxyRequire" : {
"nodetype" : "namednumber",
"number" : "1"
},
"supported" : {
"nodetype" : "namednumber",
"number" : "2"
},
"unsupported" : {
"nodetype" : "namednumber",
"number" : "3"
},
"description" :
"""This convention defines the header fields that use the option
tags per Section 19.2 of RFC 3261. These tags are used in
Require (Section 20.32), Proxy-Require (Section 20.29),
Supported (Section 20.37), and Unsupported (Section 20.40)
header fields.""",
"reference" :
"""RFC 3261, Sections 19.2, 20.32, 20.29, 20.37, and 20.40""",
},
"SipTCMethodName" : {
"basetype" : "OctetString",
"status" : "current",
"ranges" : [
{
"min" : "1",
"max" : "100"
},
],
"range" : {
"min" : "1",
"max" : "100"
},
"description" :
"""This TEXTUAL-CONVENTION is a string that uniquely identifies a
SIP method. The scope of uniqueness is the context of all
defined SIP methods.
Experimental support of extension methods is acceptable and
expected. Extension methods are those defined in
officially sanctioned by IANA.
To support experimental extension methods, any object using
this TEXTUAL-CONVENTION as syntax MAY return/accept a method
identifier value other than those sanctioned by IANA. That
system MUST ensure no collisions with officially assigned
method names.""",
"reference" :
"""RFC 3261, Section 27.4""",
},
}, # typedefs
"nodes" : {
"sipTC" : {
"nodetype" : "node",
"moduleName" : "SIP-TC-MIB",
"oid" : "1.3.6.1.2.1.148",
"status" : "current",
}, # node
}, # nodes
}