
From Barry.Constantine@jdsu.com  Mon Dec  2 06:27:28 2013
Return-Path: <Barry.Constantine@jdsu.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 690151AE2CC for <ippm@ietfa.amsl.com>; Mon,  2 Dec 2013 06:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0UyGi6tbAu8J for <ippm@ietfa.amsl.com>; Mon,  2 Dec 2013 06:27:24 -0800 (PST)
Received: from mx0a-00158d01.pphosted.com (mx0a-00158d01.pphosted.com [208.84.65.189]) by ietfa.amsl.com (Postfix) with ESMTP id B36A61AE47E for <ippm@ietf.org>; Mon,  2 Dec 2013 06:27:24 -0800 (PST)
Received: from pps.filterd (m0043267.ppops.net [127.0.0.1]) by mx0a-00158d01.pphosted.com (8.14.5/8.14.5) with SMTP id rB2EP2Sq009604 for <ippm@ietf.org>; Mon, 2 Dec 2013 06:27:22 -0800
Received: from mx1.jdsu.com ([157.234.211.50]) by mx0a-00158d01.pphosted.com with ESMTP id 1gga0n2x96-1 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ippm@ietf.org>; Mon, 02 Dec 2013 06:27:22 -0800
Received: from AMEXHTCA03.ds.jdsu.net (10.239.69.13) by mx1.jdsu.com (10.239.15.50) with Microsoft SMTP Server (TLS) id 14.2.342.3; Mon, 2 Dec 2013 06:27:20 -0800
Received: from AMEXMB01.ds.jdsu.net ([fe80::9402:2c4c:29f3:a264]) by AMEXHTCA03.ds.jdsu.net ([fe80::24df:4228:5274:253d%14]) with mapi id 14.02.0342.003; Mon, 2 Dec 2013 06:27:21 -0800
From: Barry Constantine <Barry.Constantine@jdsu.com>
To: "ippm@ietf.org" <ippm@ietf.org>
Thread-Topic: Review of draft-ietf-ippm-rate-problem-04
Thread-Index: Ac7vZTbEr/oNL+OzTvGTvJ4HM49ijQ==
Date: Mon, 2 Dec 2013 14:27:21 +0000
Message-ID: <DE2AAE0A8826CF4ABC3A6CCB756356EB201C5B@AMEXMB01.ds.jdsu.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [157.234.234.5]
Content-Type: multipart/alternative; boundary="_000_DE2AAE0A8826CF4ABC3A6CCB756356EB201C5BAMEXMB01dsjdsunet_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.72, 1.0.14, 0.0.0000 definitions=2013-12-02_01:2013-12-02,2013-12-02,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1312020081
Subject: [ippm] Review of draft-ietf-ippm-rate-problem-04
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 02 Dec 2013 14:27:28 -0000

--_000_DE2AAE0A8826CF4ABC3A6CCB756356EB201C5BAMEXMB01dsjdsunet_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi IPPM,

As agreed in VC, I reviewed this work and have the following comments.

First off, it is a very good draft and does a good job of explaining the na=
ture of the problem, while providing some context to high level measurement=
 method requirements.

So here are some specific suggestions:

Section 2:

-        Extremely large scale of access services requires low complexity

devices participating at the user end of the path.



** I was not sure how this was a different scenario from an access network =
perspective, probably needs another sentence or two to explain.



Other use cases for rate measurement involve situations where the packet sw=
itching and transport facilities are leased by one operator
from another and the link capacity available cannot be directly determined =
(e.g., from device interface utilization).  These
scenarios could include mobile backhaul, Ethernet Service access networks, =
and/or extensions of layer 2 or layer 3 networks.



** This is really important and in these cases, operators are specifying bu=
rst sizes in addition to CIR.  I think the rate measurement problem stateme=
nt should identify  burst testing as part of the problem since this is more=
 and more being added into the SLA (especially between providers, not so mu=
ch for business services yet)


As noted in [RFC2330] the actual traffic handling may influence the rate me=
asurement results for some forms of access

** Maybe a nit, but would it be better to say "traffic management" verus "t=
raffic handling"?  Also, does this imply more broadly that QoS policy is ap=
plied to the user traffic per the examples listed (packet length, IP addres=
ses, etc)?  If so, I would include DSCP in the list of examples since this =
is widely used and understood.

Opportunistic In-Service testing when there is no user traffic present thro=
ughout the test interval is essentially equivalent to Out-of-Service testin=
g.

** Suggest:  Opportunistic In-Service testing when there is no user traffic=
 present throughout (i.e. after normal business hours)

Section 3:
REPORTER:
Use information from test packets and local processes to measure delivered =
packet rates, and prepare results in the required format.

** Should a sentence or two be added to clarify that the REPORTER  may be a=
 separate test entity or may be embedded into the SENDER for example?

Section 4:
For all categories, the test protocol MUST support:

d.  Choice of UDP transport and variable port numbers, OR, choice of
       TCP transport and variable port numbers for two-way architectures
       only, OR BOTH.

**  This implies TCP "stateless" traffic per Mathis's model-based work, rig=
ht?

e.  Variable number of packets-pairs, ensembles, or streams used in a test =
session

** This should include VLAN or MPLS tagging, right?

Thank you,
Barry Constantine

JDSU Network and Service Enablement
Principal Member Technical Staff
301-325-7069


--_000_DE2AAE0A8826CF4ABC3A6CCB756356EB201C5BAMEXMB01dsjdsunet_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" 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=3D"Generator" content=3D"Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@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;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@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:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:193425065;
	mso-list-type:hybrid;
	mso-list-template-ids:-1573338338 -929555228 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:20.4pt;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:56.4pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:92.4pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:128.4pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:164.4pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:200.4pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:236.4pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:272.4pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:308.4pt;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi IPPM,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">As agreed in VC, I reviewed this work and have the f=
ollowing comments.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">First off, it is a very good draft and does a good j=
ob of explaining the nature of the problem, while providing some context to=
 high level measurement method requirements.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So here are some specific suggestions:<o:p></o:p></p=
>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2:<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:20.4pt;text-indent:-.25i=
n;mso-list:l0 level1 lfo1">
<![if !supportLists]><span style=3D"mso-list:Ignore">-<span style=3D"font:7=
.0pt &quot;Times New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;
</span></span><![endif]>Extremely large scale of access services requires l=
ow complexity<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:20.4pt">devices particip=
ating at the user end of the path.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:20.4pt"><o:p>&nbsp;</o:p=
></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in">** I was not sure h=
ow this was a different scenario from an access network perspective, probab=
ly needs another sentence or two to explain.<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><o:p>&nbsp;</o:p></=
p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in">Other use cases for=
 rate measurement involve situations where the packet switching and transpo=
rt facilities are leased by one operator<o:p></o:p></p>
<p class=3D"MsoNormal">from another and the link capacity available cannot =
be directly determined (e.g., from device interface utilization).&nbsp; The=
se<o:p></o:p></p>
<p class=3D"MsoNormal">scenarios could include mobile backhaul, Ethernet Se=
rvice access networks, and/or extensions of layer 2 or layer 3 networks.<o:=
p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><o:p>&nbsp;</o:p></=
p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in">** This is really i=
mportant and in these cases, operators are specifying burst sizes in additi=
on to CIR.&nbsp; I think the rate measurement problem statement should iden=
tify &nbsp;burst testing as part of the problem
 since this is more and more being added into the SLA (especially between p=
roviders, not so much for business services yet)<o:p></o:p></p>
<p class=3D"MsoListParagraph" style=3D"margin-left:0in"><o:p>&nbsp;</o:p></=
p>
<p class=3D"MsoNormal">As noted in [RFC2330] the actual traffic handling ma=
y influence the rate measurement results for some forms of access<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">** Maybe a nit, but would it be better to say &#8220=
;traffic management&#8221; verus &#8220;traffic handling&#8221;?&nbsp; Also=
, does this imply more broadly that QoS policy is applied to the user traff=
ic per the examples listed (packet length, IP addresses, etc)?&nbsp;
 If so, I would include DSCP in the list of examples since this is widely u=
sed and understood.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Opportunistic In-Service testing when there is no us=
er traffic present throughout the test interval is essentially equivalent t=
o Out-of-Service testing.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">** Suggest:&nbsp; Opportunistic In-Service testing w=
hen there is no user traffic present throughout (i.e. after normal business=
 hours)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 3:<o:p></o:p></p>
<p class=3D"MsoNormal">REPORTER:<o:p></o:p></p>
<p class=3D"MsoNormal">Use information from test packets and local processe=
s to measure delivered packet rates, and prepare results in the required fo=
rmat.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">** Should a sentence or two be added to clarify that=
 the REPORTER&nbsp; may be a separate test entity or may be embedded into t=
he SENDER for example?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4:<o:p></o:p></p>
<p class=3D"MsoNormal">For all categories, the test protocol MUST support:<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">d.&nbsp; Choice of UDP transport and variable port n=
umbers, OR, choice of<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TCP transport a=
nd variable port numbers for two-way architectures<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; only, OR BOTH.<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">**&nbsp; This implies TCP &#8220;stateless&#8221; tr=
affic per Mathis&#8217;s model-based work, right?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">e.&nbsp; Variable number of packets-pairs, ensembles=
, or streams used in a test session<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">** This should include VLAN or MPLS tagging, right?<=
o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thank you,<o:p></o:p></p>
<p class=3D"MsoNormal">Barry Constantine<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">JDSU Network and Service Enablement<o:p></o:p></p>
<p class=3D"MsoNormal">Principal Member Technical Staff<o:p></o:p></p>
<p class=3D"MsoNormal">301-325-7069<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_DE2AAE0A8826CF4ABC3A6CCB756356EB201C5BAMEXMB01dsjdsunet_--

