Hi Behcet,
thanks for your comments: we have updated and submitted the draft.
Please see answers inline:
On 03.02.2014 00:39, Behcet Sarikaya wrote:
Sec. 2
In addition, the following terms are
introduced:
where are the terms?
Oopsi, no further terms. We have cleared this.
Sec. 3.1
subnet link
use on of them
OK - it's subnet now.
when the group is
natively received.
What does this mean, please explain
This means native multicast packet forwarding (instead of tunneling).
As group membership information are
s/are/is
Thanks - corrected.
Sec. 5.3
The size of this option in 8 octets
s/in/is
Thanks - corrected.
Last but not least, I think the draft finishes without a discussion of
why this solution is needed. We need some text on this. I don't know if
the reference "FMIPv6-Analysis" could be useful.
This corresponds to a comment made be Georgios. We have added the
following subsection to the introduction:
1.1. Use Cases and Deployment Scenarios
Multicast Extensions for Fast Handovers enable multicast services in
those domains that operate any of the unicast fast handover protocols
[RFC5568] or [RFC5949]. Typically, fast handover protocols are
activated within an operator network or within a dedicated service
installation.
Multicast group communication has a variety of dominant use cases.
One traditional application area is infotainment with voluminous
multimedia streams delivered to a large number of receivers (e.g.,
IPTV). Other time-critical news items like stock-exchange prices are
commonly transmitted via multicast to support fair and fast updates.
Both may be mobile and both largely benefit from fast handover
operations. Operators may enhance their operational quality or offer
premium services by enabling fast handovers.
Another traditional application area for multicast is conversational
group communication in scenarios like conferencing or gaming, but
also in dedicated collaborative environments or teams. Machine-to-
machine communication in the emerging Internet of Things is expected
Schmidt, et al. Expires August 19, 2014 [Page 4]
Internet-Draft Multicast for FMIPv6/PFMIPv6 February 2014
to generate various additional mobile use cases (e.g., among cars).
High demands on transmission quality and rapidly moving parties may
require fast handovers.
Most of the deployment scenarios above are bound to a fixed
infrastructure with consumer equipment at the edge. Today, they are
thus likely to follow an operator-centric approach like PFMIPv6.
However, Internet technologies evolve for adoption in
infrastructureless scenarios at disaster recovery, rescue, crisis
prevention and civil safety. Mobile end-to-end communication in
groups is needed in Public Protection and Disaster Relief (PPDR)
scenarios, where mobile multicast communication needs 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. These use cases require fast and
reliable mobile services which cannot rely on operator
infrastructure. They are thus predestined to running multicast with
FMIPv6.
Have a safe trip to Monty Python land!
Thomas
_______________________________________________
multimob mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/multimob
