[Mip4] MIPv4 based flow movement
"Tsirtsis, George" <tsirtsis@qualcomm.com> Fri, 18 August 2006 21:16 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GEBhP-0008Cs-Lw; Fri, 18 Aug 2006 17:16:15 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GEBhO-0008CX-1n; Fri, 18 Aug 2006 17:16:14 -0400
Received: from numenor.qualcomm.com ([129.46.51.58]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GEBhM-0001E1-LY; Fri, 18 Aug 2006 17:16:14 -0400
Received: from magus.qualcomm.com (magus.qualcomm.com [129.46.61.148]) by numenor.qualcomm.com (8.13.6/8.12.5/1.0) with ESMTP id k7ILGAus020285 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Fri, 18 Aug 2006 14:16:10 -0700
Received: from NAEXBR02.na.qualcomm.com (naexbr02.qualcomm.com [10.46.92.109]) by magus.qualcomm.com (8.13.6/8.13.6/1.0) with ESMTP id k7ILG8LJ008652; Fri, 18 Aug 2006 14:16:10 -0700 (PDT)
Received: from NAEX14.na.qualcomm.com ([10.47.5.242]) by NAEXBR02.na.qualcomm.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 18 Aug 2006 14:16:07 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Fri, 18 Aug 2006 14:16:05 -0700
Message-ID: <7EB20EA0938B4D42A2D82689365C9B7A11D9F9@NAEX14.na.qualcomm.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: MIPv4 based flow movement
Thread-Index: AcbDC4QtFV6hSEoLTJy44RBmpi344A==
From: "Tsirtsis, George" <tsirtsis@qualcomm.com>
To: monami6@ietf.org, mip4@ietf.org
X-OriginalArrivalTime: 18 Aug 2006 21:16:07.0350 (UTC) FILETIME=[85346D60:01C6C30B]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc:
Subject: [Mip4] MIPv4 based flow movement
X-BeenThere: mip4@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Mobility for IPv4 <mip4.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:mip4@ietf.org>
List-Help: <mailto:mip4-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mip4>, <mailto:mip4-request@ietf.org?subject=subscribe>
Errors-To: mip4-bounces@ietf.org
Hi, We have published a draft providing a solution for per flow movement in the context of MIPv4. The proposal provides equivalent functionality to the draft-ietf-monami6-multiplecoa-00 and draft-soliman-monami6-flow-binding-01.txt but the design in based on extensions to MIPv4 instead of MIPv6. The draft defines Alternate-CoA and Flow Identification extensions. The later supports IPv4 and IPv6 filters and it is compatible to related NEMOv4 and DSMIPv4 work. You can find the draft at: http://www.ietf.org/internet-drafts/draft-tsirtsis-mip4-flowmove-00.txt To limit cross-posting I would suggest that if you have comments related to the concepts of multiple CoA and per flow movement, you should post them to Monami6 list. If you have comments on the details of how the proposal works over MIPv4 you should send them to the MIP4 list. Regards George P.S.: Abstract Mobile IPv4 allows Mobile Nodes (MN) to create mobility bindings between their Home Address (HoA) and their current Care-of Address (CoA) in a Home Agent (HA) so that the HA can redirect traffic for the MN to its current location. This draft extends MIPv4 so that the binding granularity is on a per flow basis. Extensions are defined to allow the registration of multiple CoAs and the definition of individual flows. Individual flows can then be pointed to the registered CoAs. -- Mip4 mailing list: Mip4@ietf.org Web interface: https://www1.ietf.org/mailman/listinfo/mip4 Charter page: http://www.ietf.org/html.charters/mip4-charter.html Supplemental site: http://www.mip4.org/
- [Mip4] MIPv4 based flow movement Tsirtsis, George
- [Mip4] RE: [Monami6] MIPv4 based flow movement Soliman, Hesham