
From behcetsarikaya@yahoo.com  Mon Jan  3 11:35:44 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EDB503A6B25 for <multimob@core3.amsl.com>; Mon,  3 Jan 2011 11:35:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.002
X-Spam-Level: 
X-Spam-Status: No, score=-1.002 tagged_above=-999 required=5 tests=[AWL=-0.817, BAYES_40=-0.185]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qYU1QC+gM89R for <multimob@core3.amsl.com>; Mon,  3 Jan 2011 11:35:44 -0800 (PST)
Received: from nm4.bullet.mail.sp2.yahoo.com (nm4.bullet.mail.sp2.yahoo.com [98.139.91.74]) by core3.amsl.com (Postfix) with SMTP id 2847F3A6B24 for <multimob@ietf.org>; Mon,  3 Jan 2011 11:35:44 -0800 (PST)
Received: from [98.139.91.66] by nm4.bullet.mail.sp2.yahoo.com with NNFMP; 03 Jan 2011 19:37:49 -0000
Received: from [98.139.91.47] by tm6.bullet.mail.sp2.yahoo.com with NNFMP; 03 Jan 2011 19:37:48 -0000
Received: from [127.0.0.1] by omp1047.mail.sp2.yahoo.com with NNFMP; 03 Jan 2011 19:37:48 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 988738.36496.bm@omp1047.mail.sp2.yahoo.com
Received: (qmail 47861 invoked by uid 60001); 3 Jan 2011 19:37:48 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1294083468; bh=CXQWLvpE5W2Gy1v8juY1+q5IIBgjZ/sWA+4E5cR2eAM=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=PqoCWAZBeeN86CsfLExLKpx0CujfAvp5bBAoRpdmoGdzgVq8+MnVWNXADgY9Ok3Yuv7tgU9siRoSpy1Ac6aKJy/1YoIFhGS8zXw1TXbJQnSt2GsrTeB+WILVL6XRyrNnOQknkwSQyKgi7XunKMF5c05Qcd+qfQDn2l8Kn2B1PqM=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=cSWMSvZWoKNcR9dhkeizRk/iL365rn4rnn+2oBGV1xP5XsM9vEXHN4pBx7/hVAvn+R/9hPtL1gXiG7fUjxKaO8G5JgpoisrcK9/6Eggez9hxyph0eSDUsEmOJgdm9KxxNjj3IBOqwtYJPY3nQWZHvFpxNVR2O6Lt3wuxE/FCRvw=;
Message-ID: <504261.47588.qm@web111407.mail.gq1.yahoo.com>
X-YMail-OSG: .ENjrm4VM1k6rjkzHrGPtk_9qrA5gkWv3XHXZS1AtDmZo14 G7QPU5TQDv_ClOVgbOZIZcX6KHwmX7w364Pozek_U3tYR1VpqemndMl81DoB DKN.hhSvom5hxRBFkccnHtDgNH0hKJsvJrCtwhf1NSPpzPxgQZ4YPsChLGMd Be574FY9_K7kEYJVbscpTm6gM0UFIdBAAKDZtchd61h7JJsiqkS2FlC_hb.w RbvrQuoqS_suIvf4oo6BzHHKSEck765XWBdoOG9xfuvh7Av6hug3UQVldxoH B5cQ5v9QRv4MF_nUNFCYuNaNg.X6jxER7Kq7ZaVkVKaOlQAJpd6eq5ZUbC7T lo34WcOykAZPEWvtXjdtkkYr.aGS..CsOWWcnf2gM9KNPJ0XpIom8Z_e5Ob_ fbQJ6xsKovLLP
Received: from [206.16.17.212] by web111407.mail.gq1.yahoo.com via HTTP; Mon, 03 Jan 2011 11:37:48 PST
X-Mailer: YahooMailRC/553 YahooMailWebService/0.8.107.285259
Date: Mon, 3 Jan 2011 11:37:48 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [multimob] Tuning IGMPv3/MLDv2
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Jan 2011 19:35:45 -0000

Hello Folks,
  I wish everyone a Happy New Year.

Regarding our charter item:

Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for 
mobility

We need some discussion on this so that we can make progress, we are already 
behind.

I discussed with Stig. Here are our observations:

1. Behavior tuning  can be viewed as "behavior
change", it is considered a protocol change/ protocol extension hence not in the 
current 

charter,

2. Timer tuning is OK.  However, most of the timer tuning requires explicit 
tracking.
There are currently many implementations doing explicit
tracking today, and they do this without changing the MLD protocol.
We can say that implementations with the "explicit tracking" behavior can
allow for tuning timers in a specific way.

Defining the "explicit tracking" behavior for MLD/IGMP could also be undertaken 
and there are drafts to that effect.

Please post your comments on the list.

