RFC 5563 on WiMAX Forum / 3GPP2 Proxy Mobile IPv4

rfc-editor@rfc-editor.org Tue, 09 February 2010 02:54 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B9C8828C1EA for <ietf-announce@core3.amsl.com>; Mon, 8 Feb 2010 18:54:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.564
X-Spam-Level:
X-Spam-Status: No, score=-2.564 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W2zwwdatSwXM for <ietf-announce@core3.amsl.com>; Mon, 8 Feb 2010 18:54:16 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id EE71528C1D0 for <ietf-announce@ietf.org>; Mon, 8 Feb 2010 18:54:15 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 99194E06E6; Mon, 8 Feb 2010 18:55:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5563 on WiMAX Forum / 3GPP2 Proxy Mobile IPv4
From: rfc-editor@rfc-editor.org
Message-Id: <20100209025520.99194E06E6@rfc-editor.org>
Date: Mon, 8 Feb 2010 18:55:20 -0800 (PST)
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 02:54:16 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 5563

        Title:      WiMAX Forum / 3GPP2 Proxy 
                    Mobile IPv4 
        Author:     K. Leung, G. Dommety,
                    P. Yegani, K. Chowdhury
        Status:     Informational
        Date:       February 2010
        Mailbox:    kleung@cisco.com, 
                    gdommety@cisco.com, 
                    pyegani@cisco.com,  kchowdhury@starentnetworks.com
        Pages:      41
        Characters: 92438
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-leung-mip4-proxy-mode-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5563.txt

Mobile IPv4 is a standard mobility protocol that enables an IPv4 device
to move among networks while maintaining its IP address.  The mobile
device has the Mobile IPv4 client function to signal its location to
the routing anchor, known as the Home Agent.  However, there are many
IPv4 devices without such capability due to various reasons.  This
document describes Proxy Mobile IPv4 (PMIPv4), a scheme based on
having the Mobile IPv4 client function in a network entity to provide
mobility support for an unaltered and mobility-unaware IPv4 device.
This document also describes a particular application of PMIPv4 as
specified in the WiMAX Forum and another application that is to be
adopted in 3GPP2.  This document is not an Internet Standards Track 
specification; it is published for informational purposes.


INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC