From sarikaya2012@gmail.com Wed Apr 4 09: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 A705421F8733 for ; Wed, 4 Apr 2012 09:46:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.599 X-Spam-Level: X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 lAf9cNzttgGw for ; Wed, 4 Apr 2012 09:46:06 -0700 (PDT) Received: from mail-ob0-f172.google.com (mail-ob0-f172.google.com [209.85.214.172]) by ietfa.amsl.com (Postfix) with ESMTP id 02F9421F86B1 for ; Wed, 4 Apr 2012 09:46:05 -0700 (PDT) Received: by obbtb4 with SMTP id tb4so645767obb.31 for ; Wed, 04 Apr 2012 09:46:05 -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=qBuUn56FWRg/0HTygQyxyJDi+icTY9CKeqg2q8d+1jc=; b=N7kKTvxUT+xau1KArFHECGNgw2cj4gFwODUBuWOezlZEXjGW/hcvicqs4oh1ETAuiR 0wGSdo+luT+9sautUz5GzoHdN3hWWvSisLZoy+uKxXOXjSPEjOa5gLPwZ5LNSI/retvE J5jM7lZG5jO0gXXIoaT7UI/pJRssHLI3eqEUKDWcd1NU5KdrVXPhpsLhDCcXp2zKrJDP 7zahRoYlXFt6pn4kazNO/xYt7JXre1yHodvELM5767GQA3ou2e18jOMrj3WCwk5TtzzB X/N+zUP0b1b2QS2GRfgGY2xH9LRKK3Ev2NBJrqnUFdGKrFh57FPziw6G8Vuv3ue0YlZ6 4kww== MIME-Version: 1.0 Received: by 10.182.53.106 with SMTP id a10mr25519169obp.43.1333557965396; Wed, 04 Apr 2012 09:46:05 -0700 (PDT) Received: by 10.60.164.103 with HTTP; Wed, 4 Apr 2012 09:46:05 -0700 (PDT) Date: Wed, 4 Apr 2012 11:46:05 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 04 Apr 2012 16:46:06 -0000 Folks, This mails starts a one-week adoption call on PMIPv6 multicast handover optimization draft at http://tools.ietf.org/html/draft-contreras-multimob-rams-04 There was good support at the meeting last week. Please send your comments on supporting or not to the list. Regards, Chairs From Akbar.Rahman@InterDigital.com Mon Apr 9 08:40:32 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 8697021F873D for ; Mon, 9 Apr 2012 08:40:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.134 X-Spam-Level: X-Spam-Status: No, score=-2.134 tagged_above=-999 required=5 tests=[AWL=0.465, 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 v1oZ-Ae4dmrM for ; Mon, 9 Apr 2012 08:40:32 -0700 (PDT) Received: from idcout.InterDigital.com (smtp-out1.interdigital.com [64.208.228.135]) by ietfa.amsl.com (Postfix) with ESMTP id F2F5421F874A for ; Mon, 9 Apr 2012 08:40:31 -0700 (PDT) Received: from SAM.InterDigital.com ([10.30.2.11]) by idcout.InterDigital.com with Microsoft SMTPSVC(6.0.3790.4675); Mon, 9 Apr 2012 11:40:31 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Mon, 9 Apr 2012 11:40:30 -0400 Message-ID: In-reply-to: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [multimob] WG adoption call on PMIPv6 multicast handoveroptimization draft Thread-Index: Ac0Sgm/7/8gBKjIgTCeaKuprbQWdlwD5DrSg References: From: "Rahman, Akbar" To: X-OriginalArrivalTime: 09 Apr 2012 15:40:31.0492 (UTC) FILETIME=[18AB1440:01CD1667] Cc: multimob@ietf.org Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handoveroptimization draft 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, 09 Apr 2012 15:40:32 -0000 Hi Behcet, I agree with the proposal to adopt this I-D as a WG draft. I think that the document is in good shape and that there was good WG support as you mentioned during the Paris IETF meeting. Akbar -----Original Message----- From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On Behalf Of Behcet Sarikaya Sent: Wednesday, April 04, 2012 12:46 PM To: multimob@ietf.org Subject: [multimob] WG adoption call on PMIPv6 multicast handoveroptimization draft Folks, This mails starts a one-week adoption call on PMIPv6 multicast handover optimization draft at http://tools.ietf.org/html/draft-contreras-multimob-rams-04 There was good support at the meeting last week. Please send your comments on supporting or not to the list. Regards, Chairs _______________________________________________ multimob mailing list multimob@ietf.org https://www.ietf.org/mailman/listinfo/multimob From sfigueiredo@av.it.pt Mon Apr 9 09:19: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 7ECD921F875E for ; Mon, 9 Apr 2012 09:19:00 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.299 X-Spam-Level: X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_8BIT_HEADER=0.3] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W4i8+A2xJ18e for ; Mon, 9 Apr 2012 09:19:00 -0700 (PDT) Received: from av.it.pt (mail.av.it.pt [193.136.92.53]) by ietfa.amsl.com (Postfix) with ESMTP id 015E521F864C for ; Mon, 9 Apr 2012 09:18:56 -0700 (PDT) Received: from [193.136.93.26] (account sfigueiredo@av.it.pt [193.136.93.26] verified) by av.it.pt (CommuniGate Pro SMTP 5.4.2) with ESMTPSA id 64176273; Mon, 09 Apr 2012 17:18:55 +0100 Message-ID: <4F830BF4.8000203@av.it.pt> Date: Mon, 09 Apr 2012 17:19:00 +0100 From: =?ISO-8859-1?Q?S=E9rgio_Figueiredo?= 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: sarikaya@ieee.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: multimob@ietf.org Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 09 Apr 2012 16:19:00 -0000 Hi Behcet, I support the adoption of this I-D as a MULTIMOB WG draft. Best regards, Sérgio Figueiredo On 04/04/2012 05:46 PM, Behcet Sarikaya wrote: > Folks, > > This mails starts a one-week adoption call on > PMIPv6 multicast handover optimization draft at > > http://tools.ietf.org/html/draft-contreras-multimob-rams-04 > > There was good support at the meeting last week. > > Please send your comments on supporting or not > to the list. > > Regards, > > Chairs > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob -- ---------------------------------------------- Sérgio Figueiredo ---------------------------------------------- Advanced Telecommunications and Networks Group IT-Aveiro ---------------------------------------------- From prvs=43910db40=schmidt@informatik.haw-hamburg.de Mon Apr 9 15:22: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 1BAD521F881C for ; Mon, 9 Apr 2012 15:22:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -101.85 X-Spam-Level: X-Spam-Status: No, score=-101.85 tagged_above=-999 required=5 tests=[AWL=0.400, 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 wpbuQbcw3wHB for ; Mon, 9 Apr 2012 15:22:40 -0700 (PDT) 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 0638F21F87FE for ; Mon, 9 Apr 2012 15:22:39 -0700 (PDT) Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74]) by mail6.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 10 Apr 2012 00:22:38 +0200 Received: from localhost (localhost [127.0.0.1]) by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 1DDBE1086EBB; Tue, 10 Apr 2012 00:22:38 +0200 (CEST) Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1]) by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 30473-01; Tue, 10 Apr 2012 00:22:37 +0200 (CEST) Received: from [192.168.178.36] (g231110212.adsl.alicedsl.de [92.231.110.212]) (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 2824E105D430; Tue, 10 Apr 2012 00:22:35 +0200 (CEST) Message-ID: <4F836131.8000805@informatik.haw-hamburg.de> Date: Tue, 10 Apr 2012 00:22:41 +0200 From: "Thomas C. Schmidt" User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: sarikaya@ieee.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 Cc: multimob@ietf.org, Behcet Sarikaya Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 09 Apr 2012 22:22:41 -0000 Hi, I haven't found the time to review the document in detail - but in general I support adopting the draft. Best regards, Thomas On 04.04.2012 18:46, Behcet Sarikaya wrote: > Folks, > > This mails starts a one-week adoption call on > PMIPv6 multicast handover optimization draft at > > http://tools.ietf.org/html/draft-contreras-multimob-rams-04 > > There was good support at the meeting last week. > > Please send your comments on supporting or not > to the list. > > Regards, > > Chairs > _______________________________________________ > 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 asaeda@sfc.wide.ad.jp Mon Apr 9 23:10: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 103ED21F86FE for ; Mon, 9 Apr 2012 23:10:11 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[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 RvN4L0fQWkpf for ; Mon, 9 Apr 2012 23:10:10 -0700 (PDT) Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [IPv6:2001:200:0:8803:203:178:142:146]) by ietfa.amsl.com (Postfix) with ESMTP id 44A2521F86F7 for ; Mon, 9 Apr 2012 23:10:09 -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 2477D27809A for ; Tue, 10 Apr 2012 15:10:07 +0900 (JST) Date: Tue, 10 Apr 2012 15:10:04 +0900 (JST) Message-Id: <20120410.151004.08350431.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] WG adoption call on PMIPv6 multicast handover optimization draft 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, 10 Apr 2012 06:10:11 -0000 Hi, > This mails starts a one-week adoption call on > PMIPv6 multicast handover optimization draft at > > http://tools.ietf.org/html/draft-contreras-multimob-rams-04 > > There was good support at the meeting last week. > > Please send your comments on supporting or not > to the list. I'm Ok this draft becomes the WG draft. But the following points should be considered in the revised version. In section 3.1.1.1, it says; "This option does not include specific information about the applicable filter mode defined in [9]. After the handover process, the MN has to receive the same multicast flow being received before the handover initiation (in terms of the (S,G) duple), then the filter mode information is not strictly critical to accelerate the reception of the multicast flow at the new point of attachment. This information can be, however, retrieved later through the response message to the MLD Query sent by the nMAG once the point-to-point link of the entering MN is set-up, as defined in [4]." I don't think this paragraph is true. Operations regarding MLD filter more (include or exclude) are completely opposite; include (S,G) join is the request to obtain the (S,G) session, but exclude (S,G) join is the request NOT to obtain the (S,G) session (i.e. request to obtain (*,G) but not (S,G)). If you want to ignore the exclude filter mode operation (e.g. because of its complexity), I think it is Ok. But this draft must explicitly say so and provide the procedure how you ignore the exclude filter mode operations. The option format defined in section 3.1.1.2 should be conformed with RFC3810. A multicast record must include filter more if you support both include and exclude filter mode operations. And the multicast record must be able to specify multiple source addresses for one group record as specified in RFC3810. I also recommend to note that null source address must be allowed. And at last, although I said previously, I recommend to change the name of "RAMS" to the different one, as RAMS is already well known as Unicast-Based Rapid Acquisition of Multicast RTP Sessions (RFC6285) and some of AVT drafts have been using this abbreviation. Regards, -- Hitoshi Asaeda From seiljeon@gmail.com Tue Apr 10 04:30: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 13BD921F866E for ; Tue, 10 Apr 2012 04:30:39 -0700 (PDT) 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 PJX-HRCkMn9j for ; Tue, 10 Apr 2012 04:30:38 -0700 (PDT) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 8F77F21F866D for ; Tue, 10 Apr 2012 04:30:38 -0700 (PDT) Received: by dady13 with SMTP id y13so9054543dad.27 for ; Tue, 10 Apr 2012 04:30:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=oznFekCzC0b3a3m0pa1mzsZ5o3qadDgtC4EhblVqyHc=; b=NuObaeeVYLuckn13mDmB+e7bnZS4XB+dbw4siKTyZROoKHJUmYkfUAh+CrKRBBCyTj zUU3veLmbbjDhbn3Ger6c/qzXDdLksE+mJLuiQeOFngwkbo0piA9tislvYLI/wm0b68L OUXkMOBkG3emoTz6kduQSyIeIWpJ8qxE+mNK6TER64dBea6AyfJ6Wo8k1lL8OohXy3Gl pVvkdtRthYkKbTOUHU2UscwLn09q+XWRYWBjlE//4ySKVu8jvrpxNkJHitr9Vspi/i8C O4bbjJpcCsrcpxOTy1Q6IQxyuyEoMR1Hd+39cs++PcH2htCra6fcQqzHOLw2mezgHzce lGaw== MIME-Version: 1.0 Received: by 10.68.236.198 with SMTP id uw6mr7190580pbc.99.1334057438313; Tue, 10 Apr 2012 04:30:38 -0700 (PDT) Sender: seiljeon@gmail.com Received: by 10.68.6.230 with HTTP; Tue, 10 Apr 2012 04:30:38 -0700 (PDT) In-Reply-To: References: Date: Tue, 10 Apr 2012 12:30:38 +0100 X-Google-Sender-Auth: CP0rce7lBX22vh9tT5mHHQCNxvc Message-ID: From: Seil Jeon To: sarikaya@ieee.org Content-Type: multipart/alternative; boundary=047d7b33d7c4b87d8904bd517301 Cc: multimob@ietf.org Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 10 Apr 2012 11:30:39 -0000 --047d7b33d7c4b87d8904bd517301 Content-Type: text/plain; charset=ISO-8859-1 We need to check it in details but I agree this approach (e.g. not MAG-to-MAG but MAG-to-LMA based context transfer) should be made for rapid multicast subscription in mobile environment. So, I support the WG adoption of this draft. Seil 2012/4/4 Behcet Sarikaya > Folks, > > This mails starts a one-week adoption call on > PMIPv6 multicast handover optimization draft at > > http://tools.ietf.org/html/draft-contreras-multimob-rams-04 > > There was good support at the meeting last week. > > Please send your comments on supporting or not > to the list. > > Regards, > > Chairs > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > --047d7b33d7c4b87d8904bd517301 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
We need to check it in details but I agree this approach (e.g. not MAG= -to-MAG but MAG-to-LMA based context transfer) should be made for rapid mul= ticast subscription in mobile environment.
=A0
So, I su= pport the WG adoption of this draft.
=A0
=A0
Seil
=A0

