Management Information Base for the Session Initiation Protocol (SIP)
RFC 4780

Note: This ballot was opened for revision 12 and is now closed.

(Cullen Jennings) Yes

(Dan Romascanu) (was Discuss) Yes

(Jari Arkko) No Objection

(Ross Callon) No Objection

(Brian Carpenter) No Objection

Comment (2006-08-03 for -** No value found for 'p.get_dochistory.rev' **)
No email
send info
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."

(Lisa Dusseault) No Objection

(Lars Eggert) No Objection

(Ted Hardie) No Objection

(Sam Hartman) No Objection

(Russ Housley) No Objection

(David Kessens) No Objection

(Jon Peterson) No Objection

(Mark Townsley) No Objection