From a.botta@unina.it  Fri Dec  6 05:31:41 2013
Return-Path: <a.botta@unina.it>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D0C01ADFAE for <ippm@ietfa.amsl.com>; Fri,  6 Dec 2013 05:31:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.678
X-Spam-Level: ***
X-Spam-Status: No, score=3.678 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_AFFORDABLE=1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id c7igtDjNbEwv for <ippm@ietfa.amsl.com>; Fri,  6 Dec 2013 05:31:38 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id 09FA61ADFAD for <ippm@ietf.org>; Fri,  6 Dec 2013 05:31:37 -0800 (PST)
Received: from [143.225.229.197] ([143.225.229.197]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id rB6DVUEd002173 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ippm@ietf.org>; Fri, 6 Dec 2013 14:31:31 +0100
Message-ID: <52A1D1B1.2010606@unina.it>
Date: Fri, 06 Dec 2013 14:31:29 +0100
From: Alessio Botta <a.botta@unina.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: ippm@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [ippm] [InfQ] TRICANS 2014 - Deadline is next week - 2nd IEEE Workshop on Traffic Identification and Classification for Advanced Network Services and Scenarios (TRICANS) ICC 2014 Workshop
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 06 Dec 2013 13:31:41 -0000

[Our apologies if you receive multiple copies of this CFP]

The deadline is next week!
The paper submission deadline on EDAS is 15 December 2013!

----------------------------------------------------------------------------
CALL FOR PAPER 2nd IEEE Workshop on Traffic Identification and 
Classification for Advanced Network Services and Scenarios (TRICANS)
ICC 2014 Workshop
Sidney - 14 June 2014
----------------------------------------------------------------------------

2nd IEEE Workshop on Traffic Identification and Classification for 
Advanced Network Services and Scenarios (TRICANS) - ICC 2014 Workshop
http://www.grid.unina.it/TRICANS2014

*** Scope and Topics of Interest ***
The 2014 IEEE ICC TRICANS Workshop will provide an excellent 
international forum for sharing state-of-the-art advances and 
experiences in scientific research on Internet traffic identification 
and classification and their associated applications on advanced network 
scenarios and novel network services. TRICANS 2014 will explicitly 
consider traffic identification and classification as well as management 
issues related to novel and very challenging scenarios, such as Software 
Defined Networking (SDN). The 2014 IEEE International Conference on 
Communications (ICC) will be held in the beautiful city of Sydney, 
Australia from 10-14 June 2014. Themed "Communications: The Centrepoint 
of the Digital Economy," this flagship conference of IEEE Communications 
Society will feature a comprehensive technical program including twelve 
Symposia and a number of Tutorials and Workshops. IEEE ICC 2014 will 
also include an exceptional expo program including keynote speakers and 
an Industry Forum & Exhibition. IEEE ICC is one of the flagship 
conferences of the IEEE Communications Society and it attracts about 
2-3.000 submitted scientific papers. IEEE ICC is therefore one of the 
most significant scientific events of the networking and communications 
community with a great visibility for published papers.
The ever-growing network link speeds have reached hundreds of Gbps and 
they are quickly approaching to Tbps in the core network. In order to 
support accurate network profiling of users and services, ISPs have been 
relying on Deep Packet Inspection (DPI), computational intelligence 
techniques, or other behavioral analysis of the Internet traffic. 
However, there are still a number of challenges in this field. On one 
hand, new networked applications come daily into play bringing massive 
amounts of traffic data to be processed in real-time. Such traffic 
volume keeps pushing industry and academia researchers to develop 
affordable yet efficient traffic identification and classification 
systems. To this end, there are demands for high-performance distributed 
and parallel traffic classification systems for either commodity or 
special-purposed hardware platforms. Dealing with encrypted traffic is 
of particular interest and is also very challenging. On the other hand, 
in the long-term, such solutions for traffic profiling will become part 
of the network management tools and techniques portfolio available for 
advanced network services. Also, new architectures and their supporting 
technologies, such as SDN, information- and content-centric networking 
architectures will require network profiling services to enable robust 
and dynamic networking services capabilities.
To address these research challenges, this workshop will focus on 
theory, tools, techniques, and applications of traffic identification 
and classification systems to enable advanced support for 
next-generation networking architectures, services, and scenarios. The 
topics covered by the workshop include, but are not limited to, the 
following:
- Measurement and modelling of Internet traffic for advanced networked 
services
- Network and system troubleshooting through traffic classification 
mechanisms
- Network profiling of users and networked applications
- Security and privacy in traffic identification and classification 
mechanisms
- Lightweight technologies for DPI in routers and middle-boxes
- DPI technologies support for virtual networks and cloud computing 
management
- Profiling network traffic in data center networks and cloud computing 
systems
- Inferring and assessing Quality of Experience (QoE) of users and services
- Novel visualization techniques for traffic classification and analysis
- Packet processing support in operating systems for novel line-rate 
network services
- Management of large network traffic data sets
- SDN approaches for network performance monitoring
- Traffic classification in SDN network elements and controllers

*** Submission Guidelines ***
Prospective authors are encouraged to submit a full paper (5 pages) for 
review. Only original papers that have not been published or submitted 
for publication elsewhere will be considered. Submit your papers through 
EDAS. These submissions should follow the IEEE ICC 2014 formatting 
guidelines, templates for which are available at the main conference web 
page. The maximum paper length is of five (5) pages.

*** Important Dates ***
15 December 2013: Paper submission deadline on EDAS
30 January 2014: Reviews Completed
20 February 2014: Paper Acceptance Notification
15 March 2014: Camera Ready copies submitted.
Workshop date: 14 June 2014

*** Workshop General Chairs ***
Stenio Fernandes, Federal University of Pernambuco, Recife, Brazil
Antonio Pescapé, University of Napoli ''Federico II'', Napoli, Italy
Géza Szabó, Ericsson Traffic Laboratory, Budapest, Hungary

*** Publicity Chair ***
Alessio Botta, University of Napoli ''Federico II'', Napoli, Italy

*** Technical Program Committee ***
Alberto Dainotti, CAIDA, USA
Alessio Botta, University of Napoli Federico II
Artur Ziviani, LNCC, Brazil
Carlos Kamienski, UFABC, Brazil
Djamel Sadok, UFPE, Brazil
Domenico Ficara, University of Pisa, Italy
Fabian Schneider, NEC Lab
Istvan Godor, Ericsson, Hungary
Jason Zurawski, Energy Sciences Network (ESnet), USA
José Augusto Suruagy, UFPE, Brazil
Hyun-chul Kim, Seoul National University, South Korea
László Toka, Ericsson, Hungary
Maurizio Dusi, NEC, Germany
Marco Mellia, Polito, Italy
Marinho Barcelos, UFRGS, Brazil
Myung-Sup Kim, Korea University
Nur Zincir-Heywood, Dalhousie University, Canada
Philippe Owezarski, CNRS, France
Rafael Antonello, Federal Institute of Technology (AL), Brazil
Sándor Molnár, Budapest University of Technology and Economics,, Hungary
Youngjoon Won, Korea University

*** Workshop website address ***
http://www.grid.unina.it/TRICANS2014
----------------------------------------------------------------------------

-- 
Alessio Botta, PhD
Dipartimento di Ingegneria Elettrica e delle Tecnologie dell'Informazione
Università degli Studi di Napoli "Federico II"
Via Claudio 21 -- 80125 Napoli (Italy) [Room 3.09]
Phone: +390817683865 - Fax: +390817683816
Skypeid: alessiobotta
Email: a.botta@unina.it
alessio.botta@consorzio-cini.it
WWW: http://wpage.unina.it/a.botta

---------------------------------------------------------------------
To unsubscribe, e-mail: infq-unsubscribe@infq.it
For additional commands, e-mail: infq-help@infq.it



From internet-drafts@ietf.org  Thu Dec 12 07:18:08 2013
Return-Path: <internet-drafts@ietf.org>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F3B21AE2FF; Thu, 12 Dec 2013 07:18:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zSfaNUZXSQ4R; Thu, 12 Dec 2013 07:18:06 -0800 (PST)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B8FF41ADBD0; Thu, 12 Dec 2013 07:18:06 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 4.83.p1
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20131212151806.30236.50454.idtracker@ietfa.amsl.com>
Date: Thu, 12 Dec 2013 07:18:06 -0800
Cc: ippm@ietf.org
Subject: [ippm] I-D Action: draft-ietf-ippm-rate-problem-05.txt
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 15:18:08 -0000

A New Internet-Draft is available from the on-line Internet-Drafts director=
ies.
 This draft is a work item of the IP Performance Metrics Working Group of t=
he IETF.

	Title           : Rate Measurement Test Protocol Problem Statement
	Author(s)       : Al Morton
	Filename        : draft-ietf-ippm-rate-problem-05.txt
	Pages           : 12
	Date            : 2013-12-12

Abstract:
   This memo presents an access rate-measurement problem statement for
   test protocols to measure IP Performance Metrics.  The rate
   measurement scenario has wide-spread attention of Internet access
   subscribers and seemingly all industry players, including regulators.
   Key test protocol aspects require the ability to control packet size
   on the tested path and enable asymmetrical packet size testing in a
   controller-responder architecture.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-ippm-rate-problem

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-ippm-rate-problem-05

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=3Ddraft-ietf-ippm-rate-problem-05


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From trammell@tik.ee.ethz.ch  Thu Dec 12 07:38:41 2013
Return-Path: <trammell@tik.ee.ethz.ch>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3692F1AE32D for <ippm@ietfa.amsl.com>; Thu, 12 Dec 2013 07:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FNRw0U822Un4 for <ippm@ietfa.amsl.com>; Thu, 12 Dec 2013 07:38:39 -0800 (PST)
Received: from smtp.ee.ethz.ch (smtp.ee.ethz.ch [129.132.2.219]) by ietfa.amsl.com (Postfix) with ESMTP id C841F1AE326 for <ippm@ietf.org>; Thu, 12 Dec 2013 07:38:38 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.ee.ethz.ch (Postfix) with ESMTP id D6B8ED930D for <ippm@ietf.org>; Thu, 12 Dec 2013 16:38:31 +0100 (MET)
X-Virus-Scanned: by amavisd-new on smtp.ee.ethz.ch
Received: from smtp.ee.ethz.ch ([127.0.0.1]) by localhost (.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with LMTP id oL0H64tkye91 for <ippm@ietf.org>; Thu, 12 Dec 2013 16:38:31 +0100 (MET)
Received: from pb-10243.ethz.ch (pb-10243.ethz.ch [82.130.102.152]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: briant) by smtp.ee.ethz.ch (Postfix) with ESMTPSA id 95CE4D9303 for <ippm@ietf.org>; Thu, 12 Dec 2013 16:38:31 +0100 (MET)
Message-ID: <52A9D877.9020305@tik.ee.ethz.ch>
Date: Thu, 12 Dec 2013 16:38:31 +0100
From: Brian Trammell <trammell@tik.ee.ethz.ch>
User-Agent: Postbox 3.0.8 (Macintosh/20130427)
MIME-Version: 1.0
To: "ippm@ietf.org" <ippm@ietf.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: [ippm] Comments on draft-mizrahi-owamp-twamp-checksum-trailer
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 15:38:41 -0000

Greetings, all,

(chair hat off)

At the request of its author, I've taken a look as an individual
contributor at draft-mizrahi-owamp-twamp-checksum-trailer.

The draft describes a relatively straightforward and interoperable
method for keeping UDP checksums valid during post-transmission
modification of OWAMP and TWAMP packets, specifically to allow modifying
timestamps in hardware for more accurate timing information. This
definitely seems like a useful thing to have.

I have only one complaint, and that is that the draft is not named so as
to allow convenient tracking in the datatracker as an individual draft
targeted to the IPPM working group, and would suggest that a future
revision of the draft be named
draft-mizrahi-ippm-owamp-twamp-checksum-trailer.

A couple of comments/questions:

(1) Section 3.4. recommends that authentication and the checksum trailer
not be used together. I presume that this arrangement would also not be
compatible with draft-ippm-ietf-ipsec for similar reasons?

(2) The draft presumes that the timestamping hardware and OWAMP/TWAMP
implementation are implemented together. When this is not the case
(i.e., if we want interop between timestamping hardware and OWAMP/TWAMP
implementations from different sources): Does/should the draft have any
guidance for what a timestamping hardware device should do if it does
not detect sufficient padding to add a checksum trailer and/or detects
that the final two octets of the padding may be used for some other purpose?

Best regards,

Brian (again, as individual)

From acmorton@att.com  Thu Dec 12 07:50:25 2013
Return-Path: <acmorton@att.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 06CA91AE31D for <ippm@ietfa.amsl.com>; Thu, 12 Dec 2013 07:50:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBGI8kTORFPy for <ippm@ietfa.amsl.com>; Thu, 12 Dec 2013 07:50:21 -0800 (PST)
Received: from mail-red.research.att.com (mail-red.research.att.com [204.178.8.23]) by ietfa.amsl.com (Postfix) with ESMTP id 590561AD9AC for <ippm@ietf.org>; Thu, 12 Dec 2013 07:50:21 -0800 (PST)
Received: from mail-blue.research.att.com (unknown [135.207.178.11]) by mail-red.research.att.com (Postfix) with ESMTP id 21E1255415E; Thu, 12 Dec 2013 10:50:34 -0500 (EST)
Received: from njfpsrvexg8.research.att.com (unknown [135.207.255.242]) by mail-blue.research.att.com (Postfix) with ESMTP id 4DA14F0147; Thu, 12 Dec 2013 10:50:15 -0500 (EST)
Received: from NJFPSRVEXG8.research.att.com ([fe80::cdea:b3f6:3efa:1841]) by njfpsrvexg8.research.att.com ([fe80::a44a:8177:9a5d:ac00%15]) with mapi; Thu, 12 Dec 2013 10:50:15 -0500
From: "MORTON, ALFRED C (AL)" <acmorton@att.com>
To: Barry Constantine <Barry.Constantine@jdsu.com>, "ippm@ietf.org" <ippm@ietf.org>
Date: Thu, 12 Dec 2013 10:50:13 -0500
Thread-Topic: Review of draft-ietf-ippm-rate-problem-04
Thread-Index: Ac7vZTbEr/oNL+OzTvGTvJ4HM49ijQH6Qtqg
Message-ID: <2845723087023D4CB5114223779FA9C8AC527045@njfpsrvexg8.research.att.com>
References: <DE2AAE0A8826CF4ABC3A6CCB756356EB201C5B@AMEXMB01.ds.jdsu.net>
In-Reply-To: <DE2AAE0A8826CF4ABC3A6CCB756356EB201C5B@AMEXMB01.ds.jdsu.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_2845723087023D4CB5114223779FA9C8AC527045njfpsrvexg8rese_"
MIME-Version: 1.0
Subject: Re: [ippm] Review of draft-ietf-ippm-rate-problem-04
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 15:50:25 -0000

--_000_2845723087023D4CB5114223779FA9C8AC527045njfpsrvexg8rese_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi Barry, thanks for your comments and suggestions.

I have uploaded version 05 which addresses your comments.
(the announcement seems to be delayed, but I assure you that
submission was successful)

In one case, you said:

** This is really important and in these cases, operators are specifying bu=
rst sizes in addition to CIR.  I think the rate measurement problem stateme=
nt should identify  burst testing as part of the problem since this is more=
 and more being added into the SLA (especially between providers, not so mu=
ch for business services yet)

I'm sure you read later on (section 4) that burst generation is mandatory,
and we can describe the various methods in more detail when we move beyond =
the
scope, so that's what is done.

regards,
Al


From: ippm [mailto:ippm-bounces@ietf.org] On Behalf Of Barry Constantine
Sent: Monday, December 02, 2013 9:27 AM
To: ippm@ietf.org
Subject: [ippm] Review of draft-ietf-ippm-rate-problem-04

Hi IPPM,

As agreed in VC, I reviewed this work and have the following comments.

First off, it is a very good draft and does a good job of explaining the na=
ture of the problem, while providing some context to high level measurement=
 method requirements.

So here are some specific suggestions:

Section 2:

-          Extremely large scale of access services requires low complexity

devices participating at the user end of the path.



** I was not sure how this was a different scenario from an access network =
perspective, probably needs another sentence or two to explain.



Other use cases for rate measurement involve situations where the packet sw=
itching and transport facilities are leased by one operator
from another and the link capacity available cannot be directly determined =
(e.g., from device interface utilization).  These
scenarios could include mobile backhaul, Ethernet Service access networks, =
and/or extensions of layer 2 or layer 3 networks.



** This is really important and in these cases, operators are specifying bu=
rst sizes in addition to CIR.  I think the rate measurement problem stateme=
nt should identify  burst testing as part of the problem since this is more=
 and more being added into the SLA (especially between providers, not so mu=
ch for business services yet)


As noted in [RFC2330] the actual traffic handling may influence the rate me=
asurement results for some forms of access

** Maybe a nit, but would it be better to say "traffic management" verus "t=
raffic handling"?  Also, does this imply more broadly that QoS policy is ap=
plied to the user traffic per the examples listed (packet length, IP addres=
ses, etc)?  If so, I would include DSCP in the list of examples since this =
is widely used and understood.

Opportunistic In-Service testing when there is no user traffic present thro=
ughout the test interval is essentially equivalent to Out-of-Service testin=
g.

** Suggest:  Opportunistic In-Service testing when there is no user traffic=
 present throughout (i.e. after normal business hours)

Section 3:
REPORTER:
Use information from test packets and local processes to measure delivered =
packet rates, and prepare results in the required format.

** Should a sentence or two be added to clarify that the REPORTER  may be a=
 separate test entity or may be embedded into the SENDER for example?

Section 4:
For all categories, the test protocol MUST support:

d.  Choice of UDP transport and variable port numbers, OR, choice of
       TCP transport and variable port numbers for two-way architectures
       only, OR BOTH.

**  This implies TCP "stateless" traffic per Mathis's model-based work, rig=
ht?

e.  Variable number of packets-pairs, ensembles, or streams used in a test =
session

** This should include VLAN or MPLS tagging, right?

Thank you,
Barry Constantine

JDSU Network and Service Enablement
Principal Member Technical Staff
301-325-7069


--_000_2845723087023D4CB5114223779FA9C8AC527045njfpsrvexg8rese_
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-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=
=3D"text/html; charset=3Dus-ascii"><meta name=3DGenerator content=3D"Micros=
oft Word 14 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Courier New";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:193425065;
	mso-list-type:hybrid;
	mso-list-template-ids:-1573338338 -929555228 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:20.4pt;
	text-indent:-.25in;
	font-family:"Calibri","sans-serif";
	mso-fareast-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:56.4pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:92.4pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:128.4pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:164.4pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:200.4pt;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:236.4pt;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:272.4pt;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:308.4pt;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]--></head><body lang=3DEN-US link=3Dblue vli=
nk=3Dpurple><div class=3DWordSection1><p class=3DMsoNormal><span style=3D'f=
ont-size:10.0pt;font-family:"Courier New"'>Hi Barry, thanks for your commen=
ts and suggestions.<o:p></o:p></span></p><p class=3DMsoNormal><span style=
=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p=
><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier =
New"'>I have uploaded version 05 which addresses your comments.<o:p></o:p><=
/span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:=
"Courier New"'>(the announcement seems to be delayed, but I assure you that=
<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;=
font-family:"Courier New"'>submission was successful)<o:p></o:p></span></p>=
<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier N=
ew"'><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span style=3D'font-s=
ize:10.0pt;font-family:"Courier New"'>In one case, you said:<o:p></o:p></sp=
an></p><p class=3DMsoListParagraph style=3D'margin-left:0in'>** This is rea=
lly important and in these cases, operators are specifying burst sizes in a=
ddition to CIR.&nbsp; I think the rate measurement problem statement should=
 identify &nbsp;burst testing as part of the problem since this is more and=
 more being added into the SLA (especially between providers, not so much f=
or business services yet)<o:p></o:p></p><p class=3DMsoNormal><span style=3D=
'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p=
 class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New=
"'>I'm sure you read later on (section 4) that burst generation is mandator=
y,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0p=
t;font-family:"Courier New"'>and we can describe the various methods in mor=
e detail when we move beyond the<o:p></o:p></span></p><p class=3DMsoNormal>=
<span style=3D'font-size:10.0pt;font-family:"Courier New"'>scope, so that's=
 what is done.<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'fon=
t-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;</o:p></span></p><p cla=
ss=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Courier New"'>r=
egards,<o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:=
10.0pt;font-family:"Courier New"'>Al<o:p></o:p></span></p><p class=3DMsoNor=
mal><span style=3D'font-size:10.0pt;font-family:"Courier New"'><o:p>&nbsp;<=
/o:p></span></p><p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-f=
amily:"Courier New"'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;=
border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt'><div><div style=3D'=
border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p cl=
ass=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma","sa=
ns-serif"'>From:</span></b><span style=3D'font-size:10.0pt;font-family:"Tah=
oma","sans-serif"'> ippm [mailto:ippm-bounces@ietf.org] <b>On Behalf Of </b=
>Barry Constantine<br><b>Sent:</b> Monday, December 02, 2013 9:27 AM<br><b>=
To:</b> ippm@ietf.org<br><b>Subject:</b> [ippm] Review of draft-ietf-ippm-r=
ate-problem-04<o:p></o:p></span></p></div></div><p class=3DMsoNormal><o:p>&=
nbsp;</o:p></p><p class=3DMsoNormal>Hi IPPM,<o:p></o:p></p><p class=3DMsoNo=
rmal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As agreed in VC, I reviewed =
this work and have the following comments.<o:p></o:p></p><p class=3DMsoNorm=
al><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>First off, it is a very good d=
raft and does a good job of explaining the nature of the problem, while pro=
viding some context to high level measurement method requirements.<o:p></o:=
p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>So her=
e are some specific suggestions:<o:p></o:p></p><p class=3DMsoNormal><o:p>&n=
bsp;</o:p></p><p class=3DMsoNormal>Section 2:<o:p></o:p></p><p class=3DMsoL=
istParagraph style=3D'margin-left:20.4pt;text-indent:-.25in;mso-list:l0 lev=
el1 lfo2'><![if !supportLists]><span style=3D'mso-list:Ignore'>-<span style=
=3D'font:7.0pt "Times New Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp; </span></span><![endif]>Extremely large scale of access servi=
ces requires low complexity<o:p></o:p></p><p class=3DMsoListParagraph style=
=3D'margin-left:20.4pt'>devices participating at the user end of the path.<=
o:p></o:p></p><p class=3DMsoListParagraph style=3D'margin-left:20.4pt'><o:p=
>&nbsp;</o:p></p><p class=3DMsoListParagraph style=3D'margin-left:0in'>** I=
 was not sure how this was a different scenario from an access network pers=
pective, probably needs another sentence or two to explain.<o:p></o:p></p><=
p class=3DMsoListParagraph style=3D'margin-left:0in'><o:p>&nbsp;</o:p></p><=
p class=3DMsoListParagraph style=3D'margin-left:0in'>Other use cases for ra=
te measurement involve situations where the packet switching and transport =
facilities are leased by one operator<o:p></o:p></p><p class=3DMsoNormal>fr=
om another and the link capacity available cannot be directly determined (e=
.g., from device interface utilization).&nbsp; These<o:p></o:p></p><p class=
=3DMsoNormal>scenarios could include mobile backhaul, Ethernet Service acce=
ss networks, and/or extensions of layer 2 or layer 3 networks.<o:p></o:p></=
p><p class=3DMsoListParagraph style=3D'margin-left:0in'><o:p>&nbsp;</o:p></=
p><p class=3DMsoListParagraph style=3D'margin-left:0in'>** This is really i=
mportant and in these cases, operators are specifying burst sizes in additi=
on to CIR.&nbsp; I think the rate measurement problem statement should iden=
tify &nbsp;burst testing as part of the problem since this is more and more=
 being added into the SLA (especially between providers, not so much for bu=
siness services yet)<o:p></o:p></p><p class=3DMsoListParagraph style=3D'mar=
gin-left:0in'><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>As noted in [RFC233=
0] the actual traffic handling may influence the rate measurement results f=
or some forms of access<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p=
></p><p class=3DMsoNormal>** Maybe a nit, but would it be better to say &#8=
220;traffic management&#8221; verus &#8220;traffic handling&#8221;?&nbsp; A=
lso, does this imply more broadly that QoS policy is applied to the user tr=
affic per the examples listed (packet length, IP addresses, etc)?&nbsp; If =
so, I would include DSCP in the list of examples since this is widely used =
and understood.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>Opportunistic In-Service testing when there is no user tr=
affic present throughout the test interval is essentially equivalent to Out=
-of-Service testing.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p><p class=3DMsoNormal>** Suggest:&nbsp; Opportunistic In-Service testing w=
hen there is no user traffic present throughout (i.e. after normal business=
 hours)<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3D=
