RFC4083 - Input 3rd-Generation Partnership Project (3GPP) Release 5 Requirements on the Session Initiation Protocol (SIP)

   The DHCPv6 option for SIP servers in RFC 3319 [19] seems to fulfill
   the requirement.

   In addition to the above-expressed requirement, the 3GPP access
   network may provide the SIP outbound proxy address during access
   network bearer establishment.  This is considered a less general
   mechanism, though.

4.3.  Registration

   The home network must maintain one or more SIP registrars.  The SIP
   registrar authenticates the user and registers the IP address where
   the user can be located.

   Once the terminal is switched on, the mobile device UA reads its
   configuration data.  This data may be stored in a SIM card or in any
   other memory device.  The configuration data contains an
   identification of the home network.  The device finds the SIP
   registrar address from the home network domain name.  The terminal
   sends the registration through the SIP outbound proxy.

   In order to support the search of the registrar, the home network
   contains one or more SIP servers that may be configured in DNS with
   the NAPTR/SRV record of SIP.  These are the home network edge
   proxies.  Their mission is to serve as the first points of contact in
   the home network, and to decide (with the help of location servers)
   which SIP registrar server to assign to a particular user.

   The procedures specified in RFC 3263 [10] applied to a REGISTER
   message seem to be sufficient to meet this requirement.

4.3.1.  Registration Required

   A user must register to the IMS before he/she can receive any
   invitation to any sessions.  In addition, it is desirable for the
   user to register before initiating any sessions.  The following
   factors contribute to the rationale behind this:

   1.  The SIP serving proxy in the home network needs to know when and
       from which terminal the user is available, in order to route
       received SIP requests for sessions and services.

   2.  The user can be pre-authenticated early so that authentication

上一页 [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31] [32] [33] [34] [35] [36] [37] [38] [39] [40] 下一页

复制本页网址和标题，发送给你QQ/Msn的好友一起分享

上一篇:RFC4090 - Fast Reroute Extensions to RSVP-TE for LSP Tunnels

下一篇:RFC4078 - The TV-Anytime Content Reference Identifier (CRID)