
From schmidt@informatik.haw-hamburg.de  Wed Jul  1 10:02:13 2009
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AECE28C562; Wed,  1 Jul 2009 10:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SffYtADAs3yg; Wed,  1 Jul 2009 10:02:12 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.fhtw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 5F20B28C54A; Wed,  1 Jul 2009 10:02:12 -0700 (PDT)
Envelope-to: multimob@ietf.org, netlmm@ietf.org
Received: from [141.22.26.203] by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1MM3Br-000LmV-TJ; Wed, 01 Jul 2009 19:01:47 +0200
Message-ID: <4A4B9673.10201@informatik.haw-hamburg.de>
Date: Wed, 01 Jul 2009 19:01:39 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: multimob@ietf.org, netlmm@ietf.org
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [multimob] [Fwd: New Version Notification for draft-schmidt-multimob-pmipv6-mcast-deployment-01]
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 01 Jul 2009 17:02:13 -0000

Dear all,

we have just updated the draft
http://www.ietf.org/internet-drafts/draft-schmidt-multimob-pmipv6-mcast-deployment-01.txt
with a new version that followed all the valuable feedback received from 
the list.

In addition, some clarifications (e.g., a flow chart) etc. have been added.

Please let us know about further thoughts and input so that we can 
continue to improve the document!

See you in Stockholm

Thomas

-------- Original Message --------
Subject: New Version Notification for 
draft-schmidt-multimob-pmipv6-mcast-deployment-01
Date: Wed,  1 Jul 2009 09:55:54 -0700 (PDT)
From: IETF I-D Submission Tool <idsubmission@ietf.org>
To: Schmidt@informatik.haw-hamburg.de
CC: 
schmidt@informatik.haw-hamburg.de,mw@link-lab.net,sarikaya@ieee.org,suresh.krishnan@ericsson.com


A new version of I-D, 
draft-schmidt-multimob-pmipv6-mcast-deployment-01.txt has been 
successfuly submitted by Thomas Schmidt and posted to the IETF repository.

Filename:	 draft-schmidt-multimob-pmipv6-mcast-deployment
Revision:	 01
Title:		 A Minimal Deployment Option for Multicast Listeners in PMIPv6 
Domains
Creation_date:	 2009-06-29
WG ID:		 Independent Submission
Number_of_pages: 12

Abstract:
This document describes deployment options for activating multicast
listener functions in Proxy Mobile IPv6 domains without modifying
mobility and multicast protocol standards.  Similar to Home Agents in
Mobile IPv6, PMIPv6 Local Mobility Anchors serve as multicast
subscription anchor points, while Mobile Access Gateways provide MLD
proxy functions.  In this scenario, Mobile Nodes remain agnostic of
multicast mobility operations.
 



The IETF Secretariat.



-- 

Prof. Dr. Thomas C. Schmidt
Â° Hamburg University of Applied Sciences                   Berliner Tor 7 Â°
Â° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany Â°
Â° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 Â°
Â° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 Â°

