From Dirk.von-Hugo@telekom.de Mon Mar 5 04:47:45 2012 Return-Path: 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 5E3C121F8622 for ; Mon, 5 Mar 2012 04:47:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.249 X-Spam-Level: X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id w+AOAzp10os7 for ; Mon, 5 Mar 2012 04:47:44 -0800 (PST) Received: from tcmail73.telekom.de (tcmail73.telekom.de [217.243.239.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3318121F8629 for ; Mon, 5 Mar 2012 04:47:43 -0800 (PST) Received: from he111631.emea1.cds.t-internal.com ([10.134.93.23]) by tcmail71.telekom.de with ESMTP/TLS/AES128-SHA; 05 Mar 2012 13:47:16 +0100 Received: from HE113484.emea1.cds.t-internal.com ([169.254.5.243]) by HE111631.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 5 Mar 2012 13:47:16 +0100 From: To: Date: Mon, 5 Mar 2012 13:47:15 +0100 Thread-Topic: New Version Notification for draft-vonhugo-multimob-dmm-context-00.txt Thread-Index: Acz6zN7j0hydsn/nRc6Wo/K9DgxdigAANJMA Message-ID: <05C81A773E48DD49B181B04BA21A342A27544858F8@HE113484.emea1.cds.t-internal.com> Accept-Language: en-US, de-DE Content-Language: de-DE X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, de-DE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: [multimob] WG: New Version Notification for draft-vonhugo-multimob-dmm-context-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 12:47:45 -0000 Dear all, Enclosed please find the link to our draft submitted for dmm-related future= work of multimob for discussion. http://www.ietf.org/id/draft-vonhugo-multimob-dmm-context-00.txt Thank you! Best regards Dirk -----Urspr=FCngliche Nachricht----- Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] Gesendet: Montag, 5. M=E4rz 2012 13:38 An: von Hugo, Dirk Cc: pierrick.seite@orange.com; asaeda@wide.ad.jp Betreff: New Version Notification for draft-vonhugo-multimob-dmm-context-00= .txt A new version of I-D, draft-vonhugo-multimob-dmm-context-00.txt has been su= ccessfully submitted by Dirk von Hugo and posted to the IETF repository. Filename: draft-vonhugo-multimob-dmm-context Revision: 00 Title: Context Transfer for Multicast support in Distributed Mobi= lity Management (DMM) Creation date: 2012-03-05 WG ID: Individual Submission Number of pages: 16 Abstract: This document describes a context transfer based concept to support overarching IP multicast services applicable to various existing approaches for Distributed Mobility Management. The IETF Secretariat From internet-drafts@ietf.org Mon Mar 5 08:51:44 2012 Return-Path: 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 0169321F87AD; Mon, 5 Mar 2012 08:51:44 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.595 X-Spam-Level: X-Spam-Status: No, score=-102.595 tagged_above=-999 required=5 tests=[AWL=0.004, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EiqYR50Ho7sr; Mon, 5 Mar 2012 08:51:43 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4367C21F87AB; Mon, 5 Mar 2012 08:51:43 -0800 (PST) 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.00 Message-ID: <20120305165143.21658.23686.idtracker@ietfa.amsl.com> Date: Mon, 05 Mar 2012 08:51:43 -0800 Cc: multimob@ietf.org Subject: [multimob] I-D Action: draft-ietf-multimob-pmipv6-ropt-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 16:51:44 -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 t= he IETF. 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-00.txt Pages : 29 Date : 2012-03-04 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 deployments scenarios. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multimob-pmipv6-ropt-00.txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-multimob-pmipv6-ropt-00.txt From JuanCarlos.Zuniga@InterDigital.com Mon Mar 5 09:07:45 2012 Return-Path: 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 C39D121F87E7 for ; Mon, 5 Mar 2012 09:07:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qiBYJsnBbvpb for ; Mon, 5 Mar 2012 09:07:45 -0800 (PST) Received: from idcout.InterDigital.com (smtp-out1.interdigital.com [64.208.228.135]) by ietfa.amsl.com (Postfix) with ESMTP id E3E9621F85C5 for ; Mon, 5 Mar 2012 09:07:44 -0800 (PST) Received: from SAM.InterDigital.com ([10.30.2.11]) by idcout.InterDigital.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 5 Mar 2012 12:07:44 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: base64 Date: Mon, 5 Mar 2012 12:07:43 -0500 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: New Version Notification for draft-ietf-multimob-pmipv6-ropt-00.txt Thread-Index: Acz68D+xCHU/hdabQ6OqKvEXLWbtggAANbfA From: "Zuniga, Juan Carlos" To: X-OriginalArrivalTime: 05 Mar 2012 17:07:44.0042 (UTC) FILETIME=[7B0D98A0:01CCFAF2] Cc: seiljeon@av.it.pt, yhkim@dcn.ssu.ac.kr Subject: [multimob] FW: New Version Notification for draft-ietf-multimob-pmipv6-ropt-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 17:07:45 -0000 RGVhciBhbGwsDQoNCldlIGhhdmUgdXBsb2FkZWQgdGhlIGpvaW50IHNvbHV0aW9uIFdHIGRyYWZ0 IHRvIHRoZSAiUE1JUHY2IHJvdXRpbmcgb3B0aW1pemF0aW9ucyB0byBhdm9pZCB0dW5uZWwgY29u dmVyZ2VuY2UiIHByb2JsZW0uIFdlIHRyaWVkIHRvIGFkZHJlc3MgdGhlIGNvbW1lbnRzIHJlY2Vp dmVkIG9uIHRoZSBsaXN0IGFzIHdlbGwgYXMgZHVyaW5nIHRoZSBtZWV0aW5nLg0KDQpodHRwOi8v d3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1pZXRmLW11bHRpbW9iLXBtaXB2Ni1y b3B0LTAwLnR4dCANCg0KWW91ciBjb21tZW50cyBvbiB0aGUgbmV3IGRyYWZ0IGFyZSBhcHByZWNp YXRlZC4NCg0KV2UgbG9vayBmb3J3YXJkIHRvIGRpc2N1c3Npbmcgd2l0aCB5b3Ugb24gdGhlIGxp c3QgYW5kIGF0IHRoZSBQYXJpcyBtZWV0aW5nLg0KDQpCZXN0IHJlZ2FyZHMsDQoNCkp1YW4tQ2Fy bG9zLCBldCBhbC4NCg0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IGlu dGVybmV0LWRyYWZ0c0BpZXRmLm9yZyBbbWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZ10N Cj4gU2VudDogTW9uZGF5LCBNYXJjaCAwNSwgMjAxMiAxMTo1MiBBTQ0KPiBUbzogbG1jbUB0aWQu ZXMNCj4gQ2M6IHNlaWxqZW9uQGF2Lml0LnB0OyB5aGtpbUBkY24uc3N1LmFjLmtyOyBadW5pZ2Es IEp1YW4gQ2FybG9zOw0KPiBjamJjQGl0LnVjM20uZXMNCj4gU3ViamVjdDogTmV3IFZlcnNpb24g Tm90aWZpY2F0aW9uIGZvciBkcmFmdC1pZXRmLW11bHRpbW9iLXBtaXB2Ni1yb3B0LQ0KPiAwMC50 eHQNCj4gDQo+IEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1pZXRmLW11bHRpbW9iLXBtaXB2 Ni1yb3B0LTAwLnR4dCBoYXMgYmVlbg0KPiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEx1aXMg TS4gQ29udHJlcmFzIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYNCj4gcmVwb3NpdG9yeS4NCj4gDQo+ IEZpbGVuYW1lOgkgZHJhZnQtaWV0Zi1tdWx0aW1vYi1wbWlwdjYtcm9wdA0KPiBSZXZpc2lvbjoJ IDAwDQo+IFRpdGxlOgkJIE11bHRpY2FzdCBNb2JpbGl0eSBSb3V0aW5nIE9wdGltaXphdGlvbnMg Zm9yIFByb3h5DQo+IE1vYmlsZSBJUHY2DQo+IENyZWF0aW9uIGRhdGU6CSAyMDEyLTAzLTA0DQo+ IFdHIElEOgkJIG11bHRpbW9iDQo+IE51bWJlciBvZiBwYWdlczogMjkNCj4gDQo+IEFic3RyYWN0 Og0KPiAgICBUaGUgTVVMVElNT0IgZ3JvdXAgaGFzIHNwZWNpZmllZCBhIGJhc2Ugc29sdXRpb24g dG8gc3VwcG9ydCBJUA0KPiAgICBtdWx0aWNhc3RpbmcgaW4gYSBQTUlQdjYgZG9tYWluIFtSRkM2 MjI0XS4gIEluIHRoaXMgZG9jdW1lbnQsIHNvbWUNCj4gICAgZW5oYW5jZW1lbnRzIHRvIHRoZSBi YXNlIHNvbHV0aW9uIGFyZSBkZXNjcmliZWQuICBUaGVzZSBlbmhhbmNlbWVudHMNCj4gICAgaW5j bHVkZSB0aGUgdXNlIG9mIGEgbXVsdGljYXN0IHRyZWUgbW9iaWxpdHkgYW5jaG9yIGFzIHRoZQ0K PiAgICB0b3BvbG9naWNhbCBhbmNob3IgcG9pbnQgZm9yIG11bHRpY2FzdCB0cmFmZmljLCBhcyB3 ZWxsIGFzIGEgZGlyZWN0DQo+ICAgIHJvdXRpbmcgb3B0aW9uIHdoZXJlIHRoZSBNQUcgY2FuIHBy b3ZpZGUgYWNjZXNzIHRvIG11bHRpY2FzdCBjb250ZW50DQo+ICAgIGluIHRoZSBsb2NhbCBuZXR3 b3JrLiAgVGhlc2UgZW5oYW5jZW1lbnRzIHByb3ZpZGUgYmVuZWZpdHMgc3VjaCBhcw0KPiAgICBy ZWR1Y2luZyBtdWx0aWNhc3QgdHJhZmZpYyByZXBsaWNhdGlvbiBhbmQgc3VwcG9ydGluZyBkaWZm ZXJlbnQNCj4gICAgUE1JUHY2IGRlcGxveW1lbnRzIHNjZW5hcmlvcy4NCj4gDQo+IA0KPiANCj4g DQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo= From sarikaya2012@gmail.com Mon Mar 5 10:04:39 2012 Return-Path: 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 D2A9421F8448 for ; Mon, 5 Mar 2012 10:04:39 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.559 X-Spam-Level: X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aGhuiLeP7R-f for ; Mon, 5 Mar 2012 10:04:39 -0800 (PST) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 46EB821F8669 for ; Mon, 5 Mar 2012 10:04:39 -0800 (PST) Received: by yenm5 with SMTP id m5so2017381yen.31 for ; Mon, 05 Mar 2012 10:04:38 -0800 (PST) Received-SPF: pass (google.com: domain of sarikaya2012@gmail.com designates 10.236.173.132 as permitted sender) client-ip=10.236.173.132; Authentication-Results: mr.google.com; spf=pass (google.com: domain of sarikaya2012@gmail.com designates 10.236.173.132 as permitted sender) smtp.mail=sarikaya2012@gmail.com; dkim=pass header.i=sarikaya2012@gmail.com Received: from mr.google.com ([10.236.173.132]) by 10.236.173.132 with SMTP id v4mr27903027yhl.78.1330970678993 (num_hops = 1); Mon, 05 Mar 2012 10:04:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=16Oh6Rrz1BCWrEOsdv9qw6GjdJPCmjDmLXlr/dZoi/8=; b=DCG+wgc7sXeFwKFCP6hsLYAgAWNkV1sExwtTEvHA4+Q95s1IaVFijP29YsBOhDGz2+ jDE9ibjbPIkoRPBJMFUk1hGNPrkyhoKuPvRmqeMSvPsrV1qQ3FdgmHWJAzV1ISH06UbM Mhl4EoqDMlvUbbtpe5kaBu3DyZg7hC7cM8QsLabm9NgbafcqfYFDpNffq2hneit2/9Zj EImRvO7uQ6hx2jRa/Yx4QokVRYk5esl77Z3SP/DkrV2UUDs2tU/QxoxmE9k350VNhuE3 G2hu6wGBZEKPaaSK68q8DneIoT7udHfi68gWrPyLGK8NtzmQaKJrBknEDHXrYrfGdFD7 Zk7g== MIME-Version: 1.0 Received: by 10.236.173.132 with SMTP id v4mr21998990yhl.78.1330970678922; Mon, 05 Mar 2012 10:04:38 -0800 (PST) Received: by 10.236.9.73 with HTTP; Mon, 5 Mar 2012 10:04:38 -0800 (PST) In-Reply-To: <05C81A773E48DD49B181B04BA21A342A27544858F8@HE113484.emea1.cds.t-internal.com> References: <05C81A773E48DD49B181B04BA21A342A27544858F8@HE113484.emea1.cds.t-internal.com> Date: Mon, 5 Mar 2012 12:04:38 -0600 Message-ID: From: Behcet Sarikaya To: Dirk.von-Hugo@telekom.de Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: multimob@ietf.org Subject: Re: [multimob] WG: New Version Notification for draft-vonhugo-multimob-dmm-context-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 18:04:40 -0000 Hi Dirk, Thank you for the submission. We have a slot reserved on dmm as possible future work. In that presentation if you can talk about the general problem space of dmm and dmm multicast rather than a specific solution, I think that will be good. Please point out the gaps and why we need to work on it. Regards, Behcet On Mon, Mar 5, 2012 at 6:47 AM, wrote: > > Dear all, > Enclosed please find the link to our draft submitted for dmm-related futu= re work of multimob for discussion. > > http://www.ietf.org/id/draft-vonhugo-multimob-dmm-context-00.txt > > Thank you! > Best regards > Dirk > > -----Urspr=FCngliche Nachricht----- > Von: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > Gesendet: Montag, 5. M=E4rz 2012 13:38 > An: von Hugo, Dirk > Cc: pierrick.seite@orange.com; asaeda@wide.ad.jp > Betreff: New Version Notification for draft-vonhugo-multimob-dmm-context-= 00.txt > > A new version of I-D, draft-vonhugo-multimob-dmm-context-00.txt has been = successfully submitted by Dirk von Hugo and posted to the IETF repository. > > Filename: =A0 =A0 =A0 =A0draft-vonhugo-multimob-dmm-context > Revision: =A0 =A0 =A0 =A000 > Title: =A0 =A0 =A0 =A0 =A0 Context Transfer for Multicast support in Dist= ributed Mobility Management (DMM) > Creation date: =A0 2012-03-05 > WG ID: =A0 =A0 =A0 =A0 =A0 Individual Submission > Number of pages: 16 > > Abstract: > =A0 This document describes a context transfer based concept to support > =A0 overarching IP multicast services applicable to various existing > =A0 approaches for Distributed Mobility Management. > > > > > The IETF Secretariat > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob From prvs=404258745=schmidt@informatik.haw-hamburg.de Mon Mar 5 15:33:33 2012 Return-Path: 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 C51E121E8052 for ; Mon, 5 Mar 2012 15:33:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.249 X-Spam-Level: X-Spam-Status: No, score=-102.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xC-HObCxV2aM for ; Mon, 5 Mar 2012 15:33:33 -0800 (PST) Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3]) by ietfa.amsl.com (Postfix) with ESMTP id 6EDC221E8045 for ; Mon, 5 Mar 2012 15:33:32 -0800 (PST) Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail6.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 06 Mar 2012 00:33:31 +0100 Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 47244104EB81 for ; Tue, 6 Mar 2012 00:33:31 +0100 (CET) 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 16618-02 for ; Tue, 6 Mar 2012 00:33:30 +0100 (CET) Received: from [172.20.10.5] (ip-109-43-0-20.web.vodafone.de [109.43.0.20]) (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 023E6104EB7E for ; Tue, 6 Mar 2012 00:33:29 +0100 (CET) Message-ID: <4F554D4B.7050003@informatik.haw-hamburg.de> Date: Tue, 06 Mar 2012 00:33:31 +0100 From: "Thomas C. Schmidt" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2 MIME-Version: 1.0 To: multimob@ietf.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de Subject: Re: [multimob] FW: New Version Notification for draft-ietf-multimob-pmipv6-ropt-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Mar 2012 23:33:33 -0000 Dear Juan-Carlos et al., just a quick response from a first browse through the document: Section 3: * The statement "The MTMA connects to the MAG as described in [RFC6224] and it can reuse native PMIPv6 features such as tunnel establishment and security [RFC5213], heartbeat [RFC5847], etc." is pretty vague and unclear to me - tunnel management of PMIP is between MAGs and LMAs ... but MTMA cannot act like an LMA (it has no MN-specific state), so how would it be able to perform dynamic tunnel management? * I don't understand the sense of "3.3.2. MAG as Multicast Router" - if there is only one static upstream to the MTMA, a dynamic routing protocol at the MAG seems useless. * You should address and resolve the problem of IPv4 traffic in accordance with RFC 5213. Section 4: * In Section "4.3.1. MAG as MLD Proxy" you speak about "every one of the MLD proxy instances invoked in the MAG" - why multiple instances? What shall each instance do? * In Section "4.3.1.1. Multicast Establishment" it is shown in the flow chart that membership queries are issued from the MR - these are periodic queries which are unrelated to handoffs - thus they do not operate synchronized and therefore generate a possibly large delay - was this intended? * In Section "4.3.2. MAG as multicast router" - I find a section of essentially zero content. This is unfortunate, since the deployment of a multicast routing protocol in a PMIP domain is of enhanced delicacy and full of traps, as we have seen from the repeated (fruitless) attempts Hitoshi has made. This should be explained in utmost precision, as there is no "out-of-the-box" way to do it. So far for a first scratch - I'll be happy to review a more profound version of the draft in detail. Cheer from the Cebit, Thomas On 05.03.2012 18:07, Zuniga, Juan Carlos wrote: > Dear all, > > We have uploaded the joint solution WG draft to the "PMIPv6 routing optimizations to avoid tunnel convergence" problem. We tried to address the comments received on the list as well as during the meeting. > > http://www.ietf.org/internet-drafts/draft-ietf-multimob-pmipv6-ropt-00.txt > > Your comments on the new draft are appreciated. > > We look forward to discussing with you on the list and at the Paris meeting. > > Best regards, > > Juan-Carlos, et al. > > >> -----Original Message----- >> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] >> Sent: Monday, March 05, 2012 11:52 AM >> To: lmcm@tid.es >> Cc: seiljeon@av.it.pt; yhkim@dcn.ssu.ac.kr; Zuniga, Juan Carlos; >> cjbc@it.uc3m.es >> Subject: New Version Notification for draft-ietf-multimob-pmipv6-ropt- >> 00.txt >> >> A new version of I-D, draft-ietf-multimob-pmipv6-ropt-00.txt has been >> successfully submitted by Luis M. Contreras and posted to the IETF >> repository. >> >> Filename: draft-ietf-multimob-pmipv6-ropt >> Revision: 00 >> Title: Multicast Mobility Routing Optimizations for Proxy >> Mobile IPv6 >> Creation date: 2012-03-04 >> WG ID: multimob >> Number of pages: 29 >> >> 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 deployments scenarios. >> >> >> >> >> The IETF Secretariat > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob -- Prof. Dr. Thomas C. Schmidt ° Hamburg University of Applied Sciences Berliner Tor 7 ° ° Dept. Informatik, Internet Technologies Group 20099 Hamburg, Germany ° ° http://www.haw-hamburg.de/inet Fon: +49-40-42875-8452 ° ° http://www.informatik.haw-hamburg.de/~schmidt Fax: +49-40-42875-8409 ° From sfigueiredo@av.it.pt Mon Mar 5 16:22:19 2012 Return-Path: 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 05F0C21E8048 for ; Mon, 5 Mar 2012 16:22:19 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.298 X-Spam-Level: X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xhz1w99hcjUA for ; Mon, 5 Mar 2012 16:22:18 -0800 (PST) Received: from av.it.pt (mail.av.it.pt [193.136.92.53]) by ietfa.amsl.com (Postfix) with ESMTP id E98E621E803E for ; Mon, 5 Mar 2012 16:22:16 -0800 (PST) Received: from [84.91.32.44] (account sfigueiredo@av.it.pt HELO [192.168.0.104]) by av.it.pt (CommuniGate Pro SMTP 5.4.2) with ESMTPSA id 63573290 for multimob@ietf.org; Tue, 06 Mar 2012 00:22:14 +0000 Message-ID: <4F5558B5.3010106@av.it.pt> Date: Tue, 06 Mar 2012 00:22:13 +0000 From: =?UTF-8?B?U8OpcmdpbyBGaWd1ZWlyZWRv?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Lightning/1.0b2 Thunderbird/3.1.16 MIME-Version: 1.0 To: multimob@ietf.org Content-Type: multipart/alternative; boundary="------------010806010704050704030909" Subject: [multimob] Fwd: New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 00:22:19 -0000 This is a multi-part message in MIME format. --------------010806010704050704030909 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dear all, A new Internet draft presenting use cases on PMIPv6-based DMM approaches was just submitted. The draft describes identified use cases and associated problems. Comments are surely welcome. Best regards, Sérgio Figueiredo -------- Original Message -------- Subject: New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-00.txt Date: Mon, 05 Mar 2012 15:53:11 -0800 From: internet-drafts@ietf.org To: sfigueiredo@av.it.pt CC: seiljeon@av.it.pt, ruilaa@ua.pt A new version of I-D, draft-sfigueiredo-multimob-use-case-dmm-00.txt has been successfully submitted by Sergio Figueiredo and posted to the IETF repository. Filename: draft-sfigueiredo-multimob-use-case-dmm Revision: 00 Title: IP Multicast Use Case Analysis for PMIPv6-based Distributed Mobility Management Creation date: 2012-03-05 WG ID: Individual Submission Number of pages: 13 Abstract: As mobile networks are moving towards distributed mobility management, the application of IP multicast is needed to provide efficient content delivery on the network. This document describes use cases when IP multicast is applied on PMIPv6-based DMM, and analyzes problems focused on user plane issues. The IETF Secretariat --------------010806010704050704030909 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Dear all,

A new Internet draft presenting use cases on PMIPv6-based DMM approaches was just submitted. The draft describes identified use cases and associated problems.

Comments are surely welcome.

Best regards,

Sérgio Figueiredo



-------- Original Message --------
Subject: New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-00.txt
Date: Mon, 05 Mar 2012 15:53:11 -0800
From: internet-drafts@ietf.org
To: sfigueiredo@av.it.pt
CC: seiljeon@av.it.pt, ruilaa@ua.pt 


A new version of I-D, draft-sfigueiredo-multimob-use-case-dmm-00.txt has been successfully submitted by Sergio Figueiredo and posted to the IETF repository.

Filename:	 draft-sfigueiredo-multimob-use-case-dmm
Revision:	 00
Title:		 IP Multicast Use Case Analysis for PMIPv6-based Distributed Mobility Management
Creation date:	 2012-03-05
WG ID:		 Individual Submission
Number of pages: 13

Abstract:
   As mobile networks are moving towards distributed mobility management,
   the application of IP multicast is needed to provide efficient
   content delivery on the network. This document describes use cases
   when IP multicast is applied on PMIPv6-based DMM, and analyzes
   problems focused on user plane issues.





                                                                                  


The IETF Secretariat
--------------010806010704050704030909-- From jari.arkko@piuha.net Tue Mar 6 01:13:44 2012 Return-Path: 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 0709021F86AB for ; Tue, 6 Mar 2012 01:13:44 -0800 (PST) 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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zGfwkAWTzU8E for ; Tue, 6 Mar 2012 01:13:43 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id C0FBA21F86A8 for ; Tue, 6 Mar 2012 01:13:41 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 523A72D35A; Tue, 6 Mar 2012 11:13:40 +0200 (EET) X-Virus-Scanned: amavisd-new at piuha.net Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YxG887Kk6hoP; Tue, 6 Mar 2012 11:13:38 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2a00:1d50:2::130]) by p130.piuha.net (Postfix) with ESMTP id 383DE2CC3C; Tue, 6 Mar 2012 11:13:38 +0200 (EET) Message-ID: <4F55D542.6090603@piuha.net> Date: Tue, 06 Mar 2012 11:13:38 +0200 From: Jari Arkko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0 MIME-Version: 1.0 To: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: [multimob] AD review of draft-ietf-multimob-igmp-mld-tuning X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 09:13:44 -0000 I have reviewed this draft. Thanks for writing the draft, I think it provides solid advice. There are a couple issues in the draft but I have decided to send the draft forward for an IETF last call. But I would appreciate a quick response of my issues and if necessary, a draft update this week. A couple of comments below: > Therefore, in this document it is RECOMMENDED that adjacent upstream > multicast routers enable the explicit tracking function for IP > multicast communications on wireless and mobile networks, if they > have enough resources. But draft-ietf-pim-explicit-tracking is an informational reference. I think you should loosen the language above (maybe "it is recommended ...") unless you want to introduce a normative reference and possible wait until the other document is approved as an RFC. > This document proposes 150 seconds for the [Query Interval] value by > changing the Querier's Query Interval Code (QQIC) field specified in > the IGMP/MLD Query message, for the case that a router enabling the > explicit tracking function sends General Query and potentially > operates a large number of member hosts such as more than 200 hosts > on the wireless link. This longer interval value contributes to > minimizing traffic of Report messages and battery power consumption > for mobile hosts. > > On the other hand, this document also proposes 60 to 90 seconds for > the [Query Interval] value for the case that a router enabling the > explicit tracking function attaches to a wireless link having higher > capacity of the resource. This shorter interval contributes to quick > synchronization of the membership information tracked by the router > but MAY consume battery power of mobile hosts. > I had some trouble parsing the recommendations here. Are you recommending 150 seconds when explicit tracking is in use? Or only when there are > 200 hosts? And in the second paragraph, what do you mean by "having higher capacity of the resource"? What resource? Did you just mean to say "... a wireless link with higher capacity"? > a gradual manner until it exceeds the mobile host's lifetime. > Perhaps you meant mobile host's binding lifetime? :-) Or some MLD lifetime value in the hosts? And what do you do if the various mobile hosts have different lifetimes? > For a router > that attaches to a wireless link having higher capacity of the > resource or reliable condition Just say "having higher capacity or is known to be reliable". > When a receiver host connects directly through a wireless link to a > foreign access router or a home router, the tuning of the IGMP/MLD > protocol parameters SHOULD be the same as suggested in the previous > sections. The example of this scenario occurs when route > optimization is adopted in MIPv6 [8 ] or Mobile IP [11 ], or when in > Proxy Mobile IPv6 (PMIPv6) [7 ], the mobile access gateway, whose role > is similar to the one of a foreign router, acts as a multicast > router. I do not understand what route optimization has to do with this, given that it does not support multicast... Suggest deleting the route optimization part and just leaving the PMIP part of the last sentence. > between host and home router is used to exchange IGMP/MLD messages > such as [8 ][11]. ... such as in [8][11]. > This document assumes that both multicast routers and mobile hosts > MUST be IGMPv3/MLDv2 capable, regardless whether the protocols are > the full or lightweight version. And this document does not consider > interoperability with older version protocols. The main reason not > being interoperable with older IGMP/MLD protocols is that the > explicit tracking function does not work properly with older IGMP/MLD > protocols. Please expand this a bit. Explicit tracking in the routers does not work well when older IGMP/MLD versions are in the hosts? How widespread are those older implementations? Can you provide some further advice? Jari From iesg-secretary@ietf.org Tue Mar 6 07:54:11 2012 Return-Path: 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 DAB6F21F8913; Tue, 6 Mar 2012 07:54:11 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.563 X-Spam-Level: X-Spam-Status: No, score=-102.563 tagged_above=-999 required=5 tests=[AWL=0.036, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CY5lxZbFbxQU; Tue, 6 Mar 2012 07:54:11 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 567BC21F8722; Tue, 6 Mar 2012 07:54:11 -0800 (PST) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120306155411.24195.54070.idtracker@ietfa.amsl.com> Date: Tue, 06 Mar 2012 07:54:11 -0800 Cc: multimob@ietf.org Subject: [multimob] Last Call: (Tuning the Behavior of IGMP and MLD for Routers in Mobile and Wireless Networks) to Informational RFC X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: ietf@ietf.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 15:54:12 -0000 The IESG has received a request from the Multicast Mobility WG (multimob) to consider the following document: - 'Tuning the Behavior of IGMP and MLD for Routers in Mobile and Wireless Networks' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the ietf@ietf.org mailing lists by 2012-03-20. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract IGMP and MLD are the protocols used by hosts and multicast routers to exchange their IP multicast group memberships with each other. This document describes the ways of IGMPv3 and MLDv2 protocol optimization for mobility, and aims to become a guideline for tuning of IGMPv3/ MLDv2 Queries and timer and counter values. The file can be obtained via http://datatracker.ietf.org/doc/draft-ietf-multimob-igmp-mld-tuning/ IESG discussion can be tracked via http://datatracker.ietf.org/doc/draft-ietf-multimob-igmp-mld-tuning/ballot/ No IPR declarations have been submitted directly on this I-D. From sarikaya2012@gmail.com Tue Mar 6 10:01:18 2012 Return-Path: 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 3EA2E11E8076; Tue, 6 Mar 2012 10:01:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.559 X-Spam-Level: X-Spam-Status: No, score=-3.559 tagged_above=-999 required=5 tests=[AWL=0.040, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T-b4eBqsruVS; Tue, 6 Mar 2012 10:01:17 -0800 (PST) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 01C0711E8075; Tue, 6 Mar 2012 10:01:16 -0800 (PST) Received: by yenm5 with SMTP id m5so2694071yen.31 for ; Tue, 06 Mar 2012 10:01:16 -0800 (PST) Received-SPF: pass (google.com: domain of sarikaya2012@gmail.com designates 10.100.212.4 as permitted sender) client-ip=10.100.212.4; Authentication-Results: mr.google.com; spf=pass (google.com: domain of sarikaya2012@gmail.com designates 10.100.212.4 as permitted sender) smtp.mail=sarikaya2012@gmail.com; dkim=pass header.i=sarikaya2012@gmail.com Received: from mr.google.com ([10.100.212.4]) by 10.100.212.4 with SMTP id k4mr11017503ang.35.1331056876689 (num_hops = 1); Tue, 06 Mar 2012 10:01:16 -0800 (PST) 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:cc :content-type; bh=/UOmZnrLLoalj4P7TkM81us1dI7BTG9DibDqj7dwleo=; b=N23e7FlM+0pxBKCFUljMoaCfXKhy3jLtlm9qgcfRMVzyTaXNNh20rdBTp1sjB6rlpD KIqPm7UdFvyTITgDLOXAA3aokzjMbXl6AhBKXJjxpJ7ukeoxHo3PDXAkd3GRCzyrKVF2 SQiOLryUQSjtpAgjaOAuLtZJQA3Pzn+kocmi15pmhQ2cXxrfplNWN2D66dBeUlf87qMD Uisaj44WDI1xsE7kn8kTPn9xY9IqrlPNwvMrqpQRRRUHpiHByr/63woGjYwFwuebdryd UY17fFFwe/zc+WlazfqG+8uCDgLj9Cr2iI+cgu/vKA5ADsAGAERREBZ6ao4UmPWQDjdG 3iLQ== MIME-Version: 1.0 Received: by 10.100.212.4 with SMTP id k4mr8727102ang.35.1331056876570; Tue, 06 Mar 2012 10:01:16 -0800 (PST) Received: by 10.236.9.73 with HTTP; Tue, 6 Mar 2012 10:01:16 -0800 (PST) Date: Tue, 6 Mar 2012 12:01:16 -0600 Message-ID: From: Behcet Sarikaya To: dmm@ietf.org, netext@ietf.org, mip4@ietf.org, multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [multimob] FMC Bar BoF at IETF 83 X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 06 Mar 2012 18:01:18 -0000 This is to announce that we have requested a slot for a Bar BoF in Paris on Fixed Mobile Convergence as follows: Tuesday March 28 at 19:30 There has been (business) announcements in the internet like beyond stating that FMC is currently still a hot topic (and finally a MUST facing decreasing revenue challenges) for many network and service operators - reflected in the manufacturing industry for infrastructure equipment as well as user terminals - and creating requirements on the interworking between fixed and mobile networks which - from an Intarea point of view - focus on - User Equipment identification and authentication, - Femto Access Point management, - user device type identification and - mobility considerations e.g. as support within fixed networks and differentiation on different session flows from terminal/user perspective. see also http://tools.ietf.org/html/draft-xue-intarea-fmc-ps-00 In the Bar BOF we want to discuss these issues and eventually others. If you have a presentation to make, drop us a note. Behcet & Dirk From multimob2011@gmail.com Tue Mar 6 19:46:06 2012 Return-Path: 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 B761921E802F for ; Tue, 6 Mar 2012 19:46:06 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.598 X-Spam-Level: X-Spam-Status: No, score=-3.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d1bRc39RqL2b for ; Tue, 6 Mar 2012 19:46:05 -0800 (PST) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A3FEE21E8013 for ; Tue, 6 Mar 2012 19:46:05 -0800 (PST) Received: by iazz13 with SMTP id z13so9301034iaz.31 for ; Tue, 06 Mar 2012 19:46:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=nmzTI26mKt93nk0t7cNXwQudXIvXFHzO6w5WIaJjxzk=; b=x56cdDMkH1dJGeZCDjSrinptpBp4La4pvkaA3B9Y0dgCaTXVkBkspGrohfKbCxITVZ G2Q1n2yvGwb2vsStgyqv+0+d46pMjMleBVWffttwnooTB8nZ8ihQkXo4hd7MrIgLVA2X avaZK3kv6L73T1wYoGOcPc8wZDTDAj3DOWpDrhXnHQ7gUShKTJ2SkwuM5AeW56A3ju1T pNzIk4+UuJ2NQaaj3ObzizXImeTS+IW9mH0TYno4hocOsJ7YPG40TqZ24Dvx8i7942Em YBTPgtOdXVqpo+RkecAX3C+DRhQ4M+I9/EXjIdY3lCqvMw69PlDnOIYPvs627c/XxE1y SfOg== MIME-Version: 1.0 Received: by 10.50.46.164 with SMTP id w4mr10684031igm.54.1331091965275; Tue, 06 Mar 2012 19:46:05 -0800 (PST) Received: by 10.50.173.2 with HTTP; Tue, 6 Mar 2012 19:46:05 -0800 (PST) In-Reply-To: References: Date: Wed, 7 Mar 2012 11:46:05 +0800 Message-ID: From: Aaron Feng To: "Zuniga, Juan Carlos" Content-Type: multipart/alternative; boundary=14dae9340e63c0ee1d04ba9effa2 Cc: multimob@ietf.org Subject: Re: [multimob] FW: New Version Notification for draft-ietf-multimob-pmipv6-ropt-00.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 03:46:06 -0000 --14dae9340e63c0ee1d04ba9effa2 Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm not sure about how the MAG match the MTMA? Here are two ways in my opinion. 1) The MAG can ONLY matches ONE MTMA while MTMA can match some MAGs 2) The multicast address can be divided into different sets and each MTMA is responsible for each specific set, in that way, MAG can match different MTMAs. Both can avoid tunnel convergence. However, maybe you have another idea. What's your choice? Regards, Aaron 2012/3/6 Zuniga, Juan Carlos > Dear all, > > We have uploaded the joint solution WG draft to the "PMIPv6 routing > optimizations to avoid tunnel convergence" problem. We tried to address the > comments received on the list as well as during the meeting. > > http://www.ietf.org/internet-drafts/draft-ietf-multimob-pmipv6-ropt-00.txt > > Your comments on the new draft are appreciated. > > We look forward to discussing with you on the list and at the Paris > meeting. > > Best regards, > > Juan-Carlos, et al. > > > > -----Original Message----- > > From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] > > Sent: Monday, March 05, 2012 11:52 AM > > To: lmcm@tid.es > > Cc: seiljeon@av.it.pt; yhkim@dcn.ssu.ac.kr; Zuniga, Juan Carlos; > > cjbc@it.uc3m.es > > Subject: New Version Notification for draft-ietf-multimob-pmipv6-ropt- > > 00.txt > > > > A new version of I-D, draft-ietf-multimob-pmipv6-ropt-00.txt has been > > successfully submitted by Luis M. Contreras and posted to the IETF > > repository. > > > > Filename: draft-ietf-multimob-pmipv6-ropt > > Revision: 00 > > Title: Multicast Mobility Routing Optimizations for Proxy > > Mobile IPv6 > > Creation date: 2012-03-04 > > WG ID: multimob > > Number of pages: 29 > > > > 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 deployments scenarios. > > > > > > > > > > The IETF Secretariat > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > --14dae9340e63c0ee1d04ba9effa2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi,=A0
I'm not sure about how the MAG match the MTMA? =A0Here are t= wo ways in my opinion. =A0=A0
1) The MAG can ONLY matches ONE MTMA whil= e MTMA can match some MAGs=A0
2) The multicast address can be div= ided into different sets and each MTMA is responsible for each specific set= , in that way, MAG can match different MTMAs.
Both can avoid tunnel convergence. =A0However, maybe you have another = idea. What's your choice?=A0 =A0
Regards,
Aaron =A0= =A0