Regards,

Behcet


      

From asaeda@sfc.wide.ad.jp  Wed Jan  5 01:49:19 2011
Return-Path: <asaeda@sfc.wide.ad.jp>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F37703A6D17 for <multimob@core3.amsl.com>; Wed,  5 Jan 2011 01:49:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.096
X-Spam-Level: 
X-Spam-Status: No, score=-99.096 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, RELAY_IS_203=0.994, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lsJEDLlvCKpk for <multimob@core3.amsl.com>; Wed,  5 Jan 2011 01:49:17 -0800 (PST)
Received: from mail.sfc.wide.ad.jp (mail.sfc.wide.ad.jp [203.178.142.146]) by core3.amsl.com (Postfix) with ESMTP id EA34D3A6B72 for <multimob@ietf.org>; Wed,  5 Jan 2011 01:49:16 -0800 (PST)
Received: from localhost (unknown [58.98.33.222]) by mail.sfc.wide.ad.jp (Postfix) with ESMTPSA id BC537278075; Wed,  5 Jan 2011 18:51:19 +0900 (JST)
Date: Wed, 05 Jan 2011 18:51:19 +0900 (JST)
Message-Id: <20110105.185119.23261663.asaeda@sfc.wide.ad.jp>
To: sarikaya@ieee.org, behcetsarikaya@yahoo.com
From: Hitoshi Asaeda <asaeda@sfc.wide.ad.jp>
In-Reply-To: <504261.47588.qm@web111407.mail.gq1.yahoo.com>
References: <504261.47588.qm@web111407.mail.gq1.yahoo.com>
X-Mailer: Mew version 6.2.51 on Emacs 22.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: multimob@ietf.org
Subject: Re: [multimob] Tuning IGMPv3/MLDv2
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 Jan 2011 09:49:19 -0000

Hi Behcet,

I fully agree to the folliwing decision.

Regards,
--
Hitoshi Asaeda


From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
Subject: [multimob] Tuning IGMPv3/MLDv2
Date: Mon, 3 Jan 2011 11:37:48 -0800 (PST)

> Hello Folks,
>   I wish everyone a Happy New Year.
> 
> Regarding our charter item:
> 
> Nov 2010 - Initial version of a document on how to tune IGMPv3/MLDv2 for 
> mobility
> 
> We need some discussion on this so that we can make progress, we are already 
> behind.
> 
> I discussed with Stig. Here are our observations:
> 
> 1. Behavior tuning  can be viewed as "behavior
> change", it is considered a protocol change/ protocol extension hence not in the 
> current 
> 
> charter,
> 
> 2. Timer tuning is OK.  However, most of the timer tuning requires explicit 
> tracking.
> There are currently many implementations doing explicit
> tracking today, and they do this without changing the MLD protocol.
> We can say that implementations with the "explicit tracking" behavior can
> allow for tuning timers in a specific way.
> 
> Defining the "explicit tracking" behavior for MLD/IGMP could also be undertaken 
> and there are drafts to that effect.
> 
> Please post your comments on the list.
> 
> Regards,
> 
> Behcet
> 
> 
>       
> _______________________________________________
> multimob mailing list
> multimob@ietf.org
> https://www.ietf.org/mailman/listinfo/multimob

