From sam-bounces@irtf.org Thu Jan 04 12:22:30 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2WIG-00083F-7g; Thu, 04 Jan 2007 12:22:20 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2WIE-000811-4j
	for sam@irtf.org; Thu, 04 Jan 2007 12:22:18 -0500
Received: from wx-out-0506.google.com ([66.249.82.232])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2WIC-0004cm-Uy
	for sam@irtf.org; Thu, 04 Jan 2007 12:22:18 -0500
Received: by wx-out-0506.google.com with SMTP id i28so6631490wxd
	for <sam@irtf.org>; Thu, 04 Jan 2007 09:22:16 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
	h=received:message-id:date:from:sender:to:subject:cc:mime-version:content-type:content-transfer-encoding:content-disposition:x-google-sender-auth;
	b=YTLOpl4U3v0LOJ55E8I7ax+k/e4Qht7vj5Ff+LbKhMu/mhgnS8BcM3RU9jJ3g6QzCB+FjUmj8kM+dfdHZJzpRlt4O3cOC1TYStrSXJkjx7Idol/dyKlw7XVs3WHKk0THjKRsp9jo7CbgzAfNXf8AEYWMG6C1Lb0V92vwkgS44a8=
Received: by 10.70.44.4 with SMTP id r4mr41479552wxr.1167931336746;
	Thu, 04 Jan 2007 09:22:16 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Thu, 4 Jan 2007 09:22:16 -0800 (PST)
Message-ID: <4ce32a820701040922s47dbd335n844c4edd2060d014@mail.gmail.com>
Date: Thu, 4 Jan 2007 12:22:16 -0500
From: "John Buford" <buford@samrg.org>
To: sam@irtf.org
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Google-Sender-Auth: e78f3b5af93efd43
X-Spam-Score: 0.0 (/)
X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89
Cc: 
Subject: [SAM] draft-irtf-sam-problem-statement-01.txt
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Errors-To: sam-bounces@irtf.org

The SAM Problem Statement has been updated
based on comments received on the mobility
section.

The new version is:
draft-irtf-sam-problem-statement-01.txt

Follow the ID link on www.samrg.org
to obtain the draft.

John

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam



From sam-bounces@irtf.org Thu Jan 04 12:45:29 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H2Wed-0007cS-AD; Thu, 04 Jan 2007 12:45:27 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H2Wec-0007a8-E6
	for sam@irtf.org; Thu, 04 Jan 2007 12:45:26 -0500
