Network Working Group J. Korhonen, Ed. Request for Comments: 5447 Nokia Siemens Networks Category: Standards Track J. Bournelle Orange Labs H. Tschofenig Nokia Siemens Networks C. Perkins WiChorus K. Chowdhury Starent Networks February 2009 Diameter Mobile IPv6:
Support for Network Access Server to Diameter Server Interaction Status of This Memo
This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for
improvements. Plea refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited. Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights rerved.
This document is subject to BCP 78 and the IETF Trust’s Legal
Provisions Relating to IETF Documents (trustee.ietf/
licen-info) in effect on the date of publication of this document. Plea review the documents carefully, as they describe your rights and restrictions with respect to this document.
Abstract
潜心修炼
A Mobile IPv6 node requires a home agent address, a home address, and a curity association with its home agent before it can start
utilizing Mobile IPv6. RFC 3775 requires that some or all of the
推荐表
parameters be statically configured. Mobile IPv6 bootstrapping work aims to make this information dynamically available to the mobile
node. An important aspect of the Mobile IPv6 bootstrapping solution is to support interworking with existing Authentication,
Authorization, and Accounting (AAA) infrastructures. This document
describes MIPv6 bootstrapping using the Diameter Network Access
Server to home AAA rver interface.
Korhonen, et al. Standards Track [Page 1]
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3
3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
4. Commands, Attribute-Value Pairs, and Advertising
Application Support . . . . . . . . . . . . . . . . . . . . . 6 4.1. Advertising Application Support . . . . . . . . . . . . . 6 4.2. Attribute-Value Pair Definitions . . . . . . . . . . . . . 6 4.2.1. MIP6-Agent-Info AVP . . . . . . . . . . . . . . . . . 6 4.2.2. MIP-Home-Agent-Address AVP . . . . . . . . . . . . . . 7 4.2.3. MIP-Ho
me-Agent-Host AVP . . . . . . . . . . . . . . . 7 4.2.4. MIP6-Home-Link-Prefix AVP . . . . . . . . . . . . . . 8
4.2.
5. MIP6-Feature-Vector AVP . . . . . . . . . . . . . . . 8
5. Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5.1. Home Agent Assignment by the NAS . . . . . . . . . . . . . 10 5.2. Home Agent Assignment by the Diameter Server . . . . . . . 11
5.3. Home Agent Assignment by the NAS or Diameter Server . . . 11
6. Attribute-Value Pair Occurrence Tables . . . . . . . . . . . . 12
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 13 7.1. Registration of New AVPs . . . . . . . . . . . . . . . . . 13
7.2. New Registry: Mobility Capability . . . . . . . . . . . . 13
8. Security Considerations . . . . . . . . . . . . . . . . . . . 14
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 14
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 15 10.1. Normative References . . . . . . . . . . . . . . . . . . . 15 10.2. Informative References . . . . . . . . . . . . . . . . . . 15 Korhonen, et al. Standards Track [Page 2]
1. Introduction
The Mobile IPv6 (MIPv6) specification [RFC3775] requires a mobile
node (MN) to perform registration with a home agent (HA) with
information about its current point of attachment (care-of address). The HA creates and maintains the binding between the MN’s home
address and the MN’s care-of address.
In order to register with an HA, the MN needs to know some
information, such as the home link prefix, the HA address, the home
address(es), the home link prefix length, and curity-association-
related information.
The aforementioned information may be statically configured.
However, static provisioning becomes an administrative burden for an operator. Moreover, it does not address load balancing, failover,
opportunistic home link assignment, or assignment of local HAs in
clo proximity to the MN. Also, the ability to react to sudden
environmental or topological changes is minimal. Static provisioning may not be desirable, in light of the limitations.
Dynamic assignment of MIPv6 home registration information is a
洋流是怎么形成的
desirable feature for ea of deployment and network maintenance.
For this purpo, the AAA infrastructure, which is ud for access
友谊祝福语authentication, can be leveraged to assign some or all of the
necessary parameters. The Diameter rver in the Access Service
Provider’s (ASP’s) or Mobility Service Provider’s (MSP’s) network may return the parameters to the AAA client. Regarding the
bootstrapping procedures, the AAA client might either be the Network Access Server, in ca of the integrated scenario, or the HA, in ca of the split scenario [RFC5026]. The terms "integrated" and "split" are described in the following terminology ction and were
introduced in [RFC4640] and [AAA].
2. Terminology and Abbreviations
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].
General mobility terminology can be found in [RFC3753]. The
following additional terms are either borrowed from [RFC4640] or
可诺贝儿[RFC5026] or are introduced in this document:
Access Service Authorizer (ASA):
A network operator that authenticates an MN and establishes the
MN’s authorization to receive Internet rvice.
Korhonen, et al. Standards Track [Page 3]
Access Service Provider (ASP):
A network operator that provides direct IP packet-forwarding to
and from the MN.
Mobility Service Authorizer (MSA):
水浒传第九回
A rvice provider that authorizes MIPv6 rvice.
甘油三酯偏高的原因及治疗方法
Mobility Service Provider (MSP):
A rvice provider that provides MIPv6 rvice. In order to
obtain such rvice, the MN must be authenticated and authorized
to do so.
Split Scenario:
A scenario where the mobility rvice and the network access
rvice are authorized by different entities.
Integrated Scenario:
A scenario where the mobility rvice and the network access
rvice are authorized by the same entity.
Network Access Server (NAS):
A device that provides an access rvice for a ur to a network. Home AAA (HAAA):
An Authentication, Authorization, and Accounting rver located in the ur’s home network, i.e., in the home realm.
拘役和管制有什么区别
Local AAA (LAAA):
An Authentication, Authorization, and Accounting proxy located in the local (ASP) network.
Visited AAA (VAAA):
An Authentication, Authorization, and Accounting proxy located in a visited network, i.e., in the visited realm. In a roaming ca, the local Diameter proxy has the VAAA role (e Figure 1). Korhonen, et al. Standards Track [Page 4]
3. Overview
This document address the Authentication, Authorization, and
Accounting (AAA) functionality required for the MIPv6 bootstrapping
solutions outlined in [RFC4640], and focus on the Diameter-bad
AAA functionality for the NAS-to-HAAA (home AAA) rver
communication.
In the integrated scenario, MIPv6 bootstrapping is provided as part
of the network access authentication procedure. Figure 1 shows the
participating entities.
+---------------------------+ +-----------------+ |Access Service Provider | |ASA/MSA/(MSP) | |(Mobility Service Provider)| | | | | | | | +--------+ | | +--------+ | | |Local | Diameter | | |Home | | | |Diameter|<---------------------->|Diameter| | | |Proxy | (*) | | |Server | | | +--------+ | | +--------+ | | ^ ^ | | ^ | | | | | | |(+) | | | | | | | | | Diameter | | v | | | |(+) +-------+ | | +-------+ | | | | |Home | | | |Home | | | | +-------->|Agent | |
| |Agent | | | (*)| |in ASP | | | |in MSP | | | v +-------+ | | +-------+ | +-------+ IEEE | +-----------+ +-------+ | +-----------------+ |Mobile | 802.1X | |NAS/Relay | |DHCPv6 | |
|Node |------------|Diameter |---|Server | |
| | PANA, | |Client |(+)| | |
+-------+ IKEv2, | +-----------+ +-------+ |
DHCP,... +---------------------------+
(+)
Legend:
(*): Functionality in scope of this specification.
(+): Extensions described in other documents.
Figure 1: Mobile IPv6 Bootstrapping in the Integrated Scenario
In a typical MIPv6 access scenario, an MN is attached to an ASP’s
network. During the network attachment procedure, the MN interacts
with the NAS/Diameter client. Subquently, the NAS/Diameter client interacts with the Diameter rver over the NAS-to-HAAA interface. Korhonen, et al. Standards Track [Page 5]