From behcetsarikaya@yahoo.com  Thu Jan  6 09:13:03 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1CAA33A6D14 for <multimob@core3.amsl.com>; Thu,  6 Jan 2011 09:13:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.175
X-Spam-Level: 
X-Spam-Status: No, score=-2.175 tagged_above=-999 required=5 tests=[AWL=0.424,  BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mqFx8NpwPd0s for <multimob@core3.amsl.com>; Thu,  6 Jan 2011 09:13:02 -0800 (PST)
Received: from nm13.bullet.mail.ne1.yahoo.com (nm13.bullet.mail.ne1.yahoo.com [98.138.90.76]) by core3.amsl.com (Postfix) with SMTP id F1CEF3A6C4F for <multimob@ietf.org>; Thu,  6 Jan 2011 09:13:01 -0800 (PST)
Received: from [98.138.90.48] by nm13.bullet.mail.ne1.yahoo.com with NNFMP; 06 Jan 2011 17:15:05 -0000
Received: from [98.138.89.193] by tm1.bullet.mail.ne1.yahoo.com with NNFMP; 06 Jan 2011 17:15:05 -0000
Received: from [127.0.0.1] by omp1051.mail.ne1.yahoo.com with NNFMP; 06 Jan 2011 17:15:05 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 926042.48809.bm@omp1051.mail.ne1.yahoo.com
Received: (qmail 18848 invoked by uid 60001); 6 Jan 2011 17:15:05 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1294334105; bh=oCQUonpcZYjKL6XgSzR4+7QOwygPqB6oE4AZze1OyVo=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=Il4ddpPxOeaKn5hvPcM21PiYmHoM7zg8sNP2+flct554wUrJyj12VIFi4VZm3zjm/sVB8VNS5yJxiC2LEs2jVdTTJORtjwuaOu6qLV5Z9CsfxxZvzvo8dk4CYWF2y6wP6M5XcIS0qKNOgjfCPCxTvYAfzKxqitle9CqyjWH/5RI=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=MO+PXs1tvKQq7wUqBTjavKn7mQk/C6yWGB1j7SFo0AHLk71Y/p1Nicteth//E32IDOfpPR81x+UXfsOjNEo8sbwgbrz2z5PzlFlkLTPipkagvFgaQBiz1mt/GUzX5Tk9ofUAyutL0DEBp7b0haHgfXYloZ/qN8vzxVNWo+UK46w=;
Message-ID: <243444.16543.qm@web111413.mail.gq1.yahoo.com>
X-YMail-OSG: 447qdfMVM1m4aQhZzM5l4twXUaK5ZdrNRq1bGBQakxaI6ru wk4MjTm4bRPmldERAZdCDxyHNoEbm7GVSjx_qh8allQqpV_d7Eb4KVeW16Nt SCa9ITNfYyJYnjVJM.9OrbZH3h5bmNUWTzWA6nxBKBmdI_veeogd2dvvMeC1 MO43akuyKSQqphjfyEqSSOkEh.Hn_UJrOugLFzPpv4UJZyOQY5TglvUvYZG2 mxupFB5n26qu5IQOVa5lXS8mximIm6RdP5khvbrt.5jONKvC.BX_NTeEzGj2 VtTcYaNGTtneYF_cNNCcAQ_RdMb1DK7qFfWpFdNIRhvEBPztSNEKYDrcaUBR _Al0qhWVLw2vuumZ430gCvKZ5e3Sutn5G9MQRpXqWHnfFBYa3JgsfiGGrYX2 KFOi2SmtYd4An
Received: from [206.16.17.212] by web111413.mail.gq1.yahoo.com via HTTP; Thu, 06 Jan 2011 09:15:04 PST
X-Mailer: YahooMailRC/553 YahooMailWebService/0.8.107.285259
Date: Thu, 6 Jan 2011 09:15:04 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [multimob] Fw: [MBONED] Next generation TV over the Internet: This revolution will be televised
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 06 Jan 2011 17:13:03 -0000

Please read Mboned co-chair Leonard Guiliano's Network World article.


I found pages 3 and 4 interesting and useful.

As for AMT, I think Mobile IPv6 bidirectional tunneling is essentially AMT for 
mobile.
Similarly PMIPv6 with draft-ietf-multimob-pmipv6-base-solution-07.

Regards,

Behcet




----- Forwarded Message ----
> From: Marshall Eubanks <tme@americafree.tv>
> To: MBONED WG <mboned@ietf.org>
> Sent: Wed, January 5, 2011 10:14:15 PM
> Subject: [MBONED] Next generation TV over the Internet: This revolution will be 
>televised
> 
> Thought people would want to see this by our co-chair. 
> 
> Marshall
> 
> http://www.networkworld.com/news/tech/2011/010511-tech-update-next-gen-tv.html
> 
> 
> _______________________________________________
> MBONED  mailing list
> MBONED@ietf.org
> https://www.ietf.org/mailman/listinfo/mboned
> 


      

From behcetsarikaya@yahoo.com  Wed Jan 19 13:36:13 2011
Return-Path: <behcetsarikaya@yahoo.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6DBFA28C107 for <multimob@core3.amsl.com>; Wed, 19 Jan 2011 13:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.51
X-Spam-Level: 
X-Spam-Status: No, score=-1.51 tagged_above=-999 required=5 tests=[AWL=-0.399,  BAYES_05=-1.11]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c55RHZIxl6xF for <multimob@core3.amsl.com>; Wed, 19 Jan 2011 13:36:12 -0800 (PST)
Received: from nm21.bullet.mail.ne1.yahoo.com (nm21.bullet.mail.ne1.yahoo.com [98.138.90.84]) by core3.amsl.com (Postfix) with SMTP id 6B0C228C112 for <multimob@ietf.org>; Wed, 19 Jan 2011 13:36:12 -0800 (PST)
Received: from [98.138.90.53] by nm21.bullet.mail.ne1.yahoo.com with NNFMP; 19 Jan 2011 21:38:50 -0000
Received: from [98.138.87.4] by tm6.bullet.mail.ne1.yahoo.com with NNFMP; 19 Jan 2011 21:38:50 -0000
Received: from [127.0.0.1] by omp1004.mail.ne1.yahoo.com with NNFMP; 19 Jan 2011 21:38:50 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 528994.87910.bm@omp1004.mail.ne1.yahoo.com
Received: (qmail 78623 invoked by uid 60001); 19 Jan 2011 21:38:49 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1295473129; bh=CMwNChzFtYW8+gAgzkSz/Hedk6vd4uYKqwZz8oWfi60=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=y56/ES5dWPD+Vpf/sw4rkrb0XpbNmlSzj3sCgEQnUcUVRIaMjDQ2Ee8k21zFROYOLZBVqjr2jRzlDKI99WR4LDlWSbW/0oEgav7qjUxmG6DfPAlmjrGnYZmz6V7y0Q1ew/9qzLPT/CcwTNvNYutxDsoX1jKcT69oSYh847eEitc=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Reply-To:Subject:To:MIME-Version:Content-Type; b=kiBh7NNQ435t2dEA+ZZ9QL0aYZPgRiNvJWMiTIMuu1T1UJDrjSHSfGSgzwxPVSpLXPdJlZZ8eo+ePVkgd4thBe/OoKG7IvFjeswUk0yBcpO1E6Pa/TDZZixvdAsDGjBZW42TRUYgxs80MgY8JONnZBcygnNkaNQW/KabLGeFTaM=;
Message-ID: <448903.78457.qm@web111416.mail.gq1.yahoo.com>
X-YMail-OSG: 63nNaxAVM1nr7lGI1eLc7Lcl7CFj0OUaoRMdnMSR_kogvNs VmXw9WkSy9o3E0AfzAMVPnJGtvZTSnSPsr33eC1NoyGvDqVL7QP2bogDsTEo c8hwuTiZsCq3sodvbhCoredRkgrY5sfAcrtIka4DzIWlvCAdmyaLASU0XQXY qQEhLJezNgNHZVGn3ILs7s01.J7wZv4zJDNqrq0E2oh2Wt9Czn5vUMmq7vLt UheiE.ezvquM.7uv4Jw1H9w7WtAVKzAIw8deuzMwlzYDwa5hSyMplTT5dPYr g8aejm843qcY0q4eLvufRjNISlGkcKFZaJX7JxpIUmEXk1GimDTWUV2t26fc Xta79xGRokhWEIsdSPbbNI.U65AxicAOlHgU07GoUOYe.xy6_LR7FhlY4e8I QtLPDPKp2eEDS
Received: from [206.16.17.212] by web111416.mail.gq1.yahoo.com via HTTP; Wed, 19 Jan 2011 13:38:49 PST
X-Mailer: YahooMailRC/555 YahooMailWebService/0.8.107.285259
Date: Wed, 19 Jan 2011 13:38:49 -0800 (PST)
From: Behcet Sarikaya <behcetsarikaya@yahoo.com>
To: multimob@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: [multimob] Session in IETF 80
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Behcet Sarikaya <sarikaya@ieee.org>
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 21:36:13 -0000

Hi all,
  We asked for a session in IETF 80.
Presentation requests are welcome. As usual send your requests to the chairs. 

The topics to be discussed include 

- IGMP/MLD Tuning,

- Tunnel convergence problem

and others per your requests.

Regards,

Behcet



      

From jari.arkko@piuha.net  Thu Jan 27 00:21:17 2011
Return-Path: <jari.arkko@piuha.net>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98D5D3A6942; Thu, 27 Jan 2011 00:21:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.53
X-Spam-Level: 
X-Spam-Status: No, score=-102.53 tagged_above=-999 required=5 tests=[AWL=0.069, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5ltr4LygDhBv; Thu, 27 Jan 2011 00:21:16 -0800 (PST)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id 883DD3A693A; Thu, 27 Jan 2011 00:21:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id 837602CC2F; Thu, 27 Jan 2011 10:24:18 +0200 (EET)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ioYeN6JfAH2I; Thu, 27 Jan 2011 10:24:18 +0200 (EET)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id 2E1472CC2D; Thu, 27 Jan 2011 10:24:16 +0200 (EET)
Message-ID: <4D412BAF.7060805@piuha.net>
Date: Thu, 27 Jan 2011 00:24:15 -0800
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20101027)
MIME-Version: 1.0
To: multimob@ietf.org
References: <20110117122132.19497.81881.idtracker@localhost>
In-Reply-To: <20110117122132.19497.81881.idtracker@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Cc: The IESG <iesg@ietf.org>, draft-ietf-multimob-pmipv6-base-solution@tools.ietf.org
Subject: [multimob] draft-ietf-multimob-pmipv6-base-solution in the IESG
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 08:21:17 -0000

This draft was discussed in the IESG meeting last week.

A couple of changes were brought up by a number of ADs:

1. BCP vs. Informational

The IETF BCP document class is reserved for a number of different 
purposes, including describing practices that are widely deployed and/or 
highly or urgently recommended. It was felt that given the deployment 
situation of multicast in PMIP networks that Informational would be a 
more suitable document class. Please remember that the IETF RFC 
boilerplate was recently changed. "Informational" RFC from the IETF is 
by no means an unimportant classification. Documents that have gone 
through the IETF Last Call will for instance, contain the following 
statement:

   It represents the consensus of the IETF community.  It has
   received public review and has been approved for publication by the
   Internet Engineering Steering Group (IESG).

2. RFC 2119 keywords

It was felt that as the document does not change the behaviour of 
existing specifications, just explain how to use them in a proper way, 
we should not use RFC 2119 keywords.

I have added RFC Editor notes and changed the datatracker document 
status field accordingly.

In addition, the following question from Ralph Droms should be answered:

> If I'm reading the document correctly, the LMAs arrange to receive
> multicast streams and forward the streams to the MAGs, which then
> forward the streams to subscribed MNs.
>
> In figure 1, suppose MN1, associated with LMA1, and MN2, associated
> with LMA2, are both associated with multicast stream MC.  Will MAG1
> receive copies of MC from both LMA1 and LMA2?
>
> Was a design considered in which the MAG arrange directly for the
> delivery of multicast streams as required by attached MNs?
>   

Jari


From schmidt@informatik.haw-hamburg.de  Thu Jan 27 01:28:18 2011
Return-Path: <schmidt@informatik.haw-hamburg.de>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1B94328C126; Thu, 27 Jan 2011 01:28:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.784
X-Spam-Level: 
X-Spam-Status: No, score=-101.784 tagged_above=-999 required=5 tests=[AWL=0.465, BAYES_00=-2.599, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qoalWfBwrQq0; Thu, 27 Jan 2011 01:28:16 -0800 (PST)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 5FBB728B23E; Thu, 27 Jan 2011 01:28:16 -0800 (PST)
Envelope-to: multimob@ietf.org, iesg@ietf.org
Received: from [141.22.26.184] by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72 (FreeBSD)) (envelope-from <schmidt@informatik.haw-hamburg.de>) id 1PiOCE-000OQx-C6; Thu, 27 Jan 2011 10:31:18 +0100
Message-ID: <4D413B68.6070303@informatik.haw-hamburg.de>
Date: Thu, 27 Jan 2011 10:31:20 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Jari Arkko <jari.arkko@piuha.net>
References: <20110117122132.19497.81881.idtracker@localhost> <4D412BAF.7060805@piuha.net>
In-Reply-To: <4D412BAF.7060805@piuha.net>
Content-Type: multipart/mixed; boundary="------------050501050600030304020808"
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: jari.arkko@ietf.org
Cc: Ralph Droms <rdroms.ietf@gmail.com>, multimob@ietf.org, The IESG <iesg@ietf.org>, draft-ietf-multimob-pmipv6-base-solution@tools.ietf.org
Subject: Re: [multimob] draft-ietf-multimob-pmipv6-base-solution in the IESG
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 09:28:18 -0000

This is a multi-part message in MIME format.
--------------050501050600030304020808
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

I answered the questions of Ralph on Jan. 19th (see attached).

If it felt that the answer is not satisfying / exhaustive, please let me 
know. I'll be happy to provide further input.

Thanks,

Thomas

On 27.01.2011 09:24, Jari Arkko wrote:
> This draft was discussed in the IESG meeting last week.
>
> A couple of changes were brought up by a number of ADs:
>
> 1. BCP vs. Informational
>
> The IETF BCP document class is reserved for a number of different
> purposes, including describing practices that are widely deployed and/or
> highly or urgently recommended. It was felt that given the deployment
> situation of multicast in PMIP networks that Informational would be a
> more suitable document class. Please remember that the IETF RFC
> boilerplate was recently changed. "Informational" RFC from the IETF is
> by no means an unimportant classification. Documents that have gone
> through the IETF Last Call will for instance, contain the following
> statement:
>
> It represents the consensus of the IETF community. It has
> received public review and has been approved for publication by the
> Internet Engineering Steering Group (IESG).
>
> 2. RFC 2119 keywords
>
> It was felt that as the document does not change the behaviour of
> existing specifications, just explain how to use them in a proper way,
> we should not use RFC 2119 keywords.
>
> I have added RFC Editor notes and changed the datatracker document
> status field accordingly.
>
> In addition, the following question from Ralph Droms should be answered:
>
>> If I'm reading the document correctly, the LMAs arrange to receive
>> multicast streams and forward the streams to the MAGs, which then
>> forward the streams to subscribed MNs.
>>
>> In figure 1, suppose MN1, associated with LMA1, and MN2, associated
>> with LMA2, are both associated with multicast stream MC. Will MAG1
>> receive copies of MC from both LMA1 and LMA2?
>>
>> Was a design considered in which the MAG arrange directly for the
>> delivery of multicast streams as required by attached MNs?
>
> Jari
>

-- 

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 °

--------------050501050600030304020808
Content-Type: message/rfc822;
 name="Re  Ralph Droms' Discuss on draft-ietf-multimob-pmipv6-base-solution-07  (with
 DISCUSS).eml"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment;
 filename*0="Re  Ralph Droms' Discuss on draft-ietf-multimob-pmipv6-base-";
 filename*1="solution-07  (with DISCUSS).eml"

