rfc3141.txt

来自「RFC 的详细文档！」· 文本 代码 · 共 900 行 · 第 1/2 页


RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


3.2.4.  HA-FA Authentication

   To achieve a fast registration for the case of a mobile station with
   a Home Agent, the PDSN and HA may receive from the AAA mechanism a
   HA-FA key and SPI that is used to authenticate the PDSN and the HA to
   each other.

3.2.5.  Key Distribution

   These functions are primarily useful in a wireless environment in
   which handoffs may occur rapidly (implying a need for low latency),
   or where mobile devices have limited computing power.  To achieve
   these functions, AAA will be used to securely pass keys and SPIs
   between the serving network and target network in encrypted form.
   These keys are then used for the specific functions outlined in this
   document.

3.3.  IKE and AAA

   The use of IKE in the cdma2000 wireless architecture requires the use
   of certificates.  However, the AAA servers may be able to distribute
   a pre- shared key to the Mobile IP Agents for use during Phase 1
   ISAKMP exchanges.  This may lessen the need for on-line revocation
   checks.

3.4.  Interoperability with RADIUS

   Users with a home AAA server based on RADIUS may desire to roam into
   a wireless carrier network that uses "new" AAA servers based on the
   requirements in this document, and vice verse.  The AAA protocol
   should be designed in a way so as to make conversions to and from
   RADIUS messages straight forward.  This will allow for the
   development of gateway processes to aid in interoperability.  Note:
   The features of the new AAA protocols which are beyond the feature
   set of the RADIUS protocol will not be available for users while on
   home or serving networks based on RADIUS.

4.  References

   [RFC2119]   Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119, March 1997.

5.  Security Considerations

   This document is very much about security.  These requirements do not
   require the serving and home networks to not be in the same domain
   nor must they have a direct relationship.  The serving network
   requires authorization from the home network so that the serving



Hiller, et al.               Informational                      [Page 9]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


   network obtains proof it will get paid for services rendered to the
   mobile.  This implies the home network must authenticate the user.
   AAA functions must be performed in a secure manner.  The requirements
   contained in section 2 outline the security required.

   Mobile IP supports authentication mechanisms outside IP Security.
   These mechanism may be enhanced in a cellular wireless environment by
   allowing a home AAA server to distribute keys to the serving network.
   Additionally, the home AAA server may be able to send a pre-shared
   key to be used in Phase 1 ISAKMP security association establishment
   between FA and HA.  These keys would sent in encrypted form from the
   home network to the serving network.  As supported in the
   requirements contained in section 2, the encryption could be handled
   via public cryptography and certificates.

6.  IANA Considerations

   This document does not create any new number spaces for IANA
   administration.

7.  Acknowledgements

   The authors are active members of the TIA TR45.6 committee.

8.  Authors' Addresses

   Pat R. Calhoun
   Network and Security Research Center, Sun Labs
   Sun Microsystems, Inc.
   15 Network Circle
   Menlo Park, CA 94025
   USA

   Phone: [phone]
   EMail: [e-mail]


   Ed Campbell
   CommWorks Corporation, A 3Com Company
   3800 Golf Road
   Rolling Meadows, IL 60008

   Phone: [phone]
   E-Mail: [e-mail]







Hiller, et al.               Informational                     [Page 10]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


   Gopal Dommety
   Cisco Systems, Inc.
   170 West Tasman Drive
   San Jose, CA 95134
   USA

   EMail: [e-mail]


   Tom Hiller
   Rm 2F-218
   263 Shuman Dr.
   Lucent Technologies
   Naperville, IL
   USA

   Phone: [phone]
   EMail: [e-mail]


   Raymond T. Hsu
   Qualcomm Inc.
   6455 Lusk Blvd.
   San Diego, CA 92121
   USA

   Phone: [phone]
   EMail: [e-mail]


   Mark A. Lipford
   Sprint PCS
   15405 College Blvd.
   Lenexa, KS  66219

   Phone:  [phone]
   EMail: [e-mail]


   Serge Manning
   Award Solutions, Inc.
   800 E. Campbell Rd., Suite 120
   Richardson, TX  75081

   Phone: [phone] x350
   EMail: [e-mail]





