Re: [DMM] Comments on draft-patil-dmm-issues-and-approaches2dmm-00
<Basavaraj.Patil@nokia.com> Tue, 06 March 2012 22:05 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 660BE21E8013 for <dmm@ietfa.amsl.com>; Tue, 6 Mar 2012 14:05:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.014
X-Spam-Level:
X-Spam-Status: No, score=-105.014 tagged_above=-999 required=5 tests=[AWL=1.585, 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 ZUUlg88Hiv7B for <dmm@ietfa.amsl.com>; Tue, 6 Mar 2012 14:05:19 -0800 (PST)
Received: from mgw-sa01.nokia.com (smtp.nokia.com [147.243.1.47]) by ietfa.amsl.com (Postfix) with ESMTP id 3BD8821F8624 for <dmm@ietf.org>; Tue, 6 Mar 2012 14:05:18 -0800 (PST)
Received: from vaebh101.NOE.Nokia.com (vaebh101.europe.nokia.com [10.160.244.22]) by mgw-sa01.nokia.com (Switch-3.4.4/Switch-3.4.4) with ESMTP id q26M5EDK018123; Wed, 7 Mar 2012 00:05:14 +0200
Received: from smtp.mgd.nokia.com ([65.54.30.61]) by vaebh101.NOE.Nokia.com over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Wed, 7 Mar 2012 00:05:14 +0200
Received: from 008-AM1MPN1-073.mgdnok.nokia.com ([169.254.3.150]) by 008-AM1MMR1-006.mgdnok.nokia.com ([65.54.30.61]) with mapi id 14.01.0355.003; Tue, 6 Mar 2012 23:05:13 +0100
From: Basavaraj.Patil@nokia.com
To: Peter.McCann@huawei.com, carlw@mcsr-labs.org, jouni.nospam@gmail.com
Thread-Topic: Comments on draft-patil-dmm-issues-and-approaches2dmm-00
Thread-Index: Acz74tbaKHHVfQwFSOaADK0zCMsIq///j1+A
Date: Tue, 06 Mar 2012 22:05:12 +0000
Message-ID: <CB7BE614.1BA79%basavaraj.patil@nokia.com>
In-Reply-To: <5963DDF1F751474D8DEEFDCDBEE43AE716447E36@dfweml504-mbx>
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.40]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <A568FA42FE8F75449DC6B6C790837B5C@mgd.nokia.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginalArrivalTime: 06 Mar 2012 22:05:14.0246 (UTC) FILETIME=[35045260:01CCFBE5]
X-Nokia-AV: Clean
Cc: dmm@ietf.org
Subject: Re: [DMM] Comments on draft-patil-dmm-issues-and-approaches2dmm-00
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: Tue, 06 Mar 2012 22:05:23 -0000
Hi Pete, Thanks for your review and comments. Let me come back to you with responses in the next day or two. -Raj On 3/6/12 3:48 PM, "ext Peter McCann" <Peter.McCann@huawei.com> wrote: >Hi, Raj, Carl, and Jouni, > >I have some comments on draft-patil-dmm-issues-and-approaches2dmm-00. > >I agree with most of Section 4, "Issues with current mobility models". >However, >I'd like to point out that existing networks are not just centralized in >the manner >you point out, they also tend to have a hierarchical structure, e.g., the >S-GW/P-GW split in 3GPP EPC. Therefore, the issue you outline in Section >4.3 >("Inefficient Routing and signaling overhead") is not quite true of the >3GPP >EPC, which can handle many mobility events in a localized manner similar >to >HMIP. > >The first paragraph of Section 7 talks about source address selection, >and the >need to modify applications so that they request the kind of address that >they >want. I tend to think that applications will remain unmodified for some >time >to come; however, most applications fit into the paradigm of opening >short-lived >connections to a server and could be accommodated with some sort of >automatic >handling in the MN's IP stack. > >I found the last paragraph of Section 7 quite interesting. I too think >that there >is an important piece missing that you call "seamless mobility anchor >relocation". >I think that the use of an interior routing protocol is spot on. In >fact, if you >read draft-mccann-dmm-flatarch-00, I propose just that. I think we can >use such >an anchor relocation protocol to make each access router in an autonomous >system >(or smaller region of an autonomous system) a temporary anchor for a >given prefix. >In my draft I propose running I-BGP on each AR and sending BGP UPDATES >into the >network upon localized mobility events. Such a protocol can also be used >as a >substitute for the proxy ND technique that is currently specified to >"grab" the >MN's packets at the HA. By using a routing protocol, the HA can reach >across >several routing hops so it doesn't necessarily need to be on the home >link (which >can be the first AR to which the MN attached). I think this would also >enable us >to unify the authentication protocols used at the AR with the >authentication protocol >used at the HA. The ARs are just like HAs that don't have to tunnel the >data anywhere >because the MN is locally connected. > >Does it make sense to you? > >-- >Peter J. McCann >Huawei Technologies (USA) >Peter.McCann@Huawei.com >+1 908 541 3563 >Rm. C-0105, 400 Crossings Blvd. (2nd floor), Bridgewater, NJ 08807-2863 >USA > >
- Re: [DMM] Comments on draft-patil-dmm-issues-and-… Basavaraj.Patil
- [DMM] Comments on draft-patil-dmm-issues-and-appr… Peter McCann
- Re: [DMM] Comments on draft-patil-dmm-issues-and-… jouni korhonen
- Re: [DMM] Comments on draft-patil-dmm-issues-and-… Peter McCann
- Re: [DMM] Comments on draft-patil-dmm-issues-and-… jouni korhonen
- Re: [DMM] Comments on draft-patil-dmm-issues-and-… Peter McCann