MsoNormal>Section 3:<o:p></o:p></p><p class=3DMsoNormal>REPORTER:<o:p></o:p=
></p><p class=3DMsoNormal>Use information from test packets and local proce=
sses to measure delivered packet rates, and prepare results in the required=
 format.<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>** Should a sentence or two be added to clarify that the REPOR=
TER&nbsp; may be a separate test entity or may be embedded into the SENDER =
for example?<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p cla=
ss=3DMsoNormal>Section 4:<o:p></o:p></p><p class=3DMsoNormal>For all catego=
ries, the test protocol MUST support:<o:p></o:p></p><p class=3DMsoNormal><o=
:p>&nbsp;</o:p></p><p class=3DMsoNormal>d.&nbsp; Choice of UDP transport an=
d variable port numbers, OR, choice of<o:p></o:p></p><p class=3DMsoNormal>&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; TCP transport and variable port numbers=
 for two-way architectures<o:p></o:p></p><p class=3DMsoNormal>&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp; only, OR BOTH.<o:p></o:p></p><p class=3DMsoNormal><=
o:p>&nbsp;</o:p></p><p class=3DMsoNormal>**&nbsp; This implies TCP &#8220;s=
tateless&#8221; traffic per Mathis&#8217;s model-based work, right? <o:p></=
o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>e.&n=
bsp; Variable number of packets-pairs, ensembles, or streams used in a test=
 session<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=
