Send multimob mailing list submis=
sions to
	multimob@ietf.org

To subscribe or unsubscribe via the World Wide Web, visit
	https://www1.ietf.org/mailman/listinfo/multimob
or, via email, send a message with subject or body 'help' to
	multimob-request@ietf.org

You can reach the person managing the list at
	multimob-owner@ietf.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of multimob digest..."

Today's Topics:

   1. Re:  Re: multimob Digest, Vol 2, Issue 4 (Jong-Hyouk Lee)

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

Message: 1
Date: Tue, 29 May 2007 16:11:35 +0900
From: "Jong-Hyouk Lee" <jonghyouk@gmail.com>
Subject: Re: [multimob] Re: multimob Digest, Vol 2, Issue 4
To: guanjian8632@163.com
Cc: multimob@ietf.org
Message-ID:
	<f54070070705290011k3b8c9a81j7674452195eee8a9@mail.gmail.com>
Content-Type: text/plain; charset=3D"iso-8859-1"

Dear Tony.

I'd like to ask you. In the previous e-mail, you mentioned that your group
is working on implementation of mobile multicast in real appilication. Is i=
t
based on MIPL stack? Is there any specific documents or guideline? I don't
think so.

What is your guideline? I just want to know because I seem to have forgotte=
n
big one.

Cheers.

On 5/28/07, Tony <guanjian8632@163.com> wrote:
>
>
> >Message: 1
> >Date: Thu, 24 May 2007 16:05:48 +0300
> >From: "Decoy M" <decoy77@gmail.com>
> >Subject: Re: [multimob] What is multicast mobility?
> >To: "Alexandru Petrescu" <alexandru.petrescu@gmail.com>
> >Cc: multimob@ietf.org
> >Message-ID:
> >       <495d743d0705240605j77c47e9al39e696fdd399e4fd@mail.gmail=
.com>
> >Content-Type: text/plain; charset=3D"iso-8859-1"
> >
> >On 5/24/07, Alexandru Petrescu <alexandru.petrescu@gmail.com>=
; wrote:
> >>
> >> Behcet Sarikaya wrote:
> >> > Hello Folks, Suresh, Thomas and I initiated this activit=
y and now I
> >> > would like to propose a work plan and get your comments =
and
> >> > reactions.
> >> >
> >> > Item 1. Work on MLDv2 extensions. This work will concent=
rate on the
> >> > router part and will involve how to track per-host multi=
cast listener
> >> > status and build per host context. Per host multicast li=
stener
> >> > context block, etc. will be defined.
> >>
> >> Sorry, isn't MLDv2 router implementation already keeping trac=
k of
> >> listener status?
> >
> >
> >[Decoy] I think most of th routers doesnt keep track of the indivi=
sual
> >multicast listeners but they just check whether some bosyis intere=
sted in
> >the multicast channel or not. So explicit Host tracking may not be
> required.
> >This requires table maintainance and other work as each and every =
Host
> >information needs to be stored and maintained.
> >
> >> Item 2. Base protocol MIPv6 extensions on handling multicast =
sessions
> >> > such as bandwidth inefficiency inherent in the home agen=
t's
> >> > unicasting multicast packets through the tunnel.
> >>
> >> What could the HA do?  Not unicast the multicast packets thro=
ugh the
> >> tunnel?
>        HA can record the MN information and maintain MN's MLD state et=
c.
> Forwarding
> the multicast data through unicast tunnel is just one mobile multicast
> scheme.
> >> > Item 3. Handoff survival of local (at a foreign link) mu=
lticast
> >> > sessions will be taken up in the context of care-of addr=
ess based
> >> > multicast group subscriptions.
> >>
> >> What's the influence of re-subscribing a new CoA upon each mo=
vement, on
> >> the infrastructure routing?
>   If the New AR which MN attached has the multicast group state that M=
N
> subscribed, the
> multicast disruption time is short (100~200ms). while if New AR doesn'=
t
> have the group
> states, it will take a long time to rejoin the groups.
>
>        Our group is working on implementation of mobile multicast in r=
eal
> appilication recently.
> Welcome everyone to discuss.
> >> Alex
> >>
> >>
> >> _____________________________________________________________=
_________
> >> This email has been scanned by the MessageLabs Email Security=
 System.
> >> For more information please visit http://www.messagelabs.com/=
email
> >> _____________________________________________________________=
_________
> >>
> >> _______________________________________________
> >> multimob mailing list
> >> multimob@ietf.org
> >> https://www1.ietf.org/mailman/listinfo/multimob
> >>
> >-------------- next part --------------
> >An HTML attachment was scrubbed...
> >URL:
> http://www1.ietf.org/pipermail/multimob/attachments/20070524/e38c0354/=
attachment.html
> >
> >------------------------------
> >
> >_______________________________________________
> >multimob mailing list
> >multimob@ietf.org
> >https://www1.ietf.org/mailman/listinfo/multimob
> >
> >
> >End of multimob Digest, Vol 2, Issue 4
> >**************************************
> >
>
> =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =3D =
=3D =3D =3D
>
> Tony
> guanjian8632@163.com
> 2007-05-28
> +--------------------------------------+
> |      NGIRC, Beijing JiaoTong University      |
> |      BeiJing, China,100044                           |
> |      Http://www.njtu.edu.cn                          |
> +--------------------------------------+
>
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www1.ietf.org/mailman/listinfo/multimob
>
>

--=20
Internet Management Technology Lab, Sungkyunkwan University.
Jong-Hyouk Lee.

#email: jonghyouk (at) gmail (dot) com
#webpage: http://www.hurryon.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www1.ietf.org/pipermail/multimob/attachments/20070529/7a18fc90/=
attachment.html

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

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

End of multimob Digest, Vol 2, Issue 7
**************************************