I-D ACTION:draft-ietf-mobileip-reg-revok-03.txt

Internet-Drafts@ietf.org Mon, 01 July 2002 11:47 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA28511; Mon, 1 Jul 2002 07:47:44 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id HAA09327 for ietf-123-outbound.10@ietf.org; Mon, 1 Jul 2002 07:45:02 -0400 (EDT)
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 GAA08433 for <all-ietf@loki.ietf.org>; Mon, 1 Jul 2002 06:35:57 -0400 (EDT)
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA21332; Mon, 1 Jul 2002 06:35:09 -0400 (EDT)
Message-Id: <200207011035.GAA21332@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce:;
Cc: mobile-ip@sunroof.eng.sun.com
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-mobileip-reg-revok-03.txt
Date: Mon, 01 Jul 2002 06:35:08 -0400
Sender: nsyracus@cnri.reston.va.us

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Routing for Wireless/Mobile Hosts Working Group of the IETF.

	Title		: Registration Revocation in Mobile IP
	Author(s)	: S. Glass, M. Chandra
	Filename	: draft-ietf-mobileip-reg-revok-03.txt
	Pages		: 37
	Date		: 28-Jun-02
	
During the original design of Mobile IP, the need for an
administrative domain to be able to actively revoke a current Mobile
IP registration was recognized.  Due to the lack of a specific
scenario requiring such a mechanism, it was decided that instead of an
active revocation mechanism explicitly for the purpose of registration
revocation, a passive mechanism, namely short registration lifetimes,
and the denial of a subsequent registrations from a mobile node, would
likely be sufficient for this purpose.
Investigations into requirements for a AAA protocol within the AAA
working group have forced reconsideration of a more pro-active Mobile
IP registration revocation feature whereby both domains providing
Mobile IP services can be made aware that the service is being suspended.

In the ideal model, revocations must be possible from either home
or foreign domains, so any registration revocation mechanism being
defined must provide a signaling mechanism between the two that
identify registration(s) being released, implying that since Mobile IP
services are no longer being provided on one side of the registration,
they need not be provided on the other.  In some cases the current
registration may be terminated to simply force the mobile node to
renegotiate its registration, but in other cases renegotiation may not
be allowed.  Either one of these reasons is sufficient to justify this
mechanism.

Moreover, there should also be a mechanism in place whereby the
mobile node whose registration has been terminated can also be
informed that such a revocation has occurred, if only so it may
understand it is not longer being provided Mobile IP services, though
the reasons for such a revocation need not necessarily be immediately
relayed.  This mechanism would ideally be independent of the
signaling mechanism between the agents identified above so as to
leave actual notification of the mobile node up to a separate policy 
of the domains in question

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-mobileip-reg-revok-03.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-mobileip-reg-revok-03.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-mobileip-reg-revok-03.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.
ftp://ftp.ietf.org/internet-drafts/draft-ietf-mobileip-reg-revok-03.txt"><ftp://ftp.ietf.org/internet-drafts/draft-ietf-mobileip-reg-revok-03.txt>