=A0
=
2012/4/4 Behcet Sarikaya <<= a href=3D"mailto:sarikaya2012@gmail.com">sarikaya2012@gmail.com>
Folks,

This mails starts a one-week adoption call on
PMIPv6 multicast handover optimization draft at

http://tools.ietf.org/html/draft-contreras-multimob-rams-04<= /a>

There was good support at the meeting last week.

Please send your comments on supporting or not
to the list.

Regards,

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

--047d7b33d7c4b87d8904bd517301-- From Dirk.von-Hugo@telekom.de Wed Apr 11 07:35: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 440CD21F8584 for ; Wed, 11 Apr 2012 07:35:06 -0700 (PDT) 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 S7DwjxNnkdyW for ; Wed, 11 Apr 2012 07:35:05 -0700 (PDT) Received: from tcmail33.telekom.de (tcmail33.telekom.de [194.25.30.7]) by ietfa.amsl.com (Postfix) with ESMTP id 72B1621F8517 for ; Wed, 11 Apr 2012 07:35:05 -0700 (PDT) Received: from he110889.emea1.cds.t-internal.com ([10.134.92.130]) by tcmail31.telekom.de with ESMTP/TLS/AES128-SHA; 11 Apr 2012 16:34:59 +0200 Received: from HE113484.emea1.cds.t-internal.com ([169.254.4.36]) by HE110889.emea1.cds.t-internal.com ([fe80::841f:f92c:15ca:8526%16]) with mapi; Wed, 11 Apr 2012 16:34:58 +0200 From: To: , Date: Wed, 11 Apr 2012 16:34:57 +0200 Thread-Topic: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft Thread-Index: Ac0Sgm3VV7jelLGKTZC4ZVtD86zvgQFbOMrw Message-ID: <05C81A773E48DD49B181B04BA21A342A2796F6C5CA@HE113484.emea1.cds.t-internal.com> References: In-Reply-To: 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: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 11 Apr 2012 14:35:06 -0000 Dear all, I also confirm my support for the draft as WG document on HO optimization. = I think we should in parallel (and perhaps as Appendix?) also demonstrate t= he optimized performance of both the proactive version and the reactive ver= sus the base solution - which of course is also a function of assumed RTTs = on radio part (MN-MAG) and between MAG-LMA. I would offer to propose some text for this ... Together with at least Luis= and Carlos ;-) Best regards Dirk -----Urspr=FCngliche Nachricht----- Von: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] Im Auftra= g von Behcet Sarikaya Gesendet: Mittwoch, 4. April 2012 18:46 An: multimob@ietf.org Betreff: [multimob] WG adoption call on PMIPv6 multicast handover optimizat= ion draft Folks, This mails starts a one-week adoption call on PMIPv6 multicast handover optimization draft at http://tools.ietf.org/html/draft-contreras-multimob-rams-04 There was good support at the meeting last week. Please send your comments on supporting or not to the list. Regards, Chairs _______________________________________________ multimob mailing list multimob@ietf.org https://www.ietf.org/mailman/listinfo/multimob From sarikaya2012@gmail.com Wed Apr 11 09:04:27 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 C3FFB21F8528 for ; Wed, 11 Apr 2012 09:04:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.574 X-Spam-Level: X-Spam-Status: No, score=-3.574 tagged_above=-999 required=5 tests=[AWL=0.025, 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 RQgCy4ikXmbn for ; Wed, 11 Apr 2012 09:04:27 -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 2D63F21F8527 for ; Wed, 11 Apr 2012 09:04:27 -0700 (PDT) Received: by iazz13 with SMTP id z13so1754861iaz.31 for ; Wed, 11 Apr 2012 09:04:26 -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:content-type; bh=7kAonxl9tGu7UWLQrHaiINwUYtA9QWegjEpAZJm9EkU=; b=pMb8pkOT7cFK9ol22TTH5qOvAzs0XGF9zKEjtYWuOIFMhqfuuLjPr4/1uH/SXNFY3i QsccbRpp8fC8tgqlBAKE2uE5NsRvEpTbkcI4AGHnQNoAeIZFcVPHzBBzTulm+X1SE16O EXI8WT65wZtp8YCzhAVLysFhOldAQhIjeEIbh4XdHYwb3AClIoewXo7V28srXMtXUA/0 y2gyb2L2PftrvAFFp/FcAdHyI4v9zdZPG391/gHaXFSS9IteutAN5vr/fkdqvslrkuhH Z6xXd/EQacnpxvoCVROGd95JjnM1QbzI8Qy/KqFrZhBiYRiYKFLM5MsM7L12XiPW5gcw yTeA== MIME-Version: 1.0 Received: by 10.50.189.129 with SMTP id gi1mr6262784igc.16.1334160266847; Wed, 11 Apr 2012 09:04:26 -0700 (PDT) Received: by 10.231.194.73 with HTTP; Wed, 11 Apr 2012 09:04:26 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Apr 2012 11:04:26 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 11 Apr 2012 16:04:27 -0000 Hi all, This call has ended with very strong support. Authors, please submit your draft as draft-multimob-fast-handover after revising according to the comments posted. Regards, Behcet On Wed, Apr 4, 2012 at 11:46 AM, Behcet Sarikaya wrote: > Folks, > > This mails starts a one-week adoption call on > PMIPv6 multicast handover optimization draft at > > http://tools.ietf.org/html/draft-contreras-multimob-rams-04 > > There was good support at the meeting last week. > > Please send your comments on supporting or not > to the list. > > Regards, > > Chairs From sarikaya2012@gmail.com Wed Apr 11 09:46:12 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 7F10F11E80AE for ; Wed, 11 Apr 2012 09:46:12 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.564 X-Spam-Level: X-Spam-Status: No, score=-3.564 tagged_above=-999 required=5 tests=[AWL=0.035, 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 WjCqqatMm7Mt for ; Wed, 11 Apr 2012 09:46:11 -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 D1DBA11E8098 for ; Wed, 11 Apr 2012 09:46:11 -0700 (PDT) Received: by iazz13 with SMTP id z13so1804940iaz.31 for ; Wed, 11 Apr 2012 09:46:11 -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:content-type; bh=V2vo1SxnwmXfVTHwNngA/p2kyVGeND8AKWt43iPD2+Q=; b=YiKC5KC52t1CFpaYk4LILMcahPGHTgdbqsvrcLd4JM7XeL4/m5H0q7IYw/FUnfUmrt UdB6WAEZIc4Kc3ovFFVNSm2CPGvBe1kY0VTe05x8oa+AylJqVyd683azBoMnfxFTNrCu NaISyuzDAfWpmSIMj/gwkLgglXzGMkOLB1bG3HZ8nwe1NWmpISL9nNuHiAhA0VTMtCJU A3ojklaOGDt1ex6CJ5b3HTSKmzWhO5pm1fhsZ+ank5SMn5mqEtgrZ4e+tQW5+VEaHoJw 50EjFqjDrQou50C8vXZ+H/Qo7dL4qbZZD1UD/TXuFxFpgRDygfBaeYP6qwWk44yNLM5m 8jCQ== MIME-Version: 1.0 Received: by 10.50.189.129 with SMTP id gi1mr6428214igc.16.1334162771471; Wed, 11 Apr 2012 09:46:11 -0700 (PDT) Received: by 10.231.194.73 with HTTP; Wed, 11 Apr 2012 09:46:11 -0700 (PDT) In-Reply-To: References: Date: Wed, 11 Apr 2012 11:46:11 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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, 11 Apr 2012 16:46:12 -0000 On Wed, Apr 11, 2012 at 11:04 AM, Behcet Sarikaya wrote: > Hi all, > > This call has ended with very strong support. > > Authors, please submit your draft as > > draft-multimob-fast-handover draft-ietf-multimob-fast-handover PS. Thanks Bill Atwood for pointing out this typo. > > after revising according to the comments posted. > > Regards, > > Behcet > > On Wed, Apr 4, 2012 at 11:46 AM, Behcet Sarikaya wrote: >> Folks, >> >> This mails starts a one-week adoption call on >> PMIPv6 multicast handover optimization draft at >> >> http://tools.ietf.org/html/draft-contreras-multimob-rams-04 >> >> There was good support at the meeting last week. >> >> Please send your comments on supporting or not >> to the list. >> >> Regards, >> >> Chairs From telemaco.melia@alcatel-lucent.com Fri Apr 13 02:34: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 2694921F85E6 for ; Fri, 13 Apr 2012 02:34:14 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -10.249 X-Spam-Level: X-Spam-Status: No, score=-10.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_HI=-8] 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 GNAIAlZ5iYcn for ; Fri, 13 Apr 2012 02:34:13 -0700 (PDT) Received: from smail2.alcatel.fr (smail2.alcatel.fr [64.208.49.57]) by ietfa.amsl.com (Postfix) with ESMTP id 5482721F85DF for ; Fri, 13 Apr 2012 02:34:10 -0700 (PDT) Received: from FRMRSSXCHHUB01.dc-m.alcatel-lucent.com (FRMRSSXCHHUB01.dc-m.alcatel-lucent.com [135.120.45.61]) by smail2.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id q3D9Y656002456 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Fri, 13 Apr 2012 11:34:06 +0200 Received: from FRMRSSXCHMBSE1.dc-m.alcatel-lucent.com ([135.120.45.55]) by FRMRSSXCHHUB01.dc-m.alcatel-lucent.com ([135.120.45.61]) with mapi; Fri, 13 Apr 2012 11:34:06 +0200 From: "MELIA, TELEMACO (TELEMACO)" To: "sarikaya@ieee.org" , "multimob@ietf.org" Date: Fri, 13 Apr 2012 11:34:04 +0200 Thread-Topic: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft Thread-Index: Ac0SgnO65w+m4ySgR7OKDN4RL7jtgQG1hkxA Message-ID: <3D6C64F2D792B540BAAEBCEF6509363B128DAFBCC0@FRMRSSXCHMBSE1.dc-m.alcatel-lucent.com> References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Scanned-By: MIMEDefang 2.69 on 155.132.188.80 Subject: Re: [multimob] WG adoption call on PMIPv6 multicast handover optimization draft 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: Fri, 13 Apr 2012 09:34:14 -0000 We support the adoption of this ID as WG document telemaco -----Original Message----- From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On Behal= f Of Behcet Sarikaya Sent: 04 April 2012 18:46 To: multimob@ietf.org Subject: [multimob] WG adoption call on PMIPv6 multicast handover optimizat= ion draft Folks, This mails starts a one-week adoption call on PMIPv6 multicast handover optimization draft at http://tools.ietf.org/html/draft-contreras-multimob-rams-04 There was good support at the meeting last week. Please send your comments on supporting or not to the list. Regards, Chairs _______________________________________________ multimob mailing list multimob@ietf.org https://www.ietf.org/mailman/listinfo/multimob From sarikaya2012@gmail.com Mon Apr 23 15:48: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 3B3D411E8095 for ; Mon, 23 Apr 2012 15:48:09 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.542 X-Spam-Level: X-Spam-Status: No, score=-3.542 tagged_above=-999 required=5 tests=[AWL=0.057, 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 KFbAbdkA0kea for ; Mon, 23 Apr 2012 15:48:08 -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 7398511E8075 for ; Mon, 23 Apr 2012 15:48:08 -0700 (PDT) Received: by iazz13 with SMTP id z13so86516iaz.31 for ; Mon, 23 Apr 2012 15:48: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:content-type; bh=EqUKx967eyx1fG8H2qVyN3jyTpjz4jqOnAk1V01JySw=; b=dkoZzyoZlop9o9ojrgK1jo7hsu8kL1daBr2Cd9lJWDUk6QYff69jPnkTkpknJMKj+b 0qoklGekLRkt0hcEmimj8NubS+N2lP62f2tHfeEwCYviddtsZzUiJIfVufJecNDzgJu8 klq9lp4H6NiSAjJeuQSXiQ+eMdGR7JgKmgULOJjp3psYzGMiA+qahxfdSaWOjv5Z8ZtW UKX+IWwFafyGpDIdTDavTNvRsXsbcPLrw2xTOc7G64SGZp1IG6Q2DGWCzmVf8dZxR7jP aTGO7OCdSRcblrUlMJusv5ACURxo/gVWN2ral+0lizlZuOO/y+vfCxKKiqR88d6qu85K 4J8g== MIME-Version: 1.0 Received: by 10.42.80.19 with SMTP id t19mr3376171ick.55.1335221287783; Mon, 23 Apr 2012 15:48:07 -0700 (PDT) Received: by 10.231.194.73 with HTTP; Mon, 23 Apr 2012 15:48:07 -0700 (PDT) Date: Mon, 23 Apr 2012 17:48:07 -0500 Message-ID: From: Behcet Sarikaya To: multimob@ietf.org Content-Type: multipart/mixed; boundary=20cf3010ea538e0e3f04be606ed6 Subject: [multimob] Rechartering 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, 23 Apr 2012 22:48:09 -0000 --20cf3010ea538e0e3f04be606ed6 Content-Type: text/plain; charset=ISO-8859-1 Hi all, Based on possible future work discussions we had in IETF 83 in Paris, we have prepared a revised charter which is attached to this mail. Basically a new charter item is proposed on IGMPv3/MLDv2 extensions to support better operation in mobile environments for which there was strong support and DMM multicast for which there was also strong support will be taken up subject to rechartering. Please post your comments/support on the list. Regards, Chairs --20cf3010ea538e0e3f04be606ed6 Content-Type: text/plain; charset=US-ASCII; name="2012-04-23-charter.txt" Content-Disposition: attachment; filename="2012-04-23-charter.txt" Content-Transfer-Encoding: base64 X-Attachment-Id: f_h1e40bbf0 TXVsdGljYXN0IE1vYmlsaXR5IChtdWx0aW1vYikNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t LS0tDQoNCiBDaGFydGVyDQoNCiBDdXJyZW50IFN0YXR1czogQWN0aXZlDQoNCiBDaGFpcnM6DQog ICAgIFN0aWcgVmVuYWFzIDxzdGlnQHZlbmFhcy5jb20+DQogICAgIEJlaGNldCBTYXJpa2F5YSA8 c2FyaWtheWFAaWVlZS5vcmc+DQoNCiBJbnRlcm5ldCBBcmVhIERpcmVjdG9yczoNCiAgICAgUmFs cGggRHJvbXMgPHJkcm9tcy5pZXRmQGdtYWlsLmNvbT4NCiAgICAgQnJpYW4gSGFiZXJtYW4gPGJy aWFuQGlubm92YXRpb25zbGFiLm5ldD4NCg0KIEludGVybmV0IEFyZWEgQWR2aXNvcjoNCiAgICAg QnJpYW4gSy4gSGFiZXJtYW4gPGJyaWFuQGlubm92YXRpb25zbGFiLm5ldD4NCg0KIE1haWxpbmcg TGlzdHM6DQogICAgIEdlbmVyYWwgRGlzY3Vzc2lvbjogbXVsdGltb2JAaWV0Zi5vcmcNCiAgICAg VG8gU3Vic2NyaWJlOiAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZv L211bHRpbW9iDQogICAgIEFyY2hpdmU6ICAgICAgICAgICAgaHR0cDovL3d3dy5pZXRmLm9yZy9t YWlsLWFyY2hpdmUvd2ViL211bHRpbW9iLw0KDQpEZXNjcmlwdGlvbiBvZiBXb3JraW5nIEdyb3Vw Og0KDQogIFRoZSBNdWx0aWNhc3QgbW9iaWxpdHkgKG11bHRpbW9iKSB3b3JraW5nIGdyb3VwIHBy b3ZpZGVzIGd1aWRhbmNlDQogICBmb3Igc3VwcG9ydGluZyBtdWx0aWNhc3QgaW4gYSBtb2JpbGUg ZW52aXJvbm1lbnQuIFRoZSBncm91cCB3aWxsIHdvcmsgDQogICBvbiBleHRlbnNpb25zIG9mIFBy b3h5IE1vYmlsZQ0KICAgSVB2NiB0byBpbXByb3ZlIGl0cyBjYXBhYmlsaXR5IHRvIGhhbmRsZSBt dWx0aWNhc3QgZWZmaWNpZW50bHkuIFdvcmsNCiAgIHJlcXVpcmluZyBtb2RpZmljYXRpb25zIHRv IElHTVB2My9NTER2MiBpcyBvdXQgb2Ygc2NvcGUgaW4gdGhpcw0KICAgc3RhZ2Ugb2YgdGhpcyB3 b3JraW5nIGdyb3VwLCBob3dldmVyLCBhcyBhcmUgbW9kaWZpY2F0aW9ucyB0bw0KICAgbXVsdGlj YXN0IHJvdXRpbmcgcHJvdG9jb2xzLg0KDQogICBTcGVjaWZpYyBnb2FscyBmb3IgdGhlIGdyb3Vw IGFyZToNCg0KICAgLSBBIHNvbHV0aW9uIHRvIHRoZSB0dW5uZWwgY29udmVyZ2VuY2UgcHJvYmxl bSBieSBzZXBhcmF0aW5nDQogICAgIG11bHRpY2FzdCByb3V0aW5nIGZyb20gYSBtb2JpbGl0eSBh bmNob3IuIFBvc3NpYmxlIHRlY2huaXF1ZXMgYXJlDQogICAgIHVzaW5nIG5hdGl2ZSBpbmZyYXN0 cnVjdHVyZSwgdXNpbmcgYSBkZWRpY2F0ZWQgbW9iaWxpdHkgYW5jaG9yDQogICAgIGV0Yy4NCg0K ICAgLSBNZWNoYW5pc21zIHRvIG9wdGltaXplIG11bHRpY2FzdCB0cmFmZmljIGR1cmluZyBhIGhh bmRvdmVyLiBTdWNoDQogICAgIG1lY2hhbmlzbXMgbWF5IGluY2x1ZGUgY29udGV4dCB0cmFuc2Zl ciBmdW5jdGlvbmFsaXR5Lg0KDQogICAtIE1lY2hhbmlzbXMgbmVlZGVkIHRvIHN1cHBvcnQgbXVs dGljYXN0IHNvdXJjZSBtb2JpbGl0eS4gQm90aCBhbnkNCiAgICAgc291cmNlIG11bHRpY2FzdCBh bmQgc291cmNlIHNwZWNpZmljIG11bHRpY2FzdCBzb3VyY2UgbW9iaWxpdHkNCiAgICAgd2lsbCBi ZSBjb3ZlcmVkLg0KDQogICAtIERvY3VtZW50IHRoZSBjb25maWd1cmF0aW9uIG9mIElHTVB2My9N TER2MiBpbiBtb2JpbGUgZW52aXJvbm1lbnRzDQoNCiAgIFRoZSBncm91cCBzaGFsbCBwcmltYXJp bHkgZm9jdXMgb24gUHJveHkgTW9iaWxlIElQdjYgKFBNSVB2NikgYmFzZWQNCiAgIG5ldHdvcmtz IHdoZW4gbG9va2luZyBhdCB0aGUgZmlyc3QgdGhyZWUgaXRlbXMuIEl0IGlzIHBvc3NpYmxlIGJ1 dA0KICAgbm90IHJlcXVpcmVkIHRoYXQgdGhlIHNvbHV0aW9ucyBhcmUgYXBwbGljYWJsZSBhbHNv IGZvciBNb2JpbGUgSVB2Ng0KICAgKE1JUHY2KSBiYXNlZCBuZXR3b3Jrcy4NCg0KICAgRm9yIGJh Y2tncm91bmQsIHRoZSBQTUlQdjYgc3BlY2lmaWNhdGlvbiBhcyBkZWZpbmVkIGluIFJGQyA1MjEz IGRvZXMNCiAgIG5vdCBkZXNjcmliZSBob3cgdG8gc3VwcG9ydCBtdWx0aWNhc3QuIFNvbWUgZm9y bXMgb2YgbXVsdGljYXN0DQogICBzdXBwb3J0IGNhbiwgaG93ZXZlciwgYmUgYnVpbHQgaW4gdGhl IGludm9sdmVkIG5vZGVzIGJ5IHVzaW5nDQogICBleGlzdGluZyBjYXBhYmlsaXRpZXMgb2YgbXVs dGljYXN0IHByb3RvY29scyBhbmQgdGhlIHVuZGVybHlpbmcNCiAgIG1vYmlsaXR5IHByb3RvY29s cy4gVGhlIHdvcmtpbmcgZ3JvdXAgaGFzIGFscmVhZHkgZG9jdW1lbnRlZCBob3cNCiAgIGV4aXN0 aW5nIG1lY2hhbmlzbXMgY2FuIGJlIHVzZWQgdG8gc3VwcG9ydCBtdWx0aWNhc3QsIHdpdGhvdXQN CiAgIHJlcXVpcmluZyBhbnkgYWRkaXRpb25zIG9yIGNoYW5nZXMgdG8gbWVzc2FnZSB0eXBlcyBh bmQgcGFyYW1ldGVycw0KICAgc3BlY2lmaWVkIGluIFJGQyA1MjEzLCBhbmQgYXNzdW1pbmcgYW4g dW5tb2RpZmllZCBtb2JpbGUgaG9zdC4gVGhlDQogICBjdXJyZW50IGdvYWxzIG9mIHRoZSB3b3Jr aW5nIGdyb3VwIHJlbGF0ZSB0byBpbXByb3ZpbmcgdGhlDQogICBlZmZpY2llbmN5IG9mIHRoaXMg YmFzZSBzb2x1dGlvbi4NCg0KICAgSUdNUHYzL01MRHYyIGhhcyBiZWVuIHNwZWNpZmllZCBmb3Ig d2lyZWQgbmV0d29ya3Mgd2l0aCBzaGFyZWQgbGlua3MuDQogICBNb2JpbGUgbm9kZXMgaGF2ZSBu ZWVkcyB0aGF0IGFyZSBzcGVjaWZpYyB0byB3aXJlbGVzcyBuZXR3b3JrcyBhbmQNCiAgIG1vYmls aXR5IChlLmcuIGVudGVyaW5nIGEgZG9ybWFudCBtb2RlIHRvIGNvbnNlcnZlIGJhdHRlcnkgcG93 ZXIsDQogICBtaW5pbWl6aW5nIHRoZSBsYXRlbmN5IGZvciBqb2luaW5nIGFuZCBsZWF2aW5nIGEg Z3JvdXAgaW4gc3VwcG9ydCBvZg0KICAgbW92ZW1lbnQpLg0KDQogICBJbiBwZXJmb3JtaW5nIGl0 cyB3b3JrLCB0aGUgd29ya2luZyBncm91cCB3aWxsIHdvcmsgY2xvc2VseSB3aXRoDQogICBib3Ro IHRoZSBtb2JpbGl0eSBjb21tdW5pdHkgKE5FVEVYVCBXRykgYW5kIHRoZSBtdWx0aWNhc3QgY29t bXVuaXR5DQogICAoTUJPTkVEIFdHKS4gVGhlIGdyb3VwIHdpbGwgY29uc2lkZXIgYm90aCBzb3Vy Y2Ugc3BlY2lmaWMgbXVsdGljYXN0DQogICBhbmQgYW55IHNvdXJjZSBtdWx0aWNhc3QgbXVsdGlj YXN0IG1vZGVscy4NCg0KICAgRnV0dXJlIHdvcmssIHN1YmplY3QgdG8gcmVjaGFydGVyaW5nLCBt YXkgc3R1ZHkvZXZhbHVhdGUgZXh0ZW5zaW9ucw0KICAgdG8gRGlzdHJpYnV0ZWQgTW9iaWxpdHkg TWFuYWdlbWVudCAoZG1tKSBwcm90b2NvbCB0byBzdXBwb3J0IG11bHRpY2FzdC4NCg0KDQpHb2Fs cyBhbmQgTWlsZXN0b25lczoNCiAgTm92IDIwMTAgLSBJbml0aWFsIHZlcnNpb24gb2YgYSBkb2N1 bWVudCBvbiBob3cgdG8gdHVuZSBJR01QdjMvTUxEdjIgZm9yIG1vYmlsaXR5DQogIEFwciAyMDEx IC0gU3VibWl0IGEgZG9jdW1lbnQgb24gaG93IHRvIHR1bmUgSUdNUHYzL01MRHYyIGZvciBtb2Jp bGl0eSwgZm9yIHB1YmxpY2F0aW9uIGFzIGVpdGhlciBJbmZvcm1hdGlvbmFsIG9yIEJlc3QgQ3Vy cmVudCBQcmFjdGljZQ0KICBKdW4gMjAxMSAtIEluaXRpYWwgdmVyc2lvbiBvZiBkb2N1bWVudCBv biBQTUlQdjYgcm91dGluZyBvcHRpbWl6YXRpb25zIHRvIGF2b2lkIHR1bm5lbCBjb252ZXJnZW5j ZSBwcm9ibGVtDQogIE5vdiAyMDExIC0gSW5pdGlhbCB2ZXJzaW9uIG9mIGRvY3VtZW50IG9uIFBN SVB2NiBtdWx0aWNhc3Qgc291cmNlIG1vYmlsaXR5IHNvbHV0aW9uDQogIE5vdiAyMDExIC0gSW5p dGlhbCB2ZXJzaW9uIG9mIGRvY3VtZW50IG9uIFBNSVB2NiBoYW5kb3ZlciBvcHRpbWl6YXRpb25z DQogIEp1biAyMDEyIC0gU3VibWl0IFBNSVB2NiByb3V0aW5nIG9wdGltaXphdGlvbnMgZG9jdW1l bnQgdG8gSUVTRyBmb3IgcHVibGljYXRpb24gYXMgSW5mb3JtYXRpb25hbA0KICBOb3YgMjAxMiAt IFN1Ym1pdCBQTUlQdjYgaGFuZG92ZXIgb3B0aW1pemF0aW9ucyBkb2N1bWVudCB0byBJRVNHIGZv ciBwdWJsaWNhdGlvbiBhcyBFeHBlcmltZW50YWwgU3RhbmRhcmQNCiAgTm92IDIwMTIgLSBTdWJt aXQgUE1JUHY2IG11bHRpY2FzdCBzb3VyY2UgbW9iaWxpdHkgc29sdXRpb24gdG8gSUVTRyBmb3Ig cHVibGljYXRpb24gYXMgSW50ZXJuZXQgU3RhbmRhcmQNCiAgTm92IDIwMTIgLSBJbml0aWFsIHZl cnNpb24gb2YgYSBkb2N1bWVudCBvbiBleHRlbnNpb25zIHRvIElHTVB2My9NTER2MiB0byBzdXBw b3J0IGJldHRlciBvcGVyYXRpb24gaW4gbW9iaWxlIGVudmlyb25tZW50cw0KICBKdW4gMjAxMyAt IFN1Ym1pdCAgSUdNUHYzL01MRHYyIGV4dGVuc2lvbnMgdG8gc3VwcG9ydCBiZXR0ZXIgb3BlcmF0 aW9uIGluIG1vYmlsZSBlbnZpcm9ubWVudHMgdG8gSUVTRyBhcyBJbnRlcm5ldCBTdGFuZGFyZA0K ICBKdW4gMjAxMiAtIERlY2lzaW9uIHRvIGluY2x1ZGUgbmV3IHdvcmsgaW52b2x2aW5nIGV4dGVu c2lvbnMgdG8gZG1tIHByb3RvY29sKHMpDQogIEp1biAyMDEzIC0gUmVjaGFydGVyIGJhc2VkIG9u IHRoZSBhYm92ZSBkZWNpc2lvbnMgKG9yIGNsb3NlIHRoZSBncm91cCBpZiBubyBuZXcgd29yayBp cyBuZWVkZWQpDQogIA== --20cf3010ea538e0e3f04be606ed6-- From seiljeon@gmail.com Tue Apr 24 04:03: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 31FFE21F86C7 for ; Tue, 24 Apr 2012 04:03:44 -0700 (PDT) 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 JlJfe+Mbdpla for ; Tue, 24 Apr 2012 04:03:43 -0700 (PDT) Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 81D2821F86A2 for ; Tue, 24 Apr 2012 04:03:43 -0700 (PDT) Received: by pbbrp16 with SMTP id rp16so5047129pbb.31 for ; Tue, 24 Apr 2012 04:03:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=tQ0HznC+rjOHC9/hxC7oRqo/0K95i/arXDDP2yiBdTo=; b=eRhISYvsLDJc1FaZyaS3EBYN48imZ2samHC/R1tyT+pTRhOtw+O8fGGzcEM8+hOLvt LZxrwyLrQ5Q5Au/9w1fzS5PxsQb/V6jLZ/7t423IPQqOQ1sSQCbvjsuzm/KB1JCYb/VB SsJDEe7yOnXjrMtLnUQZ5Y/qRLdaKzDOaAq0i3jSSzGy1r3N15ME0TZJMmKFCc6y2M/O xi3+o1Ff5QY12QzMXeV6WNnj8VhkaNNhA+uyNVFOzOffcF7lhMpcCVGF804qNk92nCGr x5qncFMCnGnV6IU+MKH3lUFEPlLerHG7H4IYialo8bvWeg4wHnGdRKuHqxRQRwS065Cc v9Jg== MIME-Version: 1.0 Received: by 10.68.229.200 with SMTP id ss8mr66514pbc.57.1335265423305; Tue, 24 Apr 2012 04:03:43 -0700 (PDT) Sender: seiljeon@gmail.com Received: by 10.68.6.230 with HTTP; Tue, 24 Apr 2012 04:03:43 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Apr 2012 12:03:43 +0100 X-Google-Sender-Auth: VPBt4a0wVv0kpJlr8LkkjBm-jP4 Message-ID: From: Seil Jeon To: sarikaya@ieee.org Content-Type: multipart/alternative; boundary=047d7b339bb13caba104be6ab5d5 Cc: multimob@ietf.org Subject: Re: [multimob] Rechartering 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, 24 Apr 2012 11:03:44 -0000 --047d7b339bb13caba104be6ab5d5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Behcet, Thanks to trigger new charter agenda. "Extension to DMM protocol ~" seems to be too much early. As we told in Paris meeting, MULTIMOB needs to check the base solution in DMM. ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------------- Future work, subject to rechartering, may study use cases of the base solution in DMM, and evaluate performance impact. >From that point, it may discuss MULTIMOB extensions to DMM protocol based on the identified problem(s). . ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------------- Seil Jeon *I**nstituto de **T**elecomunica=E7=F5es* Campus Universit=E1rio de Santiago P-3810-193 Aveiro - Portugal Homepage: http://sites.google.com/site/seiljeon LinkedIn: http://www.linkedin.com/profile/view?id=3D150370825&trk=3Dtab_pro 2012/4/23 Behcet Sarikaya > Hi all, > > Based on possible future work discussions we had in IETF 83 in Paris, > we have prepared a revised charter which is attached to this mail. > > Basically a new charter item is proposed on IGMPv3/MLDv2 extensions to > support better operation in mobile environments for which there was > strong support > > and > > DMM multicast for which there was also strong support will be taken up > subject to rechartering. > > Please post your comments/support on the list. > > Regards, > > Chairs > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > > --047d7b339bb13caba104be6ab5d5 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Behcet,
=A0
Thanks to trigger new charter agenda.
<= div class=3D"gmail_extra">=A0
"Extensi= on to DMM protocol ~" seems to be too much early. As we told in Paris = meeting, MULTIMOB needs to check the base solution in DMM.
=A0
------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= --------------------
Future work, subject to rechartering, may study = use cases of the base solution in DMM, and evaluate performance impact.
From that point, it may discuss MULTIMOB exten= sions to DMM protocol based on the identified problem(s).
.
--------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= ------------------
=A0
Seil J= eon
=A0