Return-path: <prvs=99337e6e3=schmidt@informatik.haw-hamburg.de>
Envelope-to: schmidt@fhtw-berlin.de
Delivery-date: Wed, 19 Jan 2011 18:32:41 +0100
Received: from mx3.haw-public.haw-hamburg.de ([141.22.6.2])
	by mail2.rz.htw-berlin.de with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.72 (FreeBSD))
	(envelope-from <prvs=99337e6e3=schmidt@informatik.haw-hamburg.de>)
	id 1Pfbth-000OHq-3H
	for schmidt@fhtw-berlin.de; Wed, 19 Jan 2011 18:32:41 +0100
Received: from mailgate.informatik.haw-hamburg.de ([141.22.30.74])
  by mail3.is.haw-hamburg.de with ESMTP/TLS/ADH-AES256-SHA; 19 Jan 2011 18:32:31 +0100
Received: by mailgate.informatik.haw-hamburg.de (Postfix)
	id 9C7DC106D00F; Wed, 19 Jan 2011 18:32:31 +0100 (CET)
Delivered-To: schmidt@informatik.haw-hamburg.de
Received: from localhost (localhost [127.0.0.1])
	by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTP id 6843B10ACB15
	for <schmidt@informatik.haw-hamburg.de>; Wed, 19 Jan 2011 18:32:31 +0100 (CET)