From gorry@erg.abdn.ac.uk  Thu Jul  2 08:01:41 2009
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 53EFB3A6DAE for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 08:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level: 
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.050,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id o2A1qIB0YSWD for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 08:01:40 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 6A1CB3A6DB4 for <multimob@ietf.org>; Thu,  2 Jul 2009 08:00:02 -0700 (PDT)
Received: from Gorry-Fairhursts-Laptop-6.local (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n62F0K46014900 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <multimob@ietf.org>; Thu, 2 Jul 2009 16:00:20 +0100 (BST)
Message-ID: <4A4CCB84.4040703@erg.abdn.ac.uk>
Date: Thu, 02 Jul 2009 16:00:20 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: multimob@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Subject: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 02 Jul 2009 15:01:41 -0000

I hope we are finally there.

Behcet and I propose to post the version of the Charter below to our 
ADs. We think we took account of all comments we received (on and off 
list), but have had to make a few small compromises.

If you find corrections needed to wording or something significant, let 
us know. There is a hard deadline of 12:00 noon, GMT for this feedback, 
after which we'll send to our ADs.

Thanks to all who engaged in this process,

Gorry & Behcet

----


Multicast Mobility (multimob)

Chairs:
Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Behcet Sarikaya <sarikaya@ieee.org>

Internet Area (int) Directors:
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Security Area Advisor:
Marshall Eubanks <tme@americafree.tv>.

Mailing Lists:
General Discussion: multimob@ietf.org
Subscribe online at: https://www1.ietf.org/mailman/listinfo/multimob

Description of Working Group

The Multicast mobility (multimob) will develop protocol extensions
and provide guidance for supporting IPv6 (and also IPv4)
multicast in a mobile environment. It will consider both source
specific multicast (SSM) and any source multicast (ASM) multicast
models. The scope of work will be limited to Proxy Mobile IPv6, MLD/IGMP
protocols and listener mobility. Work requiring modifications of
multicast routing protocols is out of scope.

Specific goals are:
- Specify PMIPv6 extensions to support IPv6 multicast including remote 
subscription and fast handover.
- Specify IGMP/MLD extensions methods for mobility.

The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213 does not
explicitly define support for multicast. The WG will work on solutions 
for multicast support in PMIPv6. It will document basic support for 
multicast with remote subscription. Such basic support will not require 
any additions or changes to RFC 5213 specified message types and 
parameters, and will assume an unmodified mobile host.  Remote
subscription is a mechanism by which a mobile node joins a multicast
group and receives multicast data forwarded via the local mobility
anchor. If required, basic multicast support may be extended to support 
optimizations to address the avalanche problem and fast handover.

IGMPv3/MLDv2 has been specified for wired networks with
shared links. Mobile nodes also have other needs (e.g.  entering a
dormant mode to conserve battery power, minimising the latency for
joining and leaving a group in support of movement). Mobile nodes also 
have other needs that are specific to wireless networks and mobility.

The WG will assess existing solutions for group management, and
determine if these methods are sufficient in a mobile environment.
This will include recommending appropriate selection of timer values
and protocol parameters. If current methods are not sufficient, the WG
shall specify updates to existing protocols. It is a goal for the WG to
ensure backward compatibility with current implementations of
group management protocols. New IGMP/MLD message types
may be specified to optimize mobile performance. Since these
could be ignored, dropped or improperly forwarded by existing hosts,
switches, routers and proxies, these will not be necessary for proper
IGMP/MLD performance, albeit with a partial or total loss of the
intended performance optimization in deployments that do not fully
support them.

Future work, subject to approval, may study/evaluate whether extensions 
are needed for the client-based mobility protocols (Mobile IPv6 and 
Dual-Stack Mobile IPv6). Future work may also include protocol 
extensions to support source mobility  and methods to allow a 
multi-homed mobile node to join multicast groups and direct multicast 
flows to appropriate local interfaces.

In performing this work, the Multimob working group will work closely
with NETLMM working group and will coordinate work on IGMP/MLD
extensions with the MBONED working group.

GOALS and MILESTONES:

Six months:
- Submit a document explaining use of multicast in PMIPv6, for 
publication as an INFO/BCP RFC.
- Submit a document on how to tune MLD for mobility, for publication as 
an INFO/BCP RFC.

One year:
- Submit a document on extensions for multicast mobility in PMIPv6 as an 
EXP/PS RFC.
- Submit a document on IGMP/MLD extensions for multicast mobility as an 
EXP/PS RFC.

Recharter or close working group.



From gorry@erg.abdn.ac.uk  Thu Jul  2 08:01:41 2009
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7261E3A6DB0 for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 08:01:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.553
X-Spam-Level: 
X-Spam-Status: No, score=-2.553 tagged_above=-999 required=5 tests=[AWL=0.046,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GymkhZrznPh3 for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 08:01:40 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 85F2E3A6F17 for <multimob@ietf.org>; Thu,  2 Jul 2009 08:00:08 -0700 (PDT)
Received: from Gorry-Fairhursts-Laptop-6.local (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n62F0Qnt014909 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 2 Jul 2009 16:00:27 +0100 (BST)
Message-ID: <4A4CCB8A.9030903@erg.abdn.ac.uk>
Date: Thu, 02 Jul 2009 16:00:26 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: multimob@ietf.org, gorry <gorry@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Subject: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 02 Jul 2009 15:01:41 -0000

I hope we are finally there.

Behcet and I propose to post the version of the Charter below to our 
ADs. We think we took account of all comments we received (on and off 
list), but have had to make a few small compromises.

If you find corrections needed to wording or something significant, let 
us know. There is a hard deadline of 12:00 noon, GMT for this feedback, 
after which we'll send to our ADs.

Thanks to all who engaged in this process,

Gorry & Behcet

----


Multicast Mobility (multimob)

Chairs:
Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Behcet Sarikaya <sarikaya@ieee.org>

Internet Area (int) Directors:
Jari Arkko <jari.arkko@piuha.net>
Ralph Droms <rdroms@cisco.com>

Internet Area Advisor:
Jari Arkko <jari.arkko@piuha.net>

Security Area Advisor:
Marshall Eubanks <tme@americafree.tv>.

Mailing Lists:
General Discussion: multimob@ietf.org
Subscribe online at: https://www1.ietf.org/mailman/listinfo/multimob

Description of Working Group

The Multicast mobility (multimob) will develop protocol extensions
and provide guidance for supporting IPv6 (and also IPv4)
multicast in a mobile environment. It will consider both source
specific multicast (SSM) and any source multicast (ASM) multicast
models. The scope of work will be limited to Proxy Mobile IPv6, MLD/IGMP
protocols and listener mobility. Work requiring modifications of
multicast routing protocols is out of scope.

Specific goals are:
- Specify PMIPv6 extensions to support IPv6 multicast including remote 
subscription and fast handover.
- Specify IGMP/MLD extensions methods for mobility.

The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213 does not
explicitly define support for multicast. The WG will work on solutions 
for multicast support in PMIPv6. It will document basic support for 
multicast with remote subscription. Such basic support will not require 
any additions or changes to RFC 5213 specified message types and 
parameters, and will assume an unmodified mobile host.  Remote
subscription is a mechanism by which a mobile node joins a multicast
group and receives multicast data forwarded via the local mobility
anchor. If required, basic multicast support may be extended to support 
optimizations to address the avalanche problem and fast handover.

IGMPv3/MLDv2 has been specified for wired networks with
shared links. Mobile nodes also have other needs (e.g.  entering a
dormant mode to conserve battery power, minimising the latency for
joining and leaving a group in support of movement). Mobile nodes also 
have other needs that are specific to wireless networks and mobility.

The WG will assess existing solutions for group management, and
determine if these methods are sufficient in a mobile environment.
This will include recommending appropriate selection of timer values
and protocol parameters. If current methods are not sufficient, the WG
shall specify updates to existing protocols. It is a goal for the WG to
ensure backward compatibility with current implementations of
group management protocols. New IGMP/MLD message types
may be specified to optimize mobile performance. Since these
could be ignored, dropped or improperly forwarded by existing hosts,
switches, routers and proxies, these will not be necessary for proper
IGMP/MLD performance, albeit with a partial or total loss of the
intended performance optimization in deployments that do not fully
support them.

Future work, subject to approval, may study/evaluate whether extensions 
are needed for the client-based mobility protocols (Mobile IPv6 and 
Dual-Stack Mobile IPv6). Future work may also include protocol 
extensions to support source mobility  and methods to allow a 
multi-homed mobile node to join multicast groups and direct multicast 
flows to appropriate local interfaces.

In performing this work, the Multimob working group will work closely
with NETLMM working group and will coordinate work on IGMP/MLD
extensions with the MBONED working group.

GOALS and MILESTONES:

Six months:
- Submit a document explaining use of multicast in PMIPv6, for 
publication as an INFO/BCP RFC.
- Submit a document on how to tune MLD for mobility, for publication as 
an INFO/BCP RFC.

One year:
- Submit a document on extensions for multicast mobility in PMIPv6 as an 
EXP/PS RFC.
- Submit a document on IGMP/MLD extensions for multicast mobility as an 
EXP/PS RFC.

Recharter or close working group.



From jouni.nospam@gmail.com  Thu Jul  2 14:24:49 2009
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C6D43A6D5A for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 14:24:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.416
X-Spam-Level: 
X-Spam-Status: No, score=-2.416 tagged_above=-999 required=5 tests=[AWL=0.183,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5be0sQyvHMCL for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 14:24:47 -0700 (PDT)
Received: from fg-out-1718.google.com (fg-out-1718.google.com [72.14.220.156]) by core3.amsl.com (Postfix) with ESMTP id C65DE3A6803 for <multimob@ietf.org>; Thu,  2 Jul 2009 14:23:43 -0700 (PDT)
Received: by fg-out-1718.google.com with SMTP id 16so540565fgg.18 for <multimob@ietf.org>; Thu, 02 Jul 2009 14:23:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=ra5uQEFqgM0EM3OKOHiWM6r1Lqio6t+NZKfS+K6jlNY=; b=wj20UQ1nqgJtO3MDY3YG1B16PGhNFpMmUo80JPpgE64bXhVTjhHlIEVhJesVdte9M/ ExugGKcUyi+EIw2BD3I80y2Lo7fbsi8TsXxosdg/KOcGRimfAnltARKBS4EhaViD5UEy YPHLMg65VHI2cS1OlMm7ELSIi2MQLSHvTodSk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=MDwm+Do0eROpX9K7TqwJHktbgMEBhfHBP97jT9qW4VeanZejUo0TKHf8cUHI9Gltpq sDxyVH4R4GuJGatqZqCqPQofHldSC2e29GDLk+VxUmAfaNnp+mF2v2Ey1tCLEKpOFSoz /OdjjtrbsGxK952GvwlD+mymJcqgvFiMAtZBs=
Received: by 10.86.96.18 with SMTP id t18mr695360fgb.58.1246569837553; Thu, 02 Jul 2009 14:23:57 -0700 (PDT)
Received: from a88-114-68-208.elisa-laajakaista.fi (a88-114-68-208.elisa-laajakaista.fi [88.114.68.208]) by mx.google.com with ESMTPS id 4sm15130027fge.18.2009.07.02.14.23.56 (version=TLSv1/SSLv3 cipher=RC4-MD5); Thu, 02 Jul 2009 14:23:57 -0700 (PDT)
Message-Id: <0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com>
From: jouni korhonen <jouni.nospam@gmail.com>
To: gorry@erg.abdn.ac.uk
In-Reply-To: <4A4CCB84.4040703@erg.abdn.ac.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 3 Jul 2009 00:23:55 +0300
References: <4A4CCB84.4040703@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.935.3)
Cc: multimob@ietf.org
Subject: Re: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 02 Jul 2009 21:24:49 -0000

Hi Gorry, Behcet,

Thanks for the new revised charter! It looks mostly fine to me.  
However, I still have few minor nits ;) Comments again prefixed with  
[JiK].

Cheers,
	Jouni

On Jul 2, 2009, at 6:00 PM, Gorry Fairhurst wrote:

> I hope we are finally there.
>
> Behcet and I propose to post the version of the Charter below to our  
> ADs. We think we took account of all comments we received (on and  
> off list), but have had to make a few small compromises.
>
> If you find corrections needed to wording or something significant,  
> let us know. There is a hard deadline of 12:00 noon, GMT for this  
> feedback, after which we'll send to our ADs.
>
> Thanks to all who engaged in this process,
>
> Gorry & Behcet
>
> ----
>
>
> Multicast Mobility (multimob)
>
> Chairs:
> Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> Behcet Sarikaya <sarikaya@ieee.org>
>
> Internet Area (int) Directors:
> Jari Arkko <jari.arkko@piuha.net>
> Ralph Droms <rdroms@cisco.com>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Security Area Advisor:
> Marshall Eubanks <tme@americafree.tv>.
>
> Mailing Lists:
> General Discussion: multimob@ietf.org
> Subscribe online at: https://www1.ietf.org/mailman/listinfo/multimob
>
> Description of Working Group
>
> The Multicast mobility (multimob) will develop protocol extensions
> and provide guidance for supporting IPv6 (and also IPv4)
> multicast in a mobile environment. It will consider both source
> specific multicast (SSM) and any source multicast (ASM) multicast
> models. The scope of work will be limited to Proxy Mobile IPv6, MLD/ 
> IGMP
> protocols and listener mobility. Work requiring modifications of
> multicast routing protocols is out of scope.
>
> Specific goals are:
> - Specify PMIPv6 extensions to support IPv6 multicast including  
> remote subscription and fast handover.
> - Specify IGMP/MLD extensions methods for mobility.
>
> The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213  
> does not
> explicitly define support for multicast. The WG will work on  
> solutions for multicast support in PMIPv6. It will document basic  
> support for multicast with remote subscription. Such basic support  
> will not require any additions or changes to RFC 5213 specified  
> message types and parameters, and will assume an unmodified mobile  
> host.  Remote
> subscription is a mechanism by which a mobile node joins a multicast
> group and receives multicast data forwarded via the local mobility
> anchor. If required, basic multicast support may be extended to  
> support optimizations to address the avalanche problem and fast  
> handover.
>
> IGMPv3/MLDv2 has been specified for wired networks with
> shared links. Mobile nodes also have other needs (e.g.  entering a
> dormant mode to conserve battery power, minimising the latency for
> joining and leaving a group in support of movement). Mobile nodes  
> also have other needs that are specific to wireless networks and  
> mobility.

[JiK] The above paragraph seems to be a bit off. I'd propose the  
following editorial change:

"IGMPv3/MLDv2 has been specified for wired networks with
  shared links. Mobile nodes also have other needs that are specific
  to wireless networks and mobility (e.g.  entering a dormant mode to
  conserve battery power, minimising the latency for joining and
  leaving a group in support of movement)."



>
>
> The WG will assess existing solutions for group management, and
> determine if these methods are sufficient in a mobile environment.
> This will include recommending appropriate selection of timer values
> and protocol parameters. If current methods are not sufficient, the WG
> shall specify updates to existing protocols. It is a goal for the WG  
> to
> ensure backward compatibility with current implementations of
> group management protocols. New IGMP/MLD message types
> may be specified to optimize mobile performance. Since these
> could be ignored, dropped or improperly forwarded by existing hosts,
> switches, routers and proxies, these will not be necessary for proper
> IGMP/MLD performance, albeit with a partial or total loss of the
> intended performance optimization in deployments that do not fully
> support them.
>
> Future work, subject to approval, may study/evaluate whether  
> extensions are needed for the client-based mobility protocols  
> (Mobile IPv6 and Dual-Stack Mobile IPv6). Future work may also  
> include protocol extensions to support source mobility  and methods  
> to allow a multi-homed mobile node to join multicast groups and  
> direct multicast flows to appropriate local interfaces.

[JiK] Can't multi-homed host/mobile nodes already join multicast  
groups? Also, I think a "clever" multi-homed host can direct multicast  
flows between its interfaces with a stock MLDv[12]. So, what's the  
beef here?


>
>
> In performing this work, the Multimob working group will work closely
> with NETLMM working group and will coordinate work on IGMP/MLD
> extensions with the MBONED working group.
>
> GOALS and MILESTONES:
>
> Six months:
> - Submit a document explaining use of multicast in PMIPv6, for  
> publication as an INFO/BCP RFC.
> - Submit a document on how to tune MLD for mobility, for publication  
> as an INFO/BCP RFC.
>
> One year:
> - Submit a document on extensions for multicast mobility in PMIPv6  
> as an EXP/PS RFC.
> - Submit a document on IGMP/MLD extensions for multicast mobility as  
> an EXP/PS RFC.
>
> Recharter or close working group.
>
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob


From behcetsarikaya@yahoo.com  Thu Jul  2 15:25:36 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E14D43A6B0E for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 15:25:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.751
X-Spam-Level: 
X-Spam-Status: No, score=-1.751 tagged_above=-999 required=5 tests=[AWL=-0.548, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id DbNf5K8jBfd2 for <multimob@core3.amsl.com>; Thu,  2 Jul 2009 15:25:35 -0700 (PDT)
Received: from n6.bullet.re3.yahoo.com (n6.bullet.re3.yahoo.com [68.142.237.91]) by core3.amsl.com (Postfix) with SMTP id DC9B73A6951 for <multimob@ietf.org>; Thu,  2 Jul 2009 15:25:34 -0700 (PDT)
Received: from [68.142.237.87] by n6.bullet.re3.yahoo.com with NNFMP; 02 Jul 2009 22:25:56 -0000
Received: from [67.195.9.82] by t3.bullet.re3.yahoo.com with NNFMP; 02 Jul 2009 22:25:55 -0000
Received: from [67.195.9.111] by t2.bullet.mail.gq1.yahoo.com with NNFMP; 02 Jul 2009 22:25:55 -0000
Received: from [127.0.0.1] by omp115.mail.gq1.yahoo.com with NNFMP; 02 Jul 2009 22:25:55 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 698087.15519.bm@omp115.mail.gq1.yahoo.com
Received: (qmail 30171 invoked by uid 60001); 2 Jul 2009 22:25:55 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1246573555; bh=m+0cB4q6SOHksWUomr9CX3gqpgpiawcyrLYvS1+ZCZc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=OV9o0ERq9+CKVWGqzlZQMorj4tWuZ6cSIrKYS/faZH869var+btVuuE2Hf9d7yvR7/YghExwx4f0NfFfPv728vpd9Vlu4KxrhUJy56pWXMji+pASeAXOw/3Wnk2lNJPdt4QQrNdtTKaC1ZNMjoec87XKTXPXWT/Sp60GDmbY7FM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=R7nFJ+mMD0whQYQ9X+UsilPDGhNFb/X2SCtDX21DPJcdVcDjEwpm09nldtM9nNMJozYhcN6YCt/p28l51hQtsPWYgeEXKL7d5aICzXC34lB3URRcULgxLXVx+f2pJQhh/8wHSvg9hZ3HuJne/UZMjHmtc9J7I+QBxTOlOXm8MVw=;
Message-ID: <517894.29527.qm@web111403.mail.gq1.yahoo.com>
X-YMail-OSG: iCZfVeEVM1nd6EX.NjbGgDjxfL4iEWt0JMc635YmPW6TM63o0oZDWMzeKncbfcnej3LmnKssnLb.5nRt5e4DvMoMq6vX8914tBansGfZfkS7TPxJKaRoty9jH5Ay6hLX3_Ix5k2YF2vv2XbXoN_unYtDHh6SErhWn5VsBP0nGE1QwvYuDoJenxVawgRmttDbArHjEZAwnVBFpJw9USpbQr0AjpBVD4XwYhhD1736qo42REITejHx7ojKnm.HTXgdRKSMPoREceaqzRJ.YXjpMxGojjfYKea57iUZ9G0G5TzJgQusyqOUbho-
Received: from [206.16.17.212] by web111403.mail.gq1.yahoo.com via HTTP; Thu, 02 Jul 2009 15:25:55 PDT
X-Mailer: YahooMailRC/1358.21 YahooMailWebService/0.7.289.15
References: <4A4CCB84.4040703@erg.abdn.ac.uk> <0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com>
Date: Thu, 2 Jul 2009 15:25:55 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: jouni korhonen <jouni.nospam@gmail.com>
In-Reply-To: <0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Cc: multimob@ietf.org
Subject: Re: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 02 Jul 2009 22:25:36 -0000

Hi Jouni,=0A=0A=A0=0A=0A=0A> > =0A> > IGMPv3/MLDv2 has been specified for w=
ired networks with=0A> > shared links. Mobile nodes also have other needs (=
e.g.=A0 entering a=0A> > dormant mode to conserve battery power, minimising=
 the latency for=0A> > joining and leaving a group in support of movement).=
 Mobile nodes also have =0A> other needs that are specific to wireless netw=
orks and mobility.=0A> =0A> [JiK] The above paragraph seems to be a bit off=
.. I'd propose the following =0A> editorial change:=0A> =0A> "IGMPv3/MLDv2 h=
as been specified for wired networks with=0A> shared links. Mobile nodes al=
so have other needs that are specific=0A> to wireless networks and mobility=
 (e.g.=A0 entering a dormant mode to=0A> conserve battery power, minimising=
 the latency for joining and=0A> leaving a group in support of movement)."=
=0A=0AOK. This looks better, we'll update the charter as requested.=0A=0A=
=0A> > The WG will assess existing solutions for group management, and=0A> =
> determine if these methods are sufficient in a mobile environment.=0A> > =
This will include recommending appropriate selection of timer values=0A> > =
and protocol parameters. If current methods are not sufficient, the WG=0A> =
> shall specify updates to existing protocols. It is a goal for the WG to=
=0A> > ensure backward compatibility with current implementations of=0A> > =
group management protocols. New IGMP/MLD message types=0A> > may be specifi=
ed to optimize mobile performance. Since these=0A> > could be ignored, drop=
ped or improperly forwarded by existing hosts,=0A> > switches, routers and =
proxies, these will not be necessary for proper=0A> > IGMP/MLD performance,=
 albeit with a partial or total loss of the=0A> > intended performance opti=
mization in deployments that do not fully=0A> > support them.=0A> > =0A> > =
Future work, subject to approval, may study/evaluate whether extensions are=
 =0A> needed for the client-based mobility protocols (Mobile IPv6 and Dual-=
Stack =0A> Mobile IPv6). Future work may also include protocol extensions t=
o support source =0A> mobility=A0 and methods to allow a multi-homed mobile=
 node to join multicast =0A> groups and direct multicast flows to appropria=
te local interfaces.=0A> =0A> [JiK] Can't multi-homed host/mobile nodes alr=
eady join multicast groups? Also, I =0A> think a "clever" multi-homed host =
can direct multicast flows between its =0A> interfaces with a stock MLDv[12=
]. So, what's the beef here?=0A=0AThis is future work. We don't know at the=
 moment how things will evolve. But maybe the work could involve the defini=
tion of a "clever" multi-homed host and related protocol modifications. =0A=
Or some other things related to multicast flows. =0AWe suggest keeping it a=
s future work?=0A=0ARegards,=0A=0ABehcet=0A=0A=0A      


From jouni.nospam@gmail.com  Fri Jul  3 01:32:08 2009
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E08CB3A6B30 for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 01:32:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.039
X-Spam-Level: 
X-Spam-Status: No, score=-2.039 tagged_above=-999 required=5 tests=[AWL=0.560,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id h5b9YAG5nz7d for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 01:32:08 -0700 (PDT)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id CF67D3A687E for <multimob@ietf.org>; Fri,  3 Jul 2009 01:32:07 -0700 (PDT)
Received: by ewy11 with SMTP id 11so862830ewy.37 for <multimob@ietf.org>; Fri, 03 Jul 2009 01:32:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=n9+I2owXZ/svLvD9AQwG6qpuxHr/0NUhGY7ptrzGwYQ=; b=UwbsQuVnUviiNXniN70awfmOcsdMdZ6PJK+JKSvKtbE8UmeEqN2JIKLzRQRx3ZOIof c8wnwn8UMY1PqdLzKteP6fii4HaeNjEftvQW+f8zDVx7vkw9WJ4nha/K+k+3abtuBg2L 2IRwb5KUEScYjBteWfD2Fq3FFD/R8BDMKL7yM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=hMXdKMrVZJMMTnTBkoY8tIKhE6+nOK1vyWvpvuaJQRGaa4Tax3Mgmu47ZVNMHul4in PSipf3vccO2w2s4k4Oau9jr+rCw90U4UYgkfMrAGtcA5gg57wQ7JcHWfHTE0dF8bNeNu 1MSooFHfDyFeXHuNRaFuR0tLT4mqPzOWQQ5Yo=
Received: by 10.210.70.14 with SMTP id s14mr612283eba.38.1246609948206; Fri, 03 Jul 2009 01:32:28 -0700 (PDT)
Received: from ?10.254.0.121? ([192.100.123.77]) by mx.google.com with ESMTPS id 23sm2225838eya.29.2009.07.03.01.32.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 03 Jul 2009 01:32:27 -0700 (PDT)
Message-Id: <1B334D1F-0AC3-4A81-853C-B4B9F1F12733@gmail.com>
From: jouni korhonen <jouni.nospam@gmail.com>
To: Behcet Sarikaya <sarikaya@ieee.org>
In-Reply-To: <517894.29527.qm@web111403.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 3 Jul 2009 11:32:23 +0300
References: <4A4CCB84.4040703@erg.abdn.ac.uk> <0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com> <517894.29527.qm@web111403.mail.gq1.yahoo.com>
X-Mailer: Apple Mail (2.935.3)
Cc: multimob@ietf.org
Subject: Re: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 03 Jul 2009 08:32:09 -0000

Behcet,


On Jul 3, 2009, at 1:25 AM, Behcet Sarikaya wrote:

>
> Hi Jouni,
>>

[snip]


>>> Future work, subject to approval, may study/evaluate whether  
>>> extensions are
>> needed for the client-based mobility protocols (Mobile IPv6 and  
>> Dual-Stack
>> Mobile IPv6). Future work may also include protocol extensions to  
>> support source
>> mobility  and methods to allow a multi-homed mobile node to join  
>> multicast
>> groups and direct multicast flows to appropriate local interfaces.
>>
>> [JiK] Can't multi-homed host/mobile nodes already join multicast  
>> groups? Also, I
>> think a "clever" multi-homed host can direct multicast flows  
>> between its
>> interfaces with a stock MLDv[12]. So, what's the beef here?
>
> This is future work. We don't know at the moment how things will  
> evolve. But maybe the work could involve the definition of a  
> "clever" multi-homed host and related protocol modifications.
> Or some other things related to multicast flows.
> We suggest keeping it as future work?


I am fine with the other future work listen in the above paragraph. I  
just don't see immediately what work there could be related to multi- 
homed hosts and moving multicast feeds between its interfaces (be  
those of the same access technology or different). As of today a multi- 
homed host can join and leave multicast groups independently on each  
of its interface. That can be controlled on the application level  
(i.e. the "clever" host).

Maybe there is something to optimize in an multi-access tech multi- 
homed host case that I am not aware of. At minimum I would suggest to  
rephrase the:
"...and methods to allow a multi-homed mobile node to join multicast  
groups and direct multicast flows to appropriate local interfaces"

to

"...and optimizations to direct multicast flows to appropriate  
interfaces in a multi-homed host"


Cheers,
	Jouni


>
>
> Regards,
>
> Behcet
>
>
>
>


From gorry@erg.abdn.ac.uk  Fri Jul  3 02:06:19 2009
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id CE8703A6E88 for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 02:06:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level: 
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q00JgG5T4osc for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 02:06:19 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id B55243A6BB9 for <multimob@ietf.org>; Fri,  3 Jul 2009 02:03:55 -0700 (PDT)
Received: from Gorry-Fairhursts-Laptop-6.local (fgrpf.plus.com [212.159.18.54]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n6393cHl012822 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 3 Jul 2009 10:03:39 +0100 (BST)
Message-ID: <4A4DC96A.4090008@erg.abdn.ac.uk>
Date: Fri, 03 Jul 2009 10:03:38 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Thunderbird 2.0.0.21 (Macintosh/20090302)
MIME-Version: 1.0
To: jouni korhonen <jouni.nospam@gmail.com>
References: <4A4CCB84.4040703@erg.abdn.ac.uk>	<0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com>	<517894.29527.qm@web111403.mail.gq1.yahoo.com> <1B334D1F-0AC3-4A81-853C-B4B9F1F12733@gmail.com>
In-Reply-To: <1B334D1F-0AC3-4A81-853C-B4B9F1F12733@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Cc: multimob@ietf.org
Subject: Re: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 03 Jul 2009 09:06:19 -0000

The first change looks good, and I believe we have all benefited from 
the discussions on the charter.

I agree with Behcet, let's make the change in your last email.

I'm not sure we need the last change proposed at the end of this email. 
Specifically I am not keen on unpacking or detailing the future work 
paragraph - If the main scope of work is addreseed, I would expect there 
to be much more experience of interactions and implications on v4 and v6 
stacks. I would also very much expect a future rechartering process to 
discuss exactly what is needed in this space.

I'd suggest avoid fine-tuning the wording here.

Gorry

jouni korhonen wrote:
> Behcet,
> 
> 
> On Jul 3, 2009, at 1:25 AM, Behcet Sarikaya wrote:
> 
>>
>> Hi Jouni,
>>>
> 
> [snip]
> 
> 
>>>> Future work, subject to approval, may study/evaluate whether 
>>>> extensions are
>>> needed for the client-based mobility protocols (Mobile IPv6 and 
>>> Dual-Stack
>>> Mobile IPv6). Future work may also include protocol extensions to 
>>> support source
>>> mobility  and methods to allow a multi-homed mobile node to join 
>>> multicast
>>> groups and direct multicast flows to appropriate local interfaces.
>>>
>>> [JiK] Can't multi-homed host/mobile nodes already join multicast 
>>> groups? Also, I
>>> think a "clever" multi-homed host can direct multicast flows between its
>>> interfaces with a stock MLDv[12]. So, what's the beef here?
>>
>> This is future work. We don't know at the moment how things will 
>> evolve. But maybe the work could involve the definition of a "clever" 
>> multi-homed host and related protocol modifications.
>> Or some other things related to multicast flows.
>> We suggest keeping it as future work?
> 
> 
> I am fine with the other future work listen in the above paragraph. I 
> just don't see immediately what work there could be related to 
> multi-homed hosts and moving multicast feeds between its interfaces (be 
> those of the same access technology or different). As of today a 
> multi-homed host can join and leave multicast groups independently on 
> each of its interface. That can be controlled on the application level 
> (i.e. the "clever" host).
> 
> Maybe there is something to optimize in an multi-access tech multi-homed 
> host case that I am not aware of. At minimum I would suggest to rephrase 
> the:
> "...and methods to allow a multi-homed mobile node to join multicast 
> groups and direct multicast flows to appropriate local interfaces"
> 
> to
> 
> "...and optimizations to direct multicast flows to appropriate 
> interfaces in a multi-homed host"
> 
> 
> Cheers,
>     Jouni
> 
> 
>>
>>
>> Regards,
>>
>> Behcet
>>
>>
>>
>>
> 
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob
> 
> 


From jouni.nospam@gmail.com  Fri Jul  3 02:19:56 2009
Return-Path: <jouni.nospam@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 190833A6C41 for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 02:19:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.109
X-Spam-Level: 
X-Spam-Status: No, score=-2.109 tagged_above=-999 required=5 tests=[AWL=0.490,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wnDV1SAoiMPG for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 02:19:55 -0700 (PDT)
Received: from mail-ew0-f215.google.com (mail-ew0-f215.google.com [209.85.219.215]) by core3.amsl.com (Postfix) with ESMTP id C41F93A6BAB for <multimob@ietf.org>; Fri,  3 Jul 2009 02:19:54 -0700 (PDT)
Received: by ewy11 with SMTP id 11so892335ewy.37 for <multimob@ietf.org>; Fri, 03 Jul 2009 02:20:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:cc:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=D+agsY49vy8vcW16JIkvDAY4ZjWzjkcB6JzSRlZHXLM=; b=STO1XZD4MGKEy02YMZ4GQKEWMqOmtmgzLzfiw/MK7h1MXPcqxLkDZpxI6rrdd+ROpQ 0n/f1wtNh8jqtvw5uOkB3Pf74JkohAib6sAkor4irtquUW7s73mWoRFt7tiZRaAVgNDZ 3ERRx5uqzwl24UGffMv7idofV21qqkK96r/5M=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=cc:message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=nFV/9lEaMPGti8Sy/MBArnjumohaJ6Nrzic83xVyk+drgQG4rBs+5QkjJNuOnQH43A 8X/HwOQIjL3vEHaT5LyVKjOgYW8XQwiNo+1ihb7feyQg5yvfG/6htpPX3c6cse78Wr5y cenF2EOrFg15FruFamOTkCiIEMlMMWo3LNXRw=
Received: by 10.210.76.4 with SMTP id y4mr1331115eba.86.1246612813286; Fri, 03 Jul 2009 02:20:13 -0700 (PDT)
Received: from ?10.254.0.121? ([192.100.123.77]) by mx.google.com with ESMTPS id 28sm8448893eyg.54.2009.07.03.02.20.12 (version=TLSv1/SSLv3 cipher=RC4-MD5); Fri, 03 Jul 2009 02:20:12 -0700 (PDT)
Message-Id: <748762AD-E801-4D48-A546-ABF63A79E878@gmail.com>
From: jouni korhonen <jouni.nospam@gmail.com>
To: gorry@erg.abdn.ac.uk
In-Reply-To: <4A4DC96A.4090008@erg.abdn.ac.uk>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Date: Fri, 3 Jul 2009 12:20:09 +0300
References: <4A4CCB84.4040703@erg.abdn.ac.uk>	<0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com>	<517894.29527.qm@web111403.mail.gq1.yahoo.com> <1B334D1F-0AC3-4A81-853C-B4B9F1F12733@gmail.com> <4A4DC96A.4090008@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.935.3)
Cc: multimob@ietf.org
Subject: Re: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 03 Jul 2009 09:19:56 -0000

Ok, fair enough.

Cheers,
	Jouni

On Jul 3, 2009, at 12:03 PM, Gorry Fairhurst wrote:

> The first change looks good, and I believe we have all benefited  
> from the discussions on the charter.
>
> I agree with Behcet, let's make the change in your last email.
>
> I'm not sure we need the last change proposed at the end of this  
> email. Specifically I am not keen on unpacking or detailing the  
> future work paragraph - If the main scope of work is addreseed, I  
> would expect there to be much more experience of interactions and  
> implications on v4 and v6 stacks. I would also very much expect a  
> future rechartering process to discuss exactly what is needed in  
> this space.
>
> I'd suggest avoid fine-tuning the wording here.
>
> Gorry
>
> jouni korhonen wrote:
>> Behcet,
>> On Jul 3, 2009, at 1:25 AM, Behcet Sarikaya wrote:
>>>
>>> Hi Jouni,
>>>>
>> [snip]
>>>>> Future work, subject to approval, may study/evaluate whether  
>>>>> extensions are
>>>> needed for the client-based mobility protocols (Mobile IPv6 and  
>>>> Dual-Stack
>>>> Mobile IPv6). Future work may also include protocol extensions to  
>>>> support source
>>>> mobility  and methods to allow a multi-homed mobile node to join  
>>>> multicast
>>>> groups and direct multicast flows to appropriate local interfaces.
>>>>
>>>> [JiK] Can't multi-homed host/mobile nodes already join multicast  
>>>> groups? Also, I
>>>> think a "clever" multi-homed host can direct multicast flows  
>>>> between its
>>>> interfaces with a stock MLDv[12]. So, what's the beef here?
>>>
>>> This is future work. We don't know at the moment how things will  
>>> evolve. But maybe the work could involve the definition of a  
>>> "clever" multi-homed host and related protocol modifications.
>>> Or some other things related to multicast flows.
>>> We suggest keeping it as future work?
>> I am fine with the other future work listen in the above paragraph.  
>> I just don't see immediately what work there could be related to  
>> multi-homed hosts and moving multicast feeds between its interfaces  
>> (be those of the same access technology or different). As of today  
>> a multi-homed host can join and leave multicast groups  
>> independently on each of its interface. That can be controlled on  
>> the application level (i.e. the "clever" host).
>> Maybe there is something to optimize in an multi-access tech multi- 
>> homed host case that I am not aware of. At minimum I would suggest  
>> to rephrase the:
>> "...and methods to allow a multi-homed mobile node to join  
>> multicast groups and direct multicast flows to appropriate local  
>> interfaces"
>> to
>> "...and optimizations to direct multicast flows to appropriate  
>> interfaces in a multi-homed host"
>> Cheers,
>>    Jouni
>>>
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>>
>>>
>>>
>> _______________________________________________
>> multimob mailing list
>> multimob@ietf.org
>> https://www.ietf.org/mailman/listinfo/multimob
>


From schmidt@informatik.haw-hamburg.de  Fri Jul  3 02:20:04 2009
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 01C8E3A6CB8 for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 02:20:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 92ryfcjfqKyi for <multimob@core3.amsl.com>; Fri,  3 Jul 2009 02:20:03 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.fhtw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 3B46D3A6BAB for <multimob@ietf.org>; Fri,  3 Jul 2009 02:20:01 -0700 (PDT)
Envelope-to: multimob@ietf.org
Received: from e178156175.adsl.alicedsl.de ([85.178.156.175] helo=[192.168.178.29]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1MMewS-000DBS-10; Fri, 03 Jul 2009 11:20:24 +0200
Message-ID: <4A4DCD57.6060308@informatik.haw-hamburg.de>
Date: Fri, 03 Jul 2009 11:20:23 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: gorry@erg.abdn.ac.uk
References: <4A4CCB84.4040703@erg.abdn.ac.uk>	<0DEE1184-BF1C-4B8A-B7C4-B2D25D3109C8@gmail.com>	<517894.29527.qm@web111403.mail.gq1.yahoo.com>	<1B334D1F-0AC3-4A81-853C-B4B9F1F12733@gmail.com> <4A4DC96A.4090008@erg.abdn.ac.uk>
In-Reply-To: <4A4DC96A.4090008@erg.abdn.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: multimob@ietf.org
Subject: Re: [multimob] Charter update
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 03 Jul 2009 09:20:04 -0000

Hi Gorry & Jouni,

Gorry Fairhurst wrote:
> 
> I'm not sure we need the last change proposed at the end of this email. 
> Specifically I am not keen on unpacking or detailing the future work 
> paragraph - If the main scope of work is addreseed, I would expect there 
> to be much more experience of interactions and implications on v4 and v6 
> stacks. I would also very much expect a future rechartering process to 
> discuss exactly what is needed in this space.
> 
> I'd suggest avoid fine-tuning the wording here.
> 
This appears quite convincing to me: Once we have worked on the subject 
& in the group for some while and intensity, a rechartering discussion 
will most likely be aware of additional experiences and insights, also 
from the work of the other mobility groups.

So I agree with Gorry to not dive to deeply into the issues of a future 
rechartering ...

Best regards,

Thomas


> jouni korhonen wrote:
>> Behcet,
>>
>>
>> On Jul 3, 2009, at 1:25 AM, Behcet Sarikaya wrote:
>>
>>>
>>> Hi Jouni,
>>>>
>>
>> [snip]
>>
>>
>>>>> Future work, subject to approval, may study/evaluate whether 
>>>>> extensions are
>>>> needed for the client-based mobility protocols (Mobile IPv6 and 
>>>> Dual-Stack
>>>> Mobile IPv6). Future work may also include protocol extensions to 
>>>> support source
>>>> mobility  and methods to allow a multi-homed mobile node to join 
>>>> multicast
>>>> groups and direct multicast flows to appropriate local interfaces.
>>>>
>>>> [JiK] Can't multi-homed host/mobile nodes already join multicast 
>>>> groups? Also, I
>>>> think a "clever" multi-homed host can direct multicast flows between 
>>>> its
>>>> interfaces with a stock MLDv[12]. So, what's the beef here?
>>>
>>> This is future work. We don't know at the moment how things will 
>>> evolve. But maybe the work could involve the definition of a "clever" 
>>> multi-homed host and related protocol modifications.
>>> Or some other things related to multicast flows.
>>> We suggest keeping it as future work?
>>
>>
>> I am fine with the other future work listen in the above paragraph. I 
>> just don't see immediately what work there could be related to 
>> multi-homed hosts and moving multicast feeds between its interfaces 
>> (be those of the same access technology or different). As of today a 
>> multi-homed host can join and leave multicast groups independently on 
>> each of its interface. That can be controlled on the application level 
>> (i.e. the "clever" host).
>>
>> Maybe there is something to optimize in an multi-access tech 
>> multi-homed host case that I am not aware of. At minimum I would 
>> suggest to rephrase the:
>> "...and methods to allow a multi-homed mobile node to join multicast 
>> groups and direct multicast flows to appropriate local interfaces"
>>
>> to
>>
>> "...and optimizations to direct multicast flows to appropriate 
>> interfaces in a multi-homed host"
>>
>>
>> Cheers,
>>     Jouni
>>
>>
>>>
>>>
>>> Regards,
>>>
>>> Behcet
>>>
>>>
>>>
>>>
>>
>> _______________________________________________
>> multimob mailing list
>> multimob@ietf.org
>> https://www.ietf.org/mailman/listinfo/multimob
>>
>>
> 
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °

From sijeon79@gmail.com  Sat Jul  4 05:54:40 2009
Return-Path: <sijeon79@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6AAFC3A6A8A for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 05:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fF+wzNFO1orE for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 05:54:39 -0700 (PDT)
Received: from mail-px0-f178.google.com (mail-px0-f178.google.com [209.85.216.178]) by core3.amsl.com (Postfix) with ESMTP id 999A93A6359 for <multimob@ietf.org>; Sat,  4 Jul 2009 05:54:39 -0700 (PDT)
Received: by pxi8 with SMTP id 8so3411188pxi.29 for <multimob@ietf.org>; Sat, 04 Jul 2009 05:55:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole; bh=vx4vKSO8PQVh+1jmASI5YmH5awL4EoAw1wrAW7qSK2w=; b=riDJcxy+Olm1f/9BAZtPpDpjxN6WUe+u9SVu5e0A3L6XyWAkukRN/osNsEDMjhXc4I qmvuaZgoQeJGxtUggoxOnrbSyhpBEY/jESh8MtWPhYWlqS/ZFyfcF+95B8C98w+jx4Q3 EYxk+3IWDCeQAxx0k8ZTEilg/P5ftdZzj0V1w=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:x-mimeole; b=UgKiststn+33rwKcB7euqCLp013eaSIKqX3Pte12lVpFUL16b0s+XKq3mT8Y4+VtwZ NOydWCKYoi0lldapxOQVN+1bNry9H+Pe3Uzw6Mxm+47pt34TGcJvG4dsYpzIx1RsoQot anvCOZ9gcdai38MNjY3zy8zNO+9q7a1R/oJpY=
Received: by 10.142.136.3 with SMTP id j3mr812258wfd.328.1246712102142; Sat, 04 Jul 2009 05:55:02 -0700 (PDT)
Received: from dcn153 ([220.70.2.100]) by mx.google.com with ESMTPS id 29sm4950883wfg.1.2009.07.04.05.55.00 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Jul 2009 05:55:00 -0700 (PDT)
From: "Seil Jeon" <sijeon79@gmail.com>
To: <multimob@ietf.org>
Date: Sat, 4 Jul 2009 21:54:46 +0900
Message-ID: <015701c9fca6$9d6b85d0$640246dc@dcn153>
MIME-Version: 1.0
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acn8pVrNZOqAVIV0Rlmit5en7PAVGAAAH/8w
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Subject: [multimob] FW: New Version Notification for draft-sijeon-multimob-mms-pmip6-00
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Jul 2009 12:54:40 -0000

 
Hello.. multimob All..

We have submitted a new draft for PMIPv6 multicasting.

Please take a look and let us know if you have any comments.

Thank you.. 


http://www.ietf.org/proceedings/staging/draft-sijeon-multimob-mms-pmip6-
00.txt



-----Original Message-----
From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
Sent: Saturday, July 04, 2009 9:45 PM
To: sijeon@dcn.ssu.ac.kr
Cc: jaehwoon@dongguk.edu; yhkim@dcn.ssu.ac.kr
Subject: New Version Notification for draft-sijeon-multimob-mms-pmip6-00 


A new version of I-D, draft-sijeon-multimob-mms-pmip6-00.txt has been
successfuly submitted by Seil Jeon and posted to the IETF repository.

Filename:	 draft-sijeon-multimob-mms-pmip6
Revision:	 00
Title:		 Mobile Multicasting Support in Proxy Mobile IPv6
Creation_date:	 2009-07-04
WG ID:		 Independent Submission
Number_of_pages: 9

Abstract:
To support IP-based group communication such as mobile IPTV in mobile
environment, IP multicasting is required. Two major constraints in mobile
multicasting are the tunnel convergence problem and high handover latency.
To reduce the constraints, several mobile multicasting schemes based on
Mobile IP have been proposed. To provide efficient mobile multicast service
related to two problems, we present a multicasting architecture and fast
handover scheme for Proxy Mobile IPv6 (PMIPv6).
 



The IETF Secretariat.


From schmidt@informatik.haw-hamburg.de  Sat Jul  4 06:25:43 2009
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 33E2428C294 for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 06:25:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level: 
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lC4znZnpR9Tc for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 06:25:42 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.fhtw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 20B573A685F for <multimob@ietf.org>; Sat,  4 Jul 2009 06:25:41 -0700 (PDT)
Envelope-to: multimob@ietf.org
Received: from e178160146.adsl.alicedsl.de ([85.178.160.146] helo=[192.168.178.29]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1MN5Fj-0008h5-ID; Sat, 04 Jul 2009 15:26:03 +0200
Message-ID: <4A4F5865.2020601@informatik.haw-hamburg.de>
Date: Sat, 04 Jul 2009 15:25:57 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Seil Jeon <sijeon79@gmail.com>
References: <015701c9fca6$9d6b85d0$640246dc@dcn153>
In-Reply-To: <015701c9fca6$9d6b85d0$640246dc@dcn153>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification for	draft-sijeon-multimob-mms-pmip6-00
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Jul 2009 13:25:43 -0000

Hi Seil,

I have a quick question: In your scenario, how do you expect MLD Reports 
to arrive at the MR?

Thanks,

Thomas

Seil Jeon wrote:
>  
> Hello.. multimob All..
> 
> We have submitted a new draft for PMIPv6 multicasting.
> 
> Please take a look and let us know if you have any comments.
> 
> Thank you.. 
> 
> 
> http://www.ietf.org/proceedings/staging/draft-sijeon-multimob-mms-pmip6-
> 00.txt
> 
> 
> 
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org] 
> Sent: Saturday, July 04, 2009 9:45 PM
> To: sijeon@dcn.ssu.ac.kr
> Cc: jaehwoon@dongguk.edu; yhkim@dcn.ssu.ac.kr
> Subject: New Version Notification for draft-sijeon-multimob-mms-pmip6-00 
> 
> 
> A new version of I-D, draft-sijeon-multimob-mms-pmip6-00.txt has been
> successfuly submitted by Seil Jeon and posted to the IETF repository.
> 
> Filename:	 draft-sijeon-multimob-mms-pmip6
> Revision:	 00
> Title:		 Mobile Multicasting Support in Proxy Mobile IPv6
> Creation_date:	 2009-07-04
> WG ID:		 Independent Submission
> Number_of_pages: 9
> 
> Abstract:
> To support IP-based group communication such as mobile IPTV in mobile
> environment, IP multicasting is required. Two major constraints in mobile
> multicasting are the tunnel convergence problem and high handover latency.
> To reduce the constraints, several mobile multicasting schemes based on
> Mobile IP have been proposed. To provide efficient mobile multicast service
> related to two problems, we present a multicasting architecture and fast
> handover scheme for Proxy Mobile IPv6 (PMIPv6).
>  
> 
> 
> 
> The IETF Secretariat.
> 
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob

-- 

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences                   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °

From sijeon79@gmail.com  Sat Jul  4 08:41:52 2009
Return-Path: <sijeon79@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9A9BE3A6834 for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 08:41:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.374
X-Spam-Level: 
X-Spam-Status: No, score=-1.374 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kKXXrrYlQ-da for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 08:41:51 -0700 (PDT)
Received: from wf-out-1314.google.com (wf-out-1314.google.com [209.85.200.171]) by core3.amsl.com (Postfix) with ESMTP id 139763A67AD for <multimob@ietf.org>; Sat,  4 Jul 2009 08:41:50 -0700 (PDT)
Received: by wf-out-1314.google.com with SMTP id 29so1125268wff.31 for <multimob@ietf.org>; Sat, 04 Jul 2009 08:42:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=HEd5Mb6kx+/Nbhd/QjkyLc5ISHoJ2s5LYB0XaJTO4/Y=; b=eEQ0Jb7f9jvNUYVGas7aY89w2Hk7UBWx+TbdWxqS4t17R7UA2SE2U5qN8cUzENCsyU 30/B5Aa5ryZVQXrNaSkdLlAIQ+rNXrzFbpuG2+t3ffDYpPB5Jr4yKabFHZArKwZV7mzs V8Im88iiuAu/w4Kbj1kyIgNeMeXPU1NX6UEr0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=SJml2rgxNd+3KLrm95Q4rfkt9eQTeGEbimpi3rzJ9OOaGPC0WckmrPJzLlj3Mi1uWr vaeoeBiVGyv14U/qJPIi3dNv6DD31OGOWo49kWe9ngz/OKC7EB7QTtOTouwegn0aYDzw a7n7Mmzv9H6RxlCXIsfHnLRETLIDASlzt5qPc=
Received: by 10.143.9.9 with SMTP id m9mr837358wfi.27.1246722132881; Sat, 04 Jul 2009 08:42:12 -0700 (PDT)
Received: from dcn153 ([220.70.2.100]) by mx.google.com with ESMTPS id 32sm15407368wfc.34.2009.07.04.08.42.11 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Jul 2009 08:42:12 -0700 (PDT)
From: "Seil Jeon" <sijeon79@gmail.com>
To: "'Thomas C. Schmidt'" <schmidt@informatik.haw-hamburg.de>
References: <015701c9fca6$9d6b85d0$640246dc@dcn153> <4A4F5865.2020601@informatik.haw-hamburg.de>
Date: Sun, 5 Jul 2009 00:41:57 +0900
Message-ID: <015801c9fcbd$f86aff30$640246dc@dcn153>
MIME-Version: 1.0
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acn8qvwLvR4AGHAiQv2AQRf4ez0B5wAEeCZw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <4A4F5865.2020601@informatik.haw-hamburg.de>
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification for	draft-sijeon-multimob-mms-pmip6-00
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Jul 2009 15:41:52 -0000

Hi.. Thomas,

As mentioned in the draft, MAG performs the function of MLD forwarding
proxy (MF-Proxy).=20

Therefore, MLD Reports received from a MN are delivered to the MAG.

The MAG forwards the message to the MR.


Thanks

Seil

-----Original Message-----
From: Thomas C. Schmidt [mailto:schmidt@informatik.haw-hamburg.de]=20
Sent: Saturday, July 04, 2009 10:26 PM
To: Seil Jeon
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification for draft-sijeon-
multimob-mms-pmip6-00

Hi Seil,

I have a quick question: In your scenario, how do you expect MLD Reports =
to
arrive at the MR?

Thanks,

Thomas

Seil Jeon wrote:
> =20
> Hello.. multimob All..
>=20
> We have submitted a new draft for PMIPv6 multicasting.
>=20
> Please take a look and let us know if you have any comments.
>=20
> Thank you..=20
>=20
>=20
> http://www.ietf.org/proceedings/staging/draft-sijeon-multimob-mms-pmip
> 6-
> 00.txt
>=20
>=20
>=20
> -----Original Message-----
> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
> Sent: Saturday, July 04, 2009 9:45 PM
> To: sijeon@dcn.ssu.ac.kr
> Cc: jaehwoon@dongguk.edu; yhkim@dcn.ssu.ac.kr
> Subject: New Version Notification for=20
> draft-sijeon-multimob-mms-pmip6-00
>=20
>=20
> A new version of I-D, draft-sijeon-multimob-mms-pmip6-00.txt has been=20
> successfuly submitted by Seil Jeon and posted to the IETF repository.
>=20
> Filename:	 draft-sijeon-multimob-mms-pmip6
> Revision:	 00
> Title:		 Mobile Multicasting Support in Proxy Mobile IPv6
> Creation_date:	 2009-07-04
> WG ID:		 Independent Submission
> Number_of_pages: 9
>=20
> Abstract:
> To support IP-based group communication such as mobile IPTV in mobile=20
> environment, IP multicasting is required. Two major constraints in=20
> mobile multicasting are the tunnel convergence problem and high =
handover
latency.
> To reduce the constraints, several mobile multicasting schemes based=20
> on Mobile IP have been proposed. To provide efficient mobile multicast =

> service related to two problems, we present a multicasting=20
> architecture and fast handover scheme for Proxy Mobile IPv6 (PMIPv6).
> =20
>=20
>=20
>=20
> The IETF Secretariat.
>=20
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob

--=20

Prof. Dr. Thomas C. Schmidt
=A1=C6 Hamburg University of Applied Sciences                   Berliner =
Tor 7
=A1=C6
=A1=C6 Dept. Informatik, Internet Technologies Group    20099 Hamburg, =
Germany
=A1=C6
=A1=C6 http://www.haw-hamburg.de/inet                   Fon: =
+49-40-42875-8452
=A1=C6
=A1=C6 http://www.informatik.haw-hamburg.de/~schmidt    Fax: =
+49-40-42875-8409
=A1=C6


From schmidt@informatik.haw-hamburg.de  Sat Jul  4 08:49:33 2009
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1AE0B28C2E2 for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 08:49:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.024
X-Spam-Level: 
X-Spam-Status: No, score=-1.024 tagged_above=-999 required=5 tests=[AWL=-1.225, BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AYVFreWk1Bg7 for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 08:49:32 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.fhtw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 29F9728C2D7 for <multimob@ietf.org>; Sat,  4 Jul 2009 08:49:31 -0700 (PDT)
Envelope-to: multimob@ietf.org
Received: from e178135053.adsl.alicedsl.de ([85.178.135.53] helo=[192.168.178.29]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1MN7US-000Grc-UH; Sat, 04 Jul 2009 17:49:25 +0200
Message-ID: <4A4F7A02.3010702@informatik.haw-hamburg.de>
Date: Sat, 04 Jul 2009 17:49:22 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Seil Jeon <sijeon79@gmail.com>
References: <015701c9fca6$9d6b85d0$640246dc@dcn153>	<4A4F5865.2020601@informatik.haw-hamburg.de> <015801c9fcbd$f86aff30$640246dc@dcn153>
In-Reply-To: <015801c9fcbd$f86aff30$640246dc@dcn153>
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: 8bit
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification	for	draft-sijeon-multimob-mms-pmip6-00
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Jul 2009 15:49:33 -0000

Hi Seil,

thanks for your reply.

Seil Jeon wrote:
> As mentioned in the draft, MAG performs the function of MLD forwarding
> proxy (MF-Proxy). 
> 
> Therefore, MLD Reports received from a MN are delivered to the MAG.
> 
> The MAG forwards the message to the MR.
> 

Yes, this is written in the draft and I read it. However, the question
was how the MLD reports travel from MAG to MR ? MLD packets are link-local.

Best regards,

Thomas

> -----Original Message-----
> From: Thomas C. Schmidt [mailto:schmidt@informatik.haw-hamburg.de] 
> Sent: Saturday, July 04, 2009 10:26 PM
> To: Seil Jeon
> Cc: multimob@ietf.org
> Subject: Re: [multimob] FW: New Version Notification for draft-sijeon-
> multimob-mms-pmip6-00
> 
> Hi Seil,
> 
> I have a quick question: In your scenario, how do you expect MLD Reports to
> arrive at the MR?
> 
> Thanks,
> 
> Thomas
> 
> Seil Jeon wrote:
>>  
>> Hello.. multimob All..
>>
>> We have submitted a new draft for PMIPv6 multicasting.
>>
>> Please take a look and let us know if you have any comments.
>>
>> Thank you.. 
>>
>>
>> http://www.ietf.org/proceedings/staging/draft-sijeon-multimob-mms-pmip
>> 6-
>> 00.txt
>>
>>
>>
>> -----Original Message-----
>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
>> Sent: Saturday, July 04, 2009 9:45 PM
>> To: sijeon@dcn.ssu.ac.kr
>> Cc: jaehwoon@dongguk.edu; yhkim@dcn.ssu.ac.kr
>> Subject: New Version Notification for 
>> draft-sijeon-multimob-mms-pmip6-00
>>
>>
>> A new version of I-D, draft-sijeon-multimob-mms-pmip6-00.txt has been 
>> successfuly submitted by Seil Jeon and posted to the IETF repository.
>>
>> Filename:	 draft-sijeon-multimob-mms-pmip6
>> Revision:	 00
>> Title:		 Mobile Multicasting Support in Proxy Mobile IPv6
>> Creation_date:	 2009-07-04
>> WG ID:		 Independent Submission
>> Number_of_pages: 9
>>
>> Abstract:
>> To support IP-based group communication such as mobile IPTV in mobile 
>> environment, IP multicasting is required. Two major constraints in 
>> mobile multicasting are the tunnel convergence problem and high handover
> latency.
>> To reduce the constraints, several mobile multicasting schemes based 
>> on Mobile IP have been proposed. To provide efficient mobile multicast 
>> service related to two problems, we present a multicasting 
>> architecture and fast handover scheme for Proxy Mobile IPv6 (PMIPv6).
>>  
>>
>>
>>
>> The IETF Secretariat.
>>
>> _______________________________________________
>> multimob mailing list
>> multimob@ietf.org
>> https://www.ietf.org/mailman/listinfo/multimob
> 

-- 

Prof. Dr. Thomas C. Schmidt
¡Æ Hamburg University of Applied Sciences                   Berliner Tor 7 ¡Æ
¡Æ Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany ¡Æ
¡Æ http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 ¡Æ
¡Æ http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 ¡Æ

From sijeon79@gmail.com  Sat Jul  4 09:35:42 2009
Return-Path: <sijeon79@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EC6213A69E6 for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 09:35:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.762
X-Spam-Level: 
X-Spam-Status: No, score=-0.762 tagged_above=-999 required=5 tests=[AWL=-0.613, BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W5dpd-OZ9cpW for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 09:35:42 -0700 (PDT)
Received: from mail-pz0-f198.google.com (mail-pz0-f198.google.com [209.85.222.198]) by core3.amsl.com (Postfix) with ESMTP id DEF8A3A6959 for <multimob@ietf.org>; Sat,  4 Jul 2009 09:35:41 -0700 (PDT)
Received: by pzk36 with SMTP id 36so3344581pzk.29 for <multimob@ietf.org>; Sat, 04 Jul 2009 09:35:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:cc:references:subject :date:message-id:mime-version:content-type:content-transfer-encoding :x-mailer:thread-index:x-mimeole:in-reply-to; bh=6xotnF7WkJCqjb0he0CyV6w6GdQComCI8w+3Eqtsvhc=; b=bXqNBIsAjCwjjQG2QyuUQ4RkU3lXRksgE8m99POuslXgORyHk7xRQJCGJO8A4D/S1o 63ZfALs7gQzfIe0yhJDoADS+j/2nS9HiY7VG2Zs8vdkC2LAt+UivupSgde7qRU+hbE8O UYfTyE5dNHjm1q9P1Eh3TulP6FHsRYzJUpGB0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:cc:references:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:thread-index :x-mimeole:in-reply-to; b=osdc9XPtwNDjpYpY4AUlZJUR/zIJIWv28B8/+u94i6+jt/HVJPxJpPL+X8Te0+ARCw UgFq6k1RCy+TA2QYh2W6zz9yu4BfnlyUkGiWzHfANG8Kz5IpcA6QryY6rIMFl3DtBQ86 euv3Go9K4v1cT1plnl+Dw1B8trTJ/2URE4+hM=
Received: by 10.143.33.16 with SMTP id l16mr859224wfj.104.1246725335712; Sat, 04 Jul 2009 09:35:35 -0700 (PDT)
Received: from dcn153 ([220.70.2.100]) by mx.google.com with ESMTPS id 27sm9911185wff.6.2009.07.04.09.35.34 (version=TLSv1/SSLv3 cipher=RC4-MD5); Sat, 04 Jul 2009 09:35:35 -0700 (PDT)
From: "Seil Jeon" <sijeon79@gmail.com>
To: "'Thomas C. Schmidt'" <schmidt@informatik.haw-hamburg.de>
References: <015701c9fca6$9d6b85d0$640246dc@dcn153>	<4A4F5865.2020601@informatik.haw-hamburg.de> <015801c9fcbd$f86aff30$640246dc@dcn153> <4A4F7A02.3010702@informatik.haw-hamburg.de>
Date: Sun, 5 Jul 2009 01:35:20 +0900
Message-ID: <015901c9fcc5$6d7d39d0$640246dc@dcn153>
MIME-Version: 1.0
Content-Type: text/plain; charset="ks_c_5601-1987"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Office Outlook 11
Thread-Index: Acn8vwKjwcQY5BFJRPGgYh8LwnUPOQAAFhQw
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
In-Reply-To: <4A4F7A02.3010702@informatik.haw-hamburg.de>
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification for draft-sijeon-multimob-mms-pmip6-00
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Jul 2009 16:35:43 -0000

Hi Thomas,

Thanks for your comment.

=20
When the MAG forwards the MLD packets, received from the MN, to the MR, =
it
uses its link-local address.

Best regards,

Seil


-----Original Message-----
From: Thomas C. Schmidt [mailto:schmidt@informatik.haw-hamburg.de]=20
Sent: Sunday, July 05, 2009 12:49 AM
To: Seil Jeon
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification for draft-sijeon-
multimob-mms-pmip6-00

Hi Seil,

thanks for your reply.

Seil Jeon wrote:
> As mentioned in the draft, MAG performs the function of MLD forwarding =

> proxy (MF-Proxy).
>=20
> Therefore, MLD Reports received from a MN are delivered to the MAG.
>=20
> The MAG forwards the message to the MR.
>=20

Yes, this is written in the draft and I read it. However, the question =
was
how the MLD reports travel from MAG to MR ? MLD packets are link-local.

Best regards,

Thomas

> -----Original Message-----
> From: Thomas C. Schmidt [mailto:schmidt@informatik.haw-hamburg.de]
> Sent: Saturday, July 04, 2009 10:26 PM
> To: Seil Jeon
> Cc: multimob@ietf.org
> Subject: Re: [multimob] FW: New Version Notification for draft-sijeon- =

> multimob-mms-pmip6-00
>=20
> Hi Seil,
>=20
> I have a quick question: In your scenario, how do you expect MLD=20
> Reports to arrive at the MR?
>=20
> Thanks,
>=20
> Thomas
>=20
> Seil Jeon wrote:
>> =20
>> Hello.. multimob All..
>>
>> We have submitted a new draft for PMIPv6 multicasting.
>>
>> Please take a look and let us know if you have any comments.
>>
>> Thank you..=20
>>
>>
>> http://www.ietf.org/proceedings/staging/draft-sijeon-multimob-mms-pmi
>> p
>> 6-
>> 00.txt
>>
>>
>>
>> -----Original Message-----
>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
>> Sent: Saturday, July 04, 2009 9:45 PM
>> To: sijeon@dcn.ssu.ac.kr
>> Cc: jaehwoon@dongguk.edu; yhkim@dcn.ssu.ac.kr
>> Subject: New Version Notification for=20
>> draft-sijeon-multimob-mms-pmip6-00
>>
>>
>> A new version of I-D, draft-sijeon-multimob-mms-pmip6-00.txt has been =

>> successfuly submitted by Seil Jeon and posted to the IETF repository.
>>
>> Filename:	 draft-sijeon-multimob-mms-pmip6
>> Revision:	 00
>> Title:		 Mobile Multicasting Support in Proxy Mobile IPv6
>> Creation_date:	 2009-07-04
>> WG ID:		 Independent Submission
>> Number_of_pages: 9
>>
>> Abstract:
>> To support IP-based group communication such as mobile IPTV in mobile =

>> environment, IP multicasting is required. Two major constraints in=20
>> mobile multicasting are the tunnel convergence problem and high=20
>> handover
> latency.
>> To reduce the constraints, several mobile multicasting schemes based=20
>> on Mobile IP have been proposed. To provide efficient mobile=20
>> multicast service related to two problems, we present a multicasting=20
>> architecture and fast handover scheme for Proxy Mobile IPv6 (PMIPv6).
>> =20
>>
>>
>>
>> The IETF Secretariat.
>>
>> _______________________________________________
>> multimob mailing list
>> multimob@ietf.org
>> https://www.ietf.org/mailman/listinfo/multimob
>=20

--=20

Prof. Dr. Thomas C. Schmidt
=A1=C6 Hamburg University of Applied Sciences                   Berliner =
Tor 7
=A1=C6
=A1=C6 Dept. Informatik, Internet Technologies Group    20099 Hamburg, =
Germany
=A1=C6
=A1=C6 http://www.haw-hamburg.de/inet                   Fon: =
+49-40-42875-8452
=A1=C6
=A1=C6 http://www.informatik.haw-hamburg.de/~schmidt    Fax: =
+49-40-42875-8409
=A1=C6


From schmidt@informatik.haw-hamburg.de  Sat Jul  4 10:04:26 2009
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 799C028C2E9 for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 10:04:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.871
X-Spam-Level: 
X-Spam-Status: No, score=-0.871 tagged_above=-999 required=5 tests=[AWL=-1.072, BAYES_00=-2.599, HELO_EQ_DE=0.35, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S6-YwZOrvYXP for <multimob@core3.amsl.com>; Sat,  4 Jul 2009 10:04:25 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.fhtw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 5687728C2D7 for <multimob@ietf.org>; Sat,  4 Jul 2009 10:04:24 -0700 (PDT)
Envelope-to: multimob@ietf.org
Received: from e178135053.adsl.alicedsl.de ([85.178.135.53] helo=[192.168.178.29]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1MN8fA-0005Ok-4T; Sat, 04 Jul 2009 19:04:32 +0200
Message-ID: <4A4F8B9D.90102@informatik.haw-hamburg.de>
Date: Sat, 04 Jul 2009 19:04:29 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Thunderbird 2.0.0.22 (Windows/20090605)
MIME-Version: 1.0
To: Seil Jeon <sijeon79@gmail.com>
References: <015701c9fca6$9d6b85d0$640246dc@dcn153>	<4A4F5865.2020601@informatik.haw-hamburg.de>	<015801c9fcbd$f86aff30$640246dc@dcn153>	<4A4F7A02.3010702@informatik.haw-hamburg.de> <015901c9fcc5$6d7d39d0$640246dc@dcn153>
In-Reply-To: <015901c9fcc5$6d7d39d0$640246dc@dcn153>
Content-Type: text/plain; charset=EUC-KR
Content-Transfer-Encoding: 8bit
Cc: multimob@ietf.org
Subject: Re: [multimob] FW: New Version Notification for	draft-sijeon-multimob-mms-pmip6-00
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 04 Jul 2009 17:04:26 -0000

Hi Seil,

thanks for clarification.

Seil Jeon wrote:

> When the MAG forwards the MLD packets, received from the MN, to the MR, it
> uses its link-local address.
> 
O.K. - this means, that you are considering one flat network containing
all MAGs and all MRs. I guess this should be mentioned explicitly,
preferably in the abstract of the draft.

Best regards,

Thomas

> -----Original Message-----
> From: Thomas C. Schmidt [mailto:schmidt@informatik.haw-hamburg.de] 
> Sent: Sunday, July 05, 2009 12:49 AM
> To: Seil Jeon
> Cc: multimob@ietf.org
> Subject: Re: [multimob] FW: New Version Notification for draft-sijeon-
> multimob-mms-pmip6-00
> 
> Hi Seil,
> 
> thanks for your reply.
> 
> Seil Jeon wrote:
>> As mentioned in the draft, MAG performs the function of MLD forwarding 
>> proxy (MF-Proxy).
>>
>> Therefore, MLD Reports received from a MN are delivered to the MAG.
>>
>> The MAG forwards the message to the MR.
>>
> 
> Yes, this is written in the draft and I read it. However, the question was
> how the MLD reports travel from MAG to MR ? MLD packets are link-local.
> 
> Best regards,
> 
> Thomas
> 
>> -----Original Message-----
>> From: Thomas C. Schmidt [mailto:schmidt@informatik.haw-hamburg.de]
>> Sent: Saturday, July 04, 2009 10:26 PM
>> To: Seil Jeon
>> Cc: multimob@ietf.org
>> Subject: Re: [multimob] FW: New Version Notification for draft-sijeon- 
>> multimob-mms-pmip6-00
>>
>> Hi Seil,
>>
>> I have a quick question: In your scenario, how do you expect MLD 
>> Reports to arrive at the MR?
>>
>> Thanks,
>>
>> Thomas
>>
>> Seil Jeon wrote:
>>>  
>>> Hello.. multimob All..
>>>
>>> We have submitted a new draft for PMIPv6 multicasting.
>>>
>>> Please take a look and let us know if you have any comments.
>>>
>>> Thank you.. 
>>>
>>>
>>> http://www.ietf.org/proceedings/staging/draft-sijeon-multimob-mms-pmi
>>> p
>>> 6-
>>> 00.txt
>>>
>>>
>>>
>>> -----Original Message-----
>>> From: IETF I-D Submission Tool [mailto:idsubmission@ietf.org]
>>> Sent: Saturday, July 04, 2009 9:45 PM
>>> To: sijeon@dcn.ssu.ac.kr
>>> Cc: jaehwoon@dongguk.edu; yhkim@dcn.ssu.ac.kr
>>> Subject: New Version Notification for 
>>> draft-sijeon-multimob-mms-pmip6-00
>>>
>>>
>>> A new version of I-D, draft-sijeon-multimob-mms-pmip6-00.txt has been 
>>> successfuly submitted by Seil Jeon and posted to the IETF repository.
>>>
>>> Filename:	 draft-sijeon-multimob-mms-pmip6
>>> Revision:	 00
>>> Title:		 Mobile Multicasting Support in Proxy Mobile IPv6
>>> Creation_date:	 2009-07-04
>>> WG ID:		 Independent Submission
>>> Number_of_pages: 9
>>>
>>> Abstract:
>>> To support IP-based group communication such as mobile IPTV in mobile 
>>> environment, IP multicasting is required. Two major constraints in 
>>> mobile multicasting are the tunnel convergence problem and high 
>>> handover
>> latency.
>>> To reduce the constraints, several mobile multicasting schemes based 
>>> on Mobile IP have been proposed. To provide efficient mobile 
>>> multicast service related to two problems, we present a multicasting 
>>> architecture and fast handover scheme for Proxy Mobile IPv6 (PMIPv6).
>>>  
>>>
>>>
>>>
>>> The IETF Secretariat.
>>>
>>> _______________________________________________
>>> multimob mailing list
>>> multimob@ietf.org
>>> https://www.ietf.org/mailman/listinfo/multimob
> 

-- 

Prof. Dr. Thomas C. Schmidt
¡Æ Hamburg University of Applied Sciences                   Berliner Tor 7 ¡Æ
¡Æ Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany ¡Æ
¡Æ http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 ¡Æ
¡Æ http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 ¡Æ

From behcetsarikaya@yahoo.com  Tue Jul  7 07:58:39 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 279B528C4BB for <multimob@core3.amsl.com>; Tue,  7 Jul 2009 07:58:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level: 
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[AWL=-0.009, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TdQht6543ReX for <multimob@core3.amsl.com>; Tue,  7 Jul 2009 07:58:38 -0700 (PDT)
Received: from web111406.mail.gq1.yahoo.com (web111406.mail.gq1.yahoo.com [67.195.15.162]) by core3.amsl.com (Postfix) with SMTP id 672C628C4B9 for <multimob@ietf.org>; Tue,  7 Jul 2009 07:58:38 -0700 (PDT)
Received: (qmail 13405 invoked by uid 60001); 7 Jul 2009 14:58:32 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1246978712; bh=vC8DIl3PV8jgJsGYrlJmpSeppCTFWLpljAQjlfvzBnc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=4irartSW/KOMB8FfruDr30Lt1s04PkZJxnr5/ENDBtdS0apJWLs4ySSZ+HjAwr/ONtFWrx6Nasef035rq65xyRgvlra3mA1DsEBgfl3/5nMwErVrVCEBPa/q0WxmLYG6Vdx/Ffkw9DQvZIePBkZqrxhMX2RMDmeRQGsJe/wYNS8=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3IfQRSljoRtj5/UiErZ4SwBRS0FzzcJDjloM/nNOVdEtG/1VhjFfkB7Xg+6/b5/cNV9OswjrRjesYiVdMALBrBgGQK4d4v8ucsqdVP5+xqIQ6vcCk4RCKCZ3Pk26PF8ee35RV9tNwmMM5u8vJ+3uKNMu+DvwSiG0qbazcRhbU5s=;
Message-ID: <804636.12717.qm@web111406.mail.gq1.yahoo.com>
X-YMail-OSG: OX7L39QVM1maSuos7LuzB7E3k4hxdarVdg9iV4sTK0V8NJpAELetiG8BnmCDjeZQHKCl26yk8M3qIMGHgdNGRllJ7.LBecnryH5F.jfloFiPyriXZ0MzNmBTiDyoiCoUNxnrRYkMAmBZ5T17RDI2nqLq0TBExbM68FJ0vOimGJK_684BKqXK4AiF81h5W8wO12INlwTQcBPMJRAGrVMGbXdbxjzyV0leQ9h0p4yczjgwRb42XL78WMi4pnLH2UgneHIElXVX1W22o.wTmvrquEIkE01dOWtbGhjjyb6TboWyr57Awn0uLePgJM1BKQ.gliKIFw--
Received: from [206.16.17.212] by web111406.mail.gq1.yahoo.com via HTTP; Tue, 07 Jul 2009 07:58:32 PDT
X-Mailer: YahooMailRC/1358.21 YahooMailWebService/0.7.289.15
Date: Tue, 7 Jul 2009 07:58:32 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [multimob] Multimob drafts
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 07 Jul 2009 14:58:39 -0000

Hi all,=0A=A0 These are the drafts submitted to Multimob in IETF draft repo=
sitory:=0A08=A0Mar=A02009=A0=A0draft-asaeda-multimob-igmp-mld-mobility-exte=
nsions =0A06=A0Jul=A02009=A0=A0draft-asaeda-multimob-igmp-mld-optimization =
=0A08=A0Mar=A02009=A0=A0draft-asaeda-multimob-pmip6-extension =0A20=A0Jun=
=A02008=A0=A0draft-deng-multimob-mip4 =0A19=A0Oct=A02008=A0=A0draft-deng-mu=
ltimob-pmip6-requirement =0A13=A0Jul=A02008=A0=A0draft-deng-multimob-ps-mob=
ilemulticast =0A13=A0May=A02009=A0=A0draft-gundavelli-multimob-pmip6basicmc=
ast-solution =0A30=A0Jun=A02009=A0=A0draft-hui-multimob-fast-handover =0A06=
=A0Jul=A02009=A0=A0draft-krishnan-multimob-pmip6basicmcast-solution =0A16=
=A0Oct=A02008=A0=A0draft-liu-multimob-igmp-mld-mobility-req =0A14=A0Jun=A02=
009=A0=A0draft-liu-multimob-multicast-receiver-mobility =0A05=A0Mar=A02009=
=A0=A0draft-sarikaya-multimob-overwireless-ps =0A21=A0Feb=A02008=A0=A0draft=
-sarikaya-multimob-ps =0A01=A0Jul=A02009=A0=A0draft-schmidt-multimob-pmipv6=
-mcast-deployment =0A04=A0Jul=A02009=A0=A0draft-sijeon-multimob-mms-pmip6 =
=0A04=A0Feb=A02009=A0=A0draft-von-hugo-multimob-agents =0A06=A0Nov=A02007=
=A0=A0draft-xia-multimob-hybrid =0A14=A0Jul=A02008=A0=A0draft-yang-multimob=
-mip6-mc-tunnel-opt =0A20=A0Nov=A02007=A0=A0draft-zhang-multimob-memcast-ps=
 =0A08=A0Aug=A02008=A0=A0draft-zhang-multimob-mld-mmcast =0A01=A0Oct=A02008=
=A0=A0draft-zhang-multimob-mldsas-mmcast =0A03=A0Nov=A02008=A0=A0draft-zhao=
-multimob-pmip6-solution=0A=0AThere are a few others submitted to other pla=
ces, we suggest those people to submit their drafts to Multimob.=0A=0AIf yo=
u have any updates on the above drafts, please submit them by next Monday, =
July 13, 2009.=0A=0ARegards,=0A=0ABehcet=0A=0A=0A      

From behcetsarikaya@yahoo.com  Wed Jul  8 15:39:49 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3BA9628B23E for <multimob@core3.amsl.com>; Wed,  8 Jul 2009 15:39:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.262
X-Spam-Level: 
X-Spam-Status: No, score=-2.262 tagged_above=-999 required=5 tests=[AWL=0.003,  BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T3amcO501D49 for <multimob@core3.amsl.com>; Wed,  8 Jul 2009 15:39:48 -0700 (PDT)
Received: from web111407.mail.gq1.yahoo.com (web111407.mail.gq1.yahoo.com [67.195.15.168]) by core3.amsl.com (Postfix) with SMTP id 604483A6FCD for <multimob@ietf.org>; Wed,  8 Jul 2009 15:39:48 -0700 (PDT)
Received: (qmail 91589 invoked by uid 60001); 8 Jul 2009 22:40:13 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1247092813; bh=NZZi2MxtN+vz9lk3AuVNbinll18D9WhGHeuLQGCoEBU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=hVuvnjhFXgxGTb6Y1qhYZEj47BMLTeOlkwBN1/ZbRWsvBr2MJRq3IvhTPt53DXhdtiH4cH5e+MZCfJHjK5OIaKEEjcqVx47QdRgzJDAW4hwG1I5Ti6bv01hXgcbiAWfr9B9IJiRtBmM7Iqi0Q5O7NMBXHPK2yq67gDfV7M27j0A=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=W5uWtTdOdZoAi5Swd5k8RA+LcQ2ys5vvMT0p0Bk9MEIpi25YnzrCMKIDppuu6xY9UsCPu2hU1NkHpXgsB6FZu9+pRUoftLX056C4gC+egFep4hn2LCQ3gy4i2eHR7mirZL4bFAbgQToY2cQXdoh7ZNGt5mMw5nKuygZGFB5PR80=;
Message-ID: <145172.91365.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: twNimv8VM1koC75yJzL.vvN1f.VrT_k83NiMDz1HEkBWc0Xf5dC5NuNYhD6YlYSySvuHnQa8QuGEK0FJppKBJK4zmm8DdptjYSg0LvK2XJpLt5m_udMyF4_cEENI2IoK8tB0HL8.GfwrxpH8t__R24KpR8HYMbPzD4QDTA0pa25N.G7FvV0xWQlRZxR798LsiSeJKGODwtnqPyGUk4molt1AbFNQAG5bzNBhIsmNTc5GNzQqOiyTvjeTy9RIPk1TJ.81VcurB_nkBuovoYUT_LU_WscBlRN0Ftlu.bY_4QgK6.aCU9rL8T03RYlyFCfjPZbXlZESzVhlqe_I7gJULSJ4gPcO8.wNtuwRAMY-
Received: from [206.16.17.212] by web111407.mail.gq1.yahoo.com via HTTP; Wed, 08 Jul 2009 15:40:12 PDT
X-Mailer: YahooMailRC/1358.21 YahooMailWebService/0.7.289.15
Date: Wed, 8 Jul 2009 15:40:12 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [multimob] Final BoF Date and Time and Room
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 08 Jul 2009 22:39:49 -0000

Hello Folks, =0A=A0 Multimob BoF will take place not on Friday afternoon as=
 originally scheduled=0A=0Abut =0A=0Aon Tuesday, July 28, 2009=0A=0Ajust be=
fore the social (I have not seen yet the social in the agenda)=0A=0Aduring =
17:10 - 18:10.=0A=0AFor details please see:=0Ahttps://datatracker.ietf.org/=
meeting/75/agenda.html=0A=0AThe agenda will be:=0A=0AMulticast Mobility BOF=
 (Multimob)=0A=0ATuesday, July 28, 2009 17:10 - 18:10 Room Congresshall B=
=0A=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=0ACHAIRS: Gorry=A0 Fairhurst <gorry@erg.abdn.ac.uk>=0A=A0=A0=A0=A0=A0=A0=
=A0 Behcet=A0 Sarikaya <sarikaya@ieee.org>=0A=A0=A0=A0=A0=A0=A0=A0 =0AAGEND=
A:=0A1. Administrativia (Chairs, 5 min) =0A=A0 - Note takers, Jabber scribe=
s=0A=A0 - Agenda bashing=0A=A0 =0A2. Multimob Problem Statement (Chairs/ADs=
, 15 min) =0A=A0 - Motivation and problem statement=0A=A0=A0=A0 - draft-irt=
f-mobopts-mmcastv6-ps-06=A0 =0A3. Operator requirements for multicast mobil=
ity (10 min) =0A=A0 -=A0 Requirements from a Global Operator (Dirk) 5=0A=A0=
 -=A0 Multicast Support Requirements for PMIP6 (Gang) 5=0A=A0 =0A4. Protoco=
ls=A0 (10 min) =0A=A0 - Group Management Solutions Overview (Thomas) 5=0A=
=A0=A0=A0 - draft-asaeda-multimob-igmp-mld-mobility-extensions=0A=A0 - Prox=
y Mobile IPv6 Solutions Overview (Suresh) 5=0A=A0=A0=A0 - draft-krishnan-mu=
ltimob-pmip6basicmcast-solution =0A=A0=A0=A0 - draft-schmidt-multimob-pmip6=
-mcast-deployment-00=0A=A0=A0=A0 - draft-sijeon-multimob-mms-pmip6=0A=A0=A0=
=A0 - draft-asaeda-multimob-pmip6-extension =0A5. Proposed Roadmap and Char=
ter Discussion (All, 20 min) =0A6. Conclusions and Next Steps (Chairs/ADs, =
5 min)=0A=0APresenters, please send your slides to the chairs.=0A=0ARegards=
,=0A=0AGorry & Behcet=0A=0A=0A=0A      

From yuankui.zhao@gmail.com  Mon Jul 13 08:06:52 2009
Return-Path: <yuankui.zhao@gmail.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7998728C45F for <multimob@core3.amsl.com>; Mon, 13 Jul 2009 08:06:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.149
X-Spam-Level: 
X-Spam-Status: No, score=-0.149 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_CHARSET_FARAWAY=2.45]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9rWfnOOePd2F for <multimob@core3.amsl.com>; Mon, 13 Jul 2009 08:06:51 -0700 (PDT)
Received: from mail-pz0-f198.google.com (mail-pz0-f198.google.com [209.85.222.198]) by core3.amsl.com (Postfix) with ESMTP id F293C28C486 for <multimob@ietf.org>; Mon, 13 Jul 2009 08:04:35 -0700 (PDT)
Received: by pzk36 with SMTP id 36so2711855pzk.29 for <multimob@ietf.org>; Mon, 13 Jul 2009 08:04:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=+9lCu3Tx4c1VRVVnz3c+AvKxMlcOjZhT+NJIyogjzWA=; b=CDzoun/DwgNXEcOvBIBwoM//eXhaifWYo/OJTD0zoya152997C7gaXf2UXjRTwiPqh yYvuwgvys/yuf7aFsS5ITeIeTeV3xeUfwWp1lunIwXlRLvlSjLf/bjuifIgG2OszZ4uA oLOUjN97TMAJ2Ul0XFxb5wkhh/e8z3f5lzgfg=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=DggyEg3Sv6mK49cfnJOJH65OlzIj8hWB5AlbmiqTjtVRrEpbYVeZ/aANxRvU90GxV4 c+eFxaPrvNH6sX/hDzOlo3YcHkT10fMt93HxPgzELVkN9qm2M97TM2LF/lOcoD4AfgSL ksVcwJjIB4rLaA/DUZBIM+26S88SygwAtdBhM=
MIME-Version: 1.0
Received: by 10.142.240.19 with SMTP id n19mr1454398wfh.198.1247497479058;  Mon, 13 Jul 2009 08:04:39 -0700 (PDT)
In-Reply-To: <20090713145850.BF7B93A6DF4@core3.amsl.com>
References: <20090713145850.BF7B93A6DF4@core3.amsl.com>
Date: Mon, 13 Jul 2009 23:04:39 +0800
Message-ID: <e71f48650907130804n2f566a30ob353c09a63de641e@mail.gmail.com>
From: "john.zhao" <yuankui.zhao@gmail.com>
To: multimob@ietf.org
Content-Type: text/plain; charset=GB2312
Content-Transfer-Encoding: quoted-printable
Subject: [multimob] New Version Notification for draft-zhao-multimob-pmip6-solution-03
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 13 Jul 2009 15:06:52 -0000

Hi all,

        I have updated my draft as the following. Welcome comment,
anything missed let me know ASAP.

        Best Rgds,
Thanks,

John.zhao


---------- Forwarded message ----------
From: IETF I-D Submission Tool <idsubmission@ietf.org>
Date: 2009/7/13
Subject: New Version Notification for draft-zhao-multimob-pmip6-solution-03
To: yuankui.zhao@gmail.com
=B3=AD=CB=CD=A3=BA pierrick.seite@orange-ftgroup.com



A new version of I-D, draft-zhao-multimob-pmip6-solution-03.txt has
been successfuly submitted by YuanKui ZHAO and posted to the IETF
repository.

Filename:        draft-zhao-multimob-pmip6-solution
Revision:        03
Title:           The Solution for Pmipv6 Multicast Service
Creation_date:   2009-07-13
WG ID:           Independent Submission
Number_of_pages: 24

Abstract:
To mobility scenario, multicast service is a valuable feature to
those mobile customers.  We need to consider how to integrate current
multicast service in PMIPv6 domain.  This draft will introduce this
kind of solution about proxy mobile multicast.  It explains the
system solution and framework about how to provide the proxy mobile
multicast system.



The IETF Secretariat.

From behcetsarikaya@yahoo.com  Tue Jul 14 09:31:31 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 67C9E3A6B6E for <multimob@core3.amsl.com>; Tue, 14 Jul 2009 09:31:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.269
X-Spam-Level: 
X-Spam-Status: No, score=-2.269 tagged_above=-999 required=5 tests=[AWL=-0.004, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZvpjiKosXFRO for <multimob@core3.amsl.com>; Tue, 14 Jul 2009 09:31:30 -0700 (PDT)
Received: from n2-vm0.bullet.mail.gq1.yahoo.com (n2-vm0.bullet.mail.gq1.yahoo.com [67.195.23.154]) by core3.amsl.com (Postfix) with SMTP id BA4E83A6B69 for <multimob@ietf.org>; Tue, 14 Jul 2009 09:31:30 -0700 (PDT)
Received: from [67.195.9.83] by n2.bullet.mail.gq1.yahoo.com with NNFMP; 14 Jul 2009 16:27:14 -0000
Received: from [67.195.9.97] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 14 Jul 2009 16:27:14 -0000
Received: from [127.0.0.1] by omp101.mail.gq1.yahoo.com with NNFMP; 14 Jul 2009 16:27:14 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 675193.17488.bm@omp101.mail.gq1.yahoo.com
Received: (qmail 70257 invoked by uid 60001); 14 Jul 2009 16:27:14 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1247588834; bh=2bJehVkShVLPdc2jiuFCHH7dxB9fkeJ71r0OZuumZPk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=H7GNMAS44RMjdCw5h8Zt0TikadafFQxrtiihxX3524RNkLc4xA40AvgGfE8cq4s295JVLa5JIqkBFdAIAHsk66x4FDsNcnbm2yPk8HLcV1wGyvqs7sGpVyitNw0UsbBMUDn9rHtZln50y4urBFkKE9Qf13O0vKF/C/RTyU1aahI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=wgBz1x4GK6TgvwEZEUjKYKoTH7A82W7QTfLNN/5sL6rY9dDXExsVWsXFaLtd8mgqs7XX4w/+Aq7dfObPpeD9m/AAS9eZrbyh3BSlEeDjrjO2sEL3itD5VOcaPZsDm/i0ABI1xtIUycjZoPELRWA59D46i+lm8wtLuUbG/6NdEaA=;
Message-ID: <452737.61586.qm@web111410.mail.gq1.yahoo.com>
X-YMail-OSG: WAzhdagVM1lwCSnc3SZrMNXDAfoitR5ZOcnQfWLqoe5nWXZQ_jmR3y7gWu5Cna1w3yPMJcUrEyb5exl1zNmVLIFfKqxheXQ5O3c146ysNKnFR4UZAWLVYGlTn1Jd92zXALQOcWSPyAbOxnpPb8kyq5DCmg5y0nvZjzgxeDyBVod_u0SkHky1fYz.xuOafRBnEI1y9W3N0fnFWdOpmmn40wt2lVuO6eCo69uR_lqrRzhzwQ8EQHdHsnoCo02xqTu4fGZjD_hjG4sI43wL7EEzht.GQgSdQUm.CvBgr.4iG9P.FbffWk9AWKJP.oePrRHSUkY9GbHK9UFRXAiYfnK7eqHNbwd.jW.D8QWf
Received: from [206.16.17.212] by web111410.mail.gq1.yahoo.com via HTTP; Tue, 14 Jul 2009 09:27:14 PDT
X-Mailer: YahooMailRC/1358.21 YahooMailWebService/0.7.289.15
Date: Tue, 14 Jul 2009 09:27:14 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [multimob] BoF Agenda posted
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 14 Jul 2009 16:31:31 -0000

Hello Folks,=0A=A0 We posted BoF agenda at:=0Ahttp://www.ietf.org/proceedin=
gs/09jul/agenda/multimob.html=0Awhich contains links to the presentations a=
s well. Some presentations are coming up soon, so please visit the agenda p=
age often.=0A=0A=A0 The agenda also contains links to the drafts. If your d=
raft is missing, please let me know.=0A=0ARegards,=0A=0AGorry & Behcet=0A=
=0A=0A      


From liuhui47967@huawei.com  Tue Jul 14 18:48:24 2009
Return-Path: <liuhui47967@huawei.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4D53A3A6958 for <multimob@core3.amsl.com>; Tue, 14 Jul 2009 18:48:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.188
X-Spam-Level: 
X-Spam-Status: No, score=-2.188 tagged_above=-999 required=5 tests=[AWL=0.411,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fZESOVUCq4mR for <multimob@core3.amsl.com>; Tue, 14 Jul 2009 18:48:23 -0700 (PDT)
Received: from szxga03-in.huawei.com (szxga03-in.huawei.com [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id ECA093A694C for <multimob@ietf.org>; Tue, 14 Jul 2009 18:48:22 -0700 (PDT)
Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KMS007JKV65UU@szxga03-in.huawei.com> for multimob@ietf.org; Wed, 15 Jul 2009 09:37:17 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KMS00GN0V65LZ@szxga03-in.huawei.com> for multimob@ietf.org; Wed, 15 Jul 2009 09:37:17 +0800 (CST)
Received: from l47967b ([10.111.12.139]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KMS00GC8V65QY@szxml04-in.huawei.com> for multimob@ietf.org; Wed, 15 Jul 2009 09:37:17 +0800 (CST)
Date: Wed, 15 Jul 2009 09:37:16 +0800
From: Liu Hui <liuhui47967@huawei.com>
In-reply-to: <452737.61586.qm@web111410.mail.gq1.yahoo.com>
To: 'Behcet Sarikaya' <sarikaya@ieee.org>, multimob@ietf.org
Message-id: <002801ca04ec$c995c870$8b0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=ISO-8859-1
Content-transfer-encoding: quoted-printable
Thread-index: AcoEoKOhrVkSz0/SSsuR7Uir98JLIQAQYk6Q
Subject: Re: [multimob] BoF Agenda posted
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 15 Jul 2009 01:48:24 -0000

Hi  Behcet,

The IGMP/MLD requirement draft in the agenda has been updated to a new
version.=20

The major changes is in section 4.4.  The wireless link type is =
abstracted
and classified and their requirements on IGMP/MLD protocols are =
discussed.
Other changes are for editorial improvement such as  better wording or
conciseness:

http://ietfreport.isoc.org/all-ids/draft-liu-multimob-igmp-mld-mobility-r=
eq-
02.txt

We welcome the comments of the group.


Best Regards,
Liu Hui


> -----Original Message-----
> From: multimob-bounces@ietf.org=20
> [mailto:multimob-bounces@ietf.org] On Behalf Of Behcet Sarikaya
> Sent: Wednesday, July 15, 2009 12:27 AM
> To: multimob@ietf.org
> Subject: [multimob] BoF Agenda posted
>=20
>=20
> Hello Folks,
> =A0 We posted BoF agenda at:
> http://www.ietf.org/proceedings/09jul/agenda/multimob.html
> which contains links to the presentations as well. Some=20
> presentations are coming up soon, so please visit the agenda=20
> page often.
>=20
> =A0 The agenda also contains links to the drafts. If your draft=20
> is missing, please let me know.
>=20
> Regards,
>=20
> Gorry & Behcet
>=20
>=20
>      =20
>=20
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob


From asaeda@sfc.wide.ad.jp  Wed Jul 15 02:45:34 2009
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6ABB23A6B8D for <multimob@core3.amsl.com>; Wed, 15 Jul 2009 02:45:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.706
X-Spam-Level: **
X-Spam-Status: No, score=2.706 tagged_above=-999 required=5 tests=[AWL=0.294,  BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, SARE_RECV_IP_222000=1.508]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8951rWfEEUH7 for <multimob@core3.amsl.com>; Wed, 15 Jul 2009 02:45:33 -0700 (PDT)
Received: from pione.sfc.wide.ad.jp (pione.sfc.wide.ad.jp [203.178.143.105]) by core3.amsl.com (Postfix) with ESMTP id B80FD3A6B1D for <multimob@ietf.org>; Wed, 15 Jul 2009 02:45:33 -0700 (PDT)
Received: from localhost (KHP222006121211.ppp-bb.dion.ne.jp [222.6.121.211]) by pione.sfc.wide.ad.jp (Postfix) with ESMTP id DB30D13D06C8 for <multimob@ietf.org>; Wed, 15 Jul 2009 18:45:32 +0900 (JST)
Date: Wed, 15 Jul 2009 18:45:36 +0900 (JST)
Message-Id: <20090715.184536.243831409.asaeda@sfc.wide.ad.jp>
To: multimob@ietf.org
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
X-Mailer: Mew version 5.2.54 on Emacs 22.2 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [multimob] three drafts available
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 15 Jul 2009 09:45:34 -0000

Hello folks,

The following drafts are available:

1. IGMP/MLD optimization
   draft-asaeda-multimob-igmp-mld-optimization-00.txt

2. IGMP/MLD protocol extension (Hold/Release extension)
   draft-asaeda-multimob-igmp-mld-mobility-extensions-03.txt

3. PMIPv6 protocol extension for IP multicast support
   draft-asaeda-multimob-pmip6-extension-02.txt

Regarding the first and second drafts, the previous draft,
igmp-mld-mobility-extensions-02, is split into these IGMP/MLD
optimization and extension drafts.

The third one is the PMIPv6 extension draft that provides the detail
spec for IP multicast support for PMIPv6. This version includes the
clear description for the protocol extension and reasons why protocol
extension is necessary for effective IP multicast communication with
PMIPv6.

According to the proposed bof agenda, the time slot to present them is
very limited, and hence I'd encourage you to read them, especially
PMIPv6 extension draft.

Regards,
--
Hitoshi Asaeda


From gorry@erg.abdn.ac.uk  Mon Jul 27 01:32:49 2009
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E5F4A3A69F5 for <multimob@core3.amsl.com>; Mon, 27 Jul 2009 01:32:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L0QD9+yX9Kdk for <multimob@core3.amsl.com>; Mon, 27 Jul 2009 01:32:49 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id E06223A68CF for <multimob@ietf.org>; Mon, 27 Jul 2009 01:32:48 -0700 (PDT)
Received: from dhcp-14b8.meeting.ietf.org (ra-gorry.erg.abdn.ac.uk [139.133.204.42]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n6R8WcBF017539 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Mon, 27 Jul 2009 09:32:39 +0100 (BST)
Message-ID: <4A6D6627.8010402@erg.abdn.ac.uk>
Date: Mon, 27 Jul 2009 10:32:39 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: multimob@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Subject: [multimob] Scribes and note takers on Tuesday - volunteer now!
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 27 Jul 2009 08:32:50 -0000

We need some volunteers to take notes and jabber-scribe for the
MultiMob BOF.  We have a full agenda and can't start the meeting without 
them, so please do volunteer now to save us time.

Volunteers please send an email to the chairs (in CC),

Gorry & Behcet

From behcetsarikaya@yahoo.com  Mon Jul 27 07:44:08 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E189B3A6A41 for <multimob@core3.amsl.com>; Mon, 27 Jul 2009 07:44:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.265
X-Spam-Level: 
X-Spam-Status: No, score=-2.265 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gnRpxEPCZiTO for <multimob@core3.amsl.com>; Mon, 27 Jul 2009 07:44:06 -0700 (PDT)
Received: from web111407.mail.gq1.yahoo.com (web111407.mail.gq1.yahoo.com [67.195.15.168]) by core3.amsl.com (Postfix) with SMTP id 0CE623A68FD for <multimob@ietf.org>; Mon, 27 Jul 2009 07:43:50 -0700 (PDT)
Received: (qmail 6216 invoked by uid 60001); 27 Jul 2009 14:43:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1248705828; bh=Kxxtd8HJOFowNI/G3d7XCHhltYHq3dwPYPBof1vCFLU=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=3mqMeKr5zYuN4T+LxDo5StefQ0Dpv1HIzk2PL1GtxJuu8rhd5oeYnVeCrbewP4tv/4gmxYV0g2rdXZCOh7caT/m4FJACv60y9eySy3z9U5I8s4Qu6GEQnEt1uQDURkOThDXbXeqyMoUAdWpO+waxUzTcofC8NEI1YzsxxbV6gE4=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=AB5sL8aPX1/ZnmHnR2ILxEDjIQcFOZ4lhKry7hiviTIQbi86erbBlYeW7SrnOcWOKztJpgURwu9+rR7EVWPCJ61JtFNE/IE1FQVMrkbQtVr/gqnzkf6clHo8Sns9RHiuu9s0AHCXEJbsiyxWZAlWv35aVZgNHx6vsHqWKoDPhEs=;
Message-ID: <929182.5351.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: Q_PPz.MVM1kf5ax5elwlER3ZTxKBGNR5EK5J2Etcaccu1ovCkfKuZiGAF8DI5ZFINwX5Vb1GOResUn15G_b7E7bBmvJWe_qg16MNC1_1.tauzc2gxd6xXwKV_7.FimzAWt1wbdcTRWmMQxxm7VJdNFCTRp_nSCamFG.xV4__CHtn8YMTpLiG1alSWBv5n8NKHKvqfH6Kpc2wkiLQ3zZMdM4n9hopzY.YF9qL9TGWLIV2FU4QxZMMZFwQ0AY0pSVfPj3r3pKz8btLN86JxhBocnp_EDkZBXnRg_o7s7I3yM8JvjylHaibRIiuMlIEoua5skeACWnWzc5iLzYV9A2bL5mSL._HgXqkXBCwpw--
Received: from [130.129.80.235] by web111407.mail.gq1.yahoo.com via HTTP; Mon, 27 Jul 2009 07:43:48 PDT
X-Mailer: YahooMailRC/1358.22 YahooMailWebService/0.7.338.1
Date: Mon, 27 Jul 2009 07:43:48 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [multimob] Multimob BoF
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Mon, 27 Jul 2009 14:44:08 -0000

Hello Folks,=0A=A0 We will have the BoF tomorrow (Tuesday Afternoon Session=
 III on July 28) starting at 17:10 at=A0Room 307 on Level 3=A0just before t=
he Social.=0A=A0 You can check the latest agenda and see the presentations =
online at:=0Ahttp://www.ietf.org/proceedings/75/agenda/multimob.html=0A=0AN=
ote the room change.=0A=0APlease attend the meeting and support Multimob.=
=0A=0ARegards,=0A=0AGorry& Behcet=0A=0A=0A      

From behcetsarikaya@yahoo.com  Tue Jul 28 01:15:16 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 019343A6D5B for <multimob@core3.amsl.com>; Tue, 28 Jul 2009 01:15:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.432
X-Spam-Level: 
X-Spam-Status: No, score=-2.432 tagged_above=-999 required=5 tests=[AWL=0.167,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ul1Wdr76Ryum for <multimob@core3.amsl.com>; Tue, 28 Jul 2009 01:15:15 -0700 (PDT)
Received: from n3.bullet.mail.re3.yahoo.com (n3.bullet.mail.re3.yahoo.com [68.142.237.110]) by core3.amsl.com (Postfix) with SMTP id E7B813A6CB6 for <multimob@ietf.org>; Tue, 28 Jul 2009 01:15:14 -0700 (PDT)
Received: from [68.142.237.87] by n3.bullet.mail.re3.yahoo.com with NNFMP; 28 Jul 2009 08:15:11 -0000
Received: from [67.195.9.83] by t3.bullet.re3.yahoo.com with NNFMP; 28 Jul 2009 08:15:11 -0000
Received: from [67.195.9.99] by t3.bullet.mail.gq1.yahoo.com with NNFMP; 28 Jul 2009 08:15:11 -0000
Received: from [127.0.0.1] by omp103.mail.gq1.yahoo.com with NNFMP; 28 Jul 2009 08:15:11 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 652323.50683.bm@omp103.mail.gq1.yahoo.com
Received: (qmail 18224 invoked by uid 60001); 28 Jul 2009 08:15:11 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1248768911; bh=sWU40GDfcmFpnruuG1dEkAQ2mIlf/fDk1OjRct02/b4=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=fhaiggExadlY8FPxK/wZSGYOBAeCaVzNFXkbTDPMuwoCGK/wT8kMAob9E7hHcsmhhlGMAGzZKA1a5P1xdlvWDLXuuHuYfNb2Djc16uhXa22F8/zSfT/0bE9nAt3F4yR2cftK55Cl4UDmKlEZHj47RD3i+Lims5i0atHQH+J5XzA=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=zmv3uLcrdASr9hjXmIYb3trRq8tYlswd18wWC6esqdgQ4wLoUj57aKD20vmEGFk15U3nop9OMNOiDqWTm/il9v2T8a9MJP+sFPaGGQKLZM18DiT8fiGYOPlfeg2/zyN6y2El8OrM/rBpp5g9u9fpda3nsyQQYvbJkfsq/xddK7s=;
Message-ID: <549429.17123.qm@web111412.mail.gq1.yahoo.com>
X-YMail-OSG: mMISi6YVM1l3L2wa_ocijYh6A.VQkT3E7hfVbDrwhMBAvzJK9FmxZ1ac5dzoZ8YD51AZOSFiXqYDdivx7tNtlFPpETvt29Jovo8ZobauTbSjqlF_Vc2kR1X7viQCyCOUuS_X12CNsm.HUfn1mPXzkVf8SwsdxkpOMF5nOWvphA68RGVjIqOzz851thjR12WyrLUbUY4SAhzPHNdVLpQwl8NiGOPPjInNJob502jjKMsFrudZflquVA50K.PtnjWa0uogb92y1wRZIdeUkfLmLHlbH7xz_BeOxLrxuOd6TQfYWoPp_zIK409c6C5SPECjj4BFRrdMSUg0eWAr65zrn7FdZ6M-
Received: from [130.129.87.243] by web111412.mail.gq1.yahoo.com via HTTP; Tue, 28 Jul 2009 01:15:11 PDT
X-Mailer: YahooMailRC/1358.22 YahooMailWebService/0.7.338.1
References: <005b01ca0f1f$b8033060$8b0c6f0a@china.huawei.com>
Date: Tue, 28 Jul 2009 01:15:11 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Liu Hui <liuhui47967@huawei.com>, multimob@ietf.org
In-Reply-To: <005b01ca0f1f$b8033060$8b0c6f0a@china.huawei.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [multimob] Multimob BoF
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jul 2009 08:15:16 -0000

Hi Hui,=0A=A0 I corrected the link. Thanks for pointing this out.=0A=0ARega=
rds,=0A=0ABehcet=0A=0A=0A=0A----- Original Message ----=0A> From: Liu Hui <=
liuhui47967@huawei.com>=0A> To: Behcet Sarikaya <sarikaya@ieee.org>=0A> Sen=
t: Monday, July 27, 2009 8:07:03 PM=0A> Subject: RE: [multimob] Multimob Bo=
F=0A> =0A> Hi Bechet,=0A> =0A> The link of the IGMP requirement draft is st=
ill version 1.=A0 Please make a=0A> check for it. =0A> =0A> Thanks,=0A> Liu=
 Hui=0A> =0A> =0A> > -----Original Message-----=0A> > From: multimob-bounce=
s@ietf.org =0A> > [mailto:multimob-bounces@ietf.org] On Behalf Of Behcet Sa=
rikaya=0A> > Sent: Monday, July 27, 2009 10:44 PM=0A> > To: multimob@ietf.o=
rg=0A> > Subject: [multimob] Multimob BoF=0A> > =0A> > Hello Folks,=0A> > =
=A0 We will have the BoF tomorrow (Tuesday Afternoon Session =0A> > III on =
July 28) starting at 17:10 at=A0Room 307 on Level 3=A0just =0A> > before th=
e Social.=0A> > =A0 You can check the latest agenda and see the presentatio=
ns online at:=0A> > http://www.ietf.org/proceedings/75/agenda/multimob.html=
=0A> > =0A> > Note the room change.=0A> > =0A> > Please attend the meeting =
and support Multimob.=0A> > =0A> > Regards,=0A> > =0A> > Gorry& Behcet=0A> =
> =0A> > =0A> >=A0 =A0 =A0 =0A> > _________________________________________=
______=0A> > multimob mailing list=0A> > multimob@ietf.org=0A> > https://ww=
w.ietf.org/mailman/listinfo/multimob=0A=0A=0A=0A      


From behcetsarikaya@yahoo.com  Tue Jul 28 02:27:49 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 48B473A6CEF for <multimob@core3.amsl.com>; Tue, 28 Jul 2009 02:27:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[AWL=-0.083, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 96bQs0qGjISF for <multimob@core3.amsl.com>; Tue, 28 Jul 2009 02:27:48 -0700 (PDT)
Received: from web111407.mail.gq1.yahoo.com (web111407.mail.gq1.yahoo.com [67.195.15.168]) by core3.amsl.com (Postfix) with SMTP id A00713A69E0 for <multimob@ietf.org>; Tue, 28 Jul 2009 02:27:48 -0700 (PDT)
Received: (qmail 80670 invoked by uid 60001); 28 Jul 2009 09:27:06 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1248773226; bh=k46D93cFIu2sd9ZAyr46MdNvpGfqpsSvKbeYffWxZe0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=6P/c6Wr5zZykcpX1wzRHz+YyNH9pGfl5xfx8iv026gFu8WSg9kb8lny8TJVZO83kkH55Kz882Ga+ZsksaxRlQ5mvjQJx3jY5aIypEe5nmz9gfpOdG8qgiwUSoTa6coDIQ7LqmQtj+BG7qIhrODZn3Gn7mxFIwgn+dHGhC59o+ak=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=LCy+te+mu4z10c7Qg2tFszNAeoNaxcL6/YQPP0D7lsb/nfGwKX15t5p7ZxpUzwQvxeNVphQjCsF3nlR4hLMuU/jf5S7G9FkqjwHLwaKzxMgKn83X9X1pBL3rb8YZuMRNu51QOabuBgQyuyKSOpyBnWO7YCmSvqM70TKNgUMlEtU=;
Message-ID: <823105.80590.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: BDWfqa8VM1m6E5J5O1TXuNxXxFzt84I33s0vWjuZ2TQ84Nqwy7ljRbkFqrmIQtyRB1871NaqVb4tc1nJoOtHLS_rFjsI5hD6.hLfLZ4.cVGNiA54lRhkYSkgk38ZozJFn1IF5rE5IyLPLD.TRNOdCe8E4mp_ZvNnERMPkb6b6cTD.tV.RMr70lIUxX3aooDr.C5uz3lUAeiWvAtnMekggDxyWNt9jTuQkZUZb_NlCnj7ft242zU.2nodLIrAyrSWKNuUgSgl.UtI.YK9y1Vlt_iE_m4pr.PJyiE7LrW_ERPYaiFiQD9qaFDYyEMEnH.Zknn008fevHto0.bJ5seQ1nfbuKJ362vEFlLAtv5_
Received: from [130.129.87.243] by web111407.mail.gq1.yahoo.com via HTTP; Tue, 28 Jul 2009 02:27:06 PDT
X-Mailer: YahooMailRC/1358.22 YahooMailWebService/0.7.338.1
References: <4A6D6627.8010402@erg.abdn.ac.uk>
Date: Tue, 28 Jul 2009 02:27:06 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
In-Reply-To: <4A6D6627.8010402@erg.abdn.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: Re: [multimob] Scribes and note takers on Tuesday - volunteer now!
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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, 28 Jul 2009 09:27:49 -0000

Folks so far we have a volunteer for Jabber. =0A=0AWe need volunteers for t=
aking the notes.=0A=0A=0A=A0=0A=0A=0A----- Original Message ----=0A> From: =
Gorry Fairhurst <gorry@erg.abdn.ac.uk>=0A> To: multimob@ietf.org=0A> Sent: =
Monday, July 27, 2009 3:32:39 AM=0A> Subject: [multimob] Scribes and note t=
akers on Tuesday - volunteer now!=0A> =0A> =0A> We need some volunteers to =
take notes and jabber-scribe for the=0A> MultiMob BOF.=A0 We have a full ag=
enda and can't start the meeting without them, =0A> so please do volunteer =
now to save us time.=0A> =0A> Volunteers please send an email to the chairs=
 (in CC),=0A> =0A> Gorry & Behcet=0A> _____________________________________=
__________=0A> multimob mailing list=0A> multimob@ietf.org=0A> https://www.=
ietf.org/mailman/listinfo/multimob=0A=0A=0A=0A      

From behcetsarikaya@yahoo.com  Wed Jul 29 04:56:27 2009
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2A97B3A69CF for <multimob@core3.amsl.com>; Wed, 29 Jul 2009 04:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.321
X-Spam-Level: 
X-Spam-Status: No, score=-2.321 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id StYQNpwKNrEX for <multimob@core3.amsl.com>; Wed, 29 Jul 2009 04:56:26 -0700 (PDT)
Received: from web111407.mail.gq1.yahoo.com (web111407.mail.gq1.yahoo.com [67.195.15.168]) by core3.amsl.com (Postfix) with SMTP id 6460D3A67B4 for <multimob@ietf.org>; Wed, 29 Jul 2009 04:56:26 -0700 (PDT)
Received: (qmail 4559 invoked by uid 60001); 29 Jul 2009 11:56:25 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1248868585; bh=0xa836IBJtFwPKwWd3WvcUGoJ/lpiRFWL5wXI7wAul0=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=nLH3AoQQEqCwabQA1F1C6w8OlGvcZWzRcbtwl8in/EjeJD6cEJm3EZ3IlDGafGOPWn2O72ZOekROzg4rC3nEERZsiiUfEuecALYCzIj6B2u0zxRGDnUAMe4W7FclOiyQQUCtw2dJdDEvAfDslpXBkqWJkE7F0zsCA6c7QKX2m1A=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=FkN+lGMrkd32GhAehbAHhZJObLcLV8mS1BLKzmgtjnHnjcZz61HRXiPLQfRB6TAROf+3ofyl5r9S6IOl4lnxYxK4Px58Picvp/GJbqBnReKTMXF+MBjzXqUhKdbXwo0FUb2eCdC5GrGJMV4xBOCC6lAUOWnrJqOk9b1vsYitnLM=;
Message-ID: <469281.4520.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: bui4mLYVM1kSq1H.IMpCFJp9OvniQi_uVirwLbc1ZA95nTV1KGhkMhz7mhTPhnkAn4C.McJYnW3FcGv0R9EGeZo8tLvjNv7d0bNXFU400cuw4ITrFQ_p5OoE9pmCRjAFW0FBtfJFT3aJBlg5GJ.qf_f64p5D3btBRobcCXxJ7QFZblVo.7DBuKmwmJFg.5sYdqv1Yqu_pI76gW_iTU154N1RUhXXL_dvdgVrRR6gI_CaCgN8NMw4uUfKFsaJyrwJ95s0vxkDByldb.8Pt7ou_RT9Zbnkax6WMHHwiHYc_t1GtiHtmogRkYUn.oC3dLwdZVrSu7rwKVCi2PXHZqUTr8FvtPzcEnXUI02tWQ--
Received: from [130.129.87.243] by web111407.mail.gq1.yahoo.com via HTTP; Wed, 29 Jul 2009 04:56:25 PDT
X-Mailer: YahooMailRC/1358.22 YahooMailWebService/0.7.338.1
Date: Wed, 29 Jul 2009 04:56:25 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable
Subject: [multimob] Minutes
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 29 Jul 2009 11:56:27 -0000

Hi all,=0A=A0 Draft minutes have been posted at:=0Ahttp://www.ietf.org/proc=
eedings/75/minutes/multimob.txt=0A=0AThanks to Matthias for his hard work i=
n taking the minutes.=0A=0AThe minutes will be detailed with Jabber activit=
y and a revised version will be posted later today.=0A=0ARegards,=0A=0AGorr=
y & Behcet=0A=0A=0A      

From gorry@erg.abdn.ac.uk  Wed Jul 29 08:40:12 2009
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A9DF93A692B for <multimob@core3.amsl.com>; Wed, 29 Jul 2009 08:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id IdEJviJYeOOQ for <multimob@core3.amsl.com>; Wed, 29 Jul 2009 08:40:11 -0700 (PDT)
Received: from erg.abdn.ac.uk (dee.erg.abdn.ac.uk [IPv6:2001:630:241:204:203:baff:fe9a:8c9b]) by core3.amsl.com (Postfix) with ESMTP id 8DBF33A6774 for <multimob@ietf.org>; Wed, 29 Jul 2009 08:40:10 -0700 (PDT)
Received: from dhcp-14b8.meeting.ietf.org (dhcp-14b8.meeting.ietf.org [130.129.20.184]) (authenticated bits=0) by erg.abdn.ac.uk (8.13.4/8.13.4) with ESMTP id n6TFdovc015032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 29 Jul 2009 16:39:51 +0100 (BST)
Message-ID: <4A706D47.1010302@erg.abdn.ac.uk>
Date: Wed, 29 Jul 2009 17:39:51 +0200
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Organization: The University of Aberdeen is a charity registered in Scotland,  No SC013683. 
User-Agent: Thunderbird 2.0.0.22 (Macintosh/20090605)
MIME-Version: 1.0
To: multimob@ietf.org
References: <469281.4520.qm@web111407.mail.gq1.yahoo.com>
In-Reply-To: <469281.4520.qm@web111407.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-ERG-MailScanner: Found to be clean
X-ERG-MailScanner-From: gorry@erg.abdn.ac.uk
Subject: Re: [multimob] Minutes
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: gorry@erg.abdn.ac.uk
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 29 Jul 2009 15:40:12 -0000

As promised by Behcet,

Here are the draft minutes. I'd like to solicit comments and 
corrections, by the 10th August.

http://www.ietf.org/proceedings/75/minutes/multimob.txt

I'd also like to extend a huge thank you to all who contributed to 
multimob - we had a sizeable set of technical contributions (which 
speaks of your interest in getting specifications defined) and many 
people helped in clarifying the Charter and what this means prior to the 
meeting - this was a great help in getting this BoF in place. We'll now 
have to await advice and directions from our Area Directors on the next 
steps.

Best wishes,

Gorry & Bhecet

Behcet Sarikaya wrote:
> Hi all,
>   Draft minutes have been posted at:
> http://www.ietf.org/proceedings/75/minutes/multimob.txt
> 
> Thanks to Matthias for his hard work in taking the minutes.
> 
> The minutes will be detailed with Jabber activity and a revised version will be posted later today.
> 
> Regards,
> 
> Gorry & Behcet
> 
> 
>       
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob
> 
> 


From pierrick.seite@orange-ftgroup.com  Thu Jul 30 02:03:12 2009
Return-Path: <pierrick.seite@orange-ftgroup.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EAA3928C17C for <multimob@core3.amsl.com>; Thu, 30 Jul 2009 02:03:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.166
X-Spam-Level: 
X-Spam-Status: No, score=0.166 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, HELO_EQ_FR=0.35, HTML_MESSAGE=0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n4eeGkEfJA8v for <multimob@core3.amsl.com>; Thu, 30 Jul 2009 02:03:11 -0700 (PDT)
Received: from R-MAIL1.rd.francetelecom.com (r-mail1.rd.francetelecom.com [217.108.152.41]) by core3.amsl.com (Postfix) with ESMTP id 1217E28C1A6 for <multimob@ietf.org>; Thu, 30 Jul 2009 02:03:10 -0700 (PDT)
Received: from ftrdmel0.rd.francetelecom.fr ([10.192.128.56]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 11:03:11 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA10F4.90475125"
Date: Thu, 30 Jul 2009 11:03:10 +0200
Message-ID: <843DA8228A1BA74CA31FB4E111A5C4623A739F@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: operator's requirements
Thread-Index: AcoQ9I/u5A4e+2E6R6G3eMmWD1rPtw==
From: <pierrick.seite@orange-ftgroup.com>
To: <multimob@ietf.org>
X-OriginalArrivalTime: 30 Jul 2009 09:03:11.0669 (UTC) FILETIME=[908CC650:01CA10F4]
Subject: [multimob] operator's requirements
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 30 Jul 2009 09:03:13 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA10F4.90475125
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Hi,
=20
I couldn't attend the multimob session due to the overlap with MEXT
session. However, I just want to say that I agree with operator's
requirements brought by Dirk. IMHO, harmonization with Multicast
delivery on fixed network and optimal routing are also requirements to
be taken into account.
=20
BR,
Pierrick

------_=_NextPart_001_01CA10F4.90475125
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 11">
<meta name=3DOriginator content=3D"Microsoft Word 11">
<link rel=3DFile-List href=3D"cid:filelist.xml@01CA1105.53755EB0">
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Helvetica 55 Roman";
	panose-1:2 0 5 3 4 0 0 2 0 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-2147483609 0 0 0 1 0;}
@font-face
	{font-family:"Helvetica 65 Medium";
	panose-1:2 0 6 3 2 0 0 2 0 4;
	mso-font-charset:0;
	mso-generic-font-family:auto;
	mso-font-pitch:variable;
	mso-font-signature:-2147483609 0 0 0 1 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
h1
	{mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:1;
	font-size:16.0pt;
	font-family:"Helvetica 55 Roman";
	mso-bidi-font-family:Arial;
	mso-font-kerning:16.0pt;
	mso-fareast-language:EN-US;}
h2
	{mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:2;
	font-size:14.0pt;
	font-family:"Helvetica 55 Roman";
	mso-bidi-font-family:Arial;
	mso-fareast-language:EN-US;
	font-style:italic;}
h3
	{mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:3;
	font-size:13.0pt;
	font-family:"Helvetica 65 Medium";
	mso-bidi-font-family:Arial;
	mso-fareast-language:EN-US;}
h4
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	page-break-after:avoid;
	mso-outline-level:4;
	font-size:14.0pt;
	font-family:"Helvetica 65 Medium";
	mso-fareast-language:EN-US;}
h5
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:5;
	font-size:13.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-language:EN-US;
	font-style:italic;}
h6
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:6;
	font-size:11.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-language:EN-US;}
p.MsoHeading7, li.MsoHeading7, div.MsoHeading7
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:7;
	font-size:12.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
p.MsoHeading8, li.MsoHeading8, div.MsoHeading8
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:8;
	font-size:12.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;
	font-style:italic;}
p.MsoHeading9, li.MsoHeading9, div.MsoHeading9
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin-top:12.0pt;
	margin-right:0cm;
	margin-bottom:3.0pt;
	margin-left:0cm;
	mso-pagination:widow-orphan;
	mso-outline-level:9;
	font-size:11.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Arial;
	mso-fareast-language:EN-US;}
p.MsoSalutation, li.MsoSalutation, div.MsoSalutation
	{mso-style-noshow:yes;
	mso-style-next:Normal;
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{mso-style-noshow:yes;
	margin:0cm;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	mso-bidi-font-size:12.0pt;
	font-family:"Helvetica 55 Roman";
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:"Times New Roman";
	mso-fareast-language:EN-US;}
span.EmailStyle19
	{mso-style-type:personal-compose;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:windowtext;}
@page Section1
	{size:595.3pt 841.9pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;
	mso-header-margin:35.4pt;
	mso-footer-margin:35.4pt;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:-132;
	mso-list-type:simple;
	mso-list-template-ids:-1607176040;}
@list l0:level1
	{mso-level-tab-stop:74.6pt;
	mso-level-number-position:left;
	margin-left:74.6pt;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:-131;
	mso-list-type:simple;
	mso-list-template-ids:-390418118;}
@list l1:level1
	{mso-level-tab-stop:60.45pt;
	mso-level-number-position:left;
	margin-left:60.45pt;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:-130;
	mso-list-type:simple;
	mso-list-template-ids:-461478350;}
@list l2:level1
	{mso-level-tab-stop:46.3pt;
	mso-level-number-position:left;
	margin-left:46.3pt;
	text-indent:-18.0pt;}
@list l3
	{mso-list-id:-129;
	mso-list-type:simple;
	mso-list-template-ids:1853684126;}
@list l3:level1
	{mso-level-tab-stop:32.15pt;
	mso-level-number-position:left;
	margin-left:32.15pt;
	text-indent:-18.0pt;}
@list l4
	{mso-list-id:-128;
	mso-list-type:simple;
	mso-list-template-ids:-242029094;}
@list l4:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:74.6pt;
	mso-level-number-position:left;
	margin-left:74.6pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l5
	{mso-list-id:-127;
	mso-list-type:simple;
	mso-list-template-ids:1904402946;}
@list l5:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:60.45pt;
	mso-level-number-position:left;
	margin-left:60.45pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l6
	{mso-list-id:-126;
	mso-list-type:simple;
	mso-list-template-ids:1008339786;}
@list l6:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:46.3pt;
	mso-level-number-position:left;
	margin-left:46.3pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l7
	{mso-list-id:-125;
	mso-list-type:simple;
	mso-list-template-ids:-670546496;}
@list l7:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:32.15pt;
	mso-level-number-position:left;
	margin-left:32.15pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
@list l8
	{mso-list-id:-120;
	mso-list-type:simple;
	mso-list-template-ids:1154267924;}
@list l8:level1
	{mso-level-tab-stop:18.0pt;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;}
@list l9
	{mso-list-id:-119;
	mso-list-type:simple;
	mso-list-template-ids:233211202;}
@list l9:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:18.0pt;
	mso-level-number-position:left;
	margin-left:18.0pt;
	text-indent:-18.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]-->
</head>

<body lang=3DFR link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:Arial'>Hi,<o:p></o:p></span></font>=
</p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
mso-bidi-font-size:10.0pt;font-family:Arial'><o:p>&nbsp;</o:p></span></fo=
nt></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;mso-bidi-font-size:10.0pt;font-family:Arial;mso-ansi-language:EN-G=
B'>I couldn't
attend the multimob session due to the overlap with MEXT session. =
However, I
just want to say that I agree with operator's requirements brought by =
Dirk. IMHO,
harmonization with Multicast delivery on fixed network and optimal =
routing are
also requirements to be taken into account.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;mso-bidi-font-size:10.0pt;font-family:Arial;mso-ansi-language:EN-G=
B'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;mso-bidi-font-size:10.0pt;font-family:Arial;mso-ansi-language:EN-G=
B'>BR,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;mso-bidi-font-size:10.0pt;font-family:Arial;mso-ansi-language:EN-G=
B'>Pierrick<o:p></o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01CA10F4.90475125--

From Dirk.von-Hugo@telekom.de  Thu Jul 30 02:09:28 2009
Return-Path: <Dirk.von-Hugo@telekom.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 24F5E28C209 for <multimob@core3.amsl.com>; Thu, 30 Jul 2009 02:09:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.484
X-Spam-Level: 
X-Spam-Status: No, score=-1.484 tagged_above=-999 required=5 tests=[AWL=0.275,  BAYES_05=-1.11, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFH8IAXR6Wfu for <multimob@core3.amsl.com>; Thu, 30 Jul 2009 02:09:27 -0700 (PDT)
Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by core3.amsl.com (Postfix) with ESMTP id ED0EF28C218 for <multimob@ietf.org>; Thu, 30 Jul 2009 02:08:45 -0700 (PDT)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail31.telekom.de with ESMTP; 30 Jul 2009 11:08:42 +0200
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 30 Jul 2009 11:08:41 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CA10F5.5485B801"
Date: Thu, 30 Jul 2009 11:08:40 +0200
Message-ID: <643B0A1D1A13AB498304E0BBC8027848012F6EA4@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <843DA8228A1BA74CA31FB4E111A5C4623A739F@ftrdmel0.rd.francetelecom.fr>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [multimob] operator's requirements
Thread-Index: AcoQ9I/u5A4e+2E6R6G3eMmWD1rPtwAADftw
References: <843DA8228A1BA74CA31FB4E111A5C4623A739F@ftrdmel0.rd.francetelecom.fr>
From: <Dirk.von-Hugo@telekom.de>
To: <pierrick.seite@orange-ftgroup.com>
X-OriginalArrivalTime: 30 Jul 2009 09:08:41.0860 (UTC) FILETIME=[555BEC40:01CA10F5]
Cc: multimob@ietf.org
Subject: Re: [multimob] operator's requirements
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Thu, 30 Jul 2009 09:09:28 -0000

This is a multi-part message in MIME format.

------_=_NextPart_001_01CA10F5.5485B801
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

Dear Pierrick,
I am happy you mention that point. I fully agree  - that's what I wanted
to express with FMC (Fixed Mobile Convergence), and I am glad if we
could discuss and evaluate that issue in more detail in the future
within the framework of a WG ;-)=20
Best regards,=20
Dirk=20
=20

________________________________

Von: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] Im
Auftrag von pierrick.seite@orange-ftgroup.com
Gesendet: Donnerstag, 30. Juli 2009 11:03
An: multimob@ietf.org
Betreff: [multimob] operator's requirements


Hi,
=20
I couldn't attend the multimob session due to the overlap with MEXT
session. However, I just want to say that I agree with operator's
requirements brought by Dirk. IMHO, harmonization with Multicast
delivery on fixed network and optimal routing are also requirements to
be taken into account.
=20
BR,
Pierrick

------_=_NextPart_001_01CA10F5.5485B801
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 6.00.2900.3527" name=3DGENERATOR>
<META content=3D"Microsoft Word 11" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01CA1105.53755EB0" rel=3DFile-List><!--[if gte =
mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:RelyOnVML/>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:HyphenationZone>21</w:HyphenationZone>
  <w:EnvelopeVis/>
  <w:PunctuationKerning/>
  <w:ValidateAgainstSchemas/>
  <w:SaveIfXMLInvalid>false</w:SaveIfXMLInvalid>
  <w:IgnoreMixedContent>false</w:IgnoreMixedContent>
  <w:AlwaysShowPlaceholderText>false</w:AlwaysShowPlaceholderText>
  <w:Compatibility>
   <w:BreakWrappedTables/>
   <w:SnapToGridInCell/>
   <w:WrapTextWithPunct/>
   <w:UseAsianBreakRules/>
   <w:DontGrowAutofit/>
  </w:Compatibility>
 </w:WordDocument>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:LatentStyles DefLockedState=3D"false" LatentStyleCount=3D"156">
 </w:LatentStyles>
</xml><![endif]-->
<STYLE>@font-face {
	font-family: Helvetica 55 Roman;
}
@font-face {
	font-family: Helvetica 65 Medium;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt =
90.0pt; mso-header-margin: 35.4pt; mso-footer-margin: 35.4pt; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-style-parent: ""; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"; mso-bidi-font-family: "Times New Roman"; mso-fareast-language: =
EN-US
}
LI.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-style-parent: ""; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"; mso-bidi-font-family: "Times New Roman"; mso-fareast-language: =
EN-US
}
DIV.MsoNormal {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-style-parent: ""; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"; mso-bidi-font-family: "Times New Roman"; mso-fareast-language: =
EN-US
}
H1 {
	FONT-SIZE: 16pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-bidi-font-family: Arial; =
mso-fareast-language: EN-US; mso-style-next: Normal; mso-outline-level: =
1; mso-font-kerning: 16.0pt
}
H2 {
	FONT-SIZE: 14pt; MARGIN: 12pt 0cm 3pt; FONT-STYLE: italic; FONT-FAMILY: =
"Helvetica 55 Roman"; mso-pagination: widow-orphan; =
mso-bidi-font-family: Arial; mso-fareast-language: EN-US; =
mso-style-next: Normal; mso-outline-level: 2
}
H3 {
	FONT-SIZE: 13pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 65 =
Medium"; mso-pagination: widow-orphan; mso-bidi-font-family: Arial; =
mso-fareast-language: EN-US; mso-style-next: Normal; mso-outline-level: =
3
}
H4 {
	FONT-SIZE: 14pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 65 =
Medium"; mso-pagination: widow-orphan; mso-fareast-language: EN-US; =
mso-style-next: Normal; mso-outline-level: 4; mso-style-noshow: yes
}
H5 {
	FONT-SIZE: 13pt; MARGIN: 12pt 0cm 3pt; FONT-STYLE: italic; FONT-FAMILY: =
"Helvetica 55 Roman"; mso-pagination: widow-orphan; =
mso-fareast-language: EN-US; mso-style-next: Normal; mso-outline-level: =
5; mso-style-noshow: yes
}
H6 {
	FONT-SIZE: 11pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-language: EN-US; =
mso-style-next: Normal; mso-outline-level: 6; mso-style-noshow: yes
}
P.MsoHeading7 {
	FONT-SIZE: 12pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"; mso-bidi-font-family: "Times New Roman"; =
mso-fareast-language: EN-US; mso-style-next: Normal; mso-outline-level: =
7; mso-style-noshow: yes
}
LI.MsoHeading7 {
	FONT-SIZE: 12pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"; mso-bidi-font-family: "Times New Roman"; =
mso-fareast-language: EN-US; mso-style-next: Normal; mso-outline-level: =
7; mso-style-noshow: yes
}
DIV.MsoHeading7 {
	FONT-SIZE: 12pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"; mso-bidi-font-family: "Times New Roman"; =
mso-fareast-language: EN-US; mso-style-next: Normal; mso-outline-level: =
7; mso-style-noshow: yes
}
P.MsoHeading8 {
	FONT-SIZE: 12pt; MARGIN: 12pt 0cm 3pt; FONT-STYLE: italic; FONT-FAMILY: =
"Helvetica 55 Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-next: Normal; =
mso-outline-level: 8; mso-style-noshow: yes
}
LI.MsoHeading8 {
	FONT-SIZE: 12pt; MARGIN: 12pt 0cm 3pt; FONT-STYLE: italic; FONT-FAMILY: =
"Helvetica 55 Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-next: Normal; =
mso-outline-level: 8; mso-style-noshow: yes
}
DIV.MsoHeading8 {
	FONT-SIZE: 12pt; MARGIN: 12pt 0cm 3pt; FONT-STYLE: italic; FONT-FAMILY: =
"Helvetica 55 Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-next: Normal; =
mso-outline-level: 8; mso-style-noshow: yes
}
P.MsoHeading9 {
	FONT-SIZE: 11pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"; mso-bidi-font-family: Arial; mso-fareast-language: EN-US; =
mso-style-next: Normal; mso-outline-level: 9; mso-style-noshow: yes
}
LI.MsoHeading9 {
	FONT-SIZE: 11pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"; mso-bidi-font-family: Arial; mso-fareast-language: EN-US; =
mso-style-next: Normal; mso-outline-level: 9; mso-style-noshow: yes
}
DIV.MsoHeading9 {
	FONT-SIZE: 11pt; MARGIN: 12pt 0cm 3pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times =
New Roman"; mso-bidi-font-family: Arial; mso-fareast-language: EN-US; =
mso-style-next: Normal; mso-outline-level: 9; mso-style-noshow: yes
}
P.MsoSalutation {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-next: Normal; =
mso-style-noshow: yes
}
LI.MsoSalutation {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-next: Normal; =
mso-style-noshow: yes
}
DIV.MsoSalutation {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-next: Normal; =
mso-style-noshow: yes
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-noshow: yes
}
LI.MsoAutoSig {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-noshow: yes
}
DIV.MsoAutoSig {
	FONT-SIZE: 10pt; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Helvetica 55 =
Roman"; mso-bidi-font-size: 12.0pt; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-bidi-font-family: "Times =
New Roman"; mso-fareast-language: EN-US; mso-style-noshow: yes
}
SPAN.EmailStyle19 {
	COLOR: windowtext; FONT-FAMILY: Arial; mso-bidi-font-size: 10.0pt; =
mso-bidi-font-family: Arial; mso-style-noshow: yes; mso-style-type: =
personal-compose; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: =
Arial; mso-hansi-font-family: Arial
}
DIV.Section1 {
	page: Section1
}
OL {
	MARGIN-BOTTOM: 0cm
}
UL {
	MARGIN-BOTTOM: 0cm
}
</STYLE>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Tableau Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
	mso-para-margin:0cm;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";
	mso-ansi-language:#0400;
	mso-fareast-language:#0400;
	mso-bidi-language:#0400;}
</style>
<![endif]--></HEAD>
<BODY lang=3DFR style=3D"tab-interval: 35.4pt" vLink=3Dpurple =
link=3Dblue>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D577440409-30072009>Dear Pierrick,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D577440409-30072009>I am happy you mention that point. I fully =
agree&nbsp;=20
- that's what I wanted to express with FMC (Fixed Mobile Convergence), =
and I am=20
glad if we could discuss and evaluate that issue in more detail&nbsp;in =
the=20
future within the framework of a WG ;-)&nbsp;</SPAN></FONT></DIV>
<DIV><SPAN lang=3Dde><FONT face=3D"Courier New"><FONT size=3D2><SPAN=20
class=3D577440409-30072009>Best regards</SPAN>,</FONT></FONT></SPAN> =
<BR><SPAN=20
lang=3Dde><FONT face=3D"Courier New" size=3D2>Dirk</FONT></SPAN> </DIV>
<DIV><FONT face=3DArial color=3D#0000ff size=3D2></FONT>&nbsp;</DIV><BR>
<DIV class=3DOutlookMessageHeader lang=3Dde dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>Von:</B> multimob-bounces@ietf.org=20
[mailto:multimob-bounces@ietf.org] <B>Im Auftrag von=20
</B>pierrick.seite@orange-ftgroup.com<BR><B>Gesendet:</B> Donnerstag, =
30. Juli=20
2009 11:03<BR><B>An:</B> multimob@ietf.org<BR><B>Betreff:</B> [multimob] =

operator's requirements<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=3DSection1>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
10.0pt">Hi,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
10.0pt"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
10.0pt; mso-ansi-language: EN-GB">I=20
couldn't attend the multimob session due to the overlap with MEXT =
session.=20
However, I just want to say that I agree with operator's requirements =
brought by=20
Dirk. IMHO, harmonization with Multicast delivery on fixed network and =
optimal=20
routing are also requirements to be taken into=20
account.<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
10.0pt; mso-ansi-language: EN-GB"><o:p>&nbsp;</o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
10.0pt; mso-ansi-language: EN-GB">BR,<o:p></o:p></SPAN></FONT></P>
<P class=3DMsoNormal><FONT face=3DArial size=3D2><SPAN lang=3DEN-GB=20
style=3D"FONT-SIZE: 10pt; FONT-FAMILY: Arial; mso-bidi-font-size: =
10.0pt; mso-ansi-language: =
EN-GB">Pierrick<o:p></o:p></SPAN></FONT></P></DIV></BODY></HTML>

------_=_NextPart_001_01CA10F5.5485B801--

From liuhui47967@huawei.com  Fri Jul 31 03:16:26 2009
Return-Path: <liuhui47967@huawei.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 3978028C0D7 for <multimob@core3.amsl.com>; Fri, 31 Jul 2009 03:16:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level: 
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553,  RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9mitWNLAhkHE for <multimob@core3.amsl.com>; Fri, 31 Jul 2009 03:16:25 -0700 (PDT)
Received: from szxga02-in.huawei.com (unknown [119.145.14.65]) by core3.amsl.com (Postfix) with ESMTP id 6107828C116 for <multimob@ietf.org>; Fri, 31 Jul 2009 03:16:25 -0700 (PDT)
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KNN00GUS5V4F3@szxga02-in.huawei.com> for multimob@ietf.org; Fri, 31 Jul 2009 18:16:17 +0800 (CST)
Received: from huawei.com ([172.24.1.33]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0KNN00M3Z5V4EB@szxga02-in.huawei.com> for multimob@ietf.org; Fri, 31 Jul 2009 18:16:16 +0800 (CST)
Received: from l47967b ([10.111.12.139]) by szxml06-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0KNN006YY5V4S7@szxml06-in.huawei.com> for multimob@ietf.org; Fri, 31 Jul 2009 18:16:16 +0800 (CST)
Date: Fri, 31 Jul 2009 18:16:16 +0800
From: Liu Hui <liuhui47967@huawei.com>
In-reply-to: <643B0A1D1A13AB498304E0BBC8027848012F6EA4@S4DE8PSAAQC.mitte.t-com.de>
To: Dirk.von-Hugo@telekom.de, pierrick.seite@orange-ftgroup.com
Message-id: <001301ca11c7$f095be70$8b0c6f0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 7BIT
Thread-index: AcoQ9I/u5A4e+2E6R6G3eMmWD1rPtwAADftwACw0z+A=
Cc: multimob@ietf.org
Subject: Re: [multimob] operator's requirements
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Fri, 31 Jul 2009 10:16:26 -0000

I agree these issues are worth exploring.  

There are already some suggestions on how to harmonize the fixed network
multicasting and mobile IP signalling, and on how to implement optimal
multicast forwarding in receiver mobility senario in the architecture draft
"draft-liu-multimob-multicast-receiver-mobility-00.txt". Section 2 gives
some general desciptions, and the latter sections show more details. I
recomment you to have a read on it and evaluate whether or not they are
applicable and complete regarding to the operator's requirements. 

It's a good thing that these commonly interested issues are discussed and
evaluated in the future.

Best Regards,
Liu Hui


> -----Original Message-----
> From: multimob-bounces@ietf.org 
> [mailto:multimob-bounces@ietf.org] On Behalf Of 
> Dirk.von-Hugo@telekom.de
> Sent: Thursday, July 30, 2009 5:09 PM
> To: pierrick.seite@orange-ftgroup.com
> Cc: multimob@ietf.org
> Subject: Re: [multimob] operator's requirements
> 
> Dear Pierrick,
> I am happy you mention that point. I fully agree  - that's 
> what I wanted to express with FMC (Fixed Mobile Convergence), 
> and I am glad if we could discuss and evaluate that issue in 
> more detail in the future within the framework of a WG ;-) 
> Best regards, Dirk 
>  
> 
> ________________________________
> 
> Von: multimob-bounces@ietf.org 
> [mailto:multimob-bounces@ietf.org] Im Auftrag von 
> pierrick.seite@orange-ftgroup.com
> Gesendet: Donnerstag, 30. Juli 2009 11:03
> An: multimob@ietf.org
> Betreff: [multimob] operator's requirements
> 
> 
> Hi,
>  
> I couldn't attend the multimob session due to the overlap 
> with MEXT session. However, I just want to say that I agree 
> with operator's requirements brought by Dirk. IMHO, 
> harmonization with Multicast delivery on fixed network and 
> optimal routing are also requirements to be taken into account.
>  
> BR,
> Pierrick
> 

