Proposal for Issue 5

Section 3.1 (or section 3.5 in the updated version)

UNKNOWN_CHALLENGE: This error code is set by the Mobile Node in the case where the Mobile Node has moved to a new Foreign Agent that cannot validate the challenge provided in the Registration Request.

UNKNOWN_CHALLENGE: This error code is received by the Mobile Node in the case where the Mobile Node has moved to a new Foreign Agent that cannot validate the challenge provided in the Registration Request.

Section 3.3

The Foreign Agent SHOULD include a new Challenge extension in any Registration Reply, successful or not.

The Foreign Agent SHOULD include a new Mobile-Foreign Challenge Extension in any Registration Reply, successful or not.

Section 1

Mobile IP defines the Mobile-Foreign Authentication extension to allow a mobile node can authenticate itself to a foreign agent.

Mobile IP defines the Mobile-Foreign Authentication extension to allow a mobile node to authenticate itself to a foreign agent.

Appendix D

The mobile node creates a Registration Request including the advertised Challenge Value in the Challenge Extension, along with an Mobile-Foreignauthentication extension.

The mobile node creates a Registration Request including the advertised Challenge Value in the Challenge Extension, along with an Mobile-Foreign Authentication extension.

Section 1.1

Any challenge that has been used by the mobile node in a Registration Request message and processed by the Foreign Agent by relaying or generating The Foreign Agent may not be able to keep records for all previously used challenges, but see section 3.2 for minimal requirements.

Any challenge that has been used by the mobile node in a Registration Request message and processed by the Foreign Agent by relaying or generating a corresponding Registration Reply message. The Foreign Agent may not be able to keep records for all previously used challenges, but see section 3.2 for minimal requirements.