RFC 5637 on Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6

rfc-editor@rfc-editor.org Thu, 01 October 2009 00:09 UTC

Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 35C5B3A6837; Wed, 30 Sep 2009 17:09:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.907
X-Spam-Level:
X-Spam-Status: No, score=-16.907 tagged_above=-999 required=5 tests=[AWL=0.692, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 23fVW76pYkEc; Wed, 30 Sep 2009 17:09:07 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 782673A6A36; Wed, 30 Sep 2009 17:09:07 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 24D36333197; Wed, 30 Sep 2009 17:09:34 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5637 on Authentication, Authorization, and Accounting (AAA) Goals for Mobile IPv6
From: rfc-editor@rfc-editor.org
Message-Id: <20091001000934.24D36333197@bosco.isi.edu>
Date: Wed, 30 Sep 2009 17:09:34 -0700
Cc: mext@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 01 Oct 2009 00:09:08 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5637

        Title:      Authentication, Authorization, and Accounting (AAA) 
                    Goals for Mobile IPv6 
        Author:     G. Giaretta, I. Guardini,
                    E. Demaria, J. Bournelle,
                    R. Lopez
        Status:     Informational
        Date:       September 2009
        Mailbox:    gerardo@qualcomm.com, 
                    ivano.guardini@telecomitalia.it, 
                    elena.demaria@telecomitalia.it,
                    julien.bournelle@gmail.com, 
                    rafa@dif.um.es
        Pages:      11
        Characters: 23409
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mext-aaa-ha-goals-01.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5637.txt

In commercial and enterprise deployments, Mobile IPv6 can be a service
offered by a Mobility Services Provider (MSP).  In this case, all
protocol operations may need to be explicitly authorized and traced,
requiring the interaction between Mobile IPv6 and the AAA
infrastructure.  Integrating the Authentication, Authorization, and
Accounting (AAA) infrastructure (e.g., Network Access Server and AAA
server) also offers a solution component for Mobile IPv6
bootstrapping.  This document describes various scenarios where a AAA
interface for Mobile IPv6 is required.  Additionally, it lists design
goals and requirements for such an interface.  This memo provides 
information for the Internet community.

This document is a product of the Mobility EXTensions for IPv6 Working Group of the IETF.


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

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
USC/Information Sciences Institute