From sam-bounces@irtf.org Fri Aug 17 05:14:37 2007
Return-path: <sam-bounces@irtf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILxue-0002us-Kz; Fri, 17 Aug 2007 05:14:36 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILxud-0002un-BA
	for sam@irtf.org; Fri, 17 Aug 2007 05:14:35 -0400
Received: from smtp.mei.co.jp ([133.183.129.25])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILxub-0006EW-Mk
	for sam@irtf.org; Fri, 17 Aug 2007 05:14:35 -0400
Received: from mail-gw.jp.panasonic.com (dodgers.mei.co.jp [157.8.1.150])
	by smtp.mei.co.jp (8.12.11.20060614/3.7W/kings) with ESMTP id
	l7H9EWO3003310
	for <sam@irtf.org>; Fri, 17 Aug 2007 18:14:32 +0900 (JST)
Received: by mail-gw.jp.panasonic.com (8.11.6p2/3.7W/somlx2) with ESMTP id
	l7H9EW907988
	for <sam@irtf.org>; Fri, 17 Aug 2007 18:14:32 +0900 (JST)
Received: from localhost (localhost [127.0.0.1])
	by mail.jp.panasonic.com (8.11.6p2/3.7W/mariners) with SMTP id
	l7H9EXN14729
	for <sam@irtf.org>; Fri, 17 Aug 2007 18:14:33 +0900 (JST)
Content-class: urn:content-classes:message
Date: Fri, 17 Aug 2007 17:14:25 +0800
MIME-Version: 1.0
Message-ID: <769E965D82021346949AF2BC41D8EAB71FB2DD@prdcm-mail.prdcm.panasonic.com.my>
X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: SAMTK @irtf69
Thread-Index: AcfgrwCetYQsXoPXTu+EM0jwX4tOWg==
From: "Lim Boon Ping" <boonping.lim@my.panasonic.com>
To: <sam@irtf.org>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 155726d2f5fe5eb5c40a9f079fd9e841
Subject: [SAM] SAMTK @irtf69
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="===============0525166229=="
Errors-To: sam-bounces@irtf.org

This is a multi-part message in MIME format.

--===============0525166229==
Content-class: urn:content-classes:message
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C7E0AF.01BA002F"

This is a multi-part message in MIME format.

------_=_NextPart_001_01C7E0AF.01BA002F
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

=20

We have recently explored into SAM-RG activities through the mailing =
list and
meeting materials, and are keen to understand more on SAM-RG latest =
technical
priority and research focus.=20

=20

We are particularly interested to understand more on SAMTK by Mr. =
Kawaguchi,
specifically on SAMTK integration with Topology Management module.

I have read the presentation material in
http://samrg.org/about/meetings/ietf69/SAMTK-kawaguchi-ierf69.ppt, and =
would
hope if Mr. Kawaguchi or the RG members could clarify some of the =
questions.

=20
What the scope of Topology management is as indicated in Slide 6? How do =
you
envision ALM/OM/hybrid protocols (given as a Plugin) seamlessly =
integrating
with SAMTK's Group Membership/Traffic management module? There are a few
dynamic topology management protocol discussed in the previous meetings, =
such
as Dynamic Mesh-based overlay multicast protocol (DMMP) and Hybrid =
Shared
Tree, could these protocol/mechanism easily being integrated/ported into
SAMTK? What're the standard input/output parameters would be provided by
SAMTK to/from the topology management plugin?=20
=20
Quite a number SAM applications have been developed using SAMTK, is =
there any
plan to integrate dynamic topology management plugin (eg. dynamic ALM
topology construction/update/route convergence), and perform experiment =
trial
on PlanetLab (or others large scale research test bed)?=20
=20
This work seems to be a good effort to spearhead a Standard Framework =
for
rapid SAM application development/deployment. How is this effort being
envisioned by other members in the RG?=20
=20

Hope to hear your thought on this soon!=20

=20

=20

Yours truly,

Boon Ping

Panasonic Kuala Lumpur Lab

=20

=20

=20

=20


------_=_NextPart_001_01C7E0AF.01BA002F
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 11 (filtered medium)">
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Courier New";
	color:windowtext;
	font-weight:normal;
	font-style:normal;
	text-decoration:none none;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
	{page:Section1;}
-->
</style>

</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Hi all,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>We have recently explored into SAM-RG =
activities
through the mailing list and meeting materials, and are keen to =
understand more
on SAM-RG latest technical priority and research focus. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>We are particularly interested to understand =
more on
SAMTK by Mr. Kawaguchi, specifically on SAMTK integration with Topology
Management module.<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>I have read the presentation material in <a
href=3D"http://samrg.org/about/meetings/ietf69/SAMTK-kawaguchi-ierf69.ppt=
"
title=3D"http://samrg.org/about/meetings/ietf69/SAMTK-kawaguchi-ierf69.pp=
t">http://samrg.org/about/meetings/ietf69/SAMTK-kawaguchi-ierf69.ppt</a>,=

and would hope if Mr. Kawaguchi or the RG members could clarify some of =
the
questions.<o:p></o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>What the =
scope of Topology management is as indicated in Slide 6? How do you =
envision ALM/OM/hybrid protocols (given as a Plugin) seamlessly =
integrating with SAMTK&#8217;s Group Membership/Traffic management =
module? There are a few dynamic topology management protocol discussed =
in the previous meetings, such as Dynamic Mesh-based overlay multicast =
protocol (DMMP) and Hybrid Shared Tree, could these protocol/mechanism =
easily being integrated/ported into SAMTK? What&#8217;re the standard =
input/output parameters would be provided by SAMTK to/from the topology =
management plugin? <o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>Quite a =
number SAM applications have been developed using SAMTK, is there any =
plan to integrate dynamic topology management plugin (eg. dynamic ALM =
topology construction/update/route convergence), and perform experiment =
trial on PlanetLab (or others large scale research test bed)? =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre><pre><fon=
t
size=3D2 face=3D"Courier New"><span style=3D'font-size:10.0pt'>This work =
seems to be a good effort to spearhead a Standard Framework for rapid =
SAM application development/deployment. How is this effort being =
envisioned by other members in the RG? =
<o:p></o:p></span></font></pre><pre><font
size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;font-family:"Courier New"'>Hope to hear your =
thought on
this soon! <o:p></o:p></span></font></p>

