| < draft-song-pppext-sip-support-01.txt | draft-song-pppext-sip-support-02.txt > | |||
|---|---|---|---|---|
| JUNHYUK SONG | JUNHYUK SONG | |||
| INTERNET DRAFT SAMSUNG ELECTRONICS | INTERNET DRAFT SAMSUNG ELECTRONICS | |||
| April 2003 | April 2003 | |||
| SIP server IPCP configuration option for PPP | SIP server configuration option for PPP | |||
| draft-song-pppext-sip-support-01.txt | draft-song-pppext-sip-support-02.txt | |||
| Status of This Memo | Status of This Memo | |||
| Distribution of this memo is unlimited. | Distribution of this memo is unlimited. | |||
| This document is an Internet-Draft and is in full conformance with | This document is an Internet-Draft and is in full conformance with | |||
| all provisions of Section 10 of RFC2026. Internet-Drafts are working | all provisions of Section 10 of RFC2026. Internet-Drafts are working | |||
| documents of the Internet Engineering Task Force (IETF), its areas, | documents of the Internet Engineering Task Force (IETF), its areas, | |||
| and its working groups. Note that other groups may also distribute | and its working groups. Note that other groups may also distribute | |||
| working documents as Internet-Drafts. | working documents as Internet-Drafts. | |||
| skipping to change at page 2, line 8 ¶ | skipping to change at page 2, line 8 ¶ | |||
| This document defines a new configuration option for the PPP IPCP | This document defines a new configuration option for the PPP IPCP | |||
| (PPP Internet Protocol Control Protocol), to return a list of the | (PPP Internet Protocol Control Protocol), to return a list of the | |||
| IPv4 addresses of SIP proxy servers. This option provides one | IPv4 addresses of SIP proxy servers. This option provides one | |||
| mechanism that a system may use to locate a SIP proxy server. | mechanism that a system may use to locate a SIP proxy server. | |||
| This approach is applicable for a system that is using PPP for the | This approach is applicable for a system that is using PPP for the | |||
| link layer protocol and IP address allocation. | link layer protocol and IP address allocation. | |||
| 1. Introduction | 1. Introduction | |||
| The SIP (Session Initiation Protocol)[3] is a signaling protocol | The SIP (Session Initiation Protocol)[3] is a signaling protocol | |||
| used for the session invitation, modification and termination. | used for the session invitation, modification, and termination. | |||
| The UAC(User Agent Client) sends a request to the UAS(User Agent | The UAC (User Agent Client) sends a request to the UAS (User Agent | |||
| Server). However, the request message (INVITE) is not directly sent | Server). However, the request message (INVITE) is not directly sent | |||
| to the callee UAS, it rather go through proxy servers, and possibly | to the callee UAS, it rather goes through proxy servers and possibly | |||
| redirect servers. This draft is specifying one mechansim that a | redirect servers. This draft specifyies one mechansim that a | |||
| system may use to locate a SIP procy server. | system may use to locate a SIP proxy server. | |||
| This draft is specifying a IPCP option that allows SIP clients to | This draft specifies an IPCP (PPP Internet Protocol Control | |||
| locate a list of SIP proxy servers that is to be used for all SIP | Protocol) option that allows SIP clients to locate a list of SIP | |||
| requests. This approach is applicable to the system utilizing PPP | proxy servers that is to be used for all SIP requests. This approach | |||
| for the link layer protocol and IP address allocation | is applicable to a system utilizing PPP for its link layer | |||
| (ex. 3GPP2 Packet Data System) | protocol and IP address allocation (ex. 3GPP2 Packet Data System) | |||
| Note : the format and behavior of these options are quoted from | Note: the text defining the format and behavior of these options is | |||
| RFC1877 [2] for the sake of consistent implementation of PPP. | quoted from RFC1877 [2], to ensure a consistent implementation. | |||
| 2. Configuration Options | 2. Configuration Options | |||
| The Configuration Option format and basic options are defined by | The IPCP Configuration Option format and the basic options are | |||
| IPCP configuration option [4]. | defined in RFC 1332 [4]. This document defines the two new | |||
| options: Primary SIP Server Address and Secondary SIP Server | ||||
| This document concerns the following values: | Address. | |||
| [?] Primary SIP Server Address | ||||
| [?+1] Secondary SIP Server Address | ||||
| 2.1. Primary SIP server Address Option | 2.1. Primary SIP Server Address Option | |||
| Description | Description | |||
| This Configuration Option defines a method for negotiating with | This Configuration Option is used for negotiating with the remote | |||
| the remote peer the address of the primary SIP server Address | peer the address of the primary SIP server Address to be used on | |||
| to be used on the local end of the link. | the local end of the link. | |||
| By default, no primary SIP server address is provided. | ||||
| A summary of the Primary SIP Address Configuration Option format is | A summary of the Primary SIP Address Configuration Option format is | |||
| shown below. The fields are transmitted from left to right. | shown below. The fields are transmitted from left to right. | |||
| 0 1 2 3 | 0 1 2 3 | |||
| 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Type | Length | Primary-SIP-Server Address | | Type | Length | Primary-SIP-Server Address | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Primary-SIP-Server Address(cont)| | Primary-SIP-Server Address(cont)| | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Type | Type | |||
| ? (Primary SIP Proxy server) | ? [To be assigned by IANA] Primary SIP Server Address Option | |||
| Length | Length | |||
| 6 | 6 | |||
| Primary-SIP-Address | Primary-SIP-Server-Address | |||
| The four octet Primary-SIP-Server Address is the address of the | The four octet Primary-SIP-Server Address is the address of the | |||
| primary proxy SIP server to be used by the local peer. | primary proxy SIP server to be used by the local peer. Setting | |||
| If all four octets are set to zero, it indicates an explicit | these four octets to zero requests that the peer provide the | |||
| request that the peer provide the address information in a | address information in a Config-Nak packet. | |||
| Config-Nak packet. | ||||
| Default | Default | |||
| No address is provided. | No primary server address is provided. | |||
| 1.3. Secondary SIP Server Address | 1.3. Secondary SIP Server Address Option | |||
| Description | Description | |||
| This Configuration Option defines a method for negotiating with | This Configuration Option is used for negotiating with | |||
| the remote peer the address of the secondary SIP server Address | the remote peer the address of the secondary SIP server Address | |||
| to be used on the local end of the link. | to be used on the local end of the link. | |||
| By default, no secondary SIP address is provided. | ||||
| A summary of the Secondary SIP Address Configuration Option format is | A summary of the Secondary SIP Address Configuration Option format is | |||
| shown below. The fields are transmitted from left to right. | shown below. The fields are transmitted from left to right. | |||
| 0 1 2 3 | 0 1 2 3 | |||
| 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| | Type | Length |Secondary-SIP-Server Address | | Type | Length |Secondary-SIP-Server Address | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Secondary-SIP-Server Addr (cont)| | Secondary-SIP-Server Addr (cont)| | |||
| +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | |||
| Type | Type | |||
| ?+1 (Secondary SIP Proxy server) | ?+1 [To be assigned by IANA] Secondary SIP Server Address Option | |||
| Length | Length | |||
| 6 | 6 | |||
| Secondary-SIP-Address | Secondary-SIP-Server-Address | |||
| The four octet Secondary-SIP-Server Address is the address of the | The four octet Secondary-SIP-Server Address is the address of the | |||
| secondary SIP server to be used by the local peer. If all four | secondary SIP server to be used by the local peer. Setting four | |||
| octets are set to zero, it indicates an explicit request that the | octets are set to zero requests that the peer provide the address | |||
| peer provide the address information in a Config-Nak packet. | information in a Config-Nak packet. | |||
| Default | Default | |||
| No address is provided. | By default, no secondary SIP address is provided. | |||
| 3. IANA Considerations | 3. IANA Considerations | |||
| Requires IPCP option number assignment | ||||
| Requires IPCP option number assignment | ||||
| 4. Acknowledgements | 4. Acknowledgements | |||
| A major portion of the text in this memo was quoted from RFC 1877. | A major portion of the text in this memo was quoted from RFC 1877. | |||
| References | References | |||
| [1] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", STD 51, | [1] Simpson, W., Editor, "The Point-to-Point Protocol (PPP)", STD 51, | |||
| RFC 1661, Daydreamer, July 1994. | RFC 1661, Daydreamer, July 1994. | |||
| [2] Steve Cobb, "PPP Internet Protocol Control Protocol Extensions for | [2] Steve Cobb, "PPP Internet Protocol Control Protocol Extensions for | |||
| Name Server Addresses" RFC 1877, Microsoft, | Name Server Addresses" RFC 1877, Microsoft, | |||
| End of changes. 21 change blocks. | ||||
| 45 lines changed or deleted | 39 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||