RFC 6521 on Home Agent-Assisted Route Optimization between Mobile IPv4 Networks

rfc-editor@rfc-editor.org Thu, 01 March 2012 16:12 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18C7221F8B74; Thu, 1 Mar 2012 08:12:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.275
X-Spam-Level:
X-Spam-Status: No, score=-102.275 tagged_above=-999 required=5 tests=[AWL=0.325, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mGVyJbz3+IUg; Thu, 1 Mar 2012 08:12:50 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 9D68E21F8B6E; Thu, 1 Mar 2012 08:12:50 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id F0283B1E006; Thu, 1 Mar 2012 08:07:10 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6521 on Home Agent-Assisted Route Optimization between Mobile IPv4 Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20120301160710.F0283B1E006@rfc-editor.org>
Date: Thu, 01 Mar 2012 08:07:10 -0800
Cc: mip4@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Thu, 01 Mar 2012 16:12:51 -0000

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

        
        RFC 6521

        Title:      Home Agent-Assisted Route Optimization between 
                    Mobile IPv4 Networks 
        Author:     A. Makela, J. Korhonen
        Status:     Experimental
        Stream:     IETF
        Date:       February 2012
        Mailbox:    antti.t.makela@iki.fi, 
                    jouni.nospam@gmail.com
        Pages:      53
        Characters: 123256
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-nemo-haaro-07.txt

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

This document describes a home agent-assisted route optimization
functionality for the IPv4 Network Mobility Protocol.  The function
is designed to facilitate optimal routing in cases where all nodes
are connected to a single home agent; thus, the use case is route
optimization within a single organization or similar entity.  The
functionality enables the discovery of eligible peer nodes (based on
information received from the home agent) and their network prefixes,
and the establishment of a direct tunnel between such nodes.
This document defines an Experimental Protocol for the Internet
community.

This document is a product of the Mobility for IPv4 Working Group of the IETF.


EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community.  It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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