IETF Logo Mail Archive

[DMM] comments on draft-ietf-dmm-best-practices-gap-analysis-03.txt

<karagian@cs.utwente.nl> Wed, 05 March 2014 08:53 UTC

Return-Path: <karagian@cs.utwente.nl>
X-Original-To: dmm@ietfa.amsl.com
Delivered-To: dmm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8641B1A02C8 for <dmm@ietfa.amsl.com>; Wed, 5 Mar 2014 00:53:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BH4dK5ITTbAS for <dmm@ietfa.amsl.com>; Wed, 5 Mar 2014 00:53:54 -0800 (PST)
Received: from out68-ams.mf.surf.net (out68-ams.mf.surf.net [145.0.1.68]) by ietfa.amsl.com (Postfix) with ESMTP id D643F1A0283 for <dmm@ietf.org>; Wed, 5 Mar 2014 00:53:52 -0800 (PST)
Received: from EXEDGE02.ad.utwente.nl (exedge02.ad.utwente.nl [130.89.5.49]) by outgoing3-ams.mf.surf.net (8.14.4/8.14.4/Debian-4) with ESMTP id s258tadP019602 for <dmm@ietf.org>; Wed, 5 Mar 2014 09:55:37 +0100
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE02.ad.utwente.nl (130.89.5.49) with Microsoft SMTP Server (TLS) id 14.2.328.9; Wed, 5 Mar 2014 09:53:51 +0100
Received: from EXMBX23.ad.utwente.nl ([169.254.3.208]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Wed, 5 Mar 2014 09:53:47 +0100
From: karagian@cs.utwente.nl
To: dmm@ietf.org
Thread-Topic: comments on draft-ietf-dmm-best-practices-gap-analysis-03.txt
Thread-Index: Ac84UGy6KsR1Eb+3Rj2/2gxqiOSSng==
Date: Wed, 05 Mar 2014 08:53:46 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F4335F1@EXMBX23.ad.utwente.nl>
References: <20140214184528.30120.70550.idtracker@ietfa.amsl.com>
In-Reply-To: <20140214184528.30120.70550.idtracker@ietfa.amsl.com>
Accept-Language: nl-NL, en-US
Content-Language: nl-NL
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mimectl: Produced By Microsoft Exchange V14.2.247.1
x-originating-ip: [80.229.76.233]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F4335F1EXMBX23adutwent_"
MIME-Version: 1.0
X-Bayes-Prob: 0.0001 (Score 0, tokens from: utwente-out:default, base:default, @@RPTN)
X-CanIt-Geo: No geolocation information available for 130.89.5.49
X-CanItPRO-Stream: utwente-out:default (inherits from utwente:default, base:default)
X-Canit-Stats-ID: 0bLxITALq - d6007ba59667 - 20140305 (trained as not-spam)
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/n6-sdH6NTcBlwluPfuWPvWgoZEg
Subject: [DMM] comments on draft-ietf-dmm-best-practices-gap-analysis-03.txt
X-BeenThere: dmm@ietf.org
X-Mailman-Version: 2.1.15
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: Wed, 05 Mar 2014 08:53:57 -0000

Hi all,



I have reviewd draft-ietf-dmm-best-practices-gap-analysis-03. The draft is in a good shape, but I have some comments!



Moreover, thanks for addressing some comments that I had on previous versions.



Comment_1: Not sure if it will help to have a table that shows how each of the presented solutions satisfy the DMM requirements



Comment_2: By looking to the gaps that you have listed, I see that some are missing or are hidden in the text.
The gaps that IMO are not currently listed are:



o) lack for support of different deployement models and at the same time lack of exposing mobility states, including binding state, access network parameers, etc, to interwork with other types of technologies.



o) lack of control and data plane separation



Best regards,

Georgios





________________________________
Van: dmm [dmm-bounces@ietf.org] namens internet-drafts@ietf.org [internet-drafts@ietf.org]
Verzonden: vrijdag 14 februari 2014 19:45
To: i-d-announce@ietf.org
Cc: dmm@ietf.org
Onderwerp: [DMM] I-D Action: draft-ietf-dmm-best-practices-gap-analysis-03.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Distributed Mobility Management Working Group of the IETF.

        Title           : Distributed Mobility Management: Current practices and gap analysis
        Authors         : Dapeng Liu
                          Juan Carlos Zuniga
                          Pierrick Seite
                          H Anthony Chan
                          Carlos J. Bernardos
        Filename        : draft-ietf-dmm-best-practices-gap-analysis-03.txt
        Pages           : 25
        Date            : 2014-02-14

Abstract:
   The present document analyzes deployment practices of existing IP
   mobility protocols in a distributed mobility management environment.
   It then identifies existing limitations when compared to the
   requirements defined for a distributed mobility management solution.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-dmm-best-practices-gap-analysis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-dmm-best-practices-gap-analysis-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-dmm-best-practices-gap-analysis-03


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

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

v2.23.0 | Report a Bug | By Email