1、 TIA-1137.110-2009 APPROVED: JUNE 1, 2009 REAFFIRMED: DECEMBER 6, 2013 TIA-1137.110 June 2009MIPv4 Specification in Converged Access Network Specification NOTICE TIA Engineering Standards and Publications are designed to serve the public interest through eliminating misunderstandings between manufac
2、turers and purchasers, facilitating interchangeability and improvement of products, and assisting the purchaser in selecting and obtaining with minimum delay the proper product for their particular need. The existence of such Standards and Publications shall not in any respect preclude any member or
3、 non-member of TIA from manufacturing or selling products not conforming to such Standards and Publications. Neither shall the existence of such Standards and Publications preclude their voluntary use by Non-TIA members, either domestically or internationally. Standards and Publications are adopted
4、by TIA in accordance with the American National Standards Institute (ANSI) patent policy. By such action, TIA does not assume any liability to any patent owner, nor does it assume any obligation whatever to parties adopting the Standard or Publication. This Standard does not purport to address all s
5、afety problems associated with its use or all applicable regulatory requirements. It is the responsibility of the user of this Standard to establish appropriate safety and health practices and to determine the applicability of regulatory limitations before its use. (From Project No. 3-0291.110-RF1,
6、formulated under the cognizance of the TIA TR-45 Mobile (b) there is no assurance that the Document will be approved by any Committee of TIA or any other body in its present or any other form; (c) the Document may be amended, modified or changed in the standards development or any editing process. T
7、he use or practice of contents of this Document may involve the use of intellectual property rights (“IPR”), including pending or issued patents, or copyrights, owned by one or more parties. TIA makes no search or investigation for IPR. When IPR consisting of patents and published pending patent app
8、lications are claimed and called to TIAs attention, a statement from the holder thereof is requested, all in accordance with the Manual. TIA takes no position with reference to, and disclaims any obligation to investigate or inquire into, the scope or validity of any claims of IPR. TIA will neither
9、be a party to discussions of any licensing terms or conditions, which are instead left to the parties involved, nor will TIA opine or judge whether proposed licensing terms or conditions are reasonable or non-discriminatory. TIA does not warrant or represent that procedures or practices suggested or
10、 provided in the Manual have been complied with as respects the Document or its contents. If the Document contains one or more Normative References to a document published by another organization (“other SSO”) engaged in the formulation, development or publication of standards (whether designated as
11、 a standard, specification, recommendation or otherwise), whether such reference consists of mandatory, alternate or optional elements (as defined in the TIA Engineering Manual, 4thedition) then (i) TIA disclaims any duty or obligation to search or investigate the records of any other SSO for IPR or
12、 letters of assurance relating to any such Normative Reference; (ii) TIAs policy of encouragement of voluntary disclosure (see Engineering Manual Section 6.5.1) of Essential Patent(s) and published pending patent applications shall apply; and (iii) Information as to claims of IPR in the records or p
13、ublications of the other SSO shall not constitute identification to TIA of a claim of Essential Patent(s) or published pending patent applications. TIA does not enforce or monitor compliance with the contents of the Document. TIA does not certify, inspect, test or otherwise investigate products, des
14、igns or services or any claims of compliance with the contents of the Document. ALL WARRANTIES, EXPRESS OR IMPLIED, ARE DISCLAIMED, INCLUDING WITHOUT LIMITATION, ANY AND ALL WARRANTIES CONCERNING THE ACCURACY OF THE CONTENTS, ITS FITNESS OR APPROPRIATENESS FOR A PARTICULAR PURPOSE OR USE, ITS MERCHA
15、NTABILITY AND ITS NONINFRINGEMENT OF ANY THIRD PARTYS INTELLECTUAL PROPERTY RIGHTS. TIA EXPRESSLY DISCLAIMS ANY AND ALL RESPONSIBILITIES FOR THE ACCURACY OF THE CONTENTS AND MAKES NO REPRESENTATIONS OR WARRANTIES REGARDING THE CONTENTS COMPLIANCE WITH ANY APPLICABLE STATUTE, RULE OR REGULATION, OR T
16、HE SAFETY OR HEALTH EFFECTS OF THE CONTENTS OR ANY PRODUCT OR SERVICE REFERRED TO IN THE DOCUMENT OR PRODUCED OR RENDERED TO COMPLY WITH THE CONTENTS. TIA SHALL NOT BE LIABLE FOR ANY AND ALL DAMAGES, DIRECT OR INDIRECT, ARISING FROM OR RELATING TO ANY USE OF THE CONTENTS CONTAINED HEREIN, INCLUDING
17、WITHOUT LIMITATION ANY AND ALL INDIRECT, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES (INCLUDING DAMAGES FOR LOSS OF BUSINESS, LOSS OF PROFITS, LITIGATION, OR THE LIKE), WHETHER BASED UPON BREACH OF CONTRACT, BREACH OF WARRANTY, TORT (INCLUDING NEGLIGENCE), PRODUCT LIABILITY OR OTHERWISE, EVEN IF AD
18、VISED OF THE POSSIBILITY OF SUCH DAMAGES. THE FOREGOING NEGATION OF DAMAGES IS A FUNDAMENTAL ELEMENT OF THE USE OF THE CONTENTS HEREOF, AND THESE CONTENTS WOULD NOT BE PUBLISHED BY TIA WITHOUT SUCH LIMITATIONS. X.S0054-110-0 v2.0 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 2
19、7 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 i Contents MIPv4 Specification in Converged Access Network CONTENTS 1 Introduction1 1.1 SCOPE.1 2 References2 2.1 Normative References2 2.2 Informative References2 3 Client Mobile IPv4 Operation4 3.1
20、 Protocol Stack4 3.2 CMIP4 Key Management 4 3.3 AT Requirements.5 3.3.1 Agent Discovery5 3.3.2 CMIP4 Registration.5 3.3.3 Reverse Tunneling.6 3.3.4 Termination .6 3.4 AGW Requirements.6 3.4.1 Agent Advertisement.6 3.4.2 CMIP4 Registration.7 3.4.3 FA-HA Security.8 3.4.4 Reverse Tunneling.9 3.4.5 Ingr
21、ess Address Filtering.10 3.4.6 Overlapping Private Address Support .10 3.4.7 Registration Revocation 10 3.5 HA Requirements 11 3.5.1 CMIP4 Registration.11 3.5.2 FA-HA Security.12 3.5.3 DHCPv4 Support.13 3.5.4 Registration Revocation 13 3.6 AAA Requirements13 3.6.1 CMIP4 Registration.13 3.6.2 FA-HA S
22、ecurity.14 3.6.3 Reverse Tunneling.15 4 Call Flows 16 4.1 Mobile IPv4 Addressing with RADIUS 16 X.S0054-110-0 v2.0 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 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 List of Figure
23、s ii LIST OF FIGURES Figure 1 Protocol Reference Model for CMIP4 Control . 4 Figure 2 Protocol Reference Model for CMIP4 User Data . 4 Figure 3 Mobile IPv4 Addressing with RADIUS 16 X.S0054-110-0 v2.0 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
24、37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 iii List of Tables LIST OF TABLES Table 1. Additional RADIUS Attributes between AGW and AAA during Access Authentication and Authorization for Supporting CMIP4 Registration8 Table 2. RADIUS Attributes between AGW and AAA for Sup
25、porting FA-HA MSA Distribution .9 Table 3. RADIUS Attributes between HA and AAA for Supporting CMIP4 Registration .12 Table 4. RADIUS Attributes between HA and AAA for Supporting FA-HA MSA distribution 12 X.S0054-110-0 v2.0 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 2
26、9 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 Revision History iv REVISION HISTORY Revision Date Remarks 0 v1.0 December 2007 Initial release 0 v2.0 August 2008 Bug fix release for the initial release X.S0054-110-0 v2.0 1 2 3 4 5 6 7 8 9 10 11 12 13 1
27、4 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 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 v Foreword FOREWORD (This foreword is not part of this Standard.) This document was prepared by 3GPP2 TSG-X. This document is an addendum of X.S0054-110-0 v1.0.
28、 This document is part of a multi-part document consisting of multiple parts that together describes Converged Access Network. This document is subject to change following formal approval. Should this document be modified, it will be re-released with a change of release date and an identifying chang
29、e in version number as follows: X.S0054-110-X version n.0 where: X an uppercase numerical or alphabetic character 0, A, B, C, that represents the revision level. n a numeric string 1, 2, 3, that indicates an point release level. This document uses the following conventions: “Shall” and “shall not” i
30、dentify requirements to be followed strictly to conform to this document and from which no deviation is permitted. “Should” and “should not” indicate that one of several possibilities is recommended as particularly suitable, without mentioning or excluding others, that a certain course of action is
31、preferred but not necessarily required, or that (in the negative form) a certain possibility or course of action is discouraged but not prohibited. “May” and “need not” indicate a course of action permissible within the limits of the document. “Can” and “cannot” are used for statements of possibilit
32、y and capability, whether material, physical or causal. .X.S0054-110-0 v2.0 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 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 1.1 SCOPE 1 1 Introduction 1 Introduction This docume
33、nt defines the stage-2 and stage-3 requirements for client based Mobile IPv4 access to the Converged Access Network supporting Ultra Mobile BroadbandTM1radio access. 1.1 SCOPE This document is part of a multi-part document that together describes IP network operation for the Converged Access Network
34、. The scope of this document covers client based Mobile IPv4 aspects in support of the UMB wireless access. 1Ultra Mobile BroadbandTMand (UMBTM) are trade and service marks owned by the CDMA Development Group (CDG). X.S0054-110-0 v2.0 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
35、 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 2 References 2 2.1 Normative References 2 References 2.1 Normative References This section provides references to other specifications and standards that are necessary to implement this document
36、. 1 IETF: RFC3344, Parkins, “IP Mobility Support for IPv4”, August 2002. 2 IETF: RFC2794, Calhoun, et.al., “Mobile IP Network Access Identifier Extension for IPv4”, March 2000. 3 IETF: RFC3012, Parkins, et.al., “Mobile IPv4 Challenge/Response Extensions”, November 2000. 4 IETF: RFC3543, Glass, et.al
37、., “Registration Revocation in Mobile IPv4”, August 2003. 5 IETF: RFC3024, Montenegro, “Reverse Tunneling for Mobile IP, revised”, January 2001. 6 3GPP2: X.S0054-100-0 v2.0, “Basic IP Service for Converged Access Network Specification”, August 2008. 7 3GPP2: X.S0011-002-D, “cdma2000 Wireless IP Netw
38、ork Standard: Simple IP and Mobile IP Access Service”, March 2006. 8 IETF: RFC1918, Rekhter, et.al., “Address Allocation for Private Internets”, February 1996. 9 IETF: RFC2131, Dorms, “Dynamic Host Configuration Protocol”, March 1997. 10 IETF: RFC3046, Patrik, “DHCP Relay Agent Information Option”,
39、January 2001. 11 3GPP2: S.S0078-B, “Common Security Algorithms”, TBDFebruary 2008. 2.2 Informative References This section provides references to other documents that may be useful for the reader of this document. 3GPP2: X.S0054-000-0 v2.0, “CAN Wireless IP Network Overview and List of Parts”, Augus
40、t 2008. 3GPP2: X.S0054-102-0 v2.0, “Multiple-Authentication and Legacy Authentication Support for Converged Access Network”, August 2008. 3GPP2: X.S0054-210-0 v1.0, “CMIP based Inter-AGW Handoff”, December 2007. 3GPP2: X.S0054-220-0 v2.0, “Network PMIP Support”, August 2008. 3GPP2: X.S0054-300-0 v1.
41、0, “QoS Support for Converged Access Network Specification”, December 2007. X.S0054-110-0 v2.0 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 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 2.2 Informative References 3 2 Ref
42、erences 3GPP2: X.S0054-400-0 v1.0, “Converged Access Network Accounting Specification”, December 2007. 3GPP2: X.S0054-910-0 v2.0, “CAN Data Dictionary”, August 2008. X.S0054-110-0 v2.0 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 41 4
43、2 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 3 Client Mobile IPv4 Operation 4 3.1 Protocol Stack 3 Client Mobile IPv4 Operation This section describes the requirements and procedures for CMIP4. 3.1 Protocol Stack Figure 1 shows the protocol reference model for CMIP4 control data between t
44、he AT and the HA. Figure 2 shows the protocol reference model for CMIP4 user data between the AT and CN. Figure 1 Protocol Reference Model for CMIP4 Control Figure 2 Protocol Reference Model for CMIP4 User Data 3.2 CMIP4 Key Management The AT may use static MN-HA key and static MN-AAA key. If the st
45、atic MH-HA key and MN-AAA key are used, the procedures in 7 shall be used. If the AT uses dynamic MN-HA key and dynamic MN-AAA key, the requirements described below in this section are applicable. Upon successful EAP access authentication, the EMSK is available at AT and the HAAA. From the EMSK, the
46、 CMIP4-MN-RK shall be computed as follows: X.S0054-110-0 v2.0 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 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 3.3 AT Requirements 5 3 Client Mobile IPv4 Operation CMIP4-MN-RK ke
47、y = HMAC-SHA-25611 (EMSK, “CMIP4-MN-RK3gpp2”) From the CMIP4-MN-RK, the MN-AAA key and its associated MN-AAA-SPI shall be derived as follows: MN-AAA key = HMAC-SHA-256 (CMIP4-MN-RK, “MN-AAA3gpp2”) MN-AAA-SPI = HMAC-SHA-256 (MN-AAA key, “3GPP2-MN-AAA-SPI3gpp2”) The MN-AAA-SPI indicates the specific s
48、ecurity association between the AT and HAAA and algorithm used in computation of the MN-AAA Authentication Extension. If the value of this computed MN-AAA-SPI is equal to or smaller than 255, then an integer value of 256 shall be added to the computed value. If the MN-AAA-SPI collides with another S
49、PI value already allocated for the AT, then the SPI value shall be monotonically incremented until the SPI value has no collision for that AT. From the CMIP4-MN-RK, the MN-HA key and its associated MN-HA-SPI shall be derived as follows: MN-HA Key = HMAC-SHA-256 (CMIP4-MN-RK, “MN-HA3gpp2”, HA IP Address) MN-HA-SPI = HMAC-SHA-256 (MN-HA key, “3GPP2-MN-HA-SPI3gpp2”) The MN-HA-SPI indicates the specific security association between the AT and HA and algorithm used in computation of the MN-HA Authentication Extension. If the value of this