Received: from mailgate.informatik.haw-hamburg.de ([127.0.0.1])
 by localhost (mailgate.informatik.haw-hamburg.de [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id 08520-07 for <schmidt@informatik.haw-hamburg.de>;
 Wed, 19 Jan 2011 18:32:31 +0100 (CET)
Received: from mx6.haw-public.haw-hamburg.de (mx6.haw-public.haw-hamburg.de [141.22.6.3])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by mailgate.informatik.haw-hamburg.de (Postfix) with ESMTPS id 02139106D00F
	for <schmidt@informatik.haw-hamburg.de>; Wed, 19 Jan 2011 18:32:30 +0100 (CET)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: At4AABuvNk1AqmIql2dsb2JhbACEEaA2FQEBAQEBCBUHNa9IjzuBJIM4dASOQg
Received: from zinfandel.tools.ietf.org ([64.170.98.42])
  by mx6.haw-public.haw-hamburg.de with ESMTP; 19 Jan 2011 18:32:29 +0100
Received: from mail2.rz.htw-berlin.de ([141.45.10.102])
	by zinfandel.tools.ietf.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.72)
	(envelope-from <schmidt@informatik.haw-hamburg.de>)
	id 1PfbtM-0006Ix-VD; Wed, 19 Jan 2011 09:32:22 -0800
Received: from [141.22.26.184]
	by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:AES256-SHA:256)
	(Exim 4.72 (FreeBSD))
	(envelope-from <schmidt@informatik.haw-hamburg.de>)
	id 1Pfbsj-000O3C-Az; Wed, 19 Jan 2011 18:31:41 +0100
