[DMM] FW: New Version Notification for draft-patil-dmm-issues-and-approaches2dmm-00.txt

<Basavaraj.Patil@nokia.com> Mon, 05 March 2012 19:28 UTC

Return-Path: <Basavaraj.Patil@nokia.com>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDA7E21F8931 for <dmm@ietfa.amsl.com>; Mon, 5 Mar 2012 11:28:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.978
X-Spam-Level:
X-Spam-Status: No, score=-104.978 tagged_above=-999 required=5 tests=[AWL=1.621, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 q-VRMVPxCKCu for <dmm@ietfa.amsl.com>; Mon, 5 Mar 2012 11:28:01 -0800 (PST)
Received: from mgw-sa02.nokia.com (smtp.nokia.com [147.243.1.48]) by ietfa.amsl.com (Postfix) with ESMTP id C714C21F8930 for <dmm@ietf.org>; Mon, 5 Mar 2012 11:27:54 -0800 (PST)
Received: from vaebh102.NOE.Nokia.com (in-mx.nokia.com [10.160.244.23]) by mgw-sa02.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id q25JRrFS031440 for <dmm@ietf.org>; Mon, 5 Mar 2012 21:27:53 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.20]) by vaebh102.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Mon, 5 Mar 2012 21:27:53 +0200
Received: from 008-AM1MPN1-073.mgdnok.nokia.com ([169.254.3.150]) by 008-AM1MMR1-011.mgdnok.nokia.com ([65.54.30.20]) with mapi id 14.01.0355.003; Mon, 5 Mar 2012 20:27:52 +0100
From: Basavaraj.Patil@nokia.com
To: dmm@ietf.org
Thread-Topic: New Version Notification for draft-patil-dmm-issues-and-approaches2dmm-00.txt
Thread-Index: AQHM+wYP1WX/mw6vJEaproFE99ew5A==
Date: Mon, 05 Mar 2012 19:27:52 +0000
Message-ID: <CB7A6FB8.1B8FC%basavaraj.patil@nokia.com>
In-Reply-To: <20120305192649.8275.39953.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.14.0.111121
x-originating-ip: [172.19.59.18]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <BA7FFFF4B6F8DD4EAAC622C72FC4EDCC@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 05 Mar 2012 19:27:53.0575 (UTC) FILETIME=[0F867F70:01CCFB06]
X-Nokia-AV: Clean
Subject: [DMM] FW: New Version Notification for draft-patil-dmm-issues-and-approaches2dmm-00.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Distributed Mobility Management Working Group <dmm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dmm>, <mailto:dmm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dmm>
List-Post: <mailto:dmm@ietf.org>
List-Help: <mailto:dmm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dmm>, <mailto:dmm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Mar 2012 19:28:01 -0000

>A new version of I-D, draft-patil-dmm-issues-and-approaches2dmm-00.txt
>has been successfully submitted by Basavaraj Patil and posted to the IETF
>repository.
>
>Filename:	 draft-patil-dmm-issues-and-approaches2dmm
>Revision:	 00
>Title:		 Approaches to Distributed mobility management using Mobile IPv6
>and its extensions
>Creation date:	 2012-03-05
>WG ID:		 Individual Submission
>Number of pages: 13
>
>Abstract:
>   Mobility solutions at the IP layer have been specified in the IETF
>   for IPv4 and IPv6.  These solutions include host and network based
>   mobility.  All of the mobility protocols enable IP session continuity
>   by providing the mobile host with an IP address or prefix that
>   remains constant even as the host moves and attaches to different
>   access networks and points of attachment.  Mobile hosts are anchored
>   at a gateway via a tunnel and the address/prefix provided to the host
>   via the gateway remains unchanged across mobility events.  All IP
>   sessions initiated or terminated at a mobile host are anchored via
>   the gateway.  A gateway centric approach such as Mobile IP, raises
>   certain concerns in terms of cost and efficiency.  A mobility model
>   wherein the network entities enabling mobility are distributed is a
>   way of alleviating the concerns of a gateway centric approach.  This
>   document considers ways to alleviate anchored mobility issues with
>   approaches that could be considered in a deployment.
>
>                  
>