3 Title: DHCP and DNS Lookup for UMB-HRPD Handoff
6 Abstract: This contribution proposed a method to discover the IP address of the
7 HRPD AN that is used for pre-establish the HRPD session and PPP
8 session before the AT switches its active air-interface to HRPD.
12 Peerapol Tinnakornsrisuphap/Jun Wang
13 QUALCOMM Inc.
18 Date: November 05, 2007
20 Recommendation: Review and adopt it in X.P00xx-610.
Contributors grant a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable
material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in
Organizational Partner’s name any Organizational Partner’s standards publication even though it may include portions of the
contribution; and at the Organization Partner’s sole discretion to permit others to reproduce in whole or in part such contributions
or the resulting Organizational Partner’s standards publication. Contributors are also willing to grant licenses under such
contributor copyrights to third parties on reasonable, non-discriminatory terms and conditions for purpose of practicing an
Organizational Partner’s standard which incorporates this contribution.
This document has been prepared by the contributors to assist the development of specifications by 3GPP2. It is proposed to the
Committee as a basis for discussion and is not to be construed as a binding proposal on the contributors. Contributors specifically
reserve the right to amend or modify the material contained herein and nothing herein shall be construed as conferring or offering
licenses or rights with respect to any intellectual property of the contributors other than provided in the copyright statement
1 2. References
3 2.1 Normative References
4  IETF: RFC 2131, R. Droms, et al. ‘Dynamic Host Configuration Protocol’, March 1997.
5  IETF: RFC 2132, S. Alexander, et al. ‘DHCP Options and BOOTP Vendor Extensions’,
6 March 1997.
7  IETF: RFC 3315, R. Droms, Ed. et al. ‘Dynamic Host Configuration Protocol for IPv6
8 (DHCPv6)’, July 2003
9  IETF: RFC 3646, R. Droms, Ed. ‘DNS Configuration options for Dynamic Host
10 Configuration Protocol for IPv6 (DHCPv6)’, December 2003.
11  3GPP2: C.S0024
12  3GPP2: X.0054-100
15 2.2 Informative References
16 1. xxx
1 4. HRPD AN Discovery
2 During UMB-HRPD active handoff, the AT needs to discover the IP address of the HRPD AN that
3 is used to pre-establish the HRPD session and PPP session before the AT switches its active
4 air-interface to HRPD. The HRPD AN IP address discovery occurs in two steps. The first step
5 (section 4.1) is HRPD AN Domain Name Discovery where the AT discovers the domain name that
6 the AT will use in the formation of a FQDN when handoff is required. This step may occur as part
7 of IP address assignment of the AT during power-up. The next step (section 4.2) is the AT uses the
8 FQDN to perform DNS query for resolution of HRPD AN IP address. This step should occur when
9 the HRPD session establishment through the inter-technology tunnel is required.
10 4.1 HRPD AN Domain Name Discovery
11 This section defines requirements for the HRPD AN Domain Name Discovery. The AT should
12 discover the HRPD Operator Domain Name via DHCP using DHCP Pption or DHCPv6 Option.
13 Upon discovery of HRPD AN Domain Name, the AT shall use the discovered domain name for
14 HRPD AN IP address resolution (see section 4.2).
15 4.1.1 DHCPv4 Option
16 The AT uses the DHCPINFORM message to acquire HRPD AN domain name using DHCP
17 Option 15 (see ).
18 The DHCP server includes HRPD AN Domain Name in Domain Name Option in the DHCPACK
19 message to send HRPD AN Domain Name to the AT.
20 184.108.40.206 AT Requirements
21 See  for DHCP requirements on the AT.
22 The AT shall support DHCP Option 15 as specifred in  if the HRPD AN Domain Name
23 Discovery is used to discover HRPD domain name.
24 The AT shall use the DHCPINFORM message to acquire the domain name of the HRPD AN as per
26 220.127.116.11 DHCP Server Requirements
27 Upon receiving a DHCPINFORM message or a Relay message containing a DHCPINFORM
28 message, if the DHCP server is configured with the Domain Name information, the DHCP server
29 shall respond with DHCPACK which includes the Domain Name using DCHP Opton 15 as
30 defined in .
31 4.1.2 DHCPv6 Option
32 The AT uses Option-Request-Option in the INFORMATION-REQUEST message with option
33 code set for requesting Domain Search List Option (see  and ).
34 The DHCPv6 server includes Domain Search List Option in the REPLY message to send Domain
35 Name list to the AT.
1 18.104.22.168 AT Requirements
2 The AT shall support DHCPv6 Domain Search List Option as specifed in  if the HRPD AN
3 Domain Name Discovery is used to discover HRPD domain name.
4 See  for additional DHCPv6 requirements for the AT.
5 If the AT sends INFORMATION-REQUEST message to request Domain Name, the AT shall use
6 Option-Request-Option in the INFORMATION-REQUEST message with option-code set to 24
7 for requesting domain serch name list (see  and ).
8 22.214.171.124 DHCPv6 Server Requirements
9 See  for additional DHCPv6 server requirements.
10 Upon receiving an Information-Request message or a Relay-Forward message containing an
11 Information-Request message containing an Option-Request-Option indicating domain search list,
12 the DHCPv6 server shall include in a Reply the Domain Search List Option.
13 4.2 HRPD AN IP Address Resolution
14 The AT resolves the IP address of the HRPD AN for establishing inter-technology handoff tunnel
15 by performing a DNS query on the following FQDN.
16 The AT shall form the FQDN as follows for DNS query:
19 - <domain-name> is discovered via DHCP (section 4.1 and section 4.2)
20 - <HRPD-sectorID-MSB104> is the hex representation in ASCII of the 104 MSBs of
21 HRPD sectorID of the HRPD pilot provided to the AT via the HRPD air-interface (See
23 - <HRPD-sectorID-LSB24> is the hex representation in ASCII of the 24 LSBs of HRPD
24 sectorID of the HRPD pilot provided to the AT via the HRPD air-interface (See ).