
From gaoxlh@gmail.com  Mon Nov  1 02:15:31 2010
Return-Path: <gaoxlh@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 CF8CD3A67D9 for <multimob@core3.amsl.com>; Mon,  1 Nov 2010 02:15:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level: 
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 HQMKWo-0-u7U for <multimob@core3.amsl.com>; Mon,  1 Nov 2010 02:15:31 -0700 (PDT)
Received: from mail-gw0-f44.google.com (mail-gw0-f44.google.com [74.125.83.44]) by core3.amsl.com (Postfix) with ESMTP id B15783A67C3 for <multimob@ietf.org>; Mon,  1 Nov 2010 02:15:30 -0700 (PDT)
Received: by gwb15 with SMTP id 15so3344347gwb.31 for <multimob@ietf.org>; Mon, 01 Nov 2010 02:15:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:x-mailer:mime-version:content-type; bh=JASa7eB3zYfckdyo5hFAQo33pMTzaSu9j46gK99URz0=; b=F0sxn5wRvGVnFnuRekl9znT7RqH5sIWCwPgXjUTkyMTRb/ZMIUO/f+d7CQcgcXW71F OKOw6o3FHgn9yPuvB8iS2uRsf7RShd0g1GHcVl1iQzl64JEg2DcNnGzLdZFpHJCTDEq/ 7z8vXRkEZtROJAoPogaYTlDQ0PDX0OrBnq6fM=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type; b=acwIBQokjATjs4/oxMXeR0j9Xanvona2upbqR7AK19bWpMtdwYpwfyIojQT9N5XZcL LBaXg5+0jfDSlc04CLkuByKvUKicNYDGmKyNtd6KTEIu7vaqphvjjlQ5inPIjOVSJYto KU/LrjzQ+eVLky7NQ7xHU/ySkFOd4+dHHtvlQ=
Received: by 10.151.44.20 with SMTP id w20mr24299205ybj.276.1288602931216; Mon, 01 Nov 2010 02:15:31 -0700 (PDT)
Received: from PC-201001071138 ([211.71.74.133]) by mx.google.com with ESMTPS id r6sm254550yba.11.2010.11.01.02.15.26 (version=SSLv3 cipher=RC4-MD5); Mon, 01 Nov 2010 02:15:29 -0700 (PDT)
Date: Mon, 1 Nov 2010 17:14:52 +0800
From: "Shuai Gao" <gaoxlh@gmail.com>
To: "multimob" <multimob@ietf.org>
Message-ID: <201011011714497960850@gmail.com>
X-mailer: Foxmail 6, 14, 103, 30 [cn]
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====001_Dragon600444812554_====="
Subject: [multimob] new version of draft-zhang-multimob-msm-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: Mon, 01 Nov 2010 09:15:31 -0000

This is a multi-part message in MIME format.

--=====001_Dragon600444812554_=====
Content-Type: text/plain;
	charset="gb2312"
Content-Transfer-Encoding: 7bit

Hi all,
	 We have completed a new revision of our multicast source mobility draft based on the comments we received.  But we missed the deadine of the IETF draft uploading system.  I attached the new draft in this mail 
and will submit it before the WG meeting. 

	As always, your comments are welcome.   

Best Regards,
 				

Shuai Gao
National Engineering Lab for Next Generation Internet Interconnection Devices
Beijing Jiaotong University
Beijing, China, 100044
gaoxlh@gmail.com
2010-11-01
--=====001_Dragon600444812554_=====
Content-Type: application/octet-stream;
	name="draft-zhang-multimob-msm-01.txt"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="draft-zhang-multimob-msm-01.txt"

