Re: [MEXT] The first proposal for the DMM charter

<pierrick.seite@orange.com> Tue, 20 December 2011 09:51 UTC

Return-Path: <pierrick.seite@orange.com>
X-Original-To: mext@ietfa.amsl.com
Delivered-To: mext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E67C21F8AAF for <mext@ietfa.amsl.com>; Tue, 20 Dec 2011 01:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.249
X-Spam-Level:
X-Spam-Status: No, score=-6.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
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 IF+ZzXr55bJ2 for <mext@ietfa.amsl.com>; Tue, 20 Dec 2011 01:51:05 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by ietfa.amsl.com (Postfix) with ESMTP id CB67121F8B1B for <mext@ietf.org>; Tue, 20 Dec 2011 01:51:04 -0800 (PST)
Received: from r-mail1.rd.francetelecom.com (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id 1D332A445CB; Tue, 20 Dec 2011 10:50:42 +0100 (CET)
Received: from ftrdsmtp1.rd.francetelecom.fr (unknown [10.192.128.46]) by r-mail1.rd.francetelecom.com (Postfix) with ESMTP id 7FB68DE4AC1; Mon, 19 Dec 2011 11:59:12 +0100 (CET)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.4675); Mon, 19 Dec 2011 11:57:46 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Mon, 19 Dec 2011 11:57:44 +0100
Message-ID: <843DA8228A1BA74CA31FB4E111A5C46202169B1B@ftrdmel0.rd.francetelecom.fr>
In-Reply-To: <80F8FA76-88EF-4986-AE9C-DBCFCA027DB9@gmail.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [MEXT] The first proposal for the DMM charter
Thread-Index: Acy90024+f9JEbUiTneED4RGoCt71QAaInuQ
References: <8CAD2158-A0AC-4767-9DDC-857536E26DC6@gmail.com> <80F8FA76-88EF-4986-AE9C-DBCFCA027DB9@gmail.com>
From: <pierrick.seite@orange.com>
To: <jouni.nospam@gmail.com>, <mext@ietf.org>
X-OriginalArrivalTime: 19 Dec 2011 10:57:46.0631 (UTC) FILETIME=[0A8EB970:01CCBE3D]
Cc: julien.ietf@gmail.com, jari.arkko@piuha.net
Subject: Re: [MEXT] The first proposal for the DMM charter
X-BeenThere: mext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Mobile IPv6 EXTensions WG <mext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mext>, <mailto:mext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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>
X-List-Received-Date: Tue, 20 Dec 2011 09:51:06 -0000

Hi Jouni,

It seems that I've some trouble with my mail box.... Please see below my comments sent on Friday...

Pierrick

> -----Message d'origine-----
> De : mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] De la part de
> jouni korhonen
> Envoyé : dimanche 18 décembre 2011 23:21
> À : mext@ietf.org
> Cc : julien.ietf@gmail.com Laganier; jouni korhonen; Jari Arkko
> Objet : Re: [MEXT] The first proposal for the DMM charter
> 
> 
> Folks,
> 
> Based of the "feedback" can I assume folks are mostly happy with the
> current text?
> 
> - Jouni
> 


---------------------------------------- 

Hi Jouni & Julien,

This charter looks good. However, please see inline few suggestions for modifications.

Thanks,
Pierrick

> -----Message d'origine-----
> De : mext-bounces@ietf.org [mailto:mext-bounces@ietf.org] De la part 
> de jouni korhonen Envoyé : mercredi 14 décembre 2011 09:54 À : 
> mext@ietf.org Cc : julien.ietf@gmail.com Laganier; jouni korhonen; 
> Jari Arkko Objet : [MEXT] The first proposal for the DMM charter
> 
> Folks,
> 
> We have been working on a charter text from DMM based on the initial 
> goal setting and the input we received during the Taipei meeting. Note 
> that this is the first draft and now we are soliciting for input.
> 
> - Jouni & Julien
> 
> 
> ----------------------------------------------------------------------
> -
> --
> 
> Distributed Mobility Management (DMM)
> -------------------------------------
> 
> Charter
> 
>  Current Status: Active
> 
>  Chairs:
>      Julien Laganier <julien.ietf@gmail.com>;
>      Jouni Korhonen <jouni.nospam@gmail.com>;
> 
>  Internet Area Directors:
>      Ralph Droms <rdroms.ietf@gmail.com>;
>      Jari Arkko <jari.arkko@piuha.net>;
> 
>  Internet Area Advisor:
>      Jari Arkko <jari.arkko@piuha.net>;
> 
>  Mailing Lists:
>      General Discussion: mext@ietf.org
>      To Subscribe:       https://www.ietf.org/mailman/listinfo/mext
>      Archive:            http://www.ietf.org/mail-archive/web/mext
> 
> Description of Working Group:
> 
>   The Distributed Mobility Management (DMM) working group specifies IP
>   mobility, access network and routing solutions, which allow for
>   setting up IP networks so that traffic is distributed in an
>   optimal way and does not rely on centrally deployed anchors to manage
>   IP mobility sessions. The distributed mobility management solutions
>   aim for transparency above the IP layer, including maintenance of
>   active transport level sessions as mobile hosts or entire mobile
>   networks change their point of attachment to the Internet.
> 
>   The protocol solutions should be enhancements to existing IP mobility
>   protocols, either host- or network-based, such as Mobile IPv6
>   [RFC6275, 5555], Proxy Mobile IPv6 [RFC5213, 5844] and
>   NEMO [RFC3963]. 