=3DMsoNormal>** This should include VLAN or MPLS tagging, right?<o:p></o:p>=
</p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>Thank yo=
u,<o:p></o:p></p><p class=3DMsoNormal>Barry Constantine<o:p></o:p></p><p cl=
ass=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>JDSU Network and =
Service Enablement<o:p></o:p></p><p class=3DMsoNormal>Principal Member Tech=
nical Staff<o:p></o:p></p><p class=3DMsoNormal>301-325-7069<o:p></o:p></p><=
p class=3DMsoNormal><o:p>&nbsp;</o:p></p></div></div></body></html>=

--_000_2845723087023D4CB5114223779FA9C8AC527045njfpsrvexg8rese_--

From jsommers@colgate.edu  Thu Dec 12 08:27:33 2013
Return-Path: <jsommers@colgate.edu>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D46DE1ADDA0 for <ippm@ietfa.amsl.com>; Thu, 12 Dec 2013 08:27:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.599
X-Spam-Level: 
X-Spam-Status: No, score=-4.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xXuHSDDD6pOr for <ippm@ietfa.amsl.com>; Thu, 12 Dec 2013 08:27:31 -0800 (PST)
Received: from mail-ie0-f175.google.com (mail-ie0-f175.google.com [209.85.223.175]) by ietfa.amsl.com (Postfix) with ESMTP id ED2071A1F61 for <ippm@ietf.org>; Thu, 12 Dec 2013 08:27:30 -0800 (PST)
Received: by mail-ie0-f175.google.com with SMTP id x13so942779ief.34 for <ippm@ietf.org>; Thu, 12 Dec 2013 08:27:25 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:content-type:subject:message-id:date:to :mime-version; bh=FzFt7lkc1jiS0IK75BDUyWpIslvgoMbADm1aVh0rzXo=; b=drknEwnmnRi2o+PmxgUgDsVsgz78r7a1WKDolLH4wumC68hOZ8CO5c4NZ+yEyq7B2h LZj9NznLCoyVPNAEdV3dS7G2peiwxNGEu9eX4hcCUGks4H1G4WSFYx+UH7RiUxBTg2Eo I6mVquu1cu+F1akwOjOcZubQ2zNQM3sSLY8CgkZHx+8P7/0RIjTz3vXGX4t/A6eQ//uN gTgrH2fgZIKittX0QhcfM3PCfidS1bDjgBoxaCxZHrXSsnahhMVPO9cyqrp05KJsiZzv 5zM29Rl1bAyIIsjARLozQdlHs/umQJChqgKyYwWlKwsISRm4FpbAREXvLL+0kL/muizX dVtA==
X-Gm-Message-State: ALoCoQlx/IWI6f/fhlfc/+GZPNpmfijn1l0ppeiPx+mEbwjMCknsqjplzsi4mgpg8wEAsA5DoDqL
X-Received: by 10.42.89.18 with SMTP id e18mr7147463icm.42.1386865644575; Thu, 12 Dec 2013 08:27:24 -0800 (PST)
Received: from [10.0.1.7] (cpe-74-79-118-209.twcny.res.rr.com. [74.79.118.209]) by mx.google.com with ESMTPSA id qc5sm15744850igb.7.2013.12.12.08.27.22 for <ippm@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 12 Dec 2013 08:27:23 -0800 (PST)
From: Joel Sommers <jsommers@colgate.edu>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E6646D93-6992-4BA5-B8B7-05F0FF000BBE"
Message-Id: <643118E8-899C-43FC-B613-4B80777F1E1B@colgate.edu>
Date: Thu, 12 Dec 2013 11:27:21 -0500
To: ippm@ietf.org
Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
X-Mailer: Apple Mail (2.1822)
Subject: [ippm] CFP - Second NSF perfSONAR Workshop (pSW 2014)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 16:27:34 -0000