I= nstituto de T<= span style=3D"color:rgb(0,32,96)" lang=3D"PT">elecomunica=E7=F5es

Campus Univers= it=E1rio de Santiago

P-3810-193 Ave= iro - Portugal

=A0

Homepage: http://sites.google.= com/site/seiljeon

LinkedIn: http://www.linkedin.com/profile/view?id=3D150370825&trk=3Dt= ab_pro


=A0
2012/4/23 Behcet Sarikaya <sarikaya2012@gmail.com>=
Hi all,

Based on possible future work discussions we had in IETF 83 in Paris,
we have prepared a revised charter which is attached to this mail.

Basically a new charter item is proposed on IGMPv3/MLDv2 extensions to
support better operation in mobile environments for which there was
strong support

and

DMM multicast for which there was also strong support will be taken up
subject to rechartering.

Please post your comments/support on the list.

Regards,

Chairs

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


--047d7b339bb13caba104be6ab5d5-- From sarikaya2012@gmail.com Tue Apr 24 07:07: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 5BA9921F87A7 for ; Tue, 24 Apr 2012 07:07:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.544 X-Spam-Level: X-Spam-Status: No, score=-3.544 tagged_above=-999 required=5 tests=[AWL=0.055, 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 8x7CSRA8qELC for ; Tue, 24 Apr 2012 07:07:17 -0700 (PDT) Received: from mail-yw0-f44.google.com (mail-yw0-f44.google.com [209.85.213.44]) by ietfa.amsl.com (Postfix) with ESMTP id BF93721F87A3 for ; Tue, 24 Apr 2012 07:07:17 -0700 (PDT) Received: by yhkk25 with SMTP id k25so429755yhk.31 for ; Tue, 24 Apr 2012 07:07:17 -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=XxYTvC6vIjPyKODxhbLYtVM8snDE4A7qtPsfblGHRmw=; b=taXtcsOVwrodT+uc+gPy9j2+Qu1Dpx+pSFn0ljxwAfyvZKmLQB4pb+7+Jnz43AIbNr 6YIWfjt0R9H5mmPNPFjZzYMC2di3Jb3evkQ/uRVSB5KOjgFMyvnPktJQLYSmJyyQM7bB Gl4bmmx0sWchjQsKUwzI3PpL2upxEPTCieM/etANZtG/qwm972Ek4l0maZIP1BZ0xwNF 4NymDAxw4NRDZOZOeFNNqty72iLD5rwJMxo2h6YJyvP9M50pmUP+/T/S9i7YmS1KpkQh ZTGQOYMHtmzO3Wv9BMB6ttZ/RytJ9cOzS3FKoNc5si5cRZUTZsZg56VNRfG4BqKctf6c uCew== MIME-Version: 1.0 Received: by 10.50.47.135 with SMTP id d7mr10172073ign.66.1335276436753; Tue, 24 Apr 2012 07:07:16 -0700 (PDT) Received: by 10.231.194.73 with HTTP; Tue, 24 Apr 2012 07:07:16 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Apr 2012 09:07:16 -0500 Message-ID: From: Behcet Sarikaya To: Seil Jeon Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: multimob@ietf.org Subject: Re: [multimob] Rechartering 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, 24 Apr 2012 14:07:18 -0000 Hi Seil, On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon wrote: > Hi Behcet, > > Thanks to trigger new charter agenda. > > "Extension to DMM protocol ~" seems to be too much early. As we told in > Paris meeting, MULTIMOB needs to check the base solution in DMM. > I think the text is clear, this item is possible future charter item, when the time comes we are going to discuss it and set the milestones accordingly. Regards, Behcet > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------- > Future work, subject to rechartering, may study use cases of the base > solution in DMM, and evaluate performance impact. > From that point, it may discuss MULTIMOB extensions to DMM protocol based= on > the identified problem(s). > . > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------- > > Seil Jeon > > > Instituto de Telecomunica=E7=F5es > > Campus Universit=E1rio de Santiago > > P-3810-193 Aveiro - Portugal > > > > Homepage: http://sites.google.com/site/seiljeon > > LinkedIn: http://www.linkedin.com/profile/view?id=3D150370825&trk=3Dtab_p= ro > > > > 2012/4/23 Behcet Sarikaya >> >> Hi all, >> >> Based on possible future work discussions we had in IETF 83 in Paris, >> we have prepared a revised charter which is attached to this mail. >> >> Basically a new charter item is proposed on IGMPv3/MLDv2 extensions to >> support better operation in mobile environments for which there was >> strong support >> >> and >> >> DMM multicast for which there was also strong support will be taken up >> subject to rechartering. >> >> Please post your comments/support on the list. >> >> Regards, >> >> Chairs >> >> _______________________________________________ >> multimob mailing list >> multimob@ietf.org >> https://www.ietf.org/mailman/listinfo/multimob >> > From sarikaya2012@gmail.com Tue Apr 24 07:35:05 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 678DC21F8833 for ; Tue, 24 Apr 2012 07:35:05 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.547 X-Spam-Level: X-Spam-Status: No, score=-3.547 tagged_above=-999 required=5 tests=[AWL=0.052, 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 hFcbDLx-VIv0 for ; Tue, 24 Apr 2012 07:35:04 -0700 (PDT) Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0CD4F21F882E for ; Tue, 24 Apr 2012 07:34:57 -0700 (PDT) Received: by yenm5 with SMTP id m5so459329yen.31 for ; Tue, 24 Apr 2012 07:34:57 -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; bh=oDY9nLeORXgnyun2XZuQaKWpz842tdDScrQ6zdCqXjg=; b=N9OnLMVTES6i+Ad3LBUrjOLYeRYZdl+Bpl/5gkus76cW6+kMsiM+NxBMEdwPu6OhLt mPVDnXMKHn/N8ae3/FvjWA8xOS+iM1mNOkI72Awa8/chvsngxQgMHGptDHDThsxukXAN qUNyDJ2f6n+8O/fUrhK1l2xrBmiKTYYQF5qpNEhxqGIkkcdvzoItJ4Pyr3J8EwWwGYZK fQeYsz7TrnQS5/dr3m3iOGuVPIR9W+cF89enjORexn8pgGZLB0daBUhgV2Ap1RRdLta9 5Z6+/sSN1aA1L2QWlASr2deihqEpugPBlUi7YnQngAHZOZ2WXOsKucGrOhu+qb+ED0+Z Je8A== MIME-Version: 1.0 Received: by 10.50.47.135 with SMTP id d7mr10315646ign.66.1335278095252; Tue, 24 Apr 2012 07:34:55 -0700 (PDT) Received: by 10.231.194.73 with HTTP; Tue, 24 Apr 2012 07:34:55 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Apr 2012 09:34:55 -0500 Message-ID: From: Behcet Sarikaya To: "Rahman, Akbar" Content-Type: text/plain; charset=ISO-8859-1 Cc: multimob@ietf.org Subject: Re: [multimob] Rechartering 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, 24 Apr 2012 14:35:05 -0000 Yes, I am attaching it inline now: Multicast Mobility (multimob) ----------------------------- Charter Current Status: Active Chairs: Stig Venaas Behcet Sarikaya Internet Area Directors: Ralph Droms Brian Haberman Internet Area Advisor: Brian K. Haberman Mailing Lists: General Discussion: multimob@ietf.org To Subscribe: https://www.ietf.org/mailman/listinfo/multimob Archive: http://www.ietf.org/mail-archive/web/multimob/ Description of Working Group: The Multicast mobility (multimob) working group provides guidance for supporting multicast in a mobile environment. The group will work on extensions of Proxy Mobile IPv6 to improve its capability to handle multicast efficiently. Work requiring modifications to IGMPv3/MLDv2 is out of scope in this stage of this working group, however, as are modifications to multicast routing protocols. Specific goals for the group are: - A solution to the tunnel convergence problem by separating multicast routing from a mobility anchor. Possible techniques are using native infrastructure, using a dedicated mobility anchor etc. - Mechanisms to optimize multicast traffic during a handover. Such mechanisms may include context transfer functionality. - Mechanisms needed to support multicast source mobility. Both any source multicast and source specific multicast source mobility will be covered. - Document the configuration of IGMPv3/MLDv2 in mobile environments The group shall primarily focus on Proxy Mobile IPv6 (PMIPv6) based networks when looking at the first three items. It is possible but not required that the solutions are applicable also for Mobile IPv6 (MIPv6) based networks. For background, the PMIPv6 specification as defined in RFC 5213 does not describe how to support multicast. Some forms of multicast support can, however, be built in the involved nodes by using existing capabilities of multicast protocols and the underlying mobility protocols. The working group has already documented how existing mechanisms can be used to support multicast, without requiring any additions or changes to message types and parameters specified in RFC 5213, and assuming an unmodified mobile host. The current goals of the working group relate to improving the efficiency of this base solution. IGMPv3/MLDv2 has been specified for wired networks with shared links. Mobile nodes have needs that are specific to wireless networks and mobility (e.g. entering a dormant mode to conserve battery power, minimizing the latency for joining and leaving a group in support of movement). In performing its work, the working group will work closely with both the mobility community (NETEXT WG) and the multicast community (MBONED WG). The group will consider both source specific multicast and any source multicast multicast models. Future work, subject to rechartering, may study/evaluate extensions to Distributed Mobility Management (dmm) protocol to support multicast. Goals and Milestones: Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for mobility Apr 2011 - Submit a document on how to tune IGMPv3/MLDv2 for mobility, for publication as either Informational or Best Current Practice Jun 2011 - Initial version of document on PMIPv6 routing optimizations to avoid tunnel convergence problem Nov 2011 - Initial version of document on PMIPv6 multicast source mobility solution Nov 2011 - Initial version of document on PMIPv6 handover optimizations Jun 2012 - Submit PMIPv6 routing optimizations document to IESG for publication as Informational Nov 2012 - Submit PMIPv6 handover optimizations document to IESG for publication as Experimental Standard Nov 2012 - Submit PMIPv6 multicast source mobility solution to IESG for publication as Internet Standard Nov 2012 - Initial version of a document on extensions to IGMPv3/MLDv2 to support better operation in mobile environments Jun 2013 - Submit IGMPv3/MLDv2 extensions to support better operation in mobile environments to IESG as Internet Standard Jun 2012 - Decision to include new work involving extensions to dmm protocol(s) Jun 2013 - Recharter based on the above decisions (or close the group if no new work is needed) From seiljeon@gmail.com Tue Apr 24 07:50: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 2B08A21F8855 for ; Tue, 24 Apr 2012 07:50:36 -0700 (PDT) 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=[AWL=-0.000, 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 1TA9LC2Ub0Cl for ; Tue, 24 Apr 2012 07:50:35 -0700 (PDT) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 4AD8421F8858 for ; Tue, 24 Apr 2012 07:50:32 -0700 (PDT) Received: by dady13 with SMTP id y13so1373423dad.27 for ; Tue, 24 Apr 2012 07:50:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=L6g68uC2UyQVG7NGFKPqpXcxU7O0hVUTGbXtfN7oPq4=; b=AMunAnrGBgKeBQAhJAEGLlquLVPGlfB4+Q6Hv/qC+k5Hw0jTz7Qj316mexSiVqIx5A C4gtLNS3scRM2zGPsFAWlDkPJfDESsVq350qvLJs8vbzOEPqsFrGViN1HaC32hLBI/Ix g0seTTRHfLzyLTGoaJesKzgMCvELG7X5o+daoufLA1QGigLMuA3Mj/VWK9AHcTlh+HgL 4Tn4MlUe8tekU8Q8TWnxlSDimiwM4E3CeC1crPApIJHA1oehmmPCGNLdiZeamrKYJrSR DamZ/YJb9oMNy31Z39b6C2ACPROoka5V/H4UEEKVuCW1dIJnSJG9g8RnjUYJPYJNLTEX IC6Q== MIME-Version: 1.0 Received: by 10.68.131.74 with SMTP id ok10mr2864585pbb.99.1335279031941; Tue, 24 Apr 2012 07:50:31 -0700 (PDT) Sender: seiljeon@gmail.com Received: by 10.68.6.230 with HTTP; Tue, 24 Apr 2012 07:50:31 -0700 (PDT) In-Reply-To: References: Date: Tue, 24 Apr 2012 15:50:31 +0100 X-Google-Sender-Auth: uUDoNFWm5-hq6tFZ4zWw6cSpWj8 Message-ID: From: Seil Jeon To: sarikaya@ieee.org Content-Type: multipart/alternative; boundary=047d7b15ae295ffb5304be6de0b2 Cc: multimob@ietf.org Subject: Re: [multimob] Rechartering 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, 24 Apr 2012 14:50:36 -0000 --047d7b15ae295ffb5304be6de0b2 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Behcet, My comment was not clear.. and yes it is possible for future multimob item. But I want that part should be revised as follows: ----------- Future work, subject to rechartering, may study use cases of the base solution in DMM, and evaluate performance impact. From that point, it may discuss MULTIMOB extensions to DMM protocol based on the identified problem(s). ----------- Regards, Seil Jeon 2012/4/24 Behcet Sarikaya > Hi Seil, > > On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon wrote: > > Hi Behcet, > > > > Thanks to trigger new charter agenda. > > > > "Extension to DMM protocol ~" seems to be too much early. As we told in > > Paris meeting, MULTIMOB needs to check the base solution in DMM. > > > > I think the text is clear, this item is possible future charter item, > when the time comes we are going to discuss it and set the milestones > accordingly. > > Regards, > > Behcet > > > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------- > > Future work, subject to rechartering, may study use cases of the base > > solution in DMM, and evaluate performance impact. > > From that point, it may discuss MULTIMOB extensions to DMM protocol > based on > > the identified problem(s). > > . > > > -------------------------------------------------------------------------= ---------------------------------------------------------------------------= ---------------------------------- > > > > Seil Jeon > > > > > > Instituto de Telecomunica=E7=F5es > > > > Campus Universit=E1rio de Santiago > > > > P-3810-193 Aveiro - Portugal > > > > > > > > Homepage: http://sites.google.com/site/seiljeon > > > > LinkedIn: http://www.linkedin.com/profile/view?id=3D150370825&trk=3Dtab= _pro > > > > > > > > 2012/4/23 Behcet Sarikaya > >> > >> Hi all, > >> > >> Based on possible future work discussions we had in IETF 83 in Paris, > >> we have prepared a revised charter which is attached to this mail. > >> > >> Basically a new charter item is proposed on IGMPv3/MLDv2 extensions to > >> support better operation in mobile environments for which there was > >> strong support > >> > >> and > >> > >> DMM multicast for which there was also strong support will be taken up > >> subject to rechartering. > >> > >> Please post your comments/support on the list. > >> > >> Regards, > >> > >> Chairs > >> > >> _______________________________________________ > >> multimob mailing list > >> multimob@ietf.org > >> https://www.ietf.org/mailman/listinfo/multimob > >> > > > --047d7b15ae295ffb5304be6de0b2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Behcet,
=A0
My comment was not clear.. and yes it is pos= sible for future multimob item.
=A0
But I want that part should be revised as follows:
=A0
-----------
Future work, subject to rechartering, may study use cases of t= he base solution in DMM, and evaluate performance impact. From that point, = it may discuss MULTIMOB extensions to DMM protocol based on the identified = problem(s).
-----------
=A0
Regards,
=A0
Seil Jeon
2012/4/24 Behcet Sarik= aya <sarikaya2012@gmail.com>
Hi Seil,

On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon <sijeon79@gmail.com> wrote:
> Hi Behcet,
>
> Thanks to trigger new charter agenda.
>
> "Extension to DMM protocol ~" seems to be too much early. As= we told in
> Paris meeting, MULTIMOB needs to check the base solution in DMM.
>

I think the text is clear, this item is possible future charter item,=
when the time comes we are going to discuss it and set the milestones
accordingly.

Regards,

Behcet
> ------------------------------= ---------------------------------------------------------------------------= ---------------------------------------------------------------------------= --
> Future work, subject to rechartering, may study use cases of the base<= br> > solution in DMM, and evaluate performance impact.
> From that point, it may discuss MULTIMOB extensions to DMM protocol ba= sed on
> the identified problem(s).
> .
> ----------------------------------------------------------------------= ---------------------------------------------------------------------------= -------------------------------------
>
> Seil Jeon
>
>
> Instituto de Telecomunica=E7=F5es
>
> Campus Universit=E1rio de Santiago
>
> P-3810-193 Aveiro - Portugal
>
>
>
> Homepage: http://sites.google.com/site/seiljeon
>
> LinkedIn: http://www.linkedin.com/profile/vie= w?id=3D150370825&trk=3Dtab_pro
>
>
>
> 2012/4/23 Behcet Sarikaya <sarikaya2012@gmail.com>
>>
>> Hi all,
>>
>> Based on possible future work discussions we had in IETF 83 in Par= is,
>> we have prepared a revised charter which is attached to this mail.=
>>
>> Basically a new charter item is proposed on IGMPv3/MLDv2 extension= s to
>> support better operation in mobile environments for which there wa= s
>> strong support
>>
>> and
>>
>> DMM multicast for which there was also strong support will be take= n up
>> subject to rechartering.
>>
>> Please post your comments/support on the list.
>>
>> Regards,
>>
>> Chairs
>>
>> _______________________________________________
>> multimob mailing list
>> multimob@ietf.org
>> https://www.ietf.org/mailman/listinfo/multimob
>>
>

--047d7b15ae295ffb5304be6de0b2-- From stig@venaas.com Tue Apr 24 10:10:40 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 C7EAC21E80A6 for ; Tue, 24 Apr 2012 10:10:40 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -102.599 X-Spam-Level: X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id AbAPUpVTy39W for ; Tue, 24 Apr 2012 10:10:40 -0700 (PDT) Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by ietfa.amsl.com (Postfix) with ESMTP id A904F21E80A1 for ; Tue, 24 Apr 2012 10:10:39 -0700 (PDT) Received: from [10.33.12.93] (128-107-239-233.cisco.com [128.107.239.233]) by ufisa.uninett.no (Postfix) with ESMTPSA id BB0937FF8; Tue, 24 Apr 2012 19:10:37 +0200 (CEST) Message-ID: <4F96DE87.1030805@venaas.com> Date: Tue, 24 Apr 2012 10:10:31 -0700 From: Stig Venaas User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: Seil Jeon References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: multimob@ietf.org Subject: Re: [multimob] Rechartering 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, 24 Apr 2012 17:10:40 -0000 On 4/24/2012 7:50 AM, Seil Jeon wrote: > Hi Behcet, > My comment was not clear.. and yes it is possible for future multimob item. > But I want that part should be revised as follows: > ----------- > Future work, subject to rechartering, may study use cases of the base > solution in DMM, and evaluate performance impact. From that point, it > may discuss MULTIMOB extensions to DMM protocol based on the identified > problem(s). I think we can skip the DMM part actually. Since it would be subject to rechartering, we would need to change the charter anyway. Even if we say "subject to rechartering" here, we may not be allowed to work on it. Also, if we don't mention DMM here, we can still get it in a new charter. Basically, I don't think a charter needs to talk about possibilities for future charters. Whether we say it or not, it all depends on what the group wants to work on, what the IESG thinks it makes sens for us to work on, etc. Stig > ----------- > Regards, > Seil Jeon > 2012/4/24 Behcet Sarikaya > > > Hi Seil, > > On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon > wrote: > > Hi Behcet, > > > > Thanks to trigger new charter agenda. > > > > "Extension to DMM protocol ~" seems to be too much early. As we > told in > > Paris meeting, MULTIMOB needs to check the base solution in DMM. > > > > I think the text is clear, this item is possible future charter item, > when the time comes we are going to discuss it and set the milestones > accordingly. > > Regards, > > Behcet > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Future work, subject to rechartering, may study use cases of the base > > solution in DMM, and evaluate performance impact. > > From that point, it may discuss MULTIMOB extensions to DMM > protocol based on > > the identified problem(s). > > . > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Seil Jeon > > > > > > Instituto de Telecomunicações > > > > Campus Universitário de Santiago > > > > P-3810-193 Aveiro - Portugal > > > > > > > > Homepage: http://sites.google.com/site/seiljeon > > > > LinkedIn: > http://www.linkedin.com/profile/view?id=150370825&trk=tab_pro > > > > > > > > > 2012/4/23 Behcet Sarikaya > > >> > >> Hi all, > >> > >> Based on possible future work discussions we had in IETF 83 in > Paris, > >> we have prepared a revised charter which is attached to this mail. > >> > >> Basically a new charter item is proposed on IGMPv3/MLDv2 > extensions to > >> support better operation in mobile environments for which there was > >> strong support > >> > >> and > >> > >> DMM multicast for which there was also strong support will be > taken up > >> subject to rechartering. > >> > >> Please post your comments/support on the list. > >> > >> Regards, > >> > >> Chairs > >> > >> _______________________________________________ > >> multimob mailing list > >> multimob@ietf.org > >> https://www.ietf.org/mailman/listinfo/multimob > >> > > > > > > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob From seiljeon@gmail.com Tue Apr 24 12:06:24 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 7668921E80A4 for ; Tue, 24 Apr 2012 12:06:24 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.765 X-Spam-Level: X-Spam-Status: No, score=-2.765 tagged_above=-999 required=5 tests=[AWL=-0.833, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, SARE_HTML_USL_OBFU=1.666] 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 ELvJeihJZHym for ; Tue, 24 Apr 2012 12:06:23 -0700 (PDT) Received: from mail-pz0-f54.google.com (mail-pz0-f54.google.com [209.85.210.54]) by ietfa.amsl.com (Postfix) with ESMTP id 7F06021E80BC for ; Tue, 24 Apr 2012 12:06:23 -0700 (PDT) Received: by dady13 with SMTP id y13so1786949dad.27 for ; Tue, 24 Apr 2012 12:06:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=meZSXexFRfLydsJkJB5yHm+jfIBpIw0IY15etTHu6+k=; b=mzZ7faCdSiikDTGcIFzbRI1L4y7fTGTtmRrD8+Bhu2GAWU/lK+oh9SfQGqWg2QzzCQ E9Ur/OEjjNhmTM0hilXVALG9dtadMTjt5Ds1d68DJm1/SIqsYC5Zi9uD2k92D8VuChgc AI6TSFLn0qN3kLjE9B/lUt49YOYFO/dsxcADcXyBThKOiXJW1m73x/p+W9UgDpsxZsFg lQcVZOl0tpdshIP/NQso8BdFiNzJ9T8xxn/gIQr/iaYdzeyKokx6ffTmOAXTE1hfsNma kdQR5ECGUBVyGFoltBTmSU1WSuFlTDEf8RkxUUhD1+KTA//gjtQzYzzv+/xPt4VrPg97 96RA== MIME-Version: 1.0 Received: by 10.68.136.137 with SMTP id qa9mr201015pbb.78.1335294383274; Tue, 24 Apr 2012 12:06:23 -0700 (PDT) Sender: seiljeon@gmail.com Received: by 10.68.6.230 with HTTP; Tue, 24 Apr 2012 12:06:23 -0700 (PDT) In-Reply-To: <4F96DE87.1030805@venaas.com> References: <4F96DE87.1030805@venaas.com> Date: Tue, 24 Apr 2012 20:06:23 +0100 X-Google-Sender-Auth: D4XTU1bGAhHJm9S5Np6MLnXciW0 Message-ID: From: Seil Jeon To: Stig Venaas Content-Type: multipart/alternative; boundary=047d7b10cff762bc6a04be717379 Cc: multimob@ietf.org Subject: Re: [multimob] Rechartering 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, 24 Apr 2012 19:06:24 -0000 --047d7b10cff762bc6a04be717379 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi Stig, See the comments in line. Best Regards, Seil 2012/4/24 Stig Venaas > On 4/24/2012 7:50 AM, Seil Jeon wrote: > >> Hi Behcet, >> My comment was not clear.. and yes it is possible for future multimob >> item. >> But I want that part should be revised as follows: >> ----------- >> Future work, subject to rechartering, may study use cases of the base >> solution in DMM, and evaluate performance impact. From that point, it >> may discuss MULTIMOB extensions to DMM protocol based on the identified >> problem(s). >> > > I think we can skip the DMM part actually. Since it would be subject to > rechartering, we would need to change the charter anyway. Even if we say > "subject to rechartering" here, we may not be allowed to work on it. > Also, if we don't mention DMM here, we can still get it in a new > charter. > > Basically, I don't think a charter needs to talk about possibilities > for future charters. Whether we say it or not, it all depends on what > the group wants to work on, what the IESG thinks it makes sens for us > to work on, etc. > Of course, a charter item will be determined by AD or IESG. Regarding on putting DMM related proposal, I remember we got a positive signal in Paris meeting. So we'd better to keep recharter description written by Behcet for now. As you said, this will be confirmed by IESG. In this sense, I support revised charter. > Stig > > ----------- >> Regards, >> Seil Jeon >> 2012/4/24 Behcet Sarikaya > > >> >> >> Hi Seil, >> >> On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon > > wrote: >> > Hi Behcet, >> > >> > Thanks to trigger new charter agenda. >> > >> > "Extension to DMM protocol ~" seems to be too much early. As we >> told in >> > Paris meeting, MULTIMOB needs to check the base solution in DMM. >> > >> >> I think the text is clear, this item is possible future charter item, >> when the time comes we are going to discuss it and set the milestones >> accordingly. >> >> Regards, >> >> Behcet >> > >> ------------------------------**------------------------------** >> ------------------------------**------------------------------** >> ------------------------------**------------------------------**-- >> > Future work, subject to rechartering, may study use cases of the >> base >> > solution in DMM, and evaluate performance impact. >> > From that point, it may discuss MULTIMOB extensions to DMM >> protocol based on >> > the identified problem(s). >> > . >> > >> ------------------------------**------------------------------** >> ------------------------------**------------------------------** >> ------------------------------**------------------------------**-- >> > >> > Seil Jeon >> > >> > >> > Instituto de Telecomunica=E7=F5es >> > >> > Campus Universit=E1rio de Santiago >> > >> > P-3810-193 Aveiro - Portugal >> > >> > >> > >> > Homepage: http://sites.google.com/site/**seiljeon >> > >> > LinkedIn: >> http://www.linkedin.com/**profile/view?id=3D150370825&trk=3D**tab_pro= >> >> > >> > >> > >> > >> > 2012/4/23 Behcet Sarikaya > > >> >> >> >> >> Hi all, >> >> >> >> Based on possible future work discussions we had in IETF 83 in >> Paris, >> >> we have prepared a revised charter which is attached to this mail= . >> >> >> >> Basically a new charter item is proposed on IGMPv3/MLDv2 >> extensions to >> >> support better operation in mobile environments for which there w= as >> >> strong support >> >> >> >> and >> >> >> >> DMM multicast for which there was also strong support will be >> taken up >> >> subject to rechartering. >> >> >> >> Please post your comments/support on the list. >> >> >> >> Regards, >> >> >> >> Chairs >> >> >> >> ______________________________**_________________ >> >> multimob mailing list >> >> multimob@ietf.org >> >> https://www.ietf.org/mailman/**listinfo/multimob >> >> >> >> > >> >> >> >> >> ______________________________**_________________ >> multimob mailing list >> multimob@ietf.org >> https://www.ietf.org/mailman/**listinfo/multimob >> > > --047d7b10cff762bc6a04be717379 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi Stig,
=A0
See the comments in line.
Best Regards,
=A0
Seil
=A0
=A0
2012/4/24 Stig Venaas <stig@venaas.com= >
On 4/24/2012 7:50 AM, Seil Jeon wrote:
Hi Behcet,
My comment was not clear.. and yes it is possible for future multimob item.=
But I want that part should be revised as follows:
-----------
Future work, subject to rechartering, may study use cases of the base
solution in DMM, and evaluate performance impact. From that point, it
may discuss MULTIMOB extensions to DMM protocol based on the identified
problem(s).

I think we can skip the DMM part actually. Since it would be subject to
rechartering, we would need to change the charter anyway. Even if we say "subject to rechartering" here, we may not be allowed to work on = it.
Also, if we don't mention DMM here, we can still get it in a new
charter.

Basically, I don't think a charter needs to talk about possibilities for future charters. Whether we say it or not, it all depends on what
the group wants to work on, what the IESG thinks it makes sens for us
to work on, etc.
=A0
Of course,=A0a charter = item=A0will be determined by AD or IESG.
Regarding on putting DMM= related proposal,=A0I remember we got a positive signal in Paris meeting.<= /div>
So we'd better to keep=A0recharter=A0description=A0written by Behc= et for now. As you said, this will be confirmed by IESG.
=A0
In this sense, I support revised charter.
=A0
=A0=
Stig

-----------
Regards,
Seil Jeon
2012/4/24 Behcet Sarikaya <sarikaya2012@gmail.com
<mailto:sari= kaya2012@gmail.com>>


=A0 =A0Hi Seil,

=A0 =A0On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon <sijeon79@gmail.com
=A0 =A0<mailto:= sijeon79@gmail.com>> wrote:
=A0 =A0 > Hi Behcet,
=A0 =A0 >
=A0 =A0 > Thanks to trigger new charter agenda.
=A0 =A0 >
=A0 =A0 > "Extension to DMM protocol ~" seems to be too much = early. As we
=A0 =A0told in
=A0 =A0 > Paris meeting, MULTIMOB needs to check the base solution in D= MM.
=A0 =A0 >

=A0 =A0I think the text is clear, this item is possible future charter ite= m,
=A0 =A0when the time comes we are going to discuss it and set the mileston= es
=A0 =A0accordingly.

=A0 =A0Regards,

=A0 =A0Behcet
=A0 =A0 >
=A0 =A0------------------------------------------------------------= ------------------------------------------------------------<= u>--------------------------------------------------------------
=A0 =A0 > Future work, subject to rechartering, may study use cases of = the base
=A0 =A0 > solution in DMM, and evaluate performance impact.
=A0 =A0 > From that point, it may discuss MULTIMOB extensions to DMM =A0 =A0protocol based on
=A0 =A0 > the identified problem(s).
=A0 =A0 > .
=A0 =A0 >
=A0 =A0------------------------------------------------------------= ------------------------------------------------------------<= u>--------------------------------------------------------------
=A0 =A0 >
=A0 =A0 > Seil Jeon
=A0 =A0 >
=A0 =A0 >
=A0 =A0 > Instituto de Telecomunica=E7=F5es
=A0 =A0 >
=A0 =A0 > Campus Universit=E1rio de Santiago
=A0 =A0 >
=A0 =A0 > P-3810-193 Aveiro - Portugal
=A0 =A0 >
=A0 =A0 >
=A0 =A0 >
=A0 =A0 > Homepage: http://sites.google.com/site/seiljeon
=A0 =A0 >
=A0 =A0 > LinkedIn:
=A0 =A0http://www.linkedin.com/profile/vie= w?id=3D150370825&trk=3Dtab_pro
=A0 =A0<http://www.linkedin.com/profile= /view?id=3D150370825&trk=3Dtab_pro>
=A0 =A0 >
=A0 =A0 >
=A0 =A0 >
=A0 =A0 > 2012/4/23 Behcet Sarikaya <sarikaya2012@gmail.com
=A0 =A0<mailto:sarikaya2012@gmail.com>>

=A0 =A0 >>
=A0 =A0 >> Hi all,
=A0 =A0 >>
=A0 =A0 >> Based on possible future work discussions we had in IETF = 83 in
=A0 =A0Paris,
=A0 =A0 >> we have prepared a revised charter which is attached to t= his mail.
=A0 =A0 >>
=A0 =A0 >> Basically a new charter item is proposed on IGMPv3/MLDv2<= br> =A0 =A0extensions to
=A0 =A0 >> support better operation in mobile environments for which= there was
=A0 =A0 >> strong support
=A0 =A0 >>
=A0 =A0 >> and
=A0 =A0 >>
=A0 =A0 >> DMM multicast for which there was also strong support wil= l be
=A0 =A0taken up
=A0 =A0 >> subject to rechartering.
=A0 =A0 >>
=A0 =A0 >> Please post your comments/support on the list.
=A0 =A0 >>
=A0 =A0 >> Regards,
=A0 =A0 >>
=A0 =A0 >> Chairs
=A0 =A0 >>
=A0 =A0 >> _______________________________________________ =A0 =A0 >> multimob mailing list
=A0 =A0 >> mu= ltimob@ietf.org <mailto:multimob@ietf.org>
=A0 =A0 >> https://www.ietf.org/mailman/listinfo/multimob

=A0 =A0 >>
=A0 =A0 >




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


--047d7b10cff762bc6a04be717379-- From sfigueiredo@av.it.pt Wed Apr 25 12:03:21 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 42FFF21F87FD for ; Wed, 25 Apr 2012 12:03:21 -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 5YbVKA3H4avH for ; Wed, 25 Apr 2012 12:03:20 -0700 (PDT) Received: from av.it.pt (mail.av.it.pt [193.136.92.53]) by ietfa.amsl.com (Postfix) with ESMTP id 8D4A921F87EA for ; Wed, 25 Apr 2012 12:03:18 -0700 (PDT) Received: from [217.129.25.167] (account sfigueiredo@av.it.pt HELO [192.168.2.102]) by av.it.pt (CommuniGate Pro SMTP 5.4.2) with ESMTPSA id 64463814 for multimob@ietf.org; Wed, 25 Apr 2012 20:03:17 +0100 Message-ID: <4F984A74.2030608@av.it.pt> Date: Wed, 25 Apr 2012 20:03:16 +0100 From: =?ISO-8859-1?Q?S=E9rgio_Figueiredo?= User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.28) Gecko/20120313 Lightning/1.0b2 Thunderbird/3.1.20 MIME-Version: 1.0 To: multimob@ietf.org References: <4F96DE87.1030805@venaas.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------090407000805030303040703" Subject: Re: [multimob] Rechartering 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, 25 Apr 2012 19:03:21 -0000 This is a multi-part message in MIME format. --------------090407000805030303040703 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Hi Behcet, Stig, all, I agree with Seil. Due to the strong interest shown in the latest meeting, I think the best option is to include one some reference to DMM. So, the charter proposed by Behcet seems to cope with this. Best regards, Sérgio -- ---------------------------------------------- Sérgio Figueiredo ---------------------------------------------- Advanced Telecommunications and Networks Group IT-Aveiro ---------------------------------------------- On 04/24/2012 08:06 PM, Seil Jeon wrote: > Hi Stig, > See the comments in line. > Best Regards, > Seil > > 2012/4/24 Stig Venaas > > > On 4/24/2012 7:50 AM, Seil Jeon wrote: > > Hi Behcet, > My comment was not clear.. and yes it is possible for future > multimob item. > But I want that part should be revised as follows: > ----------- > Future work, subject to rechartering, may study use cases of > the base > solution in DMM, and evaluate performance impact. From that > point, it > may discuss MULTIMOB extensions to DMM protocol based on the > identified > problem(s). > > > I think we can skip the DMM part actually. Since it would be > subject to > rechartering, we would need to change the charter anyway. Even if > we say > "subject to rechartering" here, we may not be allowed to work on it. > Also, if we don't mention DMM here, we can still get it in a new > charter. > > Basically, I don't think a charter needs to talk about possibilities > for future charters. Whether we say it or not, it all depends on what > the group wants to work on, what the IESG thinks it makes sens for us > to work on, etc. > > Of course, a charter item will be determined by AD or IESG. > Regarding on putting DMM related proposal, I remember we got a > positive signal in Paris meeting. > So we'd better to keep recharter description written by Behcet for > now. As you said, this will be confirmed by IESG. > In this sense, I support revised charter. > > Stig > > ----------- > Regards, > Seil Jeon > 2012/4/24 Behcet Sarikaya > >> > > > Hi Seil, > > On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon > > >> wrote: > > Hi Behcet, > > > > Thanks to trigger new charter agenda. > > > > "Extension to DMM protocol ~" seems to be too much early. As we > told in > > Paris meeting, MULTIMOB needs to check the base solution in DMM. > > > > I think the text is clear, this item is possible future > charter item, > when the time comes we are going to discuss it and set the > milestones > accordingly. > > Regards, > > Behcet > > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > Future work, subject to rechartering, may study use cases of > the base > > solution in DMM, and evaluate performance impact. > > From that point, it may discuss MULTIMOB extensions to DMM > protocol based on > > the identified problem(s). > > . > > > > -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- > > > > Seil Jeon > > > > > > Instituto de Telecomunicações > > > > Campus Universitário de Santiago > > > > P-3810-193 Aveiro - Portugal > > > > > > > > Homepage: http://sites.google.com/site/seiljeon > > > > LinkedIn: > http://www.linkedin.com/profile/view?id=150370825&trk=tab_pro > > > > > > > > > > > 2012/4/23 Behcet Sarikaya > >> > > >> > >> Hi all, > >> > >> Based on possible future work discussions we had in IETF 83 in > Paris, > >> we have prepared a revised charter which is attached to > this mail. > >> > >> Basically a new charter item is proposed on IGMPv3/MLDv2 > extensions to > >> support better operation in mobile environments for which > there was > >> strong support > >> > >> and > >> > >> DMM multicast for which there was also strong support will be > taken up > >> subject to rechartering. > >> > >> Please post your comments/support on the list. > >> > >> Regards, > >> > >> Chairs > >> > >> _______________________________________________ > >> multimob mailing list > >> multimob@ietf.org > > > >> https://www.ietf.org/mailman/listinfo/multimob > > >> > > > > > > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob > > > > > _______________________________________________ > multimob mailing list > multimob@ietf.org > https://www.ietf.org/mailman/listinfo/multimob --------------090407000805030303040703 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Behcet, Stig, all,