This sentence gives the impression that extensions to MIP/PMIP will be necessary, i.e. here, the charter seems put extensions as a requirement (I don't think it is the goal :-)). It appears to be inconsistent with the two steps approach suggested by the work items: best current practices (without protocol modification), then, if necessary, specify extensions. So, I'd suggest to reword as follows:

The protocol solutions should be based on existing IP mobility
  Protocols and related mechanisms, either host- or network-based, such as Mobile IPv6
   [RFC6275, 5555], Proxy Mobile IPv6 [RFC5213, 5844] and
  NEMO [RFC3963]. 

Alternatively, the distributed mobility management
>   solution can be transparent to any underlying IP mobility protocol.
>   Although the maintenance of stable home address(es) and/or prefix(es)
>   and upper level sessions is a desirable goal when mobile 
> hosts/routers
>   change their point of attachment to the Internet, it is not a strict
>   requirement. Mobile hosts/routers should not assume that IP
>   addressing including home address(es) and/or home network prefix(es)
>   remain the same throughout the entire upper level session lifetime.
> 

I suggest to add the following statement:

Mobile hosts/routers should not assume always-on mobility support.

>   The distributed mobility management solutions primarily target IPv6
>   Deployment and should not be tailored specifically to support IPv4,
>   in particular in situations where private IPv4 addresses and/or NATs
>   are used. At least IPv6 is assumed to be present in both the mobile
>   host/router and the access networks. Independent of the distributed
>   mobility management solution, backward compatibility must be
>   maintained. If the network or the mobile host/router do not support
>   the distributed mobility management enabling protocol, nothing should
>   break.
> 
> Work items related to the distributed mobility management include:
> 
>   o Solution Requirements: Define precisely the problem of distributed
>     mobility management and identity the requirements for a distributed
>     mobility management solution.
> 
>   o Best practices and Gap Analysis: Document best practices for the
>     deployment of existing mobility protocols in a distributed mobility
>     management environment and identify the limitations of each such
>     approach with respect to fulfillment of the solution requirements.
> 
>   o If limitations are identified as part of the above deliverable,
>     specify extensions to existing protocols that removes these
>     limitations within a distributed mobility management environment.
> 

IMHO, the gap analysis should not be part of the best current practices. The BCP may stress some limitations but an exhaustive gap analysis should be the motivation for protocols extensions. So, I suggest to rearrange work items as follows: 

   o Best practices: Document best practices for the
     deployment of existing mobility protocols in a distributed mobility
     management environment.


 o  Gap Analysis and extensions: identify the limitations of each such
    approach with respect to fulfillment of the solution requirements. If limitations are,
    specify extensions to existing protocols that removes these
    limitations within a distributed mobility management environment.


> Goals and Milestones:
> 
>   Aug 2012 - Submit I-D 'Solution Requirements' as a working
>              group document. To be Informational RFC.
>   Aug 2012 - Submit I-D 'Best practices and Gap Analysis' as a working
>              group document. To be Informational RFC.

As explained above, I think the gap analysis should not be part of the BCP. So, this goal should be:

   Aug 2012 - Submit I-D 'Best practices' as a working
              group document. To be Informational RFC.

>   Nov 2012 - Evaluate the need for additional working group document(s)
>              for extensions to fill the identified gaps.

Extensions should be motivated by a complete gap analysis. So, this goal should be:

Nov 2012 - Gap analysis and evaluation for the need of additional working group document(s)
            for extensions to fill the identified gaps.

>   Jan 2013 - Submit I-D 'Solution Requirements' to the IESG for
>              consideration as an Informational RFC.
>   Jan 2013 - Submit I-D 'Best practices and Gap Analysis' to the IESG 
> for
>              consideration as an Informational RFC.
>   Mar 2013 - Conclude the working group or re-charter.
> 
> 
> _______________________________________________
> MEXT mailing list
> MEXT@ietf.org
> https://www.ietf.org/mailman/listinfo/mext