
From sarikaya2012@gmail.com  Thu Oct  4 15:23:58 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 346F221F8507 for <multimob@ietfa.amsl.com>; Thu,  4 Oct 2012 15:23:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.488
X-Spam-Level: 
X-Spam-Status: No, score=-3.488 tagged_above=-999 required=5 tests=[AWL=0.111,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UPOIm8kjmkWV for <multimob@ietfa.amsl.com>; Thu,  4 Oct 2012 15:23:57 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id AB53E21F8504 for <multimob@ietf.org>; Thu,  4 Oct 2012 15:23:57 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so2564651iec.31 for <multimob@ietf.org>; Thu, 04 Oct 2012 15:23:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=fsjyKVtOZ1OdM9gTYDDo4/v0EzSUoJQKbTsVf7G6k4U=; b=l2YIxHRmCmzevvLCFepkD9LogMovK9sxMRn3EoKw4rVo5DKECxdkCJHFfRFhEHfKbe 3O2etxMBS1JtpHp6Usbjk/igOgJeXGWKcg65PzOPU+h7dv5I0ZK0zQIgp07Ptnk/PKkj ILOsvLDXHY56v5IwDE0Hnesr04dRCu/OwiRk5Wn0IiqWYe6gGnJeabitpRcBtW1rfqd2 PhhHzZVylH8wlH1opqtRI62+nDOWbdYi3DTVqePQz8DzqhvufnraF4ltVrSfCljncHb4 hFKdUL2XIsmlMhkVjnJPcy1bTkmAvAnyU97CVgX0uXwDf279YkQCC0yO4Ks+lwaoMVaa ZOMw==
MIME-Version: 1.0
Received: by 10.50.47.129 with SMTP id d1mr17374173ign.45.1349389437217; Thu, 04 Oct 2012 15:23:57 -0700 (PDT)
Received: by 10.231.85.26 with HTTP; Thu, 4 Oct 2012 15:23:57 -0700 (PDT)
Date: Thu, 4 Oct 2012 17:23:57 -0500
Message-ID: <CAC8QAccKGhxuUs1r3EjyhdzSfE9GdTyPH+d3uKPDJsViapFyqw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: multimob@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [multimob] IETF 85 Session
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 04 Oct 2012 22:23:58 -0000

Hi all,

We have been scheduled a 2 and a half hour session as follows:
multimob Session 1 (2:30:00)
    Wednesday, Morning Session I 0900-1130
    Room Name: Room 209

of course this could change before it becomes final.

In Atlanta, we can spend some time on the handover solutions other
than the WG draft with the aim of coming to a consensus agreement on
the next steps.

Feel free to ask for slots for Atlanta session.

Regards,

Chairs

From lmcm@tid.es  Mon Oct 15 10:10:51 2012
Return-Path: <lmcm@tid.es>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7901311E80F9 for <multimob@ietfa.amsl.com>; Mon, 15 Oct 2012 10:10:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JnCuP5bpkS2i for <multimob@ietfa.amsl.com>; Mon, 15 Oct 2012 10:10:50 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 4AFEB11E80FC for <multimob@ietf.org>; Mon, 15 Oct 2012 10:10:50 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MBY00GIA2DX7K@tid.hi.inet> for multimob@ietf.org; Mon, 15 Oct 2012 19:10:48 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id D2.2E.05494.8934C705; Mon, 15 Oct 2012 19:10:48 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MBY0065F2E0FR@tid.hi.inet> for multimob@ietf.org; Mon, 15 Oct 2012 19:10:48 +0200 (MEST)
Received: from EX10-MB2-MAD.hi.inet ([169.254.2.209]) by EX10-HTCAS5-MAD.hi.inet ([::1]) with mapi id 14.02.0318.004; Mon, 15 Oct 2012 19:10:48 +0200
Date: Mon, 15 Oct 2012 17:10:48 +0000
From: LUIS MIGUEL CONTRERAS MURILLO <lmcm@tid.es>
In-reply-to: <20121015143846.31628.97254.idtracker@ietfa.amsl.com>
X-Originating-IP: [10.95.64.115]
To: "multimob@ietf.org" <multimob@ietf.org>
Message-id: <823234EF5C7C334998D973D822FF801B18EE70C1@EX10-MB2-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: es-ES
Content-transfer-encoding: base64
Accept-Language: es-ES, en-US
Thread-topic: New Version Notification for draft-contreras-multimob-multiple-upstreams-00.txt
Thread-index: AQHNquLgDUWufK3I+kqGF2hCogsmYJe6mdWQ
X-AuditID: 0a5f4e69-b7fc06d000001576-a1-507c43980328
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrMKsWRmVeSWpSXmKPExsXCFe9nqDvDuSbAoPG/usWMj30sDoweS5b8 ZApgjOKySUnNySxLLdK3S+DKuPTzBWPBJJmKE6c+szYwbpHuYuTgkBAwkZj53LWLkRPIFJO4 cG89WxcjF4eQwHZGib8//jBDOH8YJRb3zWaBcGYySpydtI0NpJtFQFXi4nwzkG42AUOJWTsn sYLYwgJxEn8OfAWzOQWcJN5f2cMGsUFB4s+5xywgtoiAtsSbl3+YQMYwC6hLtF4WBQnzCnhL rP/3iBXCFpT4MfkeC0zJlCm5IGFmAXGJOb8mskLYihLTFjUwgtiMArISK8+fZoSYHi+x9t1K ZgjbSOLLu9PsEBcISCzZc54ZwhaVePn4H9gcIQFHiTvX77NMYBSfhWTzLITNs5BsnoVk8wJG llWMYsVJRZnpGSW5iZk56QZGehmZepl5qSWbGCHxk7mDcflOlUOMAhyMSjy8Bn0VAUKsiWXF lbmHGCU5mJREefkcawKE+JLyUyozEosz4otKc1KLDzFKcDArifBmqgPleFMSK6tSi/JhUjIc HEoSvDudgFKCRanpqRVpmTnAJAGTZuLgBGnnAWovBanhLS5IzC3OTIfIn2LU5pjdPe8hI8fO nQsfMgqx5OXnpUqJ8/aClAqAlGaU5sFNe8UoDnS2MG8JSJYHmPLg5rwCWsEEtKJrdzXIipJE hJRUA+PenZynHpyM0yjWYlPNV/gsnukmOG+9CVPhirmrN326LvhKY9dOwbK2tL/XtiYnyfxI vp9/4Etzmu9iaZY47/cp06synBgYZ8hVCbbNSb+t+OLh6gNPPxy7euqoYPGpqkW/Vn2VqVWY tznr0XSGiYdt0v3W717d9aD9zswrH/Qb1zdY81kcnu+lxFKckWioxVxUnAgAqz1t0zYDAAA=
References: <20121015143846.31628.97254.idtracker@ietfa.amsl.com>
Subject: [multimob] RV: New Version Notification for	draft-contreras-multimob-multiple-upstreams-00.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Oct 2012 17:10:51 -0000

SGkgYWxsLA0KDQpXZSBoYXZlIGp1c3QgcG9zdGVkIGEgbmV3IEktRCBkZWFsaW5nIHdpdGggdGhl
IHJlcXVpcmVtZW50cyBhbmQgZnVuY3Rpb25hbCBzcGVjaWZpY2F0aW9uIG9mIHRoZSBNTEQgcHJv
eHkgd2l0aCBtdWx0aXBsZSB1cHN0cmVhbSBpbnRlcmZhY2VzLCBjb3ZlcmluZyBhIG51bWJlciBv
ZiBwb3RlbnRpYWwgc2NlbmFyaW9zIG9mIGFwcGxpY2FiaWxpdHkgd2l0aGluIE1VTFRJTU9CIHdv
cmtpbmcgZ3JvdXAuDQoNCkFzIGEgZmlyc3Qgc3RlcCB3ZSBhcmUgZm9jdXNpbmcgb24gdGhlIHJl
cXVpcmVtZW50cyB0aGF0IHRoZSBNTEQgcHJveHkgc2hvdWxkIHNhdGlzZnkuIEZ1cnRoZXIgd29y
ayB3aWxsIGJlIGZvY3VzZWQgb24gc3BlY2lmeWluZyB0aGUgcmVxdWlyZWQgZnVuY3Rpb25hbGl0
eSB0byBjb3ZlciB0aGF0IHJlcXVpcmVtZW50cy4NCg0KVGhlIGRyYWZ0IGNhbiBiZSBmb3VuZCBm
b2xsb3dpbmcgdGhpcyBsaW5rOg0KaHR0cDovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1jb250cmVy
YXMtbXVsdGltb2ItbXVsdGlwbGUtdXBzdHJlYW1zLTAwLnR4dA0KDQpDb21tZW50cyBhcmUgbW9y
ZSB0aGFuIHdlbGNvbWUNCg0KQmVzdCByZWdhcmRzLA0KDQpMdWlzDQoNCi0tLS0tTWVuc2FqZSBv
cmlnaW5hbC0tLS0tDQpEZTogaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIFttYWlsdG86aW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnXQ0KRW52aWFkbyBlbDogbHVuZXMsIDE1IGRlIG9jdHVicmUgZGUg
MjAxMiAxNjozOQ0KUGFyYTogY2piY0BpdC51YzNtLmVzDQpDQzogTFVJUyBNSUdVRUwgQ09OVFJF
UkFTIE1VUklMTE8NCkFzdW50bzogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1j
b250cmVyYXMtbXVsdGltb2ItbXVsdGlwbGUtdXBzdHJlYW1zLTAwLnR4dA0KDQoNCkEgbmV3IHZl
cnNpb24gb2YgSS1ELCBkcmFmdC1jb250cmVyYXMtbXVsdGltb2ItbXVsdGlwbGUtdXBzdHJlYW1z
LTAwLnR4dA0KaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1pdHRlZCBieSBDYXJsb3MgSi4gQmVy
bmFyZG9zIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5hbWU6ICAg
ICAgICBkcmFmdC1jb250cmVyYXMtbXVsdGltb2ItbXVsdGlwbGUtdXBzdHJlYW1zDQpSZXZpc2lv
bjogICAgICAgIDAwDQpUaXRsZTogICAgICAgICAgIEV4dGVuc2lvbiBvZiB0aGUgTUxEIHByb3h5
IGZ1bmN0aW9uYWxpdHkgdG8gc3VwcG9ydCBtdWx0aXBsZSB1cHN0cmVhbSBpbnRlcmZhY2VzDQpD
cmVhdGlvbiBkYXRlOiAgIDIwMTItMTAtMTUNCldHIElEOiAgICAgICAgICAgSW5kaXZpZHVhbCBT
dWJtaXNzaW9uDQpOdW1iZXIgb2YgcGFnZXM6IDEzDQpVUkw6ICAgICAgICAgICAgIGh0dHA6Ly93
d3cuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWNvbnRyZXJhcy1tdWx0aW1vYi1tdWx0
aXBsZS11cHN0cmVhbXMtMDAudHh0DQpTdGF0dXM6ICAgICAgICAgIGh0dHA6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtY29udHJlcmFzLW11bHRpbW9iLW11bHRpcGxlLXVwc3RyZWFt
cw0KSHRtbGl6ZWQ6ICAgICAgICBodHRwOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1jb250
cmVyYXMtbXVsdGltb2ItbXVsdGlwbGUtdXBzdHJlYW1zLTAwDQoNCg0KQWJzdHJhY3Q6DQogICBU
aGlzIGRvY3VtZW50IHByZXNlbnRzIGRpZmZlcmVudCBzY2VuYXJpb3Mgb2YgYXBwbGljYWJpbGl0
eSBmb3IgYW4NCiAgIE1MRCBwcm94eSBydW5uaW5nIG1vcmUgdGhhbiBvbmUgdXBzdHJlYW0gaW50
ZXJmYWNlLiBTaW5jZSB0aG9zZQ0KICAgc2NlbmFyaW9zIGltcG9zZSBkaWZmZXJlbnQgcmVxdWly
ZW1lbnRzIG9uIHRoZSBNTEQgcHJveHkgd2l0aA0KICAgbXVsdGlwbGUgdXBzdHJlYW0gaW50ZXJm
YWNlcywgaXQgaXMgaW1wb3J0YW50IHRvIGVuc3VyZSB0aGF0IHRoZQ0KICAgcHJveHkgZnVuY3Rp
b25hbGl0eSBhZGRyZXNzIGFsbCBvZiB0aGVtIGZvciBjb21wYXRpYmlsaXR5Lg0KDQogICBUaGUg
cHVycG9zZSBvZiB0aGlzIGRvY3VtZW50IGlzIHRvIGRlZmluZSB0aGUgcmVxdWlyZW1lbnRzIGlu
IGFuIE1MRA0KICAgcHJveHkgd2l0aCBtdWx0aXBsZSBpbnRlcmZhY2VzIGNvdmVyaW5nIGEgdmFy
aWV0eSBvZiBhcHBsaWNhYmlsaXR5DQogICBzY2VuYXJpb3MsIGFuZCB0byBzcGVjaWZ5IHRoZSBw
cm94eSBmdW5jdGlvbmFsaXR5IHRvIHNhdGlzZnkgYWxsIG9mDQogICB0aGVtLg0KDQoNCg0KDQoN
ClRoZSBJRVRGIFNlY3JldGFyaWF0DQoNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X18NCg0KRXN0ZSBtZW5zYWplIHNlIGRpcmlnZSBleGNsdXNpdmFtZW50ZSBhIHN1IGRlc3RpbmF0
YXJpby4gUHVlZGUgY29uc3VsdGFyIG51ZXN0cmEgcG9sw610aWNhIGRlIGVudsOtbyB5IHJlY2Vw
Y2nDs24gZGUgY29ycmVvIGVsZWN0csOzbmljbyBlbiBlbCBlbmxhY2Ugc2l0dWFkbyBtw6FzIGFi
YWpvLg0KVGhpcyBtZXNzYWdlIGlzIGludGVuZGVkIGV4Y2x1c2l2ZWx5IGZvciBpdHMgYWRkcmVz
c2VlLiBXZSBvbmx5IHNlbmQgYW5kIHJlY2VpdmUgZW1haWwgb24gdGhlIGJhc2lzIG9mIHRoZSB0
ZXJtcyBzZXQgb3V0IGF0Og0KaHR0cDovL3d3dy50aWQuZXMvRVMvUEFHSU5BUy9kaXNjbGFpbWVy
LmFzcHgNCg==

From prvs=6332bd18b=schmidt@informatik.haw-hamburg.de  Sat Oct 20 05:06:27 2012
Return-Path: <prvs=6332bd18b=schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8DA5D21F8551 for <multimob@ietfa.amsl.com>; Sat, 20 Oct 2012 05:06:27 -0700 (PDT)
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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1Kk8Zvs6FoPi for <multimob@ietfa.amsl.com>; Sat, 20 Oct 2012 05:06:27 -0700 (PDT)
Received: from mx3.haw-public.haw-hamburg.de (mx3.haw-public.haw-hamburg.de [141.22.6.2]) by ietfa.amsl.com (Postfix) with ESMTP id C348A21F8529 for <multimob@ietf.org>; Sat, 20 Oct 2012 05:06:26 -0700 (PDT)
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail3.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 20 Oct 2012 14:06:25 +0200
Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 94A8F105D446 for <multimob@ietf.org>; Sat, 20 Oct 2012 14:06:25 +0200 (CEST)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 29753-05 for <multimob@ietf.org>; Sat, 20 Oct 2012 14:06:25 +0200 (CEST)
Received: from [192.168.178.36] (g231111146.adsl.alicedsl.de [92.231.111.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPSA id 0073E105D43E for <multimob@ietf.org>; Sat, 20 Oct 2012 14:06:24 +0200 (CEST)
Message-ID: <508293C5.3060004@informatik.haw-hamburg.de>
Date: Sat, 20 Oct 2012 14:06:29 +0200
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121010 Thunderbird/16.0.1
MIME-Version: 1.0
To: "multimob@ietf.org" <multimob@ietf.org>
References: <20121020120401.15030.78489.idtracker@ietfa.amsl.com>
In-Reply-To: <20121020120401.15030.78489.idtracker@ietfa.amsl.com>
X-Forwarded-Message-Id: <20121020120401.15030.78489.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
Subject: [multimob] Fwd: New Version Notification for draft-schmidt-multimob-fmipv6-pfmipv6-multicast-07.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 20 Oct 2012 12:06:27 -0000

Hi all,

FYI.

Cheers,

Thomas

-------- Original Message --------
Subject: New Version Notification for 
draft-schmidt-multimob-fmipv6-pfmipv6-multicast-07.txt
Date: Sat, 20 Oct 2012 05:04:01 -0700
From: internet-drafts@ietf.org
To: schmidt@informatik.haw-hamburg.de
CC: gorry@erg.abdn.ac.uk, rkoodli@cisco.com, mw@link-lab.net


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

Filename:	 draft-schmidt-multimob-fmipv6-pfmipv6-multicast
Revision:	 07
Title:		 Multicast Listener Extensions for MIPv6 and PMIPv6 Fast Handovers
Creation date:	 2012-10-20
WG ID:		 Individual Submission
Number of pages: 27
URL: 
http://www.ietf.org/internet-drafts/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-07.txt
Status: 
http://datatracker.ietf.org/doc/draft-schmidt-multimob-fmipv6-pfmipv6-multicast
Htmlized: 
http://tools.ietf.org/html/draft-schmidt-multimob-fmipv6-pfmipv6-multicast-07
Diff: 
http://www.ietf.org/rfcdiff?url2=draft-schmidt-multimob-fmipv6-pfmipv6-multicast-07

Abstract:
    Fast handover protocols for MIPv6 and PMIPv6 define mobility
    management procedures that support unicast communication at reduced
    handover latency.  Fast handover base operations do not affect
    multicast communication, and hence do not accelerate handover
    management for native multicast listeners.  Many multicast
    applications like IPTV or conferencing, though, are comprised of
    delay-sensitive real-time traffic and will benefit from fast handover
    execution.  This document specifies extension of the Mobile IPv6 Fast
    Handovers (FMIPv6) and the Fast Handovers for Proxy Mobile IPv6
    (PFMIPv6) protocols to include multicast traffic management in fast
    handover operations.  This multicast support is provided first at the
    control plane by a management of rapid context transfer between
    access routers, second at the data plane by an optional fast traffic
    forwarding that MAY include buffering.

 



The IETF Secretariat




From lmcm@tid.es  Mon Oct 22 02:01:33 2012
Return-Path: <lmcm@tid.es>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 499E621F88F3 for <multimob@ietfa.amsl.com>; Mon, 22 Oct 2012 02:01:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=-0.001, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5b3rdiPpnEJz for <multimob@ietfa.amsl.com>; Mon, 22 Oct 2012 02:01:27 -0700 (PDT)
Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 3C02421F8870 for <multimob@ietf.org>; Mon, 22 Oct 2012 02:01:23 -0700 (PDT)
Received: from sbrightmailg02.hi.inet (Sbrightmailg02.hi.inet [10.95.78.105]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MCA00KFHEE4CB@tid.hi.inet> for multimob@ietf.org; Mon, 22 Oct 2012 11:01:21 +0200 (MEST)
Received: from vanvan (vanvan.hi.inet [10.95.78.49])	by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 5A.30.05494.06B05805; Mon, 22 Oct 2012 11:01:20 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MCA009S6EE7G5@tid.hi.inet> for multimob@ietf.org; Mon, 22 Oct 2012 11:01:20 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.178]) by ex10-htcas4-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Mon, 22 Oct 2012 11:01:15 +0200
Date: Mon, 22 Oct 2012 09:01:15 +0000
From: LUIS MIGUEL CONTRERAS MURILLO <lmcm@tid.es>
In-reply-to: <D60519DB022FFA48974A25955FFEC08C04B13D38@SAM.InterDigital.com>
X-Originating-IP: [10.95.64.115]
To: "Rahman, Akbar" <Akbar.Rahman@InterDigital.com>
Message-id: <823234EF5C7C334998D973D822FF801B1B84F739@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: multipart/alternative; boundary="Boundary_(ID_yvM3Tgs2kj6i0Au6J7qQ0Q)"
Content-language: es-ES
Accept-Language: es-ES, en-US
Thread-topic: [multimob] Volunteers to review draft-ietf-multimob-fast-handover-01
Thread-index: Ac2cJEgS6uBlH8gaSBqw89rjTInmgwUDrkbw
X-AuditID: 0a5f4e69-b7fc06d000001576-e0-50850b60eacb
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA02SbUgTYQDHfe5u2216dc6XPdoLNtIPleY0yCIiiELQYlgRmKAnu+0Ot2l3 U7RPiikhaWaJOhKWLHNiLFSc2oia9MEsDUwsMCEWlE4CJc3ZGN3tsPbt99z/7YF7cFTtlaXi rNVGc1bKrJWrMFXpZV1mWWyTPjvYr8nrXm/DzoF8pzOI6EGx6oyBNrM1NHf8bJmKWQpzVe4h pLZ5aQepB0O3kRagxCF5ArqcCwqJk+GHZbe8BahwNekBcHb2DyIdQgB+3+mRSYceABu9M6gY wch06Gh2AZHlpA7aJzpkIieQV+CXxbGIR0kWwi33CyBNpMHQrB8TOZHMhaE7jsgcSk4C2DnV FQkQZAGc3piWSRwPtx8sRwIoaYHjvT0KiTXw0c79iAeQB6BrbgZIpVfh6O9+ucQ5cHT9pVwa JqHTO4dKnARX/OFIVi1s3R3zKNpBsj1qzh41Z4+akzgLfup8KJf4KOx/HEAlzoTdYR8W/d0B FIMgmS/nWBNjs1Cs2ZSdk8WwWayVtg0D6fex4+DpxGEfIHGgjSPSOhv0ahlVw9dZfCAFR7RJ hFvRpFfvKa801DEUz5Ry1Waa9wGIo9pE4kKMoBEGqu4WzVXuSvtxXAuJ6ypBiudoE11rZM3C i9mVEVwpxuOEOC16CL6KsvCsSdLfgnT8zVrvV6DGrJVWOlVDUKKJFE1MtfVfzyrQCBdOIAyi Gic8yX8Nq0I5IpSfjG0Qy23Ufym1Hjj9jpv4sUMpIbKrscJfM5VxMH/+fEDRqjvVem3z/ec+ V29wHusaKKlYGA4Wt2dsD5IgP8P4Y/Xea8vIt7ZA4VpRWlWux7H+811e/2ZHodL4KvzrovfS vi1v3w3X6eXMxI8VRc+nC4yUqWRgb9hjcj2TPdkIjCytxDBz9sXJFS3GM5TuCMrx1F/DWjPM TwMAAA==
References: <D60519DB022FFA48974A25955FFEC08C04B13D38@SAM.InterDigital.com>
Cc: "multimob@ietf.org" <multimob@ietf.org>
Subject: Re: [multimob] Volunteers to review	draft-ietf-multimob-fast-handover-01
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 09:01:33 -0000

--Boundary_(ID_yvM3Tgs2kj6i0Au6J7qQ0Q)
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

Hi Akbar,

I'm very sorry for our late response. Thank you very much for your in-deep =
review and valuable comments. We have included the majority of them. Please=
, see in line specific answers to your comments/suggestions

Thanks again,

Luis


De: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] En nombre =
de Rahman, Akbar
Enviado el: mi=E9rcoles, 26 de septiembre de 2012 22:20
Para: sarikaya@ieee.org; multimob@ietf.org
Asunto: Re: [multimob] Volunteers to review draft-ietf-multimob-fast-handov=
er-01


Hi,





As per my action, I have reviewed draft-ietf-multimob-fast-handover-01 and =
have the following feedback to the authors:





1.  In general, the I-D is well written and in pretty good technical shape.=
  However, I had the following comments that I suggest be incorporated into=
 an update before the WGLC.



Detailed Comments:

2.  Section 1 (Introduction)

o    I find the last paragraph in this section ("The solution described in =
this document ...") to be ambiguous and hard to "prove".  How can you reall=
y demonstrate that the approach can be applied to "possible architectural e=
volutions"?  I would suggest removing this type of claim unless you can be =
more specific.

[Luis>>] This paragraph was written having in mind the architectural evolut=
ions described in [I-D.ietf-multimob-pmipv6-ropt]. As this proposal is an a=
dd-on to the set of PMIPv6 protocols, and there is no compatibility issues =
identified with the solutions in [I-D.ietf-multimob-pmipv6-ropt], we think =
that this statement remains valid at least for the mentioned architectural =
evolutions. According to your suggestion we propose to modify the text in t=
he following way: "The solution described in this document can be also appl=
ied to the solutions described in [I-D.ietf-multimob-pmipv6-ropt]".

o    The above comment also applies to the similar statement in the abstrac=
t, and section 6.

[Luis>>] Similar change applies to section 6. For the abstract we modify th=
e text in the following way: "These extensions are not only applicable to t=
he base solution for multicast support in

Proxy Mobile IPv6, but they can also be applied to other solutions being de=
veloped to avoid the tunnel convergence problem."

o    In paragraph 3, should it be "active multicast content delivery" inste=
ad of "active multicast subscription"?

[Luis>>] The sentence "active multicast subscription" appears twice in the =
paragraph, but our understanding is that in both cases it is the most appro=
priate concept. By now we have not changed it, but, please provide addition=
al comments on this if you feel it is necessary to change that.

o    In paragraph 4, I was not really sure if the base [RFC5949] can perfor=
m the mechanism or not?  (I.E. Does it necessarily require modifications to=
 [RFC5949] to perform the mechanism?)

[Luis>>] We propose to change the wording, by using "could potentially be a=
ccomplished by using some adaptation of [RFC5949] to multicast traffic" ins=
tead of "can be accomplished by using [RFC5949] or some evolution of it "



3.  Section 2 (Terminology)

o    The description of "Proactive handover" is confusing ("... the MN de-r=
egistration from the pMAG previously to receive the MN registration from th=
e nMAG").

[Luis>>] As per your comment, we propose the following definition: "A proac=
tive handover is a handover event where the MN is firstly de-registered on =
the LMA by the pMAG, and later on it is registered by the nMAG as consequen=
ce of changing the point of attachment."



4.  Section 3 (Overview)

o    It would help a lot for readability (and understandability) to have a =
high level architecture picture in this section.  Something along the lines=
 of Figure 1 of RFC 6224 would be an obvious starting point.

[Luis>>] Done. We have included a high level figure showing the main idea o=
f the solution.

o    The 2nd paragraph stresses that subscription info for an MN to the LMA=
 is only updated after a handover event.  This may be true, but later secti=
ons (e.g. Fig. 1) do specify other new info being exchanged without a hando=
ver event.  So this should also be mentioned for balance.

[Luis>>] Agree. According to your suggestion we propose to include the foll=
owing text: "However it should be noted that some signaling is needed to di=
fferentiate what MNs are maintaining active subscriptions in order to restr=
ict the optimization procedure to them in case of handover."



5.  Section 4.2.1.1.2 (De-registration process)

o    In the S=3D1 description, it refers to the "IP addresses of the subscr=
ibed group and the source providing it".  I interpret the "source" to be re=
ferring to the Source-Specific Multicast (SSM) of [RFC4604].  But I underst=
and that an MN can also do a non SSM Join (i.e. indicate only the subscribe=
d group IP address and no source).  Is this supported in the draft?  (This =
comment applies to many places in the document).

[Luis>>] Certainly, it seems more appropriate to refer to the "multicast co=
ntext" or "multicast status information" rather than "IP addresses of the s=
ubscribed group and the source providing it". This last sentence is out-of-=
date once we have introduced in version -01 the new format for the Active M=
ulticast Subscription mobility option (in section 4.1.1.2) including the Mu=
lticast Address record inherited from RFC3810, as suggested by Hitoshi Asae=
da in a previous review of the document. So, I agree we have to re-write th=
ese kind of sentences in the sense I mention at the beginning. We have upda=
ted the document accordingly.



6.  Section 5.1.1 (Multicast Activity set to ON)

o    In Figure 1 and the corresponding text it indicates that the "Act Ind(=
start)" for the particular MN is sent by the MAG to the LMA as soon as the =
MLD Report is sent.  I understand that this message will be sent for each s=
imilar MN that attaches to the MAG (along with a corresponding ACK).  What =
are the signaling load implications for this between the MAG and the LMA?

[Luis>>] This signaling message is used to allow the LMA to distinguish amo=
ng MNs with on-going multicast subscription, and MN without active multicas=
t status. This differentiation further allows to apply the optimization pro=
cedure only to those MNs with active multicast subscription (no actions are=
 taken for MN without active multicast subscription). The signaling load of=
 the multicast activity represents one message (and the corresponding ack) =
once the MN firstly subscribes to a multicast group, and another message (a=
nd the corresponding ack) when the MN terminates the multicast subscription=
 at all. So, it can be seen as two pair of messages for the duration of the=
 multicast session. This mechanism is intended to avoid the unnecessary app=
lication of this optimization procedure for MNs not having an active multic=
ast subscription during a handover event, then preventing the LMA and the M=
AGs to implement unnecessary actions in case of no active multicast session=
 during handover. In order to clarify this we have included the motivation =
of this signaling in the document in section 5.1.

o    (My understanding is that in Fig. 1 the flag "A=3D1" is sent in a PBU =
which normally would not have been sent at this point for unicast.  Please =
correct me if I am wrong).

[Luis>>] Not actually. We define specific purpose messages for this in sect=
ions 4.3.2.1 and 4.3.2.2. Using the regular PBU/BPA signaling exchange coul=
d have been adopted instead, but in our opinion the use of specific purpose=
 messages represents a more lightweight method for signaling this issue.



7.  Section 7 (Benefits of layer-2 triggers for fast handover)

o    It was unclear what the main point of this section is (i.e. what is th=
e standards text)?  I especially found the last sentence confusing ("... an=
d that not all the multicast applications could take benefit of it, that fu=
nctionality could be seen as optional for multicast handover optimization."=
)

[Luis>>] We agree on removing this section.



8.  Section 8 (Security Considerations)

o    You obviously need to complete this section before WGLC.

[Luis>>] Agree. We have completed this section.



9.  Section 10 (Contributors)

o    Somehow the phrase ".. has largely contributed.." does not read well (=
perhaps just change "largely" to "extensively").

[Luis>>] Done.



10.General: I recall that the authors mentioned that they would do some sim=
ulations to prove the benefit of this approach vs the baseline [RFC6224] ap=
proach.  I think that will be very useful so that the WG can trade the comp=
lexity vs. performance benefits of this approach.  I did in general find th=
e complexity of even understanding all the different options (reactive vs. =
proactive, Flag setting, prevention of unicast traffic delays, etc.) to be =
a bit daunting.  I had to go back to your PPT presentations from the IETF m=
eetings to piece everything together (as those slides nicely captured the h=
igh level flow).  If we had the simulations then we could justify all the c=
omplexity.  Or even better perhaps support fewer options that give the majo=
rity of the benefits?  This to me is a key open issue.

[Luis>>] For the sake of simplicity we have included a performance comparis=
on analysis between this proposal and the base protocol focusing on the del=
ay reduction that this method achieves.





That's all.





/Akbar



-----Original Message-----
From: multimob-bounces@ietf.org<mailto:multimob-bounces@ietf.org> [mailto:m=
ultimob-bounces@ietf.org] On Behalf Of Behcet Sarikaya
Sent: Tuesday, September 25, 2012 4:38 PM
To: multimob@ietf.org<mailto:multimob@ietf.org>
Subject: [multimob] Volunteers to review draft-ietf-multimob-fast-handover-=
01



Hi all,



In IETF84, three people volunteered to review

draft-ietf-multimob-fast-handover-01,



Thomas, Akbar and Costas.



The volunteers, thanks for volunteering and please post your reviews

on the list soon.



Regards,



Behcet

_______________________________________________

multimob mailing list

multimob@ietf.org<mailto:multimob@ietf.org>

https://www.ietf.org/mailman/listinfo/multimob


________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx

--Boundary_(ID_yvM3Tgs2kj6i0Au6J7qQ0Q)
Content-type: text/html; charset=iso-8859-1
Content-transfer-encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<style>
<!--
@font-face
	{font-family:Calibri}
@font-face
	{font-family:Tahoma}
@font-face
	{font-family:Consolas}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:Consolas}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:8.0pt;
	font-family:"Tahoma","sans-serif"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.TextosinformatoCar
	{font-family:Consolas}
span.TextodegloboCar
	{font-family:"Tahoma","sans-serif"}
p.PlainText, li.PlainText, div.PlainText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.PlainTextChar
	{font-family:Consolas}
p.BalloonText, li.BalloonText, div.BalloonText
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif"}
span.BalloonTextChar
	{font-family:"Tahoma","sans-serif"}
span.EstiloCorreo26
	{font-family:"Calibri","sans-serif";
	color:windowtext}
span.EstiloCorreo27
	{font-family:"Calibri","sans-serif";
	color:#1F497D}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:72.0pt 72.0pt 72.0pt 72.0pt}
div.WordSection1
	{}
ol
	{margin-bottom:0cm}
ul
	{margin-bottom:0cm}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi Akbar,</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">I&#8217;m very sorry f=
or our late response. Thank you very much for your in-deep review and valua=
ble comments. We have included the majority of them. Please, see in line sp=
ecific answers to your comments/suggestions</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Thanks again,</span></=
p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Luis</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">&nbsp;</span></p>
<div>
<div style=3D"border:none; border-top:solid #B5C4DF 1.0pt; padding:3.0pt 0c=
m 0cm 0cm">
<p class=3D"MsoNormal"><b><span lang=3D"ES" style=3D"font-size:10.0pt; font=
-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;">De:</span></b><span lang=
=3D"ES" style=3D"font-size:10.0pt; font-family:&quot;Tahoma&quot;,&quot;san=
s-serif&quot;"> multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org=
]
<b>En nombre de </b>Rahman, Akbar<br>
<b>Enviado el:</b> mi=E9rcoles, 26 de septiembre de 2012 22:20<br>
<b>Para:</b> sarikaya@ieee.org; multimob@ietf.org<br>
<b>Asunto:</b> Re: [multimob] Volunteers to review draft-ietf-multimob-fast=
-handover-01</span></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoPlainText">Hi,</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">As per my action, I have reviewed draft-ietf-mult=
imob-fast-handover-01 and have the following feedback to the authors:</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">1.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>In general, the I-D is well written and in pretty good techni=
cal shape.&nbsp; However, I had the following comments that I suggest be in=
corporated into an update before the WGLC.</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:18.0pt"><u>Detailed Comments=
:</u></p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">2.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 1 (Introduction)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>I find the last paragraph in this section (&#8220;The =
solution described in this document &#8230;&#8221;) to be ambiguous and har=
d to &#8220;prove&#8221;.&nbsp; How can you really demonstrate that the app=
roach can be applied to &#8220;possible architectural evolutions&#8221;?&nb=
sp; I would
 suggest removing this type of claim unless you can be more specific.</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">This paragraph was writte=
n having in mind the architectural evolutions described in [I-D.ietf-multim=
ob-pmipv6-ropt]. As this proposal is an add-on to the
 set of PMIPv6 protocols, and there is no compatibility issues identified w=
ith the solutions in [I-D.ietf-multimob-pmipv6-ropt], we think that this st=
atement remains valid at least for the mentioned architectural evolutions. =
According to your suggestion we
 propose to modify the text in the following way: &#8220;The solution descr=
ibed in this document can be also applied to the solutions described in [I-=
D.ietf-multimob-pmipv6-ropt]&#8221;.</span></i></b><span style=3D"font-size=
:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F4=
97D"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>The above comment also applies to the similar statemen=
t in the abstract, and section 6.</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Similar change applies to=
 section 6. For the abstract we modify the text in the following way: &#822=
1;These extensions are not only applicable to the base solution
 for multicast support in</span></i></b></p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Proxy Mobile I=
Pv6, but they can also be applied to other solutions being developed to avo=
id the tunnel convergence problem.&#8221;</span></i></b><span style=3D"font=
-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color=
:#1F497D"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>In paragraph 3, should it be &#8220;active multicast c=
ontent delivery&#8221; instead of &#8220;active multicast subscription&#822=
1;?</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">The sentence &#8220;activ=
e multicast subscription&#8221; appears twice in the paragraph, but our und=
erstanding is that in both cases it is the most appropriate concept.
 By now we have not changed it, but, please provide additional comments on =
this if you feel it is necessary to change that.</span></i></b><span style=
=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot=
;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>In paragraph 4, I was not really sure if the base [RFC=
5949] can perform the mechanism or not?&nbsp; (I.E. Does it necessarily req=
uire modifications to [RFC5949] to perform the mechanism?)</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">We propose to change the =
wording, by using &#8220;could potentially be accomplished by using some ad=
aptation of [RFC5949] to multicast traffic&#8221; instead of &#8220;can
 be accomplished by using [RFC5949] or</span></i></b> <b><i><span style=3D"=
font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; c=
olor:#1F497D">some evolution of it &#8221;</span></i></b><span style=3D"fon=
t-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; colo=
r:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">3.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 2 (Terminology)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>The description of &#8220;Proactive handover&#8221; is=
 confusing (&#8220;&#8230; the MN de-registration from the pMAG previously =
to receive the MN registration from the nMAG&#8221;).</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">As per your comment, we p=
ropose the following definition: &#8221;A proactive handover is a handover =
event where the MN is firstly de-registered on the LMA by the
 pMAG, and later on it is registered by the nMAG as consequence of changing=
 the point of attachment.&#8221;</span></i></b><span style=3D"font-size:11.=
0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"=
></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">4.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 3 (Overview)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>It would help a lot for readability (and understandabi=
lity) to have a high level architecture picture in this section.&nbsp; Some=
thing along the lines of Figure 1 of RFC 6224 would be an obvious starting =
point.</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Done. We have included a =
high level figure showing the main idea of the solution.</span></i></b><spa=
n style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-ser=
if&quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>The 2<sup>nd</sup> paragraph stresses that subscriptio=
n info for an MN to the LMA is only updated after a handover event.&nbsp; T=
his may be true, but later sections (e.g. Fig. 1) do specify other new info=
 being exchanged without a handover event.&nbsp;
 So this should also be mentioned for balance.</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Agree. According to your =
suggestion we propose to include the following text: &#8221;However it shou=
ld be noted that some signaling is needed to differentiate what
 MNs are maintaining active subscriptions in order to restrict the optimiza=
tion procedure to them in case of handover.&#8221;</span></i></b><span styl=
e=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&quo=
t;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">5.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 4.2.1.1.2 (De-registration process)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>In the S=3D1 description, it refers to the &#8220;IP a=
ddresses of the subscribed group and the source providing it&#8221;.&nbsp; =
I interpret the &#8220;source&#8221; to be referring to the Source-Specific=
 Multicast (SSM) of [RFC4604].&nbsp; But I understand that an MN can
 also do a non SSM Join (i.e. indicate only the subscribed group IP address=
 and no source).&nbsp; Is this supported in the draft?&nbsp; (This comment =
applies to many places in the document).</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Certainly, it seems more =
appropriate to refer to the &#8220;multicast context&#8221; or &#8220;multi=
cast status information&#8221; rather than &#8220;IP addresses of the subsc=
ribed group
 and the source providing it&#8221;. This last sentence is out-of-date once=
 we have introduced in version -01 the new format for the Active Multicast =
Subscription mobility option (in section 4.1.1.2) including the Multicast A=
ddress record inherited from RFC3810,
 as suggested by Hitoshi Asaeda in a previous review of the document. So, I=
 agree we have to re-write these kind of sentences in the sense I mention a=
t the beginning. We have updated the document accordingly.</span></i></b><s=
pan style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-s=
erif&quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">6.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 5.1.1 (Multicast Activity set to ON)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>In Figure 1 and the corresponding text it indicates th=
at the &#8220;Act Ind(start)&#8221; for the particular MN is sent by the MA=
G to the LMA as soon as the MLD Report is sent.&nbsp; I understand that thi=
s message will be sent for each similar MN that attaches
 to the MAG (along with a corresponding ACK).&nbsp; What are the signaling =
load implications for this between the MAG and the LMA?
</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">This signaling message is=
 used to allow the LMA to distinguish among MNs with on-going multicast sub=
scription, and MN without active multicast status. This
 differentiation further allows to apply the optimization procedure only to=
 those MNs with active multicast subscription (no actions are taken for MN =
without active multicast subscription). The signaling load of the multicast=
 activity represents one message
 (and the corresponding ack) once the MN firstly subscribes to a multicast =
group, and another message (and the corresponding ack) when the MN terminat=
es the multicast subscription at all. So, it can be seen as two pair of mes=
sages for the duration of the multicast
 session. This mechanism is intended to avoid the unnecessary application o=
f this optimization procedure for MNs not having an active multicast subscr=
iption during a handover event, then preventing the LMA and the MAGs to imp=
lement unnecessary actions in case
 of no active multicast session during handover. In order to clarify this w=
e have included the motivation of this signaling in the document in section=
 5.1.</span></i></b><span style=3D"font-size:11.0pt; font-family:&quot;Cali=
bri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>(My understanding is that in Fig. 1 the flag &#8220;A=
=3D1&#8221; is sent in a PBU which normally would not have been sent at thi=
s point for unicast.&nbsp; Please correct me if I am wrong).</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Not actually. We define s=
pecific purpose messages for this in sections 4.3.2.1 and 4.3.2.2. Using th=
e regular PBU/BPA signaling exchange could have been adopted
 instead, but in our opinion the use of specific purpose messages represent=
s a more lightweight method for signaling this issue.</span></i></b><span s=
tyle=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-serif&=
quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">7.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 7 (Benefits of layer-2 triggers for fast handover)</p=
>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>It was unclear what the main point of this section is =
(i.e. what is the standards text)?&nbsp; I especially found the last senten=
ce confusing (&#8220;&#8230; and that not all the multicast applications co=
uld take benefit of it, that functionality could
 be seen as optional for multicast handover optimization.&#8221;)</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">We agree on removing this=
 section.</span></i></b><span style=3D"font-size:11.0pt; font-family:&quot;=
Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">8.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 8 (Security Considerations)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>You obviously need to complete this section before WGL=
C.</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Agree. We have completed =
this section.</span></i></b><span style=3D"font-size:11.0pt; font-family:&q=
uot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">9.<span style=3D"font:7.0pt &quot;Times New Roman&quot;">=
&nbsp;
</span></span>Section 10 (Contributors)</p>
<p class=3D"MsoPlainText" style=3D"margin-left:72.0pt; text-indent:-18.0pt"=
><span style=3D"font-family:&quot;Courier New&quot;,&quot;serif&quot;"><spa=
n style=3D"">o<span style=3D"font:7.0pt &quot;Times New Roman&quot;">&nbsp;=
&nbsp;&nbsp;
</span></span></span>Somehow the phrase &#8220;.. has largely contributed..=
&#8221; does not read well (perhaps just change &#8220;largely&#8221; to &#=
8220;extensively&#8221;).</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">Done.</span></i></b><span=
 style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot;,&quot;sans-seri=
f&quot;; color:#1F497D"></span></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText" style=3D"margin-left:36.0pt; text-indent:-18.0pt"=
><span style=3D"">10.</span>General: I recall that the authors mentioned th=
at they would do some simulations to prove the benefit of this approach vs =
the baseline [RFC6224] approach.&nbsp; I think
 that will be very useful so that the WG can trade the complexity vs. perfo=
rmance benefits of this approach.&nbsp; I did in general find the complexit=
y of even understanding all the different options (reactive vs. proactive, =
Flag setting, prevention of unicast traffic
 delays, etc.) to be a bit daunting.&nbsp; I had to go back to your PPT pre=
sentations from the IETF meetings to piece everything together (as those sl=
ides nicely captured the high level flow).&nbsp; If we had the simulations =
then we could justify all the complexity.&nbsp;
 Or even better perhaps support fewer options that give the majority of the=
 benefits?&nbsp; This to me is a key open issue.</p>
<p class=3D"MsoPlainText"><b><i><span style=3D"font-size:11.0pt; font-famil=
y:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D">[Luis&gt;&gt;]
</span></i></b><b><i><span style=3D"font-size:11.0pt; font-family:&quot;Cal=
ibri&quot;,&quot;sans-serif&quot;; color:#1F497D">For the sake of simplicit=
y we have included a performance comparison analysis between this proposal =
and the base protocol focusing on the delay reduction
 that this method achieves.</span></i></b><span style=3D"font-size:11.0pt; =
font-family:&quot;Calibri&quot;,&quot;sans-serif&quot;; color:#1F497D"></sp=
an></p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">That&#8217;s all.</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">/Akbar</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">-----Original Message-----<br>
From: <a href=3D"mailto:multimob-bounces@ietf.org">multimob-bounces@ietf.or=
g</a> [<a href=3D"mailto:multimob-bounces@ietf.org">mailto:multimob-bounces=
@ietf.org</a>] On Behalf Of Behcet Sarikaya<br>
Sent: Tuesday, September 25, 2012 4:38 PM<br>
To: <a href=3D"mailto:multimob@ietf.org">multimob@ietf.org</a><br>
Subject: [multimob] Volunteers to review draft-ietf-multimob-fast-handover-=
01</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">Hi all,</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">In IETF84, three people volunteered to review</p>
<p class=3D"MsoPlainText">draft-ietf-multimob-fast-handover-01,</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">Thomas, Akbar and Costas.</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">The volunteers, thanks for volunteering and pleas=
e post your reviews</p>
<p class=3D"MsoPlainText">on the list soon.</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">Regards,</p>
<p class=3D"MsoPlainText">&nbsp;</p>
<p class=3D"MsoPlainText">Behcet</p>
<p class=3D"MsoPlainText">_______________________________________________</=
p>
<p class=3D"MsoPlainText">multimob mailing list</p>
<p class=3D"MsoPlainText"><a href=3D"mailto:multimob@ietf.org">multimob@iet=
f.org</a></p>
<p class=3D"MsoPlainText"><a href=3D"https://www.ietf.org/mailman/listinfo/=
multimob">https://www.ietf.org/mailman/listinfo/multimob</a></p>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
<br>
<hr>
<font face=3D"Arial" color=3D"Gray" size=3D"1"><br>
Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nu=
estra pol=EDtica de env=EDo y recepci=F3n de correo electr=F3nico en el enl=
ace situado m=E1s abajo.<br>
This message is intended exclusively for its addressee. We only send and re=
ceive email on the basis of the terms set out at:<br>
http://www.tid.es/ES/PAGINAS/disclaimer.aspx<br>
</font>
</body>
</html>

--Boundary_(ID_yvM3Tgs2kj6i0Au6J7qQ0Q)--

From internet-drafts@ietf.org  Mon Oct 22 02:08:07 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B79321F8C4D; Mon, 22 Oct 2012 02:08:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.531
X-Spam-Level: 
X-Spam-Status: No, score=-102.531 tagged_above=-999 required=5 tests=[AWL=0.068, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XAWEp9URbFhy; Mon, 22 Oct 2012 02:08:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C71421F8BF1; Mon, 22 Oct 2012 02:08:06 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121022090806.6938.78743.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 02:08:06 -0700
Cc: multimob@ietf.org
Subject: [multimob] I-D Action: draft-ietf-multimob-fast-handover-02.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 09:08:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Multicast Mobility Working Group of the I=
ETF.

	Title           : PMIPv6 multicast handover optimization by the Subscripti=
on Information Acquisition through the LMA (SIAL)
	Author(s)       : Luis M. Contreras
                          Carlos J. Bernardos
                          Ignacio Soto
	Filename        : draft-ietf-multimob-fast-handover-02.txt
	Pages           : 42
	Date            : 2012-10-22

Abstract:
   This document specifies a multicast handover optimization mechanism
   for Proxy Mobile IPv6 to accelerate the delivery of multicast traffic
   to mobile nodes after handovers.  The mechanism is based on speeding
   up the acquisition of mobile nodes' multicast context by the mobile
   access gateways.  To do that, extensions to the current Proxy Mobile
   IPv6 protocol are proposed.  These extensions are not only applicable
   to the base solution for multicast support in Proxy Mobile IPv6, but
   they can also be applied to other solutions being developed to avoid
   the tunnel convergence problem.  Furthermore, they are also
   independent of the role played by the mobile access gateway within
   the multicast network (either acting as multicast listener discovery
   proxy or multicast router).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-multimob-fast-handover

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-multimob-fast-handover-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-fast-handover-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From internet-drafts@ietf.org  Mon Oct 22 11:07:12 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B945321F8B66; Mon, 22 Oct 2012 11:07:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.54
X-Spam-Level: 
X-Spam-Status: No, score=-102.54 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QCiVw4l13uZp; Mon, 22 Oct 2012 11:07:04 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12CF511E80F5; Mon, 22 Oct 2012 11:07:04 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121022180703.7551.40147.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 11:07:03 -0700
Cc: multimob@ietf.org
Subject: [multimob] I-D Action: draft-ietf-multimob-fast-handover-03.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 18:07:12 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Multicast Mobility Working Group of the I=
ETF.

	Title           : PMIPv6 multicast handover optimization by the Subscripti=
on Information Acquisition through the LMA (SIAL)
	Author(s)       : Luis M. Contreras
                          Carlos J. Bernardos
                          Ignacio Soto
	Filename        : draft-ietf-multimob-fast-handover-03.txt
	Pages           : 42
	Date            : 2012-10-22

Abstract:
   This document specifies a multicast handover optimization mechanism
   for Proxy Mobile IPv6 to accelerate the delivery of multicast traffic
   to mobile nodes after handovers.  The mechanism is based on speeding
   up the acquisition of mobile nodes' multicast context by the mobile
   access gateways.  To do that, extensions to the current Proxy Mobile
   IPv6 protocol are proposed.  These extensions are not only applicable
   to the base solution for multicast support in Proxy Mobile IPv6, but
   they can also be applied to other solutions being developed to avoid
   the tunnel convergence problem.  Furthermore, they are also
   independent of the role played by the mobile access gateway within
   the multicast network (either acting as multicast listener discovery
   proxy or multicast router).


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-multimob-fast-handover

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-multimob-fast-handover-03

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-fast-handover-03


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From sfigueiredo@av.it.pt  Mon Oct 22 12:10:35 2012
Return-Path: <sfigueiredo@av.it.pt>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ABD011E809C for <multimob@ietfa.amsl.com>; Mon, 22 Oct 2012 12:10:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sGufrdeTmfsi for <multimob@ietfa.amsl.com>; Mon, 22 Oct 2012 12:10:30 -0700 (PDT)
Received: from av.it.pt (mail.av.it.pt [193.136.92.53]) by ietfa.amsl.com (Postfix) with ESMTP id 101C921F849D for <multimob@ietf.org>; Mon, 22 Oct 2012 12:10:28 -0700 (PDT)
Received: from [193.136.93.233] (account sfigueiredo@av.it.pt [193.136.93.233] verified) by av.it.pt (CommuniGate Pro SMTP 5.4.2) with ESMTPSA id 66713764 for multimob@ietf.org; Mon, 22 Oct 2012 20:10:24 +0100
Message-ID: <50859A22.9050406@av.it.pt>
Date: Mon, 22 Oct 2012 20:10:26 +0100
From: =?UTF-8?B?U8OpcmdpbyBGaWd1ZWlyZWRv?= <sfigueiredo@av.it.pt>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/20121011 Thunderbird/16.0.1
MIME-Version: 1.0
To: multimob@ietf.org
References: <20121022185922.7529.40290.idtracker@ietfa.amsl.com>
In-Reply-To: <20121022185922.7529.40290.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [multimob] New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-03.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 19:10:35 -0000

Dear all,

We updated our draft on "P Multicast Use Cases and Analysis over 
Distributed Mobility Management". The major changes are summarized as 
follows:

- added a clear separation between the operation description and the 
analysis of the pros and cons for each use case (reflecting the comments 
received in the previous meeting);
- we now consider the use cases where multicast router is deployed in MARs;
- extended Assumptions section;
- added a Table summarizing the provided analysis.


You can find the updated draft in the link below:
http://www.ietf.org/id/draft-sfigueiredo-multimob-use-case-dmm-03.txt

We'll appreciate very much your comments and reviews.


Best regards,
Sérgio


On 10/22/2012 07:59 PM, internet-drafts@ietf.org wrote:
> A new version of I-D, draft-sfigueiredo-multimob-use-case-dmm-03.txt
> has been successfully submitted by Sergio Figueiredo and posted to the
> IETF repository.
>
> Filename:	 draft-sfigueiredo-multimob-use-case-dmm
> Revision:	 03
> Title:		 IP Multicast Use Cases and Analysis over Distributed Mobility Management
> Creation date:	 2012-10-22
> WG ID:		 Individual Submission
> Number of pages: 18
> URL:             http://www.ietf.org/internet-drafts/draft-sfigueiredo-multimob-use-case-dmm-03.txt
> Status:          http://datatracker.ietf.org/doc/draft-sfigueiredo-multimob-use-case-dmm
> Htmlized:        http://tools.ietf.org/html/draft-sfigueiredo-multimob-use-case-dmm-03
> Diff:            http://www.ietf.org/rfcdiff?url2=draft-sfigueiredo-multimob-use-case-dmm-03
>
> Abstract:
>     Mobile networks are changing towards distributed mobility management
>     (DMM), tackling inefficiencies of existing mobility protocols
>     regarding network management and packet routing. Identifying IP
>     multicast use cases applicable to DMM is a logical step before
>     exploring solution spaces. This document describes use cases where IP
>     multicast is applied in DMM environments, considering two main
>     deployment options: multicast router or MLD-Proxy deployment at a
>     Mobility Access Router (MAR). Due to the lack of standard terminology,
>     we refer to MAR as the entity embedding mobility-related functions,
>     e.g. providing network access and flow anchoring capabilities. Each
>     deployment option is thoroughly analyzed regarding its advantages and
>     disadvantages, and both multicast listener and source mobility
>     support are considered.
>
>                                                                                    
>
>
> The IETF Secretariat
>


From internet-drafts@ietf.org  Mon Oct 22 13:33:17 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AF4C21F8451; Mon, 22 Oct 2012 13:33:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TLICTLR8tAs4; Mon, 22 Oct 2012 13:33:16 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 730E621F8434; Mon, 22 Oct 2012 13:33:16 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121022203316.15909.82915.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 13:33:16 -0700
Cc: multimob@ietf.org
Subject: [multimob] I-D Action: draft-ietf-multimob-pmipv6-ropt-02.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 20:33:17 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Multicast Mobility Working Group of the I=
ETF.

	Title           : Multicast Mobility Routing Optimizations for Proxy Mobil=
e IPv6
	Author(s)       : Juan Carlos Zuniga
                          Luis M. Contreras
                          Carlos J. Bernardos
                          Seil Jeon
                          Younghan Kim
	Filename        : draft-ietf-multimob-pmipv6-ropt-02.txt
	Pages           : 30
	Date            : 2012-10-22

Abstract:
   The MULTIMOB group has specified a base solution to support IP
   multicasting in a PMIPv6 domain [RFC6224].  In this document, some
   enhancements to the base solution are described.  These enhancements
   include the use of a multicast tree mobility anchor as the
   topological anchor point for multicast traffic, as well as a direct
   routing option where the MAG can provide access to multicast content
   in the local network.  These enhancements provide benefits such as
   reducing multicast traffic replication and supporting different
   PMIPv6 deployment scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-multimob-pmipv6-ropt

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-multimob-pmipv6-ropt-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-pmipv6-ropt-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From sarikaya2012@gmail.com  Mon Oct 22 14:51:30 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC0E1F042B for <multimob@ietfa.amsl.com>; Mon, 22 Oct 2012 14:51:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.521
X-Spam-Level: 
X-Spam-Status: No, score=-3.521 tagged_above=-999 required=5 tests=[AWL=0.078,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Hwpe5rOjSRwC for <multimob@ietfa.amsl.com>; Mon, 22 Oct 2012 14:51:29 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 4DACF21F88C1 for <multimob@ietf.org>; Mon, 22 Oct 2012 14:51:29 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so5164298iec.31 for <multimob@ietf.org>; Mon, 22 Oct 2012 14:51:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=SkItUutdHiujUsBjOuHFw6Vd0nHWC6b0cQpqQWQwv0o=; b=eKwlofZN8e13IJLHwF3DNBkSFU5uRWFfJADfqP0mxWPfM3tAkNIcpMNZaCKBIHWTus lEfZ7nXbliSU4HiPh5iJy4aYsmHBQheJuY4MHdoZdpPYcIhEFUEvxl57JEEOK1WqENDn RDgkGyvgb+BeXLmIjsa+iXWFke4YecCm3rXelAZazz8RL4EogVSCd24mU9SokIoBPvSg pc38ZbhaNikLOzla+nH2V2gNNxHYygJVP8ZLMjmGmHByRRLA0hcz7678jb69RPbWI0OR YZQljYO4g+FrSM1KnYNLO+Hu5+R28/DxJ77ORiTUUvKlzXW45XSKksQ4VqBhpqMDsy+3 jWcA==
MIME-Version: 1.0
Received: by 10.50.173.37 with SMTP id bh5mr10974072igc.45.1350942687908; Mon, 22 Oct 2012 14:51:27 -0700 (PDT)
Received: by 10.231.85.26 with HTTP; Mon, 22 Oct 2012 14:51:27 -0700 (PDT)
Date: Mon, 22 Oct 2012 16:51:27 -0500
Message-ID: <CAC8QAcef8eVpSGmmV5WS7eVz00R5YacAVnM4uTdg6nz-r94EVw@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: multimob@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [multimob] IETF 85 Agenda
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:51:30 -0000

Hi all,

A draft agenda for Multimob session has been posted.

Regards,

Behcet

From internet-drafts@ietf.org  Mon Oct 22 14:55:06 2012
Return-Path: <internet-drafts@ietf.org>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A232A21F847C; Mon, 22 Oct 2012 14:55:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KSZhLl9YGFxF; Mon, 22 Oct 2012 14:55:06 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB3F021F846B; Mon, 22 Oct 2012 14:54:59 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121022215459.9272.3770.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 14:54:59 -0700
Cc: multimob@ietf.org
Subject: [multimob] I-D Action: draft-ietf-multimob-pmipv6-source-02.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Oct 2012 21:55:06 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Multicast Mobility Working Group of the I=
ETF.

	Title           : Mobile Multicast Sender Support in Proxy Mobile IPv6 (PM=
IPv6) Domains
	Author(s)       : Thomas C. Schmidt
                          Shuai Gao
                          Hong-Ke Zhang
                          Matthias Waehlisch
	Filename        : draft-ietf-multimob-pmipv6-source-02.txt
	Pages           : 26
	Date            : 2012-10-22

Abstract:
   Multicast communication can be enabled in Proxy Mobile IPv6 domains
   via the Local Mobility Anchors by deploying MLD Proxy functions at
   Mobile Access Gateways, via a direct traffic distribution within an
   ISP's access network, or by selective route optimization schemes.
   This document describes the support of mobile multicast senders in
   Proxy Mobile IPv6 domains for all three scenarios.  Protocol
   optimizations for synchronizing PMIPv6 with PIM, as well as extended
   MLD Proxy functions are presented.  Mobile sources always remain
   agnostic of multicast mobility operations.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-multimob-pmipv6-source

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-multimob-pmipv6-source-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-pmipv6-source-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From cjbc@it.uc3m.es  Tue Oct 23 11:31:37 2012
Return-Path: <cjbc@it.uc3m.es>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D938F11E80EE for <multimob@ietfa.amsl.com>; Tue, 23 Oct 2012 11:31:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.492
X-Spam-Level: 
X-Spam-Status: No, score=-5.492 tagged_above=-999 required=5 tests=[AWL=0.207,  BAYES_00=-2.599, J_CHICKENPOX_21=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XHilJDAPY5V0 for <multimob@ietfa.amsl.com>; Tue, 23 Oct 2012 11:31:37 -0700 (PDT)
Received: from smtp01.uc3m.es (smtp01.uc3m.es [163.117.176.131]) by ietfa.amsl.com (Postfix) with ESMTP id C009711E80DC for <multimob@ietf.org>; Tue, 23 Oct 2012 11:31:36 -0700 (PDT)
X-uc3m-safe: yes
Received: from [163.117.139.72] (acorde.it.uc3m.es [163.117.139.72]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: cjbc@smtp01.uc3m.es) by smtp01.uc3m.es (Postfix) with ESMTPSA id 016DDCB296C for <multimob@ietf.org>; Tue, 23 Oct 2012 20:31:35 +0200 (CEST)
Message-ID: <1351017094.27864.43.camel@acorde.it.uc3m.es>
From: Carlos =?ISO-8859-1?Q?Jes=FAs?= Bernardos Cano <cjbc@it.uc3m.es>
To: multimob@ietf.org
Date: Tue, 23 Oct 2012 20:31:34 +0200
Organization: Universidad Carlos III de Madrid
Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";  boundary="=-w08BT9ajWsgaF7lvwxAV"
X-Mailer: Evolution 3.4.3-1 
Mime-Version: 1.0
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-6.8.0.1017-19300.001
X-TM-AS-Result: No--8.763-7.0-31-1
X-imss-scan-details: No--8.763-7.0-31-1
Subject: [multimob] [Fwd: I-D Action: draft-ietf-multimob-pmipv6-ropt-02.txt]
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: cjbc@it.uc3m.es
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 18:31:38 -0000

--=-w08BT9ajWsgaF7lvwxAV
Content-Type: multipart/mixed; boundary="=-3pbX9XpBQJl2xkAoFph7"


--=-3pbX9XpBQJl2xkAoFph7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

(re-sending, as Juan Carlos is having some issues posting to the list,
apologies if there are duplicates)

Hi all,
       =20
	We have just submitted a new version of the routing optimizations WG
document, in which we have implemented the changes discussed at IETF 84
in Vancouver.
       =20
	We look forward to your new reviews and comments.
       =20
	Best regards,
       =20
	Juan Carlos

--=20
Carlos Jes=C3=BAs Bernardos Cano  http://www.netcom.it.uc3m.es/
GPG FP: D29B 0A6A 639A A561 93CA  4D55 35DC BA4D D170 4F67

--=-3pbX9XpBQJl2xkAoFph7
Content-Disposition: inline
Content-Description: Forwarded message - I-D Action:
 draft-ietf-multimob-pmipv6-ropt-02.txt
Content-Type: message/rfc822

Return-Path: <i-d-announce-bounces@ietf.org>
X-Spam-Checker-Version: SpamAssassin 3.1.7-deb (2006-10-05) on
 antispam.uc3m.es
X-Spam-Level: 
X-Spam-Status: No, score=1.0 required=3.0 tests=AWL,BAYES_00,NO_REAL_NAME
 autolearn=no version=3.1.7-deb
X-Original-To: cjbc@it.uc3m.es
Delivered-To: cjbc@correo01.uc3m.es
Received: from smtp01.uc3m.es (pip-L01.uc3m.es [163.117.176.61]) (using
 TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate
 requested) by correo01.uc3m.es (Postfix) with ESMTPS id 56143137C9; Mon, 22
 Oct 2012 22:33:46 +0200 (CEST)
Received: from mail.ietf.org (mail.ietf.org [64.170.98.30]) by
 smtp01.uc3m.es (Postfix) with ESMTP id 82FB9CC5EA1; Mon, 22 Oct 2012
 22:33:45 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1;
 t=1350937999; bh=XcZxRZ616vviCbrlcPFhbsBamRoarKscHAWNMrmVt+U=;
 h=MIME-Version:From:To:Subject:Message-ID:Date:Cc:Reply-To:List-Id:
 List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe:
 Content-Type:Content-Transfer-Encoding:Sender;
 b=bQJRTqMdq8g4GZwgD8V1K9ogmfCK834cFMSs1PR56WMoNbaKjYEQ0DMJ6iAN8hzsK
 8suzoNAtq2xbbcGxIoS0i4HLzDY2h6R3i0WwcmV2IIk+bmZZoJ3FbP34Pi9up9VBKl
 oda0+wMPQwI2D8/q7PJ52DvB6fBRcieINn8hhV90=
X-Original-To: i-d-announce@ietfa.amsl.com
Delivered-To: i-d-announce@ietfa.amsl.com
X-Virus-Scanned: amavisd-new at amsl.com
MIME-Version: 1.0
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Subject: I-D Action: draft-ietf-multimob-pmipv6-ropt-02.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 4.34
Message-ID: <20121022203316.15909.82915.idtracker@ietfa.amsl.com>
Date: Mon, 22 Oct 2012 13:33:16 -0700
Cc: multimob@ietf.org
X-BeenThere: i-d-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: internet-drafts@ietf.org
List-Id: Internet Draft Announcements only <i-d-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/i-d-announce>,
 <mailto:i-d-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/i-d-announce>
List-Post: <mailto:i-d-announce@ietf.org>
List-Help: <mailto:i-d-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/i-d-announce>,
 <mailto:i-d-announce-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Sender: i-d-announce-bounces@ietf.org
Errors-To: i-d-announce-bounces@ietf.org
X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7
 (smtp01.uc3m.es); Mon, 22 Oct 2012 22:33:45 +0200 (CEST)
X-TM-AS-Product-Ver: IMSS-7.1.0.1224-6.8.0.1017-19296.001
X-TM-AS-Result: No--5.964-7.0-31-1
X-imss-scan-details: No--5.964-7.0-31-1
Content-Transfer-Encoding: quoted-printable


A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the Multicast Mobility Working Group of the I=
ETF.

	Title           : Multicast Mobility Routing Optimizations for Proxy Mobil=
e IPv6
	Author(s)       : Juan Carlos Zuniga
                          Luis M. Contreras
                          Carlos J. Bernardos
                          Seil Jeon
                          Younghan Kim
	Filename        : draft-ietf-multimob-pmipv6-ropt-02.txt
	Pages           : 30
	Date            : 2012-10-22

Abstract:
   The MULTIMOB group has specified a base solution to support IP
   multicasting in a PMIPv6 domain [RFC6224].  In this document, some
   enhancements to the base solution are described.  These enhancements
   include the use of a multicast tree mobility anchor as the
   topological anchor point for multicast traffic, as well as a direct
   routing option where the MAG can provide access to multicast content
   in the local network.  These enhancements provide benefits such as
   reducing multicast traffic replication and supporting different
   PMIPv6 deployment scenarios.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-multimob-pmipv6-ropt

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-multimob-pmipv6-ropt-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-multimob-pmipv6-ropt-02


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt

--=-3pbX9XpBQJl2xkAoFph7--

--=-w08BT9ajWsgaF7lvwxAV
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
Content-Transfer-Encoding: 7bit

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEABECAAYFAlCG4oYACgkQNdy6TdFwT2f88wCeI4uTNzF2Dutxy4DGpReHP44C
6KgAoLGxhX0qP5gQuny7FbEa/7LdhnCM
=6Wy9
-----END PGP SIGNATURE-----

--=-w08BT9ajWsgaF7lvwxAV--


From lmcm@tid.es  Tue Oct 23 12:09:58 2012
Return-Path: <lmcm@tid.es>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0809411E80E3 for <multimob@ietfa.amsl.com>; Tue, 23 Oct 2012 12:09:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level: 
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lRs3uYSamMld for <multimob@ietfa.amsl.com>; Tue, 23 Oct 2012 12:09:57 -0700 (PDT)
Received: from tidos.tid.es (tidos.tid.es [195.235.93.44]) by ietfa.amsl.com (Postfix) with ESMTP id AC08E11E80D9 for <multimob@ietf.org>; Tue, 23 Oct 2012 12:09:56 -0700 (PDT)
Received: from sbrightmailg01.hi.inet (sbrightmailg01.hi.inet [10.95.64.104]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0MCD00JD018J5N@tid.hi.inet> for multimob@ietf.org; Tue, 23 Oct 2012 21:09:55 +0200 (MEST)
Received: from tid (tid.hi.inet [10.95.64.10])	by sbrightmailg01.hi.inet (Symantec Messaging Gateway) with SMTP id 05.4B.03050.38BE6805; Tue, 23 Oct 2012 21:09:55 +0200 (CEST)
Received: from correo.tid.es (mailhost.hi.inet [10.95.64.100]) by tid.hi.inet (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPS id <0MCD00JCW18J5N@tid.hi.inet> for multimob@ietf.org; Tue, 23 Oct 2012 21:09:55 +0200 (MEST)
Received: from EX10-MB1-MAD.hi.inet ([169.254.1.178]) by ex10-htcas3-mad.hi.inet ([::1]) with mapi id 14.02.0318.004; Tue, 23 Oct 2012 21:09:55 +0200
Date: Tue, 23 Oct 2012 19:09:54 +0000
From: LUIS MIGUEL CONTRERAS MURILLO <lmcm@tid.es>
In-reply-to: <20121022180703.7551.40147.idtracker@ietfa.amsl.com>
X-Originating-IP: [10.95.64.115]
To: "multimob@ietf.org" <multimob@ietf.org>
Message-id: <823234EF5C7C334998D973D822FF801B1B8570D4@EX10-MB1-MAD.hi.inet>
MIME-version: 1.0
Content-type: text/plain; charset=utf-8
Content-language: es-ES
Content-transfer-encoding: base64
Accept-Language: es-ES, en-US
Thread-topic: [multimob] I-D Action: draft-ietf-multimob-fast-handover-03.txt
Thread-index: AQHNsIBCtbAnNcSLcEygR8kQxeLBQJfHQStQ
X-AuditID: 0a5f4068-b7f176d000000bea-e2-5086eb83841e
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprDKsWRmVeSWpSXmKPExsXCFe/Apdv8ui3A4N1rSYsZH/tYHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVsaWrtmCKfMWujmbWBsY1cl2MnBwSAiYS/7ovskPYYhIX7q1n 62Lk4hAS2MgocbL9IpTzh1Hi2u4WVpAqIYGZjBJNTQYgNouAqkTjnR0sIDabgKHErJ2TwGqE BXwkTs/YATaVU8BR4t2FZSwQGxQk/px7DGaLCGhLvHn5hwnEZhZIk/h4/ipYnFfAW+LrzKds ELagxI/J94DiHEA16hJTpuRClItLzPk1kRXCVpSYtqiBEcRmFJCVWHn+NCNIuYiAr0TP/ziI TUYSf9/dYYa4QEBiyZ7zULaoxMvH/1hByoUEHCTeLpCbwCg+C8neWQh7ZyHZOwvJ3gWMLKsY xYqTijLTM0pyEzNz0g0M9TIy9TLzUks2MUKiJ2MH4/KdKocYBTgYlXh4D1xsCxBiTSwrrsw9 xCjJwaQkynv7JVCILyk/pTIjsTgjvqg0J7X4EKMEB7OSCO/ku0A53pTEyqrUonyYlAwHh5IE Lxsw0oUEi1LTUyvSMnOAKQImzcTBCdLOA9T+/hVIe3FBYm5xZjpE/hSjKsfOnQsfMgqx5OXn pUqJ8z4EKRIAKcoozYOb84pRHOhgYV5BkDU8wCQHN+EV0HAmoOHmPK0gw0sSEVJSDYwOMmU6 U6omsvdv4V340DV4HlPEk1Oz5ZwnzOtfXuS7ILF3/oX4Y11aN2XC6ryyeA0XLH986sLSbr88 rulL1U1Zmx7z8K8Q5dBfUiax8VH1T8GGvoNS3z96COvc3mWtG8rfaKCdFnzreOy9HdztCtYO Rt8UGeRy9zxI57uUJN907EjuBTuhl0osxRmJhlrMRcWJAHvqWnAvAwAA
References: <20121022180703.7551.40147.idtracker@ietfa.amsl.com>
Subject: [multimob] RV: I-D Action: draft-ietf-multimob-fast-handover-03.txt
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 19:09:58 -0000

SGkgYWxsLA0KDQpZZXN0ZXJkYXkgd2Ugc3VibWl0dGVkIGEgbmV3IHZlcnNpb24gb2YgdGhlIFdH
IGRvY3VtZW50ICJkcmFmdC1pZXRmLW11bHRpbW9iLWZhc3QtaGFuZG92ZXIiLCBhZGRyZXNzaW5n
IHJlY2VpdmVkIGNvbW1lbnRzIGFuZCBwZW5kaW5nIHNlY3Rpb25zLg0KDQpBZGRpdGlvbmFsIGNv
bW1lbnRzIGFyZSB3ZWxjb21lLg0KDQpCZXN0IHJlZ2FyZHMsDQoNCkx1aXMNCg0KLS0tLS1NZW5z
YWplIG9yaWdpbmFsLS0tLS0NCkRlOiBtdWx0aW1vYi1ib3VuY2VzQGlldGYub3JnIFttYWlsdG86
bXVsdGltb2ItYm91bmNlc0BpZXRmLm9yZ10gRW4gbm9tYnJlIGRlIGludGVybmV0LWRyYWZ0c0Bp
ZXRmLm9yZw0KRW52aWFkbyBlbDogbHVuZXMsIDIyIGRlIG9jdHVicmUgZGUgMjAxMiAyMDowNw0K
UGFyYTogaS1kLWFubm91bmNlQGlldGYub3JnDQpDQzogbXVsdGltb2JAaWV0Zi5vcmcNCkFzdW50
bzogW211bHRpbW9iXSBJLUQgQWN0aW9uOiBkcmFmdC1pZXRmLW11bHRpbW9iLWZhc3QtaGFuZG92
ZXItMDMudHh0DQoNCg0KQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhl
IG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KIFRoaXMgZHJhZnQgaXMgYSB3
b3JrIGl0ZW0gb2YgdGhlIE11bHRpY2FzdCBNb2JpbGl0eSBXb3JraW5nIEdyb3VwIG9mIHRoZSBJ
RVRGLg0KDQogICAgICAgIFRpdGxlICAgICAgICAgICA6IFBNSVB2NiBtdWx0aWNhc3QgaGFuZG92
ZXIgb3B0aW1pemF0aW9uIGJ5IHRoZSBTdWJzY3JpcHRpb24gSW5mb3JtYXRpb24gQWNxdWlzaXRp
b24gdGhyb3VnaCB0aGUgTE1BIChTSUFMKQ0KICAgICAgICBBdXRob3IocykgICAgICAgOiBMdWlz
IE0uIENvbnRyZXJhcw0KICAgICAgICAgICAgICAgICAgICAgICAgICBDYXJsb3MgSi4gQmVybmFy
ZG9zDQogICAgICAgICAgICAgICAgICAgICAgICAgIElnbmFjaW8gU290bw0KICAgICAgICBGaWxl
bmFtZSAgICAgICAgOiBkcmFmdC1pZXRmLW11bHRpbW9iLWZhc3QtaGFuZG92ZXItMDMudHh0DQog
ICAgICAgIFBhZ2VzICAgICAgICAgICA6IDQyDQogICAgICAgIERhdGUgICAgICAgICAgICA6IDIw
MTItMTAtMjINCg0KQWJzdHJhY3Q6DQogICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyBhIG11bHRp
Y2FzdCBoYW5kb3ZlciBvcHRpbWl6YXRpb24gbWVjaGFuaXNtDQogICBmb3IgUHJveHkgTW9iaWxl
IElQdjYgdG8gYWNjZWxlcmF0ZSB0aGUgZGVsaXZlcnkgb2YgbXVsdGljYXN0IHRyYWZmaWMNCiAg
IHRvIG1vYmlsZSBub2RlcyBhZnRlciBoYW5kb3ZlcnMuICBUaGUgbWVjaGFuaXNtIGlzIGJhc2Vk
IG9uIHNwZWVkaW5nDQogICB1cCB0aGUgYWNxdWlzaXRpb24gb2YgbW9iaWxlIG5vZGVzJyBtdWx0
aWNhc3QgY29udGV4dCBieSB0aGUgbW9iaWxlDQogICBhY2Nlc3MgZ2F0ZXdheXMuICBUbyBkbyB0
aGF0LCBleHRlbnNpb25zIHRvIHRoZSBjdXJyZW50IFByb3h5IE1vYmlsZQ0KICAgSVB2NiBwcm90
b2NvbCBhcmUgcHJvcG9zZWQuICBUaGVzZSBleHRlbnNpb25zIGFyZSBub3Qgb25seSBhcHBsaWNh
YmxlDQogICB0byB0aGUgYmFzZSBzb2x1dGlvbiBmb3IgbXVsdGljYXN0IHN1cHBvcnQgaW4gUHJv
eHkgTW9iaWxlIElQdjYsIGJ1dA0KICAgdGhleSBjYW4gYWxzbyBiZSBhcHBsaWVkIHRvIG90aGVy
IHNvbHV0aW9ucyBiZWluZyBkZXZlbG9wZWQgdG8gYXZvaWQNCiAgIHRoZSB0dW5uZWwgY29udmVy
Z2VuY2UgcHJvYmxlbS4gIEZ1cnRoZXJtb3JlLCB0aGV5IGFyZSBhbHNvDQogICBpbmRlcGVuZGVu
dCBvZiB0aGUgcm9sZSBwbGF5ZWQgYnkgdGhlIG1vYmlsZSBhY2Nlc3MgZ2F0ZXdheSB3aXRoaW4N
CiAgIHRoZSBtdWx0aWNhc3QgbmV0d29yayAoZWl0aGVyIGFjdGluZyBhcyBtdWx0aWNhc3QgbGlz
dGVuZXIgZGlzY292ZXJ5DQogICBwcm94eSBvciBtdWx0aWNhc3Qgcm91dGVyKS4NCg0KDQpUaGUg
SUVURiBkYXRhdHJhY2tlciBzdGF0dXMgcGFnZSBmb3IgdGhpcyBkcmFmdCBpczoNCmh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWlldGYtbXVsdGltb2ItZmFzdC1oYW5kb3Zl
cg0KDQpUaGVyZSdzIGFsc28gYSBodG1saXplZCB2ZXJzaW9uIGF2YWlsYWJsZSBhdDoNCmh0dHA6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtbXVsdGltb2ItZmFzdC1oYW5kb3Zlci0w
Mw0KDQpBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQpo
dHRwOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLW11bHRpbW9iLWZhc3Qt
aGFuZG92ZXItMDMNCg0KDQpJbnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFu
b255bW91cyBGVFAgYXQ6DQpmdHA6Ly9mdHAuaWV0Zi5vcmcvaW50ZXJuZXQtZHJhZnRzLw0KDQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KbXVsdGltb2Ig
bWFpbGluZyBsaXN0DQptdWx0aW1vYkBpZXRmLm9yZw0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9tdWx0aW1vYg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KDQpFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3UgZGVzdGluYXRh
cmlvLiBQdWVkZSBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61vIHkgcmVjZXBj
acOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRvIG3DoXMgYWJh
am8uDQpUaGlzIG1lc3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0cyBhZGRyZXNz
ZWUuIFdlIG9ubHkgc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMgb2YgdGhlIHRl
cm1zIHNldCBvdXQgYXQ6DQpodHRwOi8vd3d3LnRpZC5lcy9FUy9QQUdJTkFTL2Rpc2NsYWltZXIu
YXNweA0K

From sarikaya2012@gmail.com  Tue Oct 23 13:47:46 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F79E21F85C4 for <multimob@ietfa.amsl.com>; Tue, 23 Oct 2012 13:47:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.526
X-Spam-Level: 
X-Spam-Status: No, score=-3.526 tagged_above=-999 required=5 tests=[AWL=0.073,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FXybJMOBT0Aw for <multimob@ietfa.amsl.com>; Tue, 23 Oct 2012 13:47:46 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id F33FA21F8596 for <multimob@ietf.org>; Tue, 23 Oct 2012 13:47:45 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so6975667iec.31 for <multimob@ietf.org>; Tue, 23 Oct 2012 13:47:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=bFCBviARwOIMjIl6VY8j1+8YzTkFenArfEPlCUKeq7k=; b=xZebFOiJgaXoRouMgf1qaAtG7XVfhmEVNeQPfzdYeoRzlxW9yfLNvK30I3qv7E8QFj I2zkev2pAi3lRTAyP6rNvqwbt84e5MC4pRsKIu4XO6mkSZMWBusE227+VAjeYf+2LqST BwS/eGu5xQa5HVeieyWjN/JqCqyzfREiu+yVsTUJhO6Stlv7YON6CajuYcvsrmHCsJE+ NTRkzxikYRTW0BxZAT30+mv/VC4Yh/oxzS1W62ykGP0bHV9G+UlADKPwCx2LU//948LL aDVa9193bubDEjNKjzitsFWxVNEUHDjzASqlpo6yOgVbaKdrYAvzw7PNZgCkH6K0ex/X vroA==
MIME-Version: 1.0
Received: by 10.50.5.205 with SMTP id u13mr374180igu.37.1351025265649; Tue, 23 Oct 2012 13:47:45 -0700 (PDT)
Received: by 10.231.85.26 with HTTP; Tue, 23 Oct 2012 13:47:45 -0700 (PDT)
Date: Tue, 23 Oct 2012 15:47:45 -0500
Message-ID: <CAC8QAccs78xPb+y2PzvQEPtnc3jv6ph=yp_1B1y0dKYrrd3sbA@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: multimob@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [multimob] IETF 85 Agenda
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Oct 2012 20:47:46 -0000

Hi all,

The latest agenda is posted at:

http://www.ietf.org/proceedings/85/agenda/agenda-85-multimob

Please take a look and let us know if any changes are needed?

Regards,

Behcet

From asaeda@sfc.wide.ad.jp  Wed Oct 24 19:11:03 2012
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C0FD41F0C4A for <multimob@ietfa.amsl.com>; Wed, 24 Oct 2012 19:11: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.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Dc3f1fN4rbqv for <multimob@ietfa.amsl.com>; Wed, 24 Oct 2012 19:11:03 -0700 (PDT)
Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4A07F1F0C3A for <multimob@ietf.org>; Wed, 24 Oct 2012 19:11:03 -0700 (PDT)
Received: from localhost (unknown [202.249.37.10]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id 28D442780EC for <multimob@ietf.org>; Thu, 25 Oct 2012 11:10:57 +0900 (JST)
Date: Thu, 25 Oct 2012 11:10:58 +0900 (JST)
Message-Id: <20121025.111058.187877044.asaeda@sfc.wide.ad.jp>
To: multimob@ietf.org
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <CAC8QAccs78xPb+y2PzvQEPtnc3jv6ph=yp_1B1y0dKYrrd3sbA@mail.gmail.com>
References: <CAC8QAccs78xPb+y2PzvQEPtnc3jv6ph=yp_1B1y0dKYrrd3sbA@mail.gmail.com>
X-Mailer: Mew version 6.3 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Subject: Re: [multimob] IETF 85 Agenda
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 02:11:03 -0000

Hi,

Please allocate a 10 to 20 min time slot for the following draft.
"Multicast Routing Optimization by PIM-SM with PMIPv6"
http://tools.ietf.org/html/draft-asaeda-multimob-pmip6-extension-11

This is already -11 version.
I'd like to know whether people want "Multicast Routing Optimization
by PIM-SM with PMIPv6" or not in this meeting.
Comment welcome.

Regards,
--
Hitoshi Asaeda


From sarikaya2012@gmail.com  Fri Oct 26 14:07:20 2012
Return-Path: <sarikaya2012@gmail.com>
X-Original-To: multimob@ietfa.amsl.com
Delivered-To: multimob@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8D7C21F8666 for <multimob@ietfa.amsl.com>; Fri, 26 Oct 2012 14:07:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.529
X-Spam-Level: 
X-Spam-Status: No, score=-3.529 tagged_above=-999 required=5 tests=[AWL=0.070,  BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UOponAmjhAIB for <multimob@ietfa.amsl.com>; Fri, 26 Oct 2012 14:07:20 -0700 (PDT)
Received: from mail-ie0-f172.google.com (mail-ie0-f172.google.com [209.85.223.172]) by ietfa.amsl.com (Postfix) with ESMTP id 651CD21F862B for <multimob@ietf.org>; Fri, 26 Oct 2012 14:07:20 -0700 (PDT)
Received: by mail-ie0-f172.google.com with SMTP id 9so4979337iec.31 for <multimob@ietf.org>; Fri, 26 Oct 2012 14:07:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:date:message-id:subject:from:to:content-type; bh=jelNw40yRSlB2YIKbrAgcLpa4lN/FdoZsDiyP0dteFA=; b=KFMXFPOe/l3KYcspehLQBn0+FzuU/cQ5rC1cXeMaaJioAlR68Wn+ScTNRZKcmwai4E 7Ro1jkfrSGRdNl+i2Y96xRFQNZozeIYPwwgZi+8y+t0cR1czgyUwtZpenOOVpX9LPsoH Mxpr570JFqM2TPyyE8H0Gp0kHjMbJbnkCsS3sFJBpcfhfQwe/w3eJHNOoeBuXkymkKks /m+0myAhO4lmtq3EQGGZVpR95crK5T80iuobFBbt4aMfJRY6WuCvMwX4FhxB/ZZCEFOC pH4kmB9r7yqRQxmOHelfAsrVihOaIE/ShrYlHlIDBAZXLrlCP0Ph+m7yOTrzm5NtKHjd d7qg==
MIME-Version: 1.0
Received: by 10.42.247.136 with SMTP id mc8mr12758058icb.36.1351285639742; Fri, 26 Oct 2012 14:07:19 -0700 (PDT)
Received: by 10.231.85.26 with HTTP; Fri, 26 Oct 2012 14:07:19 -0700 (PDT)
Date: Fri, 26 Oct 2012 16:07:19 -0500
Message-ID: <CAC8QAcdR4bQpVKCCAEYO7tYr0XT=wsZ=pxjnK7ABzwqyOLV3xg@mail.gmail.com>
From: Behcet Sarikaya <sarikaya2012@gmail.com>
To: multimob@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
Subject: [multimob] Presentations for IETF 85
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: sarikaya@ieee.org
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Oct 2012 21:07:21 -0000

Hi all,

It seems like the agenda at
http://www.ietf.org/proceedings/85/agenda/agenda-85-multimob
is now stable.

It is time to submit the presentations. Please submit your presentation to
multimob-chairs@tools.ietf.org

Regards,

Behcet
