Management Information Base for the Session Initiation Protocol (SIP)
draft-ietf-sip-mib-12
Yes
No Objection
Note: This ballot was opened for revision 12 and is now closed.
Lars Eggert No Objection
(Cullen Jennings; former steering group member) Yes
(Dan Romascanu; former steering group member) (was Discuss) Yes
(Brian Carpenter; former steering group member) No Objection
I'm curious. If this is used to manage a session end to end, what is going to
happen to the following items when there is a NAT on the path?
sipUACfgServerAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reflects the address of a SIP server
this user agent will use to proxy/redirect calls."
sipServerHostAddr OBJECT-TYPE
SYNTAX InetAddress
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This is the host portion of a SIP URI that is
assigned to the SIP server. It MAY contain a fully
qualified domain name, or an IP address. The length
of the value will depend on the type of address
specified.
sipServerHostAddrType formalizes the type of address
given by this object. It is the user's
responsibility to maintain consistency between this
object and the type specified by
sipServerHostAddrType."
(David Kessens; former steering group member) No Objection
(Jari Arkko; former steering group member) No Objection
(Jon Peterson; former steering group member) No Objection
(Lisa Dusseault; former steering group member) No Objection
(Mark Townsley; former steering group member) No Objection
(Ross Callon; former steering group member) No Objection
(Russ Housley; former steering group member) No Objection
(Sam Hartman; former steering group member) No Objection
(Ted Hardie; former steering group member) No Objection