2012/3/6 Zuniga, Juan Carlos <JuanCarlos.Zuniga@interdigital.com>
Dear all,

We have uploaded the joint solution WG draft to the "PMIPv6 routing op= timizations to avoid tunnel convergence" problem. We tried to address = the comments received on the list as well as during the meeting.

http://www.ietf.org/internet-drafts/draft-iet= f-multimob-pmipv6-ropt-00.txt

Your comments on the new draft are appreciated.

We look forward to discussing with you on the list and at the Paris meeting= .

Best regards,

Juan-Carlos, et al.


> -----Original Message-----
> From: internet-drafts@ietf= .org [mailto:internet-draft= s@ietf.org]
> Sent: Monday, March 05, 2012 11:52 AM
> To: lmcm@tid.es
> Cc: seiljeon@av.it.pt; yhkim@dcn.ssu.ac.kr; Zuniga, Juan Carl= os;
> cjbc@it.uc3m.es
> Subject: New Version Notification for draft-ietf-multimob-pmipv6-ropt-=
> 00.txt
>
> A new version of I-D, draft-ietf-multimob-pmipv6-ropt-00.txt has been<= br> > successfully submitted by Luis M. Contreras and posted to the IETF
> repository.
>
> Filename: =A0 =A0 =A0draft-ietf-multimob-pmipv6-ropt
> Revision: =A0 =A0 =A000
> Title: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 Multicast Mobility Routing Opti= mizations for Proxy
> Mobile IPv6
> Creation date: =A0 =A0 =A0 =A0 2012-03-04
> WG ID: =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 multimob
> Number of pages: 29
>
> Abstract:
> =A0 =A0The MULTIMOB group has specified a base solution to support IP<= br> > =A0 =A0multicasting in a PMIPv6 domain [RFC6224]. =A0In this document,= some
> =A0 =A0enhancements to the base solution are described. =A0These enhan= cements
> =A0 =A0include the use of a multicast tree mobility anchor as the
> =A0 =A0topological anchor point for multicast traffic, as well as a di= rect
> =A0 =A0routing option where the MAG can provide access to multicast co= ntent
> =A0 =A0in the local network. =A0These enhancements provide benefits su= ch as
> =A0 =A0reducing multicast traffic replication and supporting different=
> =A0 =A0PMIPv6 deployments scenarios.
>
>
>
>
> The IETF Secretariat
_______________________________________________
multimob mailing list
multimob@ietf.org
https://www.ietf.org/mailman/listinfo/multimob

