Re: [DMM] WGLC #2 for draft-ietf-dmm-best-practices-gap-analysis-04

h chan <h.anthony.chan@huawei.com> Thu, 03 July 2014 20:07 UTC

Return-Path: <h.anthony.chan@huawei.com>
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 AA0FD1A04F1 for <dmm@ietfa.amsl.com>; Thu, 3 Jul 2014 13:07:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] 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 Y7vNfK4hOoQe for <dmm@ietfa.amsl.com>; Thu, 3 Jul 2014 13:07:54 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B3B3E1A0384 for <dmm@ietf.org>; Thu, 3 Jul 2014 13:07:53 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml403-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJP43707; Thu, 03 Jul 2014 20:07:52 +0000 (GMT)
Received: from SZXEML412-HUB.china.huawei.com (10.82.67.91) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 3 Jul 2014 21:07:50 +0100
Received: from szxeml557-mbx.china.huawei.com ([169.254.5.136]) by szxeml412-hub.china.huawei.com ([10.82.67.91]) with mapi id 14.03.0158.001; Fri, 4 Jul 2014 04:07:44 +0800
From: h chan <h.anthony.chan@huawei.com>
To: "pierrick.seite@orange.com" <pierrick.seite@orange.com>, Jouni Korhonen <jouni.nospam@gmail.com>, Charlie Perkins <charles.perkins@earthlink.net>, "dmm@ietf.org" <dmm@ietf.org>
Thread-Topic: [DMM] WGLC #2 for draft-ietf-dmm-best-practices-gap-analysis-04
Thread-Index: AQHPfuP8FzQpamyJ+EiTh4KXY9xNKptevHAAgAKLb4CAAOWAgIAsyDtw
Date: Thu, 03 Jul 2014 20:07:44 +0000
Message-ID: <6E31144C030982429702B11D6746B98C3711BA46@szxeml557-mbx.china.huawei.com>
References: <5382B78C.5060409@gmail.com> <538D4E54.90205@gmail.com> <538D5F0A.3060006@earthlink.net> <538F8181.5000403@gmail.com> <3950_1401956609_53902901_3950_8205_1_81C77F07008CA24F9783A98CFD706F7114255588@PEXCVZYM12.corporate.adroot.infra.ftgroup>
In-Reply-To: <3950_1401956609_53902901_3950_8205_1_81C77F07008CA24F9783A98CFD706F7114255588@PEXCVZYM12.corporate.adroot.infra.ftgroup>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.192.11.218]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/dmm/W45xXb-bua0x0LiLhg4NXnTYCxc
Cc: "dmm-chairs@tools.ietf.org" <dmm-chairs@tools.ietf.org>
Subject: Re: [DMM] WGLC #2 for draft-ietf-dmm-best-practices-gap-analysis-04
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: Thu, 03 Jul 2014 20:07:58 -0000

I also like to try more generic wording. How about the following:

   2.  Internetwork Location Information (LI) function: managing and
       keeping track of the internetwork location of an MN.  The
       location information may be a binding of the IP advertised
       address/prefix (e.g., HoA or HNP) to the IP routing address of
       the MN or of a node that can forward packets destined to the MN.
       It is a control plane function.

       In a client-server protocol model, location information query and update
       messages may be exchanged between a location information client
       (LIc) and a location information server (LIs).

   3.  Forwarding Management (FM) function: packet interception and
       forwarding to/from the IP address/prefix assigned to the MN,
       based on the internetwork location information, either to the
       destination or to some other network element that knows how to
       forward the packets to their destination.

       FM may optionally be split into the control plane (FM-CP) and
       data plane (FM-DP).

They are two basic functions of a network: to process information and to forward. It also specifically includes "binding" in the information. 

H Anthony Chan

-----Original Message-----
From: dmm [mailto:dmm-bounces@ietf.org] On Behalf Of pierrick.seite@orange.com
Sent: Thursday, June 05, 2014 3:23 AM
To: Jouni Korhonen; Charlie Perkins; dmm@ietf.org
Cc: dmm-chairs@tools.ietf.org
Subject: Re: [DMM] WGLC #2 for draft-ietf-dmm-best-practices-gap-analysis-04

Hi,

Just to explain why we chose the term "Location management" instead of "binding management": 

Actually, we have considered that "binding management" has too much IP mobility flavor and we wanted something more generic. BTW, of course, LM refers to IP location management...  "binding management" is fine but it may implicitly lead the reader to consider only IP mobility protocols... So,  we use "Location management" to be more generic and open the door to other mobility management mechanisms. That said, I'll not oppose to use "binding management" if there is a group consensus.

Pierrick

>-----Message d'origine-----
>De : dmm [mailto:dmm-bounces@ietf.org] De la part de Jouni Korhonen 
>Envoyé : mercredi 4 juin 2014 22:29 À : Charlie Perkins; dmm@ietf.org 
>Cc : dmm-chairs@tools.ietf.org Objet : Re: [DMM] WGLC #2 for 
>draft-ietf-dmm-best-practices-gap-analysis-
>04
>
>
>Charlie,
>
>Right, sorry for missing these.
>
>- jouni
>
>
>6/3/2014 8:37 AM, Charlie Perkins kirjoitti:
>>
>> Hello Jouni,
>>
>> I communicated three issues:
>>
>> - The gap does not explain the gaps between the requirements and
>>      FMIP / [seamoby] documents / [hokey]
>> - The document does not explain the relevance of the SIPTO example
>>      in fulfilling the requirements.  In fact, SIPTO has "limited mobility
>>      support".
>> - The document uses terminology "LMs" and "LMc" that could be
>>      improved.  Almost every existing IETF approach refers to some sort
>>      of "binding management", and it would be better to stay aligned
>>      with that.  This is especially true lately, since "location 
>> management"
>>      is relevant to advertisements and even surveillance.
>>
>> Regards,
>> Charlie P.
>>
>>
>> On 6/2/2014 9:25 PM, Jouni Korhonen wrote:
>>> Folks,
>>>
>>> The WGLC has ended for this I-D. There was one comment on the list:
>>> http://www.ietf.org/mail-archive/web/dmm/current/msg01152.html
>>>
>>> I also sent few editorial/typo correction comments offline to the 
>>> authors while doing my review for the proto write-up.
>>>
>>> We take the I-D passed the WGLC #2 but a new quick revision to 
>>> include the two comments is needed before we ship the I-D out of the
>WG.
>>>
>>> - Jouni (as a DMM co-chair)
>>>
>>>
>>> 5/26/2014 6:39 AM, Jouni Korhonen kirjoitti:
>>>> Folks,
>>>>
>>>> This email starts a one week WGLC #2 for 
>>>> draft-ietf-dmm-best-practices-gap-analysis-04. Issue you comments 
>>>> to the mailing list and place possible tickets to the issue tracker.
>>>> There are quite a few changed mainly to tackle Charlie's comments.
>>>>
>>>> The WGLC ends 2ns June 2014 EOB (EEST). Silence is accounted as an 
>>>> acceptance for the content.
>>>>
>>>> - Jouni (as a DMM co-chair)
>>>
>>> _______________________________________________
>>> dmm mailing list
>>> dmm@ietf.org
>>> https://www.ietf.org/mailman/listinfo/dmm
>>>
>>
>
>_______________________________________________
>dmm mailing list
>dmm@ietf.org
>https://www.ietf.org/mailman/listinfo/dmm

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

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