DQoNCg0KDQoNCg0KDQoNCiAgICBNVUxUSU1PQiBXb3JraW5nIEdyb3VwICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgIEhvbmctS2UgWmhhbmcgDQogICAgSW50ZXJuZXQgRHJhZnQg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFpoaS1XZWkgWWFu
IA0KICAgIEV4cGlyZXM6IE1heSAyMDExICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIFNodWFpIEdhbyANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIExpLUxpIFdhbmcgDQogICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgQmVpamluZyBKaWFvdG9uZyBV
bml2ZXJzaXR5IA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgUWlhbiBXdQ0KICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICBIZS1XdSBMaSANCiAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIFRz
aW5naHVhIFVuaXZlcnNpdHkgIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgTm92ZW1iZXIgMSwgMjAxMCANCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgDQogICAgICAgICAgICAgICAgTXVsdGljYXN0IFNvdXJjZSBNb2JpbGl0eSBT
dXBwb3J0IGluIFBNSVB2NiBOZXR3b3JrIA0KICAgICAgICAgICAgICAgICAgICAgICAgICBkcmFm
dC16aGFuZy1tdWx0aW1vYi1tc20tMDEudHh0IA0KDQoNCiAgICBTdGF0dXMgb2YgdGhpcyBNZW1v
IA0KDQogICAgICAgQnkgc3VibWl0dGluZyB0aGlzIEludGVybmV0LURyYWZ0LCBlYWNoIGF1dGhv
ciByZXByZXNlbnRzIHRoYXQgYW55IA0KICAgICAgIGFwcGxpY2FibGUgcGF0ZW50IG9yIG90aGVy
IElQUiBjbGFpbXMgb2Ygd2hpY2ggaGUgb3Igc2hlIGlzIGF3YXJlIA0KICAgICAgIGhhdmUgYmVl
biBvciB3aWxsIGJlIGRpc2Nsb3NlZCwgYW5kIGFueSBvZiB3aGljaCBoZSBvciBzaGUgYmVjb21l
cyANCiAgICAgICBhd2FyZSB3aWxsIGJlIGRpc2Nsb3NlZCwgaW4gYWNjb3JkYW5jZSB3aXRoIFNl
Y3Rpb24gNiBvZiBCQ1AgNzkuIA0KDQogICAgICAgSW50ZXJuZXQtRHJhZnRzIGFyZSB3b3JraW5n
IGRvY3VtZW50cyBvZiB0aGUgSW50ZXJuZXQgRW5naW5lZXJpbmcgDQogICAgICAgVGFzayBGb3Jj
ZSAoSUVURiksIGl0cyBhcmVhcywgYW5kIGl0cyB3b3JraW5nIGdyb3Vwcy4gIE5vdGUgdGhhdCAN
CiAgICAgICBvdGhlciBncm91cHMgbWF5IGFsc28gZGlzdHJpYnV0ZSB3b3JraW5nIGRvY3VtZW50
cyBhcyBJbnRlcm5ldC1EcmFmdHMuIA0KDQogICAgICAgSW50ZXJuZXQtRHJhZnRzIGFyZSBkcmFm
dCBkb2N1bWVudHMgdmFsaWQgZm9yIGEgbWF4aW11bSBvZiBzaXggbW9udGhzIA0KICAgICAgIGFu
ZCBtYXkgYmUgdXBkYXRlZCwgcmVwbGFjZWQsIG9yIG9ic29sZXRlZCBieSBvdGhlciBkb2N1bWVu
dHMgYXQgYW55IA0KICAgICAgIHRpbWUuICBJdCBpcyBpbmFwcHJvcHJpYXRlIHRvIHVzZSBJbnRl
cm5ldC1EcmFmdHMgYXMgcmVmZXJlbmNlIA0KICAgICAgIG1hdGVyaWFsIG9yIHRvIGNpdGUgdGhl
bSBvdGhlciB0aGFuIGFzICJ3b3JrIGluIHByb2dyZXNzIi4gDQoNCiAgICAgICBUaGUgbGlzdCBv
ZiBjdXJyZW50IEludGVybmV0LURyYWZ0cyBjYW4gYmUgYWNjZXNzZWQgYXQgDQogICAgICAgICAg
ICBodHRwOi8vd3d3LmlldGYub3JnL2lldGYvMWlkLWFic3RyYWN0cy50eHQgDQoNCiAgICAgICBU
aGUgbGlzdCBvZiBJbnRlcm5ldC1EcmFmdCBTaGFkb3cgRGlyZWN0b3JpZXMgY2FuIGJlIGFjY2Vz
c2VkIGF0IA0KICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9zaGFkb3cuaHRtbCANCg0K
ICAgICAgIFRoaXMgSW50ZXJuZXQtRHJhZnQgd2lsbCBleHBpcmUgb24gTWF5LCAyMDExLiANCg0K
ICAgIEFic3RyYWN0IA0KDQogICAgICAgUHJveHkgTW9iaWxlIElQdjYsIHNwZWNpZmllZCBpbiBS
RkMgNTIxMywgaXMgYSBuZXR3b3JrLWJhc2VkIG1vYmlsaXR5IA0KICAgICAgIHByb3RvY29sLiBJ
dCB1c2VzIGEgTW9iaWxlIEFjY2VzcyBHYXRld2F5IChNQUcpIGFuZCBhIExvY2FsIE1vYmlsaXR5
IA0KICAgICAgIEFuY2hvciAoTE1BKSB0byBhbGxvdyBob3N0cyB0byBtb3ZlIGFyb3VuZCB3aXRo
aW4gYSBkb21haW4gd2hpbGUgDQogICAgICAga2VlcGluZyB0aGVpciBhZGRyZXNzIG9yIGFkZHJl
c3MgcHJlZml4IHN0YWJsZSBbMV0uIEFsdGhvdWdoIHRoZSANCiAgICAgICBpc3N1ZXMgb2YgbW9i
aWxlIG11bHRpY2FzdCBpbiB0aGUgUE1JUHY2IG5ldHdvcmsgYXJlIGJlaW5nIGRpc2N1c3NlZCAN
CiAgICAgICBpbiB0aGUgTXVsdGltb2IgV0csIGhvdyB0byBwcm92aWRlIHRoZSBzZXJ2aWNlIGNv
bm5lY3Rpdml0eSBmb3IgdGhlIA0KICAgICAgIG1vYmlsZSBtdWx0aWNhc3Qgc291cmNlIGlzIHN0
aWxsIGEgcHJvYmxlbSBmb3IgdGhlIFBNSVB2Ni4gVGhpcyANCiAgICAgICBkb2N1bWVudCBkaXNj
dXNzZXMgdGhlIGV4dGVuc2lvbnMgb2YgdGhlIFBNSVB2NiB0byBzdXBwb3J0IHRoZSANCiAgICAg
ICBtdWx0aWNhc3Qgc291cmNlIG1vYmlsaXR5LiANCiAgICAgDQoMICAgICANCiAgICAgDQogICAg
WmhhbmcgZXQgYWwuICAgICAgICAgICAgICBFeHBpcmVzIE1heSwyMDExICAgICAgICAgICAgICAg
ICAgICBbUGFnZSAxXSANCiAgICAgDQoMICAgIEludGVybmV0LURyYWZ0ICAgICAgTVNNIFN1cHBv
cnQgaW4gUE1JUHY2IE5ldHdvcmsgICAgICAgIE5vdmVtYmVyIDIwMTAgDQogICAgIA0KDQogICAg
Q29udmVudGlvbnMgdXNlZCBpbiB0aGlzIGRvY3VtZW50IA0KDQogICAgICAgVGhlIGtleSB3b3Jk
cyAiTVVTVCIsICJNVVNUIE5PVCIsICJSRVFVSVJFRCIsICJTSEFMTCIsICJTSEFMTCBOT1QiLCAN
CiAgICAgICAiU0hPVUxEIiwgIlNIT1VMRCBOT1QiLCAiUkVDT01NRU5ERUQiLCAiTUFZIiwgYW5k
ICJPUFRJT05BTCIgaW4gdGhpcyANCiAgICAgICBkb2N1bWVudCBhcmUgdG8gYmUgaW50ZXJwcmV0
ZWQgYXMgZGVzY3JpYmVkIGluIFtSRkMyMTE5XS4gDQoNCiAgICBUYWJsZSBvZiBDb250ZW50cyAN
Cg0KICAgICAgIDEuIEludHJvZHVjdGlvbi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLjIgDQogICAgICAgMi4gT3ZlcnZpZXcuLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMyANCiAgICAgICAzLiBFeHRlbnNpb25z
IG9mIFBNSVB2Ni4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi40IA0KICAg
ICAgICAgIDMuMS4gTU4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLjQgDQogICAgICAgICAgMy4yLiBNQUcuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uNCANCiAgICAgICAgICAzLjMuIExNQS4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi41IA0KICAgICAgIDQu
IE11bHRpY2FzdCBzb3VyY2UgbW9iaWxpdHkgcHJvY2VkdXJlLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLjUgDQogICAgICAgNS4gRm9ybWF0IG9mIHNpZ25hbGluZyBtZXNzYWdlcy4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uNiANCiAgICAgICAgICA1LjEuIFBCVS4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi42IA0KICAgICAgICAgIDUuMi4g
UEJBLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjcg
DQogICAgICAgICAgNS4zLiBNdWx0aWNhc3QgYWRkcmVzcyBvcHRpb24uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4uLi4uLi4uOCANCiAgICAgICA2LiBTZWN1cml0eSBDb25zaWRlcmF0aW9ucy4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi44IA0KICAgICAgIDcuIFJlZmVyZW5jZXMu
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjggDQogICAg
ICAgQXV0aG9ycycgQWRkcmVzc2VzLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4uLi4uLi4xMCANCiAgICAgICBJbnRlbGxlY3R1YWwgUHJvcGVydHkgU3RhdGVtZW50Li4uLi4u
Li4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLjEwIA0KICAgICAgIEZ1bGwgQ29weXJpZ2h0IFN0YXRl
bWVudC4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uMTEgDQogICAgICAgQWNr
bm93bGVkZ21lbnQuLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4uLi4u
Li4xMSANCiAgICAgICAgDQogICAgMS4gSW50cm9kdWN0aW9uIA0KDQogICAgICAgRGlmZmVyZW50
IGZyb20gTUlQdjYgWzJdLCBQTUlQdjYgWzFdIHdhcyBwcm9wb3NlZCB0byBzdXBwb3J0IHRoZSAN
CiAgICAgICBuZXR3b3JrLWJhc2VkIG1vYmlsaXR5IG1hbmFnZW1lbnQuIFRoZSBlbnRpdGllcyBp
biB0aGUgUE1JUHY2IGhhdmUgDQogICAgICAgdGhlIHJlc3BvbnNpYmlsaXR5IHRvIHRyYWNrIHRo
ZSBNTiwgdXBkYXRlIHRoZSBsb2NhdGlvbiBvZiB0aGUgTU4gYW5kIA0KICAgICAgIHJlZGlyZWN0
IHRoZSBwYWNrZXRzIHRvIGFuZCBmcm9tIHRoZSBNTi4gSG93ZXZlciwgdGhlIGJhc2ljIFBNSVB2
NiANCiAgICAgICBwcm90b2NvbCBvbmx5IHNvbHZlcyB0aGUgbW9iaWxpdHkgbWFuYWdlbWVudCBm
b3IgdGhlIE1OIHdoaWNoIGlzIA0KICAgICAgIGludm9sdmVkIGluIHRoZSB1bmljYXN0IGNvbW11
bmljYXRpb24uIEluIG9yZGVyIHRvIGRlcGxveSB0aGUgDQogICAgICAgbXVsdGljYXN0IHNlcnZp
Y2UgaW4gdGhlIFBNSVB2NiBuZXR3b3JrLCBtYW55IHNjaGVtZXMgaGF2ZSBiZWVuIA0KICAgICAg
IHByb3Bvc2VkIFszLTZdLiBIb3dldmVyLCBhbGwgb2YgdGhlc2Ugc2NoZW1lcyBhaW0gdG8gc3Vw
cG9ydCB0aGUgDQogICAgICAgbXVsdGljYXN0IHNlcnZpY2UgZm9yIHRoZSBtb2JpbGUgcmVjZWl2
ZXIgYW5kIGhvdyB0byBzdXBwb3J0IHRoZSANCiAgICAgICBtdWx0aWNhc3Qgc291cmNlIG1vYmls
aXR5IGluIHRoZSBQTUlQdjYgbmV0d29yayBpcyBub3QgeWV0IGRpc2N1c3NlZC4gDQogICAgICAg
V2l0aG91dCBkb3VidCwgdGhlIG11bHRpY2FzdCBzb3VyY2UgbW9iaWxpdHkgaXMgYWxzbyBhIHZl
cnkgaW1wb3J0YW50IA0KICAgICAgIGlzc3VlIGZvciB0aGUgZGVwbG95bWVudCBvZiB0aGUgbXVs
dGljYXN0IHNlcnZpY2UuIEZvciBleGFtcGxlLCB0aGVyZSANCiAgICAgICBpcyBhbiBhZHZhbmNl
ZCBjb25jZXB0IGJhc2VkIG9uIHRoZSBJbnRlbGxpZ2VudCBUcmFuc3BvcnQgU3lzdGVtcyANCiAg
ICAgICAoSVRTKSBzZXJ2aWNlLiBJbiB0aGlzIGNvbmNlcHQsIGFsbCB0aGUgdmVoaWNsZXMgb24g
dGhlIHNhbWUgcm91dGUgDQogICAgICAgYXJlIGlkZW50aWZpZWQgYnkgdXNpbmcgYSBHUFMgb3Ig
YSBjYXItbmF2aWdhdGlvbiBzeXN0ZW0uIFRoZSANCiAgICAgICB2ZWhpY2xlcyBtdWx0aWNhc3Qg
cmVhbC10aW1lIHZpZGVvIGluZm9ybWF0aW9uIGFib3V0IHRoZSANCiAgICAgICB0cmFuc3BvcnRh
dGlvbiB0aHJvdWdoIHRoZSBjb21tdW5pY2F0aW9uIGluZnJhc3RydWN0dXJlIGxpa2UgM0csIFdp
RmkgDQogICAgICAgdG8gdGhlIG90aGVyIHZlaGljbGVzIGludGVyZXN0ZWQgaW4gaXQuIFdlIGNh
bGwgdGhpcyBhZHZhbmNlIA0KICAgICAgIGluZm9ybWF0aW9uICdGdXR1cmUgdmlzaW9uJyBhbmQg
dGhlIHNpbWlsYXIgY29uY2VwdCBoYXMgYmVlbiBwcm9wb3NlZCANCiAgICAgDQogICAgIA0KICAg
IFpoYW5nIGV0IGFsLiAgICAgICAgICAgICAgRXhwaXJlcyBNYXksMjAxMSAgICAgICAgICAgICAg
ICAgICAgW1BhZ2UgMl0gDQogICAgICAgIA0KDCAgICBJbnRlcm5ldC1EcmFmdCAgICAgIE1TTSBT
dXBwb3J0IGluIFBNSVB2NiBOZXR3b3JrICAgICAgICBOb3ZlbWJlciAyMDEwIA0KICAgICANCg0K
ICAgICAgIGluIFs3XS4gVGhlIG11bHRpY2FzdCBzb3VyY2UgbW9iaWxpdHkganVzdCBwcm92aWRl
cyBhIG5ldHdvcmsgDQogICAgICAgZGlzdHJpYnV0aW9uIGZ1bmN0aW9uYWxpdHkgKHByb3RvY29s
KSB0byByZWFsaXplIHRoZSBhYm92ZSBjb25jZXB0LiANCg0KICAgICAgIEluIHRoaXMgZG9jdW1l
bnQsIGEgbXVsdGljYXN0IHNvdXJjZSBtb2JpbGl0eSBzdXBwb3J0aW5nIHNjaGVtZSBpcyANCiAg
ICAgICBwcm9wb3NlZC4gSW4gdGhpcyBzY2hlbWUsIHRoZSBiYXNpYyBQTUlQdjYgc2lnbmFsaW5n
cyBhcmUgZXh0ZW5kZWQgDQogICAgICAgYW5kIHRoZSBMTUEgd2hpY2ggYWN0cyBhcyB0aGUgUlAg
KFJlbmRlenZvdXMgUG9pbnQpLCByZXNwb25zZXMgdG8gdGhlIA0KICAgICAgIGpvaW4gbWVzc2Fn
ZSBzZW50IHRvIHRoZSBzb3VyY2UgKGUuZy4sIE1OKS4gVGhlIG11bHRpY2FzdCBwYWNrZXRzIGFy
ZSANCiAgICAgICBzZW50IGZyb20gTU4gdG8gdGhlIExNQSBhcyB0aGUgYmFzaWMgUE1JUHY2IHNw
ZWNpZmllZC4gVGhlbiB0aGVzZSAgDQogICAgICAgcGFja2V0cyBhcmUgdHJhbnNtaXR0ZWQgdGhy
b3VnaCB0aGUgbXVsdGljYXN0IHRyZWUgZXN0YWJsaXNoZWQgDQogICAgICAgYmV0d2VlbiB0aGUg
TE1BIGFuZCB0aGUgcmVjZWl2ZXJzIHVzaW5nIHRoZSB0cmFkaXRpb25hbCBtdWx0aWNhc3QgDQog
ICAgICAgcm91dGluZyBwcm90b2NvbHMuICANCg0KICAgIDIuIE92ZXJ2aWV3ICANCg0KICAgICAg
IFRoZSBwcm9ibGVtIG9mIG11bHRpY2FzdCBzb3VyY2UgbW9iaWxpdHkgd2FzIGFsc28gY29uY2Vy
bmVkIGluIHRoZSANCiAgICAgICBNSVB2NiBuZXR3b3JrIGluIHdoaWNoIHRoZSBSUFQtYmFzZWQg
KFJlbmRlenZvdXMgUG9pbnQgVHJlZS1iYXNlZCkgDQogICAgICAgc2NoZW1lIGFuZCB0aGUgU1BU
LWJhc2VkIChTaG9ydGVzdCBQYXRoIFRyZWUtYmFzZWQpIHNjaGVtZSBhcmUgDQogICAgICAgcHJv
cG9zZWQgYXMgdHdvIHNvbHV0aW9ucyBbOF0uIEluIHRoZSBSUFQtYmFzZWQgc2NoZW1lLCB0aGUg
SG9tZSANCiAgICAgICBBZ2VudCAoSEEpIGFjdHMgYXMgdGhlIFJQIGluIG9yZGVyIHRvIHByb3Zp
ZGUgdGhlIHRyYW5zcGFyZW5jeSBvZiANCiAgICAgICBzb3VyY2UgbW9iaWxpdHkuIFRoZSBtdWx0
aWNhc3QgdHJlZSBpcyBzdGFibGUsIHdoaWxlIHRoZSBtdWx0aWNhc3QgDQogICAgICAgcGF0aCBt
YXkgbm90IGJlIG9wdGltaXplZCBpbiB0aGlzIHNjaGVtZS4gSW4gdGhlIFNQVC1iYXNlZCBzY2hl
bWUsIA0KICAgICAgIHRoZSBNTiBuZWVkIHJlY29uc3RydWN0IHRoZSBtdWx0aWNhc3QgdHJlZSBv
bmNlIHRoZSBMMyAobmV0d29yayBsYXllcikgDQogICAgICAgaGFuZG92ZXIgaGFwcGVucy4gVGhl
IG11bHRpY2FzdCBwYXRoIGNhbiBiZSBvcHRpbWl6ZWQgaW4gdGhpcyBjYXNlLCANCiAgICAgICBo
b3dldmVyLCB0aGUgZnJlcXVlbnQgaGFuZG92ZXIgb2YgdGhlIHNvdXJjZSBtYXkgbGVhZCB0byB0
aGUgDQogICAgICAgdW5zdGFiaWxpdHkgb2YgdGhlIG11bHRpY2FzdCB0cmVlLiAgDQoNCiAgICAg
ICBUaGUgYWJvdmUgdHdvIHNjaGVtZXMgY2FuIGFsc28gYmUgdXNlZCBpbiB0aGUgUE1JUHY2IG5l
dHdvcmsuIEZvciB0aGUgDQogICAgICAgU1BULWJhc2VkIHNjaGVtZSwgdGhlIFNQVCBjYW4gYmUg
cmVjb25zdHJ1Y3RlZCBvbmNlIHRoZSBNTiBtb3ZlcyB0byANCiAgICAgICB0aGUgbmV3IE1BRy4g
QW5kIGZvciB0aGUgUlBULWJhc2VkIHNjaGVtZSwgdGhlIExNQSBjYW4gYWN0IGFzIHRoZSBSUCAN
CiAgICAgICBmb3IgdGhlIE1OLiAgSG93ZXZlciwgdGhlIFNQVC1iYXNlZCBzY2hlbWUgaXMgbm90
IHN1aXRhYmxlIGluIHRoZSANCiAgICAgICBQTUlQdjYgbmV0d29yayBkdWUgdG8gdGhlIGZvbGxv
d2luZyByZWFzb25zOiANCg0KICAgICAgIC0tLVRoZSBQTUlQdjYgaXMgdXNlZCB0byBlbmhhbmNl
IHRoZSBoYW5kb3ZlciBwZXJmb3JtYW5jZSBmb3IgdGhlIE1OLCANCiAgICAgICB3aGljaCBtb3Zl
cyBpbiB0aGUgcmVzdHJpY3RlZCBkb21haW4uIFNvIHRoZSBMTUEgYW5kIHRoZSBNQUcgbWF5IG5v
dCANCiAgICAgICBiZSBzbyBmYXIuIEluIG90aGVyIHdvcmRzLCB0aGUgZGlmZmVyZW5jZXMgYmV0
d2VlbiB0aGUgdHdvIHBhdGhzIA0KICAgICAgIGNvcnJlc3BvbmRpbmcgdG8gdGhlIFJQVC1iYXNl
ZCBzY2hlbWUgYW5kIHRoZSBTUFQtYmFzZWQgc2NoZW1lIG1heSANCiAgICAgICBub3QgYmUgc28g
ZXZpZGVudDsgDQoNCiAgICAgICAtLS1UaGUgc3RhYmlsaXR5IG9mIHRoZSBtdWx0aWNhc3QgdHJl
ZSBpcyBhIHZlcnkgaW1wb3J0YW50IGZhY3RvciBmb3IgDQogICAgICAgdGhlIG11bHRpY2FzdCBz
ZXJ2aWNlLCB3aGljaCBhZmZlY3RzIHRoZSBkaXNydXB0aW9uIGxhdGVuY3kgYW5kIHRoZW4gDQog
ICAgICAgdGhlIHBlcmZvcm1hbmNlIG9mIHRoZSBtdWx0aWNhc3Qgc2VydmljZSBkdXJpbmcgdGhl
IG11bHRpY2FzdCBzb3VyY2UgDQogICAgICAgbW9iaWxpdHkuIEhvd2V2ZXIsIGluIHRoZSBTUFQt
YmFzZWQgc2NoZW1lLCB0aGUgbXVsdGljYXN0IHRyZWUgbmVlZHMgDQogICAgICAgdG8gYmUgcmVj
b25zdHJ1Y3RlZCBldmVuIHRoZSBNTiBtb3ZlcyBiZXR3ZWVuIHR3byBuZWFyYnkgTUFHcywgd2hp
Y2ggDQogICAgICAgbGVhZHMgdG8gdGhlIGZyZXF1ZW50IGRpc3J1cHRpb24gYW5kIGxvdyBlZmZp
Y2llbmN5IG9mIHRoZSBtdWx0aWNhc3QgDQogICAgICAgc2VydmljZTsgDQoNCg0KICAgICANCiAg
ICAgDQogICAgWmhhbmcgZXQgYWwuICAgICAgICAgICAgICBFeHBpcmVzIE1heSwyMDExICAgICAg
ICAgICAgICAgICAgICBbUGFnZSAzXSANCiAgICAgICAgDQoMICAgIEludGVybmV0LURyYWZ0ICAg
ICAgTVNNIFN1cHBvcnQgaW4gUE1JUHY2IE5ldHdvcmsgICAgICAgIE5vdmVtYmVyIDIwMTAgDQog
ICAgIA0KDQogICAgICAgLS0tQSBtb2JpbGUgbXVsdGljYXN0IHNvdXJjZSBtdXN0IHByb3ZpZGUg
YWRkcmVzcyB0cmFuc3BhcmVuY3kgYXQgdHdvIA0KICAgICAgIGxheWVyczogVG8gY29tcGx5IHdp
dGggUmV2ZXJzZSBQYXRoIEZvcndhcmQgKFJQRikgY2hlY2tzLCBpdCBoYXMgdG8gDQogICAgICAg
dXNlIGFuIGFkZHJlc3Mgd2l0aGluIHRoZSBzb3VyY2UgZmllbGQgb2YgdGhlIElQdjYgYmFzaWMg
aGVhZGVyLCANCiAgICAgICB3aGljaCBpcyBpbiB0b3BvbG9naWNhbCBhZ3JlZW1lbnQgd2l0aCB0
aGUgZW1wbG95ZWQgbXVsdGljYXN0IA0KICAgICAgIGRpc3RyaWJ1dGlvbiB0cmVlLiBGb3IgYXBw
bGljYXRpb24gdHJhbnNwYXJlbmN5LCB0aGUgbG9naWNhbCBub2RlIA0KICAgICAgIGlkZW50aWZp
ZXIgbXVzdCBiZSBwcmVzZW50ZWQgYXMgdGhlIHBhY2tldCBzb3VyY2UgYWRkcmVzcyB0byB0aGUg
DQogICAgICAgdHJhbnNwb3J0IGxheWVyIGF0IHRoZSByZWNlaXZlciBzaWRlLiBJdCBpcyBhIHRv
dWdoIHByb2JsZW0gZm9yIHRoZSAgDQogICAgICAgU1BULWJhc2VkIHNjaGVtZSBiZWNhdXNlIHRo
ZSBpZGVudGlmaWVyIGFuZCB0aGUgbG9jYXRvciBvZiB0aGUgTU4gYXJlIA0KICAgICAgIHNlcGFy
YXRlZC4gVGhlIE1OIGNhbiBvbmx5IGNvbmZpZ3VyZSB0aGUgSG9BIChIb21lIEFkZHJlc3MpIGFz
IGl0cyANCiAgICAgICBpZGVudGlmaWVyIGFuZCBpdHMgbG9jYXRvciBpcyB0aGUgYWRkcmVzcyBv
ZiB0aGUgTUFHLiBIb3dldmVyLCB0aGUgDQogICAgICAgUlBULWJhc2VkIHNjaGVtZSBjYW4gZWFz
aWx5IHNvbHZlIHRoaXMgcHJvYmxlbSBiZWNhdXNlIHRoZSBIb0EgaXMgDQogICAgICAganVzdCBh
bmNob3JlZCBhdCB0aGUgTE1BLiANCg0KICAgICAgIFRodXMsIHdlIHN1Z2dlc3QgdXNpbmcgdGhl
IFJQVC1iYXNlZCBzY2hlbWUgdG8gcHJvdmlkZSB0aGUgbXVsdGljYXN0IA0KICAgICAgIHNvdXJj
ZSBtb2JpbGl0eSBpbiB0aGUgUE1JUHY2IG5ldHdvcmsuIEFjY29yZGluZyB0byB0aGUgYmFzaWMg
UE1JUHY2IA0KICAgICAgIHNwZWNpZmljYXRpb24sIGFsbCB0aGUgcGFja2V0cyB0byBhbmQgZnJv
bSB0aGUgTU4gbXVzdCBiZSB0cmFuc21pdHRlZCANCiAgICAgICB0byB0aGUgTE1BIHRocm91Z2gg
dGhlIExNQS1NQUcgdHVubmVsIGZpcnN0bHksIHRoYXQgbWVhbnMgdGhlIExNQSBpcyANCiAgICAg
ICBhIGZpeGVkIHBvaW50IG9uIHRoZSB3YXkgdG8gYW5kIGZyb20gdGhlIE1OLiBTbyB3ZSBjYW4g
c2V0IHRoZSBMTUEgdG8gDQogICAgICAgYmUgdGhlIFJQIGFuZCB0aGUgcHJveHkgc291cmNlIG9m
IHRoZSBtdWx0aWNhc3QuIFRoZSBtdWx0aWNhc3QgDQogICAgICAgcGFja2V0cyBzZW50IGJ5IHRo
ZSBNTiBhcmUgZmlyc3RseSBzZW50IHRvIHRoZSBMTUEgYXMgdHJhZGl0aW9uYWwgDQogICAgICAg
UE1JUHY2IHNwZWNpZmllZCBhbmQgdGhlbiB0aGUgcGFja2V0cyBhcmUgdHJhbnNtaXR0ZWQgZnJv
bSB0aGUgTE1BIHRvIA0KICAgICAgIHRoZSByZWNlaXZlcnMgYWNjb3JkaW5nIHRvIHRoZSBtdWx0
aWNhc3Qgcm91dGluZyBwcm90b2NvbHMuICANCg0KICAgIDMuIEV4dGVuc2lvbnMgb2YgUE1JUHY2
IA0KDQogICAgICAgSW4gb3JkZXIgdG8gc3VwcG9ydCB0aGUgbW9iaWxpdHkgb2YgdGhlIG11bHRp
Y2FzdCBzb3VyY2UsIHRoZSBMTUEgaXMgDQogICAgICAgc2VsZWN0ZWQgdG8gYmUgdGhlIFJQIG9m
IHRoZSBtb2JpbGUgbXVsdGljYXN0IHNlcnZpY2UuIEJlc2lkZXMsIHRoZSANCiAgICAgICBqb2lu
IG1lc3NhZ2UgaXMgcHJvY2Vzc2VkIGJ5IHRoZSBMTUEuIFRoZW4gdGhlIHNpZ25hbGluZyBtZXNz
YWdlcyBhbmQgDQogICAgICAgdGhlIHJlbGF0ZWQgcHJvY2Vzc2luZyBvZiBiYXNpYyBQTUlQdjYg
c2hvdWxkIGJlIGV4dGVuZGVkLiAgDQoNCiAgICAzLjEuIE1OIA0KDQogICAgICAgSW4gb3JkZXIg
dG8gcHJvdmlkZSB0aGUgbXVsdGljYXN0IHNlcnZpY2UgZHVyaW5nIHRoZSBNTidzIG1vdmVtZW50
LCANCiAgICAgICB0aGUgTUFHIG11c3QgcmVjb2duaXplIHRoYXQgdGhlIGF0dGFjaGVkIE1OIGlz
IGEgbXVsdGljYXN0IHNvdXJjZS4gIA0KICAgICAgIFRoaXMgaW5mb3JtYXRpb24gY2FuIGJlIGxl
YXJuZWQgYnkgdGhlIE1BRyBkdXJpbmcgdGhlIGF1dGhlbnRpY2F0aW9uIA0KICAgICAgIHBoYXNl
IGZvciBleGFtcGxlIGFuZCB0aGUgY29ycmVzcG9uZGluZyBtdWx0aWNhc3QgYWRkcmVzcyBtdXN0
IGJlIA0KICAgICAgIGNvbnRhaW5lZCBpbiB0aGlzIGluZm9ybWF0aW9uIGF0IGxlYXN0LiBUaGUg
cGFydGljdWxhciBwcm9jZWR1cmUgaXMgDQogICAgICAgb3V0IG9mIHRoaXMgZG9jdW1lbnQuIA0K
DQogICAgMy4yLiBNQUcgDQoNCiAgICAgICBXaGVuIHRoZSBNQUcgZmluZHMgdGhhdCB0aGUgYXR0
YWNoZWQgTU4gaXMgYSBtdWx0aWNhc3Qgc291cmNlLCBpdCANCiAgICAgICBzaG91bGQgc2VuZCB0
aGUgZXh0ZW5kZWQgUHJveHkgQmluZGluZyBVcGRhdGUgKFBCVSkgbWVzc2FnZSB0byB0aGUgDQog
ICAgICAgTE1BLiBJbiB0aGUgZXh0ZW5kZWQgUEJVIG1lc3NhZ2UsIGEgb25lIGJpdCAiUyIgZmxh
ZyBpcyBhZGRlZCBhbmQgc2V0IA0KICAgICAgIHRvICIxIi4gVGhlIG11bHRpY2FzdCBhZGRyZXNz
IGlzIGNvbnRhaW5lZCBpbiB0aGUgTXVsdGljYXN0IGFkZHJlc3MgDQogICAgICAgb3B0aW9uIG9m
IHRoZSBQQlUgbWVzc2FnZSB3aGVuIHRoZSAiUyIgaXMgc2V0IHRvICIxIi4gVGhlbiB0aGUgTUFH
IA0KDQogICAgIA0KICAgICANCiAgICBaaGFuZyBldCBhbC4gICAgICAgICAgICAgIEV4cGlyZXMg
TWF5LDIwMTEgICAgICAgICAgICAgICAgICAgIFtQYWdlIDRdIA0KICAgICAgICANCgwgICAgSW50
ZXJuZXQtRHJhZnQgICAgICBNU00gU3VwcG9ydCBpbiBQTUlQdjYgTmV0d29yayAgICAgICAgTm92
ZW1iZXIgMjAxMCANCiAgICAgDQoNCiAgICAgICBlbmNhcHN1bGF0ZXMgdGhlIG11bHRpY2FzdCBw
YWNrZXRzIGludG8gdGhlIGJpLWRpcmVjdGlvbmFsIHR1bm5lbCBhbmQgDQogICAgICAgc2VuZHMg
dGhlbSB0byB0aGUgTE1BIGZpcnN0bHkuICANCg0KICAgIDMuMy4gTE1BIA0KDQogICAgICAgV2hl
biByZWNlaXZpbmcgdGhlIGV4dGVuZGVkIFBCVSBtZXNzYWdlLCB0aGUgbm9ybWFsIFBNSVB2NiB0
dW5uZWwgaXMgDQogICAgICAgZXN0YWJsaXNoZWQgYmV0d2VlbiBMTUEgYW5kIE1BRy4gQmVzaWRl
cywgdGhlIExNQSByZWNvZ25pemVzIHRoYXQgaXQgDQogICAgICAgc2hvdWxkIGFjdCBhcyB0aGUg
UlAgZm9yIHRoZSBtdWx0aWNhc3Qgc2Vzc2lvbiBzcGVjaWZpZWQgYnkgdGhlIA0KICAgICAgIE11
bHRpY2FzdCBhZGRyZXNzIG9wdGlvbi4gIA0KDQogICAgICAgVGhlIExNQSBhbHNvIGludGVyY2Vw
dHMgdGhlIGpvaW4gbWVzc2FnZSBhbmQgcHJvY2VlZHMgaXQgZm9yIHRoZSBNTi4gDQogICAgICAg
VGhlbiB0aGUgU1BUIGJldHdlZW4gTE1BIGFuZCB0aGUgbmV3IHJlY2VpdmVyIGNhbiBiZSBlc3Rh
Ymxpc2hlZC4gSW4gDQogICAgICAgdGhpcyB3YXksIHRoZSBtdWx0aWNhc3Qgc2VydmljZSBjYW4g
YWx3YXlzIGJlIHByb3ZpZGVkIHRocm91Z2ggdGhlIA0KICAgICAgIFJQVCBhbmQgdGhlIHN0YWJp
bGl0eSBvZiB0aGUgbXVsdGljYXN0IHRyZWUgaXMgZ3VhcmFudGVlZC4gDQoNCiAgICA0LiBNdWx0
aWNhc3Qgc291cmNlIG1vYmlsaXR5IHByb2NlZHVyZSANCg0KICAgICAgIEZpZ3VyZSAxIHNob3dz
IHRoZSBwcm90b2NvbCBwcm9jZWR1cmUuIA0KDQogICAgICAgICAgICstLS0tLSsgICAgICAgICAg
ICAgICstLS0tLSsgICAgICAgICAgICArLS0tLS0rICAgICAgICAgICAgKy0tLS0tKyANCiAgICAg
ICAgICAgfCBNTiAgfCAgICAgICAgICAgICAgfCBNQUcxfCAgICAgICAgICAgIHwgTE1BIHwgICAg
ICAgICAgICB8IE1BRzJ8IA0KICAgICAgICAgICArLS0tLS0rICAgICAgICAgICAgICArLS0tLS0r
ICAgICAgICAgICAgKy0tLS0tKyAgICAgICAgICAgICstLS0tLSsgDQogICAgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgICAgfCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8
IA0KICAgICAgICAgIDEpICAgfC0tLSBSdHIgU29sLS0tLS0tPnwgICAgICAgICAgICAgICAgICB8
ICAgICAgICAgICAgICAgICAgfCAgDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fC0tLS0tLS0gUEJVIC0tLS0tPnwgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAgIDIpICAg
fCAgICAgICAgICAgICAgIChNdWx0aWNhc3QgYWRkcmVzcyBvcHRpb24pICAgICAgICAgICAgICAg
fCANCiAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgIEFjY2VwdCBQQlUgICAgICAgICAgICB8IA0KICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgIChBbGxvY2F0ZSBITlAxLCBhY3QgYXMgUlAgZm9yIE1OKSAg
fCANCiAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8PC0tLS0tLSBQQkEgLS0tLS0t
fCAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgICAgICAgICB8PC0tLS0gUnRyIEFkdiAtLS0t
fCAgICAgICAoSE5QMSkgICAgIHwgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCANCiAgICAgICAgICAzKSAgIHw9PW11bHRpY2FzdCBkYXRhPT58PW11bHRpY2FzdCBkYXRhPT0+
fCAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgKHByb2Nlc3MgdGhlIGpvaW4gYW5kIGVzdGFibGlzaCBTUFQp
fCANCiAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgICAgNCkgICB8LS0tLS0tLS0tLS0tLS0tLS0t
LS0tLSBSdHIgU29sLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLT58IA0KICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8PC0tLS0tIFBCVSAtLS0tLS0t
fCANCiAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAoTXVsdGlj
YXN0IGFkZHJlc3Mgb3B0aW9uKXwgDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAgIDUpICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICBBY2NlcHQgUEJVICAgICAgICAgICAg
fCANCiAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8ICAoQWxsb2NhdGUgSE5QMSwg
cmVmcmVzaCB0dW5uZWwpICAgIHwgDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8LS0tLS0tLSBQQkEgLS0tLS0+
fCANCg0KICAgICANCiAgICAgDQogICAgWmhhbmcgZXQgYWwuICAgICAgICAgICAgICBFeHBpcmVz
IE1heSwyMDExICAgICAgICAgICAgICAgICAgICBbUGFnZSA1XSANCiAgICAgICAgDQoMICAgIElu
dGVybmV0LURyYWZ0ICAgICAgTVNNIFN1cHBvcnQgaW4gUE1JUHY2IE5ldHdvcmsgICAgICAgIE5v
dmVtYmVyIDIwMTAgDQogICAgIA0KDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgICAgICAgKEhOUDEpICAgICB8IA0KICAgICAgICAgICAgICAg
fDwtLS0tLS0tLS0tLS0tLS0tLS0tLSBSdHIgQWR2IC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0g
fCANCiAgICAgICAgICA2KSAgIHw9PT09PT09PT09PT09PT09PT18PT09bXVsdGljYXN0IGRhdGE9
fD09PT09PT09PT09PT09PT09PnwgDQogICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHw8PW11bHRpY2FzdCBkYXRhPT18IA0KICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgIChjb250aW51ZSB0aGUgcGFja2V0IHRyYW5zbWlzc2lvbikg
fCANCiAgICAgICAgICAgICAgIHwgICAgICAgICAgICAgICAgICB8ICAgICAgICAgICAgICAgICAg
fCAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgIA0KICAgICAgICAgICAgICAgICAgIEZpZ3Vy
ZSAxOiBNdWx0aWNhc3QgU291cmNlIE1vYmlsaXR5IFByb2NlZHVyZSANCiAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgIA0KICAgICAgIFRoZSBkZXRhaWxlZCBkZXNjcmlw
dGlvbnMgYXJlIGFzIGZvbGxvd3M6IA0KDQogICAgICAgMSkgVGhlIE1OIGNvbm5lY3RzIHRvIHRo
ZSBNQUcxIGluaXRpYWxseSBhbmQgc2VuZHMgUm91dGVyIA0KICAgICAgICAgIFNvbGljaXRhdGlv
biAoUlMpIG1lc3NhZ2UgdG8gdGhlIE1BRzE7IA0KDQogICAgICAgMikgV2hlbiB0aGUgYXR0YWNo
bWVudCBvZiBNTiBpcyBkZXRlY3RlZCBieSB0aGUgTUFHMSwgYW4gZXh0ZW5kZWQgDQogICAgICAg
ICAgUEJVIG1lc3NhZ2UgaXMgc2VudCB0byB0aGUgTE1BLiBCZWNhdXNlIHRoZSBMTUEgZmluZHMg
dGhlIFMgZmxhZyANCiAgICAgICAgICBhbmQgdGhlIE11bHRpY2FzdCBhZGRyZXNzIG9wdGlvbiBj
b250YWluZWQgaW4gdGhlIFBCVSBtZXNzYWdlLCANCiAgICAgICAgICB0aGUgTE1BIGFjdHMgYXMg
dGhlIFJQIG9mIHRoZSBtdWx0aWNhc3Qgc2VydmljZSBjb3JyZXNwb25kaW5nIHRvIA0KICAgICAg
ICAgIHRoZSBNdWx0aWNhc3QgYWRkcmVzcyBhbmQgcmVzcG9uc2VzIHRvIHRoZSBqb2luIG1lc3Nh
Z2Ugc2VudCB0byANCiAgICAgICAgICB0aGUgTU4uIEFuZCB0aGVuIHRoZSBMTUEgc2VuZHMgYmFj
ayBhIFBCQSBtZXNzYWdlIHRvIHRoZSBNQUcxLiANCiAgICAgICAgICBBZnRlcndhcmRzLCB0aGUg
YmktZGlyZWN0aW9uYWwgdHVubmVsIGlzIGVzdGFibGlzaGVkIGJldHdlZW4gdGhlIA0KICAgICAg
ICAgIE1BRzEgYW5kIHRoZSBMTUE7IA0KDQogICAgICAgMykgVGhlIG11bHRpY2FzdCBwYWNrZXRz
IGFyZSBzZW50IGZyb20gdGhlIE1OIHRvIHRoZSBMTUEgYXMgdGhlIA0KICAgICAgICAgIGJhc2lj
IFBNSVB2NiBzcGVjaWZpZWQuIFNpbmNlIHRoZSBTUFQgd2lsbCBiZSBlc3RhYmxpc2hlZCBiZXR3
ZWVuIA0KICAgICAgICAgIHRoZSBMTUEgYW5kIHRoZSByZWNlaXZlciwgdGhlIHBhY2tldHMgYXJl
IHRyYW5zbWl0dGVkIGJldHdlZW4gdGhlIA0KICAgICAgICAgIExNQSBhbmQgdGhlIHJlY2VpdmVy
IGFjY29yZGluZyB0byB0aGUgbXVsdGljYXN0IHJvdXRpbmcgcHJvdG9jb2w7IA0KDQogICAgICAg
NCkgV2hlbiB0aGUgTU4gbW92ZXMgdG8gdGhlIE1BRzIsIHRoZSBtdWx0aWNhc3QgcmVsYXRlZCBp
bmZvcm1hdGlvbiANCiAgICAgICAgICBpcyBhbHNvIGxlYXJuZWQgYnkgdGhlIE1BRzI7IA0KDQog
ICAgICAgNSkgVGhlbiB0aGUgTE1BLU1BRyBiaS1kaXJlY3Rpb25hbCBpcyByZWZyZXNoZWQsIGhv
d2V2ZXIsIHRoZSBTUFQgDQogICAgICAgICAgYmV0d2VlbiB0aGUgTE1BIGFuZCB0aGUgcmVjZWl2
ZXIgaXMga2VwdCB1bmNoYW5nZWQ7IA0KDQogICAgICAgNikgVGhlIG11bHRpY2FzdCBwYWNrZXRz
IHRyYW5zbWlzc2lvbiBjb250aW51ZXMgYWZ0ZXIgdGhlIGhhbmRvdmVyIA0KICAgICAgICAgIGFu
ZCB0aGUgbW9iaWxpdHkgb2YgdGhlIHNvdXJjZSBpcyB0cmFuc3BhcmVudCB0byB0aGUgcmVjZWl2
ZXIuIA0KDQogICAgNS4gRm9ybWF0IG9mIHNpZ25hbGluZyBtZXNzYWdlcyANCg0KICAgIDUuMS4g
UEJVIA0KDQogICAgICAgVGhlIGZvcm1hdCBvZiB0aGUgUEJVIG1lc3NhZ2UgaXMgc2hvd24gaW4g
RmlndXJlIDIuIA0KDQogICAgICAgICAwICAgICAgICAgICAgICAgICAgIDEgICAgICAgICAgICAg
ICAgICAgMiAgICAgICAgICAgICAgICAgICAzIA0KICAgICAgICAgMCAxIDIgMyA0IDUgNiA3IDgg
OSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIA0KDQogICAgIA0K
ICAgICANCiAgICBaaGFuZyBldCBhbC4gICAgICAgICAgICAgIEV4cGlyZXMgTWF5LDIwMTEgICAg
ICAgICAgICAgICAgICAgIFtQYWdlIDZdIA0KICAgICAgICANCgwgICAgSW50ZXJuZXQtRHJhZnQg
ICAgICBNU00gU3VwcG9ydCBpbiBQTUlQdjYgTmV0d29yayAgICAgICAgTm92ZW1iZXIgMjAxMCAN
CiAgICAgDQoNCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICB8ICAgICAgICAgICAgU2VxdWVuY2UgIyAgICAgICAgIHwgDQogICAgICAg
ICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKyANCiAgICAgICAgIHxBfEh8THxLfE18UnxQfFN8ICBSZXNlcnZlZCAgICAgfCAg
ICAgICAgICAgIExpZmV0aW1lICAgICAgICAgICB8IA0KICAgICAgICAgKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSsgDQogICAg
ICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgfCANCiAgICAgICAgIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAuIA0KICAgICAgICAgLiAgICAgICAgICAg
ICAgICAgICAgICBNdWx0aWNhc3QgYWRkcmVzcyBvcHRpb24gICAgICAgICAgICAgICAgIC4NCiAg
ICAgICAgIC4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAuIA0KICAgICAgICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgDQogICAgICAgICArLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKyAN
CiAgICAgICAgICANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIEZpZ3VyZSAyOiBQQlUg
TWVzc2FnZSBGb3JtYXQgIA0KDQogICAgICAgUyBmbGFnIGFuZCBNdWx0aWNhc3QgYWRkcmVzcyBv
cHRpb24gICANCg0KICAgICAgICAgIDEtYml0ICJNdWx0aWNhc3Qgc291cmNlIGlkZW50aWZpY2F0
aW9uIiBmbGFnIGlzIHVzZWQgdG8gaWRlbnRpZnkgDQogICAgICAgICAgd2hldGhlciB0aGlzIE1O
IGlzIGEgbXVsdGljYXN0IHNvdXJjZS4gV2hlbiB0aGlzIGZsYWcgaXMgc2V0IHRvICIxIiwgDQog
ICAgICAgICAgdGhlIHJlbGF0ZWQgbXVsdGljYXN0IGFkZHJlc3MgaXMgYXR0YWNoZWQgaW4gdGhl
IE11bHRpY2FzdCBhZGRyZXNzIA0KICAgICAgICAgIG9wdGlvbi4NCg0KICAgIDUuMi4gUEJBIA0K
DQogICAgICAgVGhlIGZvcm1hdCBvZiB0aGUgUEJBIG1lc3NhZ2UgaXMgc2hvd24gaW4gRmlndXJl
IDMuIA0KDQogICAgICAgICAwICAgICAgICAgICAgICAgICAgIDEgICAgICAgICAgICAgICAgICAg
MiAgICAgICAgICAgICAgICAgICAzIA0KICAgICAgICAgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEg
MiAzIDQgNSA2IDcgOCA5IDAgMSAyIDMgNCA1IDYgNyA4IDkgMCAxIA0KICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0r
LSsgDQogICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgIHwgICBTdGF0dXMg
ICAgICB8S3xSfFB8U3wgIFJlcy4gfCANCiAgICAgICAgICstKy0rLSstKy0rLSstKy0rLSstKy0r
LSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rIA0KICAgICAgICAgfCAg
ICAgICAgIFNlcXVlbmNlICMgICAgICAgICAgICB8ICAgICAgICAgICBMaWZldGltZSAgICAgICAg
ICAgIHwgDQogICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgICAgICAgIHwgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICB8IA0KICAgICAgICAg
LiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgIC4gDQogICAgICAgICAuICAgICAgICAgICAgICAgICAgICAgICAgTXVsdGljYXN0IGFk
ZHJlc3Mgb3B0aW9uICAgICAgICAgICAgICAgLiANCiAgICAgICAgIC4gICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAuIA0KICAgICAg
ICAgfCAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgIHwgDQogICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgICAgICAgICANCiAgICAgICAgICAg
ICAgICAgICAgICAgICAgICBGaWd1cmUgMzogUEJBIE1lc3NhZ2UgRm9ybWF0IA0KDQogICAgICAg
UyBmbGFnIGFuZCBNdWx0aWNhc3QgYWRkcmVzcyBvcHRpb24gICANCg0KDQogICAgIA0KICAgICAN
CiAgICBaaGFuZyBldCBhbC4gICAgICAgICAgICAgIEV4cGlyZXMgTWF5LDIwMTEgICAgICAgICAg
ICAgICAgICAgIFtQYWdlIDddIA0KICAgICAgICANCgwgICAgSW50ZXJuZXQtRHJhZnQgICAgICBN
U00gU3VwcG9ydCBpbiBQTUlQdjYgTmV0d29yayAgICAgICAgTm92ZW1iZXIgMjAxMCANCiAgICAg
DQoNCiAgICAgICAgICBUaGUgUyBmbGFnIGlzIHNldCB0byAiMSIgaWYgdGhlIExNQSBjYW4gYWN0
IGFzIHRoZSBSUCBmb3IgdGhlICAgIA0KICAgICAgICAgIG11bHRpY2FzdCBzZXJ2aWNlIGlkZW50
aWZpZWQgYnkgdGhlIE11bHRpY2FzdCBhZGRyZXNzIG9wdGlvbi4gVGhlIExNQSANCiAgICAgICAg
ICB3aWxsIG5vdCBhY3QgYXMgdGhlIFJQIGZvciB0aGUgbXVsdGljYXN0IHNlcnZpY2UgaWYgdGhl
IFMgZmxhZyBpcyBzZXQgDQogICAgICAgICAgdG8gIjAiIG9yIHRoZXJlIGlzIG5vIFMgZmxhZyBp
biB0aGUgUEJBIG1lc3NhZ2UuIEhvdyB0byBwcm92aWRlIHRoZSANCiAgICAgICAgICBtdWx0aWNh
c3Qgc291cmNlIG1vYmlsaXR5IHNlcnZpY2UgaW4gdGhlIHNjZW5hcmlvIHdpdGggdGhlIExNQSBu
b3QgDQogICAgICAgICAgYWN0aW5nIGFzIHRoZSBSUCB3aWxsIGJlIGRpc2N1c3NlZCBpbiB0aGUg
ZnV0dXJlLiANCg0KICAgIDUuMy4gTXVsdGljYXN0IGFkZHJlc3Mgb3B0aW9uIA0KDQogICAgICAg
VGhlIGZvcm1hdCBvZiBNdWx0aWNhc3QgYWRkcmVzcyBvcHRpb24gaXMgaWxsdXN0cmF0ZWQgaW4g
RmlndXJlIDQuIA0KDQogICAgICAgICAgIDAgICAgICAgICAgICAgICAgICAgMSAgICAgICAgICAg
ICAgICAgICAyICAgICAgICAgICAgICAgICAgIDMgDQogICAgICAgICAgIDAgMSAyIDMgNCA1IDYg
NyA4IDkgMCAxIDIgMyA0IDUgNiA3IDggOSAwIDEgMiAzIDQgNSA2IDcgOCA5IDAgMSANCiAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKyANCiAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
IHwgIE9wdGlvbiBUeXBlICB8IE9wdGlvbiBMZW5ndGggfCANCiAgICAgICAgICArLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKyAN
CiAgICAgICAgICB8ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgfCANCiAgICAgICAgICArICAgICAgICAgICAgICAgICAgICAgICAg
ICAgTXVsdGljYXN0IGFkZHJlc3MgICAgICAgICAgICAgICAgICAgKyANCiAgICAgICAgICB8ICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgfCANCiAgICAgICAgICArLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSstKy0rLSst
Ky0rLSstKy0rLSstKy0rLSstKy0rLSstKyANCiAgICAgDQogICAgICAgICAgICAgICAgICAgIEZp
Z3VyZSA0OiBGb3JtYXQgb2YgTXVsdGljYXN0IEFkZHJlc3MgT3B0aW9uIA0KDQogICAgICAgT3B0
aW9uIFR5cGUgDQoNCiAgICAgICAgICBUQkQgDQoNCiAgICAgICBPcHRpb24gTGVuZ3RoIA0KDQog
ICAgICAgICAgOC1iaXQgdW5zaWduZWQgaW50ZWdlciBpbmRpY2F0aW5nIHRoZSBsZW5ndGggb2Yg
dGhlIG9wdGlvbiBpbiBvY3RldHMsIA0KICAgICAgICAgIGV4Y2x1ZGluZyB0aGUgb3B0aW9uIHR5
cGUgYW5kIG9wdGlvbiBsZW5ndGggZmllbGRzLiBUaGlzIGZpZWxkIGNhbiBiZSANCiAgICAgICAg
ICBzZXQgdG8gMTYgYW5kIDQgZm9yIHRoZSBJUHY2IGFuZCBJUHY0IG11bHRpY2FzdCBhZGRyZXNz
ZXMsIHJlc3BlY3RpdmVseS4gDQoNCiAgICAgICBNdWx0aWNhc3QgYWRkcmVzcyANCg0KICAgICAg
ICAgIFRoZSBtdWx0aWNhc3QgYWRkcmVzcyByZWxhdGVkIHRvIHRoZSBtdWx0aWNhc3Qgc2Vzc2lv
biBwcm92aWRlZCBieSB0aGUgDQogICAgICAgICAgTU4uIA0KDQogICAgNi4gU2VjdXJpdHkgQ29u
c2lkZXJhdGlvbnMgDQoNCiAgICAgICBUaGlzIGRvY3VtZW50IGRvZXMgbm90IGludHJvZHVjZSBh
bnkgc2VjdXJpdHkgY29uc2lkZXJhdGlvbnMuIA0KDQogICAgNy4gUmVmZXJlbmNlcyANCg0KICAg
ICAgIFsxXSAgR3VuZGF2ZWxsaSwgZXQgYWwuLiAiUHJveHkgTW9iaWxlIElwdjYiLCBSRkM1MjEz
LCBBdWd1c3QgMjAwOC4gIA0KDQogICAgIA0KICAgICANCiAgICBaaGFuZyBldCBhbC4gICAgICAg
ICAgICAgIEV4cGlyZXMgTWF5LDIwMTEgICAgICAgICAgICAgICAgICAgIFtQYWdlIDhdIA0KICAg
ICAgICANCgwgICAgSW50ZXJuZXQtRHJhZnQgICAgICBNU00gU3VwcG9ydCBpbiBQTUlQdjYgTmV0
d29yayAgICAgICAgTm92ZW1iZXIgMjAxMCANCiAgICAgDQoNCiAgICAgICBbMl0gIERhdmlkIEIu
IEpvaG5zb24sIENoYXJsZXMgRS4gUGVya2lucyBhbmQgSmFyaSBBcmtrby4gIk1vYmlsaXR5IA0K
ICAgICAgICAgICAgU3VwcG9ydCBpbiBJUHY2IiwgUkZDIDM3NzUsIEp1bmUgMjAwNC4gDQoNCiAg
ICAgICBbM10gIFQgQy4gU2NobWlkdCwgTS4gV2FlaGxpc2NoIGFuZCBTLiBLcmlzaG5hbi4gIkJh
c2UgRGVwbG95bWVudCANCiAgICAgICAgICAgIGZvciBNdWx0aWNhc3QgTGlzdGVuZXIgU3VwcG9y
dCBpbiBQTUlQdjYgRG9tYWlucyIsIGRyYWZ0LWlldGYtDQogICAgICAgICAgICBtdWx0aW1vYi1w
bWlwdjYtYmFzZS1zb2x1dGlvbi0wMCwgRmVicnVhcnkgMjQsIDIwMTAuIA0KDQogICAgICAgWzRd
ICBILiBBc2FlZGEsIFAuIFNlaXRlIGFuZCBKLiBYaWEuICJQTUlQdjYgRXh0ZW5zaW9ucyBmb3Ig
DQogICAgICAgICAgICBNdWx0aWNhc3QiLCBkcmFmdC1hc2FlZGEtbXVsdGltb2ItcG1pcDYtZXh0
ZW5zaW9uLTAzLCBNYXJjaCA4LCANCiAgICAgICAgICAgIDIwMTAuIA0KDQogICAgICAgWzVdICBT
ZWlsIEplb24gYW5kIFlvdW5naGFuIEtpbS4gIk1vYmlsZSBNdWx0aWNhc3RpbmcgU3VwcG9ydCBp
biANCiAgICAgICAgICAgIFByb3h5IE1vYmlsZSBJUHY2IiwgZHJhZnQtc2lqZW9uLW11bHRpbW9i
LW1tcy1wbWlwNi0wMiwgTWFyY2ggNCwgDQogICAgICAgICAgICAyMDEwLiANCg0KICAgICAgIFs2
XSAgVCBDLiBTY2htaWR0LCBNLiBXYWVobGlzY2gsIFIuIEtvb2RsaSBhbmQgRy4gRmFpcmh1cnN0
LiANCiAgICAgICAgICAgICJNdWx0aWNhc3QgTGlzdGVuZXIgRXh0ZW5zaW9ucyBmb3IgTUlQdjYg
YW5kIFBNSVB2NiBGYXN0IA0KICAgICAgICAgICAgSGFuZG92ZXJzIiwgZHJhZnQtc2NobWlkdC1t
dWx0aW1vYi1mbWlwdjYtcGZtaXB2Ni1tdWx0aWNhc3QtMDEsIA0KICAgICAgICAgICAgTWFyY2gg
MDYsIDIwMTAuIA0KDQogICAgICAgWzddICBLLiBTYXRvLCBNLiBLYXRzdW1vdG8sIFQuIE1pa2ku
ICJGdXR1cmUgdmlzaW9uIGRpc3RyaWJ1dGlvbiANCiAgICAgICAgICAgIHN5c3RlbSBhbmQgbmV0
d29yayIsIFRoaXMgcGFwZXIgYXBwZWFycyBpbjogSUVFRSBJbnRlcm5hdGlvbmFsIA0KICAgICAg
ICAgICAgU3ltcG9zaXVtIG9uIENvbW11bmljYXRpb25zIGFuZCBJbmZvcm1hdGlvbiBUZWNobm9s
b2d5LCAyMDA0LiANCiAgICAgICAgICAgIElTQ0lUIDIwMDQsIHZvbC4xLCBwcDogMjc0IC0gMjc5
LCBPY3RvYmVyIDIwMDQuIA0KDQogICAgICAgWzhdICBULiBTY2htaWR0LCBNLiBXYWVobGlzY2gg
YW5kIEcuIEZhaXJodXJzdC4gIk11bHRpY2FzdCBNb2JpbGl0eSANCiAgICAgICAgICAgIGluIE1v
YmlsZSBJUCBWZXJzaW9uIDYgKE1JUHY2KTogUHJvYmxlbSBTdGF0ZW1lbnQgYW5kIEJyaWVmIA0K
ICAgICAgICAgICAgU3VydmV5IiwgUkZDIDU3NTcsIEZlYnJ1YXJ5IDIwMTAuDQoNCg0KDQoNCg0K
DQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQogICAgIA0KICAgICANCiAgICBaaGFuZyBldCBhbC4g
ICAgICAgICAgICAgIEV4cGlyZXMgTWF5LDIwMTEgICAgICAgICAgICAgICAgICAgIFtQYWdlIDld
IA0KICAgICAgICANCgwgICAgSW50ZXJuZXQtRHJhZnQgICAgICBNU00gU3VwcG9ydCBpbiBQTUlQ
djYgTmV0d29yayAgICAgICAgTm92ZW1iZXIgMjAxMCANCiAgICAgDQoNCiAgICBBdXRob3JzJyBB
ZGRyZXNzZXMgDQoNCiAgICAgICBIb25nLUtlIFpoYW5nLCBaaGktV2VpIFlhbiwgU2h1YWktR2Fv
LCBMaS1MaSBXYW5nIA0KICAgICAgIE5hdGlvbmFsIEVuZ2luZWVyaW5nIExhYiBmb3IgTkdJIElu
dGVyY29ubmVjdGlvbiBEZXZpY2VzICANCiAgICAgICBCZWlqaW5nIEppYW90b25nIFVuaXZlcnNp
dHksIENoaW5hIA0KICAgICAgICAgIA0KICAgICAgIFBob25lOiArODYxMDUxNjg1Njc3IA0KICAg
ICAgIEVtYWlsOmhremhhbmdAYmp0dS5lZHUuY24gIA0KICAgICAgICAgICAgIDA2MTIwMjMyQGJq
dHUuZWR1LmNuIA0KICAgICAgICAgICAgIDA5MTExMDQ0QGJqdHUuZWR1LmNuIA0KICAgICAgICAg
ICAgIHNoZ2FvQGJqdHUuZWR1LmNuIA0KICAgICAgICANCiAgICAgICBRaWFuIFd1LCBIZS1XdSBM
aSAgDQogICAgICAgTmV0d29yayBSZXNlYXJjaCBDZW50ZXIgDQogICAgICAgVHNpbmdodWEgVW5p
dmVyc2l0eSwgQ2hpbmEgDQogICAgICAgIA0KICAgICAgIFBob25lOiArODYxMDYyNzcyMzc1IA0K
ICAgICAgIEVtYWlsOnd1cWlhbkBjZXJuZXQuZWR1LmNuIA0KICAgICAgICAgICAgIGxpaGV3dUBj
ZXJuZXQuZWR1LmNuIA0KICAgICANCg0KICAgIEludGVsbGVjdHVhbCBQcm9wZXJ0eSBTdGF0ZW1l
bnQgDQoNCiAgICAgICBUaGUgSUVURiB0YWtlcyBubyBwb3NpdGlvbiByZWdhcmRpbmcgdGhlIHZh
bGlkaXR5IG9yIHNjb3BlIG9mIGFueSANCiAgICAgICBJbnRlbGxlY3R1YWwgUHJvcGVydHkgUmln
aHRzIG9yIG90aGVyIHJpZ2h0cyB0aGF0IG1pZ2h0IGJlIGNsYWltZWQgdG8gDQogICAgICAgcGVy
dGFpbiB0byB0aGUgaW1wbGVtZW50YXRpb24gb3IgdXNlIG9mIHRoZSB0ZWNobm9sb2d5IGRlc2Ny
aWJlZCBpbiANCiAgICAgICB0aGlzIGRvY3VtZW50IG9yIHRoZSBleHRlbnQgdG8gd2hpY2ggYW55
IGxpY2Vuc2UgdW5kZXIgc3VjaCByaWdodHMgDQogICAgICAgbWlnaHQgb3IgbWlnaHQgbm90IGJl
IGF2YWlsYWJsZTsgbm9yIGRvZXMgaXQgcmVwcmVzZW50IHRoYXQgaXQgaGFzIA0KICAgICAgIG1h
ZGUgYW55IGluZGVwZW5kZW50IGVmZm9ydCB0byBpZGVudGlmeSBhbnkgc3VjaCByaWdodHMuICBJ
bmZvcm1hdGlvbiANCiAgICAgICBvbiB0aGUgcHJvY2VkdXJlcyB3aXRoIHJlc3BlY3QgdG8gcmln
aHRzIGluIFJGQyBkb2N1bWVudHMgY2FuIGJlIA0KICAgICAgIGZvdW5kIGluIEJDUCA3OCBhbmQg
QkNQIDc5LiANCg0KICAgICAgIENvcGllcyBvZiBJUFIgZGlzY2xvc3VyZXMgbWFkZSB0byB0aGUg
SUVURiBTZWNyZXRhcmlhdCBhbmQgYW55IA0KICAgICAgIGFzc3VyYW5jZXMgb2YgbGljZW5zZXMg
dG8gYmUgbWFkZSBhdmFpbGFibGUsIG9yIHRoZSByZXN1bHQgb2YgYW4gDQogICAgICAgYXR0ZW1w
dCBtYWRlIHRvIG9idGFpbiBhIGdlbmVyYWwgbGljZW5zZSBvciBwZXJtaXNzaW9uIGZvciB0aGUg
dXNlIG9mIA0KICAgICAgIHN1Y2ggcHJvcHJpZXRhcnkgcmlnaHRzIGJ5IGltcGxlbWVudGVycyBv
ciB1c2VycyBvZiB0aGlzIA0KICAgICAgIHNwZWNpZmljYXRpb24gY2FuIGJlIG9idGFpbmVkIGZy
b20gdGhlIElFVEYgb24tbGluZSBJUFIgcmVwb3NpdG9yeSBhdCANCiAgICAgICBodHRwOi8vd3d3
LmlldGYub3JnL2lwci4gDQoNCiAgICAgICBUaGUgSUVURiBpbnZpdGVzIGFueSBpbnRlcmVzdGVk
IHBhcnR5IHRvIGJyaW5nIHRvIGl0cyBhdHRlbnRpb24gYW55IA0KICAgICAgIGNvcHlyaWdodHMs
IHBhdGVudHMgb3IgcGF0ZW50IGFwcGxpY2F0aW9ucywgb3Igb3RoZXIgcHJvcHJpZXRhcnkgDQog
ICAgICAgcmlnaHRzIHRoYXQgbWF5IGNvdmVyIHRlY2hub2xvZ3kgdGhhdCBtYXkgYmUgcmVxdWly
ZWQgdG8gaW1wbGVtZW50IA0KICAgICAgIHRoaXMgc3RhbmRhcmQuICBQbGVhc2UgYWRkcmVzcyB0
aGUgaW5mb3JtYXRpb24gdG8gdGhlIElFVEYgYXQgDQogICAgICAgaWV0Zi1pcHJAaWV0Zi5vcmcu
IA0KDQoNCg0KICAgICANCiAgICAgDQogICAgWmhhbmcgZXQgYWwuICAgICAgICAgICAgICBFeHBp
cmVzIE1heSwyMDExICAgICAgICAgICAgICAgICAgIFtQYWdlIDEwXSANCiAgICAgICAgDQoMICAg
IEludGVybmV0LURyYWZ0ICAgICAgTVNNIFN1cHBvcnQgaW4gUE1JUHY2IE5ldHdvcmsgICAgICAg
IE5vdmVtYmVyIDIwMTAgDQogICAgIA0KDQogICAgRnVsbCBDb3B5cmlnaHQgU3RhdGVtZW50IA0K
DQogICAgICAgQ29weXJpZ2h0IChDKSBUaGUgSUVURiBUcnVzdCAoMjAxMCkuIA0KDQogICAgICAg
VGhpcyBkb2N1bWVudCBpcyBzdWJqZWN0IHRvIHRoZSByaWdodHMsIGxpY2Vuc2VzIGFuZCByZXN0
cmljdGlvbnMgDQogICAgICAgY29udGFpbmVkIGluIEJDUCA3OCwgYW5kIGV4Y2VwdCBhcyBzZXQg
Zm9ydGggdGhlcmVpbiwgdGhlIGF1dGhvcnMgDQogICAgICAgcmV0YWluIGFsbCB0aGVpciByaWdo
dHMuIA0KDQogICAgICAgVGhpcyBkb2N1bWVudCBhbmQgdGhlIGluZm9ybWF0aW9uIGNvbnRhaW5l
ZCBoZXJlaW4gYXJlIHByb3ZpZGVkIG9uIGFuIA0KICAgICAgICJBUyBJUyIgYmFzaXMgYW5kIFRI
RSBDT05UUklCVVRPUiwgVEhFIE9SR0FOSVpBVElPTiBIRS9TSEUgUkVQUkVTRU5UUyANCiAgICAg
ICBPUiBJUyBTUE9OU09SRUQgQlkgKElGIEFOWSksIFRIRSBJTlRFUk5FVCBTT0NJRVRZLCBUaGUg
SUVURiBUUlVTVCBBTkQgDQogICAgICAgVEhFIElOVEVSTkVUIEVOR0lORUVSSU5HIFRBU0sgRk9S
Q0UgRElTQ0xBSU0gQUxMIFdBUlJBTlRJRVMsIEVYUFJFU1MgDQogICAgICAgT1IgSU1QTElFRCwg
SU5DTFVESU5HIEJVVCBOT1QgTElNSVRFRCBUTyBBTlkgV0FSUkFOVFkgVEhBVCBUSEUgVVNFIE9G
IA0KICAgICAgIFRIRSBJTkZPUk1BVElPTiBIRVJFSU4gV0lMTCBOT1QgSU5GUklOR0UgQU5ZIFJJ
R0hUUyBPUiBBTlkgSU1QTElFRCANCiAgICAgICBXQVJSQU5USUVTIE9GIE1FUkNIQU5UQUJJTElU
WSBPUiBGSVRORVNTIEZPUiBBIFBBUlRJQ1VMQVIgUFVSUE9TRS4gDQoNCiAgICAgICAgDQoNCiAg
ICBBY2tub3dsZWRnbWVudCANCg0KICAgICAgIEZ1bmRpbmcgZm9yIHRoZSBSRkMgRWRpdG9yIGZ1
bmN0aW9uIGlzIGN1cnJlbnRseSBwcm92aWRlZCBieSB0aGUgDQogICAgICAgSW50ZXJuZXQgU29j
aWV0eS4gDQoNCiAgICAgDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0KDQoNCg0K
DQoNCiAgICAgDQogICAgIA0KICAgIFpoYW5nIGV0IGFsLiAgICAgICAgICAgICAgRXhwaXJlcyBN
YXksMjAxMSAgICAgICAgICAgICAgICAgICBbUGFnZSAxMV0gDQogICAgICAgIA0KDA==