I agree with Seil. Due to the strong interest shown in the latest meeting, I think the best option is to include one some reference to DMM.
So, the charter proposed by Behcet seems to cope with this.

Best regards,

Sérgio

-- 
----------------------------------------------
Sérgio Figueiredo
----------------------------------------------
Advanced Telecommunications and Networks Group
IT-Aveiro
----------------------------------------------


On 04/24/2012 08:06 PM, Seil Jeon wrote:
Hi Stig,
 
See the comments in line.
Best Regards,
 
Seil
 

 
2012/4/24 Stig Venaas <stig@venaas.com>
On 4/24/2012 7:50 AM, Seil Jeon wrote:
Hi Behcet,
My comment was not clear.. and yes it is possible for future multimob item.
But I want that part should be revised as follows:
-----------
Future work, subject to rechartering, may study use cases of the base
solution in DMM, and evaluate performance impact. From that point, it
may discuss MULTIMOB extensions to DMM protocol based on the identified
problem(s).

I think we can skip the DMM part actually. Since it would be subject to
rechartering, we would need to change the charter anyway. Even if we say
"subject to rechartering" here, we may not be allowed to work on it.
Also, if we don't mention DMM here, we can still get it in a new
charter.

Basically, I don't think a charter needs to talk about possibilities
for future charters. Whether we say it or not, it all depends on what
the group wants to work on, what the IESG thinks it makes sens for us
to work on, etc.
 