Message-ID: <4D371FFB.2090501@informatik.haw-hamburg.de>
Date: Wed, 19 Jan 2011 18:31:39 +0100
From: "Thomas C. Schmidt" <schmidt@informatik.haw-hamburg.de>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
To: Ralph Droms <rdroms.ietf@gmail.com>
CC: The IESG <iesg@ietf.org>, multimob-chairs@tools.ietf.org, 
 draft-ietf-multimob-pmipv6-base-solution@tools.ietf.org
References: <20110118203439.18460.22887.idtracker@localhost>
In-Reply-To: <20110118203439.18460.22887.idtracker@localhost>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-DELIVERED-TO: iesg@tools.ietf.org
X-Sender-Verification-Failed: Verification failed for sender schmidt@informatik.haw-hamburg.de
X-SA-Exim-Connect-IP: 141.45.10.102
X-SA-Exim-Rcpt-To: multimob-chairs@tools.ietf.org, draft-ietf-multimob-pmipv6-base-solution@tools.ietf.org
X-SA-Exim-Mail-From: schmidt@informatik.haw-hamburg.de
Subject: Re: Ralph Droms' Discuss on draft-ietf-multimob-pmipv6-base-solution-07:
 (with DISCUSS)
X-SA-Exim-Version: 4.2.1 (built Mon, 22 Mar 2010 06:51:10 +0000)
X-SA-Exim-Scanned: Yes (on zinfandel.tools.ietf.org)
X-Virus-Scanned: by amavisd-new at informatik.haw-hamburg.de
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
X-HTW-MAINCATEGORY: clean
X-HTW-RECIPIENT-EXPANDED-FROM: schmidt@fhtw-berlin.de
X-HTW-DELIVERED-TO: tschmidt@htw-berlin.de

