rfc文档
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 security-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 close 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 these limitations.
Dynamic assignment of MIPv6 home registration information is a desirable feature for ease of deployment and network maintenance. For this purpose, the AAA infrastructure, which is used for access authentication, can be leveraged to assign some or all of the necessary parameters. The Diameter server in the Access Service
Provider’s (ASP’s) or Mobility Service Provider’s (MSP’s) network may return these parameters to the AAA client. Regarding the
bootstrapping procedures, the AAA client might either be the Network Access Server, in case of the integrated scenario, or the HA, in case of the split scenario [RFC5026]. The terms "integrated" and "split" are described in the following terminology section 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 service.
Korhonen, et al. Standards Track [Page 3]
暂无评价 8页 免费 MODELLING NETWORK TOP... 3页 免费喜欢此文档的还喜欢 ... rfc5778.Diameter Mobile IPv6 Support for Home Agent to Diameter Server ...
Nokia Siemens Network J. Bournelle Orange Labs K. Chowdhury Cisco Systems A...Standards Track [Page 1] RFC 5779 Diameter Support for Proxy Mobile IPv6 ...
百度文库_文档分享平台 新闻网页贴吧知道音乐图片视频地图百科文库 搜 试试 7 帮助 全部 DOC PPT TXT PDF XLS 百度文库 专业资料 工程科技 信息与通信...
rfc5447.Diameter Mobile ... 17页 免费 rfc5778... rfc文档rfc文档隐藏>> Network Working Group ...support for Mobile IPv6 as an extension to the...
Internet Protocol V6 RFC 5453 Reserved IPv6 Interface Identifiers RFC 5447 Diameter Mobile IPv6: Support for Network Access Server to Diameter Server ...
rfc5447.Diameter Mobile ... 17页 免费 rfc3266.Support for IPv6... 5...If implemented, the NLS MUST change each time the network addresses over ...
百度文库_文档分享平台 新闻网页贴吧知道音乐图片视频地图百科文库 搜 试试 7 帮助 全部 DOC PPT TXT PDF XLS 百度文库 专业资料 工程科技 信息与通信...
support: Application session management Diameter Applications Diameter Mobile IPv...(MobileIP, RFC 4004) Diameter Network Access Server Application (NASREQ, ...
Γ Diameter Application В ? Diameter Mobile IPv4 Application (MobileIP, RFC 4004) ? Diameter Network Access Server Application (NASREQ, RFC 4005) ? ...
Γ Diameter Application В ? Diameter Mobile IPv4 Application (MobileIP, RFC 4004) ? Diameter Network Access Server Application (NASREQ, RFC 4005) ? ...
热门文档