Of course, a charter item will be determined by AD or IESG.
Regarding on putting DMM related proposal, I remember we got a positive signal in Paris meeting.
So we'd better to keep recharter description written by Behcet for now. As you said, this will be confirmed by IESG.
 
In this sense, I support revised charter.
 
 
Stig

-----------
Regards,
Seil Jeon
2012/4/24 Behcet Sarikaya <sarikaya2012@gmail.com
<mailto:sarikaya2012@gmail.com>>


   Hi Seil,

   On Tue, Apr 24, 2012 at 6:03 AM, Seil Jeon <sijeon79@gmail.com
   <mailto:sijeon79@gmail.com>> wrote:
    > Hi Behcet,
    >
    > Thanks to trigger new charter agenda.
    >
    > "Extension to DMM protocol ~" seems to be too much early. As we
   told in
    > Paris meeting, MULTIMOB needs to check the base solution in DMM.
    >

   I think the text is clear, this item is possible future charter item,
   when the time comes we are going to discuss it and set the milestones
   accordingly.

   Regards,

   Behcet
    >
   --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    > Future work, subject to rechartering, may study use cases of the base
    > solution in DMM, and evaluate performance impact.
    > From that point, it may discuss MULTIMOB extensions to DMM
   protocol based on
    > the identified problem(s).
    > .
    >
   --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
    >
    > Seil Jeon
    >
    >
    > Instituto de Telecomunicações
    >
    > Campus Universitário de Santiago
    >
    > P-3810-193 Aveiro - Portugal
    >
    >
    >
    > Homepage: http://sites.google.com/site/seiljeon
    >
    > LinkedIn:
   http://www.linkedin.com/profile/view?id=150370825&trk=tab_pro
   <http://www.linkedin.com/profile/view?id=150370825&trk=tab_pro>
    >
    >
    >
    > 2012/4/23 Behcet Sarikaya <sarikaya2012@gmail.com
   <mailto:sarikaya2012@gmail.com>>

    >>
    >> Hi all,
    >>
    >> Based on possible future work discussions we had in IETF 83 in
   Paris,
    >> we have prepared a revised charter which is attached to this mail.
    >>
    >> Basically a new charter item is proposed on IGMPv3/MLDv2
   extensions to
    >> support better operation in mobile environments for which there was
    >> strong support
    >>
    >> and
    >>
    >> DMM multicast for which there was also strong support will be
   taken up
    >> subject to rechartering.
    >>
    >> Please post your comments/support on the list.
    >>
    >> Regards,
    >>
    >> Chairs
    >>
    >> _______________________________________________
    >> multimob mailing list
    >> multimob@ietf.org <mailto:multimob@ietf.org>
    >> https://www.ietf.org/mailman/listinfo/multimob

    >>
    >




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



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

--------------090407000805030303040703--