--Apple-Mail=_E6646D93-6992-4BA5-B8B7-05F0FF000BBE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=windows-1252

CFP - Second NSF perfSONAR Workshop (pSW 2014)

[Apologies if you got multiple copies of this email]

Second NSF Workshop on perfSONAR based Multi-domain Network Performance =
Measurement and Monitoring (pSW 2014)
Venue: National Science Foundation, Arlington, VA
Dates: 02/20/14 =96 02/21/14
Website: http://psW2014.wordpress.com

**Call for Participation (By Invitation Only)**

perfSONAR (http://www.perfsonar.net) is an infrastructure and a set of =
services for network performance monitoring, facilitating the ability to =
make and exchange performance measurements in order to: (a) solve =
end-to-end performance problems on paths crossing several networks, and =
(b) enable network-aware applications. There are over 700 publicly =
registered perfSONAR toolkit deployments worldwide, and the adoption is =
continuing to grow rapidly within data-intensive application =
communities.

The Second NSF-sponsored perfSONAR Workshop (pSW2014) will run from 9am =
February 20th to noon February 21st, 2014 at NSF, Arlington VA. The =
second workshop builds upon the success of the first workshop held 8-9 =
July 2010 in Arlington, VA, and is open to members of the network and =
system measurement community that includes a variety of stakeholders: =
researchers, applications developers, network operators, network =
managers, and others with an interest in network/system research and =
performance measurement/monitoring. The workshop aims to bring together =
these stakeholders for delivering targeted tutorials, talks sharing =
latest advances/demos from invited speakers, and fostering discussions =
to identify gaps that exist for solving prominent issues such as:

- Network measurement tools development and calibration
- Algorithms and Techniques for Automated Network Troubleshooting
- Architectures for Federated Measurement Collection, Analysis and =
Sharing
- Measurement Federation related Standards-development Efforts
- Monitoring of Software Defined, and Overlay Networks
- Measurement of Cloud and Grid Application Environments
- Security and Policy Considerations for Federated Measurements
- Case Studies of End-to-End Network/System Performance Troubleshooting
- Applications Integration and Deployment (e.g., network support use =
cases in Science DMZ, Cloud/HPC and BigData)

Participants who would like to present at the workshop are requested to =
send a presentation abstract along with a brief bio (in PDF format) to =
pSWkshp2014@gmail.com with the subject line as "<Speaker Name> =
Presentation Abstract". NSF-funded travel grants are available for =
speakers.
**Presentation Abstract Submission deadline: December 20, 2013**
**Acceptance notification: January 10, 2014**

Participants who would like to attend the workshop to contribute in the =
discussions should send a 1-Page description (in PDF format) of the =
intent to participate to pSWkshp2014@gmail.com with the subject line as =
"<Attendee Name> Intent Abstract". The description should include: (i) a =
brief bio, (ii) a set of challenges and opportunities relating to =
network/system performance measurement/monitoring that should be =
discussed in the workshop, and (iii) how your participation would add =
value to the workshop discussions.
**Intent Abstract Submission deadline: December 20, 2013**
**Invitation notification: January 10, 2014**
If travel support is needed, please follow instructions provided at - =
http://psw2014.wordpress.com/travel-support

We strongly encourage participation not only from current perfSONAR =
stakeholders, but also from potential stakeholders and research =
community members not previously involved in perfSONAR activities but =
are interested in joining and contributing to the perfSONAR community.=

--Apple-Mail=_E6646D93-6992-4BA5-B8B7-05F0FF000BBE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=windows-1252

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dwindows-1252"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div =
style=3D"font-family: Tahoma; font-size: 13px;">CFP - Second NSF =
perfSONAR Workshop (pSW 2014)</div><div style=3D"font-family: Tahoma; =
font-size: 13px;"><br></div><div style=3D"font-family: Tahoma; =
font-size: 13px;">[Apologies if you got multiple copies of this =
email]</div><div style=3D"font-family: Tahoma; font-size: =
13px;"><br></div><div style=3D"font-family: Tahoma; font-size: =
13px;">Second NSF Workshop on perfSONAR based Multi-domain Network =
Performance Measurement and Monitoring (pSW 2014)</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">Venue: National Science =
Foundation, Arlington, VA</div><div style=3D"font-family: Tahoma; =
font-size: 13px;">Dates: 02/20/14 =96 02/21/14</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">Website:&nbsp;<a =
href=3D"http://psW2014.wordpress.com">http://psW2014.wordpress.com</a></di=
v><div style=3D"font-family: Tahoma; font-size: 13px;"><br></div><div =
style=3D"font-family: Tahoma; font-size: 13px;">**Call for Participation =
(By Invitation Only)**</div><div style=3D"font-family: Tahoma; =
font-size: 13px;"><br></div><div style=3D"font-family: Tahoma; =
font-size: 13px;">perfSONAR (<a =
href=3D"http://www.perfsonar.net">http://www.perfsonar.net</a>) is an =
infrastructure and a set of services for network performance monitoring, =
facilitating the ability to make and exchange performance measurements =
in order to: (a) solve end-to-end performance problems on paths crossing =
several networks, and (b) enable network-aware applications. There are =
over 700 publicly registered perfSONAR toolkit deployments worldwide, =
and the adoption is continuing to grow rapidly within data-intensive =
application communities.</div><div style=3D"font-family: Tahoma; =
font-size: 13px;"><br></div><div style=3D"font-family: Tahoma; =
font-size: 13px;">The Second NSF-sponsored perfSONAR Workshop (pSW2014) =
will run from 9am February 20th to noon February 21st, 2014 at NSF, =
Arlington VA. The second workshop builds upon the success of the first =
workshop held 8-9 July 2010 in Arlington, VA, and is open to members of =
the network and system measurement community that includes a variety of =
stakeholders: researchers, applications developers, network operators, =
network managers, and others with an interest in network/system research =
and performance measurement/monitoring. The workshop aims to bring =
together these stakeholders for delivering targeted tutorials, talks =
sharing latest advances/demos from invited speakers, and fostering =
discussions to identify gaps that exist for solving prominent issues =
such as:</div><div style=3D"font-family: Tahoma; font-size: =
13px;"><br></div><div style=3D"font-family: Tahoma; font-size: 13px;">- =
Network measurement tools development and calibration</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">- Algorithms and =
Techniques for Automated Network Troubleshooting</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">- Architectures for =
Federated Measurement Collection, Analysis and Sharing</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">- Measurement Federation =
related Standards-development Efforts</div><div style=3D"font-family: =
Tahoma; font-size: 13px;">- Monitoring of Software Defined, and Overlay =
Networks</div><div style=3D"font-family: Tahoma; font-size: 13px;">- =
Measurement of Cloud and Grid Application Environments</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">- Security and Policy =
Considerations for Federated Measurements</div><div style=3D"font-family: =
Tahoma; font-size: 13px;">- Case Studies of End-to-End Network/System =
Performance Troubleshooting</div><div style=3D"font-family: Tahoma; =
font-size: 13px;">- Applications Integration and Deployment (e.g., =
network support use cases in Science DMZ, Cloud/HPC and =
BigData)</div><div style=3D"font-family: Tahoma; font-size: =
13px;"><br></div><div style=3D"font-family: Tahoma; font-size: =
13px;">Participants who would like to present at the workshop are =
requested to send a presentation abstract along with a brief bio (in PDF =
format) to&nbsp;<a =
href=3D"mailto:pSWkshp2014@gmail.com">pSWkshp2014@gmail.com</a>&nbsp;with =
the subject line as "&lt;Speaker Name&gt; Presentation Abstract". =
NSF-funded travel grants are available for speakers.</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">**Presentation Abstract =
Submission deadline: December 20, 2013**</div><div style=3D"font-family: =
Tahoma; font-size: 13px;">**Acceptance notification: January 10, =
2014**</div><div style=3D"font-family: Tahoma; font-size: =
13px;"><br></div><div style=3D"font-family: Tahoma; font-size: =
13px;">Participants who would like to attend the workshop to contribute =
in the discussions should send a 1-Page description (in PDF format) of =
the intent to participate to&nbsp;<a =
href=3D"mailto:pSWkshp2014@gmail.com">pSWkshp2014@gmail.com</a>&nbsp;with =
the subject line as "&lt;Attendee Name&gt; Intent Abstract". The =
description should include: (i) a brief bio, (ii) a set of challenges =
and opportunities relating to network/system performance =
measurement/monitoring that should be discussed in the workshop, and =
(iii) how your participation would add value to the workshop =
discussions.</div><div style=3D"font-family: Tahoma; font-size: =
13px;">**Intent Abstract Submission deadline: December 20, =
2013**</div><div style=3D"font-family: Tahoma; font-size: =
13px;">**Invitation notification: January 10, 2014**</div><div =
style=3D"font-family: Tahoma; font-size: 13px;">If travel support is =
needed, please follow instructions provided at -&nbsp;<a =
href=3D"http://psw2014.wordpress.com/travel-support">http://psw2014.wordpr=
ess.com/travel-support</a></div><div style=3D"font-family: Tahoma; =
font-size: 13px;"><br></div><div style=3D"font-family: Tahoma; =
font-size: 13px;">We strongly encourage participation not only from =
current perfSONAR stakeholders, but also from potential stakeholders and =
research community members not previously involved in perfSONAR =
activities but are interested in joining and contributing to the =
perfSONAR community.</div></body></html>=