<pre><font size=3D2 face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt'><o:p>&nbsp;</o:p></span></font></pre>

<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Yours truly,<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Boon <st1:place =
w:st=3D"on">Ping</st1:place><o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'>Panasonic Kuala Lumpur =
Lab<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 face=3D"Courier New"><span =
style=3D'font-size:10.0pt;
font-family:"Courier New"'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

</div>

</body>

</html>

------_=_NextPart_001_01C7E0AF.01BA002F--



--===============0525166229==
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

--===============0525166229==--





From sam-bounces@irtf.org Fri Aug 17 05:59:45 2007
Return-path: <sam-bounces@irtf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
	by megatron.ietf.org with esmtp (Exim 4.43)
	id 1ILycL-0001PZ-Pq; Fri, 17 Aug 2007 05:59:45 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.43) id 1ILycK-0001PH-Lf
	for sam@irtf.org; Fri, 17 Aug 2007 05:59:44 -0400
Received: from mail1.nagoya-u.jp ([133.6.1.41])
	by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1ILycI-000744-PP
	for sam@irtf.org; Fri, 17 Aug 2007 05:59:44 -0400
Received: from [192.168.203.120] (unknown [133.6.33.173])
	by mail1.nagoya-u.jp (Postfix) with ESMTP id 866C280098;
	Fri, 17 Aug 2007 18:59:32 +0900 (JST)
Message-ID: <46C57182.6010401@nagoya-u.jp>
Date: Fri, 17 Aug 2007 18:59:30 +0900
From: Nobuo Kawaguchi <kawaguti@nagoya-u.jp>
Organization: Nagoya University
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Lim Boon Ping <boonping.lim@my.panasonic.com>
Subject: Re: [SAM] SAMTK @irtf69
References: <769E965D82021346949AF2BC41D8EAB71FB2DD@prdcm-mail.prdcm.panasonic.com.my>
In-Reply-To: <769E965D82021346949AF2BC41D8EAB71FB2DD@prdcm-mail.prdcm.panasonic.com.my>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5
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 Lim Boon Ping,

Thank you for having interest of SAMTK.
We are currently under alpha-development phase.

However, most of development efforts of SAMTK are 
held for protocol abstraction and group-management.
So topology management is not currently implemented.
(It is open for plug-in developers)

However, current plug-in interface is very simple.
If you have any comments, please let me know.

(Below is a part of current plug-in interface implementation )
---
    qint64 writeDatagram ( const char * data, qint64 size, SAMGroupAddress *g=NULL);
    bool start(ushort selfport);
    qint64 readDatagram ( char * data, qint64 maxSize, QHostAddress *address=0, quint16 *port = 0);
    bool hasPendingDatagrams () const;
    qint64 pendingDatagramSize ();   
    void close();
    bool setGroup(SAMGroupAddress *group);
    bool addMember(const SAMGroupMember &member);
    bool deleteMember(const SAMGroupMember &member);
---
SAMGroupAddress is a class for group of node addresses obtained 
from group management module.

Most of interface design is derived from Qt QUDPSocket.

I'm not sure it is enough to implement other ALM/OM protocols.
However, we are willing to support plug-in development on SAMTK.

yours,

Nobuo Kawaguchi

Lim Boon Ping wrote:
> Hi all,
> 
>  
> 
> We have recently explored into SAM-RG activities through the mailing list and
> meeting materials, and are keen to understand more on SAM-RG latest technical
> priority and research focus. 
> 
>  
> 
> We are particularly interested to understand more on SAMTK by Mr. Kawaguchi,
> specifically on SAMTK integration with Topology Management module.
> 
> I have read the presentation material in
> http://samrg.org/about/meetings/ietf69/SAMTK-kawaguchi-ierf69.ppt, and would
> hope if Mr. Kawaguchi or the RG members could clarify some of the questions.
> 
>  
> What the scope of Topology management is as indicated in Slide 6? How do you
> envision ALM/OM/hybrid protocols (given as a Plugin) seamlessly integrating
> with SAMTK's Group Membership/Traffic management module? There are a few
> dynamic topology management protocol discussed in the previous meetings, such
> as Dynamic Mesh-based overlay multicast protocol (DMMP) and Hybrid Shared
> Tree, could these protocol/mechanism easily being integrated/ported into
> SAMTK? What're the standard input/output parameters would be provided by
> SAMTK to/from the topology management plugin? 
>  
> Quite a number SAM applications have been developed using SAMTK, is there any
> plan to integrate dynamic topology management plugin (eg. dynamic ALM
> topology construction/update/route convergence), and perform experiment trial
> on PlanetLab (or others large scale research test bed)? 
>  
> This work seems to be a good effort to spearhead a Standard Framework for
> rapid SAM application development/deployment. How is this effort being
> envisioned by other members in the RG? 
>  
> 
> Hope to hear your thought on this soon! 
> 
>  
> 
>  
> 
> Yours truly,
> 
> Boon Ping
> 
> Panasonic Kuala Lumpur Lab
> 
>  
> 
>  
> 
>  
> 
>  
> 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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