Received: from tmailer.gwdg.de ([134.76.10.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H2Wea-0001qt-2l
	for sam@irtf.org; Thu, 04 Jan 2007 12:45:26 -0500
Received: from agbruss5.hyghum-virol.med.uni-goettingen.de ([134.76.117.118]
	helo=IFITMG) by mailer.gwdg.de with smtp (Exim 4.63)
	(envelope-from <lei@informatik.uni-goettingen.de>)
	id 1H2WeT-0001uQ-0z; Thu, 04 Jan 2007 18:45:17 +0100
Message-ID: <000c01c73028$17e0c4e0$76754c86@IFITMG>
From: "Jun Lei" <lei@informatik.uni-goettingen.de>
To: "John Buford" <buford@samrg.org>
References: <4ce32a820701040922s47dbd335n844c4edd2060d014@mail.gmail.com>
Subject: Re: [SAM] draft-irtf-sam-problem-statement-01.txt
Date: Thu, 4 Jan 2007 18:45:16 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3028
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028
X-Spam-Level: /
X-Spam-Report: Content analysis: 0.0 points, 6.0 required
	_SUMMARY_
X-Virus-Scanned: (clean) by exiscan+sophie
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: sam@irtf.org
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Errors-To: sam-bounces@irtf.org

Dear John and all SAM partners,

        Happy new year and I wish all of you have a peaceful, happy and 
successful 2007.

        I am looking forward to seeing u in Las Vegas.

Cheers

Jun

----- Original Message ----- 
From: "John Buford" <buford@samrg.org>
To: <sam@irtf.org>
Sent: Thursday, January 04, 2007 6:22 PM
Subject: [SAM] draft-irtf-sam-problem-statement-01.txt


> The SAM Problem Statement has been updated
> based on comments received on the mobility
> section.
>
> The new version is:
> draft-irtf-sam-problem-statement-01.txt
>
> Follow the ID link on www.samrg.org
> to obtain the draft.
>
> John
>
> _______________________________________________
> SAM mailing list
> SAM@irtf.org
> https://www1.ietf.org/mailman/listinfo/sam
> 



_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam



From sam-bounces@irtf.org Tue Jan 09 10:30:52 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H4Iw0-0004MR-76; Tue, 09 Jan 2007 10:30:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H4Ivy-0004Lf-Py
	for sam@irtf.org; Tue, 09 Jan 2007 10:30:42 -0500
Received: from oak.research.panasonic.com ([150.169.1.4])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H4Ivw-0006k7-HS
	for sam@irtf.org; Tue, 09 Jan 2007 10:30:42 -0500
Received: from redwood.research.panasonic.com (redwood.research.panasonic.com
	[150.169.3.3])
	by oak.research.panasonic.com (1.1.1/1.1.1) with ESMTP id
	l09FUed7007219; Tue, 9 Jan 2007 10:30:40 -0500
Received: from bufordw2 ([150.169.17.3])
	by redwood.research.panasonic.com (MOS 3.7.4b-GA)
	with SMTP id APO12081; Tue, 9 Jan 2007 10:28:26 -0500 (EST)
From: "John Buford" <buford@research.panasonic.com>
To: <sam@irtf.org>
Date: Tue, 9 Jan 2007 10:30:36 -0500
Message-ID: <MBEDJFICFCDPPFADFCIHMEGCDDAA.buford@research.panasonic.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Importance: Normal
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed
Cc: 
Subject: [SAM] Final Schedule for Workshop on P2P Multicasting 07
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: buford@samrg.org
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Errors-To: sam-bounces@irtf.org


The final schedule for P2PM 07 which will be held
Thursday January 11 is available at
http://samrg.org/p2pm07/program.html

Please note the revised starting time of 8:10am
for the Keynote address by Prof. Kevin Almeroth.

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam



From sam-bounces@irtf.org Thu Jan 11 18:10:55 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H594I-0002wx-V5; Thu, 11 Jan 2007 18:10:46 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H594H-0002ws-Uf
	for sam@irtf.org; Thu, 11 Jan 2007 18:10:45 -0500
Received: from wx-out-0506.google.com ([66.249.82.238])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H594G-0008OX-Ek
	for sam@irtf.org; Thu, 11 Jan 2007 18:10:45 -0500
Received: by wx-out-0506.google.com with SMTP id i28so670048wxd
	for <sam@irtf.org>; Thu, 11 Jan 2007 15:10:44 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	b=d83CyzCd2wPGnnVJ3tq4P7eYCEtvHDMjZH5lxIanBcF9yldykz+1HuksdKsH/QSCC7WIXIp3VofjroRnohfSmHVpjgK4LboI7obq48UA1VHSPamvcuU7F4yH80Vrat68XPaZWjd8DKgO+bN5pzuh8t3r5nDGvJpEgErF8xMGldk=
Received: by 10.70.11.1 with SMTP id 1mr3842874wxk.1168557044250;
	Thu, 11 Jan 2007 15:10:44 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Thu, 11 Jan 2007 15:10:44 -0800 (PST)
Message-ID: <4ce32a820701111510o71b260ex426a253a1ea6c4ff@mail.gmail.com>
Date: Thu, 11 Jan 2007 18:10:44 -0500
From: "John Buford" <buford@samrg.org>
To: sam@irtf.org
MIME-Version: 1.0
X-Google-Sender-Auth: f8c271a8f43d77eb
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
Subject: [SAM] Slides for keynote presentation at P2PM07 available
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1745670898=="
Errors-To: sam-bounces@irtf.org

--===============1745670898==
Content-Type: multipart/alternative; 
	boundary="----=_Part_30843_26421303.1168557044177"

------=_Part_30843_26421303.1168557044177
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Presentation slides on Prof. Kevin Almeroth's keynote at P2P Multicasting 07
on "Multicast Help Wanted: From Where and How Much?"
are available at

http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt

------=_Part_30843_26421303.1168557044177
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Presentation slides on Prof. Kevin Almeroth&#39;s keynote at P2P Multicasting 07</div>
<div>on &quot;Multicast Help Wanted: From Where and How Much?&quot;</div>
<div>are available at</div>
<div>&nbsp;</div>
<div><a href="http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt">http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt</a><br clear="all"></div>

------=_Part_30843_26421303.1168557044177--


--===============1745670898==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============1745670898==--




From sam-bounces@irtf.org Thu Jan 11 20:42:17 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5BQm-0005V0-QK; Thu, 11 Jan 2007 20:42:08 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5BQl-0005Uu-CO
	for sam@irtf.org; Thu, 11 Jan 2007 20:42:07 -0500
Received: from wx-out-0506.google.com ([66.249.82.239])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5BQk-00020V-38
	for sam@irtf.org; Thu, 11 Jan 2007 20:42:07 -0500
Received: by wx-out-0506.google.com with SMTP id i28so703109wxd
	for <sam@irtf.org>; Thu, 11 Jan 2007 17:42:05 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=cr/AGEG/naHRnwNe/gYbMCBmanG1H4e3BhZ5fuBMSQAlTvTdp+9ub3xcR6sou/S0jwzhMAE8bUQ//RYGg9sqknw0J8s6QIvIgKh3sGhaJW4EKgCDcOx7HAfOCqwwjd2oVX4+ua21H8hrGc55E06+5UVZ6IXex0lElaJApkLXswE=
Received: by 10.70.42.20 with SMTP id p20mr215969wxp.1168566125437;
	Thu, 11 Jan 2007 17:42:05 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Thu, 11 Jan 2007 17:42:05 -0800 (PST)
Message-ID: <4ce32a820701111742nb62a37cy3e587d319d4d1b28@mail.gmail.com>
Date: Thu, 11 Jan 2007 20:42:05 -0500
From: "John Buford" <buford@samrg.org>
To: "Yangwoo Ko" <newcat@icu.ac.kr>, sam@irtf.org
Subject: Re: [SAM] Slides for keynote presentation at P2PM07 available
In-Reply-To: <45A6D0AB.3020408@icu.ac.kr>
MIME-Version: 1.0
References: <4ce32a820701111510o71b260ex426a253a1ea6c4ff@mail.gmail.com>
	<45A6D0AB.3020408@icu.ac.kr>
X-Google-Sender-Auth: 6a3c3f2784789b86
X-Spam-Score: 0.1 (/)
X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4
Cc: 
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1580697510=="
Errors-To: sam-bounces@irtf.org

--===============1580697510==
Content-Type: multipart/alternative; 
	boundary="----=_Part_32176_20501628.1168566125394"

------=_Part_32176_20501628.1168566125394
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

sorry, it is fixed now.

On 1/11/07, Yangwoo Ko <newcat@icu.ac.kr> wrote:
>
>
> I cannot access it. Would you check the URL again?
>
> John Buford wrote:
> > Presentation slides on Prof. Kevin Almeroth's keynote at P2P
> > Multicasting 07
> > on "Multicast Help Wanted: From Where and How Much?"
> > are available at
> >
> > http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt
> > ------------------------------------------------------------------------
> >
> > _______________________________________________
> > SAM mailing list
> > SAM@irtf.org
> > https://www1.ietf.org/mailman/listinfo/sam
> >
>
>

------=_Part_32176_20501628.1168566125394
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

sorry, it is fixed now.<br><br>
<div><span class="gmail_quote">On 1/11/07, <b class="gmail_sendername">Yangwoo Ko</b> &lt;<a href="mailto:newcat@icu.ac.kr">newcat@icu.ac.kr</a>&gt; wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid"><br>I cannot access it. Would you check the URL again?<br><br>John Buford wrote:<br>&gt; Presentation slides on Prof. Kevin Almeroth&#39;s keynote at P2P
<br>&gt; Multicasting 07<br>&gt; on &quot;Multicast Help Wanted: From Where and How Much?&quot;<br>&gt; are available at<br>&gt;<br>&gt; <a href="http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt">http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt
</a><br>&gt; ------------------------------------------------------------------------<br>&gt;<br>&gt; _______________________________________________<br>&gt; SAM mailing list<br>&gt; <a href="mailto:SAM@irtf.org">SAM@irtf.org
</a><br>&gt; <a href="https://www1.ietf.org/mailman/listinfo/sam">https://www1.ietf.org/mailman/listinfo/sam</a><br>&gt;<br><br></blockquote></div><br><br clear="all">

------=_Part_32176_20501628.1168566125394--


--===============1580697510==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============1580697510==--




From sam-bounces@irtf.org Fri Jan 12 04:07:53 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H5IO0-0001hv-Qs; Fri, 12 Jan 2007 04:07:44 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H5INy-0001hd-8x
	for sam@irtf.org; Fri, 12 Jan 2007 04:07:42 -0500
Received: from cluster-b.mailcontrol.com ([217.68.146.190])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H5INw-0006zm-Ld
	for sam@irtf.org; Fri, 12 Jan 2007 04:07:42 -0500
Received: from rly37b.srv.mailcontrol.com (localhost.localdomain [127.0.0.1])
	by rly37b.srv.mailcontrol.com (MailControl) with ESMTP id
	l0C97Q9q015140
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
	for <sam@irtf.org>; Fri, 12 Jan 2007 09:07:30 GMT
Received: from submission.mailcontrol.com (submission.mailcontrol.com
	[86.111.216.190])
	by rly37b.srv.mailcontrol.com (MailControl) id l0C97KOF014723
	for sam@irtf.org; Fri, 12 Jan 2007 09:07:20 GMT
Received: from hhe500-02.hbg.de.pan.eu (gate.eu.panasonic.com [194.173.20.12])
	by rly37b-eth0.srv.mailcontrol.com (envelope-sender
	Osvaldo.Gonsa@eu.panasonic.com) (MIMEDefang) with ESMTP id
	l0C97HMU014398; Fri, 12 Jan 2007 09:07:20 +0000 (GMT)
Received: from eundadmi01.pan.eu(10.100.96.64) by hhe500-02.hbg.de.pan.eu via
	smtp id 78e4_e162ef7a_a218_11db_87ef_0030482aac25;
	Fri, 12 Jan 2007 09:42:47 +0100
Received: from VPN-MRelay-01.PRDCG.Panasonic.de ([10.100.176.55])
	by eundadmi01.pan.eu (Lotus Domino Release 6.5.4FP3)
	with ESMTP id 2007011210070836-187811 ;
	Fri, 12 Jan 2007 10:07:08 +0100 
X-Spam-Status: No, hits=0.0 required=4.5
	tests=AWL: -0.342,BAYES_00: -1.665,HTML_MESSAGE: 0.001,
	TOTAL_SCORE: -2.006
X-Spam-Level: 
Received: from localhost ([127.0.0.1]) by VPN-MRelay-01.PRDCG.Panasonic.de;
	Fri, 12 Jan 2007 10:11:46 +0100
MIME-Version: 1.0
X-MimeOLE: Produced By Microsoft Exchange V6.5
Subject: RE: [SAM] Slides for keynote presentation at P2PM07 available
In-reply-to: <4ce32a820701111742nb62a37cy3e587d319d4d1b28@mail.gmail.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [SAM] Slides for keynote presentation at P2PM07 available
thread-index: Acc16sID0VqWHiAoRZCZWGI5/lQo/AAPdUEg
References: <4ce32a820701111510o71b260ex426a253a1ea6c4ff@mail.gmail.com><45A6D0AB.3020408@icu.ac.kr>
	<4ce32a820701111742nb62a37cy3e587d319d4d1b28@mail.gmail.com>
To: "John Buford" <buford@samrg.org>, <sam@irtf.org>
Message-ID: <4D2F935F08D41A4C8866693F4F0D7C4F0111B2C9@lan-ex-01.panasonic.de>
Date: Fri, 12 Jan 2007 10:05:12 +0100
From: "Osvaldo Gonsa" <Osvaldo.Gonsa@eu.panasonic.com>
Content-class: urn:content-classes:message
X-Scanned-By: MailControl A-06-00-00 (www.mailcontrol.com) on 10.66.1.147
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 36b1f8810cb91289d885dc8ab4fc8172
Cc: 
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0456695494=="
Errors-To: sam-bounces@irtf.org

This is a multi-part message in MIME format.

--===============0456695494==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C73628.C540D7D4"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C73628.C540D7D4
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

John,
=20
no, it's not fixed yet :(=20
I still can't access it, the server gives me a 404 not found message.
=20
regards
=20
Osvaldo


________________________________

	From: John Buford [mailto:buford@samrg.org]=20
	Sent: Freitag, 12. Januar 2007 02:42
	To: Yangwoo Ko; sam@irtf.org
	Subject: Re: [SAM] Slides for keynote presentation at P2PM07
available
=09
=09
	sorry, it is fixed now.
=09
=09
	On 1/11/07, Yangwoo Ko <newcat@icu.ac.kr> wrote:=20


		I cannot access it. Would you check the URL again?
	=09
		John Buford wrote:
		> Presentation slides on Prof. Kevin Almeroth's keynote
at P2P=20
		> Multicasting 07
		> on "Multicast Help Wanted: From Where and How Much?"
		> are available at
		>
		>
http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt=20
		>
------------------------------------------------------------------------
		>
		> _______________________________________________
		> SAM mailing list
		> SAM@irtf.org=20
		> https://www1.ietf.org/mailman/listinfo/sam
		>
	=09
	=09




------_=_NextPart_001_01C73628.C540D7D4
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.5700.6" name=3DGENERATOR></HEAD>
<BODY>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007>John,</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007>no, it's not fixed yet :( =
</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007>I still can't access it, the server gives me =
a 404 not=20
found message.</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007>regards</SPAN></FONT></DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007></SPAN></FONT>&nbsp;</DIV>
<DIV dir=3Dltr align=3Dleft><FONT face=3DArial color=3D#0000ff =
size=3D2><SPAN=20
class=3D487560309-12012007>Osvaldo</SPAN></FONT></DIV><BR>
<BLOCKQUOTE=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
  <HR tabIndex=3D-1>
  <FONT face=3DTahoma size=3D2><B>From:</B> John Buford =
[mailto:buford@samrg.org]=20
  <BR><B>Sent:</B> Freitag, 12. Januar 2007 02:42<BR><B>To:</B> Yangwoo =
Ko;=20
  sam@irtf.org<BR><B>Subject:</B> Re: [SAM] Slides for keynote =
presentation at=20
  P2PM07 available<BR></FONT><BR></DIV>
  <DIV></DIV>sorry, it is fixed now.<BR><BR>
  <DIV><SPAN class=3Dgmail_quote>On 1/11/07, <B =
class=3Dgmail_sendername>Yangwoo=20
  Ko</B> &lt;<A =
href=3D"mailto:newcat@icu.ac.kr">newcat@icu.ac.kr</A>&gt;=20
  wrote:</SPAN>=20
  <BLOCKQUOTE class=3Dgmail_quote=20
  style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: =
#ccc 1px solid"><BR>I=20
    cannot access it. Would you check the URL again?<BR><BR>John Buford=20
    wrote:<BR>&gt; Presentation slides on Prof. Kevin Almeroth's keynote =
at P2P=20
    <BR>&gt; Multicasting 07<BR>&gt; on "Multicast Help Wanted: From =
Where and=20
    How Much?"<BR>&gt; are available at<BR>&gt;<BR>&gt; <A=20
    =
href=3D"http://samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt">http:/=
/samrg.org/p2pm07/Keynote-KevinAlmeroth-p2pm-07.ppt=20
    </A><BR>&gt;=20
    =
------------------------------------------------------------------------<=
BR>&gt;<BR>&gt;=20
    _______________________________________________<BR>&gt; SAM mailing=20
    list<BR>&gt; <A href=3D"mailto:SAM@irtf.org">SAM@irtf.org =
</A><BR>&gt; <A=20
    =
href=3D"https://www1.ietf.org/mailman/listinfo/sam">https://www1.ietf.org=
/mailman/listinfo/sam</A><BR>&gt;<BR><BR></BLOCKQUOTE></DIV><BR><BR=20
  clear=3Dall></BLOCKQUOTE></BODY></HTML>

------_=_NextPart_001_01C73628.C540D7D4--



--===============0456695494==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============0456695494==--





From sam-bounces@irtf.org Fri Jan 19 13:24:01 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1H7yP4-0001hO-Ru; Fri, 19 Jan 2007 13:23:54 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1H7yP3-0001hH-4t
	for sam@irtf.org; Fri, 19 Jan 2007 13:23:53 -0500
Received: from wx-out-0506.google.com ([66.249.82.224])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1H7yOp-0003HJ-TP
	for sam@irtf.org; Fri, 19 Jan 2007 13:23:53 -0500
Received: by wx-out-0506.google.com with SMTP id i28so601714wxd
	for <sam@irtf.org>; Fri, 19 Jan 2007 10:23:39 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=rXPRIsGjXrgl1ynm/PxHrXma1o5d3X+GhtMSqZyE/MxQQgLhCbSQH2QSv1IHRnNDrOFPUS5imk8zUv+V0gwRgSgpAFaAd/bKhDqgloKXcWHis3AbG+eSxpIWJqoYJbg0/yioIpuOTHViLxvyIkgWhry9MVTiiSPtbyckG0MRX8E=
Received: by 10.70.113.16 with SMTP id l16mr4291408wxc.1169231019417;
	Fri, 19 Jan 2007 10:23:39 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Fri, 19 Jan 2007 10:23:39 -0800 (PST)
Message-ID: <4ce32a820701191023l6565e033qff31d99b86086301@mail.gmail.com>
Date: Fri, 19 Jan 2007 13:23:39 -0500
From: "John Buford" <buford@samrg.org>
To: sam@irtf.org
In-Reply-To: <4ce32a820701191021g76dc8630y76757fcc31ace44e@mail.gmail.com>
MIME-Version: 1.0
References: <4ce32a820701191021g76dc8630y76757fcc31ace44e@mail.gmail.com>
X-Google-Sender-Auth: 28765cca9d74bc3d
X-Spam-Score: 0.1 (/)
X-Scan-Signature: f66b12316365a3fe519e75911daf28a8
Subject: [SAM] CFP - P2P Networking Track at Globecom 2007 - deadline March
	15
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1705762486=="
Errors-To: sam-bounces@irtf.org

--===============1705762486==
Content-Type: multipart/alternative; 
	boundary="----=_Part_18560_31039052.1169231019308"

------=_Part_18560_31039052.1169231019308
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

(Apologies for duplicate postings)

IEEE GLOBECOM 2007 (Washington, D.C., November 26-30, 2007) with the theme
"Innovate, Educate, Accelerate", will feature a General Symposium and 9
technical symposia.  The focus of the General Symposium is on Emerging
Technologies.

The *Peer-to-Peer Networking Track* in the General Symposium invites
state-of-art work in all areas of peer-to-peer networking, overlay
networking, peer casting, application layer multicasting, service overlays,
peer-to-peer search algorithms. Topics of particular interest include, but
are not limited to:
Overlay architectures and topologies
Overlay maintenance algorithms
Overlay and application layer multicast
Peercasting and overlay content distribution
Federated and hierarchical overlays
One-hop and variable-hop overlays
Peer-to-peer SIP
Overlay support for mobile nodes
Measurement based overlays
Replication and load-balancing strategies
Service overlays
Peer-to-peer service/resource discovery
Tools for large-scale performance analysis
Distributed security techniques
Novel applications
Semantic routing
Advanced search and query techniques
Semantic search
Coupling of agent systems and P2P systems
Experience with deployed systems

Submission deadline is March 15, 2007.

For further information:
P2P Networking Track, see: http://samrg.org/globecom2007-gs/p2p-networking/
Globecom 2007 - General Symposium, see:
http://samrg.org/globecom2007-gs/index.html
Globecom 2007 - http://www.comsoc.org/confs/globecom/2007/tech.html

------=_Part_18560_31039052.1169231019308
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>(Apologies for duplicate postings)</div>
<div>
<div>
<p><font face="Arial" size="2">IEEE GLOBECOM 2007<span> (<font face="Times New Roman" size="3">Washington, D.C., November 26-30, 2007) </font></span>with the theme &quot;Innovate, Educate, Accelerate&quot;, will feature a General Symposium and 9 technical symposia.&nbsp; The focus of the General Symposium is on Emerging Technologies. 
</font></p>
<p><font face="Arial" size="2">The <i><strong>Peer-to-Peer Networking Track</strong></i> in the General Symposium invites state-of-art work in all areas of peer-to-peer networking, overlay networking, peer casting, application layer multicasting, service overlays, peer-to-peer search algorithms. Topics of particular interest include, but are not limited to: 
</font></p>
<li><font face="Arial" size="2">Overlay architectures and topologies </font>
<li><font face="Arial" size="2">Overlay maintenance algorithms </font>
<li><font face="Arial" size="2">Overlay and application layer multicast </font>
<li><font face="Arial" size="2">Peercasting and overlay content distribution </font>
<li><font face="Arial" size="2">Federated and hierarchical overlays </font>
<li><font face="Arial" size="2">One-hop and variable-hop overlays </font>
<li><font face="Arial" size="2">Peer-to-peer SIP </font>
<li><font face="Arial" size="2">Overlay support for mobile nodes </font>
<li><font face="Arial" size="2">Measurement based overlays </font>
<li><font face="Arial" size="2">Replication and load-balancing strategies </font>
<li><font face="Arial" size="2">Service overlays </font>
<li><font face="Arial" size="2">Peer-to-peer service/resource discovery </font>
<li><font face="Arial" size="2">Tools for large-scale performance analysis </font>
<li><font face="Arial" size="2">Distributed security techniques </font>
<li><font face="Arial" size="2">Novel applications </font>
<li><font face="Arial" size="2">Semantic routing </font>
<li><font face="Arial" size="2">Advanced search and query techniques </font>
<li><font face="Arial" size="2">Semantic search </font>
<li><font face="Arial" size="2">Coupling of agent systems and P2P systems </font>
<li><font face="Arial" size="2">Experience with deployed systems </font></li></li></li></li></li></li></li></li></li></li></li></li></li></li></li></li></li></li></li></li></div>
<div><font face="Arial" size="2"></font>&nbsp;</div>
<div><span><font face="Arial" size="2">Submission deadline is March 15, 2007.</font></span></div>
<div><font face="Arial" size="2"></font>&nbsp;</div>
<div><span><font face="Arial" size="2">For further information:</font></span></div>
<div><span><font face="Arial" size="2">P2P Networking Track, see: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://samrg.org/globecom2007-gs/p2p-networking/" target="_blank"><font color="#800080">http://samrg.org/globecom2007-gs/p2p-networking/ 
</font></a></font></span></div>
<div><span><font face="Arial" size="2">Globecom 2007 - General Symposium, see: <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://samrg.org/globecom2007-gs/index.html" target="_blank">http://samrg.org/globecom2007-gs/index.html
</a></font></span> </div>
<div><span><font face="Arial" size="2">Globecom 2007 - <a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.comsoc.org/confs/globecom/2007/tech.html" target="_blank"><font color="#800080">http://www.comsoc.org/confs/globecom/2007/tech.html
</font> </a></font></span></div></div><br clear="all"><br>

------=_Part_18560_31039052.1169231019308--


--===============1705762486==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============1705762486==--




From sam-bounces@irtf.org Mon Jan 29 14:27:10 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBc9L-0007jv-BR; Mon, 29 Jan 2007 14:26:43 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBc9K-0007jq-9z
	for sam@irtf.org; Mon, 29 Jan 2007 14:26:42 -0500
Received: from wx-out-0506.google.com ([66.249.82.227])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBc9H-00014s-PT
	for sam@irtf.org; Mon, 29 Jan 2007 14:26:42 -0500
Received: by wx-out-0506.google.com with SMTP id i28so1949780wxd
	for <sam@irtf.org>; Mon, 29 Jan 2007 11:26:39 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=iSNpxMjleK/BEUGIdHl3TAbcwfX0v2Gg4PXcXWZo03FyDFb7e/mvifc/l5e61F8h/Tsfn1cvOQDrV3enJPWUSjRkfAfsG0UMPChBuN3/LLJ3svXqbytIvUoGsPNjRfCIe9h/O5TQRgC5etwkzytbMdC6+ciXnL0GAzAVwDjrSzE=
Received: by 10.70.91.11 with SMTP id o11mr1611057wxb.1170098798643;
	Mon, 29 Jan 2007 11:26:38 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Mon, 29 Jan 2007 11:26:38 -0800 (PST)
Message-ID: <4ce32a820701291126l2a6897d8nce4c4b3f03462475@mail.gmail.com>
Date: Mon, 29 Jan 2007 14:26:38 -0500
From: "John Buford" <buford@samrg.org>
To: sam@irtf.org
In-Reply-To: <4ce32a820701121512i7e1582dds4f4400ec818c4208@mail.gmail.com>
MIME-Version: 1.0
References: <4ce32a820701121512i7e1582dds4f4400ec818c4208@mail.gmail.com>
X-Google-Sender-Auth: 62ee1b014dce12d1
X-Spam-Score: 0.5 (/)
X-Scan-Signature: bc6181926481d86059e678c9f7cb8b34
Subject: [SAM] SAM RG interim meeting results
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0563871328=="
Errors-To: sam-bounces@irtf.org

--===============0563871328==
Content-Type: multipart/alternative; 
	boundary="----=_Part_64205_27024760.1170098798602"

------=_Part_64205_27024760.1170098798602
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Presentations and meeting notes for the Jan 11 interim SAM RG meeting
are available here:

http://www.samrg.org/about/meetings/meetings.html
(not all slides are available yet, they will be uploaded as they
become available)

Presentations made at the P2PM07 workshop are available here:
http://www.samrg.org/p2pm07/program.html

(not all slides are available yet, they will be uploaded as they become
available)

We are currently planning to hold an RG meeting at IEFT 69 (Chicago).

Minutes from the meeting follow.

===============================================================


Meeting Notes
Scalable Adaptive Multicast RG
Interim Meeting Jan 11, 2007.

1. John Buford (Panasonic)

Overview of problem statement draft
and the existing technologies available
(ALM, Overlay multicast, Proxied overlay
multicast, tunneling with native multicast
islands).
An example architecture and some
operational scenarios.

1. Jeremy Mineweaser (MIT Lincoln Labs)

Adaptativity depends on suitable metrics
and ability to collect these metrics in
real-time and feedback to the network.


Discussion:

KA: Do you think adaptive approach is too complex to be worth the benefit?
JM: remains to be seen
KA: We don't really have a one-size-fits-all protocol

2. Mark Pullen (GMU)

Unlike commercial ISPs,DoD ISPs have an incentive
to use multicast to reduce congestion.
But universal deployment in GIG may not work any better
than in commercial sector.
Gaming community can use multicast in different ways
than DoD since they don't require the real-world fidelity.

In battlefield, reliability and robustness may not be
fully achievable.

We at GMU have a prototype to manage multicast using
web services in cooperation with Naval Post-Graduate school.

There is a need for a framework to interoperate
different mechanisms, a pervasive interoperability should be targeted.
Need the pieces to interoperate in order to mix and match technologies.
Would like to see a standardized tunneling mechanism as well.
Could use the framework for "relative" QoS not absolute QoS.
Relative QoS is important for military applications.

3. Keith Ross (Polytechnic)

P2P Multicast is an IPTV case study
There are several success stories: PPLive, Coolstream, ppstream
200K users at 400-800 kbps for Chinese New Years

What are the challenges?
- Bandwidth intensive
- peers dynamic
- asymetric residential access
- incentives for redistribution
- lags among viewers
- security (pollution, overtaking for DDoS)

Comparison of two Architectures
- Push, tree-based designs, eg. ESM from CMU
- Pull, meshed based designs
   Inspired from BiTorrent
   But with live streaming
  More successful than ESM

Overview of pull-mesh
 Locate other peers watching same channel
 Establish TCP connection
 Ask neighbors what chunks they have
 Request and receive chunks
 Start media player
 Upload chunks to others

Presents some measurements of download
 vs upload rate for different users

Popular and unpopular channels
Pull-mesh / IPTV is killer application for multicast

JM: what are limitations?
KR: free-riding problem, susceptibility to pollution attack
Audience: what is the performance comparison between pull and push
KR: coolstreaming paper has analysis that shows the ESM
    is not good under churn
JB: what about licensed content?
KR: yes, content provides can see this as another distribution channel


4. Kurt Tutschku (U. Wuerzburg)

Challenges on scalable multicast in overlay with mobile networks
There are several challenges due to mobile nodes in an overlay
  which translate to problems with overlay multicast with mobile
  nodes
These problems relate to roaming in the native network,
node performance capability, variation in network connectivity etc.


5. Wenjun Zeng (U. Missouri)

Do you plan to consider reliability, congestion control,
   etc., in the design?
Pull vs push is an important distinction, as made by Keith
Is there a hybrid of pull vs push?
E.g., tree-bone based approach

6. General Discussion

What about data aggregation for sensor
data collection (ad hoc wireless networks),
is there a multicast solution for this case,
and how does it fit?

The benefits of an overlay approach for launching SAM framework:
Overlays provide a number of interesting functions including
search, indexing, relaying, topology characterization, measurement.
Integrating awareness of native multicast in to the overlay is
another function like these others that a specific overlay can
chose to use or not depending on application requirements.

Solutions to the problems of overlays in terms of reliability
and security can be used for multicast reliability and security
perhaps.

------=_Part_64205_27024760.1170098798602
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<span class="gmail_quote"></span>
<div>&nbsp;</div>
<div>Presentations and meeting notes for the Jan 11 <span class="st" id="st" name="st">interim</span> SAM RG meeting</div>
<div>are available here:</div>
<div>&nbsp;</div>
<div><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.samrg.org/about/meetings/meetings.html" target="_blank">http://www.samrg.org/about/meetings/meetings.html</a></div>
<div>(not all slides are available yet, they will be uploaded as they</div>
<div>become available)</div>
<div>&nbsp;</div>
<div>Presentations made at the P2PM07 workshop are available here:</div>
<div><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.samrg.org/p2pm07/program.html" target="_blank">http://www.samrg.org/p2pm07/program.html</a></div>
<div>&nbsp;</div>
<div>(not all slides are available yet, they will be uploaded as they become</div>
<div>available)</div>
<div>&nbsp;</div>
<div>We are currently planning to hold an RG meeting at IEFT 69 (Chicago).</div>
<div>&nbsp;</div>
<div>Minutes from the meeting follow.</div>
<div>&nbsp;</div>
<div>===============================================================</div>
<div>&nbsp;</div>
<div>
<p>Meeting Notes<br>Scalable Adaptive Multicast RG<br><span class="st" id="st" name="st">Interim</span> Meeting Jan 11, 2007.</p>
<p>1. John Buford (Panasonic)</p>
<p>Overview of problem statement draft<br>and the existing technologies available<br>(ALM, Overlay multicast, Proxied overlay<br>multicast, tunneling with native multicast<br>islands).<br>An example architecture and some 
<br>operational scenarios.</p>
<p>1. Jeremy Mineweaser (MIT Lincoln Labs)</p>
<p>Adaptativity depends on suitable metrics<br>and ability to collect these metrics in<br>real-time and feedback to the network.</p>
<p><br>Discussion:</p>
<p>KA: Do you think adaptive approach is too complex to be worth the benefit?<br>JM: remains to be seen<br>KA: We don&#39;t really have a one-size-fits-all protocol</p>
<p>2. Mark Pullen (GMU)</p>
<p>Unlike commercial ISPs,DoD ISPs have an incentive <br>to use multicast to reduce congestion.<br>But universal deployment in GIG may not work any better <br>than in commercial sector.<br>Gaming community can use multicast in different ways 
<br>than DoD since they don&#39;t require the real-world fidelity.</p>
<p>In battlefield, reliability and robustness may not be <br>fully achievable.</p>
<p>We at GMU have a prototype to manage multicast using <br>web services in cooperation with Naval Post-Graduate school.</p>
<p>There is a need for a framework to interoperate <br>different mechanisms, a pervasive interoperability should be targeted.<br>Need the pieces to interoperate in order to mix and match technologies.<br>Would like to see a standardized tunneling mechanism as well. 
<br>Could use the framework for &quot;relative&quot; QoS not absolute QoS. <br>Relative QoS is important for military applications.</p>
<p>3. Keith Ross (Polytechnic)</p>
<p>P2P Multicast is an IPTV case study<br>There are several success stories: PPLive, Coolstream, ppstream<br>200K users at 400-800 kbps for Chinese New Years</p>
<p>What are the challenges?<br>- Bandwidth intensive<br>- peers dynamic<br>- asymetric residential access<br>- incentives for redistribution<br>- lags among viewers<br>- security (pollution, overtaking for DDoS)</p>
<p>Comparison of two Architectures<br>- Push, tree-based designs, eg. ESM from CMU<br>- Pull, meshed based designs<br>&nbsp;&nbsp; Inspired from BiTorrent<br>&nbsp;&nbsp; But with live streaming<br>&nbsp; More successful than ESM</p>
<p>Overview of pull-mesh<br>&nbsp;Locate other peers watching same channel<br>&nbsp;Establish TCP connection<br>&nbsp;Ask neighbors what chunks they have<br>&nbsp;Request and receive chunks<br>&nbsp;Start media player<br>&nbsp;Upload chunks to others 
</p>
<p>Presents some measurements of download<br>&nbsp;vs upload rate for different users</p>
<p>Popular and unpopular channels<br>Pull-mesh / IPTV is killer application for multicast</p>
<p>JM: what are limitations?<br>KR: free-riding problem, susceptibility to pollution attack<br>Audience: what is the performance comparison between pull and push<br>KR: coolstreaming paper has analysis that shows the ESM 
<br>&nbsp;&nbsp;&nbsp; is not good under churn<br>JB: what about licensed content?<br>KR: yes, content provides can see this as another distribution channel</p>
<p><br>4. Kurt Tutschku (U. Wuerzburg)</p>
<p>Challenges on scalable multicast in overlay with mobile networks<br>There are several challenges due to mobile nodes in an overlay<br>&nbsp; which translate to problems with overlay multicast with mobile <br>&nbsp; nodes<br>These problems relate to roaming in the native network, 
<br>node performance capability, variation in network connectivity etc.</p>
<p><br>5. Wenjun Zeng (U. Missouri)</p>
<p>Do you plan to consider reliability, congestion control, <br>&nbsp;&nbsp; etc., in the design?<br>Pull vs push is an important distinction, as made by Keith<br>Is there a hybrid of pull vs push?<br>E.g., tree-bone based approach 
</p>
<p>6. General Discussion</p>
<p>What about data aggregation for sensor <br>data collection (ad hoc wireless networks), <br>is there a multicast solution for this case,<br>and how does it fit?</p>
<p>The benefits of an overlay approach for launching SAM framework:<br>Overlays provide a number of interesting functions including<br>search, indexing, relaying, topology characterization, measurement.<br>Integrating awareness of native multicast in to the overlay is 
<br>another function like these others that a specific overlay can<br>chose to use or not depending on application requirements.</p>
<p>Solutions to the problems of overlays in terms of reliability <br>and security can be used for multicast reliability and security<br>perhaps.</p>
<p>&nbsp;</p></div>

------=_Part_64205_27024760.1170098798602--


--===============0563871328==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============0563871328==--




From sam-bounces@irtf.org Mon Jan 29 14:31:39 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBcE3-0000mk-I5; Mon, 29 Jan 2007 14:31:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBcE2-0000mc-BS
	for sam@irtf.org; Mon, 29 Jan 2007 14:31:34 -0500
Received: from wx-out-0506.google.com ([66.249.82.231])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBcE1-0001gj-Rq
	for sam@irtf.org; Mon, 29 Jan 2007 14:31:34 -0500
Received: by wx-out-0506.google.com with SMTP id i28so1951280wxd
	for <sam@irtf.org>; Mon, 29 Jan 2007 11:31:31 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:references:x-google-sender-auth;
	b=A2oYqHt5JH5rPuKLP3IXDrGsNFm8pSu7ABdAje9RFv1FS85IUkTwIzWrSVSqbSTmEcdygWf21aAZGvMmU6b8gfOnUOkEcUy6SgMPLcPN8OLeOl41z5AAx4WnaaCakGzxUUDDiIfce36WJ+8cu4Bl17kFgLFxJnHx+shAKEPC35g=
Received: by 10.70.75.14 with SMTP id x14mr1619651wxa.1170099090975;
	Mon, 29 Jan 2007 11:31:30 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Mon, 29 Jan 2007 11:31:30 -0800 (PST)
Message-ID: <4ce32a820701291131u659faa48r665e8dba5caa2c7c@mail.gmail.com>
Date: Mon, 29 Jan 2007 14:31:30 -0500
From: "John Buford" <buford@samrg.org>
To: sam@irtf.org
In-Reply-To: <4ce32a820701121512i7e1582dds4f4400ec818c4208@mail.gmail.com>
MIME-Version: 1.0
References: <4ce32a820701121512i7e1582dds4f4400ec818c4208@mail.gmail.com>
X-Google-Sender-Auth: 2a2454a426cdb25b
X-Spam-Score: 0.3 (/)
X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96
Subject: [SAM] SAM RG interim meeting results
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0650825800=="
Errors-To: sam-bounces@irtf.org

--===============0650825800==
Content-Type: multipart/alternative; 
	boundary="----=_Part_64297_20658045.1170099090704"

------=_Part_64297_20658045.1170099090704
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Presentations and meeting notes for the Jan 11 interim SAM RG meeting
are available here:

http://www.samrg.org/about/meetings/meetings.html
(not all slides are available yet, they will be uploaded as they
become available)

Presentations made at the P2PM07 workshop are available here:
http://www.samrg.org/p2pm07/program.html

(not all slides are available yet, they will be uploaded as they become
available)

We are currently planning to hold an RG meeting at IEFT 69 (Chicago).

Minutes from the meeting follow.

===============================================================


Meeting Notes
Scalable Adaptive Multicast RG
Interim Meeting Jan 11, 2007.

1. John Buford (Panasonic)

Overview of problem statement draft
and the existing technologies available
(ALM, Overlay multicast, Proxied overlay
multicast, tunneling with native multicast
islands).
An example architecture and some
operational scenarios.

1. Jeremy Mineweaser (MIT Lincoln Labs)

Adaptativity depends on suitable metrics
and ability to collect these metrics in
real-time and feedback to the network.


Discussion:

KA: Do you think adaptive approach is too complex to be worth the benefit?
JM: remains to be seen
KA: We don't really have a one-size-fits-all protocol

2. Mark Pullen (GMU)

Unlike commercial ISPs,DoD ISPs have an incentive
to use multicast to reduce congestion.
But universal deployment in GIG may not work any better
than in commercial sector.
Gaming community can use multicast in different ways
than DoD since they don't require the real-world fidelity.

In battlefield, reliability and robustness may not be
fully achievable.

We at GMU have a prototype to manage multicast using
web services in cooperation with Naval Post-Graduate school.

There is a need for a framework to interoperate
different mechanisms, a pervasive interoperability should be targeted.
Need the pieces to interoperate in order to mix and match technologies.
Would like to see a standardized tunneling mechanism as well.
Could use the framework for "relative" QoS not absolute QoS.
Relative QoS is important for military applications.

3. Keith Ross (Polytechnic)

P2P Multicast is an IPTV case study
There are several success stories: PPLive, Coolstream, ppstream
200K users at 400-800 kbps for Chinese New Years

What are the challenges?
- Bandwidth intensive
- peers dynamic
- asymetric residential access
- incentives for redistribution
- lags among viewers
- security (pollution, overtaking for DDoS)

Comparison of two Architectures
- Push, tree-based designs, eg. ESM from CMU
- Pull, meshed based designs
   Inspired from BiTorrent
   But with live streaming
  More successful than ESM

Overview of pull-mesh
 Locate other peers watching same channel
 Establish TCP connection
 Ask neighbors what chunks they have
 Request and receive chunks
 Start media player
 Upload chunks to others

Presents some measurements of download
 vs upload rate for different users

Popular and unpopular channels
Pull-mesh / IPTV is killer application for multicast

JM: what are limitations?
KR: free-riding problem, susceptibility to pollution attack
Audience: what is the performance comparison between pull and push
KR: coolstreaming paper has analysis that shows the ESM
    is not good under churn
JB: what about licensed content?
KR: yes, content provides can see this as another distribution channel


4. Kurt Tutschku (U. Wuerzburg)

Challenges on scalable multicast in overlay with mobile networks
There are several challenges due to mobile nodes in an overlay
  which translate to problems with overlay multicast with mobile
  nodes
These problems relate to roaming in the native network,
node performance capability, variation in network connectivity etc.


5. Wenjun Zeng (U. Missouri)

Do you plan to consider reliability, congestion control,
   etc., in the design?
Pull vs push is an important distinction, as made by Keith
Is there a hybrid of pull vs push?
E.g., tree-bone based approach

6. General Discussion

What about data aggregation for sensor
data collection (ad hoc wireless networks),
is there a multicast solution for this case,
and how does it fit?

The benefits of an overlay approach for launching SAM framework:
Overlays provide a number of interesting functions including
search, indexing, relaying, topology characterization, measurement.
Integrating awareness of native multicast in to the overlay is
another function like these others that a specific overlay can
chose to use or not depending on application requirements.

Solutions to the problems of overlays in terms of reliability
and security can be used for multicast reliability and security
perhaps.

------=_Part_64297_20658045.1170099090704
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>Presentations and meeting notes for the Jan 11 interim SAM RG meeting</div>
<div>are available here:</div>
<div>&nbsp;</div>
<div><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.samrg.org/about/meetings/meetings.html" target="_blank">http://www.samrg.org/about/meetings/meetings.html</a></div>
<div>(not all slides are available yet, they will be uploaded as they</div>
<div>become available)</div>
<div>&nbsp;</div>
<div>Presentations made at the P2PM07 workshop are available here:</div>
<div><a onclick="return top.js.OpenExtLink(window,event,this)" href="http://www.samrg.org/p2pm07/program.html" target="_blank">http://www.samrg.org/p2pm07/program.html</a></div>
<div>&nbsp;</div>
<div>(not all slides are available yet, they will be uploaded as they become</div>
<div>available)</div>
<div>&nbsp;</div>
<div>We are currently planning to hold an RG meeting at IEFT 69 (Chicago).</div>
<div>&nbsp;</div>
<div>Minutes from the meeting follow.</div>
<div>&nbsp;</div>
<div>===============================================================</div>
<div>&nbsp;</div>
<div>
<p>Meeting Notes<br>Scalable Adaptive Multicast RG<br>Interim Meeting Jan 11, 2007.</p>
<p>1. John Buford (Panasonic)</p>
<p>Overview of problem statement draft<br>and the existing technologies available<br>(ALM, Overlay multicast, Proxied overlay<br>multicast, tunneling with native multicast<br>islands).<br>An example architecture and some 
<br>operational scenarios.</p>
<p>1. Jeremy Mineweaser (MIT Lincoln Labs)</p>
<p>Adaptativity depends on suitable metrics<br>and ability to collect these metrics in<br>real-time and feedback to the network.</p>
<p><br>Discussion:</p>
<p>KA: Do you think adaptive approach is too complex to be worth the benefit?<br>JM: remains to be seen<br>KA: We don&#39;t really have a one-size-fits-all protocol</p>
<p>2. Mark Pullen (GMU)</p>
<p>Unlike commercial ISPs,DoD ISPs have an incentive <br>to use multicast to reduce congestion.<br>But universal deployment in GIG may not work any better <br>than in commercial sector.<br>Gaming community can use multicast in different ways 
<br>than DoD since they don&#39;t require the real-world fidelity.</p>
<p>In battlefield, reliability and robustness may not be <br>fully achievable.</p>
<p>We at GMU have a prototype to manage multicast using <br>web services in cooperation with Naval Post-Graduate school.</p>
<p>There is a need for a framework to interoperate <br>different mechanisms, a pervasive interoperability should be targeted.<br>Need the pieces to interoperate in order to mix and match technologies.<br>Would like to see a standardized tunneling mechanism as well. 
<br>Could use the framework for &quot;relative&quot; QoS not absolute QoS. <br>Relative QoS is important for military applications.</p>
<p>3. Keith Ross (Polytechnic)</p>
<p>P2P Multicast is an IPTV case study<br>There are several success stories: PPLive, Coolstream, ppstream<br>200K users at 400-800 kbps for Chinese New Years</p>
<p>What are the challenges?<br>- Bandwidth intensive<br>- peers dynamic<br>- asymetric residential access<br>- incentives for redistribution<br>- lags among viewers<br>- security (pollution, overtaking for DDoS)</p>
<p>Comparison of two Architectures<br>- Push, tree-based designs, eg. ESM from CMU<br>- Pull, meshed based designs<br>&nbsp;&nbsp; Inspired from BiTorrent<br>&nbsp;&nbsp; But with live streaming<br>&nbsp; More successful than ESM</p>
<p>Overview of pull-mesh<br>&nbsp;Locate other peers watching same channel<br>&nbsp;Establish TCP connection<br>&nbsp;Ask neighbors what chunks they have<br>&nbsp;Request and receive chunks<br>&nbsp;Start media player<br>&nbsp;Upload chunks to others 
</p>
<p>Presents some measurements of download<br>&nbsp;vs upload rate for different users</p>
<p>Popular and unpopular channels<br>Pull-mesh / IPTV is killer application for multicast</p>
<p>JM: what are limitations?<br>KR: free-riding problem, susceptibility to pollution attack<br>Audience: what is the performance comparison between pull and push<br>KR: coolstreaming paper has analysis that shows the ESM 
<br>&nbsp;&nbsp;&nbsp; is not good under churn<br>JB: what about licensed content?<br>KR: yes, content provides can see this as another distribution channel</p>
<p><br>4. Kurt Tutschku (U. Wuerzburg)</p>
<p>Challenges on scalable multicast in overlay with mobile networks<br>There are several challenges due to mobile nodes in an overlay<br>&nbsp; which translate to problems with overlay multicast with mobile <br>&nbsp; nodes<br>These problems relate to roaming in the native network, 
<br>node performance capability, variation in network connectivity etc.</p>
<p><br>5. Wenjun Zeng (U. Missouri)</p>
<p>Do you plan to consider reliability, congestion control, <br>&nbsp;&nbsp; etc., in the design?<br>Pull vs push is an important distinction, as made by Keith<br>Is there a hybrid of pull vs push?<br>E.g., tree-bone based approach 
</p>
<p>6. General Discussion</p>
<p>What about data aggregation for sensor <br>data collection (ad hoc wireless networks), <br>is there a multicast solution for this case,<br>and how does it fit?</p>
<p>The benefits of an overlay approach for launching SAM framework:<br>Overlays provide a number of interesting functions including<br>search, indexing, relaying, topology characterization, measurement.<br>Integrating awareness of native multicast in to the overlay is 
<br>another function like these others that a specific overlay can<br>chose to use or not depending on application requirements.</p>
<p>Solutions to the problems of overlays in terms of reliability <br>and security can be used for multicast reliability and security<br>perhaps.</p></div>

------=_Part_64297_20658045.1170099090704--


--===============0650825800==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============0650825800==--




From sam-bounces@irtf.org Mon Jan 29 15:16:54 2007
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1HBcvp-0002v9-U7; Mon, 29 Jan 2007 15:16:49 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1HBcvp-0002v4-7P
	for sam@irtf.org; Mon, 29 Jan 2007 15:16:49 -0500
Received: from an-out-0708.google.com ([209.85.132.250])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HBcvm-0000YC-08
	for sam@irtf.org; Mon, 29 Jan 2007 15:16:49 -0500
Received: by an-out-0708.google.com with SMTP id c16so581114ana
	for <sam@irtf.org>; Mon, 29 Jan 2007 12:16:45 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta;
	h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth;
	b=jbVGIenDRwpbLfECZJep/J7Nmi1BB+gLihWIjBDpCGf5RiLN2hscm3wN91rec7UQLd4/e7XyeBvvdNoDzoxyp+MeO7RiP1KRyKeVjqSwtquZliSs1NuKSB58BsvKdRpNweZ9wwx8bsQQ2Jx01eXKb47TbigLL2E7zECMGhQB2Gw=
Received: by 10.100.136.13 with SMTP id j13mr646634and.1170101805086;
	Mon, 29 Jan 2007 12:16:45 -0800 (PST)
Received: by 10.70.19.9 with HTTP; Mon, 29 Jan 2007 12:16:45 -0800 (PST)
Message-ID: <4ce32a820701291216l137b1e5au1684ec0a58a4451e@mail.gmail.com>
Date: Mon, 29 Jan 2007 15:16:45 -0500
From: "John Buford" <buford@samrg.org>
To: sam@irtf.org
MIME-Version: 1.0
X-Google-Sender-Auth: 184d49ab7231a848
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22
Subject: [SAM] draft-irtf-sam-hybrid-overlay-framework-01.txt
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG"
	<sam.irtf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sam>,
	<mailto:sam-request@irtf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0054197554=="
Errors-To: sam-bounces@irtf.org

--===============0054197554==
Content-Type: multipart/alternative; 
	boundary="----=_Part_65265_17120422.1170101805022"

------=_Part_65265_17120422.1170101805022
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

A new ID on "Hybrid Overlay Multicast Framework" is available.

draft-irtf-sam-hybrid-overlay-framework-01.txt

Follow the ID link on samrg.org to locate all active SAM IDs.

John

------=_Part_65265_17120422.1170101805022
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>&nbsp;</div>
<div>A new&nbsp;ID on &quot;Hybrid Overlay Multicast Framework&quot; is available.</div>
<div>&nbsp;</div>
<div>draft-irtf-sam-hybrid-overlay-framework-01.txt </div>
<div>&nbsp;</div>
<div>Follow the ID link on <a href="http://samrg.org">samrg.org</a> to locate all active SAM IDs.</div>
<div>&nbsp;</div>
<div>John</div>

------=_Part_65265_17120422.1170101805022--


--===============0054197554==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
SAM mailing list
SAM@irtf.org
https://www1.ietf.org/mailman/listinfo/sam

--===============0054197554==--