--=====001_Dragon600444812554_=====--


From helen.liu@huawei.com  Mon Nov  1 21:00:05 2010
Return-Path: <helen.liu@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 06ED43A67CC for <multimob@core3.amsl.com>; Mon,  1 Nov 2010 21:00:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.218
X-Spam-Level: 
X-Spam-Status: No, score=-0.218 tagged_above=-999 required=5 tests=[AWL=0.277,  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 FIYd2PvdgJKR for <multimob@core3.amsl.com>; Mon,  1 Nov 2010 21:00:04 -0700 (PDT)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id DA41D3A6AB1 for <multimob@ietf.org>; Mon,  1 Nov 2010 21:00:03 -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 <0LB80084AOFWLT@szxga03-in.huawei.com> for multimob@ietf.org; Tue, 02 Nov 2010 11:59:56 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LB800JS6OFW0L@szxga03-in.huawei.com> for multimob@ietf.org; Tue, 02 Nov 2010 11:59:56 +0800 (CST)
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 02 Nov 2010 11:59:51 +0800
Received: from SZXEML504-MBX.china.huawei.com ([169.254.4.68]) by szxeml402-hub.china.huawei.com ([fe80::952d:2bf3:cb35:cafa%21]) with mapi id 14.01.0218.012; Tue, 02 Nov 2010 11:59:55 +0800
Date: Tue, 02 Nov 2010 03:59:56 +0000
From: Liuhui <helen.liu@huawei.com>
In-reply-to: <643B0A1D1A13AB498304E0BBC802784802BB3DBA@S4DE8PSAAQC.mitte.t-com.de>
X-Originating-IP: [10.110.98.139]
To: "Dirk.von-Hugo@telekom.de" <Dirk.von-Hugo@telekom.de>, "multimob@ietf.org" <multimob@ietf.org>
Message-id: <283829E9EFBF22459301B900C9A2E434EBD39C@szxeml504-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [multimob] Revised MLD/IGMP Tuning drafts
Thread-index: Act0lWrtXF5VL1TVTn6Xw0GzS8UjPAB42GhQAPHkZCA=
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: Re: [multimob] Revised MLD/IGMP Tuning drafts
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: Tue, 02 Nov 2010 04:00:05 -0000

Hi Dirk,

Thanks for your detailed review and helpful suggestion :) 
Please see my considerations in-line: 

> -----Original Message-----
> From: multimob-bounces@ietf.org 
> [mailto:multimob-bounces@ietf.org] On Behalf Of 
> Dirk.von-Hugo@telekom.de
> Sent: Thursday, October 28, 2010 6:41 PM
> To: multimob@ietf.org
> Subject: Re: [multimob] Revised MLD/IGMP Tuning drafts
> 
> Dear all,
> Please find below some suggestions to the Multimob MLD tuning drafts:
> 
> In general IMO both revised drafts have considerably 
> improved. Thanks to the autors for their effort!
>  
> Qin and Hui give a detailed introduction in wireless and 
> mobile multicast isues which could be shortened a bit (BTW 
> also fixed access bandwidth e.g. DSL in general is asymmetric 
> - however for wireless it could also be a hybrid connection 
> with e.g. broadcast e.g. DVB downlink and individual unicast 
> e.g. WLAN uplink). 

Accepted. We will shorten the introduction part, and emphasize wireless characteristics on asymmetric link as suggested.

> I am not sure whether we need a comparison in detail between 
> MLD/IGMP versions as only IGMPv3/MLDv2 is mentioned in the charter.

Yes, this section should be shortened to more general summarization.

> 
> Both drafts propose to use Explicit Tracking which can 
> considerably reduce message traffic and speed up leave 
> latency thus saving resources on both network and terminal 
> side. I don't understand why channel changing at receiver 
> side will speed up (3rd para on p.13, Wu et al.)- when a host 
> has sent the Leave it stops listening to the old channel and 
> can send Join to new group and start listening to them ...

Generally, explicit tracking is thought of beneficial for fast leave.  Because the router has exact knowledge of membership and when a receiver leaves, the router need not wait for the response of a Query to collect other member's state to decide the release of a channel.

In the case when bandwidth resources between router and receiver are limited (such as wireless application or wired xdsl applications), one channel is sometimes occupied by only one receiver.  Only if a channel is released, can it be used by another receiver.  The fast leave or releasing of one channel is the precondition of the joining by other receiver to enable it's changing to this channel. In this sense the changing channel is sped up by explicit tracking.

I think we could describe it more detailedly in next revision if needed.

> 
> Whereas Hitoshi and Yogo propose specific figures for Timers 
> and Counters (unfortunately without a reference to 
> measurements verifying the optimization gain), Qin and Hui 
> propose an adaptive Timer increase which seems to be more 
> elegant - but doesn't this require a protocol change?

Adaptive timer setting doesn't require protocol change IMHO.  Though it needs some interface between IGMP and other calculation module to set this parameter. The calculation itself is not in IGMP's scope, thus it will not change the protocol behavior.

> 'Switching between Unicast and Multicast Queries' is 
> implicitly also proposed by Hitoshi and Yogo ...

We propose this according  to the operating mode of MBMS in 3GPP, because multicast mode is not necessarily more efficient than unicast one in all scenarios (e.g when number of receiver is small)

> 
> Actually I don't see real controversary between both drafts 
> but rather to be complementary to each other - however I am 
> no expert on IGMP/MLD ... 
> My overall suggestion is that merging both documents could 
> provide a complete solution to be adopted by the WG.

We'd like to respect WG's decision on this issue. 


Best Regards,
Liu Hui

From asaeda@sfc.wide.ad.jp  Tue Nov  2 02:42:04 2010
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 C7ED03A68CF for <multimob@core3.amsl.com>; Tue,  2 Nov 2010 02:42:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.096
X-Spam-Level: 
X-Spam-Status: No, score=-99.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 dMQGDqfAHnyE for <multimob@core3.amsl.com>; Tue,  2 Nov 2010 02:42:02 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id 206A23A6949 for <multimob@ietf.org>; Tue,  2 Nov 2010 02:41:50 -0700 (PDT)
Received: from localhost (wifi-139-222.sfc.wide.ad.jp [203.178.139.222]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id E42D3278086; Tue,  2 Nov 2010 18:41:46 +0900 (JST)
Date: Tue, 02 Nov 2010 18:41:46 +0900 (JST)
Message-Id: <20101102.184146.26972078.asaeda@sfc.wide.ad.jp>
To: Dirk.von-Hugo@telekom.de
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <643B0A1D1A13AB498304E0BBC802784802BB3DBA@S4DE8PSAAQC.mitte.t-com.de>
References: <326815.19541.qm@web111404.mail.gq1.yahoo.com> <643B0A1D1A13AB498304E0BBC802784802BB3DBA@S4DE8PSAAQC.mitte.t-com.de>
X-Mailer: Mew version 6.2 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] Revised MLD/IGMP Tuning drafts
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: Tue, 02 Nov 2010 09:42:04 -0000

Hi Dirk,

> Qin and Hui give a detailed introduction in wireless and mobile
> multicast isues which could be shortened a bit (BTW also fixed
> access bandwidth e.g. DSL in general is asymmetric - however for
> wireless it could also be a hybrid connection with e.g. broadcast
> e.g. DVB downlink and individual unicast e.g. WLAN uplink). 
> I am not sure whether we need a comparison in detail between
> MLD/IGMP versions as only IGMPv3/MLDv2 is mentioned in the charter.

The draft aims to propose IGMP/MLD optimization by tuning timers or
other values.
Therefore, IMO, it is better that such detail description would be
included in other draft, e.g., the requirement draft, not in the
optimization draft, if needed.

