1 - 3 - 6 - 8 - 9 - A - B - C - D - E - F - G - H - I - K - L - M - N - O - P - R - S - T - U - V - W
mobile node
Click on the red underlined text to get to the source
... Binding Update and
Binding Acknowledgment messages between the Mobile Node and Home
Agent using a mobility message authentication option ...
... SA with its Home Agent. A
Mobile Node can implement Mobile IPv6 without having to integrate it
with the IPsec ...
...
- In certain deployment environments, the mobile node needs dynamic
assignment of a home agent and home address ...
... - Network deployments in which not all Mobile Nodes and Home Agents
have IKEv2 implementations ...
... Networks in which the establishment of the security association
between the Mobile Node and the authentication server (AAA Home) is
...
... This document presents a lightweight mechanism to authenticate the
Mobile Node at the Home Agent or at the Authentication,
Authorization, and Accounting (AAA ...
... shared-key-based mobility security association between the
Mobile Node and the respective authenticating entity. This shared-
key-based mobility security association ...
... This document introduces new mobility options to aid in
authentication of the Mobile Node to the Home Agent or AAAH server.
...
... is not provided when these options are used for authentication of the
Mobile Node to the Home Agent. Thus, unless the network can
...
... shared-key-based mobility security association between Mobile Node
and Home Agent consists of a mobility Security Parameter Index ...
... Authentication Protocol
The Mobile Node MUST use the Mobile Node Identifier option,
specifically the MN-NAI mobility ...
...
The Mobile Node MUST use the Mobile Node Identifier option,
specifically the MN-NAI mobility option as defined in [RFC4283 ...
... RFC4283] to
identify itself while authenticating with the Home Agent. The Mobile
Node uses the Mobile Node Identifier option as defined in [RFC4283]
...
... identify itself while authenticating with the Home Agent. The Mobile
Node uses the Mobile Node Identifier option as defined in [RFC4283]
to identify itself as may be required for use with some existing AAA
infrastructure ...
... AAA
infrastructure designs.
The Mobile Node MAY use the Message Identifier option as defined in
Section 6 for additional replay protection ...
... mobility message authentication option described in Section 5 may
be used by the Mobile Node to transfer authentication data when the
Mobile Node ...
... Mobile Node to transfer authentication data when the
Mobile Node and the Home Agent are utilizing a mobility SPI (a number
...
... The shared-key-based mobility security association between Mobile
Node and Home Agent used within this specification consists of a
mobility SPI ...
... security association with the Home Agent. The Mobile Node MUST
include this option in a BU if it has a shared-key-based ...
... Home Agent has a shared-key-based mobility
security association with the Mobile Node.
The Mobile Node ...
... Binding Update message based on the shared mobility security
association between the Mobile Node and AAA server in Home network
...
...
The Mobile Node MAY use the Mobile Node Identifier option [RFC4283]
to enable the Home Agent ...
... Authentication Failure Detection at the Mobile Node ...
... status code MIPV6-AUTH-FAIL to the Mobile Node,
if a shared-key-based mobility security association ...
... shared-key-based mobility security association to be used
between Mobile Node and Home Agent for authentication exists. If
...
... Home
Agent verify that a Binding Update has been freshly generated by the
Mobile Node and not replayed by an attacker from some previous
Binding Update ...
... Binding Update. This is especially useful for cases where the Home
Agent does not maintain stateful information about the Mobile Node
after the binding entry has been removed ...
... mobility message replay protection option when
included is used by the Mobile Node for matching BA with BU.
...
... Binding Update) and the Binding Update from the Mobile Node does not
include this option, the Home Agent discards the BU ...
... timestamp used in a Binding Update from
the Mobile Node MUST be greater than that used in any previous
successful Binding Update.
...
... timestamp MUST be greater than all previously accepted timestamps for
the requesting Mobile Node.
If the timestamp ...
... field into the Timestamp field in the BA it returns to the Mobile
Node. If the timestamp is not valid, the Home Agent ...
... timestamp check fails.
If the Mobile Node receives a Binding Acknowledgement with the code
MIPV6 ...
... Binding Acknowledgement with the code
MIPV6-ID-MISMATCH, the Mobile Node MUST authenticate the BA by
...
...
If authentication succeeds, the Mobile Node MUST adjust its timestamp
and send subsequent Binding Update ...
... Timestamp value it sent in the corresponding BU. If the
values match, the Mobile Node proceeds to process the MN-HA
authentication data ...
... authentication data in the BA. If the values do not match, the
Mobile Node silently discards the BA.
...
... Patel, A., Leung, K., Khalil, M., Akhtar, H., and K. Chowdhury, "Mobile Node Identifier Option for Mobile IPv6", RFC 4283prop, November 2005. ...
... home address, it MUST accept any Sequence
Number value in a received Binding Update from this Mobile Node.
With the mechanism defined in this document, it is possible for the
...
...
With the mechanism defined in this document, it is possible for the
Mobile Node to register with a different Home Agent during each
...
... in the network to maintain state about the Mobile Node. Also, if the
Home Agent does not cache ...
... create a binding cache entry for the Mobile Node. Thus, when
authentication option is used, Sequence Number ...
... Home Agent does not save state
information for every Mobile Node) would be for the Home Agent to
reject the first BU ...
... sequence number for the session and force the Mobile Node to send a
fresh BU with the suggested sequence number ...