--Apple-Mail=_E6646D93-6992-4BA5-B8B7-05F0FF000BBE--

From a.botta@unina.it  Sun Dec 15 03:23:23 2013
Return-Path: <a.botta@unina.it>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B4DB91ADF47 for <ippm@ietfa.amsl.com>; Sun, 15 Dec 2013 03:23:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.678
X-Spam-Level: ***
X-Spam-Status: No, score=3.678 tagged_above=-999 required=5 tests=[BAYES_50=0.8, GB_AFFORDABLE=1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id u1W4VxAqtIDg for <ippm@ietfa.amsl.com>; Sun, 15 Dec 2013 03:23:20 -0800 (PST)
Received: from smtp1.unina.it (smtp1.unina.it [192.132.34.61]) by ietfa.amsl.com (Postfix) with ESMTP id 80FA31ADF23 for <ippm@ietf.org>; Sun, 15 Dec 2013 03:23:19 -0800 (PST)
Received: from [192.168.1.16] ([151.70.109.206]) (authenticated bits=0) by smtp1.unina.it (8.14.4/8.14.4) with ESMTP id rBFBNAmK005557 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ippm@ietf.org>; Sun, 15 Dec 2013 12:23:10 +0100
Message-ID: <52AD911E.6070903@unina.it>
Date: Sun, 15 Dec 2013 12:23:10 +0100
From: Alessio Botta <a.botta@unina.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: ippm@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [ippm] TRICANS 2014 - Deadline extended - 2nd IEEE Workshop on Traffic Identification and Classification for Advanced Network Services and Scenarios (TRICANS) ICC 2014 Workshop
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 15 Dec 2013 11:23:23 -0000

[Our apologies if you receive multiple copies of this CFP]

The deadline for paper submission has been extended!
The new paper submission deadline on EDAS is 31 December 2013.
This deadline is firm!

----------------------------------------------------------------------------
CALL FOR PAPER 2nd IEEE Workshop on Traffic Identification and 
Classification for Advanced Network Services and Scenarios (TRICANS)
ICC 2014 Workshop
Sidney - 14 June 2014
----------------------------------------------------------------------------

2nd IEEE Workshop on Traffic Identification and Classification for 
Advanced Network Services and Scenarios (TRICANS) - ICC 2014 Workshop
http://www.grid.unina.it/TRICANS2014

*** Scope and Topics of Interest ***
The 2014 IEEE ICC TRICANS Workshop will provide an excellent 
international forum for sharing state-of-the-art advances and 
experiences in scientific research on Internet traffic identification 
and classification and their associated applications on advanced network 
scenarios and novel network services. TRICANS 2014 will explicitly 
consider traffic identification and classification as well as management 
issues related to novel and very challenging scenarios, such as Software 
Defined Networking (SDN). The 2014 IEEE International Conference on 
Communications (ICC) will be held in the beautiful city of Sydney, 
Australia from 10-14 June 2014. Themed "Communications: The Centrepoint 
of the Digital Economy," this flagship conference of IEEE Communications 
Society will feature a comprehensive technical program including twelve 
Symposia and a number of Tutorials and Workshops. IEEE ICC 2014 will 
also include an exceptional expo program including keynote speakers and 
an Industry Forum & Exhibition. IEEE ICC is one of the flagship 
conferences of the IEEE Communications Society and it attracts about 
2-3.000 submitted scientific papers. IEEE ICC is therefore one of the 
most significant scientific events of the networking and communications 
community with a great visibility for published papers.
The ever-growing network link speeds have reached hundreds of Gbps and 
they are quickly approaching to Tbps in the core network. In order to 
support accurate network profiling of users and services, ISPs have been 
relying on Deep Packet Inspection (DPI), computational intelligence 
techniques, or other behavioral analysis of the Internet traffic. 
However, there are still a number of challenges in this field. On one 
hand, new networked applications come daily into play bringing massive 
amounts of traffic data to be processed in real-time. Such traffic 
volume keeps pushing industry and academia researchers to develop 
affordable yet efficient traffic identification and classification 
systems. To this end, there are demands for high-performance distributed 
and parallel traffic classification systems for either commodity or 
special-purposed hardware platforms. Dealing with encrypted traffic is 
of particular interest and is also very challenging. On the other hand, 
in the long-term, such solutions for traffic profiling will become part 
of the network management tools and techniques portfolio available for 
advanced network services. Also, new architectures and their supporting 
technologies, such as SDN, information- and content-centric networking 
architectures will require network profiling services to enable robust 
and dynamic networking services capabilities.
To address these research challenges, this workshop will focus on 
theory, tools, techniques, and applications of traffic identification 
and classification systems to enable advanced support for 
next-generation networking architectures, services, and scenarios. The 
topics covered by the workshop include, but are not limited to, the 
following:
- Measurement and modelling of Internet traffic for advanced networked 
services
- Network and system troubleshooting through traffic classification 
mechanisms
- Network profiling of users and networked applications
- Security and privacy in traffic identification and classification 
mechanisms
- Lightweight technologies for DPI in routers and middle-boxes
- DPI technologies support for virtual networks and cloud computing 
management
- Profiling network traffic in data center networks and cloud computing 
systems
- Inferring and assessing Quality of Experience (QoE) of users and services
- Novel visualization techniques for traffic classification and analysis
- Packet processing support in operating systems for novel line-rate 
network services
- Management of large network traffic data sets
- SDN approaches for network performance monitoring
- Traffic classification in SDN network elements and controllers

*** Submission Guidelines ***
Prospective authors are encouraged to submit a full paper (5 pages) for 
review. Only original papers that have not been published or submitted 
for publication elsewhere will be considered. Submit your papers through 
EDAS. These submissions should follow the IEEE ICC 2014 formatting 
guidelines, templates for which are available at the main conference web 
page. The maximum paper length is of five (5) pages.

*** Important Dates ***
31 December 2013 (extended, firm): Paper submission deadline on EDAS
30 January 2014: Reviews Completed
20 February 2014: Paper Acceptance Notification
15 March 2014: Camera Ready copies submitted.
Workshop date: 14 June 2014

*** Workshop General Chairs ***
Stenio Fernandes, Federal University of Pernambuco, Recife, Brazil
Antonio Pescapé, University of Napoli ''Federico II'', Napoli, Italy
Géza Szabó, Ericsson Traffic Laboratory, Budapest, Hungary

*** Publicity Chair ***
Alessio Botta, University of Napoli ''Federico II'', Napoli, Italy

*** Technical Program Committee ***
Alberto Dainotti, CAIDA, USA
Alessio Botta, University of Napoli Federico II
Artur Ziviani, LNCC, Brazil
Carlos Kamienski, UFABC, Brazil
Djamel Sadok, UFPE, Brazil
Domenico Ficara, University of Pisa, Italy
Fabian Schneider, NEC Lab
Istvan Godor, Ericsson, Hungary
Jason Zurawski, Energy Sciences Network (ESnet), USA
José Augusto Suruagy, UFPE, Brazil
Hyun-chul Kim, Seoul National University, South Korea
László Toka, Ericsson, Hungary
Maurizio Dusi, NEC, Germany
Marco Mellia, Polito, Italy
Marinho Barcelos, UFRGS, Brazil
Myung-Sup Kim, Korea University
Nur Zincir-Heywood, Dalhousie University, Canada
Philippe Owezarski, CNRS, France
Rafael Antonello, Federal Institute of Technology (AL), Brazil
Sándor Molnár, Budapest University of Technology and Economics,, Hungary
Youngjoon Won, Korea University

*** Workshop website address ***
http://www.grid.unina.it/TRICANS2014
----------------------------------------------------------------------------

-- 
Alessio Botta, PhD
Dipartimento di Ingegneria Elettrica e delle Tecnologie dell'Informazione
Università degli Studi di Napoli "Federico II"
Via Claudio 21 -- 80125 Napoli (Italy) [Room 3.09]
Phone: +390817683865 - Fax: +390817683816
Skypeid: alessiobotta
Email: a.botta@unina.it
alessio.botta@consorzio-cini.it
WWW: http://wpage.unina.it/a.botta





From a.botta@unina.it  Fri Dec 27 05:10:43 2013
Return-Path: <a.botta@unina.it>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 14BB31AE0F7 for <ippm@ietfa.amsl.com>; Fri, 27 Dec 2013 05:10:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.841
X-Spam-Level: ***
X-Spam-Status: No, score=3.841 tagged_above=-999 required=5 tests=[BAYES_60=1.5, GB_AFFORDABLE=1, HELO_EQ_IT=0.635, HOST_EQ_IT=1.245, RP_MATCHES_RCVD=-0.538, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SlkFxLGfUbEr for <ippm@ietfa.amsl.com>; Fri, 27 Dec 2013 05:10:40 -0800 (PST)
Received: from smtp2.unina.it (smtp2.unina.it [192.132.34.62]) by ietfa.amsl.com (Postfix) with ESMTP id B471C1ADE72 for <ippm@ietf.org>; Fri, 27 Dec 2013 05:10:39 -0800 (PST)
Received: from [192.168.1.16] ([151.70.23.3]) (authenticated bits=0) by smtp2.unina.it (8.14.4/8.14.4) with ESMTP id rBRDAWkU030357 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <ippm@ietf.org>; Fri, 27 Dec 2013 14:10:33 +0100
Message-ID: <52BD7C48.3000803@unina.it>
Date: Fri, 27 Dec 2013 14:10:32 +0100
From: Alessio Botta <a.botta@unina.it>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ippm@ietf.org
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: [ippm] TRICANS 2014 - Deadline approaching - 2nd IEEE Workshop on Traffic Identification and Classification for Advanced Network Services and Scenarios (TRICANS) ICC 2014 Workshop
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Dec 2013 13:10:43 -0000

Dear Colleagues,

please note that the deadline for paper submission is approaching fast.
The paper submission deadline on EDAS is on the 31st and is firm.

The call for paper follows.

[Our apologies if you receive multiple copies of this CFP]

----------------------------------------------------------------------------
CALL FOR PAPER 2nd IEEE Workshop on Traffic Identification and 
Classification for Advanced Network Services and Scenarios (TRICANS)
ICC 2014 Workshop
Sydney - 14 June 2014
----------------------------------------------------------------------------

2nd IEEE Workshop on Traffic Identification and Classification for 
Advanced Network Services and Scenarios (TRICANS) - ICC 2014 Workshop
http://www.grid.unina.it/TRICANS2014

*** Scope and Topics of Interest ***
The 2014 IEEE ICC TRICANS Workshop will provide an excellent 
international forum for sharing state-of-the-art advances and 
experiences in scientific research on Internet traffic identification 
and classification and their associated applications on advanced network 
scenarios and novel network services. TRICANS 2014 will explicitly 
consider traffic identification and classification as well as management 
issues related to novel and very challenging scenarios, such as Software 
Defined Networking (SDN). The 2014 IEEE International Conference on 
Communications (ICC) will be held in the beautiful city of Sydney, 
Australia from 10-14 June 2014. Themed "Communications: The Centrepoint 
of the Digital Economy," this flagship conference of IEEE Communications 
Society will feature a comprehensive technical program including twelve 
Symposia and a number of Tutorials and Workshops. IEEE ICC 2014 will 
also include an exceptional expo program including keynote speakers and 
an Industry Forum & Exhibition. IEEE ICC is one of the flagship 
conferences of the IEEE Communications Society and it attracts about 
2-3.000 submitted scientific papers. IEEE ICC is therefore one of the 
most significant scientific events of the networking and communications 
community with a great visibility for published papers.
The ever-growing network link speeds have reached hundreds of Gbps and 
they are quickly approaching to Tbps in the core network. In order to 
support accurate network profiling of users and services, ISPs have been 
relying on Deep Packet Inspection (DPI), computational intelligence 
techniques, or other behavioral analysis of the Internet traffic. 
However, there are still a number of challenges in this field. On one 
hand, new networked applications come daily into play bringing massive 
amounts of traffic data to be processed in real-time. Such traffic 
volume keeps pushing industry and academia researchers to develop 
affordable yet efficient traffic identification and classification 
systems. To this end, there are demands for high-performance distributed 
and parallel traffic classification systems for either commodity or 
special-purposed hardware platforms. Dealing with encrypted traffic is 
of particular interest and is also very challenging. On the other hand, 
in the long-term, such solutions for traffic profiling will become part 
of the network management tools and techniques portfolio available for 
advanced network services. Also, new architectures and their supporting 
technologies, such as SDN, information- and content-centric networking 
architectures will require network profiling services to enable robust 
and dynamic networking services capabilities.
To address these research challenges, this workshop will focus on 
theory, tools, techniques, and applications of traffic identification 
and classification systems to enable advanced support for 
next-generation networking architectures, services, and scenarios. The 
topics covered by the workshop include, but are not limited to, the 
following:
- Measurement and modelling of Internet traffic for advanced networked 
services
- Network and system troubleshooting through traffic classification 
mechanisms
- Network profiling of users and networked applications
- Security and privacy in traffic identification and classification 
mechanisms
- Lightweight technologies for DPI in routers and middle-boxes
- DPI technologies support for virtual networks and cloud computing 
management
- Profiling network traffic in data center networks and cloud computing 
systems
- Inferring and assessing Quality of Experience (QoE) of users and services
- Novel visualization techniques for traffic classification and analysis
- Packet processing support in operating systems for novel line-rate 
network services
- Management of large network traffic data sets
- SDN approaches for network performance monitoring
- Traffic classification in SDN network elements and controllers

*** Submission Guidelines ***
Prospective authors are encouraged to submit a full paper (5 pages) for 
review. Only original papers that have not been published or submitted 
for publication elsewhere will be considered. Submit your papers through 
EDAS. These submissions should follow the IEEE ICC 2014 formatting 
guidelines, templates for which are available at the main conference web 
page. The maximum paper length is of five (5) pages.

*** Important Dates ***
31 December 2013 (extended, firm): Paper submission deadline on EDAS
30 January 2014: Reviews Completed
20 February 2014: Paper Acceptance Notification
15 March 2014: Camera Ready copies submitted.
Workshop date: 14 June 2014

*** Workshop General Chairs ***
Stenio Fernandes, Federal University of Pernambuco, Recife, Brazil
Antonio Pescapé, University of Napoli ''Federico II'', Napoli, Italy
Géza Szabó, Ericsson Traffic Laboratory, Budapest, Hungary

*** Publicity Chair ***
Alessio Botta, University of Napoli ''Federico II'', Napoli, Italy

*** Technical Program Committee ***
Alberto Dainotti, CAIDA, USA
Alessio Botta, University of Napoli Federico II
Artur Ziviani, LNCC, Brazil
Carlos Kamienski, UFABC, Brazil
Djamel Sadok, UFPE, Brazil
Domenico Ficara, University of Pisa, Italy
Fabian Schneider, NEC Lab
Istvan Godor, Ericsson, Hungary
Jason Zurawski, Energy Sciences Network (ESnet), USA
José Augusto Suruagy, UFPE, Brazil
Hyun-chul Kim, Seoul National University, South Korea
László Toka, Ericsson, Hungary
Maurizio Dusi, NEC, Germany
Marco Mellia, Polito, Italy
Marinho Barcelos, UFRGS, Brazil
Myung-Sup Kim, Korea University
Nur Zincir-Heywood, Dalhousie University, Canada
Philippe Owezarski, CNRS, France
Rafael Antonello, Federal Institute of Technology (AL), Brazil
Sándor Molnár, Budapest University of Technology and Economics,, Hungary
Youngjoon Won, Korea University

*** Workshop website address ***
http://www.grid.unina.it/TRICANS2014
----------------------------------------------------------------------------

-- 
Alessio Botta, PhD
Dipartimento di Ingegneria Elettrica e delle Tecnologie dell'Informazione
Università degli Studi di Napoli "Federico II"
Via Claudio 21 -- 80125 Napoli (Italy) [Room 3.09]
Phone: +390817683865 - Fax: +390817683816
Skypeid: alessiobotta
Email: a.botta@unina.it
alessio.botta@consorzio-cini.it
WWW: http://wpage.unina.it/a.botta





From Anura.Jayasumana@ColoState.edu  Fri Dec 27 07:48:57 2013
Return-Path: <Anura.Jayasumana@ColoState.edu>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C65A1AE20E for <ippm@ietfa.amsl.com>; Fri, 27 Dec 2013 07:48:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.263
X-Spam-Level: 
X-Spam-Status: No, score=0.263 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PLStWlwhCG1f for <ippm@ietfa.amsl.com>; Fri, 27 Dec 2013 07:48:54 -0800 (PST)
Received: from bird.ColoState.EDU (spamcanner.colostate.edu [129.82.103.165]) by ietfa.amsl.com (Postfix) with ESMTP id 504DC1ADF69 for <ippm@ietf.org>; Fri, 27 Dec 2013 07:48:54 -0800 (PST)
Received: from jansen.ColoState.EDU (jansen.colostate.edu [129.82.103.132]) by bird.ColoState.EDU (8.13.8/8.12.11) with ESMTP id rBRFgieb007655; Fri, 27 Dec 2013 08:42:44 -0700
Received: from mail1.engr.colostate.edu (mail1.engr.colostate.edu [129.82.20.31]) by jansen.ColoState.EDU (8.13.1/8.13.1) with ESMTP id rBRFmQrB026082; Fri, 27 Dec 2013 08:48:26 -0700
Received: from [129.82.23.180] (unknown [129.82.23.180]) by mail1.engr.colostate.edu (Postfix) with ESMTPSA id EA4B142B; Fri, 27 Dec 2013 08:48:25 -0700 (MST)
Message-ID: <52BDA150.7070901@ColoState.edu>
Date: Fri, 27 Dec 2013 08:48:32 -0700
From: Anura Jayasumana <Anura.Jayasumana@ColoState.edu>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0
MIME-Version: 1.0
To: ippm@ietf.org
References: <52BD1B64.3010602@ColoState.edu>
In-Reply-To: <52BD1B64.3010602@ColoState.edu>
X-Forwarded-Message-Id: <52BD1B64.3010602@ColoState.edu>
Content-Type: multipart/alternative; boundary="------------070301020702090405010205"
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.87, 1.0.14, 0.0.0000 definitions=2013-12-27_04:2013-12-27,2013-12-27,1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 suspectscore=1 phishscore=0 adultscore=0 bulkscore=95 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1312270085
Subject: [ippm] Call for papers - IEEE SDN Architecture and Applications 2014
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Anura.Jayasumana@ColoState.edu
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Dec 2013 15:48:57 -0000

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


                      CALL FOR PAPERS

IEEE SDN Architecture and Applications 2014
1st IEEE WoWMoM Workshop on Software Defined Networking Architecture and
Applications

www.cnrl.colostate.edu/sdnwmom2014/ 
<http://www.cnrl.colostate.edu/sdnwmom2014/>

To be held in conjunction with IEEE WoWMoM 2014

June 16, 2014 - Sydney, Australia

Submission Deadline March 7, 2014

In recent years SDN (Software Defined Networking) has emerged as an
exciting area of research which is challenging the  current networking
paradigm of designing and managing computer networks.  SDN has the
potential to revolutionize not only the way networks are built but can
lead to emergence of new applications that were not hitherto possible.
This workshop is aimed at providing a platform for researchers and
practitioners to share their learnings and latest research results in
this emerging area and its novel applications.  We solicit  papers with
focus on theory and empirical data that would demonstrate significant
advancement in the state of the art and stimulate research in broad
areas of SDN and its applications. Authors can consider submitting
papers  in following areas but are not limited to:

SDN Controller Architecture
Network Virtualization and Abstraction for SDN
SDN Application Development for wireless, mobile and multimedia networks
SDN applications in Data Centers, enterprise and Service Provider
Networks
Advancement in South-bound APIs for network programming
Advancement in North-bound APIs for application programming.
Co-existence of SDN and traditional networks
Security in SDN networks
Performance Analysis of single and multi-controller architectures
Theoretical foundation of separation of control and data plane
architecture
Tools for Management and Troubleshooting of SDN based networks
Application-aware network design using SDN
Virtualization of Wireless and Mobile network services to enable
programmability
Robust protocols for controller to network element and network element
to controller communication in wireless/mobile environment

PAPER SUBMISSION AND PUBLICATION

Papers should neither have been published elsewhere nor being currently
under review by another conference or journal. Manuscripts are limited
to 6 pages, single spacing, double column, and must strictly adhere to
the template format.  Accepted papers will appear in the symposium
proceedings published by IEEE. There will be no separate workshop
registration, as one single registration will cover both conference and
workshops participation. At least one author of each accepted paper is
required and present his/her work at the workshop.

IMPORTANT DATES

Full papers due:          March 7, 2014

Notification:             April 15, 2014

Workshop:                 June 16, 2014

ORGANIZING COMMITTEE

Workshop Chairs:

Tarun Banka,                  Cisco Systems, San Jose, CA
Anura Jayasumana,       Colorado State University,  Fort Collins, CO

TPC Committee:

Eric Keller                University of Colorado, Boulder, CO, USA
Swades De               Indian Institute of Technology, New Delhi, India
Nischal Piratla      Xerox Research Center, Bangalore, India
David Meyer          Brocade Systems, USA
Adrian Farrel        Juniper Networks and Old Dog Consulting, USA
                                 IETF Routing Area Director
Manoj Pandey     Cisco Systems, CA, USA
Angela Nicoara    Deutsche Telekom Innovation Laboratories, CA, USA
Eddie Ruan           Cisco Systems, CA, USA
Petros Zerfos       IBM T.J. Watson Research Center, USA
Cristian Lumezanu   NEC-Labs, Princeton, NJ, USA
Mohamed El Gendy  Ericsson,  CA,  USA.

---------------------------------------------------------------------------- 



--------------070301020702090405010205
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <br>
    <div class="moz-forward-container"> <tt>Â  Â  Â  Â  Â  Â  Â  Â  Â  Â Â  CALL
        FOR PAPERS</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> IEEE SDN Architecture and Applications 2014</tt><tt><br>
      </tt><tt> 1st IEEE WoWMoM Workshop on Software Defined Networking
        Architecture and</tt><tt><br>
      </tt><tt> Applications</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Â  Â  Â  Â  Â  Â  Â  Â  Â </tt><tt><a moz-do-not-send="true"
          href="http://www.cnrl.colostate.edu/sdnwmom2014/"
          target="_blank">www.cnrl.colostate.edu/sdnwmom2014/</a></tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> To be held in conjunction with IEEE WoWMoM 2014</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> June 16, 2014 - Sydney, Australia</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Submission Deadline March 7, 2014</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> In recent years SDN (Software Defined Networking) has
        emerged as an</tt><tt><br>
      </tt><tt> exciting area of research which is challenging the
        Â current networking</tt><tt><br>
      </tt><tt> paradigm of designing and managing computer networks.
        Â SDN has the</tt><tt><br>
      </tt><tt> potential to revolutionize not only the way networks are
        built but can</tt><tt><br>
      </tt><tt> lead to emergence of new applications that were not
        hitherto possible.</tt><tt><br>
      </tt><tt> This workshop is aimed at providing a platform for
        researchers and</tt><tt><br>
      </tt><tt> practitioners to share their learnings and latest
        research results in</tt><tt><br>
      </tt><tt> this emerging area and its novel applications. Â We
        solicit Â papers with</tt><tt><br>
      </tt><tt> focus on theory and empirical data that would
        demonstrate significant</tt><tt><br>
      </tt><tt> advancement in the state of the art and stimulate
        research in broad</tt><tt><br>
      </tt><tt> areas of SDN and its applications. Authors can consider
        submitting</tt><tt><br>
      </tt><tt> papers Â in following areas but are not limited to:</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> SDN Controller Architecture</tt><tt><br>
      </tt><tt> Network Virtualization and Abstraction for SDN</tt><tt><br>
      </tt><tt> SDN Application Development for wireless, mobile and
        multimedia networks</tt><tt><br>
      </tt><tt> SDN applications in Data Centers, enterprise and Service
        Provider</tt><tt><br>
      </tt><tt> Networks</tt><tt><br>
      </tt><tt> Advancement in South-bound APIs for network programming</tt><tt><br>
      </tt><tt> Advancement in North-bound APIs for application
        programming.</tt><tt><br>
      </tt><tt> Co-existence of SDN and traditional networks</tt><tt><br>
      </tt><tt> Security in SDN networks</tt><tt><br>
      </tt><tt> Performance Analysis of single and multi-controller
        architectures</tt><tt><br>
      </tt><tt> Theoretical foundation of separation of control and data
        plane</tt><tt><br>
      </tt><tt> architecture</tt><tt><br>
      </tt><tt> Tools for Management and Troubleshooting of SDN based
        networks</tt><tt><br>
      </tt><tt> Application-aware network design using SDN</tt><tt><br>
      </tt><tt> Virtualization of Wireless and Mobile network services
        to enable</tt><tt><br>
      </tt><tt> programmability</tt><tt><br>
      </tt><tt> Robust protocols for controller to network element and
        network element</tt><tt><br>
      </tt><tt> to controller communication in wireless/mobile
        environment</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> PAPER SUBMISSION AND PUBLICATION</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Papers should neither have been published elsewhere nor
        being currently</tt><tt><br>
      </tt><tt> under review by another conference or journal.
        Manuscripts are limited</tt><tt><br>
      </tt><tt> to 6 pages, single spacing, double column, and must
        strictly adhere to</tt><tt><br>
      </tt><tt> the template format. Â Accepted papers will appear in the
        symposium</tt><tt><br>
      </tt><tt> proceedings published by IEEE. There will be no separate
        workshop</tt><tt><br>
      </tt><tt> registration, as one single registration will cover both
        conference and</tt><tt><br>
      </tt><tt> workshops participation. At least one author of each
        accepted paper is</tt><tt><br>
      </tt><tt> required and present his/her work at the workshop.</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> IMPORTANT DATES</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Full papers due: Â  Â  Â  Â  Â March 7, 2014</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Notification: Â  Â  Â  Â  Â  Â  April 15, 2014</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Workshop: Â  Â  Â  Â  Â  Â  Â  Â  June 16, 2014</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> ORGANIZING COMMITTEE</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Workshop Chairs:</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Tarun Banka, Â  Â  Â  Â  Â  Â Â Â Â Â Â Â Cisco Systems, San Jose,
        CA</tt><tt><br>
      </tt><tt> Anura Jayasumana, Â  Â  Â  Colorado State University, Â Fort
        Collins, CO</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> TPC Committee:</tt><tt><br>
      </tt><tt> </tt><tt><br>
      </tt><tt> Eric Keller Â  Â  Â Â Â Â Â Â Â Â Â  Â University of Colorado,
        Boulder, CO, USA</tt><tt><br>
      </tt><tt> Swades De Â  Â  Â  Â Â Â Â Â Â  Â Indian Institute of Technology,
        New Delhi, India</tt><tt><br>
      </tt><tt> Nischal Piratla Â Â Â  Â Xerox Research Center, Bangalore,
        India</tt><tt><br>
      </tt><tt> David Meyer Â  Â  Â  Â Â Â Brocade Systems, USA</tt><tt><br>
      </tt><tt> Adrian Farrel Â  Â  Â Â Â Juniper Networks and Old Dog
        Consulting, USA</tt><tt><br>
      </tt><tt> Â  Â  Â  Â  Â  Â  Â  Â  Â Â Â Â Â Â Â Â Â Â Â Â Â Â  Â IETF Routing Area
        Director</tt><tt><br>
      </tt><tt> Manoj Pandey Â  Â  Cisco Systems, CA, USA</tt><tt><br>
      </tt><tt> Angela Nicoara Â  Â Deutsche Telekom Innovation
        Laboratories, CA, USA</tt><tt><br>
      </tt><tt> Eddie Ruan Â  Â  Â Â Â  Â Â Cisco Systems, CA, USA</tt><tt><br>
      </tt><tt> Petros Zerfos Â  Â  Â Â IBM T.J. Watson Research Center, USA</tt><tt><br>
      </tt><tt> Cristian LumezanuÂ  Â NEC-Labs, Princeton, NJ, USA</tt><tt><br>
      </tt><tt> Mohamed El Gendy Â Ericsson, Â CA, Â USA.</tt><o:p></o:p><br>
      <br>
      ----------------------------------------------------------------------------

      <br>
    </div>
    <br>
  </body>
</html>

--------------070301020702090405010205--
