RFC 5265 on Mobile IPv4 Traversal across IPsec-Based VPN Gateways

rfc-editor@rfc-editor.org Tue, 17 June 2008 22:16 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 834B33A6ACA; Tue, 17 Jun 2008 15:16:45 -0700 (PDT)
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 4E5383A6813; Tue, 17 Jun 2008 15:16:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.756
X-Spam-Level:
X-Spam-Status: No, score=-16.756 tagged_above=-999 required=5 tests=[AWL=0.243, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, USER_IN_DEF_WHITELIST=-15]
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 aLn+4L8ub6YP; Tue, 17 Jun 2008 15:16:37 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id CDF703A679C; Tue, 17 Jun 2008 15:16:35 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id D186A137621; Tue, 17 Jun 2008 15:17:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5265 on Mobile IPv4 Traversal across IPsec-Based VPN Gateways
From: rfc-editor@rfc-editor.org
Message-Id: <20080617221719.D186A137621@bosco.isi.edu>
Date: Tue, 17 Jun 2008 15:17:19 -0700
Cc: mip4@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <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/pipermail/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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        
        RFC 5265

        Title:      Mobile IPv4 Traversal across IPsec-Based 
                    VPN Gateways 
        Author:     S. Vaarala, E. Klovning
        Status:     Standards Track
        Date:       June 2008
        Mailbox:    sami.vaarala@iki.fi, 
                    espen@birdstep.com
        Pages:      39
        Characters: 86254
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mip4-vpn-problem-solution-05.txt

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

This document outlines a solution for the Mobile IPv4 (MIPv4) and
IPsec coexistence problem for enterprise users.  The solution
consists of an applicability statement for using Mobile IPv4 and
IPsec for session mobility in corporate remote access scenarios, and
a required mechanism for detecting the trusted internal network
securely.  [STANDARDS TRACK]

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

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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-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
USC/Information Sciences Institute


_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/ietf-announce