> Both drafts propose to use Explicit Tracking which can considerably
> reduce message traffic and speed up leave latency thus saving
> resources on both network and terminal side.

The spec of the explicit tracking function has been proposed in the
following draft;
http://tools.ietf.org/html/draft-asaeda-mboned-explicit-tracking-01

> Whereas Hitoshi and Yogo propose specific figures for Timers and
> Counters (unfortunately without a reference to measurements
> verifying the optimization gain),

Right. Since I think describing the simulation scenarios may be out of
scope of the I-D, I've not included in the I-D.
I hope I could refer our paper in the revised draft.

> Qin and Hui propose an adaptive
> Timer increase which seems to be more elegant - but doesn't this
> require a protocol change?
> 'Switching between Unicast and Multicast Queries' is implicitly also
> proposed by Hitoshi and Yogo ...

Unicast general query is allowed in RFC3376 and 3810, and hence we had
proposed the use of unicast query for mobility since -00 version of
our optimization draft published on July 2009.
http://tools.ietf.org/html/draft-asaeda-multimob-igmp-mld-optimization-00

However, I believe changing the destination address of general query
and changind the query interval "according to the network or node
condition" require protocol change. They are beyond the standard spec.

Since IMO it is a protocol change, the discussion about unicast vs.
multicast general query with different query intervals has been
discussed in the following "protocol extension" draft.
http://tools.ietf.org/html/draft-asaeda-multimob-igmp-mld-mobility-extensions-04
It is not in the current charter, but if you are interested in, please
take a look at it.

> My overall suggestion is that merging both documents could provide a
> complete solution to be adopted by the WG.

At this moment I'm sorry but I cannot find any reason to merge the
draft.

Regards,
--
Hitoshi Asaeda