Dear Ralph,

thanks for overlooking the document. Please see answers inline.
>
> ----------------------------------------------------------------------
> DISCUSS:
> ----------------------------------------------------------------------
>
> If I'm reading the document correctly, the LMAs arrange to receive
> multicast streams and forward the streams to the MAGs, which then
> forward the streams to subscribed MNs.
>

Yes, that's correct.

> In figure 1, suppose MN1, associated with LMA1, and MN2, associated
> with LMA2, are both associated with multicast stream MC.  Will MAG1
> receive copies of MC from both LMA1 and LMA2?
>

Yes, it will. This is the result of "limited" PMIP awareness of 
multicast management at the MAG - it acts just as a standard MLD proxy.

> Was a design considered in which the MAG arrange directly for the
> delivery of multicast streams as required by attached MNs?
>

An explicit coordination of multicast management at MAGs with respect to 
different MN <-> LMAs bindings was out of scope for this document, as 
this would require new protocol operations. The charter only permitted 
the re-use of existing protocols.

The alternative approach,  to limit the deployment of multicast-enabled 
LMAs in PMIP to one single entity (that requires no coordination), is 
discussed/compared in Appendix C.

A further direction to avoid duplicate packet delivery at MAGs is 
discuseed in Section 4.6. "Multicast Availability throughout the Access 
Network". This option requires multicast to arrive at the MAGs natively 
by other means, e.g., all MAGs have a common access to *one* multicast 
delivery network.


To my understanding, these directions explore the solution space for 
protocol re-uses.

Solutions that optimize multicast streams jointly with handover 
performance (context transfer) are future work in Multimob.

Thanks,

Thomas


-- 

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 °

--------------050501050600030304020808--

