CDMA2000 Wireless Data Requirements for AAA
RFC 3141

Document Type RFC - Informational (June 2001; No errata)
Was draft-hiller-cdma2000-aaa (individual)
Last updated 2013-03-02
Stream Legacy
Formats plain text pdf html bibtex
Stream Legacy state (None)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state RFC 3141 (Informational)
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                     T. Hiller, Lucent Technologies
Request for Comments: 3141                 P. Walsh, Lucent Technologies
Category: Informational                                 X. Chen, Alcatel
                                                               M. Munson
                                               G. Dommety, Cisco Systems
                        S. Sivalingham, Ericsson Wireless Communications
                           B. Lim, LG Information & Communications, Ltd.
                                          P. McCann, Lucent Technologies
                                          H. Shiino, Lucent Technologies
                                                  B. Hirschman, Motorola
                                       S. Manning, Award Solutions, Inc.
                                                  R. Hsu, Qualcomm, Inc.
                        H. Koo, Samsung Telecommunications America, Inc.
                                                  M. Lipford, Sprint PCS
                                      P. Calhoun, Sun Laboratories, Inc.
                                                         C. Lo, Vodafone
                                                     E. Jaques, Vodafone
                      E. Campbell, CommWorks Corporation, A 3Com Company
                                               Y. Xu, WaterCove Networks
                                 S. Baba, Toshiba America Research, Inc.
                                               T. Ayaki, DDI Corporation
                                                 T. Seki, DO Corporation
                                                      A. Hameed, Fujitsu
                                                               June 2001

              CDMA2000 Wireless Data Requirements for AAA

Status of this Memo

   This memo provides information for the Internet community.  It does
   not specify an Internet standard of any kind.  Distribution of this
   memo is unlimited.

Copyright Notice

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

Abstract

   This memo specifies cdma2000 wireless data AAA (Authentication,
   Authorization, Accounting) requirements associated with third
   generation wireless architecture that supports roaming among service
   providers for traditional PPP and Mobile IP services.

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

1.  Introduction

   The architecture is designed for use with a cellular network as an
   access medium.  Sections 1, 2, present a brief high level review of
   the cdma2000 wireless data architecture.  Section 3 presents cdma2000
   AAA requirements.

   This document specifies AAA requirements associated with a third
   generation cdma2000 wireless architecture that supports roaming among
   service providers for traditional PPP and Mobile IP services.  The
   architecture is designed for use with a cellular network as an access
   medium.

   Sections 1 and 2 present a brief, high level review of the cdma2000
   wireless  data architecture as an aid to interested AAA WG members.
   Section 3 presents cdma2000 AAA requirements, and is self contained
   relative to the architecture review.

1.1.  Requirements language

   In this document, the key words "MAY", "MUST, "MUST NOT", "optional",
   "recommended", "SHOULD", and "SHOULD NOT", are to be interpreted as
   described in [RFC2119].

   Please note that the requirements specified in this document are to
   be used in evaluating AAA protocol submissions.  As such, the
   requirements language refers to capabilities of these protocols; the
   protocol documents will specify whether these features are required,
   recommended, or optional.  For example, requiring that a protocol
   support confidentiality is NOT the same thing as requiring that all
   protocol traffic be encrypted.

   A protocol submission is not compliant if it fails to satisfy one or
   more of the MUST or MUST NOT requirements for the capabilities that
   it implements.  A protocol submission that satisfies all the MUST,
   MUST NOT, SHOULD and SHOULD NOT requirements for its capabilities is
   said to be "unconditionally compliant"; one that satisfies all the
   MUST and MUST NOT requirements but not all the SHOULD or SHOULD NOT
   requirements for its protocols is said to be "conditionally
   compliant."

1.2.  General Service Requirements

      o  Provide service during subscriber visiting between wireless
         networks systems while maintaining a formal customer-service
         provider relation with only one wireless service provider.

      o  Support Traditional PPP and Mobile IP services:

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

         o  Support dynamic and static home address assignments for
Show full document text