From behcetsarikaya@yahoo.com  Tue Nov  2 12:05:01 2010
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 E58E63A6A09 for <multimob@core3.amsl.com>; Tue,  2 Nov 2010 12:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level: 
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[BAYES_50=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 11HbrrD7pIk2 for <multimob@core3.amsl.com>; Tue,  2 Nov 2010 12:05:01 -0700 (PDT)
Received: from nm30-vm0.bullet.mail.sp2.yahoo.com (nm30-vm0.bullet.mail.sp2.yahoo.com [98.139.91.238]) by core3.amsl.com (Postfix) with SMTP id 3E9C73A6A0A for <multimob@ietf.org>; Tue,  2 Nov 2010 12:05:01 -0700 (PDT)
Received: from [98.139.91.70] by nm30.bullet.mail.sp2.yahoo.com with NNFMP; 02 Nov 2010 19:05:02 -0000
Received: from [98.139.91.39] by tm10.bullet.mail.sp2.yahoo.com with NNFMP; 02 Nov 2010 19:05:02 -0000
Received: from [127.0.0.1] by omp1039.mail.sp2.yahoo.com with NNFMP; 02 Nov 2010 19:05:02 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 841755.16919.bm@omp1039.mail.sp2.yahoo.com
Received: (qmail 47943 invoked by uid 60001); 2 Nov 2010 19:05:02 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1288724702; bh=TEVrvIKba/BoBIgEfEN91EzJnCUjwFR1eIzTG1qTBnY=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=qRvA24kdRMVDy7lAwaz+51Fm44papBR36rSSDqoCRYiMBlNvktSxPNmhyRQHP5ORvwFQg+0r3UA1LhrNuhTD9bW9t6RspUZsWNjYqjrv/wnqRWqmcqkNo8m7ogMPKZSXrgtiWSCM4kwtSHHGRnJs/Ml9zC0fz6JdofBPljkAXp4=
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; b=dFJYW/93QFKL4McQFwsujZsFtyWElYy7FtzlgMjLUQSJFaFUgVdIEKVuQjpRYVtSp8rjkNEppNPtt50m8TypbBBRBMkTIDfkKaRZF6PvgufVTYiqj7LTl6uDW0F4IxtYHoI7SMNi1cB54EafOaMbKCnnTqu54PpK76LYEbEmbnA=;
Message-ID: <172030.45271.qm@web111411.mail.gq1.yahoo.com>
X-YMail-OSG: .RiVTssVM1m_u_GBXYP62tP9qcXhXkkkqEcKl9hB4oIpSLn jJLwZV3.Lfo1D3G5pBH9Dy8KwxcDD0TtPUvSErFmKSuD1TpO97_GN9xd8Dlk IbZi4B2qoNP69NwR62FJ1SbefllQ2sQA37LygowM59tSDi1Wi1lF8bJ3SiSo QKdDTtZX057RQT_dU9uPkTTLlNNb45JPt7ZCslx3N38odzfsbKKm8l9IIXwK m0gwmZIWPG1C9pUimN6evcG93gSKdCy.8VBs1E7qiDiVIxkABAerPM59hSYl PaFG9fK2z8NBdT.jibv050Y_q1UJPsz5xQgORHYSS0.YICCsX5CO_4HEQnyo -
Received: from [206.16.17.212] by web111411.mail.gq1.yahoo.com via HTTP; Tue, 02 Nov 2010 12:05:02 PDT
X-Mailer: YahooMailRC/504.5 YahooMailWebService/0.8.107.284920
Date: Tue, 2 Nov 2010 12:05:02 -0700 (PDT)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [multimob] SLIDES
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, 02 Nov 2010 19:05:02 -0000

Those presenting,

Please send your slides to the chairs.

So far we received only one.



      

From asaeda@sfc.wide.ad.jp  Mon Nov  8 09:29:43 2010
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 B45AC3A697F for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 09:29:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.796
X-Spam-Level: 
X-Spam-Status: No, score=-98.796 tagged_above=-999 required=5 tests=[AWL=0.300, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 ntg0-b0lVH5S for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 09:29:42 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id D13323A67E5 for <multimob@ietf.org>; Mon,  8 Nov 2010 09:29:42 -0800 (PST)
Received: from localhost (dhcp-451b.meeting.ietf.org [130.129.69.27]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id D97392780DC for <multimob@ietf.org>; Tue,  9 Nov 2010 02:30:00 +0900 (JST)
Date: Tue, 09 Nov 2010 01:29:56 +0800 (CST)
Message-Id: <20101109.012956.182492154.asaeda@sfc.wide.ad.jp>
To: multimob@ietf.org
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: [multimob] new igmp/mld tuning draft
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, 08 Nov 2010 17:29:43 -0000

Hello all,

Because I needed to improve many parts for my igmp/mld tuning draft
(-04), I've modified the draft and uploaded the tentatively revised
draft (-04a) on the following web page.
http://www.sfc.wide.ad.jp/~asaeda/paper/draft-asaeda-multimob-igmp-mld-optimization-04a.txt

I'm sorry for this very late update, but if you have time, please take
a look at it before tomorrows meeting.

Regards,
--
Hitoshi Asaeda


From schmidt@informatik.haw-hamburg.de  Mon Nov  8 09:32:02 2010
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 2D3FD3A6851 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 09:32:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
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 XKkXq+Suf6QP for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 09:31:59 -0800 (PST)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 133983A6837 for <multimob@ietf.org>; Mon,  8 Nov 2010 09:31:59 -0800 (PST)
Envelope-to: multimob@ietf.org
Received: from [220.113.5.98] (helo=[192.168.1.81]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1PFVZs-000IGA-3I for multimob@ietf.org; Mon, 08 Nov 2010 18:32:20 +0100
Message-ID: <4CD8341D.7040305@informatik.haw-hamburg.de>
Date: Tue, 09 Nov 2010 01:32:13 +0800
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: "multimob@ietf.org" <multimob@ietf.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: multimob@ietf.org
Subject: [multimob] Fwd: New Version Notification for draft-schmidt-multimob-fmipv6-pfmipv6-multicast-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, 08 Nov 2010 17:32:02 -0000

Hi all,

we have submitted an update of the FMIPv6/PFMIPv6 multicast draft: 
http://www.ietf.org/id/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-03.txt

This revision has filled the remaining gaps and undertaken some 
editorial improvements.

Sorry for being late, but this was just a finish-up.

Let's discuss tomorrow ...

Thomas

-------- Original Message --------
Subject: New Version Notification for 
draft-schmidt-multimob-fmipv6-pfmipv6-multicast-03
Date: Mon,  8 Nov 2010 09:20:40 -0800 (PST)
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,rkoodli@cisco.com,gorry@erg.abdn.ac.uk


A new version of I-D, 
draft-schmidt-multimob-fmipv6-pfmipv6-multicast-03.txt has been 
successfully submitted by Thomas Schmidt and posted to the IETF repository.

Filename:	 draft-schmidt-multimob-fmipv6-pfmipv6-multicast
Revision:	 03
Title:		 Multicast Listener Extensions for MIPv6 and PMIPv6 Fast Handovers
Creation_date:	 2010-11-08
WG ID:		 Independent Submission
Number_of_pages: 24

Abstract:
Fast handover protocols for MIPv6 and PMIPv6 define mobility
management procedures that support unicast communication at reduced
handover latencies.  Fast handover base operations do not affect
multicast communication, and hence do not accelerate handover
management for native multicast listeners.  Many multicast
applications like IPTV or conferencing, though, are comprised of
delay-sensitive real-time traffic and will benefit from fast handover
execution.  This document specifies extension of the Mobile IPv6 Fast
Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6
(PFMIPv6) protocols to include multicast traffic management in fast
handover operations.
 



The IETF Secretariat.



From gaoxlh@gmail.com  Mon Nov  8 17:19:08 2010
Return-Path: <gaoxlh@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 36EDD3A6862 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 17:19:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.929
X-Spam-Level: 
X-Spam-Status: No, score=-1.929 tagged_above=-999 required=5 tests=[AWL=0.670,  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 tMUcAEPTem4Q for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 17:19:07 -0800 (PST)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 473C63A67EC for <multimob@ietf.org>; Mon,  8 Nov 2010 17:19:07 -0800 (PST)
Received: by wyb28 with SMTP id 28so6154261wyb.31 for <multimob@ietf.org>; Mon, 08 Nov 2010 17:19:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:date:from:to:subject :message-id:x-mailer:mime-version:content-type :content-transfer-encoding; bh=MPAWcnaGWPbq19zEA+KwmxKYSgQAsfIIldLTCE3JJpo=; b=b7esuvXu1TFXzVcuYUeIwZUejjOWySJUR80I3cXimwm9bvcm7VEclxMUimgFDSgJcf kgB8xJOvvCR31lOCcwQVgIMaZKIC/LYfRa7efAH3JKCC96slma+Cv2xS6xHXqQYCkkee iHc/jEGCUCyhI66uqYxC7uFrhvq63yHUWhRy0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:subject:message-id:x-mailer:mime-version:content-type :content-transfer-encoding; b=gziMaba8gi1Qkla80688lXypyVlysvAyXXeuu/52jeWSN6cSMd5X5kV6+wYx9b3/tt NQyKbdGQsfbyHswXW8rd5xkaQb2wzDi3JXS4IIDpbGe4DpwSMPHW7SRzq85UrQTpLZl2 37A5ApXQWYS9yCr6UJzKvPyXsdWAnc9mcLgsc=
Received: by 10.227.128.131 with SMTP id k3mr6134857wbs.66.1289265568826; Mon, 08 Nov 2010 17:19:28 -0800 (PST)
Received: from PC-201001071138 ([211.71.74.133]) by mx.google.com with ESMTPS id b30sm526020wbb.4.2010.11.08.17.19.27 (version=SSLv3 cipher=RC4-MD5); Mon, 08 Nov 2010 17:19:28 -0800 (PST)
Date: Tue, 9 Nov 2010 09:19:00 +0800
From: "Shuai Gao" <gaoxlh@gmail.com>
To: "multimob" <multimob@ietf.org>
Message-ID: <201011090918581251390@gmail.com>
X-mailer: Foxmail 6, 14, 103, 30 [cn]
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: [multimob] new version about draft-zhang-multimob-msm-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: Tue, 09 Nov 2010 01:19:08 -0000

Hi, all,

   We just submitted new version multicast source mobility draft:   http://www.ietf.org/id/draft-zhang-multimob-msm-01.txt

I'm sorry for this very late submission.  If you have time, please take a look it 
and let's discuss this afternoon.


Best Regards,

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


From jari.arkko@piuha.net  Mon Nov  8 20:18:17 2010
Return-Path: <jari.arkko@piuha.net>
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 5756C3A6924 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:18:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.954
X-Spam-Level: 
X-Spam-Status: No, score=-101.954 tagged_above=-999 required=5 tests=[AWL=-0.573, BAYES_00=-2.599, HTML_MESSAGE=0.001, HTML_TITLE_SUBJ_DIFF=1.217, USER_IN_WHITELIST=-100]
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 tHBshfFbl46e for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:18:15 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 9327A3A6A05 for <multimob@ietf.org>; Mon,  8 Nov 2010 20:18:14 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 18C0C2CC4A for <multimob@ietf.org>; Tue,  9 Nov 2010 06:18:37 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kUOqFCPYCCKY for <multimob@ietf.org>; Tue,  9 Nov 2010 06:18:35 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 2199B2CC32 for <multimob@ietf.org>; Tue,  9 Nov 2010 06:18:33 +0200 (EET)
Message-ID: <4CD8CB98.5060506@piuha.net>
Date: Tue, 09 Nov 2010 12:18:32 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: multimob@ietf.org
Content-Type: multipart/mixed; boundary="------------090806040001080508040609"
Subject: [multimob] new charter
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: Tue, 09 Nov 2010 04:18:17 -0000

This is a multi-part message in MIME format.
--------------090806040001080508040609
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Would this new charter be acceptable for the working group:



--------------090806040001080508040609
Content-Type: text/plain;
 name="nov2010charternew.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="nov2010charternew.txt"

Multicast Mobility (multimob)
-----------------------------

 Charter

 Current Status: Active

 Chairs:
     Behcet Sarikaya <sarikaya@ieee.org>
     Stig Venaas <stig@venaas.com>
     Behcet Sarikaya <bsarikaya@huawei.com>

 Internet Area Directors:
     Ralph Droms <rdroms.ietf@gmail.com>
     Jari Arkko <jari.arkko@piuha.net>

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

 Mailing Lists:
     General Discussion: multimob@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

  The Multicast mobility (multimob) working group provides guidance
  for supporting multicast in a mobile environment. The scope of work
  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
  listener mobility. The group will work on extensions of Proxy Mobile
  IPv6 to improve its capability to handle multicast efficiently. Work
  requiring modifications to IGMPv3/MLDv2 is out of scope in this
  stage of this working group, however, as are modifications to
  multicast routing protocols.

  Specific goals for the group are: 

  - A solution to the tunnel convergence problem by separating
    multicast routing from the Local Mobility Anchor (LMA) in
    PMIPv6. Possible techniques are using native infrastructure, using
    a dedicated LMA etc.

  - Extensions to PMIPv6 for handover optimizations including context
    transfer. A requirements document and solution document will be
    published.

  - The Multimob WG will explore PMIPv6 extensions needed to support
    multicast source mobility. Both any source multicast and source
    specific multicast source mobility will be covered.

  - Document the configuration of IGMPv3/MLDv2 in mobile environments

  The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213
  does not describe how to support multicast. Some forms of multicast
  support can, however, be built in the involved nodes by using
  existing capabilities of multicast protocols and the underlying
  mobility protocols. The working group has already documented how
  existing mechanisms can be used to support multicast, without
  requiring any additions or changes to message types and parameters
  specified in RFC 5213, and assuming an unmodified mobile host. The
  current goals of the working group relate to improving the
  efficiency of this base solution. The work will employ the remote
  subscription model. This is a mechanism by which a mobile node joins
  a multicast group and receives multicast data forwarded via the
  local mobility anchor.

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

  In performing its work, the working group will work closely with
  both the mobility community (NETEXT WG) and the multicast community
  (MBONED WG). The group will consider both source specific multicast
  and any source multicast multicast models.

  Future work, subject to rechartering, may study/evaluate extensions
  to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility
Apr 2011 - Initial version of document stating requirements on PMIPv6 extensions for handover
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice
Jun 2011 - Initial version of document on PMIPv6 direct routing optimizations to avoid tunnel convergence problem
Nov 2011 - Initial version of document on PMIPv6 handover optimizations
Nov 2011 - Initial version of document on PMIPv6 multicast source mobility solution
Apr 2012 - Submit requirements document to IESG for publication as informational
Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG for publication as Internet Standard
Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for publication as Internet Standard
Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for publication as Internet Standard
Dec 2012 - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2
Dec 2012 - Recharter based on the above decisions (or close the group if no new work is needed)



--------------090806040001080508040609
Content-Type: text/html; charset=ISO-8859-1;
 name="nov2010charternew-from-old.diff.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="nov2010charternew-from-old.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.32: rfcdiff nov2010charterold.txt nov2010charternew.txt --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Linux dummy 2.6.31-22-generic #67-Ubuntu SMP Sat Oct 16 18:51:35 UTC 2010 x86_64 GNU/Linux --> 
<!-- Using awk: /usr/bin/gawk: GNU Awk 3.1.6 --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/bin/wdiff: GNU wdiff 0.5 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: nov2010charterold.txt - nov2010charternew.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;nov2010charterold.txt&nbsp;</th><th> </th><th>&nbsp;nov2010charternew.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l1" /><small>skipping to change at</small><em> line 27</em></th><th> </th><th><a name="part-r1" /><small>skipping to change at</small><em> line 27</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Internet Area Advisor:</td><td> </td><td class="right"> Internet Area Advisor:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td> </td><td class="right">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Mailing Lists:</td><td> </td><td class="right"> Mailing Lists:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     General Discussion: multimob@ietf.org</td><td> </td><td class="right">     General Discussion: multimob@ietf.org</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob</td><td> </td><td class="right">     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html</td><td> </td><td class="right">     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Description of Working Group:</td><td> </td><td class="right">Description of Working Group:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  The Multicast mobility (multimob) working group provides guidance for</td><td> </td><td class="rblock">  The Multicast mobility (multimob) working group provides guidance</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  supporting multicast in a mobile environment. The scope of work will</td><td> </td><td class="rblock">  for supporting multicast in a mobile environment. The scope of work</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and listener</td><td> </td><td class="rblock">  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobility. Work requiring modifications to <span class="delete">mobility protocols and</span></td><td> </td><td class="rblock">  listener mobility. <span class="insert">The group will work on extensions of Proxy Mobile</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  IGMPv3/MLDv2 is out of scope in this <span class="delete">first</span> stage of this working <span class="delete">group.</span></td><td> </td><td class="rblock"><span class="insert">  IPv6 to improve its capability to handle multicast efficiently.</span> Work</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Modifications</span> to multicast routing <span class="delete">protocols are out of scope.</span></td><td> </td><td class="rblock">  requiring modifications to IGMPv3/MLDv2 is out of scope in this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  stage of this working <span class="insert">group, however, as are modifications</span> to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  multicast routing <span class="insert">protocols.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Specific goals for the group are:</td><td> </td><td class="right">  Specific goals for the group are:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  - <span class="delete">Document how</span> multicast <span class="delete">can be supported</span> in a <span class="delete">Proxy Mobile IPv6</span></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  environment</span></td><td> </td><td class="rblock">  - <span class="insert">A solution to the tunnel convergence problem by separating</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">    multicast <span class="insert">routing from the Local Mobility Anchor (LMA)</span> in</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">    <span class="insert">PMIPv6. Possible techniques are using native infrastructure, using</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">    a <span class="insert">dedicated LMA etc.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  - Extensions to PMIPv6 for handover optimizations including context</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    transfer. A requirements document and solution document will be</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    published.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  - The Multimob WG will explore PMIPv6 extensions needed to support</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    multicast source mobility. Both any source multicast and source</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    specific multicast source mobility will be covered.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  - Document the configuration of IGMPv3/MLDv2 in mobile environments</td><td> </td><td class="right">  - Document the configuration of IGMPv3/MLDv2 in mobile environments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213</td><td> </td><td class="right">  The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  does not describe how to support multicast. Some forms of multicast</td><td> </td><td class="right">  does not describe how to support multicast. Some forms of multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  support can, however, be built in the involved nodes by using existing</td><td> </td><td class="rblock">  support can, however, be built in the involved nodes by using</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  capabilities of multicast protocols and the underlying mobility</td><td> </td><td class="rblock">  existing capabilities of multicast protocols and the underlying</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  protocols. The <span class="delete">first task of the</span> working group <span class="delete">is</span> to <span class="delete">document such</span></td><td> </td><td class="rblock">  mobility protocols. The working group <span class="insert">has already documented how</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  solutions for PMIPv6. This work will not require</span> any additions or</td><td> </td><td class="rblock"><span class="insert">  existing mechanisms can be used</span> to <span class="insert">support multicast, without</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  changes to message types and parameters specified in RFC 5213, and</td><td> </td><td class="rblock"><span class="insert">  requiring</span> any additions or changes to message types and parameters</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">must assume</span> an unmodified mobile host. The work will employ the remote</td><td> </td><td class="rblock">  specified in RFC 5213, and <span class="insert">assuming</span> an unmodified mobile host. The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  subscription model. This is a mechanism by which a mobile node joins a</td><td> </td><td class="rblock">  <span class="insert">current goals of the working group relate to improving the</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  multicast group and receives multicast data forwarded via the local</td><td> </td><td class="rblock"><span class="insert">  efficiency of this base solution. The</span> work will employ the remote</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobility anchor.</td><td> </td><td class="rblock">  subscription model. This is a mechanism by which a mobile node joins</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  a multicast group and receives multicast data forwarded via the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  local mobility anchor.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  IGMPv3/MLDv2 has been specified for wired networks with shared links.</td><td> </td><td class="right">  IGMPv3/MLDv2 has been specified for wired networks with shared links.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Mobile nodes have needs that are specific to wireless networks and</td><td> </td><td class="right">  Mobile nodes have needs that are specific to wireless networks and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  mobility (e.g. entering a dormant mode to conserve battery power,</td><td> </td><td class="right">  mobility (e.g. entering a dormant mode to conserve battery power,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  minimizing the latency for joining and leaving a group in support of</td><td> </td><td class="right">  minimizing the latency for joining and leaving a group in support of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  movement).</td><td> </td><td class="right">  movement).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">The second task of the WG is to assess existing solutions for group</span></td><td> </td><td class="rblock">  In performing its work, the working group will work closely with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  management, and determine to what extent these methods are sufficient</span></td><td> </td><td class="rblock">  both the mobility community <span class="insert">(NETEXT WG)</span> and the multicast community</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  in a mobile environment. This will include recommending appropriate</span></td><td> </td><td class="rblock">  (MBONED WG). The group will consider both source specific multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  selection of timer values and protocol parameters.</span></td><td> </td><td class="rblock">  and any source multicast multicast models.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  In performing its work, the working group will work closely with both</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  the mobility community <span class="delete">(NETLMM and NETEXT WGs)</span> and the multicast</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  community (MBONED WG). The group will consider both source specific</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  multicast and any source multicast multicast models.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Future work, subject to rechartering, may study/evaluate extensions to</td><td> </td><td class="rblock">  Future work, subject to rechartering, may study/evaluate extensions</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">support PMIPv6 optimizations to address the avalanche problem and fast</span></td><td> </td><td class="rblock">  to IGMPv3/MLDv2 to support better operation in mobile environments.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  handover and extensions to</span> IGMPv3/MLDv2 to support better operation in</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobile environments.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Goals and Milestones:</td><td> </td><td class="right">Goals and Milestones:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Nov 2009 - Initial version of a document explaining the use of multicast in PMIPv6</span></td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility</td><td> </td><td class="right">  Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0007" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Apr <span class="delete">2010</span> - <span class="delete">Submit a document explaining the use</span> of <span class="delete">multicast in PMIPv6,</span> for <span class="delete">publication as either Informational or Best Current Practice</span></td><td> </td><td class="rblock">Apr <span class="insert">2011</span> - <span class="insert">Initial version</span> of <span class="insert">document stating requirements on PMIPv6 extensions</span> for <span class="insert">handover</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Apr <span class="delete">2010</span> - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice</td><td> </td><td class="rblock">Apr <span class="insert">2011</span> - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Jun <span class="delete">2010</span> - <span class="delete">Decision to include additional optimization work involving extensions</span> to PMIPv6</td><td> </td><td class="rblock">Jun <span class="insert">2011</span> - <span class="insert">Initial version of document on PMIPv6 direct routing optimizations</span> to <span class="insert">avoid tunnel convergence problem</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Jun <span class="delete">2010</span> - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2</td><td> </td><td class="rblock"><span class="insert">Nov 2011 - Initial version of document on PMIPv6 handover optimizations</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">Jun 2010</span> - Recharter based on the above decisions (or close the group if no new work is needed)</td><td> </td><td class="rblock"><span class="insert">Nov 2011 - Initial version of document on</span> PMIPv6 <span class="insert">multicast source mobility solution</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Apr 2012 - Submit requirements document to IESG for publication as informational</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">Jun <span class="insert">2012 - Submit PMIPv6 local routing optimizations document to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Dec 2012</span> - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Dec 2012</span> - Recharter based on the above decisions (or close the group if no new work is needed)</td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 7 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>31 lines changed or deleted</i></th><th><i> </i></th><th><i>39 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.32. The latest version is available from <a href="http://www.levkowetz.com/ietf/tools/rfcdiff/" >http://www.levkowetz.com/ietf/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--------------090806040001080508040609--

From tme@americafree.tv  Mon Nov  8 20:26:17 2010
Return-Path: <tme@americafree.tv>
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 AC3EE3A6875 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:26:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.663
X-Spam-Level: 
X-Spam-Status: No, score=-102.663 tagged_above=-999 required=5 tests=[AWL=-0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 uHzh8flWWYw2 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:26:15 -0800 (PST)
Received: from mail.americafree.tv (rossini.americafree.tv [63.105.122.34]) by core3.amsl.com (Postfix) with ESMTP id D91343A68EB for <multimob@ietf.org>; Mon,  8 Nov 2010 20:26:08 -0800 (PST)
Received: from [IPv6:::1] (rossini.americafree.tv [63.105.122.34]) by mail.americafree.tv (Postfix) with ESMTP id 0A2379307C51; Mon,  8 Nov 2010 23:26:29 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset=us-ascii
From: Marshall Eubanks <tme@americafree.tv>
In-Reply-To: <4CD8CB98.5060506@piuha.net>
Date: Mon, 8 Nov 2010 23:26:27 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <8CDA2C0B-1CCA-4985-9B71-7DCDB9DF4ADC@americafree.tv>
References: <4CD8CB98.5060506@piuha.net>
To: Jari Arkko <jari.arkko@piuha.net>
X-Mailer: Apple Mail (2.1081)
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 04:26:17 -0000

On Nov 8, 2010, at 11:18 PM, Jari Arkko wrote:

> Would this new charter be acceptable for the working group:
>=20
>=20
> Multicast Mobility (multimob)
> -----------------------------
>=20
> Charter
>=20
> Current Status: Active
>=20
> Chairs:
>     Behcet Sarikaya <sarikaya@ieee.org>
>     Stig Venaas <stig@venaas.com>
>     Behcet Sarikaya <bsarikaya@huawei.com>
>=20
> Internet Area Directors:
>     Ralph Droms <rdroms.ietf@gmail.com>
>     Jari Arkko <jari.arkko@piuha.net>
>=20
> Internet Area Advisor:
>     Jari Arkko <jari.arkko@piuha.net>
>=20
> Mailing Lists:
>     General Discussion: multimob@ietf.org
>     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
>     Archive:            =
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html
>=20
> Description of Working Group:
>=20
>  The Multicast mobility (multimob) working group provides guidance
>  for supporting multicast in a mobile environment. The scope of work
>  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
>  listener mobility. The group will work on extensions of Proxy Mobile
>  IPv6 to improve its capability to handle multicast efficiently. Work
>  requiring modifications to IGMPv3/MLDv2 is out of scope in this
>  stage of this working group, however, as are modifications to
>  multicast routing protocols.
>=20
>  Specific goals for the group are:=20
>=20
>  - A solution to the tunnel convergence problem by separating
>    multicast routing from the Local Mobility Anchor (LMA) in
>    PMIPv6. Possible techniques are using native infrastructure, using
>    a dedicated LMA etc.
>=20
>  - Extensions to PMIPv6 for handover optimizations including context
>    transfer. A requirements document and solution document will be
>    published.
>=20
>  - The Multimob WG will explore PMIPv6 extensions needed to support
>    multicast source mobility. Both any source multicast and source
>    specific multicast source mobility will be covered.
>=20
>  - Document the configuration of IGMPv3/MLDv2 in mobile environments
>=20
>  The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213
>  does not describe how to support multicast. Some forms of multicast
>  support can, however, be built in the involved nodes by using
>  existing capabilities of multicast protocols and the underlying
>  mobility protocols. The working group has already documented how
>  existing mechanisms can be used to support multicast, without
>  requiring any additions or changes to message types and parameters
>  specified in RFC 5213, and assuming an unmodified mobile host. The
>  current goals of the working group relate to improving the
>  efficiency of this base solution. The work will employ the remote
>  subscription model. This is a mechanism by which a mobile node joins
>  a multicast group and receives multicast data forwarded via the
>  local mobility anchor.
>=20
>  IGMPv3/MLDv2 has been specified for wired networks with shared links.
>  Mobile nodes have needs that are specific to wireless networks and
>  mobility (e.g. entering a dormant mode to conserve battery power,
>  minimizing the latency for joining and leaving a group in support of
>  movement).
>=20
>  In performing its work, the working group will work closely with
>  both the mobility community (NETEXT WG) and the multicast community
>  (MBONED WG). The group will consider both source specific multicast
>  and any source multicast multicast models.
>=20
>  Future work, subject to rechartering, may study/evaluate extensions
>  to IGMPv3/MLDv2 to support better operation in mobile environments.
>=20
>=20
> Goals and Milestones:
> Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 =
for mobility

2009 ?

Marshall

> Apr 2011 - Initial version of document stating requirements on PMIPv6 =
extensions for handover
> Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, =
for publication as either Informational or Best Current Practice
> Jun 2011 - Initial version of document on PMIPv6 direct routing =
optimizations to avoid tunnel convergence problem
> Nov 2011 - Initial version of document on PMIPv6 handover =
optimizations
> Nov 2011 - Initial version of document on PMIPv6 multicast source =
mobility solution
> Apr 2012 - Submit requirements document to IESG for publication as =
informational
> Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG =
for publication as Internet Standard
> Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for =
publication as Internet Standard
> Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG =
for publication as Internet Standard
> Dec 2012 - Decision to include additional optimization work involving =
extensions to IGMPv3 or MLDv2
> Dec 2012 - Recharter based on the above decisions (or close the group =
if no new work is needed)
>=20
>=20
>  nov2010charterold.txt 		 nov2010charternew.txt =09
> skipping to change at line 27		skipping to change at line 27=09
> Internet Area Advisor:		 Internet Area Advisor:=09
> Jari Arkko <jari.arkko@piuha.net>		 Jari Arkko =
<jari.arkko@piuha.net>=09
> Mailing Lists:		 Mailing Lists:=09
> General Discussion: multimob@ietf.org		 General Discussion: =
multimob@ietf.org=09
> To Subscribe: https://www.ietf.org/mailman/listinfo/multimob		 =
To Subscribe: https://www.ietf.org/mailman/listinfo/multimob=09
> Archive: =
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html		=
 Archive: =
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html=09
> Description of Working Group:		Description of Working Group:=09
> The Multicast mobility (multimob) working group provides guidance for		=
 The Multicast mobility (multimob) working group provides guidance=09
> supporting multicast in a mobile environment. The scope of work will		=
 for supporting multicast in a mobile environment. The scope of work=09
> be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and listener		=
 will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and=09
> mobility. Work requiring modifications to mobility protocols and		=
 listener mobility. The group will work on extensions of Proxy Mobile=09
> IGMPv3/MLDv2 is out of scope in this first stage of this working =
group.		 IPv6 to improve its capability to handle multicast =
efficiently. Work=09
> Modifications to multicast routing protocols are out of scope.		=
 requiring modifications to IGMPv3/MLDv2 is out of scope in this=09
> stage of this working group, however, as are modifications to=09
> multicast routing protocols.=09
> Specific goals for the group are:		 Specific goals for the =
group are:=09
> - Document how multicast can be supported in a Proxy Mobile IPv6		=
=09
> environment		 - A solution to the tunnel convergence problem =
by separating=09
> multicast routing from the Local Mobility Anchor (LMA) in=09
> PMIPv6. Possible techniques are using native infrastructure, using=09
> a dedicated LMA etc.=09
> - Extensions to PMIPv6 for handover optimizations including context=09
> transfer. A requirements document and solution document will be=09
> published.=09
> - The Multimob WG will explore PMIPv6 extensions needed to support=09
> multicast source mobility. Both any source multicast and source=09
> specific multicast source mobility will be covered.=09
> - Document the configuration of IGMPv3/MLDv2 in mobile environments		=
 - Document the configuration of IGMPv3/MLDv2 in mobile environments=09
> The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213		=
 The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213=09
> does not describe how to support multicast. Some forms of multicast		=
 does not describe how to support multicast. Some forms of multicast=09
> support can, however, be built in the involved nodes by using existing	=
	 support can, however, be built in the involved nodes by using=09=

> capabilities of multicast protocols and the underlying mobility		=
 existing capabilities of multicast protocols and the underlying=09
> protocols. The first task of the working group is to document such		=
 mobility protocols. The working group has already documented how=09
> solutions for PMIPv6. This work will not require any additions or		=
 existing mechanisms can be used to support multicast, without=09
> changes to message types and parameters specified in RFC 5213, and		=
 requiring any additions or changes to message types and parameters=09
> must assume an unmodified mobile host. The work will employ the remote	=
	 specified in RFC 5213, and assuming an unmodified mobile host. =
The=09
> subscription model. This is a mechanism by which a mobile node joins a	=
	current goals of the working group relate to improving the=09
> multicast group and receives multicast data forwarded via the local		=
 efficiency of this base solution. The work will employ the remote=09
> mobility anchor.		 subscription model. This is a mechanism =
by which a mobile node joins=09
> a multicast group and receives multicast data forwarded via the=09
> local mobility anchor.=09
> IGMPv3/MLDv2 has been specified for wired networks with shared links.		=
 IGMPv3/MLDv2 has been specified for wired networks with shared links.=09=

> Mobile nodes have needs that are specific to wireless networks and		=
 Mobile nodes have needs that are specific to wireless networks and=09
> mobility (e.g. entering a dormant mode to conserve battery power,		=
 mobility (e.g. entering a dormant mode to conserve battery power,=09
> minimizing the latency for joining and leaving a group in support of		=
 minimizing the latency for joining and leaving a group in support of=09
> movement).		 movement).=09
> The second task of the WG is to assess existing solutions for group		=
 In performing its work, the working group will work closely with=09
> management, and determine to what extent these methods are sufficient		=
 both the mobility community (NETEXT WG) and the multicast community=09
> in a mobile environment. This will include recommending appropriate		=
 (MBONED WG). The group will consider both source specific multicast=09
> selection of timer values and protocol parameters.		 and any =
source multicast multicast models.=09
> In performing its work, the working group will work closely with both		=
=09
> the mobility community (NETLMM and NETEXT WGs) and the multicast		=
=09
> community (MBONED WG). The group will consider both source specific		=
=09
> multicast and any source multicast multicast models.		=09
> Future work, subject to rechartering, may study/evaluate extensions to	=
	 Future work, subject to rechartering, may study/evaluate =
extensions=09
> support PMIPv6 optimizations to address the avalanche problem and fast	=
	 to IGMPv3/MLDv2 to support better operation in mobile =
environments.=09
> handover and extensions to IGMPv3/MLDv2 to support better operation in	=
	=09
> mobile environments.		=09
> Goals and Milestones:		Goals and Milestones:=09
> Nov 2009 - Initial version of a document explaining the use of =
multicast in PMIPv6		=09
> Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 =
for mobility		 Nov 2009 - Initial version of a document on how =
to tune IGMPv3/MLDv2 for mobility=09
> Apr 2010 - Submit a document explaining the use of multicast in =
PMIPv6, for publication as either Informational or Best Current Practice	=
	Apr 2011 - Initial version of document stating requirements on =
PMIPv6 extensions for handover=09
> Apr 2010 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, =
for publication as either Informational or Best Current Practice		=
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, =
for publication as either Informational or Best Current Practice=09
> Jun 2010 - Decision to include additional optimization work involving =
extensions to PMIPv6		Jun 2011 - Initial version of document =
on PMIPv6 direct routing optimizations to avoid tunnel convergence =
problem=09
> Jun 2010 - Decision to include additional optimization work involving =
extensions to IGMPv3 or MLDv2		Nov 2011 - Initial version of =
document on PMIPv6 handover optimizations=09
> Jun 2010 - Recharter based on the above decisions (or close the group =
if no new work is needed)		Nov 2011 - Initial version of =
document on PMIPv6 multicast source mobility solution=09
> Apr 2012 - Submit requirements document to IESG for publication as =
informational=09
> Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG =
for publication as Internet Standard=09
> Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for =
publication as Internet Standard=09
> Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG =
for publication as Internet Standard=09
> Dec 2012 - Decision to include additional optimization work involving =
extensions to IGMPv3 or MLDv2=09
> Dec 2012 - Recharter based on the above decisions (or close the group =
if no new work is needed)=09
>  End of changes. 7 change blocks.=20
> 31 lines changed or deleted		39 lines changed or added=09
>=20
> This html diff was produced by rfcdiff 1.32. The latest version is =
available from http://www.levkowetz.com/ietf/tools/rfcdiff/
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob


From schmidt@fhtw-berlin.de  Mon Nov  8 20:58:09 2010
Return-Path: <schmidt@fhtw-berlin.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 D513528C0DD for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:58:09 -0800 (PST)
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 KX8KTAZF5WDo for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:58:08 -0800 (PST)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 6B0433A677C for <multimob@ietf.org>; Mon,  8 Nov 2010 20:58:08 -0800 (PST)
Envelope-to: multimob@ietf.org
Received: from dhcp-4535.meeting.ietf.org ([130.129.69.53]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@fhtw-berlin.de>) id 1PFgHu-000H3k-HR; Tue, 09 Nov 2010 05:58:31 +0100
Message-ID: <4CD8D4E7.4030205@fhtw-berlin.de>
Date: Tue, 09 Nov 2010 12:58:15 +0800
From: "Thomas C. Schmidt" <schmidt@fhtw-berlin.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4CD8CB98.5060506@piuha.net>
In-Reply-To: <4CD8CB98.5060506@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: multimob@ietf.org
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 04:58:09 -0000

Hi Jari, hi all,

from a first look, the scope looks a bit too narrow to me ...

IMHO it's fine to start from PMIP, but there are a number of 
problems/protocols that are better solved in a bit more generic way.

One obvious example is context transfer, where we believe that a 
rigorous restriction to PMIP would narrow the value of an otherwise more 
general approach 
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-03

... the other immediate example would be direct / optimized routing, 
where the actual PMIP handover mechanisms fade to the background, and 
multicast route organization towards the ARs comes into focus. Such 
mechanisms most likely will not be bound to PMIP operations.

Cheers,

Thomas

On 09.11.2010 12:18, Jari Arkko wrote:
> Would this new charter be acceptable for the working group:
>
>
nov2010charternew.txt

Multicast Mobility (multimob)
-----------------------------

  Charter

  Current Status: Active

  Chairs:
      Behcet Sarikaya <sarikaya@ieee.org>
      Stig Venaas <stig@venaas.com>
      Behcet Sarikaya <bsarikaya@huawei.com>

  Internet Area Directors:
      Ralph Droms <rdroms.ietf@gmail.com>
      Jari Arkko <jari.arkko@piuha.net>

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

  Mailing Lists:
      General Discussion: multimob@ietf.org
      To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
      Archive: 
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

   The Multicast mobility (multimob) working group provides guidance
   for supporting multicast in a mobile environment. The scope of work
   will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
   listener mobility. The group will work on extensions of Proxy Mobile
   IPv6 to improve its capability to handle multicast efficiently. Work
   requiring modifications to IGMPv3/MLDv2 is out of scope in this
   stage of this working group, however, as are modifications to
   multicast routing protocols.

   Specific goals for the group are:

   - A solution to the tunnel convergence problem by separating
     multicast routing from the Local Mobility Anchor (LMA) in
     PMIPv6. Possible techniques are using native infrastructure, using
     a dedicated LMA etc.

   - Extensions to PMIPv6 for handover optimizations including context
     transfer. A requirements document and solution document will be
     published.

   - The Multimob WG will explore PMIPv6 extensions needed to support
     multicast source mobility. Both any source multicast and source
     specific multicast source mobility will be covered.

   - Document the configuration of IGMPv3/MLDv2 in mobile environments

   The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213
   does not describe how to support multicast. Some forms of multicast
   support can, however, be built in the involved nodes by using
   existing capabilities of multicast protocols and the underlying
   mobility protocols. The working group has already documented how
   existing mechanisms can be used to support multicast, without
   requiring any additions or changes to message types and parameters
   specified in RFC 5213, and assuming an unmodified mobile host. The
   current goals of the working group relate to improving the
   efficiency of this base solution. The work will employ the remote
   subscription model. This is a mechanism by which a mobile node joins
   a multicast group and receives multicast data forwarded via the
   local mobility anchor.

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

   In performing its work, the working group will work closely with
   both the mobility community (NETEXT WG) and the multicast community
   (MBONED WG). The group will consider both source specific multicast
   and any source multicast multicast models.

   Future work, subject to rechartering, may study/evaluate extensions
   to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for 
mobility
Apr 2011 - Initial version of document stating requirements on PMIPv6 
extensions for handover
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, 
for publication as either Informational or Best Current Practice
Jun 2011 - Initial version of document on PMIPv6 direct routing 
optimizations to avoid tunnel convergence problem
Nov 2011 - Initial version of document on PMIPv6 handover optimizations
Nov 2011 - Initial version of document on PMIPv6 multicast source 
mobility solution
Apr 2012 - Submit requirements document to IESG for publication as 
informational
Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG 
for publication as Internet Standard
Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for 
publication as Internet Standard
Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for 
publication as Internet Standard
Dec 2012 - Decision to include additional optimization work involving 
extensions to IGMPv3 or MLDv2
Dec 2012 - Recharter based on the above decisions (or close the group if 
no new work is needed)


From jari.arkko@piuha.net  Mon Nov  8 20:59:56 2010
Return-Path: <jari.arkko@piuha.net>
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 282D13A6887 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:59:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.532
X-Spam-Level: 
X-Spam-Status: No, score=-102.532 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cyy-TZKh91kc for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 20:59:52 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id C28F83A683A for <multimob@ietf.org>; Mon,  8 Nov 2010 20:59:51 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 2B3F12CC3C; Tue,  9 Nov 2010 07:00:14 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id v4hAIl0A1im4; Tue,  9 Nov 2010 07:00:13 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 812C12CC32; Tue,  9 Nov 2010 07:00:11 +0200 (EET)
Message-ID: <4CD8D559.2060608@piuha.net>
Date: Tue, 09 Nov 2010 13:00:09 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Marshall Eubanks <tme@americafree.tv>
References: <4CD8CB98.5060506@piuha.net> <8CDA2C0B-1CCA-4985-9B71-7DCDB9DF4ADC@americafree.tv>
In-Reply-To: <8CDA2C0B-1CCA-4985-9B71-7DCDB9DF4ADC@americafree.tv>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 04:59:56 -0000

I will change the 2009 date to 2010. Sorry for the typo.

Jari


From jari.arkko@piuha.net  Mon Nov  8 21:03:56 2010
Return-Path: <jari.arkko@piuha.net>
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 11AAB3A683A for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 21:03:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.535
X-Spam-Level: 
X-Spam-Status: No, score=-102.535 tagged_above=-999 required=5 tests=[AWL=0.064, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 emIblmItquFR for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 21:03:55 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 29DF23A6878 for <multimob@ietf.org>; Mon,  8 Nov 2010 21:03:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BA4372CC3C; Tue,  9 Nov 2010 07:04:17 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRk6XQpY+-nK; Tue,  9 Nov 2010 07:04:15 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 5F2782CC32; Tue,  9 Nov 2010 07:04:12 +0200 (EET)
Message-ID: <4CD8D64A.9000906@piuha.net>
Date: Tue, 09 Nov 2010 13:04:10 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: Stig Venaas <stig@venaas.com>
References: <377989.83980.qm@web111409.mail.gq1.yahoo.com> <4CD8CA75.8030501@piuha.net> <4CD8CD87.6060909@venaas.com>
In-Reply-To: <4CD8CD87.6060909@venaas.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 05:03:56 -0000

Responding to one off-line e-mail from Stig about the charter:

> I'm not so sure we need a requirements document.
>
> That is, I would like to remove
>
> Apr 2011 - Initial version of document stating requirements on PMIPv6 
> extensions for handover
> Apr 2012 - Submit requirements document to IESG for publication as 
> informational
>
> and also drop requirements from:
>
>  - Extensions to PMIPv6 for handover optimizations including context
>     transfer. A requirements document and solution document will be
>     published.

That would be fine by me. Any other thoughts?

Jari


From schmidt@informatik.haw-hamburg.de  Mon Nov  8 21:09:07 2010
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 2A4373A67F9 for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 21:09:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.249
X-Spam-Level: 
X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
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 q+EVsMsB-vDD for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 21:09:05 -0800 (PST)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id EA4733A67A6 for <multimob@ietf.org>; Mon,  8 Nov 2010 21:09:04 -0800 (PST)
Envelope-to: multimob@ietf.org
Received: from dhcp-84e4.meeting.ietf.org ([130.129.132.228]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1PFgSV-000I56-9c for multimob@ietf.org; Tue, 09 Nov 2010 06:09:27 +0100
Message-ID: <4CD8D77D.1010404@informatik.haw-hamburg.de>
Date: Tue, 09 Nov 2010 13:09:17 +0800
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: multimob@ietf.org
References: <377989.83980.qm@web111409.mail.gq1.yahoo.com>	<4CD8CA75.8030501@piuha.net> <4CD8CD87.6060909@venaas.com> <4CD8D64A.9000906@piuha.net>
In-Reply-To: <4CD8D64A.9000906@piuha.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 05:09:07 -0000

Hi,

fully agree. I don't think we need dedicated requirements documents, as 
requirements are IMHO relatively straight forward:

  1. Comply to / integrate with the unicast mobility protocol and 
general multicast routing
  2. Admit performance compatible to unicast behaviour.

Best,

Thomas

On 09.11.2010 13:04, Jari Arkko wrote:
> Responding to one off-line e-mail from Stig about the charter:
>
>> I'm not so sure we need a requirements document.
>>
>> That is, I would like to remove
>>
>> Apr 2011 - Initial version of document stating requirements on PMIPv6
>> extensions for handover
>> Apr 2012 - Submit requirements document to IESG for publication as
>> informational
>>
>> and also drop requirements from:
>>
>> - Extensions to PMIPv6 for handover optimizations including context
>> transfer. A requirements document and solution document will be
>> published.
>
> That would be fine by me. Any other thoughts?
>
> Jari
>
> _______________________________________________
> 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 JuanCarlos.Zuniga@InterDigital.com  Mon Nov  8 21:36:00 2010
Return-Path: <JuanCarlos.Zuniga@InterDigital.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 66EA23A691C for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 21:36:00 -0800 (PST)
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 SY2+KQGIDJeP for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 21:35:59 -0800 (PST)
Received: from idcout.InterDigital.com (idcexmail.interdigital.com [12.32.197.135]) by core3.amsl.com (Postfix) with ESMTP id C5CFA3A690A for <multimob@ietf.org>; Mon,  8 Nov 2010 21:35:58 -0800 (PST)
Received: from SAM.InterDigital.com ([10.30.2.11]) by idcout.InterDigital.com with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 9 Nov 2010 00:36:17 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Nov 2010 00:36:12 -0500
Message-ID: <D60519DB022FFA48974A25955FFEC08C035F8D4D@SAM.InterDigital.com>
In-Reply-To: <4CD8CB98.5060506@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [multimob] new charter
Thread-Index: Act/xlIzZRKhebu/RBCVSGz19gPObQACCu2Q
References: <4CD8CB98.5060506@piuha.net>
From: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>
To: "Jari Arkko" <jari.arkko@piuha.net>, <multimob@ietf.org>
X-OriginalArrivalTime: 09 Nov 2010 05:36:17.0449 (UTC) FILETIME=[08026190:01CB7FD0]
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 05:36:00 -0000

Hi Jari, all,

For the following milestones:

"Jun 2011 - Initial version of document on PMIPv6 direct routing
optimizations to avoid tunnel convergence problem"
and
"Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG
for publication as Internet Standard"


I think it is better to simply call it "routing optimizations", and
avoid the "local" or "direct" words. So it would read:


"Jun 2011 - Initial version of document on PMIPv6 routing optimizations
to avoid tunnel convergence problem"
and
"Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for
publication as Internet Standard"

Regards,

Juan-Carlos


> -----Original Message-----
> From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On
> Behalf Of Jari Arkko
> Sent: Monday, November 08, 2010 11:19 PM
> To: multimob@ietf.org
> Subject: [multimob] new charter
>=20
> Would this new charter be acceptable for the working group:
>=20


From sijeon79@gmail.com  Mon Nov  8 22:54:13 2010
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 E3EDC3A686A for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 22:54:13 -0800 (PST)
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 vBjb8TPc8bnH for <multimob@core3.amsl.com>; Mon,  8 Nov 2010 22:54:12 -0800 (PST)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by core3.amsl.com (Postfix) with ESMTP id CAD803A67AD for <multimob@ietf.org>; Mon,  8 Nov 2010 22:54:11 -0800 (PST)
Received: by yxp4 with SMTP id 4so4391509yxp.31 for <multimob@ietf.org>; Mon, 08 Nov 2010 22:54:35 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:reply-to:from:to:cc:subject :date:organization:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:thread-index:x-mimeole; bh=WKycidujeKSfOmxKj7UE4qt4PQBJSPqwEk2BY2GeUqw=; b=cacaeygUvgGE0X/upyHxDOzelrTxcQf0RcOUzcx2dNEDth+b0isHvaZHwgbWlmoMP9 TUDHXEw3fT5jX15wawRnS1q3cdn1uMfUM2gPaPQLke63MkaIUxiZccecUmJGN0IhZAZu H/mMYgVsQjWyQaM8zsX/0+VFxHm9xSp+XQfH8=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=reply-to:from:to:cc:subject:date:organization:message-id :mime-version:content-type:content-transfer-encoding:x-mailer :thread-index:x-mimeole; b=f8qa0rSHbVxHprGbFjqT0C5ItqsFWKGmB9U4x+G6C/lqDWRAsoOB5s3uAjhBXMnKRa HWjk4ekx8LWff3hX9zHjsJS6U0PFvPwQBRfCjiEL20S1tRShcJpY9pD+et8KUZV393eI c8I+/q+LRBUDppxjZ4qDS4A8isSlGrQan/P6A=
Received: by 10.151.41.4 with SMTP id t4mr10115147ybj.238.1289285674937; Mon, 08 Nov 2010 22:54:34 -0800 (PST)
Received: from kjwkor (dhcp-7423.meeting.ietf.org [130.129.116.35]) by mx.google.com with ESMTPS id g3sm650839yha.2.2010.11.08.22.54.30 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 08 Nov 2010 22:54:34 -0800 (PST)
From: "Seil Jeon" <sijeon79@gmail.com>
To: "'Jari Arkko'" <jari.arkko@piuha.net>
Date: Tue, 9 Nov 2010 15:54:51 +0900
Organization: dcn
Message-ID: <6D993C94A039483BB3B177FD2A8921A6@kjwkor>
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: Act/yscPwEgTbLIMQsifTobMJ3Bs/AADfUew
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5994
Cc: multimob@ietf.org
Subject: [multimob] FW:  new charter
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: sijeon79@gmail.com
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, 09 Nov 2010 06:54:14 -0000

 
Hi, Jari, 

"  Specific goals for the group are: 

  - A solution to the tunnel convergence problem by separating
    multicast routing from the Local Mobility Anchor (LMA) in
    PMIPv6. Possible techniques are using native infrastructure, using
    a dedicated LMA etc.
   ....
  The work will employ the remote
  subscription model. This is a mechanism by which a mobile node joins
  a multicast group and receives multicast data forwarded via the
  local mobility anchor."

I partially agree what schmidt said.

We are now proceeding base multicasting solution for PMIPv6.

As a next step, IMHO, enhancing performance for overall multicasting
mobility (MultiMob) needs to be covered.

On focusing the problem, direct routing solution is very good item but
mobility protocol needs to be generic.

And I'm not sure we need to stick "via the local mobility anchor".

To be honest, the local routing solution may not fit on the remote
subscription model.


Seil Jeon


-----Original Message-----
From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On
Behalf Of Thomas C. Schmidt
Sent: Tuesday, November 09, 2010 1:58 PM
To: Jari Arkko
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter

Hi Jari, hi all,

from a first look, the scope looks a bit too narrow to me ...

IMHO it's fine to start from PMIP, but there are a number of
problems/protocols that are better solved in a bit more generic way.

One obvious example is context transfer, where we believe that a rigorous
restriction to PMIP would narrow the value of an otherwise more general
approach
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-
03

... the other immediate example would be direct / optimized routing, where
the actual PMIP handover mechanisms fade to the background, and multicast
route organization towards the ARs comes into focus. Such mechanisms most
likely will not be bound to PMIP operations.

Cheers,

Thomas

On 09.11.2010 12:18, Jari Arkko wrote:
> Would this new charter be acceptable for the working group:
>
>
nov2010charternew.txt

Multicast Mobility (multimob)
-----------------------------

  Charter

  Current Status: Active

  Chairs:
      Behcet Sarikaya <sarikaya@ieee.org>
      Stig Venaas <stig@venaas.com>
      Behcet Sarikaya <bsarikaya@huawei.com>

  Internet Area Directors:
      Ralph Droms <rdroms.ietf@gmail.com>
      Jari Arkko <jari.arkko@piuha.net>

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

  Mailing Lists:
      General Discussion: multimob@ietf.org
      To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
      Archive: 
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

   The Multicast mobility (multimob) working group provides guidance
   for supporting multicast in a mobile environment. The scope of work
   will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
   listener mobility. The group will work on extensions of Proxy Mobile
   IPv6 to improve its capability to handle multicast efficiently. Work
   requiring modifications to IGMPv3/MLDv2 is out of scope in this
   stage of this working group, however, as are modifications to
   multicast routing protocols.

   Specific goals for the group are:

   - A solution to the tunnel convergence problem by separating
     multicast routing from the Local Mobility Anchor (LMA) in
     PMIPv6. Possible techniques are using native infrastructure, using
     a dedicated LMA etc.

   - Extensions to PMIPv6 for handover optimizations including context
     transfer. A requirements document and solution document will be
     published.

   - The Multimob WG will explore PMIPv6 extensions needed to support
     multicast source mobility. Both any source multicast and source
     specific multicast source mobility will be covered.

   - Document the configuration of IGMPv3/MLDv2 in mobile environments

   The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213
   does not describe how to support multicast. Some forms of multicast
   support can, however, be built in the involved nodes by using
   existing capabilities of multicast protocols and the underlying
   mobility protocols. The working group has already documented how
   existing mechanisms can be used to support multicast, without
   requiring any additions or changes to message types and parameters
   specified in RFC 5213, and assuming an unmodified mobile host. The
   current goals of the working group relate to improving the
   efficiency of this base solution. The work will employ the remote
   subscription model. This is a mechanism by which a mobile node joins
   a multicast group and receives multicast data forwarded via the
   local mobility anchor.

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

   In performing its work, the working group will work closely with
   both the mobility community (NETEXT WG) and the multicast community
   (MBONED WG). The group will consider both source specific multicast
   and any source multicast multicast models.

   Future work, subject to rechartering, may study/evaluate extensions
   to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for
mobility Apr 2011 - Initial version of document stating requirements on
PMIPv6 extensions for handover Apr 2011 - Submit a document on how to tune
IGMPv3/MLDv2 for mobility, for publication as either Informational or Best
Current Practice Jun 2011 - Initial version of document on PMIPv6 direct
routing optimizations to avoid tunnel convergence problem Nov 2011 -
Initial version of document on PMIPv6 handover optimizations Nov 2011 -
Initial version of document on PMIPv6 multicast source mobility solution
Apr 2012 - Submit requirements document to IESG for publication as
informational Jun 2012 - Submit PMIPv6 local routing optimizations document
to IESG for publication as Internet Standard Nov 2012 - Submit PMIPv6
handover optimizations document to IESG for publication as Internet
Standard Nov 2012 - Submit PMIPv6 multicast source mobility solution to
IESG for publication as Internet Standard Dec 2012 - Decision to include
additional optimization work involving extensions to IGMPv3 or MLDv2 Dec
2012 - Recharter based on the above decisions (or close the group if no new
work is needed)

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


From jari.arkko@piuha.net  Tue Nov  9 01:07:51 2010
Return-Path: <jari.arkko@piuha.net>
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 2D90728C11E for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:07:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.538
X-Spam-Level: 
X-Spam-Status: No, score=-102.538 tagged_above=-999 required=5 tests=[AWL=0.060, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 i1jMVAvMEqul for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:07:49 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 912453A6895 for <multimob@ietf.org>; Tue,  9 Nov 2010 01:07:47 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 725432CC3C for <multimob@ietf.org>; Tue,  9 Nov 2010 11:08:10 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rED7NhfGOsbJ for <multimob@ietf.org>; Tue,  9 Nov 2010 11:08:08 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 82A8A2CC32 for <multimob@ietf.org>; Tue,  9 Nov 2010 11:08:05 +0200 (EET)
Message-ID: <4CD90F73.2010008@piuha.net>
Date: Tue, 09 Nov 2010 17:08:03 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: multimob@ietf.org
References: <4CD8CB98.5060506@piuha.net>
In-Reply-To: <4CD8CB98.5060506@piuha.net>
Content-Type: multipart/mixed; boundary="------------080000010800070103090400"
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 09:07:51 -0000

This is a multi-part message in MIME format.
--------------080000010800070103090400
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

New revisions based on discussion today:



--------------080000010800070103090400
Content-Type: text/plain;
 name="nov2010charternew.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="nov2010charternew.txt"

Multicast Mobility (multimob)
-----------------------------

 Charter

 Current Status: Active

 Chairs:
     Behcet Sarikaya <sarikaya@ieee.org>
     Stig Venaas <stig@venaas.com>
     Behcet Sarikaya <bsarikaya@huawei.com>

 Internet Area Directors:
     Ralph Droms <rdroms.ietf@gmail.com>
     Jari Arkko <jari.arkko@piuha.net>

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

 Mailing Lists:
     General Discussion: multimob@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

  The Multicast mobility (multimob) working group provides guidance
  for supporting multicast in a mobile environment. The scope of work
  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
  listener mobility. The group will work on extensions of Proxy Mobile
  IPv6 to improve its capability to handle multicast efficiently. Work
  requiring modifications to IGMPv3/MLDv2 is out of scope in this
  stage of this working group, however, as are modifications to
  multicast routing protocols.

  Specific goals for the group are: 

  - A solution to the tunnel convergence problem by separating
    multicast routing from a mobility anchor. Possible techniques are
    using native infrastructure, using a dedicated mobility anchor
    etc.

  - Mechanisms to optimize multicast traffic during a handover. Such
    mechanisms may include context transfer functionality.

  - Mechanisms needed to support multicast source mobility. Both any
    source multicast and source specific multicast source mobility
    will be covered.

  - Document the configuration of IGMPv3/MLDv2 in mobile environments

  The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based
  networks when looking at the first three items. It is possible but
  not required that the solutions are applicable also for Mobile IPv6
  (MIPv6) based networks.

  For background, the PMIPv6 specification as defined in RFC 5213 does
  not describe how to support multicast. Some forms of multicast
  support can, however, be built in the involved nodes by using
  existing capabilities of multicast protocols and the underlying
  mobility protocols. The working group has already documented how
  existing mechanisms can be used to support multicast, without
  requiring any additions or changes to message types and parameters
  specified in RFC 5213, and assuming an unmodified mobile host. The
  current goals of the working group relate to improving the
  efficiency of this base solution. The work will employ the remote
  subscription model. This is a mechanism by which a mobile node joins
  a multicast group and receives multicast data forwarded via the
  local mobility anchor.

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

  In performing its work, the working group will work closely with
  both the mobility community (NETEXT WG) and the multicast community
  (MBONED WG). The group will consider both source specific multicast
  and any source multicast multicast models.

  Future work, subject to rechartering, may study/evaluate extensions
  to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice
Jun 2011 - Initial version of document on PMIPv6 direct routing optimizations to avoid tunnel convergence problem
Nov 2011 - Initial version of document on PMIPv6 handover optimizations
Nov 2011 - Initial version of document on PMIPv6 multicast source mobility solution
Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG for publication as Internet Standard
Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for publication as Internet Standard
Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for publication as Internet Standard
Dec 2012 - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2
Dec 2012 - Recharter based on the above decisions (or close the group if no new work is needed)

- remove sol = pmip extension
- allow pmip and optionally mip multicast optimization

--------------080000010800070103090400
Content-Type: text/html; charset=ISO-8859-1;
 name="nov2010charternew-from-old.diff.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="nov2010charternew-from-old.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.32: rfcdiff nov2010charterold.txt nov2010charternew.txt --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Linux dummy 2.6.31-22-generic #67-Ubuntu SMP Sat Oct 16 18:51:35 UTC 2010 x86_64 GNU/Linux --> 
<!-- Using awk: /usr/bin/gawk: GNU Awk 3.1.6 --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/bin/wdiff: GNU wdiff 0.5 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: nov2010charterold.txt - nov2010charternew.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;nov2010charterold.txt&nbsp;</th><th> </th><th>&nbsp;nov2010charternew.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l1" /><small>skipping to change at</small><em> line 27</em></th><th> </th><th><a name="part-r1" /><small>skipping to change at</small><em> line 27</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Internet Area Advisor:</td><td> </td><td class="right"> Internet Area Advisor:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td> </td><td class="right">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Mailing Lists:</td><td> </td><td class="right"> Mailing Lists:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     General Discussion: multimob@ietf.org</td><td> </td><td class="right">     General Discussion: multimob@ietf.org</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob</td><td> </td><td class="right">     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html</td><td> </td><td class="right">     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Description of Working Group:</td><td> </td><td class="right">Description of Working Group:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  The Multicast mobility (multimob) working group provides guidance for</td><td> </td><td class="rblock">  The Multicast mobility (multimob) working group provides guidance</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  supporting multicast in a mobile environment. The scope of work will</td><td> </td><td class="rblock">  for supporting multicast in a mobile environment. The scope of work</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and listener</td><td> </td><td class="rblock">  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobility. Work requiring modifications to <span class="delete">mobility protocols and</span></td><td> </td><td class="rblock">  listener mobility. <span class="insert">The group will work on extensions of Proxy Mobile</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  IGMPv3/MLDv2 is out of scope in this <span class="delete">first</span> stage of this working <span class="delete">group.</span></td><td> </td><td class="rblock"><span class="insert">  IPv6 to improve its capability to handle multicast efficiently.</span> Work</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Modifications</span> to multicast routing <span class="delete">protocols are out of scope.</span></td><td> </td><td class="rblock">  requiring modifications to IGMPv3/MLDv2 is out of scope in this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  stage of this working <span class="insert">group, however, as are modifications</span> to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  multicast routing <span class="insert">protocols.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Specific goals for the group are:</td><td> </td><td class="right">  Specific goals for the group are:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  - <span class="delete">Document how</span> multicast <span class="delete">can be supported in</span> a <span class="delete">Proxy Mobile IPv6</span></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  environment</span></td><td> </td><td class="rblock">  - <span class="insert">A solution to the tunnel convergence problem by separating</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">    multicast <span class="insert">routing from a mobility anchor. Possible techniques are</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    using native infrastructure, using a dedicated mobility anchor</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    etc.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  - Mechanisms to optimize multicast traffic during</span> a <span class="insert">handover. Such</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    mechanisms may include context transfer functionality.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  - Mechanisms needed to support multicast source mobility. Both any</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    source multicast and source specific multicast source mobility</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    will be covered.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  - Document the configuration of IGMPv3/MLDv2 in mobile environments</td><td> </td><td class="right">  - Document the configuration of IGMPv3/MLDv2 in mobile environments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213</td><td> </td><td class="rblock">  The <span class="insert">group shall primarily focus on</span> Proxy Mobile IPv6 (PMIPv6) <span class="insert">based</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  does not describe how to support multicast. Some forms of multicast</td><td> </td><td class="rblock"><span class="insert">  networks when looking at the first three items. It is possible but</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  support can, however, be built in the involved nodes by using existing</td><td> </td><td class="rblock"><span class="insert">  not required that the solutions are applicable also for Mobile IPv6</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  capabilities of multicast protocols and the underlying mobility</td><td> </td><td class="rblock"><span class="insert">  (MIPv6) based networks.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  protocols. The <span class="delete">first task of the</span> working group <span class="delete">is</span> to <span class="delete">document such</span></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  solutions for PMIPv6. This work will not require</span> any additions or</td><td> </td><td class="rblock"><span class="insert">  For background, the PMIPv6</span> specification as defined in RFC 5213 does</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  changes to message types and parameters specified in RFC 5213, and</td><td> </td><td class="rblock">  not describe how to support multicast. Some forms of multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">must assume</span> an unmodified mobile host. The work will employ the remote</td><td> </td><td class="rblock">  support can, however, be built in the involved nodes by using</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  subscription model. This is a mechanism by which a mobile node joins a</td><td> </td><td class="rblock">  existing capabilities of multicast protocols and the underlying</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  multicast group and receives multicast data forwarded via the local</td><td> </td><td class="rblock">  mobility protocols. The working group <span class="insert">has already documented how</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobility anchor.</td><td> </td><td class="rblock"><span class="insert">  existing mechanisms can be used</span> to <span class="insert">support multicast, without</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  requiring</span> any additions or changes to message types and parameters</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  specified in RFC 5213, and <span class="insert">assuming</span> an unmodified mobile host. The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  <span class="insert">current goals of the working group relate to improving the</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  efficiency of this base solution. The</span> work will employ the remote</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  subscription model. This is a mechanism by which a mobile node joins</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  a multicast group and receives multicast data forwarded via the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  local mobility anchor.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  IGMPv3/MLDv2 has been specified for wired networks with shared links.</td><td> </td><td class="right">  IGMPv3/MLDv2 has been specified for wired networks with shared links.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Mobile nodes have needs that are specific to wireless networks and</td><td> </td><td class="right">  Mobile nodes have needs that are specific to wireless networks and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  mobility (e.g. entering a dormant mode to conserve battery power,</td><td> </td><td class="right">  mobility (e.g. entering a dormant mode to conserve battery power,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  minimizing the latency for joining and leaving a group in support of</td><td> </td><td class="right">  minimizing the latency for joining and leaving a group in support of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  movement).</td><td> </td><td class="right">  movement).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">The second task of the WG is to assess existing solutions for group</span></td><td> </td><td class="rblock">  In performing its work, the working group will work closely with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  management, and determine to what extent these methods are sufficient</span></td><td> </td><td class="rblock">  both the mobility community <span class="insert">(NETEXT WG)</span> and the multicast community</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  in a mobile environment. This will include recommending appropriate</span></td><td> </td><td class="rblock">  (MBONED WG). The group will consider both source specific multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  selection of timer values and protocol parameters.</span></td><td> </td><td class="rblock">  and any source multicast multicast models.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  In performing its work, the working group will work closely with both</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  the mobility community <span class="delete">(NETLMM and NETEXT WGs)</span> and the multicast</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  community (MBONED WG). The group will consider both source specific</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  multicast and any source multicast multicast models.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Future work, subject to rechartering, may study/evaluate extensions to</td><td> </td><td class="rblock">  Future work, subject to rechartering, may study/evaluate extensions</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">support PMIPv6 optimizations to address the avalanche problem and fast</span></td><td> </td><td class="rblock">  to IGMPv3/MLDv2 to support better operation in mobile environments.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  handover and extensions to</span> IGMPv3/MLDv2 to support better operation in</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobile environments.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Goals and Milestones:</td><td> </td><td class="right">Goals and Milestones:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Nov <span class="delete">2009 - Initial version of a document explaining the use of multicast in PMIPv6</span></td><td> </td><td class="rblock">Nov <span class="insert">2010</span> - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Nov 2009</span> - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility</td><td> </td><td class="rblock">Apr <span class="insert">2011</span> - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Apr <span class="delete">2010 - Submit a document explaining the use of multicast in PMIPv6, for publication as either Informational or Best Current Practice</span></td><td> </td><td class="rblock">Jun <span class="insert">2011</span> - <span class="insert">Initial version of document on PMIPv6 direct routing optimizations to avoid tunnel convergence problem</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Apr 2010</span> - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice</td><td> </td><td class="rblock"><span class="insert">Nov 2011 - Initial version of document on PMIPv6 handover optimizations</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Jun <span class="delete">2010</span> - <span class="delete">Decision</span> to <span class="delete">include additional optimization work involving extensions</span> to PMIPv6</td><td> </td><td class="rblock"><span class="insert">Nov 2011 - Initial version of document on PMIPv6 multicast source mobility solution</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">Jun 2010</span> - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2</td><td> </td><td class="rblock"><span class="insert">Jun 2012 - Submit PMIPv6 local routing optimizations document</span> to <span class="insert">IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">Jun 2010</span> - Recharter based on the above decisions (or close the group if no new work is needed)</td><td> </td><td class="rblock"><span class="insert">Nov 2012 - Submit PMIPv6 handover optimizations document</span> to <span class="insert">IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Nov 2012 - Submit</span> PMIPv6 <span class="insert">multicast source mobility solution to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Dec 2012</span> - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Dec 2012</span> - Recharter based on the above decisions (or close the group if no new work is needed)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">- remove sol = pmip extension</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">- allow pmip and optionally mip multicast optimization</span></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 6 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>32 lines changed or deleted</i></th><th><i> </i></th><th><i>45 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.32. The latest version is available from <a href="http://www.levkowetz.com/ietf/tools/rfcdiff/" >http://www.levkowetz.com/ietf/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--------------080000010800070103090400--

From jari.arkko@piuha.net  Tue Nov  9 01:09:15 2010
Return-Path: <jari.arkko@piuha.net>
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 472463A68D2 for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:09:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.542
X-Spam-Level: 
X-Spam-Status: No, score=-102.542 tagged_above=-999 required=5 tests=[AWL=0.057, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 KieYuPxAWFZA for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:09:14 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id E5E823A68AB for <multimob@ietf.org>; Tue,  9 Nov 2010 01:09:13 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E79DF2CC3C; Tue,  9 Nov 2010 11:09:31 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nRlLzrETqC9j; Tue,  9 Nov 2010 11:09:31 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id DA1FC2CC32; Tue,  9 Nov 2010 11:09:29 +0200 (EET)
Message-ID: <4CD90FC8.5080703@piuha.net>
Date: Tue, 09 Nov 2010 17:09:28 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: "Zuniga, Juan Carlos" <JuanCarlos.Zuniga@InterDigital.com>
References: <4CD8CB98.5060506@piuha.net> <D60519DB022FFA48974A25955FFEC08C035F8D4D@SAM.InterDigital.com>
In-Reply-To: <D60519DB022FFA48974A25955FFEC08C035F8D4D@SAM.InterDigital.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 09:09:15 -0000

Yes, that makes sense. Thanks.

Jari

Zuniga, Juan Carlos kirjoitti:
> Hi Jari, all,
>
> For the following milestones:
>
> "Jun 2011 - Initial version of document on PMIPv6 direct routing
> optimizations to avoid tunnel convergence problem"
> and
> "Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG
> for publication as Internet Standard"
>
>
> I think it is better to simply call it "routing optimizations", and
> avoid the "local" or "direct" words. So it would read:
>
>
> "Jun 2011 - Initial version of document on PMIPv6 routing optimizations
> to avoid tunnel convergence problem"
> and
> "Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for
> publication as Internet Standard"
>
> Regards,
>
> Juan-Carlos
>
>
>   
>> -----Original Message-----
>> From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On
>> Behalf Of Jari Arkko
>> Sent: Monday, November 08, 2010 11:19 PM
>> To: multimob@ietf.org
>> Subject: [multimob] new charter
>>
>> Would this new charter be acceptable for the working group:
>>
>>     
>
>
>   


From jari.arkko@piuha.net  Tue Nov  9 01:10:01 2010
Return-Path: <jari.arkko@piuha.net>
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 7206A3A69B8 for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:10:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.544
X-Spam-Level: 
X-Spam-Status: No, score=-102.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 eEmrDSwVkcWr for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:10:00 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 300323A68D7 for <multimob@ietf.org>; Tue,  9 Nov 2010 01:09:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 46D562CC3C; Tue,  9 Nov 2010 11:10:22 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PoYZ6EoiMicV; Tue,  9 Nov 2010 11:10:21 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 04A232CC32; Tue,  9 Nov 2010 11:10:19 +0200 (EET)
Message-ID: <4CD90FFA.3060408@piuha.net>
Date: Tue, 09 Nov 2010 17:10:18 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: sijeon79@gmail.com
References: <6D993C94A039483BB3B177FD2A8921A6@kjwkor>
In-Reply-To: <6D993C94A039483BB3B177FD2A8921A6@kjwkor>
Content-Type: text/plain; charset=ks_c_5601-1987; format=flowed
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] FW:  new charter
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: Tue, 09 Nov 2010 09:10:01 -0000

OK

Seil Jeon kirjoitti:
>  
> Hi, Jari, 
>
> "  Specific goals for the group are: 
>
>   - A solution to the tunnel convergence problem by separating
>     multicast routing from the Local Mobility Anchor (LMA) in
>     PMIPv6. Possible techniques are using native infrastructure, using
>     a dedicated LMA etc.
>    ....
>   The work will employ the remote
>   subscription model. This is a mechanism by which a mobile node joins
>   a multicast group and receives multicast data forwarded via the
>   local mobility anchor."
>
> I partially agree what schmidt said.
>
> We are now proceeding base multicasting solution for PMIPv6.
>
> As a next step, IMHO, enhancing performance for overall multicasting
> mobility (MultiMob) needs to be covered.
>
> On focusing the problem, direct routing solution is very good item but
> mobility protocol needs to be generic.
>
> And I'm not sure we need to stick "via the local mobility anchor".
>
> To be honest, the local routing solution may not fit on the remote
> subscription model.
>
>
> Seil Jeon
>
>
> -----Original Message-----
> From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On
> Behalf Of Thomas C. Schmidt
> Sent: Tuesday, November 09, 2010 1:58 PM
> To: Jari Arkko
> Cc: multimob@ietf.org
> Subject: Re: [multimob] new charter
>
> Hi Jari, hi all,
>
> from a first look, the scope looks a bit too narrow to me ...
>
> IMHO it's fine to start from PMIP, but there are a number of
> problems/protocols that are better solved in a bit more generic way.
>
> One obvious example is context transfer, where we believe that a rigorous
> restriction to PMIP would narrow the value of an otherwise more general
> approach
> http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-
> 03
>
> ... the other immediate example would be direct / optimized routing, where
> the actual PMIP handover mechanisms fade to the background, and multicast
> route organization towards the ARs comes into focus. Such mechanisms most
> likely will not be bound to PMIP operations.
>
> Cheers,
>
> Thomas
>
> On 09.11.2010 12:18, Jari Arkko wrote:
>   
>> Would this new charter be acceptable for the working group:
>>
>>
>>     
> nov2010charternew.txt
>
> Multicast Mobility (multimob)
> -----------------------------
>
>   Charter
>
>   Current Status: Active
>
>   Chairs:
>       Behcet Sarikaya <sarikaya@ieee.org>
>       Stig Venaas <stig@venaas.com>
>       Behcet Sarikaya <bsarikaya@huawei.com>
>
>   Internet Area Directors:
>       Ralph Droms <rdroms.ietf@gmail.com>
>       Jari Arkko <jari.arkko@piuha.net>
>
>   Internet Area Advisor:
>       Jari Arkko <jari.arkko@piuha.net>
>
>   Mailing Lists:
>       General Discussion: multimob@ietf.org
>       To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
>       Archive: 
> http://www.ietf.org/mail-archive/web/multimob/current/maillist.html
>
> Description of Working Group:
>
>    The Multicast mobility (multimob) working group provides guidance
>    for supporting multicast in a mobile environment. The scope of work
>    will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
>    listener mobility. The group will work on extensions of Proxy Mobile
>    IPv6 to improve its capability to handle multicast efficiently. Work
>    requiring modifications to IGMPv3/MLDv2 is out of scope in this
>    stage of this working group, however, as are modifications to
>    multicast routing protocols.
>
>    Specific goals for the group are:
>
>    - A solution to the tunnel convergence problem by separating
>      multicast routing from the Local Mobility Anchor (LMA) in
>      PMIPv6. Possible techniques are using native infrastructure, using
>      a dedicated LMA etc.
>
>    - Extensions to PMIPv6 for handover optimizations including context
>      transfer. A requirements document and solution document will be
>      published.
>
>    - The Multimob WG will explore PMIPv6 extensions needed to support
>      multicast source mobility. Both any source multicast and source
>      specific multicast source mobility will be covered.
>
>    - Document the configuration of IGMPv3/MLDv2 in mobile environments
>
>    The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213
>    does not describe how to support multicast. Some forms of multicast
>    support can, however, be built in the involved nodes by using
>    existing capabilities of multicast protocols and the underlying
>    mobility protocols. The working group has already documented how
>    existing mechanisms can be used to support multicast, without
>    requiring any additions or changes to message types and parameters
>    specified in RFC 5213, and assuming an unmodified mobile host. The
>    current goals of the working group relate to improving the
>    efficiency of this base solution. The work will employ the remote
>    subscription model. This is a mechanism by which a mobile node joins
>    a multicast group and receives multicast data forwarded via the
>    local mobility anchor.
>
>    IGMPv3/MLDv2 has been specified for wired networks with shared links.
>    Mobile nodes have needs that are specific to wireless networks and
>    mobility (e.g. entering a dormant mode to conserve battery power,
>    minimizing the latency for joining and leaving a group in support of
>    movement).
>
>    In performing its work, the working group will work closely with
>    both the mobility community (NETEXT WG) and the multicast community
>    (MBONED WG). The group will consider both source specific multicast
>    and any source multicast multicast models.
>
>    Future work, subject to rechartering, may study/evaluate extensions
>    to IGMPv3/MLDv2 to support better operation in mobile environments.
>
>
> Goals and Milestones:
> Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for
> mobility Apr 2011 - Initial version of document stating requirements on
> PMIPv6 extensions for handover Apr 2011 - Submit a document on how to tune
> IGMPv3/MLDv2 for mobility, for publication as either Informational or Best
> Current Practice Jun 2011 - Initial version of document on PMIPv6 direct
> routing optimizations to avoid tunnel convergence problem Nov 2011 -
> Initial version of document on PMIPv6 handover optimizations Nov 2011 -
> Initial version of document on PMIPv6 multicast source mobility solution
> Apr 2012 - Submit requirements document to IESG for publication as
> informational Jun 2012 - Submit PMIPv6 local routing optimizations document
> to IESG for publication as Internet Standard Nov 2012 - Submit PMIPv6
> handover optimizations document to IESG for publication as Internet
> Standard Nov 2012 - Submit PMIPv6 multicast source mobility solution to
> IESG for publication as Internet Standard Dec 2012 - Decision to include
> additional optimization work involving extensions to IGMPv3 or MLDv2 Dec
> 2012 - Recharter based on the above decisions (or close the group if no new
> work is needed)
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob
>
>
>   


From jari.arkko@piuha.net  Tue Nov  9 01:12:49 2010
Return-Path: <jari.arkko@piuha.net>
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 032043A68AB for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:12:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.546
X-Spam-Level: 
X-Spam-Status: No, score=-102.546 tagged_above=-999 required=5 tests=[AWL=0.052, BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 SP1LgHccJSYP for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:12:43 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 0AAF73A68D7 for <multimob@ietf.org>; Tue,  9 Nov 2010 01:12:41 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 1B0FF2CC3C for <multimob@ietf.org>; Tue,  9 Nov 2010 11:13:04 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ANZdP9s2bTEn for <multimob@ietf.org>; Tue,  9 Nov 2010 11:13:02 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 43B012CC32 for <multimob@ietf.org>; Tue,  9 Nov 2010 11:13:00 +0200 (EET)
Message-ID: <4CD9109B.2060409@piuha.net>
Date: Tue, 09 Nov 2010 17:12:59 +0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: multimob@ietf.org
References: <4CD8CB98.5060506@piuha.net> <4CD90F73.2010008@piuha.net>
In-Reply-To: <4CD90F73.2010008@piuha.net>
Content-Type: multipart/mixed; boundary="------------040803050000070900080901"
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 09:12:49 -0000

This is a multi-part message in MIME format.
--------------040803050000070900080901
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

One more revision:


--------------040803050000070900080901
Content-Type: text/plain;
 name="nov2010charternew.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="nov2010charternew.txt"

Multicast Mobility (multimob)
-----------------------------

 Charter

 Current Status: Active

 Chairs:
     Behcet Sarikaya <sarikaya@ieee.org>
     Stig Venaas <stig@venaas.com>
     Behcet Sarikaya <bsarikaya@huawei.com>

 Internet Area Directors:
     Ralph Droms <rdroms.ietf@gmail.com>
     Jari Arkko <jari.arkko@piuha.net>

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

 Mailing Lists:
     General Discussion: multimob@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

  The Multicast mobility (multimob) working group provides guidance
  for supporting multicast in a mobile environment. The scope of work
  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
  listener mobility. The group will work on extensions of Proxy Mobile
  IPv6 to improve its capability to handle multicast efficiently. Work
  requiring modifications to IGMPv3/MLDv2 is out of scope in this
  stage of this working group, however, as are modifications to
  multicast routing protocols.

  Specific goals for the group are: 

  - A solution to the tunnel convergence problem by separating
    multicast routing from a mobility anchor. Possible techniques are
    using native infrastructure, using a dedicated mobility anchor
    etc.

  - Mechanisms to optimize multicast traffic during a handover. Such
    mechanisms may include context transfer functionality.

  - Mechanisms needed to support multicast source mobility. Both any
    source multicast and source specific multicast source mobility
    will be covered.

  - Document the configuration of IGMPv3/MLDv2 in mobile environments

  The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based
  networks when looking at the first three items. It is possible but
  not required that the solutions are applicable also for Mobile IPv6
  (MIPv6) based networks.

  For background, the PMIPv6 specification as defined in RFC 5213 does
  not describe how to support multicast. Some forms of multicast
  support can, however, be built in the involved nodes by using
  existing capabilities of multicast protocols and the underlying
  mobility protocols. The working group has already documented how
  existing mechanisms can be used to support multicast, without
  requiring any additions or changes to message types and parameters
  specified in RFC 5213, and assuming an unmodified mobile host. The
  current goals of the working group relate to improving the
  efficiency of this base solution.

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

  In performing its work, the working group will work closely with
  both the mobility community (NETEXT WG) and the multicast community
  (MBONED WG). The group will consider both source specific multicast
  and any source multicast multicast models.

  Future work, subject to rechartering, may study/evaluate extensions
  to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice
Jun 2011 - Initial version of document on PMIPv6 routing optimizations to avoid tunnel convergence problem
Nov 2011 - Initial version of document on PMIPv6 handover optimizations
Nov 2011 - Initial version of document on PMIPv6 multicast source mobility solution
Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for publication as Internet Standard
Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for publication as Internet Standard
Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for publication as Internet Standard
Dec 2012 - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2
Dec 2012 - Recharter based on the above decisions (or close the group if no new work is needed)

- remove sol = pmip extension
- allow pmip and optionally mip multicast optimization

--------------040803050000070900080901
Content-Type: text/html; charset=ISO-8859-1;
 name="nov2010charternew-from-old.diff.html"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="nov2010charternew-from-old.diff.html"

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 
<!-- Generated by rfcdiff 1.32: rfcdiff nov2010charterold.txt nov2010charternew.txt --> 
<!-- <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional" > -->
<!-- System: Linux dummy 2.6.31-22-generic #67-Ubuntu SMP Sat Oct 16 18:51:35 UTC 2010 x86_64 GNU/Linux --> 
<!-- Using awk: /usr/bin/gawk: GNU Awk 3.1.6 --> 
<!-- Using diff: /usr/bin/diff: diff (GNU diffutils) 2.8.1 --> 
<!-- Using wdiff: /usr/bin/wdiff: GNU wdiff 0.5 --> 
<html> 
<head> 
  <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" /> 
  <meta http-equiv="Content-Style-Type" content="text/css" /> 
  <title>Diff: nov2010charterold.txt - nov2010charternew.txt</title> 
  <style type="text/css"> 
    body    { margin: 0.4ex; margin-right: auto; } 
    tr      { } 
    td      { white-space: pre; font-family: monospace; vertical-align: top; font-size: 0.86em;} 
    th      { font-size: 0.86em; } 
    .small  { font-size: 0.6em; font-style: italic; font-family: Verdana, Helvetica, sans-serif; } 
    .left   { background-color: #EEE; } 
    .right  { background-color: #FFF; } 
    .diff   { background-color: #CCF; } 
    .lblock { background-color: #BFB; } 
    .rblock { background-color: #FF8; } 
    .insert { background-color: #8FF; } 
    .delete { background-color: #ACF; } 
    .void   { background-color: #FFB; } 
    .cont   { background-color: #EEE; } 
    .linebr { background-color: #AAA; } 
    .lineno { color: red; background-color: #FFF; font-size: 0.7em; text-align: right; padding: 0 2px; } 
    .elipsis{ background-color: #AAA; } 
    .left .cont { background-color: #DDD; } 
    .right .cont { background-color: #EEE; } 
    .lblock .cont { background-color: #9D9; } 
    .rblock .cont { background-color: #DD6; } 
    .insert .cont { background-color: #0DD; } 
    .delete .cont { background-color: #8AD; } 
    .stats, .stats td, .stats th { background-color: #EEE; padding: 2px 0; } 
  </style> 
</head> 
<body > 
  <table border="0" cellpadding="0" cellspacing="0"> 
  <tr bgcolor="orange"><th></th><th>&nbsp;nov2010charterold.txt&nbsp;</th><th> </th><th>&nbsp;nov2010charternew.txt&nbsp;</th><th></th></tr> 
      <tr><td class="lineno"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno"></td></tr>
      <tr bgcolor="gray" ><td></td><th><a name="part-l1" /><small>skipping to change at</small><em> line 27</em></th><th> </th><th><a name="part-r1" /><small>skipping to change at</small><em> line 27</em></th><td></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Internet Area Advisor:</td><td> </td><td class="right"> Internet Area Advisor:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td> </td><td class="right">     Jari Arkko &lt;jari.arkko@piuha.net&gt;</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"> Mailing Lists:</td><td> </td><td class="right"> Mailing Lists:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     General Discussion: multimob@ietf.org</td><td> </td><td class="right">     General Discussion: multimob@ietf.org</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob</td><td> </td><td class="right">     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html</td><td> </td><td class="right">     Archive:            http://www.ietf.org/mail-archive/web/multimob/current/maillist.html</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Description of Working Group:</td><td> </td><td class="right">Description of Working Group:</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0001" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  The Multicast mobility (multimob) working group provides guidance for</td><td> </td><td class="rblock">  The Multicast mobility (multimob) working group provides guidance</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  supporting multicast in a mobile environment. The scope of work will</td><td> </td><td class="rblock">  for supporting multicast in a mobile environment. The scope of work</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and listener</td><td> </td><td class="rblock">  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobility. Work requiring modifications to <span class="delete">mobility protocols and</span></td><td> </td><td class="rblock">  listener mobility. <span class="insert">The group will work on extensions of Proxy Mobile</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  IGMPv3/MLDv2 is out of scope in this <span class="delete">first</span> stage of this working <span class="delete">group.</span></td><td> </td><td class="rblock"><span class="insert">  IPv6 to improve its capability to handle multicast efficiently.</span> Work</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Modifications</span> to multicast routing <span class="delete">protocols are out of scope.</span></td><td> </td><td class="rblock">  requiring modifications to IGMPv3/MLDv2 is out of scope in this</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  stage of this working <span class="insert">group, however, as are modifications</span> to</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  multicast routing <span class="insert">protocols.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Specific goals for the group are:</td><td> </td><td class="right">  Specific goals for the group are:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0002" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  - <span class="delete">Document how</span> multicast <span class="delete">can be supported in</span> a <span class="delete">Proxy Mobile IPv6</span></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  environment</span></td><td> </td><td class="rblock">  - <span class="insert">A solution to the tunnel convergence problem by separating</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">    multicast <span class="insert">routing from a mobility anchor. Possible techniques are</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    using native infrastructure, using a dedicated mobility anchor</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    etc.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  - Mechanisms to optimize multicast traffic during</span> a <span class="insert">handover. Such</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    mechanisms may include context transfer functionality.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  - Mechanisms needed to support multicast source mobility. Both any</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    source multicast and source specific multicast source mobility</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">    will be covered.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  - Document the configuration of IGMPv3/MLDv2 in mobile environments</td><td> </td><td class="right">  - Document the configuration of IGMPv3/MLDv2 in mobile environments</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0003" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213</td><td> </td><td class="rblock">  The <span class="insert">group shall primarily focus on</span> Proxy Mobile IPv6 (PMIPv6) <span class="insert">based</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  does not describe how to support multicast. Some forms of multicast</td><td> </td><td class="rblock"><span class="insert">  networks when looking at the first three items. It is possible but</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  support can, however, be built in the involved nodes by using existing</td><td> </td><td class="rblock"><span class="insert">  not required that the solutions are applicable also for Mobile IPv6</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  capabilities of multicast protocols and the underlying mobility</td><td> </td><td class="rblock"><span class="insert">  (MIPv6) based networks.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  protocols. The <span class="delete">first task of the</span> working group <span class="delete">is</span> to <span class="delete">document such</span></td><td> </td><td class="rblock"><span class="insert"></span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  solutions for PMIPv6. This work will not require</span> any additions or</td><td> </td><td class="rblock"><span class="insert">  For background, the PMIPv6</span> specification as defined in RFC 5213 does</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  changes to message types and parameters specified in RFC 5213, and</td><td> </td><td class="rblock">  not describe how to support multicast. Some forms of multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">must assume</span> an unmodified mobile host. The <span class="delete">work will employ the remote</span></td><td> </td><td class="rblock">  support can, however, be built in the involved nodes by using</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  subscription model. This is a mechanism by which a mobile node joins a</span></td><td> </td><td class="rblock">  existing capabilities of multicast protocols and the underlying</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  multicast</span> group <span class="delete">and receives multicast data forwarded via</span> the <span class="delete">local</span></td><td> </td><td class="rblock">  mobility protocols. The working group <span class="insert">has already documented how</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  mobility anchor.</span></td><td> </td><td class="rblock"><span class="insert">  existing mechanisms can be used</span> to <span class="insert">support multicast, without</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">  requiring</span> any additions or changes to message types and parameters</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  specified in RFC 5213, and <span class="insert">assuming</span> an unmodified mobile host. The</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  <span class="insert">current goals of the working</span> group <span class="insert">relate to improving</span> the</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">  <span class="insert">efficiency of this base solution.</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  IGMPv3/MLDv2 has been specified for wired networks with shared links.</td><td> </td><td class="right">  IGMPv3/MLDv2 has been specified for wired networks with shared links.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  Mobile nodes have needs that are specific to wireless networks and</td><td> </td><td class="right">  Mobile nodes have needs that are specific to wireless networks and</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  mobility (e.g. entering a dormant mode to conserve battery power,</td><td> </td><td class="right">  mobility (e.g. entering a dormant mode to conserve battery power,</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  minimizing the latency for joining and leaving a group in support of</td><td> </td><td class="right">  minimizing the latency for joining and leaving a group in support of</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">  movement).</td><td> </td><td class="right">  movement).</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0004" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">The second task of the WG is to assess existing solutions for group</span></td><td> </td><td class="rblock">  In performing its work, the working group will work closely with</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  management, and determine to what extent these methods are sufficient</span></td><td> </td><td class="rblock">  both the mobility community <span class="insert">(NETEXT WG)</span> and the multicast community</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  in a mobile environment. This will include recommending appropriate</span></td><td> </td><td class="rblock">  (MBONED WG). The group will consider both source specific multicast</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  selection of timer values and protocol parameters.</span></td><td> </td><td class="rblock">  and any source multicast multicast models.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">                                                                         </td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  In performing its work, the working group will work closely with both</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  the mobility community <span class="delete">(NETLMM and NETEXT WGs)</span> and the multicast</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  community (MBONED WG). The group will consider both source specific</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  multicast and any source multicast multicast models.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0005" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Future work, subject to rechartering, may study/evaluate extensions to</td><td> </td><td class="rblock">  Future work, subject to rechartering, may study/evaluate extensions</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">support PMIPv6 optimizations to address the avalanche problem and fast</span></td><td> </td><td class="rblock">  to IGMPv3/MLDv2 to support better operation in mobile environments.</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  handover and extensions to</span> IGMPv3/MLDv2 to support better operation in</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  mobile environments.</td><td> </td><td class="rblock"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left"></td><td> </td><td class="right"></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="left">Goals and Milestones:</td><td> </td><td class="right">Goals and Milestones:</td><td class="lineno" valign="top"></td></tr>
      <tr><td><a name="diff0006" /></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Nov <span class="delete">2009 - Initial version of a document explaining the use of multicast in PMIPv6</span></td><td> </td><td class="rblock">Nov <span class="insert">2010</span> - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Nov 2009</span> - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility</td><td> </td><td class="rblock">Apr <span class="insert">2011</span> - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Apr <span class="delete">2010 - Submit a document explaining the use of multicast in PMIPv6, for publication as either Informational or Best Current Practice</span></td><td> </td><td class="rblock">Jun <span class="insert">2011</span> - <span class="insert">Initial version of document on PMIPv6 routing optimizations</span> to <span class="insert">avoid tunnel convergence problem</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"><span class="delete">  Apr 2010</span> - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice</td><td> </td><td class="rblock"><span class="insert">Nov 2011 - Initial version of document on PMIPv6 handover optimizations</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Jun <span class="delete">2010</span> - <span class="delete">Decision to include additional optimization work involving extensions</span> to PMIPv6</td><td> </td><td class="rblock"><span class="insert">Nov 2011 - Initial version of document on</span> PMIPv6 <span class="insert">multicast source mobility solution</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  Jun <span class="delete">2010</span> - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2</td><td> </td><td class="rblock">Jun <span class="insert">2012 - Submit PMIPv6 routing optimizations document to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock">  <span class="delete">Jun 2010</span> - Recharter based on the above decisions (or close the group if no new work is needed)</td><td> </td><td class="rblock"><span class="insert">Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for publication as Internet Standard</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Dec 2012</span> - Decision to include additional optimization work involving extensions to IGMPv3 or MLDv2</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">Dec 2012</span> - Recharter based on the above decisions (or close the group if no new work is needed)</td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock">                                                                         </td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">- remove sol = pmip extension</span></td><td class="lineno" valign="top"></td></tr>
      <tr><td class="lineno" valign="top"></td><td class="lblock"></td><td> </td><td class="rblock"><span class="insert">- allow pmip and optionally mip multicast optimization</span></td><td class="lineno" valign="top"></td></tr>

     <tr><td></td><td class="left"></td><td> </td><td class="right"></td><td></td></tr>
     <tr bgcolor="gray"><th colspan="5" align="center"><a name="end">&nbsp;End of changes. 6 change blocks.&nbsp;</a></th></tr>
     <tr class="stats"><td></td><th><i>32 lines changed or deleted</i></th><th><i> </i></th><th><i>42 lines changed or added</i></th><td></td></tr>
     <tr><td colspan="5" align="center" class="small"><br/>This html diff was produced by rfcdiff 1.32. The latest version is available from <a href="http://www.levkowetz.com/ietf/tools/rfcdiff/" >http://www.levkowetz.com/ietf/tools/rfcdiff/</a> </td></tr>
   </table>
   </body>
   </html>

--------------040803050000070900080901--

From Dirk.von-Hugo@telekom.de  Tue Nov  9 01:34:01 2010
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 411893A68FB for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level: 
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, 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 Io5ezZVgum8r for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:33:59 -0800 (PST)
Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id E48EE3A69C2 for <multimob@ietf.org>; Tue,  9 Nov 2010 01:33:58 -0800 (PST)
Received: from s4de8psaans.blf.telekom.de (HELO s4de8psaans.mitte.t-com.de) ([10.151.180.168]) by tcmail81.telekom.de with ESMTP; 09 Nov 2010 10:33:42 +0100
Received: from S4DE8PSAAQC.mitte.t-com.de ([10.151.229.14]) by s4de8psaans.mitte.t-com.de with Microsoft SMTPSVC(6.0.3790.4675);  Tue, 9 Nov 2010 10:33:41 +0100
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Tue, 9 Nov 2010 10:33:40 +0100
Message-ID: <643B0A1D1A13AB498304E0BBC802784802CB1D6D@S4DE8PSAAQC.mitte.t-com.de>
In-Reply-To: <4CD9109B.2060409@piuha.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [multimob] new charter
Thread-Index: Act/7pYfFWf0qXw+QledMnpUwJdAKQAAZ/iw
References: <4CD8CB98.5060506@piuha.net> <4CD90F73.2010008@piuha.net> <4CD9109B.2060409@piuha.net>
From: <Dirk.von-Hugo@telekom.de>
To: <jari.arkko@piuha.net>, <multimob@ietf.org>
X-OriginalArrivalTime: 09 Nov 2010 09:33:41.0569 (UTC) FILETIME=[322A9B10:01CB7FF1]
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 09:34:01 -0000

Dear Jari,=20
Fine, thanks - that leaves more space for further activities ... But =
since now source mobility is included the old introductory text seems =
outdated:

Description of Working Group:

  The Multicast mobility (multimob) working group provides guidance
  for supporting multicast in a mobile environment. The scope of work
  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
  listener mobility. The group will work on extensions of Proxy Mobile
  IPv6 to improve its capability to handle multicast efficiently. Work
  requiring modifications to IGMPv3/MLDv2 is out of scope in this
  stage of this working group, however, as are modifications to
  multicast routing protocols.

Instead we could just skip that sentence saying:

  The Multicast mobility (multimob) working group provides guidance
  for supporting multicast in a mobile environment. ...
  The group will _primarily_ work on extensions of Proxy Mobile
  IPv6 to improve its capability to handle multicast efficiently. Work
  requiring modifications to IGMPv3/MLDv2 is out of scope in this
  stage of this working group, however, as are modifications to
  multicast routing protocols.

Further improvements?

Best regards
Dirk=20
-----Urspr=FCngliche Nachricht-----
Von: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] Im =
Auftrag von Jari Arkko
Gesendet: Dienstag, 9. November 2010 10:13
An: multimob@ietf.org
Betreff: Re: [multimob] new charter

One more revision:

Multicast Mobility (multimob)
-----------------------------

 Charter

 Current Status: Active

 Chairs:
     Behcet Sarikaya <sarikaya@ieee.org>
     Stig Venaas <stig@venaas.com>
     Behcet Sarikaya <bsarikaya@huawei.com>

 Internet Area Directors:
     Ralph Droms <rdroms.ietf@gmail.com>
     Jari Arkko <jari.arkko@piuha.net>

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

 Mailing Lists:
     General Discussion: multimob@ietf.org
     To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
     Archive:            =
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

  The Multicast mobility (multimob) working group provides guidance
  for supporting multicast in a mobile environment. The scope of work
  will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
  listener mobility. The group will work on extensions of Proxy Mobile
  IPv6 to improve its capability to handle multicast efficiently. Work
  requiring modifications to IGMPv3/MLDv2 is out of scope in this
  stage of this working group, however, as are modifications to
  multicast routing protocols.

  Specific goals for the group are:=20

  - A solution to the tunnel convergence problem by separating
    multicast routing from a mobility anchor. Possible techniques are
    using native infrastructure, using a dedicated mobility anchor
    etc.

  - Mechanisms to optimize multicast traffic during a handover. Such
    mechanisms may include context transfer functionality.

  - Mechanisms needed to support multicast source mobility. Both any
    source multicast and source specific multicast source mobility
    will be covered.

  - Document the configuration of IGMPv3/MLDv2 in mobile environments

  The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based
  networks when looking at the first three items. It is possible but
  not required that the solutions are applicable also for Mobile IPv6
  (MIPv6) based networks.

  For background, the PMIPv6 specification as defined in RFC 5213 does
  not describe how to support multicast. Some forms of multicast
  support can, however, be built in the involved nodes by using
  existing capabilities of multicast protocols and the underlying
  mobility protocols. The working group has already documented how
  existing mechanisms can be used to support multicast, without
  requiring any additions or changes to message types and parameters
  specified in RFC 5213, and assuming an unmodified mobile host. The
  current goals of the working group relate to improving the
  efficiency of this base solution.

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

  In performing its work, the working group will work closely with
  both the mobility community (NETEXT WG) and the multicast community
  (MBONED WG). The group will consider both source specific multicast
  and any source multicast multicast models.

  Future work, subject to rechartering, may study/evaluate extensions
  to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for =
mobility
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, =
for publication as either Informational or Best Current Practice
Jun 2011 - Initial version of document on PMIPv6 routing optimizations =
to avoid tunnel convergence problem
Nov 2011 - Initial version of document on PMIPv6 handover optimizations
Nov 2011 - Initial version of document on PMIPv6 multicast source =
mobility solution
Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for =
publication as Internet Standard
Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for =
publication as Internet Standard
Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for =
publication as Internet Standard
Dec 2012 - Decision to include additional optimization work involving =
extensions to IGMPv3 or MLDv2
Dec 2012 - Recharter based on the above decisions (or close the group if =
no new work is needed)

- remove sol =3D pmip extension
- allow pmip and optionally mip multicast optimization

From schmidt@fhtw-berlin.de  Tue Nov  9 01:36:10 2010
Return-Path: <schmidt@fhtw-berlin.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 77BFC3A69C4 for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:36:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.337
X-Spam-Level: 
X-Spam-Status: No, score=-2.337 tagged_above=-999 required=5 tests=[AWL=-0.087, 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 wMCW1+PfMVCx for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 01:36:09 -0800 (PST)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 0B99D3A69FD for <multimob@ietf.org>; Tue,  9 Nov 2010 01:36:09 -0800 (PST)
Envelope-to: multimob@ietf.org
Received: from dhcp-4535.meeting.ietf.org ([130.129.69.53]) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.68 (FreeBSD)) (envelope-from <schmidt@fhtw-berlin.de>) id 1PFkcx-0007bN-Ty; Tue, 09 Nov 2010 10:36:32 +0100
Message-ID: <4CD91616.9040902@fhtw-berlin.de>
Date: Tue, 09 Nov 2010 17:36:22 +0800
From: "Thomas C. Schmidt" <schmidt@fhtw-berlin.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Lightning/1.0b2 Thunderbird/3.1.6
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <4CD8CB98.5060506@piuha.net> <4CD8D4E7.4030205@fhtw-berlin.de>
In-Reply-To: <4CD8D4E7.4030205@fhtw-berlin.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: multimob@ietf.org
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 09:36:10 -0000

Hi Jari, hi all,

here is a proposal for modifying the charter text:

Replace
"The scope of work will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 
protocols and listener mobility. "

by
"The scope of work will be limited to multicast optimization problems 
from Proxy Mobile IPv6 and IGMPv3/MLDv2 protocols. Proposed solutions 
must address these problems, but may be of wider applicability by 
following generic approaches."

Cheers,

Thomas

On 09.11.2010 12:58, Thomas C. Schmidt wrote:
> Hi Jari, hi all,
>
> from a first look, the scope looks a bit too narrow to me ...
>
> IMHO it's fine to start from PMIP, but there are a number of
> problems/protocols that are better solved in a bit more generic way.
>
> One obvious example is context transfer, where we believe that a
> rigorous restriction to PMIP would narrow the value of an otherwise more
> general approach
> http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-03
>
>
> ... the other immediate example would be direct / optimized routing,
> where the actual PMIP handover mechanisms fade to the background, and
> multicast route organization towards the ARs comes into focus. Such
> mechanisms most likely will not be bound to PMIP operations.
>
> Cheers,
>
> Thomas
>
> On 09.11.2010 12:18, Jari Arkko wrote:
>> Would this new charter be acceptable for the working group:
>>
>>
> nov2010charternew.txt
>
> Multicast Mobility (multimob)
> -----------------------------
>
> Charter
>
> Current Status: Active
>
> Chairs:
> Behcet Sarikaya <sarikaya@ieee.org>
> Stig Venaas <stig@venaas.com>
> Behcet Sarikaya <bsarikaya@huawei.com>
>
> Internet Area Directors:
> Ralph Droms <rdroms.ietf@gmail.com>
> Jari Arkko <jari.arkko@piuha.net>
>
> Internet Area Advisor:
> Jari Arkko <jari.arkko@piuha.net>
>
> Mailing Lists:
> General Discussion: multimob@ietf.org
> To Subscribe: https://www.ietf.org/mailman/listinfo/multimob
> Archive:
> http://www.ietf.org/mail-archive/web/multimob/current/maillist.html
>
> Description of Working Group:
>
> The Multicast mobility (multimob) working group provides guidance
> for supporting multicast in a mobile environment. The scope of work
> will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
> listener mobility. The group will work on extensions of Proxy Mobile
> IPv6 to improve its capability to handle multicast efficiently. Work
> requiring modifications to IGMPv3/MLDv2 is out of scope in this
> stage of this working group, however, as are modifications to
> multicast routing protocols.
>
> Specific goals for the group are:
>
> - A solution to the tunnel convergence problem by separating
> multicast routing from the Local Mobility Anchor (LMA) in
> PMIPv6. Possible techniques are using native infrastructure, using
> a dedicated LMA etc.
>
> - Extensions to PMIPv6 for handover optimizations including context
> transfer. A requirements document and solution document will be
> published.
>
> - The Multimob WG will explore PMIPv6 extensions needed to support
> multicast source mobility. Both any source multicast and source
> specific multicast source mobility will be covered.
>
> - Document the configuration of IGMPv3/MLDv2 in mobile environments
>
> The Proxy Mobile IPv6 (PMIPv6) specification as defined in RFC 5213
> does not describe how to support multicast. Some forms of multicast
> support can, however, be built in the involved nodes by using
> existing capabilities of multicast protocols and the underlying
> mobility protocols. The working group has already documented how
> existing mechanisms can be used to support multicast, without
> requiring any additions or changes to message types and parameters
> specified in RFC 5213, and assuming an unmodified mobile host. The
> current goals of the working group relate to improving the
> efficiency of this base solution. The work will employ the remote
> subscription model. This is a mechanism by which a mobile node joins
> a multicast group and receives multicast data forwarded via the
> local mobility anchor.
>
> IGMPv3/MLDv2 has been specified for wired networks with shared links.
> Mobile nodes have needs that are specific to wireless networks and
> mobility (e.g. entering a dormant mode to conserve battery power,
> minimizing the latency for joining and leaving a group in support of
> movement).
>
> In performing its work, the working group will work closely with
> both the mobility community (NETEXT WG) and the multicast community
> (MBONED WG). The group will consider both source specific multicast
> and any source multicast multicast models.
>
> Future work, subject to rechartering, may study/evaluate extensions
> to IGMPv3/MLDv2 to support better operation in mobile environments.
>
>
> Goals and Milestones:
> Nov 2009 - Initial version of a document on how to tune IGMPv3/MLDv2 for
> mobility
> Apr 2011 - Initial version of document stating requirements on PMIPv6
> extensions for handover
> Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility,
> for publication as either Informational or Best Current Practice
> Jun 2011 - Initial version of document on PMIPv6 direct routing
> optimizations to avoid tunnel convergence problem
> Nov 2011 - Initial version of document on PMIPv6 handover optimizations
> Nov 2011 - Initial version of document on PMIPv6 multicast source
> mobility solution
> Apr 2012 - Submit requirements document to IESG for publication as
> informational
> Jun 2012 - Submit PMIPv6 local routing optimizations document to IESG
> for publication as Internet Standard
> Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for
> publication as Internet Standard
> Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for
> publication as Internet Standard
> Dec 2012 - Decision to include additional optimization work involving
> extensions to IGMPv3 or MLDv2
> Dec 2012 - Recharter based on the above decisions (or close the group if
> no new work is needed)
>
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob

From asaeda@sfc.wide.ad.jp  Tue Nov  9 02:08:34 2010
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 8AF2C3A6987 for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 02:08:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.996
X-Spam-Level: 
X-Spam-Status: No, score=-98.996 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
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 mTo-9bDVJlqz for <multimob@core3.amsl.com>; Tue,  9 Nov 2010 02:08:26 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id 756CC28C1A6 for <multimob@ietf.org>; Tue,  9 Nov 2010 02:08:26 -0800 (PST)
Received: from localhost (dhcp-7770.meeting.ietf.org [130.129.119.112]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id CC251278199; Tue,  9 Nov 2010 19:08:45 +0900 (JST)
Date: Tue, 09 Nov 2010 18:08:41 +0800 (CST)
Message-Id: <20101109.180841.200238725.asaeda@sfc.wide.ad.jp>
To: jari.arkko@piuha.net
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <4CD9109B.2060409@piuha.net>
References: <4CD8CB98.5060506@piuha.net> <4CD90F73.2010008@piuha.net> <4CD9109B.2060409@piuha.net>
X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] new charter
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: Tue, 09 Nov 2010 10:08:35 -0000

Hi,

It seems there are several ambiguities expecially for handover.

Does this charter imply we may have two independent drafts for "PMIPv6
routing optimizations" and "handover optimizations"?
And what is handover "optimizations"?

Currently there are no multicast handover functions in PMIPv6.
Providing "smoth" handover function must be in the charter because it
is the basic requirement for PIMPv6 extension.
However, providing "fast" handover may not be necessarily included in
the initial basic extension draft as the fast handover includes the
discussion about prediction or other scenarios, which are not the
basic requirement. This would be described in the different draft
and discussed after the initial requirement is fulfilled.

According to above thoughts, I may propose to change;

From:
> Jun 2011 - Initial version of document on PMIPv6 routing
> optimizations to avoid tunnel convergence problem

To:
Jun 2011 - Initial version of document on PMIPv6 routing optimizations
to avoid tunnel convergence problem and give smooth handover including
context transfer mechanism

And, as I said above, I don't know whether fast handover should be
included in the charter "at this moment", but if you want to include
it, the statement should be changed;

From:
> Nov 2011 - Initial version of document on PMIPv6 handover optimizations

To:
Nov 2011 - Initial version of document on PMIPv6 fast handover

Regards,
--
Hitoshi Asaeda


From behcetsarikaya@yahoo.com  Mon Nov 15 14:17:21 2010
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 EA48E3A6C2F for <multimob@core3.amsl.com>; Mon, 15 Nov 2010 14:17:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.215
X-Spam-Level: 
X-Spam-Status: No, score=-0.215 tagged_above=-999 required=5 tests=[AWL=-0.216, BAYES_50=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 Ir5SvtJanP8o for <multimob@core3.amsl.com>; Mon, 15 Nov 2010 14:17:13 -0800 (PST)
Received: from nm10-vm0.bullet.mail.sp2.yahoo.com (nm10-vm0.bullet.mail.sp2.yahoo.com [98.139.91.198]) by core3.amsl.com (Postfix) with SMTP id 403993A6D4A for <multimob@ietf.org>; Mon, 15 Nov 2010 14:17:13 -0800 (PST)
Received: from [98.139.91.67] by nm10.bullet.mail.sp2.yahoo.com with NNFMP; 15 Nov 2010 22:17:52 -0000
Received: from [98.139.91.57] by tm7.bullet.mail.sp2.yahoo.com with NNFMP; 15 Nov 2010 22:17:52 -0000
Received: from [127.0.0.1] by omp1057.mail.sp2.yahoo.com with NNFMP; 15 Nov 2010 22:17:52 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 902725.16584.bm@omp1057.mail.sp2.yahoo.com
Received: (qmail 16354 invoked by uid 60001); 15 Nov 2010 22:17:52 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1289859472; bh=7Lghmb/Y3i01j60rQsKHwxoQ6sk9CIilUaA3mKFv0pA=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=XHkl7bqQwcnO5u35KG77w0ZJyTPyq6k/h8zUIX9VRWWBWKSELaEQzwnHxzasSc4ngHurFRkyLzJKBbmCpa7So/pImN6kj4vwlBAA/ZhE4HkidD5vMuRJGE9JBDVCkpbc/REU1HEBBLVW9WynMJ28zbGQ8mrHOwqjfcFGhsDIczA=
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; b=3RO/Iaz78SjvJOWZkQTSBTpgaPqnZ1FDqQ9Vo9f/sbFh+c1j1Q6DLHZuF0pAmqJ3p4r8w8W7Vn+sVKeFOTtiEYKoPdKIeaK14C6lMfHTLsEIT9nJbNdqQgVjK+lhREdTWMvVMAa/V3676n29a6WPKBWvI5zcHgZzVw3ScmmZJ7U=;
Message-ID: <372973.14802.qm@web111411.mail.gq1.yahoo.com>
X-YMail-OSG: jjsUBFUVM1k88iUqxb6gz9kAsYk7E05GOwI0RFH9JjTAgMv SuxQLayNE5KjBylEEtNivJhOGtdbXAzhV2z_b_Z_l9NSjxMSU6wg9qEmJBYP xlAv917g_U9BWxzaFyicsEKHQaKmQ6XzFvzkYOQV5g4oCxCA_a8V6u9C6mgk elyDUThgFqbZzxphEWv3os_OjglQ5rI2JBModdol7va5osKD9t4Z3BI0qit8 zIEwt3C5Q4.ilfQUXMP9oY_GFqeQEid4J_MRQlyruFlDPYjn1zFYIcgmH6OH 9M4swI0mQc26XaKhvLJoFCB5.6mBObsb5CoJji4BTO1dU6mcqLgUCVnDFWH6 QfdiiIqZSPqCtcf66nD1e74x4QJzBsH3UnpzdcF2o_sHtIR9R
Received: from [206.16.17.212] by web111411.mail.gq1.yahoo.com via HTTP; Mon, 15 Nov 2010 14:17:52 PST
X-Mailer: YahooMailRC/504.5 YahooMailWebService/0.8.107.285259
Date: Mon, 15 Nov 2010 14:17:52 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [multimob] IETF 79 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: Mon, 15 Nov 2010 22:17:21 -0000

Version 0 is posted at:

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

Thanks to Akbar for taking the minutes!


      

From helen.liu@huawei.com  Mon Nov 15 23:10:26 2010
Return-Path: <helen.liu@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 7C29B3A6DC0 for <multimob@core3.amsl.com>; Mon, 15 Nov 2010 23:10:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.273
X-Spam-Level: 
X-Spam-Status: No, score=-0.273 tagged_above=-999 required=5 tests=[AWL=0.222,  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 TWF5lhwRN99W for <multimob@core3.amsl.com>; Mon, 15 Nov 2010 23:10:24 -0800 (PST)
Received: from szxga03-in.huawei.com (unknown [119.145.14.66]) by core3.amsl.com (Postfix) with ESMTP id C2C6E3A6DC8 for <multimob@ietf.org>; Mon, 15 Nov 2010 23:09:14 -0800 (PST)
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 <0LBY00CMAUI6H9@szxga03-in.huawei.com> for multimob@ietf.org; Tue, 16 Nov 2010 15:08:30 +0800 (CST)
Received: from szxeml201-edg.china.huawei.com ([172.24.2.119]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTP id <0LBY00BCJUI6OG@szxga03-in.huawei.com> for multimob@ietf.org; Tue, 16 Nov 2010 15:08:30 +0800 (CST)
Received: from SZXEML402-HUB.china.huawei.com (10.82.67.32) by szxeml201-edg.china.huawei.com (172.24.2.39) with Microsoft SMTP Server (TLS) id 14.1.218.12; Tue, 16 Nov 2010 15:08:27 +0800
Received: from SZXEML504-MBX.china.huawei.com ([169.254.4.68]) by szxeml402-hub.china.huawei.com ([fe80::952d:2bf3:cb35:cafa%21]) with mapi id 14.01.0218.012; Tue, 16 Nov 2010 15:08:29 +0800
Date: Tue, 16 Nov 2010 07:08:28 +0000
From: Liuhui <helen.liu@huawei.com>
In-reply-to: <372973.14802.qm@web111411.mail.gq1.yahoo.com>
X-Originating-IP: [10.110.98.139]
To: Behcet Sarikaya <sarikaya@ieee.org>, "multimob@ietf.org" <multimob@ietf.org>
Message-id: <283829E9EFBF22459301B900C9A2E434EC108E@szxeml504-mbx.china.huawei.com>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-language: en-US
Content-transfer-encoding: 7BIT
Accept-Language: en-US, zh-CN
Thread-topic: [multimob] IETF 79 Minutes
Thread-index: AQHLhRL9AXzzlyfzGkmLzMatP2reW5Nzr3xA
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Subject: Re: [multimob] IETF 79 Minutes
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: Tue, 16 Nov 2010 07:10:27 -0000

Thank Akbar for the notes. I have a few amends to avoid misunderstanding: 
"All tunings require protocol changes, but some are small and some are very large. Most of the items listed on pg. 4 will only require small protocol changes but one may rquire bigger changes"
The "protocol changes" should be "router implementation changes" and "very large changes" should be expressed by "bigger changes". 
 
Besides an item of "-Possibly extended to wired network where efficiency and robustness are required" might be added.

Thanks,
Liu Hui

>-----Original Message-----
>From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On Behalf Of
>Behcet Sarikaya
>Sent: Tuesday, November 16, 2010 6:18 AM
>To: multimob@ietf.org
>Subject: [multimob] IETF 79 Minutes
>
>Version 0 is posted at:
>
>http://www.ietf.org/proceedings/79/minutes/multimob.txt
>
>Thanks to Akbar for taking the minutes!
>
>
>
>_______________________________________________
>multimob mailing list
>multimob@ietf.org
>https://www.ietf.org/mailman/listinfo/multimob

From bill@cse.concordia.ca  Mon Nov 22 10:10:37 2010
Return-Path: <bill@cse.concordia.ca>
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 A34CC3A6AE8 for <multimob@core3.amsl.com>; Mon, 22 Nov 2010 10:10:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.421
X-Spam-Level: 
X-Spam-Status: No, score=-1.421 tagged_above=-999 required=5 tests=[AWL=-0.681, BAYES_20=-0.74]
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 oS5KL827+-pa for <multimob@core3.amsl.com>; Mon, 22 Nov 2010 10:10:36 -0800 (PST)
Received: from oldperseverance.encs.concordia.ca (oldperseverance.encs.concordia.ca [132.205.96.94]) by core3.amsl.com (Postfix) with ESMTP id 2BBD928C11B for <multimob@ietf.org>; Mon, 22 Nov 2010 10:10:31 -0800 (PST)
Received: from [IPv6:::1] (bill@poise.encs.concordia.ca [132.205.2.209]) by oldperseverance.encs.concordia.ca (envelope-from bill@cse.concordia.ca) (8.13.7/8.13.7) with ESMTP id oAMIBQ11031429 for <multimob@ietf.org>; Mon, 22 Nov 2010 13:11:26 -0500
Message-ID: <4CEAB24D.9020101@cse.concordia.ca>
Date: Mon, 22 Nov 2010 13:11:25 -0500
From: Bill Atwood <bill@cse.concordia.ca>
Organization: Concordia University, Department of Computer Science and Software Engineering
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: multimob@ietf.org
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-Scanned-By: MIMEDefang 2.58 on oldperseverance.encs.concordia.ca at 2010/11/22 13:11:26 EST
Subject: [multimob] The Trickle Algorithm
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, 22 Nov 2010 18:10:38 -0000

While I have not been following the multimob work closely enough to be
sure, it seems to me that the work on the Trickle Algorithm
(draft-ietf-roll-trickle-05.txt) could be of use in a present or future
optimization of traffic that was implementing wireless multicast control
features.

  Bill
-- 

Dr. J.W. Atwood, Eng.             tel:   +1 (514) 848-2424 x3046
Distinguished Professor Emeritus  fax:   +1 (514) 848-2830
Department of Computer Science
   and Software Engineering
Concordia University EV 3.185     email: bill@cse.concordia.ca
1455 de Maisonneuve Blvd. West    http: //users.encs.concordia.ca/~bill
Montreal, Quebec Canada H3G 1M8

From wwwrun@core3.amsl.com  Tue Nov 23 09:18:05 2010
Return-Path: <wwwrun@core3.amsl.com>
X-Original-To: multimob@ietf.org
Delivered-To: multimob@core3.amsl.com
Received: by core3.amsl.com (Postfix, from userid 30) id DBA5D3A68DE; Tue, 23 Nov 2010 09:18:04 -0800 (PST)
From: IESG Secretary <iesg-secretary@ietf.org>
To: IETF Announcement list <ietf-announce@ietf.org>
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0
Message-Id: <20101123171804.DBA5D3A68DE@core3.amsl.com>
Date: Tue, 23 Nov 2010 09:18:04 -0800 (PST)
X-Mailman-Approved-At: Tue, 23 Nov 2010 11:30:22 -0800
Cc: bsarikaya@huawei.com, multimob@ietf.org
Subject: [multimob] WG Review: Recharter of Mobility Multicast (multimob)
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: iesg@ietf.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, 23 Nov 2010 17:18:05 -0000

A modified charter has been submitted for the Mobility Multicast
(multimob) working group in the Internet Area of the IETF.  The IESG has
not made any determination as yet.  The modified charter is provided below
for informational purposes only.  Please send your comments to the IESG
mailing list (iesg@ietf.org) by Tuesday, November 30, 2010.

Mobility Multicast (multimob)
-------------------------------
Current Status: Active Working Group 
Last Modified: 2010-11-09

Chairs:
    Behcet Sarikaya <sarikaya@ieee.org>
    Stig Venaas <stig@venaas.com>
    Behcet Sarikaya <bsarikaya@huawei.com>

Internet Area Directors:
    Ralph Droms <rdroms.ietf@gmail.com>
    Jari Arkko <jari.arkko@piuha.net>

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

Mailing Lists:
    General Discussion: multimob@ietf.org
    To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
    Archive:           
http://www.ietf.org/mail-archive/web/multimob/current/maillist.html

Description of Working Group:

 The Multicast mobility (multimob) working group provides guidance
 for supporting multicast in a mobile environment. The scope of work
 will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
 listener mobility. The group will work on extensions of Proxy Mobile
 IPv6 to improve its capability to handle multicast efficiently. Work
 requiring modifications to IGMPv3/MLDv2 is out of scope in this
 stage of this working group, however, as are modifications to
 multicast routing protocols.

 Specific goals for the group are: 

 - A solution to the tunnel convergence problem by separating
   multicast routing from a mobility anchor. Possible techniques are
   using native infrastructure, using a dedicated mobility anchor
   etc.

 - Mechanisms to optimize multicast traffic during a handover. Such
   mechanisms may include context transfer functionality.

 - Mechanisms needed to support multicast source mobility. Both any
   source multicast and source specific multicast source mobility
   will be covered.

 - Document the configuration of IGMPv3/MLDv2 in mobile environments

 The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based
 networks when looking at the first three items. It is possible but
 not required that the solutions are applicable also for Mobile IPv6
 (MIPv6) based networks.

 For background, the PMIPv6 specification as defined in RFC 5213 does
 not describe how to support multicast. Some forms of multicast
 support can, however, be built in the involved nodes by using
 existing capabilities of multicast protocols and the underlying
 mobility protocols. The working group has already documented how
 existing mechanisms can be used to support multicast, without
 requiring any additions or changes to message types and parameters
 specified in RFC 5213, and assuming an unmodified mobile host. The
 current goals of the working group relate to improving the
 efficiency of this base solution.

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

 In performing its work, the working group will work closely with
 both the mobility community (NETEXT WG) and the multicast community
 (MBONED WG). The group will consider both source specific multicast
 and any source multicast multicast models.

 Future work, subject to rechartering, may study/evaluate extensions
 to IGMPv3/MLDv2 to support better operation in mobile environments.


Goals and Milestones:
Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for 
           mobility
Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, 
           for publication as either Informational or Best Current 
           Practice
Jun 2011 - Initial version of document on PMIPv6 routing optimizations 
           to avoid tunnel convergence problem
Nov 2011 - Initial version of document on PMIPv6 handover optimizations
Nov 2011 - Initial version of document on PMIPv6 multicast source 
           mobility solution
Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for 
           publication as Internet Standard
Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for 
           publication as Internet Standard
Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for 
           publication as Internet Standard
Dec 2012 - Decision to include additional optimization work involving 
           extensions to IGMPv3 or MLDv2
Dec 2012 - Recharter based on the above decisions (or close the group if 
           no new work is needed)

From stig@venaas.com  Tue Nov 30 09:53:10 2010
Return-Path: <stig@venaas.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 445BB28C0E8; Tue, 30 Nov 2010 09:53:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.984
X-Spam-Level: 
X-Spam-Status: No, score=-101.984 tagged_above=-999 required=5 tests=[AWL=0.616, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 kRBAXtBNqTUR; Tue, 30 Nov 2010 09:53:09 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by core3.amsl.com (Postfix) with ESMTP id 5A83F3A6C04; Tue, 30 Nov 2010 09:53:08 -0800 (PST)
Received: from [IPv6:2001:420:4:ea0c:8d74:7d9a:5225:f101] (unknown [IPv6:2001:420:4:ea0c:8d74:7d9a:5225:f101]) by ufisa.uninett.no (Postfix) with ESMTPSA id 6E6A280D8; Tue, 30 Nov 2010 18:54:18 +0100 (CET)
Message-ID: <4CF53A48.70205@venaas.com>
Date: Tue, 30 Nov 2010 09:54:16 -0800
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.12) Gecko/20101027 Thunderbird/3.1.6
MIME-Version: 1.0
To: iesg@ietf.org
References: <20101123171804.DBA5D3A68DE@core3.amsl.com>
In-Reply-To: <20101123171804.DBA5D3A68DE@core3.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: bsarikaya@huawei.com, multimob@ietf.org
Subject: Re: [multimob] WG Review: Recharter of Mobility Multicast (multimob)
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: Tue, 30 Nov 2010 17:53:10 -0000

On 11/23/2010 9:18 AM, IESG Secretary wrote:
> A modified charter has been submitted for the Mobility Multicast
> (multimob) working group in the Internet Area of the IETF.  The IESG has
> not made any determination as yet.  The modified charter is provided below
> for informational purposes only.  Please send your comments to the IESG
> mailing list (iesg@ietf.org) by Tuesday, November 30, 2010.
>
> Mobility Multicast (multimob)
> -------------------------------
> Current Status: Active Working Group
> Last Modified: 2010-11-09
>
> Chairs:
>      Behcet Sarikaya<sarikaya@ieee.org>
>      Stig Venaas<stig@venaas.com>
>      Behcet Sarikaya<bsarikaya@huawei.com>
>
> Internet Area Directors:
>      Ralph Droms<rdroms.ietf@gmail.com>
>      Jari Arkko<jari.arkko@piuha.net>
>
> Internet Area Advisor:
>      Jari Arkko<jari.arkko@piuha.net>
>
> Mailing Lists:
>      General Discussion: multimob@ietf.org
>      To Subscribe:       https://www.ietf.org/mailman/listinfo/multimob
>      Archive:
> http://www.ietf.org/mail-archive/web/multimob/current/maillist.html
>
> Description of Working Group:
>
>   The Multicast mobility (multimob) working group provides guidance
>   for supporting multicast in a mobile environment. The scope of work
>   will be limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
>   listener mobility. The group will work on extensions of Proxy Mobile

We need to include source mobility here (since source mobility below).
Maybe say "source and listener mobility".

Stig

>   IPv6 to improve its capability to handle multicast efficiently. Work
>   requiring modifications to IGMPv3/MLDv2 is out of scope in this
>   stage of this working group, however, as are modifications to
>   multicast routing protocols.
>
>   Specific goals for the group are:
>
>   - A solution to the tunnel convergence problem by separating
>     multicast routing from a mobility anchor. Possible techniques are
>     using native infrastructure, using a dedicated mobility anchor
>     etc.
>
>   - Mechanisms to optimize multicast traffic during a handover. Such
>     mechanisms may include context transfer functionality.
>
>   - Mechanisms needed to support multicast source mobility. Both any
>     source multicast and source specific multicast source mobility
>     will be covered.
>
>   - Document the configuration of IGMPv3/MLDv2 in mobile environments
>
>   The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based
>   networks when looking at the first three items. It is possible but
>   not required that the solutions are applicable also for Mobile IPv6
>   (MIPv6) based networks.
>
>   For background, the PMIPv6 specification as defined in RFC 5213 does
>   not describe how to support multicast. Some forms of multicast
>   support can, however, be built in the involved nodes by using
>   existing capabilities of multicast protocols and the underlying
>   mobility protocols. The working group has already documented how
>   existing mechanisms can be used to support multicast, without
>   requiring any additions or changes to message types and parameters
>   specified in RFC 5213, and assuming an unmodified mobile host. The
>   current goals of the working group relate to improving the
>   efficiency of this base solution.
>
>   IGMPv3/MLDv2 has been specified for wired networks with shared links.
>   Mobile nodes have needs that are specific to wireless networks and
>   mobility (e.g. entering a dormant mode to conserve battery power,
>   minimizing the latency for joining and leaving a group in support of
>   movement).
>
>   In performing its work, the working group will work closely with
>   both the mobility community (NETEXT WG) and the multicast community
>   (MBONED WG). The group will consider both source specific multicast
>   and any source multicast multicast models.
>
>   Future work, subject to rechartering, may study/evaluate extensions
>   to IGMPv3/MLDv2 to support better operation in mobile environments.
>
>
> Goals and Milestones:
> Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for
>             mobility
> Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility,
>             for publication as either Informational or Best Current
>             Practice
> Jun 2011 - Initial version of document on PMIPv6 routing optimizations
>             to avoid tunnel convergence problem
> Nov 2011 - Initial version of document on PMIPv6 handover optimizations
> Nov 2011 - Initial version of document on PMIPv6 multicast source
>             mobility solution
> Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for
>             publication as Internet Standard
> Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for
>             publication as Internet Standard
> Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for
>             publication as Internet Standard
> Dec 2012 - Decision to include additional optimization work involving
>             extensions to IGMPv3 or MLDv2
> Dec 2012 - Recharter based on the above decisions (or close the group if
>             no new work is needed)


From behcetsarikaya@yahoo.com  Tue Nov 30 11:53:09 2010
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 3AAB33A6BDF for <multimob@core3.amsl.com>; Tue, 30 Nov 2010 11:53:09 -0800 (PST)
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 MH-iPSjI4o10 for <multimob@core3.amsl.com>; Tue, 30 Nov 2010 11:53:08 -0800 (PST)
Received: from nm12.bullet.mail.sp2.yahoo.com (nm12.bullet.mail.sp2.yahoo.com [98.139.91.82]) by core3.amsl.com (Postfix) with SMTP id 721E63A6BC7 for <multimob@ietf.org>; Tue, 30 Nov 2010 11:53:08 -0800 (PST)
Received: from [98.139.91.63] by nm12.bullet.mail.sp2.yahoo.com with NNFMP; 30 Nov 2010 19:54:18 -0000
Received: from [98.139.91.30] by tm3.bullet.mail.sp2.yahoo.com with NNFMP; 30 Nov 2010 19:54:18 -0000
Received: from [127.0.0.1] by omp1030.mail.sp2.yahoo.com with NNFMP; 30 Nov 2010 19:54:18 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 214384.49419.bm@omp1030.mail.sp2.yahoo.com
Received: (qmail 94782 invoked by uid 60001); 30 Nov 2010 19:54:18 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1291146857; bh=C7CHlTZZaMebZFE6Sqi6fA48YO3kQFjDiJ1QMjcNkDk=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=hrhJiJTguWc+GsxbN/4igejkt0ZUy/xQ3+8WQ/TpqUoE8MnGwBZj4awBU1FEN0HftXoYVk1t4ZXaz2aMxds80jykE4P8GOvNNhSIXROikTrr+jLwU0gXZmDDJMM/HdeOAwlPxTV2R3V0RkUIaUxOeUtApLjCGVvd2+hcv/Hh9hA=
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; b=GUm9F99jkHpx54racTBvZP5v/rNU/B2SDA3+LBEqGMPa00rlMXjDZ844UVCs884cD2oTwhOUJ/kgxYQTGKmFeR3j5Zi2FodT/ubJcSnnEN3l2fjSwBOpyVsfKOOBBSIwL9ImI/ZjeXi6pG7wHrwZmmdWn5WKiabSFiKg2oOGTdI=;
Message-ID: <914121.92290.qm@web111415.mail.gq1.yahoo.com>
X-YMail-OSG: ZQXDehwVM1mhQ_Ea641Wzqq.Ue0qbPfy5i3ImevIWSbrfmX x8qS588CryQMsceIS_9ugLSaQB0lWuCOL4hGnKayrSO5Hxte9Q_JaNsBrPzF U9HnG3bJTFD7nk9pM7.wZu12L8AsIHyUxYo6u5NnNfhv6euurUBCaArkP5St FIkT2sUNHc6qid8yOK5hPzFimEh_AJun.rJHRkW6MvXUXj4oWvLvdRcCN6QB Icgj.Zx_S9dHo7rogcsMReHaSOp8Iui.byHU0SP4djAnNgOdayMLPljMC5VC l9VxNa4NUWOZqnEnps216f9jKdU7GQvPZnMcZOmffLLuvOvMyobbmkQF3BvI 8H.A1Ir_ztqidAjEoM_S6LIKf0p0vFASbl5jMVqp7pNxZ
Received: from [206.16.17.212] by web111415.mail.gq1.yahoo.com via HTTP; Tue, 30 Nov 2010 11:54:17 PST
X-Mailer: YahooMailRC/553 YahooMailWebService/0.8.107.285259
References: <20101123171804.DBA5D3A68DE@core3.amsl.com> <4CF53A48.70205@venaas.com>
Date: Tue, 30 Nov 2010 11:54:17 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: Stig Venaas <stig@venaas.com>, iesg@ietf.org
In-Reply-To: <4CF53A48.70205@venaas.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: multimob@ietf.org
Subject: Re: [multimob] WG Review: Recharter of Mobility Multicast (multimob)
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, 30 Nov 2010 19:53:09 -0000

> On 11/23/2010 9:18 AM, IESG Secretary wrote:

> > A modified charter has been  submitted for the Mobility Multicast
> > (multimob) working group in the  Internet Area of the IETF.  The IESG has
> > not made any determination  as yet.  The modified charter is provided below
> > for informational  purposes only.  Please send your comments to the IESG
> > mailing list  (iesg@ietf.org) by Tuesday, November 30,  2010.
> >
> > Mobility Multicast (multimob)
 ...
> >   The scope of work
> >   will be  limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols and
> >   listener  mobility. 
> 
> We need to  include source mobility here (since source mobility below).
> Maybe say "source  and listener mobility".

Yes, please replace the above sentence with:

The scope of work will be  limited to Proxy Mobile IPv6, IGMPv3/MLDv2 protocols, 
source and listener  mobility.

Regards,

Behcet



      