From iesg-secretary@ietf.org  Thu Jan 27 09:43:42 2011
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 834263A69A1; Thu, 27 Jan 2011 09:43:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.474
X-Spam-Level: 
X-Spam-Status: No, score=-102.474 tagged_above=-999 required=5 tests=[AWL=0.125, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FwMMEHj8MRfH; Thu, 27 Jan 2011 09:43:41 -0800 (PST)
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 603BF3A69B7; Thu, 27 Jan 2011 09:43:41 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 3.10
Message-ID: <20110127174341.4101.43398.idtracker@localhost>
Date: Thu, 27 Jan 2011 09:43:41 -0800
Cc: Internet Architecture Board <iab@iab.org>, multimob mailing list <multimob@ietf.org>, multimob chair <multimob-chairs@tools.ietf.org>, RFC Editor <rfc-editor@rfc-editor.org>
Subject: [multimob] Document Action: 'Base Deployment for Multicast Listener Support in	PMIPv6 Domains' to Informational RFC	(draft-ietf-multimob-pmipv6-base-solution-07.txt)
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 17:43:42 -0000

The IESG has approved the following document:
- 'Base Deployment for Multicast Listener Support in PMIPv6 Domains'
  (draft-ietf-multimob-pmipv6-base-solution-07.txt) as an Informational
RFC

This document is the product of the Multicast Mobility Working Group.

The IESG contact persons are Jari Arkko and Ralph Droms.

A URL of this Internet Draft is:
http://datatracker.ietf.org/doc/draft-ietf-multimob-pmipv6-base-solution/




Technical Summary

   This document describes deployment options for activating multicast
   listener functions in Proxy Mobile IPv6 domains without modifying
   mobility and multicast protocol standards. 

Working Group Summary

   This is a product of the MULTIMOB working group.

Document Quality

   The document has been reviewed by the working group and
   proxy MIP experts.

Personnel

   The document shepherd is Bechet Sarikaya. The responsible Area
   Director is Jari Arkko.

RFC Editor Note

  Please remove the RFC 2119 boilerplate text and change all MUST/SHOULD/MAY keywords
  to lower case.

From stig@venaas.com  Thu Jan 27 09:52:12 2011
Return-Path: <stig@venaas.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6887F3A69C0 for <multimob@core3.amsl.com>; Thu, 27 Jan 2011 09:52:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.354
X-Spam-Level: 
X-Spam-Status: No, score=-102.354 tagged_above=-999 required=5 tests=[AWL=0.246, BAYES_00=-2.599, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3eEgjphoEKO5 for <multimob@core3.amsl.com>; Thu, 27 Jan 2011 09:52:10 -0800 (PST)
Received: from ufisa.uninett.no (ufisa.uninett.no [IPv6:2001:700:1:2:158:38:152:126]) by core3.amsl.com (Postfix) with ESMTP id 1EE4B3A69C1 for <multimob@ietf.org>; Thu, 27 Jan 2011 09:52:10 -0800 (PST)
Received: from [IPv6:2001:420:4:ea0c:119a:6650:e1b1:e5a9] (unknown [IPv6:2001:420:4:ea0c:119a:6650:e1b1:e5a9]) by ufisa.uninett.no (Postfix) with ESMTPSA id E0B477FDF for <multimob@ietf.org>; Thu, 27 Jan 2011 18:55:12 +0100 (CET)
Message-ID: <4D41B17A.8000800@venaas.com>
Date: Thu, 27 Jan 2011 09:55:06 -0800
From: Stig Venaas <stig@venaas.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: multimob mailing list <multimob@ietf.org>
References: <20110127174341.4101.43398.idtracker@localhost>
In-Reply-To: <20110127174341.4101.43398.idtracker@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [multimob] Document Action: 'Base Deployment for Multicast Listener Support in	PMIPv6 Domains' to Informational	RFC	(draft-ietf-multimob-pmipv6-base-solution-07.txt)
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 17:52:12 -0000

With this we (multimob) have completed our first charter item!
Thanks to the authors and everyone else involved for all the hard work.

Stig

From shares@huawei.com  Thu Jan 27 14:53:05 2011
Return-Path: <shares@huawei.com>
X-Original-To: multimob@core3.amsl.com
Delivered-To: multimob@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4E7F93A69DB for <multimob@core3.amsl.com>; Thu, 27 Jan 2011 14:53:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level: 
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sq0eoYOtssxx for <multimob@core3.amsl.com>; Thu, 27 Jan 2011 14:53:04 -0800 (PST)
Received: from usaga01-in.huawei.com (usaga01-in.huawei.com [206.16.17.211]) by core3.amsl.com (Postfix) with ESMTP id 3241C3A69AE for <multimob@ietf.org>; Thu, 27 Jan 2011 14:53:04 -0800 (PST)
Received: from huawei.com (usaga01-in [172.18.4.6]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0LFP000Q1EDKMP@usaga01-in.huawei.com> for multimob@ietf.org; Thu, 27 Jan 2011 14:56:08 -0800 (PST)
Received: from H00901778 (99.sub-75-199-144.myvzw.com [75.199.144.99]) by usaga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug  8 2006)) with ESMTPA id <0LFP008DOEDFGO@usaga01-in.huawei.com> for multimob@ietf.org; Thu, 27 Jan 2011 14:56:08 -0800 (PST)
Date: Thu, 27 Jan 2011 17:56:06 -0500
From: Hares Susan <shares@huawei.com>
In-reply-to: <4D41B17A.8000800@venaas.com>
To: 'Stig Venaas' <stig@venaas.com>, 'multimob mailing list' <multimob@ietf.org>
Message-id: <06E8CDE069C24416A2E5AAD4060D4BD0@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.5931
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7BIT
Thread-index: Acu+S2eXcQhbQx8wQ8KZSmyQJaYsWQAKfKww
References: <20110127174341.4101.43398.idtracker@localhost> <4D41B17A.8000800@venaas.com>
Subject: Re: [multimob] Document Action: 'Base Deployment for Multicast Listener Support in	PMIPv6 Domains' to Informational	RFC(draft-ietf-multimob-pmipv6-base-solution-07.txt)
X-BeenThere: multimob@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multicast Mobility <multimob.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/multimob>
List-Post: <mailto:multimob@ietf.org>
List-Help: <mailto:multimob-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/multimob>, <mailto:multimob-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 22:53:05 -0000

 Congratulations Stig and Behcet! 

Sue 

-----Original Message-----
From: multimob-bounces@ietf.org [mailto:multimob-bounces@ietf.org] On Behalf
Of Stig Venaas
Sent: Thursday, January 27, 2011 12:55 PM
To: multimob mailing list
Subject: Re: [multimob] Document Action: 'Base Deployment for Multicast
Listener Support in PMIPv6 Domains' to Informational
RFC(draft-ietf-multimob-pmipv6-base-solution-07.txt)

With this we (multimob) have completed our first charter item!
Thanks to the authors and everyone else involved for all the hard work.

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


