IETF Logo Mail Archive

Re: [MEXT] [Mobopts] MIPv6 IPsec Route Optimization (IRO)

"Haddad, Wassim Michel" <whaddad@qualcomm.com> Mon, 17 November 2008 20:57 UTC

Return-Path: <mext-bounces@ietf.org>
X-Original-To: mext-archive@optimus.ietf.org
Delivered-To: ietfarch-mext-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E1E4E3A68C5; Mon, 17 Nov 2008 12:57:28 -0800 (PST)
X-Original-To: mext@core3.amsl.com
Delivered-To: mext@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 062B83A6A4C for <mext@core3.amsl.com>; Mon, 17 Nov 2008 12:57:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 mczvFR7Lv5vb for <mext@core3.amsl.com>; Mon, 17 Nov 2008 12:57:26 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by core3.amsl.com (Postfix) with ESMTP id B65943A6876 for <mext@ietf.org>; Mon, 17 Nov 2008 12:57:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=whaddad@qualcomm.com; q=dns/txt; s=qcdkim; t=1226955446; x=1258491446; h=from:to:cc:date:subject:thread-topic:thread-index: message-id:in-reply-to:accept-language:content-language: x-ms-has-attach:x-ms-tnef-correlator:acceptlanguage: content-type:mime-version:x-ironport-av; z=From:=20"Haddad,=20Wassim=20Michel"=20<whaddad@qualcomm. com>|To:=20Arnaud=20Ebalard=20<arno@natisbad.org>,=20IETF =20MEXT=20WG=20ML=20<mext@ietf.org>|CC:=20Mobopts=20IRTF =20WG=20ML=20<mobopts@irtf.org>,=0D=0A=20=20=20=20=20=20 =20=20"Haddad,=20Wassim=20Michel"=0D=0A=09<whaddad@qualco mm.com>|Date:=20Mon,=2017=20Nov=202008=2012:57:23=20-0800 |Subject:=20Re:=20[Mobopts]=20MIPv6=20IPsec=20Route=20Opt imization=20(IRO)|Thread-Topic:=20[Mobopts]=20MIPv6=20IPs ec=20Route=20Optimization=20(IRO)|Thread-Index:=20AclIjx3 hkebhNUm7Qh6vLV5ld4PmOwAZ/i2x|Message-ID:=20<C54744E3.6A5 8%whaddad@qualcomm.com>|In-Reply-To:=20<87d4guwy7y.fsf@na tisbad.org>|Accept-Language:=20en-US|Content-Language:=20 en|X-MS-Has-Attach:|X-MS-TNEF-Correlator:|acceptlanguage: =20en-US|Content-Type:=20multipart/alternative=3B=0D=0A =09boundary=3D"_000_C54744E36A58whaddadqualcommcom_" |MIME-Version:=201.0|X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5 100,188,5436"=3B=20a=3D"13206048"; bh=xt+AoEUMr2bXaDVnTlDyZNuE+/l837GhX72IOLuQ8KE=; b=DPWTTPsJo8iZkwA8Pzmv/Rm94KX65gaDWPL88qRQBMjkdCYulPx+1QCM lT2hKIJ1bcC6RJ+uN9ce4j4eoyRVVl9nAA8Iv5wm+OPITc98qmdLm944v hNNUR92sk1cpl/Djh1ypURkpH5KxytOXc9zCkUGxp1uQULDD9B1HBDhIk M=;
X-IronPort-AV: E=McAfee;i="5100,188,5436"; a="13206048"
Received: from pdmz-ns-mip.qualcomm.com (HELO numenor.qualcomm.com) ([199.106.114.10]) by wolverine02.qualcomm.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Nov 2008 12:57:26 -0800
Received: from msgtransport04.qualcomm.com (msgtransport04.qualcomm.com [129.46.61.156]) by numenor.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id mAHKvPBY028493 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 17 Nov 2008 12:57:26 -0800
Received: from nasanexhub04.na.qualcomm.com (nasanexhub04.qualcomm.com [129.46.134.222]) by msgtransport04.qualcomm.com (8.14.2/8.14.2/1.0) with ESMTP id mAHKvPfs011627 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 17 Nov 2008 12:57:25 -0800
Received: from NASANEXMB01.na.qualcomm.com ([129.46.50.85]) by nasanexhub04.na.qualcomm.com ([129.46.134.222]) with mapi; Mon, 17 Nov 2008 12:57:24 -0800
From: "Haddad, Wassim Michel" <whaddad@qualcomm.com>
To: Arnaud Ebalard <arno@natisbad.org>, IETF MEXT WG ML <mext@ietf.org>
Date: Mon, 17 Nov 2008 12:57:23 -0800
Thread-Topic: [Mobopts] MIPv6 IPsec Route Optimization (IRO)
Thread-Index: AclIjx3hkebhNUm7Qh6vLV5ld4PmOwAZ/i2x
Message-ID: <C54744E3.6A58%whaddad@qualcomm.com>
In-Reply-To: <87d4guwy7y.fsf@natisbad.org>
Accept-Language: en-US
Content-Language: en
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
MIME-Version: 1.0
Cc: Mobopts IRTF WG ML <mobopts@irtf.org>
Subject: Re: [MEXT] [Mobopts] MIPv6 IPsec Route Optimization (IRO)
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/mext>
List-Post: <mailto:mext@ietf.org>
List-Help: <mailto:mext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mext>, <mailto:mext-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1426650434=="
Sender: mext-bounces@ietf.org
Errors-To: mext-bounces@ietf.org

On 11/17/08 3:30 AM, "Arnaud Ebalard" <arno@natisbad.org> wrote:

Hi,

Sorry for crossposting but the topic discussed in the draft may be of
interest for people of the 3 lists.

> IETF I-D Submission Tool <idsubmission@ietf.org> writes:
>
> A new version of I-D, draft-ebalard-mext-ipsec-ro-00.txt has been
> successfuly submitted by Arnaud Ebalard and posted to the IETF
> repository.
>
> Filename:      draft-ebalard-mext-ipsec-ro
> Revision:      00
> Title:         Mobile IPv6 IPsec Route Optimization (IRO)
> Creation_date: 2008-11-17
> WG ID:         Independent Submission
> Number_of_pages: 44
>
> Abstract:
>
> This memo specifies an improved alternate route optimization procedure
> for Mobile IPv6 designed specifically for environments where IPsec is
> used between peers (most probably with IKE). The replacement of the
> complex Return Routability procedure for a simple mechanism and the
> removal of HAO and RH2 extensions from exchanged packets result in
> performance and security improvements.

I have just submitted a new I-D [1] which certainly requires an
introduction (and disclaimer): it specifies a MIPv6 Route Optimization
procedure *dedicated* to environments where IPsec/IKE is used between
peers (MN-HA, MN-CN, MN-MN) for protecting both signaling and data
traffic.

Some of the improvements provided by this "IPsec Route Optimization"
mechanism (IRO) are also proposed for the IPsec communications between
the MN and its HA.

Among the features provided by IRO (introduction of the document as
a more accurate list):

  * Complete removal of RH2 and HAO (resulting in simplified packet
    handling on both sides and possibly better compatibility with
    filtering implemented in the network),

=> You can have complete removal of both options without introducing a new RO mode.
Please check http://www.ietf.org/internet-drafts/draft-haddad-mipshop-tunneling-optimization-01.txt


Regards,

Wassim H.




_______________________________________________
MEXT mailing list
MEXT@ietf.org
https://www.ietf.org/mailman/listinfo/mext

v2.23.0 | Report a Bug | By Email