Hiller, et al.               Informational                     [Page 11]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


   Peter J. McCann
   Lucent Technologies
   Rm 2Z-305
   263 Shuman Blvd
   Naperville, IL 60566
   USA

   Phone: [phone]
   EMail: [e-mail]


   Mark Munson
   1371 Winding Branch Circle
   Atlanta, Georgia 30338
   USA

   Phone: [phone]
   EMail: [e-mail]


   Haeng Koo
   Samsung Telecommunications America, Inc.
   1130 E. Arapaho Road
   Richardson, TX 75081
   USA

   Phone: [phone]
   EMail: [e-mail]


   Pat Walsh
   Lucent Technologies
   263 Shuman Blvd.
   1F-545
   Naperville, IL

   Phone: [phone]
   EMail: [e-mail]













Hiller, et al.               Informational                     [Page 12]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


   Yingchun Xu
   WaterCove Networks
   One Century Centre, Suite 550
   1750 E. Golf Road
   Schaumburg, IL

   Phone: [phone]
   EMail: [e-mail]


   Brent Hirschman
   1501 Shure Dr.
   Arlington Heights, IL 60006
   USA

   Phone: [phone]
   EMail: [e-mail]


   Eric Jaques
   Vodafone
   2999 Oak Road, MS-750
   Walnut Creek, CA 94596
   USA

   Phone: [phone]
   EMail: [e-mail]


   Sanjeevan Sivalingham
   Ericsson Wireless Communications Inc.,
   Rm Q-356C
   6455 Lusk Blvd
   San Diego, CA 92126
   USA

   Phone: [phone]
   EMail:  [e-mail]













Hiller, et al.               Informational                     [Page 13]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


   Xing Chen
   Alcatel USA
   1000 Coit Road
   Plano, TX 75075
   USA

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Byung-Keun Lim
   LG Electronics Inc.
   533, Hogye-dong, Donan-Ku, Anyang-shi, Kyungki-do, 431-080,
   Korea

   Phone: [phone]
   Fax:   [phone]
   EMail: [e-mail]


   Hajime Shiino
   Lucent Technologies Japan Ltd.
   25 Mori Bldg. 1-4-30 Roppongi,
   Minato-ku Tokyo
   Japan

   Phone: [phone]
   EMail: [e-mail]


   Shinichi Baba
   Toshiba America Research, Inc.
   PO Box 136,
   Convent Station, NJ 07961-0136
   USA

   Phone: [phone]
   EMail: [e-mail]












Hiller, et al.               Informational                     [Page 14]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


   Takahiro Ayaki
   DDI corporation
   Ichibancho FS Bldg.
   8, Ichibancho, Chiyoda-ku Tokyo
   Japan

   Phone: [phone]
   EMail: [e-mail]


   Alan Hameed
   Fujitsu
   2801 Telecom Parkway
   Richardson, Texas 75082
   USA

   Phone: [phone]


   Charles N. Lo
   Vodafone AirTouch
   2999 Oak Rd
   Walnut Creek, CA  94596
   USA

   Phone: [phone]
   EMail: [e-mail]


   Takuo Seki
   IDO Corporation
   Gobancho YS Bldg.
   12-3, Gobancho, Chiyoda-ku Tokyo
   Japan

   Phone: [phone]
   EMail: [e-mail]














Hiller, et al.               Informational                     [Page 15]

RFC 3141          CDMA2000 Wireless Data Requirements          June 2001


Full Copyright Statement

   Copyright (C) The Internet Society (2001).  All Rights Reserved.

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Acknowledgement

   Funding for the RFC Editor function is currently provided by the
   Internet Society.



















Hiller, et al.               Informational                     [Page 16]