draft-ietf-mip4-rfc3012bis-01.txt   draft-ietf-mip4-rfc3012bis-02.txt 
Network Working Group Charles E. Perkins Network Working Group Charles E. Perkins
Internet-Draft Nokia Research Center Internet-Draft Nokia Research Center
Expires: October 20, 2004 Pat R. Calhoun Expires: December 10, 2004 Pat R. Calhoun
Black Storm Networks Black Storm Networks
Jayshree. Bharatia Jayshree. Bharatia
Nortel Networks Nortel Networks
April 21, 2004 June 11, 2004
Mobile IPv4 Challenge/Response Extensions (revised) Mobile IPv4 Challenge/Response Extensions (revised)
draft-ietf-mip4-rfc3012bis-01.txt draft-ietf-mip4-rfc3012bis-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with By submitting this Internet-Draft, I certify that any applicable
all provisions of Section 10 of RFC2026. patent or other IPR claims of which I am aware have been disclosed,
and any of which I become aware will be disclosed, in accordance with
RFC 3668.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that other Task Force (IETF), its areas, and its working groups. Note that
groups may also distribute working documents as Internet-Drafts. other groups may also distribute working documents as
Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at http:// The list of current Internet-Drafts can be accessed at
www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on October 20, 2004. This Internet-Draft will expire on December 10, 2004.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2004). All Rights Reserved. Copyright (C) The Internet Society (2004). All Rights Reserved.
Abstract Abstract
Mobile IP, as originally specified, defines an authentication Mobile IP, as originally specified, defines an authentication
extension (the Mobile-Foreign Authentication extension) by which a extension (the Mobile-Foreign Authentication extension) by which a
mobile node can authenticate itself to a foreign agent. mobile node can authenticate itself to a foreign agent.
skipping to change at page 2, line 19 skipping to change at page 3, line 7
authentication extension called the Mobile-AAA Authentication authentication extension called the Mobile-AAA Authentication
extension. This new extension is provided so that a mobile node can extension. This new extension is provided so that a mobile node can
supply credentials for authorization using commonly available AAA supply credentials for authorization using commonly available AAA
infrastructure elements. This Authorization-enabling extension MAY infrastructure elements. This Authorization-enabling extension MAY
co-exist in the same Registration Request with Authentication co-exist in the same Registration Request with Authentication
extensions defined for Mobile IP Registration by RFC3344. This extensions defined for Mobile IP Registration by RFC3344. This
document obsoletes RFC3012. document obsoletes RFC3012.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Terminology . . . . . . . . . . . . . . . . . . . . . . . 4
2. Mobile IP Agent Advertisement Challenge Extension . . . . . . 5 2. Mobile IP Agent Advertisement Challenge Extension . . . . . . 6
2.1 Handling of Solicited Agent Advertisements . . . . . . . . 5 2.1 Handling of Solicited Agent Advertisements . . . . . . . . 6
3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 7 3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3.1 Mobile Node Processing for Registration Requests . . . . . 7 3.1 Mobile Node Processing for Registration Requests . . . . . 8
3.2 Foreign Agent Processing for Registration Requests . . . . 8 3.2 Foreign Agent Processing for Registration Requests . . . . 9
3.3 Foreign Agent Processing for Registration Replies . . . . 10 3.3 Foreign Agent Processing for Registration Replies . . . . 11
3.4 Home Agent Processing for the Challenge Extensions . . . . 11 3.4 Home Agent Processing for the Challenge Extensions . . . . 12
3.5 Mobile Node Processing for Registration Replies . . . . . 11 3.5 Mobile Node Processing for Registration Replies . . . . . 12
4. Mobile-Foreign Challenge Extension . . . . . . . . . . . . . . 13 4. Mobile-Foreign Challenge Extension . . . . . . . . . . . . . . 14
5. Generalized Mobile IP Authentication Extension . . . . . . . . 14 5. Generalized Mobile IP Authentication Extension . . . . . . . . 15
6. Mobile-AAA Authentication subtype . . . . . . . . . . . . . . 15 6. Mobile-AAA Authentication subtype . . . . . . . . . . . . . . 16
7. Reserved SPIs for Mobile IP . . . . . . . . . . . . . . . . . 16 7. Reserved SPIs for Mobile IP . . . . . . . . . . . . . . . . . 17
8. SPIs for RADIUS AAA Servers . . . . . . . . . . . . . . . . . 17 8. SPIs for RADIUS AAA Servers . . . . . . . . . . . . . . . . . 18
9. Configurable Parameters . . . . . . . . . . . . . . . . . . . 18 9. Configurable Parameters . . . . . . . . . . . . . . . . . . . 19
10. Error Values . . . . . . . . . . . . . . . . . . . . . . . . 19 10. Error Values . . . . . . . . . . . . . . . . . . . . . . . . 20
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 20 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . 21
12. Security Considerations . . . . . . . . . . . . . . . . . . 21 12. Security Considerations . . . . . . . . . . . . . . . . . . 22
13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 22 13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 23
A. Change History . . . . . . . . . . . . . . . . . . . . . . . . 23 A. Change History . . . . . . . . . . . . . . . . . . . . . . . . 24
B. Verification Infrastructure . . . . . . . . . . . . . . . . . 25 B. Verification Infrastructure . . . . . . . . . . . . . . . . . 26
C. Message Flow for FA Challenge Messaging with Mobile-AAA C. Message Flow for FA Challenge Messaging with Mobile-AAA
Extension . . . . . . . . . . . . . . . . . . . . . . . . . . 27 Extension . . . . . . . . . . . . . . . . . . . . . . . . . . 28
D. Message Flow for FA Challenge Messaging with MN-FA D. Message Flow for FA Challenge Messaging with MN-FA
Authentication . . . . . . . . . . . . . . . . . . . . . . . . 28 Authentication . . . . . . . . . . . . . . . . . . . . . . . . 29
E. Foreign Agent Algorithm for Tracking Used Challenges . . . . . 29 E. Foreign Agent Algorithm for Tracking Used Challenges . . . . . 30
14. Normative References . . . . . . . . . . . . . . . . . . . . 30 14. Normative References . . . . . . . . . . . . . . . . . . . . 31
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 31 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 32
Intellectual Property and Copyright Statements . . . . . . . . 32 Intellectual Property and Copyright Statements . . . . . . . . 33
1. Introduction 1. Introduction
Mobile IP defines the Mobile-Foreign Authentication extension to Mobile IP defines the Mobile-Foreign Authentication extension to
allow a mobile node to authenticate itself to a foreign agent. Such allow a mobile node to authenticate itself to a foreign agent. Such
authentication mechanisms are mostly external to the principal authentication mechanisms are mostly external to the principal
operation of Mobile IP, since the foreign agent can easily route operation of Mobile IP, since the foreign agent can easily route
packets to and from a mobile node whether or not the mobile node is packets to and from a mobile node whether or not the mobile node is
reporting a legitimately owned home address to the foreign agent. reporting a legitimately owned home address to the foreign agent.
Unfortunately, that extension does not provide the foreign agent any Unfortunately, that extension does not provide the foreign agent any
skipping to change at page 8, line 13 skipping to change at page 9, line 13
chosen as CHAP_SPI or HMAC_CHAP_SPI (see Section 9), then the mobile chosen as CHAP_SPI or HMAC_CHAP_SPI (see Section 9), then the mobile
node specifies CHAP-style authentication [RFC1994] using MD5 node specifies CHAP-style authentication [RFC1994] using MD5
[RFC1321] or HMAC_MD5, respectively. [RFC1321] or HMAC_MD5, respectively.
In either case, the Mobile-Foreign Challenge extension followed by In either case, the Mobile-Foreign Challenge extension followed by
one of the above specified authentication extensions MUST follow the one of the above specified authentication extensions MUST follow the
Mobile-Home Authentication extension, if present. Mobile-Home Authentication extension, if present.
A mobile node MAY include the Mobile-AAA Authentication extension in A mobile node MAY include the Mobile-AAA Authentication extension in
the Registration Request when the mobile node registers directly with the Registration Request when the mobile node registers directly with
its home agent (using a co-located care-of address). In this case, if its home agent (using a co-located care-of address). In this case,
the mobile node uses an SPI value of CHAP_SPI or HMAC_CHAP_SPI if the mobile node uses an SPI value of CHAP_SPI or HMAC_CHAP_SPI
(Section 8) in the MN-AAA Authentication extension, the mobile node (Section 8) in the MN-AAA Authentication extension, the mobile node
MUST include the Mobile-Foreign Challenge extension prior to the MUST include the Mobile-Foreign Challenge extension prior to the
Mobile-AAA Authentication extension. The mechanism used by the Mobile-AAA Authentication extension. The mechanism used by the
mobile node to obtain the Challenge value in this case is outside the mobile node to obtain the Challenge value in this case is outside the
scope of this document. scope of this document.
3.2 Foreign Agent Processing for Registration Requests 3.2 Foreign Agent Processing for Registration Requests
Upon receipt of the Registration Request, if the foreign agent has Upon receipt of the Registration Request, if the foreign agent has
issued a Challenge as part of its Agent Advertisements, and it does issued a Challenge as part of its Agent Advertisements, and it does
not have a security association with the mobile node, then the not have a security association with the mobile node, then the
foreign agent SHOULD check that the Mobile-Foreign Challenge foreign agent SHOULD check that the Mobile-Foreign Challenge
extension exists, and that it contains a challenge value previously extension exists, and that it contains a challenge value previously
unused by the mobile node. This ensures that the mobile node is not unused by the mobile node. This ensures that the mobile node is not
attempting to replay a previous advertisement and authentication. In attempting to replay a previous advertisement and authentication. In
this case, if the Registration Request does not include a challenge this case, if the Registration Request does not include a challenge
extension, the foreign agent MUST include FA Error extension (defined extension, the foreign agent MUST include FA Error extension (defined
in [FAERR]) in the Registration Reply message with Status code set in [FAERR]) in the Registration Reply message with Status code set to
to MISSING_CHALLENGE. MISSING_CHALLENGE.
A foreign agent that sends Agent Advertisements containing a A foreign agent that sends Agent Advertisements containing a
Challenge value MAY send a Registration Reply message with a Challenge value MAY send a Registration Reply message with a
MISSING_CHALLENGE error if the mobile node sends a Registration MISSING_CHALLENGE error if the mobile node sends a Registration
Request with a Mobile-Foreign Authentication extension without Request with a Mobile-Foreign Authentication extension without
including a Challenge. In other words, such a foreign agent MAY including a Challenge. In other words, such a foreign agent MAY
refuse to process a Registration Request from the mobile node unless refuse to process a Registration Request from the mobile node unless
the request contains an unused Challenge. the request contains an unused Challenge.
If a mobile node retransmits a Registration Request with the same If a mobile node retransmits a Registration Request with the same
skipping to change at page 20, line 9 skipping to change at page 21, line 9
| | | | | | | |
| HA_BAD_AAA_AUTH | TBD | 3.4 | | HA_BAD_AAA_AUTH | TBD | 3.4 |
+--------------------+-------+--------------------------+ +--------------------+-------+--------------------------+
Table 2: Error Values Table 2: Error Values
11. IANA Considerations 11. IANA Considerations
All protocol values in this specification are to be the same as All protocol values in this specification are to be the same as
defined in RFC 3012 [RFC3012]. Additionaly, new error codes defined in RFC 3012 [RFC3012]. Additionaly, new error codes
FA_BAD_AAA_AUTH and HA_BAD_AAA_AUTH are defined by this document. The FA_BAD_AAA_AUTH and HA_BAD_AAA_AUTH are defined by this document.
Status code list for the FA Error extension defined in [FAERR] is The Status code list for the FA Error extension defined in [FAERR] is
extended with the new Status code MISSING_CHALLENGE along with the extended with the new Status code MISSING_CHALLENGE along with the
new sub-type (TBD) for the protocol extension specified in this new sub-type (TBD) for the protocol extension specified in this
document. document.
12. Security Considerations 12. Security Considerations
In the event that a malicious mobile node attempts to replay the In the event that a malicious mobile node attempts to replay the
authenticator for an old Mobile-Foreign Challenge, the foreign agent authenticator for an old Mobile-Foreign Challenge, the foreign agent
would detect it since the agent always checks whether it has recently would detect it since the agent always checks whether it has recently
advertised the Challenge (see Section 3.2). Allowing mobile nodes advertised the Challenge (see Section 3.2). Allowing mobile nodes
skipping to change at page 25, line 5 skipping to change at page 25, line 19
[RFC3344]. [RFC3344].
o Added protection against bogus Registration Reply and Agent o Added protection against bogus Registration Reply and Agent
Advertisement. Also, the processing of the Challenge is clarified Advertisement. Also, the processing of the Challenge is clarified
if it is received in the multicast/unicast Agent Advertisement. if it is received in the multicast/unicast Agent Advertisement.
List of the changes for draft-ietf-mip4-rfc3012bis-01: List of the changes for draft-ietf-mip4-rfc3012bis-01:
o Minor editorial changes are made through out the document. o Minor editorial changes are made through out the document.
o Added reference of FA Error extension in the References section o Added reference of FA Error extension in the References section
and also updated relevant text in section 3.2 and section 11. and also updated relevant text in section 3.2 and section 11.
List of the changes for draft-ietf-mip4-rfc3012bis-02:
o Minor editorial changes are made in Appendix C and Appendix D.
o Updated Boilerplate.
Appendix B. Verification Infrastructure Appendix B. Verification Infrastructure
The Challenge extensions in this protocol specification are expected The Challenge extensions in this protocol specification are expected
to be useful to help the foreign agent manage connectivity for to be useful to help the foreign agent manage connectivity for
visiting mobile nodes, even in situations where the foreign agent visiting mobile nodes, even in situations where the foreign agent
does not have any security association with the mobile node or the does not have any security association with the mobile node or the
mobile node's home agent. In order to carry out the necessary mobile node's home agent. In order to carry out the necessary
authentication, it is expected that the foreign agent will need the authentication, it is expected that the foreign agent will need the
assistance of external administrative systems, which have come to be assistance of external administrative systems, which have come to be
called AAA systems. For the purposes of this document, we call the called AAA systems. For the purposes of this document, we call the
skipping to change at page 27, line 46 skipping to change at page 28, line 46
an Mobile-AAA authentication extension. an Mobile-AAA authentication extension.
3. The foreign agent relays the Registration Request either to the 3. The foreign agent relays the Registration Request either to the
home agent specified by the mobile node, or else to its locally home agent specified by the mobile node, or else to its locally
configured Verification Infrastructure (see Appendix B), configured Verification Infrastructure (see Appendix B),
according to local policy. according to local policy.
4. The foreign agent receives a Registration Reply with the 4. The foreign agent receives a Registration Reply with the
appropriate indications for authorizing connectivity for the appropriate indications for authorizing connectivity for the
mobile node. mobile node.
5. The foreign agent relays the Registration Reply to the mobile 5. The foreign agent relays the Registration Reply to the mobile
node, possibly along with a new Challenge Value to be used by the node, possibly along with a new Challenge Value to be used by the
mobile node in its next Registration Reply message. mobile node in its next Registration Request message.
Appendix D. Message Flow for FA Challenge Messaging with MN-FA Appendix D. Message Flow for FA Challenge Messaging with MN-FA
Authentication Authentication
MN FA home agent MN FA home agent
|<-- Adv+Challenge--| | |<-- Adv+Challenge--| |
| (if needed) | | | (if needed) | |
| | | | | |
|-- RReq+Challenge->| | |-- RReq+Challenge->| |
| + Auth.Ext. | | | + Auth.Ext. | |
skipping to change at page 28, line 41 skipping to change at page 29, line 41
2. The mobile node creates a Registration Request including the 2. The mobile node creates a Registration Request including the
advertised Challenge Value in the Challenge Extension, along with advertised Challenge Value in the Challenge Extension, along with
an Mobile-Foreign Authentication extension. an Mobile-Foreign Authentication extension.
3. The foreign agent relays the Registration Request to the home 3. The foreign agent relays the Registration Request to the home
agent specified by the mobile node. agent specified by the mobile node.
4. The foreign agent receives a Registration Reply with the 4. The foreign agent receives a Registration Reply with the
appropriate indications for authorizing connectivity for the appropriate indications for authorizing connectivity for the
mobile node. mobile node.
5. The foreign agent relays the Registration Reply to the mobile 5. The foreign agent relays the Registration Reply to the mobile
node, possibly along with a new Challenge Value to be used by the node, possibly along with a new Challenge Value to be used by the
mobile node in its next Registration Reply message. If the Reply mobile node in its next Registration Request message. If the
contains the Code value HA_BAD_AAA_AUTH (see Section 10), the Reply contains the Code value HA_BAD_AAA_AUTH (see Section 10),
foreign agent takes actions indicated for rejected registrations. the foreign agent takes actions indicated for rejected
registrations.
Appendix E. Foreign Agent Algorithm for Tracking Used Challenges Appendix E. Foreign Agent Algorithm for Tracking Used Challenges
If the foreign agent maintains a large CHALLENGE_WINDOW, it becomes If the foreign agent maintains a large CHALLENGE_WINDOW, it becomes
more important for scalability purposes to efficiently compare more important for scalability purposes to efficiently compare
incoming challenges against the set of Challenge values which have incoming challenges against the set of Challenge values which have
been advertised recently. This can be done by keeping the Challenge been advertised recently. This can be done by keeping the Challenge
values in order of advertisement, and by making use of the mandated values in order of advertisement, and by making use of the mandated
behavior that mobile nodes MUST NOT use Challenge values which were behavior that mobile nodes MUST NOT use Challenge values which were
advertised before the last advertised Challenge value that the mobile advertised before the last advertised Challenge value that the mobile
skipping to change at page 32, line 8 skipping to change at page 33, line 8
Nortel Networks Nortel Networks
2221, Lakeside Blvd 2221, Lakeside Blvd
Richardson, TX 75082 Richardson, TX 75082
Fax: +1 972-684-3775 Fax: +1 972-684-3775
EMail: jayshree@nortelnetworks.com EMail: jayshree@nortelnetworks.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it might or might not be available; nor does it represent that it has
has made any effort to identify any such rights. Information on the made any independent effort to identify any such rights. Information
IETF's procedures with respect to rights in standards-track and on the procedures with respect to rights in RFC documents can be
standards-related documentation can be found in BCP-11. Copies of found in BCP 78 and BCP 79.
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to Copies of IPR disclosures made to the IETF Secretariat and any
obtain a general license or permission for the use of such assurances of licenses to be made available, or the result of an
proprietary rights by implementors or users of this specification can attempt made to obtain a general license or permission for the use of
be obtained from the IETF Secretariat. such proprietary rights by implementers or users of this
specification can be obtained from the IETF on-line IPR repository at
http://www.ietf.org/ipr.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights that may cover technology that may be required to implement
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF at
Director. ietf-ipr@ietf.org.
Full Copyright Statement
Copyright (C) The Internet Society (2004). All Rights Reserved. Disclaimer of Validity
This document and translations of it may be copied and furnished to This document and the information contained herein are provided on an
others, and derivative works that comment on or otherwise explain it "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
or assist in its implementation may be prepared, copied, published OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
and distributed, in whole or in part, without restriction of any ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
kind, provided that the above copyright notice and this paragraph are INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
included on all such copies and derivative works. However, this INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
document itself may not be modified in any way, such as by removing WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be Copyright Statement
revoked by the Internet Society or its successors or assignees.
This document and the information contained herein is provided on an Copyright (C) The Internet Society (2004). This document is subject
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING to the rights, licenses and restrictions contained in BCP 78, and
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING except as set forth therein, the authors retain all their rights.
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Acknowledgment Acknowledgment
Funding for the RFC Editor function is currently provided by the Funding for the RFC Editor function is currently provided by the
Internet Society. Internet Society.
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/