--14dae9340e63c0ee1d04ba9effa2-- From asaeda@sfc.wide.ad.jp Tue Mar 6 20:19:31 2012 Return-Path: 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 5E12621E8048 for ; Tue, 6 Mar 2012 20:19:31 -0800 (PST) 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OORyOgWhcIb8 for ; Tue, 6 Mar 2012 20:19:30 -0800 (PST) Received: from mail.sfc.wide.ad.jp (shonan.sfc.wide.ad.jp [203.178.142.130]) by ietfa.amsl.com (Postfix) with ESMTP id 6263121E8039 for ; Tue, 6 Mar 2012 20:19:30 -0800 (PST) Received: from localhost (p17150-ipngn201hodogaya.kanagawa.ocn.ne.jp [114.177.0.150]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id EC81F2780E7; Wed, 7 Mar 2012 13:19:26 +0900 (JST) Date: Wed, 07 Mar 2012 13:19:26 +0900 (JST) Message-Id: <20120307.131926.44862475.asaeda@sfc.wide.ad.jp> To: jari.arkko@piuha.net From: Hitoshi Asaeda In-Reply-To: <4F55D542.6090603@piuha.net> References: <4F55D542.6090603@piuha.net> 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 Cc: multimob@ietf.org Subject: Re: [multimob] AD review of draft-ietf-multimob-igmp-mld-tuning X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 04:19:31 -0000 Hi Jari, Thank you for your review. > Thanks for writing the draft, I think it provides solid advice. There > are a couple issues in the draft but I have decided to send the draft > forward for an IETF last call. But I would appreciate a quick response > of my issues and if necessary, a draft update this week. I got it. Please read the following comments and tell us whether our changes are Ok for you. We will submit the revised draft soon just after we receive your reply. > A couple of comments below: > >> Therefore, in this document it is RECOMMENDED that adjacent upstream >> multicast routers enable the explicit tracking function for IP >> multicast communications on wireless and mobile networks, if they >> have enough resources. > > But draft-ietf-pim-explicit-tracking is an informational reference. I > think you should loosen the language above (maybe "it is recommended > ...") unless you want to introduce a normative reference and possible > wait until the other document is approved as an RFC. We will change "RECOMMENDED" to "recommended". >> This document proposes 150 seconds for the [Query Interval] value by >> changing the Querier's Query Interval Code (QQIC) field specified in >> the IGMP/MLD Query message, for the case that a router enabling the >> explicit tracking function sends General Query and potentially >> operates a large number of member hosts such as more than 200 hosts >> on the wireless link. This longer interval value contributes to >> minimizing traffic of Report messages and battery power consumption >> for mobile hosts. >> >> On the other hand, this document also proposes 60 to 90 seconds for >> the [Query Interval] value for the case that a router enabling the >> explicit tracking function attaches to a wireless link having higher >> capacity of the resource. This shorter interval contributes to quick >> synchronization of the membership information tracked by the router >> but MAY consume battery power of mobile hosts. > > I had some trouble parsing the recommendations here. Are you > recommending 150 seconds when explicit tracking is in use? Or only > when there are > 200 hosts? Thank you for pointing out. It should be changed to; "This document proposes 150 seconds for the [Query Interval] value by changing the Querier's Query Interval Code (QQIC) field specified in the IGMP/MLD Query message, for the case that a router enables the explicit tracking function and potentially operates a large number of member hosts such as more than 200 hosts on the wireless link." > And in the second paragraph, what do you > mean by "having higher capacity of the resource"? What resource? Did > you just mean to say "... a wireless link with higher capacity"? It should be; "a router enabling the explicit tracking function attaches to a wireless link with higher capacity". >> a gradual manner until it exceeds the mobile host's lifetime. > > Perhaps you meant mobile host's binding lifetime? :-) Or some MLD > lifetime value in the hosts? And what do you do if the various mobile > hosts have different lifetimes? Well, this discussion may need more text, while the detail discussion is not the target of this draft, because it depends on mobile protocols. Hence I'll change the paragraph to; "In situations where Mobile IPv6 [8] is used, when the home agent implements multicast router functionality and multicast data packets are tunneled to and from the home agent, the home agent MAY want to slow down Query periodicity. It happens, for example, when the home agent detects network congestion. In this case, the home agent starts forwarding queries with the default [Query Interval] value and increases the value in a gradual manner. Or do you think it is better to just remove this whole paragraph as it is not congruent to this draft? >> For a router >> that attaches to a wireless link having higher capacity of the >> resource or reliable condition > > Just say "having higher capacity or is known to be reliable". Thanks. Done. >> When a receiver host connects directly through a wireless link to a >> foreign access router or a home router, the tuning of the IGMP/MLD >> protocol parameters SHOULD be the same as suggested in the previous >> sections. The example of this scenario occurs when route >> optimization is adopted in MIPv6 [8 >> ] >> or Mobile IP [11 >> ], >> or when in >> Proxy Mobile IPv6 (PMIPv6) [7 >> ], >> the mobile access gateway, whose role >> is similar to the one of a foreign router, acts as a multicast >> router. > > I do not understand what route optimization has to do with this, given > that it does not support multicast... Suggest deleting the route > optimization part and just leaving the PMIP part of the last sentence. Will do. Thanks. >> between host and home router is used to exchange IGMP/MLD messages >> such as [8 >> ][11]. > > ... such as in [8][11]. Done. >> This document assumes that both multicast routers and mobile hosts >> MUST be IGMPv3/MLDv2 capable, regardless whether the protocols are >> the full or lightweight version. And this document does not consider >> interoperability with older version protocols. The main reason not >> being interoperable with older IGMP/MLD protocols is that the >> explicit tracking function does not work properly with older IGMP/MLD >> protocols. > > > Please expand this a bit. Explicit tracking in the routers does not > work well when older IGMP/MLD versions are in the hosts? How > widespread are those older implementations? Can you provide some > further advice? Older IGMP/MLD protocols have a report suppression mechanism. It means older hosts do not respond their report when they hear reports having the same record. We will change the above sentense with the following sentense. "One of the reasons not being interoperable with older IGMP/MLD protocols is that the explicit tracking function does not work properly with older IGMP/MLD protocols because of a report suppression mechanism; a host would not send a pending IGMP/MLD report if a similar report was sent by another listener on the link." Again, thank you for your review. Regards, -- Hitoshi Asaeda From jari.arkko@piuha.net Tue Mar 6 22:17:56 2012 Return-Path: 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 A9C7A21E807D for ; Tue, 6 Mar 2012 22:17:56 -0800 (PST) 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=[BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9cRiQsPzQmHW for ; Tue, 6 Mar 2012 22:17:55 -0800 (PST) Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7E221E8010 for ; Tue, 6 Mar 2012 22:17:55 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id E4C472DA06; Wed, 7 Mar 2012 08:17:50 +0200 (EET) X-Virus-Scanned: amavisd-new at piuha.net Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbaKkKqYz91T; Wed, 7 Mar 2012 08:17:49 +0200 (EET) Received: from [127.0.0.1] (p130.piuha.net [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 0370A2CC3C; Wed, 7 Mar 2012 08:17:48 +0200 (EET) Message-ID: <4F56FD8C.6070107@piuha.net> Date: Wed, 07 Mar 2012 08:17:48 +0200 From: Jari Arkko User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20120129 Thunderbird/10.0 MIME-Version: 1.0 To: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org References: <4F55D542.6090603@piuha.net> In-Reply-To: <4F55D542.6090603@piuha.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [multimob] AD review of draft-ietf-multimob-igmp-mld-tuning X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 06:17:56 -0000 > > A couple of comments below: > > > >> Therefore, in this document it is RECOMMENDED that adjacent upstream > >> multicast routers enable the explicit tracking function for IP > >> multicast communications on wireless and mobile networks, if they > >> have enough resources. > > > > But draft-ietf-pim-explicit-tracking is an informational reference. I > > think you should loosen the language above (maybe "it is recommended > > ...") unless you want to introduce a normative reference and possible > > wait until the other document is approved as an RFC. > > We will change "RECOMMENDED" to "recommended". OK > > >> This document proposes 150 seconds for the [Query Interval] value by > >> changing the Querier's Query Interval Code (QQIC) field specified in > >> the IGMP/MLD Query message, for the case that a router enabling the > >> explicit tracking function sends General Query and potentially > >> operates a large number of member hosts such as more than 200 hosts > >> on the wireless link. This longer interval value contributes to > >> minimizing traffic of Report messages and battery power consumption > >> for mobile hosts. > >> > >> On the other hand, this document also proposes 60 to 90 seconds for > >> the [Query Interval] value for the case that a router enabling the > >> explicit tracking function attaches to a wireless link having higher > >> capacity of the resource. This shorter interval contributes to quick > >> synchronization of the membership information tracked by the router > >> but MAY consume battery power of mobile hosts. > > > > I had some trouble parsing the recommendations here. Are you > > recommending 150 seconds when explicit tracking is in use? Or only > > when there are> 200 hosts? > > Thank you for pointing out. > It should be changed to; > "This document proposes 150 seconds for the [Query Interval] value > by changing the Querier's Query Interval Code (QQIC) field specified > in the IGMP/MLD Query message, for the case that a router enables > the explicit tracking function and potentially operates a large > number of member hosts such as more than 200 hosts on the wireless > link." Looks good. > > > And in the second paragraph, what do you > > mean by "having higher capacity of the resource"? What resource? Did > > you just mean to say "... a wireless link with higher capacity"? > > It should be; "a router enabling the explicit tracking function > attaches to a wireless link with higher capacity". OK > > >> a gradual manner until it exceeds the mobile host's lifetime. > > > > Perhaps you meant mobile host's binding lifetime? :-) Or some MLD > > lifetime value in the hosts? And what do you do if the various mobile > > hosts have different lifetimes? > > Well, this discussion may need more text, while the detail discussion > is not the target of this draft, because it depends on mobile > protocols. > Hence I'll change the paragraph to; > > "In situations where Mobile IPv6 [8] is used, when the home agent > implements multicast router functionality and multicast data packets > are tunneled to and from the home agent, the home agent MAY want to > slow down Query periodicity. It happens, for example, when the home > agent detects network congestion. In this case, the home agent > starts forwarding queries with the default [Query Interval] value > and increases the value in a gradual manner. This is fine. > > Or do you think it is better to just remove this whole paragraph as it > is not congruent to this draft? > > >> For a router > >> that attaches to a wireless link having higher capacity of the > >> resource or reliable condition > > > > Just say "having higher capacity or is known to be reliable". > > Thanks. Done. OK > > >> When a receiver host connects directly through a wireless link to a > >> foreign access router or a home router, the tuning of the IGMP/MLD > >> protocol parameters SHOULD be the same as suggested in the previous > >> sections. The example of this scenario occurs when route > >> optimization is adopted in MIPv6 [8 > >> ] > >> or Mobile IP [11 > >> ], > >> or when in > >> Proxy Mobile IPv6 (PMIPv6) [7 > >> ], > >> the mobile access gateway, whose role > >> is similar to the one of a foreign router, acts as a multicast > >> router. > > > > I do not understand what route optimization has to do with this, given > > that it does not support multicast... Suggest deleting the route > > optimization part and just leaving the PMIP part of the last sentence. > > Will do. Thanks. OK > > >> between host and home router is used to exchange IGMP/MLD messages > >> such as [8 > >> ][11]. > > > > ... such as in [8][11]. > > Done. OK > > >> This document assumes that both multicast routers and mobile hosts > >> MUST be IGMPv3/MLDv2 capable, regardless whether the protocols are > >> the full or lightweight version. And this document does not consider > >> interoperability with older version protocols. The main reason not > >> being interoperable with older IGMP/MLD protocols is that the > >> explicit tracking function does not work properly with older IGMP/MLD > >> protocols. > > > > > > Please expand this a bit. Explicit tracking in the routers does not > > work well when older IGMP/MLD versions are in the hosts? How > > widespread are those older implementations? Can you provide some > > further advice? > > Older IGMP/MLD protocols have a report suppression mechanism. It means > older hosts do not respond their report when they hear reports having > the same record. > > We will change the above sentense with the following sentense. > > "One of the reasons not being interoperable with older IGMP/MLD > protocols is that the explicit tracking function does not work > properly with older IGMP/MLD protocols because of a report > suppression mechanism; a host would not send a pending IGMP/MLD > report if a similar report was sent by another listener on the link." OK Jari From internet-drafts@ietf.org Tue Mar 6 23:46:46 2012 Return-Path: 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 46B4E21F8513; Tue, 6 Mar 2012 23:46:46 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.579 X-Spam-Level: X-Spam-Status: No, score=-102.579 tagged_above=-999 required=5 tests=[AWL=0.020, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7J8HSpbUaOe; Tue, 6 Mar 2012 23:46:45 -0800 (PST) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FF4321F8508; Tue, 6 Mar 2012 23:46:28 -0800 (PST) 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.00 Message-ID: <20120307074628.17031.38503.idtracker@ietfa.amsl.com> Date: Tue, 06 Mar 2012 23:46:28 -0800 Cc: multimob@ietf.org Subject: [multimob] I-D Action: draft-ietf-multimob-igmp-mld-tuning-05.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Mar 2012 07:46:46 -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 t= he IETF. Title : Tuning the Behavior of IGMP and MLD for Routers in Mobil= e and Wireless Networks Author(s) : Hitoshi Asaeda Hui Liu Qin Wu Filename : draft-ietf-multimob-igmp-mld-tuning-05.txt Pages : 13 Date : 2012-03-06 IGMP and MLD are the protocols used by hosts and multicast routers to exchange their IP multicast group memberships with each other. This document describes the ways of IGMPv3 and MLDv2 protocol optimization for mobility, and aims to become a guideline for tuning of IGMPv3/ MLDv2 Queries and timer and counter values. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multimob-igmp-mld-tuning-05.= txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-multimob-igmp-mld-tuning-05.t= xt From lmcm@tid.es Mon Mar 12 03:32:19 2012 Return-Path: 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 BE55221F86C2 for ; Mon, 12 Mar 2012 03:32:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.88 X-Spam-Level: X-Spam-Status: No, score=-4.88 tagged_above=-999 required=5 tests=[AWL=1.719, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ZBWDl4Jx8Pi1 for ; Mon, 12 Mar 2012 03:32:19 -0700 (PDT) Received: from correo-bck.tid.es (correo-bck.tid.es [195.235.93.200]) by ietfa.amsl.com (Postfix) with ESMTP id 8939021F85EE for ; Mon, 12 Mar 2012 03:32:18 -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 <0M0R00AUUP9TDL@tid.hi.inet> for multimob@ietf.org; Mon, 12 Mar 2012 11:32:17 +0100 (MET) Received: from vanvan (vanvan.hi.inet [10.95.78.49]) by sbrightmailg02.hi.inet (Symantec Messaging Gateway) with SMTP id 6D.CD.02643.0B0DD5F4; Mon, 12 Mar 2012 11:32:17 +0100 (CET) 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 <0M0R00AUPP9SDL@tid.hi.inet> for multimob@ietf.org; Mon, 12 Mar 2012 11:32:16 +0100 (MET) Received: from EXCLU2K7.hi.inet ([10.95.67.65]) by htcasmad1.hi.inet ([192.168.0.1]) with mapi; Mon, 12 Mar 2012 11:32:16 +0100 Date: Mon, 12 Mar 2012 11:32:15 +0100 From: LUIS MIGUEL CONTRERAS MURILLO In-reply-to: <20120312083041.23959.49117.idtracker@ietfa.amsl.com> To: "multimob@ietf.org" Message-id: 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-rams-04.txt Thread-index: Ac0AKmqS4A8HThQlS6a9WTx8U/HgbgAADCLw acceptlanguage: es-ES, en-US X-AuditID: 0a5f4e69-b7f6b6d000000a53-25-4f5dd0b03379 X-MS-Has-Attach: X-MS-TNEF-Correlator: X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrAKsWRmVeSWpSXmKPExsXCFe9nqLvxQqy/we1udosZH/tYHBg9liz5 yRTAGMVlk5Kak1mWWqRvl8CVMX/eaqaCH+IVVw/uZGlgXCHexcjJISFgIjFhdRs7hC0mceHe erYuRi4OIYFtjBLTH39lhXB+M0rsXLGUHcJpZJS4swGkjJODRUBV4u796WA2m4ChxKydk1hB bGEBP4kzTQfBbE4BJ4mF046xgNgiAtoSb17+YQKxmYFqrqz8B1bDK+ApsfdVBxOELSjxY/I9 oHoOoBp1iSlTciHKxSXm/JrICmErSkxb1MAIYjMKyEqsPH+aEWK8v8Sbu2fYIWwjieN/r0DV yEj8X76XBeJLAYkle84zQ9iiEi8fQ5wgJOAo8ebQWbYJjOKzkFwxC+GKWUiumIXkigWMLKsY xYqTijLTM0pyEzNz0g2M9DIy9TLzUks2MUKiKHMH4/KdKocYBTgYlXh4Myyj/IVYE8uKK3MP MUpyMCmJ8q49H+svxJeUn1KZkVicEV9UmpNafIhRgoNZSYQ3azZQjjclsbIqtSgfJiXDwaEk wWsCjHghwaLU9NSKtMwcYKqASTNxcIK08wC1c4LU8BYXJOYWZ6ZD5E8xqnJM+Lj2EqMQS15+ XqqUOK8OSJEASFFGaR7cnFeM4kAHC/O6gGR5gMkObsIroOFMQMM/c0WDDC9JREhJNTB2r7QQ iKnZtWBql4zx5Zt1e1/yXZz/UOq3f/LB53sd0xr+zqlInd3ksuPw+2fnZuzUmDDv9oo54dNz r57yL3p34PPCb5/21Pipd/NHv3zQ4nhH39zvU/n98PW/P4X8bi/ZMpvJyswnvczj9dFv6062 e13mCPPMfRTy+V794lkd4X9VT818dXR5lRJLcUaioRZzUXEiAOHFEVEzAwAA References: <20120312083041.23959.49117.idtracker@ietfa.amsl.com> Subject: [multimob] RV: New Version Notification for draft-contreras-multimob-rams-04.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 10:32:19 -0000 RGVhciBhbGwsDQoNCldlIGhhdmUganVzdCBzdWJtaXR0ZWQgdGhlIHVwZGF0ZSBvZiBkcmFmdC1j b250cmVyYXMtbXVsdGltb2ItcmFtcy4gVGhpcyB2ZXJzaW9uIHRyeSB0byBhZGRyZXNzIHRoZSBj b21tZW50cyBzZW50IHRvIHRoZSBtYWlsaW5nIGxpc3QgZHVyaW5nIHRoZSBwYXN0IHdlZWtzLg0K DQpUaGUgbmV3IHZlcnNpb24gY2FuIGJlIGZvdW5kIGF0OiBodHRwOi8vdG9vbHMuaWV0Zi5vcmcv aHRtbC9kcmFmdC1jb250cmVyYXMtbXVsdGltb2ItcmFtcy0wNC4NCg0KQmVzdCByZWdhcmRzLA0K DQpMdWlzDQoNCi0tLS0tTWVuc2FqZSBvcmlnaW5hbC0tLS0tDQpEZTogaW50ZXJuZXQtZHJhZnRz QGlldGYub3JnIFttYWlsdG86aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnXQ0KRW52aWFkbyBlbDog bHVuZXMsIDEyIGRlIG1hcnpvIGRlIDIwMTIgOTozMQ0KUGFyYTogTFVJUyBNSUdVRUwgQ09OVFJF UkFTIE1VUklMTE8NCkNDOiBpc290b0BkaXQudXBtLmVzOyBjamJjQGl0LnVjM20uZXMNCkFzdW50 bzogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1jb250cmVyYXMtbXVsdGltb2It cmFtcy0wNC50eHQNCg0KQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWNvbnRyZXJhcy1tdWx0 aW1vYi1yYW1zLTA0LnR4dCBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IEx1aXMg TS4gQ29udHJlcmFzIGFuZCBwb3N0ZWQgdG8gdGhlIElFVEYgcmVwb3NpdG9yeS4NCg0KRmlsZW5h bWU6ICAgICAgICBkcmFmdC1jb250cmVyYXMtbXVsdGltb2ItcmFtcw0KUmV2aXNpb246ICAgICAg ICAwNA0KVGl0bGU6ICAgICAgICAgICBQTUlQdjYgbXVsdGljYXN0IGhhbmRvdmVyIG9wdGltaXph dGlvbiBieSB0aGUgUmVxdWVzdCBvZiBBY3RpdmUgTXVsdGljYXN0IFN1YnNjcmlwdGlvbiAoUkFN UykNCkNyZWF0aW9uIGRhdGU6ICAgMjAxMi0wMy0xMA0KV0cgSUQ6ICAgICAgICAgICBJbmRpdmlk dWFsIFN1Ym1pc3Npb24NCk51bWJlciBvZiBwYWdlczogMzcNCg0KQWJzdHJhY3Q6DQogICBUaGlz IGRvY3VtZW50IHNwZWNpZmllcyBhIG11bHRpY2FzdCBoYW5kb3ZlciBvcHRpbWl6YXRpb24gbWVj aGFuaXNtDQogICBmb3IgUHJveHkgTW9iaWxlIElQdjYgdG8gYWNjZWxlcmF0ZSB0aGUgZGVsaXZl cnkgb2YgbXVsdGljYXN0IHRyYWZmaWMNCiAgIHRvIG1vYmlsZSBub2RlcyBhZnRlciBoYW5kb3Zl cnMuIFRoZSBtZWNoYW5pc20gaXMgYmFzZWQgb24gc3BlZWRpbmcNCiAgIHVwIHRoZSBhY3F1aXNp dGlvbiBvZiBtb2JpbGUgbm9kZXMmIzM5OyBhY3RpdmUgbXVsdGljYXN0IHN1YnNjcmlwdGlvbnMN CiAgIGluZm9ybWF0aW9uIGJ5IHRoZSBtb2JpbGUgYWNjZXNzIGdhdGV3YXlzLiBUbyBkbyB0aGF0 LCBleHRlbnNpb25zIHRvDQogICB0aGUgY3VycmVudCBQcm94eSBNb2JpbGUgSVB2NiBwcm90b2Nv bCBhcmUgcHJvcG9zZWQuIFRoZXNlIGV4dGVuc2lvbnMNCiAgIGFyZSBub3Qgb25seSBhcHBsaWNh YmxlIHRvIHRoZSBiYXNlIHNvbHV0aW9uIGZvciBtdWx0aWNhc3Qgc3VwcG9ydCBpbg0KICAgUHJv eHkgTW9iaWxlIElQdjYsIGJ1dCBhbHNvIGNhbiBiZSBhcHBsaWVkIHRvIG90aGVyIHNvbHV0aW9u cw0KICAgZW52aXNpb25lZCBhcyBwb3NzaWJsZSBhcmNoaXRlY3R1cmFsIGV2b2x1dGlvbnMgb2Yg aXQuIEZ1cnRoZXJtb3JlLA0KICAgdGhleSBhcmUgYWxzbyBpbmRlcGVuZGVudCBvZiB0aGUgcm9s ZSBwbGF5ZWQgYnkgdGhlIG1vYmlsZSBhY2Nlc3MNCiAgIGdhdGV3YXkgd2l0aGluIHRoZSBtdWx0 aWNhc3QgbmV0d29yayAoZWl0aGVyIGFjdGluZyBhcyBtdWx0aWNhc3QNCiAgIGxpc3RlbmVyIGRp c2NvdmVyeSBwcm94eSBvciBtdWx0aWNhc3Qgcm91dGVyKS4NCg0KDQoNCg0KDQpUaGUgSUVURiBT ZWNyZXRhcmlhdA0KDQpFc3RlIG1lbnNhamUgc2UgZGlyaWdlIGV4Y2x1c2l2YW1lbnRlIGEgc3Ug ZGVzdGluYXRhcmlvLiBQdWVkZSBjb25zdWx0YXIgbnVlc3RyYSBwb2zDrXRpY2EgZGUgZW52w61v IHkgcmVjZXBjacOzbiBkZSBjb3JyZW8gZWxlY3Ryw7NuaWNvIGVuIGVsIGVubGFjZSBzaXR1YWRv IG3DoXMgYWJham8uDQpUaGlzIG1lc3NhZ2UgaXMgaW50ZW5kZWQgZXhjbHVzaXZlbHkgZm9yIGl0 cyBhZGRyZXNzZWUuIFdlIG9ubHkgc2VuZCBhbmQgcmVjZWl2ZSBlbWFpbCBvbiB0aGUgYmFzaXMg b2YgdGhlIHRlcm1zIHNldCBvdXQgYXQNCmh0dHA6Ly93d3cudGlkLmVzL0VTL1BBR0lOQVMvZGlz Y2xhaW1lci5hc3B4DQo= From sarikaya2012@gmail.com Mon Mar 12 14:24:36 2012 Return-Path: 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 00ECC11E80F3 for ; Mon, 12 Mar 2012 14:24:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.562 X-Spam-Level: X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id usGuBjSXe1Jf for ; Mon, 12 Mar 2012 14:24:35 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id CD42811E80E4 for ; Mon, 12 Mar 2012 14:24:32 -0700 (PDT) Received: by iazz13 with SMTP id z13so8183750iaz.31 for ; Mon, 12 Mar 2012 14:24:32 -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=1Qn9YHp25lKxgYp/c7tWuTsymVo7T9I6UegyftmUBRI=; b=0QGm06R/twWLc7BrCJL3SQE4ZP0HRwE+gdl7nwZKlxjPE5bpgfbRQPMQbuhTYtuOFc rStQG70rd6RedKV3qfnFphHdrj0t2HeAV0Jue6GSHqTXdG2HLgBdYBXOp9ClvaQG2pKy FgsyPVrGMI/pQybEF7E7QJEKf3u/1z0DUsrk6QGBL/e4qtx+9N8EN2OIkhMllTC+6po7 7GXiBQuRiCq4fGE4uYlxsl6XHc2xkhwWk2tbhpaePNBBPtwCg+ZHUL3GkmyFBPeUL40A a9fb71dRBIOM5T4QmbZgkHwKD3JfHbASMo37KYOUb5U01rY32f3qCGf670Nvwbf+WOxc LyEg== MIME-Version: 1.0 Received: by 10.42.131.129 with SMTP id z1mr17321381ics.53.1331587472543; Mon, 12 Mar 2012 14:24:32 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Mon, 12 Mar 2012 14:24:32 -0700 (PDT) Date: Mon, 12 Mar 2012 16:24:32 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [multimob] Presentations X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 21:24:36 -0000 Folks, I posted the agenda which seems to have stabilized. Please send your slides to the chairs. We solicit volunteers for Jabber scibing and taking the minutes, please volunteer. Behcet From sfigueiredo@av.it.pt Mon Mar 12 16:25:04 2012 Return-Path: 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 33ADC21F8A3B for ; Mon, 12 Mar 2012 16:25:04 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.298 X-Spam-Level: X-Spam-Status: No, score=-2.298 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VHiDskyiB3Jt for ; Mon, 12 Mar 2012 16:25:03 -0700 (PDT) Received: from av.it.pt (mail.av.it.pt [193.136.92.53]) by ietfa.amsl.com (Postfix) with ESMTP id C114321F8A14 for ; Mon, 12 Mar 2012 16:25:01 -0700 (PDT) Received: from [217.129.25.167] (account sfigueiredo@av.it.pt HELO [192.168.0.104]) by av.it.pt (CommuniGate Pro SMTP 5.4.2) with ESMTPSA id 63734502 for multimob@ietf.org; Mon, 12 Mar 2012 23:25:00 +0000 Message-ID: <4F5E85CB.3080804@av.it.pt> Date: Mon, 12 Mar 2012 23:24:59 +0000 From: =?UTF-8?B?U8OpcmdpbyBGaWd1ZWlyZWRv?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Lightning/1.0b2 Thunderbird/3.1.16 MIME-Version: 1.0 To: multimob@ietf.org Content-Type: multipart/alternative; boundary="------------060003050100050200080901" Subject: [multimob] Fwd: New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-01.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Mar 2012 23:25:04 -0000 This is a multi-part message in MIME format. --------------060003050100050200080901 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Dear all, An updated version of the Internet draft "IP Multicast Use Case Analysis for PMIPv6â€based Distributed Mobility Management " has been submitted. This version mainly improves the quality and correctness of the previous version. Your comments are very appreciated. We hope it will trigger productive discussions in Paris meeting. Best regards, Sérgio Figueiredo -------- Original Message -------- Subject: New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-01.txt Date: Mon, 12 Mar 2012 15:17:41 -0700 From: internet-drafts@ietf.org To: sfigueiredo@av.it.pt CC: seiljeon@av.it.pt, ruilaa@ua.pt A new version of I-D, draft-sfigueiredo-multimob-use-case-dmm-01.txt has been successfully submitted by Sergio Figueiredo and posted to the IETF repository. Filename: draft-sfigueiredo-multimob-use-case-dmm Revision: 01 Title: IP Multicast Use Case Analysis for PMIPv6.based Distributed Mobility Management Creation date: 2012-03-12 WG ID: Individual Submission Number of pages: 13 Abstract: As mobile networks are moving towards distributed mobility management, the application of IP multicast is needed to provide efficient content delivery on the network. This document describes use cases when IP multicast is applied on PMIPv6-based DMM, and analyzes problems focused on user plane issues. The IETF Secretariat --------------060003050100050200080901 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Dear all,

An updated version of the Internet draft "IP Multicast Use Case Analysis for PMIPv6â€based Distributed Mobility Management " has been submitted. This version mainly improves the quality and correctness of the previous version.

Your comments are very appreciated. We hope it will trigger productive discussions in Paris meeting.


Best regards,

Sérgio Figueiredo


-------- Original Message --------
Subject: New Version Notification for draft-sfigueiredo-multimob-use-case-dmm-01.txt
Date: Mon, 12 Mar 2012 15:17:41 -0700
From: internet-drafts@ietf.org
To: sfigueiredo@av.it.pt
CC: seiljeon@av.it.pt, ruilaa@ua.pt 


A new version of I-D, draft-sfigueiredo-multimob-use-case-dmm-01.txt has been successfully submitted by Sergio Figueiredo and posted to the IETF repository.

Filename:	 draft-sfigueiredo-multimob-use-case-dmm
Revision:	 01
Title:		 IP Multicast Use Case Analysis for PMIPv6.based Distributed Mobility Management
Creation date:	 2012-03-12
WG ID:		 Individual Submission
Number of pages: 13

Abstract:
   As mobile networks are moving towards distributed mobility management,
   the application of IP multicast is needed to provide efficient
   content delivery on the network. This document describes use cases
   when IP multicast is applied on PMIPv6-based DMM, and analyzes
   problems focused on user plane issues.





                                                                                  


The IETF Secretariat
--------------060003050100050200080901-- From sarikaya2012@gmail.com Wed Mar 14 10:03:56 2012 Return-Path: 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 99C3B21F8733; Wed, 14 Mar 2012 10:03:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.56 X-Spam-Level: X-Spam-Status: No, score=-3.56 tagged_above=-999 required=5 tests=[AWL=0.039, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MhEItOpwWvpP; Wed, 14 Mar 2012 10:03:56 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id E2B1C21F85D3; Wed, 14 Mar 2012 10:03:55 -0700 (PDT) Received: by iazz13 with SMTP id z13so3005525iaz.31 for ; Wed, 14 Mar 2012 10:03:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=T8q0ZQ5dYmluJU8Sw/gNCJBNKcqPDqXG+ElJb3vqya8=; b=a02xwRYOaQHlQtturP0YywFr+OG0Cm+Iwd08ceH1fBFoPODWUkiQdZiINM+tAYzHqY HzpEzSszy+MZ59rky3AtXea/wmVOYoOhg7Q6Oag71mAI4+kh/h7DxkHXR3ewceD5L3mC FVB4Oy1dQxV2GMaJ27y+pof/sIQeVUh6n1Ku1hdRrZS9dyXUJteZqdHjFRPF4flG4gHr 1vW/hvUSJexVL8B8BFpU4hyZlSJdgiiuhGchG8OYBaJyKBmIELkNzhZ71F8gPCbDT70x RV7qWB8dyNz3SfMAORCJWKFjcQm7OXz/cJBXkoUwLrq9LqkVY2ffeQ5LOHcOrV18gD0k 7HbA== MIME-Version: 1.0 Received: by 10.50.192.196 with SMTP id hi4mr5664689igc.55.1331744635430; Wed, 14 Mar 2012 10:03:55 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Wed, 14 Mar 2012 10:03:55 -0700 (PDT) In-Reply-To: <20120313221840.16417.11343.idtracker@ietfa.amsl.com> References: <20120313221840.16417.11343.idtracker@ietfa.amsl.com> Date: Wed, 14 Mar 2012 12:03:55 -0500 Message-ID: From: Behcet Sarikaya To: Adrian Farrel Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org, The IESG , multimob-chairs@tools.ietf.org Subject: Re: [multimob] Adrian Farrel's Discuss on draft-ietf-multimob-igmp-mld-tuning-05: (with DISCUSS) X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 17:03:56 -0000 Hi Adrian, Thanks for your comments. My replies to the shepherd related ones are inline. On Tue, Mar 13, 2012 at 5:18 PM, Adrian Farrel wrote: > Adrian Farrel has entered the following ballot position for > draft-ietf-multimob-igmp-mld-tuning-05: Discuss > > When responding, please keep the subject line intact and reply to all > email addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > Please refer to http://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > I like this document: thank you. However, I have some small issues. > > I think the first two of my Discuss issues are small procedural > questions that can be resolved through process rather than changes > to the document. Thus the actions should come from the AD, chairs, > and shepherd. > > The subsequent issues are for the authors. > > --- > > The Shepherd write-up says... > > =A0(7) Has each author confirmed that any and all appropriate IPR > =A0disclosures required for full conformance with the provisions of BCP > 78 > =A0and BCP 79 have already been filed. If not, explain why. > > =A0There have been no IPR disclosures filed on this document > > This is not an answer to the question that was asked. > Since there was no IPR disclosures filed on this document, therefore there was no question of filing the IPR disclosures with proper provisions. So the shepherd thought that this item (Item 7) in the shepherd document was properly answered. > --- > > Was this document sent for review by the PIM working group (that is now > responsible for MLD and IGMP maintenance)? The shepherd write-up tends > to imply not. > > While, as an Informational RFC that does not change the protocol, that > is not strictly necessary, it would have made good sense. I see that one > of the PIM WG chairs is acknowledged for his comments, so perhaps this > received wider review. > I think the author already answered this. Regards, Behcet From sarikaya2012@gmail.com Wed Mar 14 10:32:00 2012 Return-Path: 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 7B23C21E8024; Wed, 14 Mar 2012 10:32:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.561 X-Spam-Level: X-Spam-Status: No, score=-3.561 tagged_above=-999 required=5 tests=[AWL=0.038, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Cv8NqWwIYFmc; Wed, 14 Mar 2012 10:31:58 -0700 (PDT) Received: from mail-ey0-f172.google.com (mail-ey0-f172.google.com [209.85.215.172]) by ietfa.amsl.com (Postfix) with ESMTP id B3C5721F876F; Wed, 14 Mar 2012 10:31:57 -0700 (PDT) Received: by eaaq11 with SMTP id q11so1225066eaa.31 for ; Wed, 14 Mar 2012 10:31:56 -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:cc :content-type; bh=HN2j7MaT2UlhlkYtMZWKHrnueNcLQKQ9zKss7lre2so=; b=NgH+gXNtD/Cg45cNUrn6ivsWAORjHvPIDdXpequ7PMreQwNLssGAFZK2nTwvtXgURo JT1lm7G40itiG213prFJ4qVsEwcnYnWCIbCHNx5m/+2tDp0JIocR+X2i3eXKzfOv79eZ ++Uk5BsOzu4WpraYOlNSzQ2gS0UqQ0SJQ16tjpJ7elc9nOn7yFXYBzpfQXAtjrvW0zkJ PTL+av72T6VxTBygp9aHfm7J6i4lUkYUgDkxUmkvY524KNot2t8dm75eawCAShUxVRBH GYASltmRnqGCSUhfL4b07NLidPLBsJo9ST7LknQE5OyJV8ZKxuVKp5I7AB+ll7MoLMiB Y5PQ== MIME-Version: 1.0 Received: by 10.50.193.131 with SMTP id ho3mr12922385igc.55.1331746315934; Wed, 14 Mar 2012 10:31:55 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Wed, 14 Mar 2012 10:31:55 -0700 (PDT) Date: Wed, 14 Mar 2012 12:31:55 -0500 Message-ID: From: Behcet Sarikaya To: Internet Area , dmm@ietf.org, netext@ietf.org, mip4@ietf.org, multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [multimob] FMC Bar Bof Date Correction X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 17:32:00 -0000 Hi all, Our previous mail on March 6 announcing FMC Bar Bof had by mistake the date as March 28. Tuesday March 27 at 19:30 or 7:30pm is the correct one. We are going to send another mail once this is confirmed by IETF. Sorry for the confusion and thanks to Wassim, Med, Sophie for waking us up :-). Behcet ------------------------------------------------------------------------------------------------------------------------------ Hi all, FMC Problem Statement draft draft-xue-intarea-fmc-ps-00.txt has been submitted as below. We also requested a slot for holding FMC Bar Bof tentatively on Tuesday, March 28 at 19:30. If you have a presentation to make please drop a note to us. Regards, Behcet & Dirk From sarikaya2012@gmail.com Wed Mar 14 15:56:06 2012 Return-Path: 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 4110E21F8712; Wed, 14 Mar 2012 15:56:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.562 X-Spam-Level: X-Spam-Status: No, score=-3.562 tagged_above=-999 required=5 tests=[AWL=0.037, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HzKaJ91LyStr; Wed, 14 Mar 2012 15:56:04 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 5405C21F8731; Wed, 14 Mar 2012 15:56:04 -0700 (PDT) Received: by iazz13 with SMTP id z13so3411853iaz.31 for ; Wed, 14 Mar 2012 15:56:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=SGlvcE7CuJiUMKXwPpKkyFuBo43vTDWMyBkTQ46PD4M=; b=v3A8ez/UhzNYOulULMQcumx1Ryh95wM2pa+FHNLpbulip+GJfIWZupVs5tzxFFbJ8n 6fJhU9Sx44j8/iOpp3E+PacZcnWQHQsrryq5nuiKsVvSkrCVU/yIIloXuowDLtEXc20l HHSJwXI6z1nVpY8dUq0Fu3CgksOvu5MUqTX7b01YDlwjx/xfseIx6wOuz62qblltSCLx 6pjLdQFoG6zjliQX0M4ecdSPHwSsj5RBts/4iZTMk6ucF3tpmfCwjOVkuUIZ/Z4ryI+R 9/IFxdulbH5dmTizbNfumXO3uKPYGmCkxkYh6TcV/S+79n+sRjJxKQ0jkqxtEAFGhsqq +DIg== MIME-Version: 1.0 Received: by 10.50.207.72 with SMTP id lu8mr7502693igc.0.1331765763974; Wed, 14 Mar 2012 15:56:03 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Wed, 14 Mar 2012 15:56:03 -0700 (PDT) In-Reply-To: <035701cd0231$8ee8d8d0$acba8a70$@olddog.co.uk> References: <20120313221840.16417.11343.idtracker@ietfa.amsl.com> <035701cd0231$8ee8d8d0$acba8a70$@olddog.co.uk> Date: Wed, 14 Mar 2012 17:56:03 -0500 Message-ID: From: Behcet Sarikaya To: adrian@olddog.co.uk Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org, The IESG , multimob-chairs@tools.ietf.org Subject: Re: [multimob] Adrian Farrel's Discuss on draft-ietf-multimob-igmp-mld-tuning-05: (with DISCUSS) X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 22:56:06 -0000 Hi Adrian, On Wed, Mar 14, 2012 at 5:26 PM, Adrian Farrel wrote: > Hi Behcet, > > Thanks for this. > >> > The Shepherd write-up says... >> > >> > =A0(7) Has each author confirmed that any and all appropriate IPR >> > =A0disclosures required for full conformance with the provisions of BC= P >> > =A078 =A0and BCP 79 have already been filed. If not, explain why. >> > >> > =A0There have been no IPR disclosures filed on this document >> > >> > This is not an answer to the question that was asked. >> >> Since there was no IPR disclosures filed on this document, therefore >> there was no question of filing the IPR disclosures with proper >> provisions. So the shepherd thought that this item (Item 7) in the >> shepherd document was properly answered. > > The specific question in the write-up is "Has each author confirmed...?" = not > "Have any disclosure been made?" > > This is normally tested by an email to each author with the specific ques= tion > "Can you confirm...?" and a response from each author. > Yes, that could be done. However, isn't it better to get the sherpherd document Item 7 to be modified slightly, instead of the current form: (7) Has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why. To something like: (7) If an IPR claim has been made, has each author confirmed that any and all appropriate IPR disclosures required for full conformance with the provisions of BCP 78 and BCP 79 have already been filed. If not, explain why. Then the shepherd could simply reply N/A to this item if no IPR claim exist= s. Regards, Behcet > Thanks, > Adrian > From bill.wu@huawei.com Wed Mar 14 22:58:41 2012 Return-Path: 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 DD2FB21F8758; Wed, 14 Mar 2012 22:58:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.512 X-Spam-Level: X-Spam-Status: No, score=-5.512 tagged_above=-999 required=5 tests=[AWL=1.087, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CRAOPWb1P6El; Wed, 14 Mar 2012 22:58:41 -0700 (PDT) Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [119.145.14.64]) by ietfa.amsl.com (Postfix) with ESMTP id D915321F8755; Wed, 14 Mar 2012 22:58:40 -0700 (PDT) Received: from huawei.com (szxga05-in [172.24.2.49]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0W0029RWJZKV@szxga05-in.huawei.com>; Thu, 15 Mar 2012 13:57:35 +0800 (CST) Received: from szxrg01-dlp.huawei.com ([172.24.2.119]) by szxga05-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0M0W00082WJZVW@szxga05-in.huawei.com>; Thu, 15 Mar 2012 13:57:35 +0800 (CST) Received: from szxeml214-edg.china.huawei.com ([172.24.2.119]) by szxrg01-dlp.huawei.com (MOS 4.1.9-GA) with ESMTP id AHL78155; Thu, 15 Mar 2012 13:57:35 +0800 Received: from SZXEML410-HUB.china.huawei.com (10.82.67.137) by szxeml214-edg.china.huawei.com (172.24.2.29) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Mar 2012 13:56:40 +0800 Received: from w53375 (10.138.41.149) by szxeml410-hub.china.huawei.com (10.82.67.137) with Microsoft SMTP Server (TLS) id 14.1.323.3; Thu, 15 Mar 2012 13:57:26 +0800 Date: Thu, 15 Mar 2012 13:57:25 +0800 From: Qin Wu X-Originating-IP: [10.138.41.149] To: Pete Resnick , sarikaya@ieee.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.6109 X-Mailer: Microsoft Outlook Express 6.00.2900.5931 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-CFilter-Loop: Reflected References: <20120313221840.16417.11343.idtracker@ietfa.amsl.com> <035701cd0231$8ee8d8d0$acba8a70$@olddog.co.uk> <4F61726C.9020507@qualcomm.com> Cc: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org, multimob-chairs@tools.ietf.org, The IESG , adrian@olddog.co.uk, Behcet Sarikaya Subject: Re: [multimob] Adrian Farrel's Discuss on draft-ietf-multimob-igmp-mld-tuning-05: (with DISCUSS) X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 05:58:42 -0000 At the request of item (7) and this call, I like to confirm that I have no IPR and also not aware of any IPR that is related to this document. Thanks! Regards! -Qin WU ----- Original Message ----- From: "Pete Resnick" To: Cc: "Behcet Sarikaya" ; ; ; ; "The IESG" ; Sent: Thursday, March 15, 2012 12:39 PM Subject: Re: Adrian Farrel's Discuss on draft-ietf-multimob-igmp-mld-tuning-05: (with DISCUSS) > On 3/14/12 5:56 PM, Behcet Sarikaya wrote: >> On Wed, Mar 14, 2012 at 5:26 PM, Adrian Farrel wrote: >> >>> The specific question in the write-up is "Has each author >>> confirmed...?" not >>> "Have any disclosure been made?" >>> >>> This is normally tested by an email to each author with the specific question >>> "Can you confirm...?" and a response from each author. >>> >> Yes, that could be done. >> >> However, isn't it better to get the sherpherd document Item 7 to be >> modified slightly, instead of the current form: >> (7) Has each author confirmed that any and all appropriate IPR >> disclosures required for full conformance with the provisions of BCP >> 78 and BCP 79 have already been filed. If not, explain why. >> >> To something like: >> >> (7) If an IPR claim has been made, has each author confirmed that any >> and all appropriate IPR >> disclosures required for full conformance with the provisions of BCP >> 78 and BCP 79 have already been filed. If not, explain why. >> >> Then the shepherd could simply reply N/A to this item if no IPR claim exists. >> > > No, that is not sufficient. We have had several occasions where no > disclosure was made, only to find out after publication that one of the > authors of the document was a patent holder on technology that was in > the draft. We do actually want you to ask the question of the authors. > > pr > -- > Pete Resnick > Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 > From adrian@olddog.co.uk Wed Mar 14 16:01:10 2012 Return-Path: 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 97EC921F8783; Wed, 14 Mar 2012 16:01:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.387 X-Spam-Level: X-Spam-Status: No, score=-2.387 tagged_above=-999 required=5 tests=[AWL=0.212, BAYES_00=-2.599] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NZWY14bHnktM; Wed, 14 Mar 2012 16:01:09 -0700 (PDT) Received: from asmtp5.iomartmail.com (asmtp5.iomartmail.com [62.128.201.176]) by ietfa.amsl.com (Postfix) with ESMTP id E12EB21F8732; Wed, 14 Mar 2012 16:01:03 -0700 (PDT) Received: from asmtp5.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q2EMQo82024171; Wed, 14 Mar 2012 22:26:51 GMT Received: from 950129200 ([90.84.146.227]) (authenticated bits=0) by asmtp5.iomartmail.com (8.13.8/8.13.8) with ESMTP id q2EMQesK024108 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 14 Mar 2012 22:26:49 GMT From: "Adrian Farrel" To: References: <20120313221840.16417.11343.idtracker@ietfa.amsl.com> In-Reply-To: Date: Wed, 14 Mar 2012 22:26:42 -0000 Message-ID: <035701cd0231$8ee8d8d0$acba8a70$@olddog.co.uk> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQHluZu9zriRYe4d1L+YKbQap/KMJwJlAYR7liW6GRA= Content-Language: en-gb X-Mailman-Approved-At: Thu, 15 Mar 2012 08:22:47 -0700 Cc: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org, 'The IESG' , multimob-chairs@tools.ietf.org Subject: Re: [multimob] Adrian Farrel's Discuss on draft-ietf-multimob-igmp-mld-tuning-05: (with DISCUSS) X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: adrian@olddog.co.uk List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Mar 2012 23:01:10 -0000 Hi Behcet, Thanks for this. > > The Shepherd write-up says... > > > > =A0(7) Has each author confirmed that any and all appropriate IPR > > =A0disclosures required for full conformance with the provisions of = BCP > > 78 =A0and BCP 79 have already been filed. If not, explain why. > > > > =A0There have been no IPR disclosures filed on this document > > > > This is not an answer to the question that was asked. >=20 > Since there was no IPR disclosures filed on this document, therefore > there was no question of filing the IPR disclosures with proper > provisions. So the shepherd thought that this item (Item 7) in the > shepherd document was properly answered. The specific question in the write-up is "Has each author confirmed...?" = not "Have any disclosure been made?" This is normally tested by an email to each author with the specific = question "Can you confirm...?" and a response from each author. Thanks, Adrian From presnick@qualcomm.com Wed Mar 14 21:39:14 2012 Return-Path: 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 7952821F854B; Wed, 14 Mar 2012 21:39:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -106.57 X-Spam-Level: X-Spam-Status: No, score=-106.57 tagged_above=-999 required=5 tests=[AWL=0.029, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Wk7eSBtkuSHa; Wed, 14 Mar 2012 21:39:13 -0700 (PDT) Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id F158411E8074; Wed, 14 Mar 2012 21:39:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1331786353; x=1363322353; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F61726C.9020507@qualcomm.com>|Date:=20We d,=2014=20Mar=202012=2023:39:08=20-0500|From:=20Pete=20Re snick=20|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20|CC:=20Behc et=20Sarikaya=20,=20,=0D=0A=09,=20,=0D=0A=09The=20IESG =20,=20 |Subject:=20Re:=20Adrian=20Farrel's=20Discuss=20on=20draf t-ietf-multimob-igmp-mld-tuning-05:=0D=0A=20(with=20DISCU SS)|References:=20<20120313221840.16417.11343.idtracker@i etfa.amsl.com>=09=09<035701cd0231$8ee8d8d0 $acba8a70$@olddog.co.uk>=20|In-Reply-To:=20|Content-Type:=20text/plain=3B=20charset=3D"ISO-8 859-1"=3B=20format=3Dflowed|Content-Transfer-Encoding:=20 7bit|X-Originating-IP:=20[172.30.39.5]; bh=+mNu267QVtsYWjDKuBO2gx2LXUWPhfmhL/xqdKexfi8=; b=MgFcKXJ0JcjB57STXnFjP6tUK6PzQza4zZXfF+PqE2mWKIvrSp9MokWT nP7TenpsIQDQQg40EoKaDut/o6pL1GExnULGrlG2ZLTRl+UmXwbTCKzYA K+7NYuz+ekSI8xN++oYPouPOYu9WX9bGmw2DRxgLJgfDhyDd2HhC8yebI 0=; X-IronPort-AV: E=McAfee;i="5400,1158,6649"; a="170307282" Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine02.qualcomm.com with ESMTP; 14 Mar 2012 21:39:12 -0700 X-IronPort-AV: E=Sophos;i="4.73,587,1325491200"; d="scan'208";a="119719760" Received: from nasanexhc07.na.qualcomm.com ([172.30.39.190]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 14 Mar 2012 21:39:12 -0700 Received: from resnick2.qualcomm.com (172.30.39.5) by qcmail1.qualcomm.com (172.30.39.190) with Microsoft SMTP Server (TLS) id 14.1.339.1; Wed, 14 Mar 2012 21:39:11 -0700 Message-ID: <4F61726C.9020507@qualcomm.com> Date: Wed, 14 Mar 2012 23:39:08 -0500 From: Pete Resnick User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4 MIME-Version: 1.0 To: References: <20120313221840.16417.11343.idtracker@ietfa.amsl.com> <035701cd0231$8ee8d8d0$acba8a70$@olddog.co.uk> In-Reply-To: Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit X-Originating-IP: [172.30.39.5] X-Mailman-Approved-At: Thu, 15 Mar 2012 08:22:47 -0700 Cc: multimob@ietf.org, draft-ietf-multimob-igmp-mld-tuning@tools.ietf.org, multimob-chairs@tools.ietf.org, The IESG , adrian@olddog.co.uk, Behcet Sarikaya Subject: Re: [multimob] Adrian Farrel's Discuss on draft-ietf-multimob-igmp-mld-tuning-05: (with DISCUSS) X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Mar 2012 04:39:15 -0000 On 3/14/12 5:56 PM, Behcet Sarikaya wrote: > On Wed, Mar 14, 2012 at 5:26 PM, Adrian Farrel wrote: > >> The specific question in the write-up is "Has each author >> confirmed...?" not >> "Have any disclosure been made?" >> >> This is normally tested by an email to each author with the specific question >> "Can you confirm...?" and a response from each author. >> > Yes, that could be done. > > However, isn't it better to get the sherpherd document Item 7 to be > modified slightly, instead of the current form: > (7) Has each author confirmed that any and all appropriate IPR > disclosures required for full conformance with the provisions of BCP > 78 and BCP 79 have already been filed. If not, explain why. > > To something like: > > (7) If an IPR claim has been made, has each author confirmed that any > and all appropriate IPR > disclosures required for full conformance with the provisions of BCP > 78 and BCP 79 have already been filed. If not, explain why. > > Then the shepherd could simply reply N/A to this item if no IPR claim exists. > No, that is not sufficient. We have had several occasions where no disclosure was made, only to find out after publication that one of the authors of the document was a patent holder on technology that was in the draft. We do actually want you to ask the question of the authors. pr -- Pete Resnick Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102 From sarikaya2012@gmail.com Thu Mar 22 14:35:50 2012 Return-Path: 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 7806C21F8547 for ; Thu, 22 Mar 2012 14:35:50 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.567 X-Spam-Level: X-Spam-Status: No, score=-3.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KDejdi6--MGS for ; Thu, 22 Mar 2012 14:35:50 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 7A93621F8542 for ; Thu, 22 Mar 2012 14:35:47 -0700 (PDT) Received: by iazz13 with SMTP id z13so4258472iaz.31 for ; Thu, 22 Mar 2012 14:35:47 -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=9DYb0MVIVOfwLgv5MoHAj7IKYoh67gERZ9JxfvZVEQU=; b=TpVnynM6LRhWu84ngH0u9tFpuQeg9PG4CEDXIIAjMn24SD+jTI9S6rPhH1yUy/glkz KzNWRnm3gFzmdLYjLYeu/7d78S1/u/+CzUcmCzbSWeYcYOF8RYxNs5HJ4aeorxrj3/TY XtXLzeKFDBxaDd9IYYHbBF6grc5PEieGCQ7iRh4pS5JIeskZdHk/Px2dL6SfuXtyjKVG eqajHEjY1RGExUwHOy0dZ506uYcdeig4axTqd2PydDZlxL1vnFJJnLDTXktKDCjjzo9Z qLnY9vuFLSt+gn4SGdYUD4jLQ+YI/ol8vrEVR7SM7iNSxw//lokerrqS9ZyCTfXMoGka CNRQ== MIME-Version: 1.0 Received: by 10.50.47.135 with SMTP id d7mr238870ign.66.1332452146893; Thu, 22 Mar 2012 14:35:46 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Thu, 22 Mar 2012 14:35:46 -0700 (PDT) Date: Thu, 22 Mar 2012 16:35:46 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [multimob] PRESENTATIONS X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Mar 2012 21:35:50 -0000 Folks, Meeting time is coming close. Presenters: please send the slides to the chairs. Behcet From prvs=42262b749=Sebastian.Woelke@haw-hamburg.de Fri Mar 23 08:25:06 2012 Return-Path: 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 1ADE221F8452; Fri, 23 Mar 2012 08:25:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.156 X-Spam-Level: X-Spam-Status: No, score=0.156 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, FM_FORGED_GMAIL=0.622, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D06ae19hIq9N; Fri, 23 Mar 2012 08:25:02 -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 2EF9B21F8453; Fri, 23 Mar 2012 08:25:01 -0700 (PDT) Received: from dehawshub02.mailcluster.haw-hamburg.de ([141.22.200.52]) by mail3.is.haw-hamburg.de with ESMTP/TLS/RC4-MD5; 23 Mar 2012 16:24:59 +0100 Received: from dehawscas03.mailcluster.haw-hamburg.de (141.22.200.83) by DEHAWSHUB02.mailcluster.haw-hamburg.de (141.22.200.52) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 23 Mar 2012 16:24:59 +0100 Received: from mail-gx0-f172.google.com (141.22.200.35) by haw-mailer.haw-hamburg.de (141.22.200.80) with Microsoft SMTP Server (TLS) id 8.1.358.0; Fri, 23 Mar 2012 16:24:59 +0100 Received: by ggmi1 with SMTP id i1so3162953ggm.31 for ; Fri, 23 Mar 2012 08:24:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.60.30.3 with SMTP id o3mr15210633oeh.9.1332516297358; Fri, 23 Mar 2012 08:24:57 -0700 (PDT) Received: by 10.182.186.10 with HTTP; Fri, 23 Mar 2012 08:24:57 -0700 (PDT) Date: Fri, 23 Mar 2012 16:24:57 +0100 Message-ID: From: =?ISO-8859-1?Q?Sebastian_W=F6lke?= To: , , , Content-Type: multipart/alternative; boundary="e89a8ff1c60c8fbe3504bbeaa0d9" X-Mailman-Approved-At: Fri, 23 Mar 2012 08:36:18 -0700 Subject: [multimob] Multicast Proxy Release X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: Sebastian.Woelke@haw-hamburg.de List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 15:25:06 -0000 --e89a8ff1c60c8fbe3504bbeaa0d9 Content-Type: text/plain; charset="ISO-8859-1" Hi all, I want to announce our IGMP/MLD proxy implementation named mcproxy. It is implemented in C++ and conforms to RFC 4605. Mcproxy runs on Linux with Kernel version > 2.6.36. Its core features are: - support of IGMPv2/MLDv1; IGMPv3/MLDv2 support coming soon - multiple proxy instances per host: needed for PMIPv6 (RFC6224) - dynamic configuration: add/del downstream interfaces at runtime - high performance and throughput: operates on Linux Kernel tables The latest beta version and further documentation of the mcproxy prototype are available at http://mcproxy.realmv6.org/ Any questions and feedback are very welcome. Regards, Sebastian --e89a8ff1c60c8fbe3504bbeaa0d9 Content-Type: text/html; charset="ISO-8859-1" Content-Transfer-Encoding: quoted-printable
Hi all,

I want to announce our IGM= P/MLD proxy implementation named mcproxy. It is implemented in C++ and=A0co= nforms to RFC 4605. Mcproxy=A0runs on Linux with Kernel version > 2.6.36= .=A0

Its core features are:

=A0 =A0= - support of IGMPv2/MLDv1; IGMPv3/MLDv2 support coming soon
=A0 = =A0 - multiple proxy instances per host: needed for=A0PMIPv6 (RFC6224)
=A0 =A0 - dynamic configuration: add/del downstream interfaces at runtime
=A0 =A0 - high performance and throughput: operates on Linux Kerne= l tables

The latest beta version and further docum= entation of the mcproxy prototype are available at=A0http://m= cproxy.realmv6.org/

Any questions and feedback are very welcome.
=
Regards,
=A0 Sebastian

<= /div> --e89a8ff1c60c8fbe3504bbeaa0d9-- From sarikaya2012@gmail.com Fri Mar 23 08:55:36 2012 Return-Path: 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 CB8AF21F8597; Fri, 23 Mar 2012 08:55:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.568 X-Spam-Level: X-Spam-Status: No, score=-3.568 tagged_above=-999 required=5 tests=[AWL=0.031, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id npiY2egdMBc1; Fri, 23 Mar 2012 08:55:32 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1E0E621F857A; Fri, 23 Mar 2012 08:55:32 -0700 (PDT) Received: by iazz13 with SMTP id z13so5679491iaz.31 for ; Fri, 23 Mar 2012 08:55:31 -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:cc :content-type; bh=y3PclEIu+XdLv3VPjFNOHZs0r8+OsImn+z/SUtUDkkk=; b=XH5ViN806RBefSL8L5PQ8PCtSglJEuQl0NHbJ05XcBGVWqc8mGNT8IpYuAUsVP1Gbf 5dvjV86/n9TJQf8iL7PIwYqVDprwRIIZUlR7pNEZB1Bu6rZvtdaL1ZXw1bb118aPD2qk XR98i/FeeLcC+caOm41cDCLC/f0s92PiJ9lxDoo1/NOMs8AnvYmLAl9tsEz2fV5ssWgE /CnWX1ySzquhrTEh+70ikPYy7enOht3K6KwLR+FFWlB8ySEg8saH72JxEMV+jfN+Zk4W qnhJmlsi5Da+WJGDYW6JqbiNbP9nBT3cLj3fHNw3Dy8yznbKVqYnJf6RfodndN4dazXP AUlw== MIME-Version: 1.0 Received: by 10.50.189.129 with SMTP id gi1mr2551299igc.16.1332518131809; Fri, 23 Mar 2012 08:55:31 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Fri, 23 Mar 2012 08:55:31 -0700 (PDT) Date: Fri, 23 Mar 2012 10:55:31 -0500 Message-ID: From: Behcet Sarikaya To: Internet Area Content-Type: text/plain; charset=ISO-8859-1 Cc: netext@ietf.org, mip4@ietf.org, multimob@ietf.org, dmm@ietf.org Subject: [multimob] FMC Side Meeting Announcement X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Mar 2012 15:55:37 -0000 Side meeting on Fixed Mobile Convergence will take place on Thursday March 29, 2012 from 18:10 to 20:00 at room 212-213. The agenda and materials are posted at: http://www-etud.iro.umontreal.ca/~sarikaya/fmc/fmc.html Come and join us in this meeting. Behcet & Dirk From sarikaya2012@gmail.com Sun Mar 25 13:41:09 2012 Return-Path: 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 9BBCE21E801B; Sun, 25 Mar 2012 13:41:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.569 X-Spam-Level: X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gD7Ca-8Az6OK; Sun, 25 Mar 2012 13:41:09 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id A91E321E801A; Sun, 25 Mar 2012 13:41:08 -0700 (PDT) Received: by iazz13 with SMTP id z13so8527345iaz.31 for ; Sun, 25 Mar 2012 13:41:08 -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:cc :content-type; bh=rm5Ri9JI8gtkv5QlDwhU9Y8LU4mFzLqS4ANJdv+qAF4=; b=ZHSaz6+K0+qNKZJ6spN0cPIL5q+Ghg+Wf4N19NKGD+G+eDYA5c0dj/qTyk6VY+VuhJ LZg/sbCQVOO9au0Au6tmmRjbi4Gm8CTZzOo1G0Rxuh87OYvDzJXKScdUQmjZ2AjLlA/z umk49ryUg0jEbtm17kpKrDYH7TaHJZYvPrcn1XK4s5VWnnOQKSrj3kla/lIhjjJ9dC/8 RhHZ0RdvcRuegH+Cok+IGlKxikBMMugC3i39VPB1j106MCZOivpeJW8ul2cFH2yfDnYf O1Z9/XLJGWCmb9EzlAg7cQoM8898XvxkWr9wON5Co24R2xRrEKjTXAsk49NEBpoa+667 6I0w== MIME-Version: 1.0 Received: by 10.50.203.99 with SMTP id kp3mr3951191igc.16.1332708068305; Sun, 25 Mar 2012 13:41:08 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Sun, 25 Mar 2012 13:41:08 -0700 (PDT) Date: Sun, 25 Mar 2012 15:41:08 -0500 Message-ID: From: Behcet Sarikaya To: Internet Area Content-Type: text/plain; charset=ISO-8859-1 Cc: netext@ietf.org, mip4@ietf.org, multimob@ietf.org, dmm@ietf.org Subject: [multimob] FMC Final Date & Time: Tuesday X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 25 Mar 2012 20:41:09 -0000 IETF could not find us an appropriate room so as a result we will hold FMC meeting at the original time. Details are below: Tuesday March 27 at 19:30 or 7:30 Meet at Hotel Concorde Lobby Take a look at the materials at the link given below. On Fri, Mar 23, 2012 at 10:55 AM, Behcet Sarikaya wrote: > Side meeting on Fixed Mobile Convergence will take place on Thursday > March 29, 2012 > from 18:10 to 20:00 at room 212-213. > > The agenda and materials are posted at: > http://www-etud.iro.umontreal.ca/~sarikaya/fmc/fmc.html > > Come and join us in this meeting. Behcet & Dirk From sarikaya2012@gmail.com Mon Mar 26 06:29:53 2012 Return-Path: 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 0C4BA21F84C8 for ; Mon, 26 Mar 2012 06:29:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.569 X-Spam-Level: X-Spam-Status: No, score=-3.569 tagged_above=-999 required=5 tests=[AWL=0.030, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Gi7Sgr+D5mZX for ; Mon, 26 Mar 2012 06:29:52 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id 76D1121F84B3 for ; Mon, 26 Mar 2012 06:29:49 -0700 (PDT) Received: by iazz13 with SMTP id z13so9775264iaz.31 for ; Mon, 26 Mar 2012 06:29:49 -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=xtgbbgdtJUoluhiyES6DTYBjh/6ndqg1/wKV1uh3jBs=; b=FKbVHqhAcYk349Oo3WTg7Mt2eZs12gq02oomvt8VJrHSJNRrRFi4YSs1NuOPW5KydK e7gLsh3gOor4Z582wkoOR3Li902aehaJWf+KeqwOqV8GptWUueQ0Ms13FudfhkHyh43j PKNJ4LW7EgQB5e3RlTY2Rqz3YPXOrS/i4X+vYNYBzqvute6CLH3mXLbas8H+Yw0dRFsY QWiyaBh76/pbFxy4j8WAR1drLDbNndCYwyf34bls/WB0vKX6jVw24qZ1STwIM0mOpK4U 2v956hne5CrJsGWQnJteqFyqdJEUB2Fr5VtvPzBhfGDNsRuVNbI+i4oV/Nlqv6CvN1hc uD7Q== MIME-Version: 1.0 Received: by 10.50.47.135 with SMTP id d7mr5473389ign.66.1332768589179; Mon, 26 Mar 2012 06:29:49 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Mon, 26 Mar 2012 06:29:49 -0700 (PDT) Date: Mon, 26 Mar 2012 08:29:49 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [multimob] Administrativia X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 26 Mar 2012 13:29:53 -0000 Hi all, Minutes of our meeting today at IETF 83 has been posted at: http://www.ietf.org/proceedings/83/minutes/minutes-83-multimob.txt Thanks Akbar again for your great work! Thanks Dapeng for your nice introduction to DMM. Also all slides have now been uploaded, check it out from the agenda page: http://www.ietf.org/proceedings/83/agenda/agenda-83-multimob.html Please check the minutes and post any corrections you may have. Regards, Chairs From asaeda@sfc.wide.ad.jp Mon Mar 26 21:20:50 2012 Return-Path: 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 9E2CD21F84DF for ; Mon, 26 Mar 2012 21:20:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -98.962 X-Spam-Level: X-Spam-Status: No, score=-98.962 tagged_above=-999 required=5 tests=[AWL=0.134, 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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id JxoVqvvJr6Pr for ; Mon, 26 Mar 2012 21:20:48 -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 87D5A21F84E4 for ; Mon, 26 Mar 2012 21:20:47 -0700 (PDT) Received: from localhost (dhcp-143-211.sfc.wide.ad.jp [203.178.143.211]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id C606C278098 for ; Tue, 27 Mar 2012 13:20:43 +0900 (JST) Date: Tue, 27 Mar 2012 13:20:43 +0900 (JST) Message-Id: <20120327.132043.81454785.asaeda@sfc.wide.ad.jp> To: multimob@ietf.org From: Hitoshi Asaeda In-Reply-To: References: 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] Administrativia X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2012 04:20:51 -0000 Hi, I'm afraid that I could not attend this IETF. Anyway, we revised the draft describing PIM-SM and PMIPv6. http://tools.ietf.org/html/draft-asaeda-multimob-pmip6-extension-10 According to some comments, we changed the title of this draft to; "Multicast Routing Optimization by PIM-SM with PMIPv6". IMO, it would be great if new charter includes routing optimization and this draft is the candidate of the solution. I hope now people can understand the approach. Regards, -- Hitoshi Asaeda From sarikaya2012@gmail.com Tue Mar 27 00:40:23 2012 Return-Path: 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 65EEB21F879F for ; Tue, 27 Mar 2012 00:40:23 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.571 X-Spam-Level: X-Spam-Status: No, score=-3.571 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RCNXgbhlmIdD for ; Tue, 27 Mar 2012 00:40:22 -0700 (PDT) Received: from mail-iy0-f172.google.com (mail-iy0-f172.google.com [209.85.210.172]) by ietfa.amsl.com (Postfix) with ESMTP id CE30421F8795 for ; Tue, 27 Mar 2012 00:40:22 -0700 (PDT) Received: by iazz13 with SMTP id z13so11149223iaz.31 for ; Tue, 27 Mar 2012 00:40:22 -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:cc :content-type; bh=KFWAkG6IGd+fRPhrlLUi/y41ZCZKmGXKvtDszoS2mak=; b=wFexwBTGYKTRDGf1xPn2oubwD0XymldZAkjron8B/QX5+lntIPKGB1VkEs8jyS4M/1 9NW8JjjMITFRoJIDlKEgLTf3fzrSXTmEpGPsej0Kil6p7H6kfig/wed6oL/3C/ZGvIYR iSaH7XsHg5hXed1HDQXYiwdR5LrFze9WqrJV7Z7EzL+bLCgGzKLwOA1jM/K69dJeIeIO glUu2ziS7kd2NI5fEREox1I+bjVP8vPELpGYLS8ZR2eoKDTjoGfYpS4DXMMGMAtOE0Jz YlBDU5+QawxGwDW7mt3Rk5Gcg+AtnmiOiYYzcuU4Ahz0SF6TpQ7Odq3ecAeifeVkIWqx AH3A== MIME-Version: 1.0 Received: by 10.50.189.129 with SMTP id gi1mr7698182igc.16.1332834022527; Tue, 27 Mar 2012 00:40:22 -0700 (PDT) Received: by 10.231.179.71 with HTTP; Tue, 27 Mar 2012 00:40:22 -0700 (PDT) Date: Tue, 27 Mar 2012 02:40:22 -0500 Message-ID: From: Behcet Sarikaya To: Hitoshi Asaeda Content-Type: text/plain; charset=ISO-8859-1 Cc: multimob@ietf.org Subject: [multimob] draft-asaeda-multimob-pmip6-extension-10 X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list Reply-To: sarikaya@ieee.org List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Mar 2012 07:40:23 -0000 A new draft revision has been posted, please read it and post your comments on the list. Behcet On Mon, Mar 26, 2012 at 11:20 PM, Hitoshi Asaeda wrote: > Hi, > > I'm afraid that I could not attend this IETF. > > Anyway, we revised the draft describing PIM-SM and PMIPv6. > http://tools.ietf.org/html/draft-asaeda-multimob-pmip6-extension-10 > > According to some comments, we changed the title of this draft to; > "Multicast Routing Optimization by PIM-SM with PMIPv6". > IMO, it would be great if new charter includes routing optimization > and this draft is the candidate of the solution. > > I hope now people can understand the approach. > > Regards, > -- > Hitoshi Asaeda > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob From ietf-ipr@ietf.org Wed Mar 28 04:37:55 2012 Return-Path: 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 AEFFD21F891F; Wed, 28 Mar 2012 04:37:55 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.419 X-Spam-Level: X-Spam-Status: No, score=-102.419 tagged_above=-999 required=5 tests=[AWL=0.180, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YCCuUXR5QN0G; Wed, 28 Mar 2012 04:37:55 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D21A521F8902; Wed, 28 Mar 2012 04:37:54 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: IETF Secretariat To: JuanCarlos.Zuniga@InterDigital.com, lmcm@tid.es, cjbc@it.uc3m.es, seiljeon@av.it.pt, yhkim@dcn.ssu.ac.kr X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120328113754.24932.57034.idtracker@ietfa.amsl.com> Date: Wed, 28 Mar 2012 04:37:54 -0700 Cc: multimob@ietf.org, rdroms.ietf@gmail.com, ipr-announce@ietf.org Subject: [multimob] IPR Disclosure: InterDigital Patent Holdings, Inc.'s Statement about IPR related to draft-ietf-multimob-pmipv6-ropt-00 X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2012 11:37:55 -0000 Dear Juan Zuniga, Luis M. Contreras, Carlos J. Bernardos, Seil Jeon, Youngh= an Kim: An IPR disclosure that pertains to your Internet-Draft entitled "Multicast Mobility Routing Optimizations for Proxy Mobile IPv6" (draft-ietf-multimob- pmipv6-ropt) was submitted to the IETF Secretariat on 2012-03-19 and has be= en posted on the "IETF Page of Intellectual Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1723/). The title of the IPR disclosure is "InterDigital Patent Holdings, Inc.'s Statement about IPR related to draft-= ietf- multimob-pmipv6-ropt-00.""); The IETF Secretariat From iesg-secretary@ietf.org Wed Mar 28 05:01:42 2012 Return-Path: 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 535D821E8161; Wed, 28 Mar 2012 05:01:42 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.577 X-Spam-Level: X-Spam-Status: No, score=-102.577 tagged_above=-999 required=5 tests=[AWL=0.022, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QzQ4sHzTapAz; Wed, 28 Mar 2012 05:01:41 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1FCE21E8169; Wed, 28 Mar 2012 05:01:41 -0700 (PDT) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: The IESG To: IETF-Announce X-Test-IDTracker: no X-IETF-IDTracker: 4.00 Message-ID: <20120328120141.32525.63526.idtracker@ietfa.amsl.com> Date: Wed, 28 Mar 2012 05:01:41 -0700 Cc: multimob mailing list , multimob chair , RFC Editor Subject: [multimob] Document Action: 'Tuning the Behavior of IGMP and MLD for Routers in Mobile and Wireless Networks' to Informational RFC (draft-ietf-multimob-igmp-mld-tuning-05.txt) X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2012 12:01:42 -0000 The IESG has approved the following document: - 'Tuning the Behavior of IGMP and MLD for Routers in Mobile and Wireless Networks' (draft-ietf-multimob-igmp-mld-tuning-05.txt) as an Informational RFC This document is the product of the Multicast Mobility Working Group. The IESG contact persons are Jari Arkko and Ralph Droms. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-multimob-igmp-mld-tuning/ Technical Summary IGMP and MLD are the protocols used by hosts and multicast routers to exchange their IP multicast group memberships with each other. This document describes the ways of IGMPv3 and MLDv2 protocol optimization for mobility, and aims to become a guideline for tuning of IGMPv3/ MLDv2 Queries and timer and counter values. WG Summary Nothing worth noting outside ordinary WG process. Document Quality Nothing worth noting outside ordinary WG process. Personnel The document shepherd is Bechet Sarikaya, and the responsible area director is Jari Arkko. RFC Editor Note Please remove any reference to 2119 and lowercase all current keyword text. Change this text in Section 1: OLD: The proposed behavior interoperates with the IGMPv3 and MLDv2 protocols. NEW: This document does not make any changes to the IGMPv3 and MLDv2 protocols and only suggests optimal settings for the configurable parameters of the protocols in mobile and wireless environments. From internet-drafts@ietf.org Wed Mar 28 05:30:08 2012 Return-Path: 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 E6A4021E81CC; Wed, 28 Mar 2012 05:30:08 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.55 X-Spam-Level: X-Spam-Status: No, score=-102.55 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XpihUEcA26HY; Wed, 28 Mar 2012 05:30:08 -0700 (PDT) Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B4A21E8195; Wed, 28 Mar 2012 05:30:08 -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.00 Message-ID: <20120328123008.10907.25269.idtracker@ietfa.amsl.com> Date: Wed, 28 Mar 2012 05:30:08 -0700 Cc: multimob@ietf.org Subject: [multimob] I-D Action: draft-ietf-multimob-igmp-mld-tuning-06.txt X-BeenThere: multimob@ietf.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Multicast Mobility List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Mar 2012 12:30:09 -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 t= he IETF. Title : Tuning the Behavior of IGMP and MLD for Routers in Mobil= e and Wireless Networks Author(s) : Hitoshi Asaeda Hui Liu Qin Wu Filename : draft-ietf-multimob-igmp-mld-tuning-06.txt Pages : 13 Date : 2012-03-28 IGMP and MLD are the protocols used by hosts and multicast routers to exchange their IP multicast group memberships with each other. This document describes the ways of IGMPv3 and MLDv2 protocol optimization for mobility, and aims to become a guideline for tuning of IGMPv3/ MLDv2 Queries and timer and counter values. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-multimob-igmp-mld-tuning-06.= txt Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ This Internet-Draft can be retrieved at: ftp://ftp.ietf.org/internet-drafts/draft-ietf-multimob-igmp-mld-tuning-06.t= xt