Re: [multimob] I-D Action:draft-ietf-multimob-fmipv6-pfmipv6-multicast-01.txt

<karagian@cs.utwente.nl> Tue, 01 October 2013 06:06 UTC

Return-Path: <karagian@cs.utwente.nl>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBD721F995F for <multimob@ietfa.amsl.com>; Mon, 30 Sep 2013 23:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.797
X-Spam-Level:
X-Spam-Status: No, score=0.797 tagged_above=-999 required=5 tests=[AWL=-1.300, BAYES_50=0.001, HELO_EQ_NL=0.55, HOST_EQ_NL=1.545, HTML_MESSAGE=0.001]
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 4DkNRyGHOyAD for <multimob@ietfa.amsl.com>; Mon, 30 Sep 2013 23:06:33 -0700 (PDT)
Received: from EXEDGE01.ad.utwente.nl (exedge01.ad.utwente.nl [130.89.5.48]) by ietfa.amsl.com (Postfix) with ESMTP id 5713C21F995B for <multimob@ietf.org>; Mon, 30 Sep 2013 23:06:31 -0700 (PDT)
Received: from EXHUB02.ad.utwente.nl (130.89.4.229) by EXEDGE01.ad.utwente.nl (130.89.5.48) with Microsoft SMTP Server (TLS) id 14.2.328.9; Tue, 1 Oct 2013 08:06:32 +0200
Received: from EXMBX23.ad.utwente.nl ([169.254.3.114]) by EXHUB02.ad.utwente.nl ([130.89.4.229]) with mapi id 14.02.0328.009; Tue, 1 Oct 2013 08:06:30 +0200
From: karagian@cs.utwente.nl
To: schmidt@informatik.haw-hamburg.de
Thread-Topic: [multimob] I-D Action:draft-ietf-multimob-fmipv6-pfmipv6-multicast-01.txt
Thread-Index: AQHOucPFGQ0RZJFPB0+MtdBpNsnqrZnfY3m/gAABv4Y=
Date: Tue, 01 Oct 2013 06:06:28 +0000
Message-ID: <FF1A9612A94D5C4A81ED7DE1039AB80F4F3D509A@EXMBX23.ad.utwente.nl>
References: <201309251549114085692@gmail.com>
In-Reply-To: <201309251549114085692@gmail.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: [86.91.134.3]
Content-Type: multipart/alternative; boundary="_000_FF1A9612A94D5C4A81ED7DE1039AB80F4F3D509AEXMBX23adutwent_"
MIME-Version: 1.0
Cc: multimob@ietf.org
Subject: Re: [multimob] I-D Action:draft-ietf-multimob-fmipv6-pfmipv6-multicast-01.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 Oct 2013 06:06:43 -0000

Hi Thomas,



During the last multimob WG meeting in Berlin I had volunteerd to provide comments on the last version of this draft.

Here are these comments:


Comment_1:  The draft is useful since it is providing a solution for seamless and fast handover for multicast applications by extending existing seamless and fast handover solutions used for unicast applications, which are the Mobile IPv6 Fast Handovers (FMIPv6) specified in RFC5568 and the Fast Handovers for Proxy Mobile IPv6 (PFMIPv6) specified in RFC5949.

Comment_2: A motivation section is missing from the draft. In my opinion it is very useful to include such section in this draft. In particular, this draft mentions that a seamless and fast handover solutions is needed for multicast applications like IPTV. Other scenarios and applications that will make use of such a solutions are Public Protection and Disaster Relief (PPDR) scenarios, where mobile multicast communications need to be supported between members of rescue teams, police officers, fire brigade teams, paramedic teams, command control offices in order to support the protection and health of citizens.

In particular three main PPDR scenarios & application types could be distinguished:

1)            City security scenario:  that can be used to support the day to day safety and security of citizens.
2)            Disaster recovery scenario that deals with the protection of people and rescue teams during large scale natural or man-made disasters, like flooding, earth quakes and nuclear disasters.
3)            Temporary Protection PPDR scenario that deals with safety and security of citizens visiting large planned events like football matches, pop concerts and protest demonstrations.


Comment_3: List the requirements that need to be satisfied by this solution. You may use as example Section 1.1 of  http://www.ietf.org/id/draft-ietf-multimob-handover-optimization-04.txt


Comment_4: Provide a more detailed message flow description, similar to the one that is given in Section 5.1.2 in±
http://www.ietf.org/id/draft-ietf-multimob-handover-optimization-04.txt
This comment holds for Figures 2, 3, 4, 5

Comment_5: There is no description on how this draft, which specifies a mobile multicast listener support solution, can be used in combination a the mobile multicast senders, solution e.g., http://www.ietf.org/id/draft-ietf-multimob-pmipv6-source-05.txt.
There are scenarios and applications that require the use of these two solutions simultaneously.


Best regards,

Georgios



>
>A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Multicast Mobility Working Group of the IETF.
>
>       Title           : Multicast Listener Extensions for MIPv6 and PMIPv6 Fast Handovers
>       Author(s)       : Thomas C. Schmidt
>                          Matthias Waehlisch
>                          Rajeev Koodli
>                          Godred Fairhurst
>                          Dapeng Liu
>       Filename        : draft-ietf-multimob-fmipv6-pfmipv6-multicast-01.txt
>       Pages           : 27
>       Date            : 2013-02-25
>
>Abstract:
>   Fast handover protocols for MIPv6 and PMIPv6 define mobility
>   management procedures that support unicast communication at reduced
>   handover latency.  Fast handover base operations do not affect
>   multicast communication, and hence do not accelerate handover
>   management for native multicast listeners.  Many multicast
>   applications like IPTV or conferencing, though, are comprised of
>   delay-sensitive real-time traffic and will benefit from fast handover
>   execution.  This document specifies extension of the Mobile IPv6 Fast
>   Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6
>   (PFMIPv6) protocols to include multicast traffic management in fast
>   handover operations.  This multicast support is provided first at the
>   control plane by a management of rapid context transfer between
>   access routers, second at the data plane by an optional fast traffic
>   forwarding that may include buffering.
>
>
>The IETF datatracker status page for this draft is:
>https://datatracker.ietf.org/doc/draft-ietf-multimob-fmipv6-pfmipv6-multicast
>
>There's also a htmlized version available at:
>http://tools.ietf.org/html/draft-ietf-multimob-fmipv6-pfmipv6-multicast-01
>
>A diff from the previous version is available at:
>http://www.ietf.org/rfcdiff?url2=draft-ietf-multimob-fmipv6-pfmipv6-multicast-01
>
>
>Internet-Drafts are also available by anonymous FTP at:
>ftp://ftp.ietf.org/internet-drafts/
>
>_______________________________________________
>multimob mailing list
>multimob@ietf.org
>https://www.ietf.org/mailman/listinfo/multimob

= = = = = = = = = = = = = = = = = = = =


        致
礼!


Shuai Gao
Associate Professor
National Engineering Lab for Next Generation Internet Interconnection Devices
Beijing Jiaotong University
Beijing, China, 100044
gaoxlh@gmail.com
2013-09-25

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