RFC 3012 on Mobile IPv4 Challenge/Response
RFC Editor <rfc-ed@ISI.EDU> Fri, 08 December 2000 01:29 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA24355; Thu, 7 Dec 2000 20:29:38 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id UAA03073 for ietf-123-outbound.10@ietf.org; Thu, 7 Dec 2000 20:25:02 -0500 (EST)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id UAA03012 for <all-ietf@loki.ietf.org>; Thu, 7 Dec 2000 20:14:32 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with SMTP id UAA20779 for <all-ietf@ietf.org>; Thu, 7 Dec 2000 20:14:31 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.9.3/8.9.3) with ESMTP id RAA13885; Thu, 7 Dec 2000 17:14:31 -0800 (PST)
Message-Id: <200012080114.RAA13885@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 3012 on Mobile IPv4 Challenge/Response
Cc: rfc-ed@ISI.EDU, mobile-ip@standards.nortelnetworks.com
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 07 Dec 2000 17:14:31 -0800
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3012 Title: Mobile IPv4 Challenge/Response Extensions Author(s): C. Perkins, P. Calhoun Status: Standards Track Date: November 2000 Mailbox: charliep@iprg.nokia.com, pcalhoun@eng.sun.com Pages: 17 Characters: 37005 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mobileip-challenge-13.txt URL: ftp://ftp.isi.edu/in-notes/rfc3012.txt Mobile IP, as originally specified, defines an authentication extension (the Mobile-Foreign Authentication extension) by which a mobile node can authenticate itself to a foreign agent. Unfortunately, this extension does not provide ironclad replay protection for the foreign agent, and does not allow for the use of existing techniques (such as CHAP) for authenticating portable computer devices. In this specification, we define extensions for the Mobile IP Agent Advertisements and the Registration Request that allow a foreign agent to use a challenge/response mechanism to authenticate the mobile node. This document is a product of the IP Routing for Wireless/Mobile Hosts Working Group of the IETF. This is now a Proposed Standard Protocol. This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please 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. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.
- RFC 3012 on Mobile IPv4 Challenge/Response RFC Editor