From henk@ripe.net Tue Feb 17 05:54:18 2009 Return-Path: X-Original-To: ippm@core3.amsl.com Delivered-To: ippm@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2B2583A6949 for ; Tue, 17 Feb 2009 05:54:18 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -5.299 X-Spam-Level: X-Spam-Status: No, score=-5.299 tagged_above=-999 required=5 tests=[AWL=-5.300, BAYES_50=0.001] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MNPgbLFtRgLH for ; Tue, 17 Feb 2009 05:54:17 -0800 (PST) Received: from postlady.ripe.net (postlady.ripe.net [193.0.19.65]) by core3.amsl.com (Postfix) with ESMTP id 327A93A63D3 for ; Tue, 17 Feb 2009 05:54:17 -0800 (PST) Received: from herring.ripe.net ([193.0.1.203]) by postlady.ripe.net with esmtp (Exim 4.63) (envelope-from ) id 1LZQOn-0007gj-UN for ippm@ietf.org; Tue, 17 Feb 2009 14:54:10 +0100 Received: from geir.local (gw.office.nsrp.ripe.net [193.0.1.126]) by herring.ripe.net (Postfix) with ESMTP id D8D2F2F583 for ; Tue, 17 Feb 2009 14:54:09 +0100 (CET) Message-ID: <499AC181.7010009@ripe.net> Date: Tue, 17 Feb 2009 14:54:09 +0100 From: Henk Uijterwaal User-Agent: Thunderbird 2.0.0.19 (Macintosh/20081209) MIME-Version: 1.0 To: "ippm >> IETF IPPM WG" References: <497EDBC7.8080908@ripe.net> In-Reply-To: <497EDBC7.8080908@ripe.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-RIPE-Spam-Level: ---- X-RIPE-Signature: e0cdef1f45f89a40ad608d255b27e7d57ba0a3cffbc374c0975c4e1eef448ef6 Subject: Re: [ippm] Getting ready for San Fransisco X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 17 Feb 2009 13:54:18 -0000 IPPM group, > We're about 2 months away from our next meeting in San Fransisco, which > means that now is the time to start preparing it. A month has passed... We have a meeting slot in SF (Tuesday afternoon), so: > 1. If you want to present something in SF, please send us a note and > we'll put you on the agenda. > > 2. Our new charter will probably be approved in the next weeks or so. > There > is consensus about the text. That means that we are ready to accept > drafts > under the new charter. If you do plan to write a draft, please let us > know. Include title, authors, ETA for the first and final versions, > etc. It has been approved, so if you want to submit a draft under the new charter, please go ahead. Henk ------------------------------------------------------------------------------ Henk Uijterwaal Email: henk.uijterwaal(at)ripe.net RIPE Network Coordination Centre http://www.amsterdamned.org/~henk P.O.Box 10096 Singel 258 Phone: +31.20.5354414 1001 EB Amsterdam 1016 AB Amsterdam Fax: +31.20.5354445 The Netherlands The Netherlands Mobile: +31.6.55861746 ------------------------------------------------------------------------------ Belgium: an unsolvable problem, discussed in endless meetings, with no hope for a solution, where everybody still lives happily. From acmorton@att.com Fri Feb 20 13:17:36 2009 Return-Path: X-Original-To: ippm@core3.amsl.com Delivered-To: ippm@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 641CC3A6AD0 for ; Fri, 20 Feb 2009 13:17:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.796 X-Spam-Level: X-Spam-Status: No, score=-105.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qEVTZBxMoJog for ; Fri, 20 Feb 2009 13:17:35 -0800 (PST) Received: from mail146.messagelabs.com (mail146.messagelabs.com [216.82.241.147]) by core3.amsl.com (Postfix) with ESMTP id BF28C3A69E5 for ; Fri, 20 Feb 2009 13:17:34 -0800 (PST) X-VirusChecked: Checked X-Env-Sender: acmorton@att.com X-Msg-Ref: server-3.tower-146.messagelabs.com!1235164667!2251821!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [144.160.128.141] Received: (qmail 12054 invoked from network); 20 Feb 2009 21:17:48 -0000 Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com) (144.160.128.141) by server-3.tower-146.messagelabs.com with AES256-SHA encrypted SMTP; 20 Feb 2009 21:17:48 -0000 Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph161.enaf.ffdc.sbc.com (8.14.3/8.14.3) with ESMTP id n1KLHlmL020776 for ; Fri, 20 Feb 2009 13:17:47 -0800 Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11]) by flph161.enaf.ffdc.sbc.com (8.14.3/8.14.3) with ESMTP id n1KLHhIK020687 for ; Fri, 20 Feb 2009 13:17:43 -0800 Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id n1KLHgJe009946 for ; Fri, 20 Feb 2009 15:17:43 -0600 Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id n1KLHdQY009905 for ; Fri, 20 Feb 2009 15:17:40 -0600 Message-Id: <200902202117.n1KLHdQY009905@klph001.kcdc.att.com> Received: from acmt.att.com (vpn-135-70-226-37.vpn.east.att.com[135.70.226.37](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20090220211739gw1000u6cse>; Fri, 20 Feb 2009 21:17:39 +0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 20 Feb 2009 16:17:38 -0500 To: ippm@ietf.org From: Al Morton In-Reply-To: <7.1.0.9.0.20081109092728.0036fb48@att.com> References: <7.1.0.9.0.20081109092728.0036fb48@att.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: ippm-ads@tools.ietf.org Subject: Re: [ippm] Use TLS in TWAMP-Control? X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2009 21:17:36 -0000 At the last IPPM meeting, I was asked to re-send this to the list, to see if it might prompt any additional discussion ... At 10:19 AM 11/9/2008, Al Morton wrote: >IPPM folks, > >At the last IPPM session in Dublin, we had a short discussion >on TWAMP security in the context of the various TWAMP extensions >proposed there: > > From http://www.ietf.org/proceedings/08jul/minutes/ippm.txt >> >>Discussion about TWAMP security >>- Lars: Formerly there were some strong security concerns about OWAMP, >> but allowed to go through. Building TWAMP on OWAMP raised those >> concerns again. Are extensions like this going to raise more >> concerns? What can be done to make security people happier? >>- Al: Going to have to ask security people what their concerns are. >>- Henk, Stas: Do not have records of reservations from security people. > >I took the opportunity to discuss the proposed extensions >with Pasi Eronen one evening in Dublin. To briefly summarize, >Pasi did not have concern with the proposed TWAMP features, but suggested >that IPPM take a look at using TLS in the TWAMP Control protocol >and assess the interest to implement a TLS-Control option if >it were available. I agreed to re-initiate the investigation and >discussion, and that's what I'm doing now... > >I put a few slides together and posted them here temporarily: >http://wftp3.itu.int/packet/Background%20Docs/TLS_in_TWAMP_1108.ppt >I've only looked at the initial Control session set-up impact. >We can discuss this topic on the list, and perhaps if there's time >on the IPPM agenda, perhaps we can spend a few minutes there as well. > >Some of the issues with using TLS in OWAMP-Control are identified in >http://tools.ietf.org/html/rfc4656#section-6.6 > >Another resource is a draft from the NETCONF wg: >http://tools.ietf.org/html/draft-ietf-netconf-tls-06 >This memo describes how to use TLS to secure NETCONF. >There are some clear synergies between NETCONF and TWAMP-Control, >but >1,$ s/NETCONF/TWAMP-Control/g >isn't going to do it for us. :-D > >regards, >Al From acmorton@att.com Fri Feb 20 13:28:59 2009 Return-Path: X-Original-To: ippm@core3.amsl.com Delivered-To: ippm@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE3B228C188 for ; Fri, 20 Feb 2009 13:28:59 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -105.796 X-Spam-Level: X-Spam-Status: No, score=-105.796 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_FROM_MTA_HEADER=0.803, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mOZHiy7H1iGH for ; Fri, 20 Feb 2009 13:28:59 -0800 (PST) Received: from mail161.messagelabs.com (mail161.messagelabs.com [216.82.253.115]) by core3.amsl.com (Postfix) with ESMTP id 100F428C129 for ; Fri, 20 Feb 2009 13:28:59 -0800 (PST) X-VirusChecked: Checked X-Env-Sender: acmorton@att.com X-Msg-Ref: server-13.tower-161.messagelabs.com!1235165351!16105165!1 X-StarScan-Version: 6.0.0; banners=-,-,- X-Originating-IP: [144.160.128.141] Received: (qmail 1913 invoked from network); 20 Feb 2009 21:29:12 -0000 Received: from sbcsmtp9.sbc.com (HELO flph161.enaf.ffdc.sbc.com) (144.160.128.141) by server-13.tower-161.messagelabs.com with AES256-SHA encrypted SMTP; 20 Feb 2009 21:29:12 -0000 Received: from enaf.ffdc.sbc.com (localhost.localdomain [127.0.0.1]) by flph161.enaf.ffdc.sbc.com (8.14.3/8.14.3) with ESMTP id n1KLTBrd006232 for ; Fri, 20 Feb 2009 13:29:11 -0800 Received: from klph001.kcdc.att.com (klph001.kcdc.att.com [135.188.3.11]) by flph161.enaf.ffdc.sbc.com (8.14.3/8.14.3) with ESMTP id n1KLT68R006146 for ; Fri, 20 Feb 2009 13:29:07 -0800 Received: from kcdc.att.com (localhost.localdomain [127.0.0.1]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id n1KLT6Hd021774 for ; Fri, 20 Feb 2009 15:29:06 -0600 Received: from maillennium.att.com (dns.maillennium.att.com [135.25.114.99]) by klph001.kcdc.att.com (8.14.0/8.14.0) with ESMTP id n1KLT1St021663 for ; Fri, 20 Feb 2009 15:29:01 -0600 Message-Id: <200902202129.n1KLT1St021663@klph001.kcdc.att.com> Received: from acmt.att.com (vpn-135-70-226-37.vpn.east.att.com[135.70.226.37](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20090220212901gw1000u6d2e>; Fri, 20 Feb 2009 21:29:01 +0000 X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9 Date: Fri, 20 Feb 2009 16:28:57 -0500 To: ippm@ietf.org From: Al Morton Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: lencia@att.com Subject: [ippm] Reflect-Octets: New TWAMP Test Packet Format? X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2009 21:29:00 -0000 IPPM, Len Ciavattone and I introduced the possibility for a significant test packet format overhaul last November at IETF-73: http://www.ietf.org/proceedings/08nov/slides/ippm-4/ippm-4.htm and in the draft http://tools.ietf.org/html/draft-ietf-ippm-twamp-reflect-octets-00#section-5 We were proposing to make some changes as part of the Reflect-Octets draft/work item, because it makes sense to deal with several format aspects at once. There were some suggestions made at the mike and captured in the minutes: >Open question: consider change the structure of the TWAMP structure >to TLV type structure to make it more extensible. > >Questions from the floor: Roman Kraznowski said he had some things he'd >like to add. He'd post to the list. Please take a look at the slides and the draft and make further comments, so we can determine a path forward. thanks and regards, Al and Len From roman.krzanowski@verizon.com Fri Feb 20 14:26:08 2009 Return-Path: X-Original-To: ippm@core3.amsl.com Delivered-To: ippm@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2120B3A6A3B for ; Fri, 20 Feb 2009 14:26:08 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.599 X-Spam-Level: X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QbZvOe-Rf3eV for ; Fri, 20 Feb 2009 14:26:07 -0800 (PST) Received: from sacmail4.verizon.com (sacmail4.verizon.com [192.76.84.42]) by core3.amsl.com (Postfix) with ESMTP id 4FDF73A6911 for ; Fri, 20 Feb 2009 14:26:07 -0800 (PST) Received: from smtpftw3.verizon.com (smtpftw3.verizon.com [138.83.140.92]) by sacmail4.verizon.com (8.13.7+Sun/8.13.3) with ESMTP id n1KMQGLo020871; Fri, 20 Feb 2009 17:26:21 -0500 (EST) Received: from ftwccout01.verizon.com (ftwccout01.verizon.com [138.83.131.134]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id n1KMQGTf008625; Fri, 20 Feb 2009 17:26:16 -0500 (EST) Received: from ftwccout01.verizon.com (unknown [127.0.0.1]) by ftwccout01.verizon.com (Symantec Mail Security) with ESMTP id 9223B528002; Fri, 20 Feb 2009 17:26:16 -0500 (EST) X-AuditID: 8a538386-a00ebbb000000947-31-499f2e0884ca Received: from smtpftw3.verizon.com (unknown [138.83.140.92]) by ftwccout01.verizon.com (EMF) with ESMTP id 6BC1A4E4002; Fri, 20 Feb 2009 17:26:16 -0500 (EST) Received: from FHDP1CCMXCG01.us.one.verizon.com ([166.68.240.33]) by smtpftw3.verizon.com (8.13.3/8.13.3) with ESMTP id n1KMQ9VI008404; Fri, 20 Feb 2009 17:26:16 -0500 (EST) Received: from FHDP1CCMXCV02.us.one.verizon.com ([166.68.240.12]) by FHDP1CCMXCG01.us.one.verizon.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 20 Feb 2009 17:26:15 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Fri, 20 Feb 2009 17:26:14 -0500 Message-ID: In-reply-to: <200902202129.n1KLT1St021663@klph001.kcdc.att.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [ippm] Reflect-Octets: New TWAMP Test Packet Format? Thread-Index: AcmTokqiPYOPMNJkQtupTbcQMH2/vgAB7GTQ References: <200902202129.n1KLT1St021663@klph001.kcdc.att.com> From: "Krzanowski, Roman" To: "Al Morton" , X-OriginalArrivalTime: 20 Feb 2009 22:26:15.0515 (UTC) FILETIME=[3E4432B0:01C993AA] X-Brightmail-Tracker: AAAAAA== Cc: lencia@att.com Subject: Re: [ippm] Reflect-Octets: New TWAMP Test Packet Format? X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Feb 2009 22:26:08 -0000 Al I am for the TLV structure as it would open TWAMP for future enhancements as well as=20 For some propratary extensions , if needed vendor specific TLV code, optional TLVs and so on... In most of the control algorithms ( and other) I see TLv as an elegant solution to the data structures=20 We would need to preserve the compatibility with the current format but .. I guess this canbe done My 3cs.. rmk -----Original Message----- From: ippm-bounces@ietf.org [mailto:ippm-bounces@ietf.org] On Behalf Of Al Morton Sent: Friday, February 20, 2009 4:29 PM To: ippm@ietf.org Cc: lencia@att.com Subject: [ippm] Reflect-Octets: New TWAMP Test Packet Format? IPPM, Len Ciavattone and I introduced the possibility for a significant test packet format overhaul last November at IETF-73: http://www.ietf.org/proceedings/08nov/slides/ippm-4/ippm-4.htm and in the draft http://tools.ietf.org/html/draft-ietf-ippm-twamp-reflect-octets-00#secti on-5 We were proposing to make some changes as part of the Reflect-Octets draft/work item, because it makes sense to deal with several format aspects at once. There were some suggestions made at the mike and captured in the minutes: >Open question: consider change the structure of the TWAMP structure >to TLV type structure to make it more extensible. > >Questions from the floor: Roman Kraznowski said he had some things he'd >like to add. He'd post to the list. Please take a look at the slides and the draft and make further comments, so we can determine a path forward. thanks and regards, Al and Len _______________________________________________ ippm mailing list ippm@ietf.org https://www.ietf.org/mailman/listinfo/ippm From Nischal.Piratla@telekom.de Tue Feb 24 12:38:42 2009 Return-Path: X-Original-To: ippm@core3.amsl.com Delivered-To: ippm@core3.amsl.com Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7384C3A6841 for ; Tue, 24 Feb 2009 12:38:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.248 X-Spam-Level: X-Spam-Status: No, score=-3.248 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1] Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3cDcI+yjBAho for ; Tue, 24 Feb 2009 12:38:40 -0800 (PST) Received: from tcmail83.telekom.de (tcmail83.telekom.de [62.225.183.131]) by core3.amsl.com (Postfix) with ESMTP id 306CB3A697D for ; Tue, 24 Feb 2009 12:38:40 -0800 (PST) Received: from s4de9jsaanm.mgb.telekom.de (HELO S4DE9JSAANM.ost.t-com.de) ([10.125.177.122]) by tcmail81.telekom.de with ESMTP; 24 Feb 2009 21:38:57 +0100 Received: from S4DE9JSAAMV.ost.t-com.de ([10.125.177.113]) by S4DE9JSAANM.ost.t-com.de with Microsoft SMTPSVC(6.0.3790.3959); Tue, 24 Feb 2009 21:38:57 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C996BF.EA1841FA" Date: Tue, 24 Feb 2009 21:38:56 +0100 Message-ID: <74786E53E28B4D49B86B31C87D32FE5503844562@S4DE9JSAAMV.ost.t-com.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: CFP: The Fourth IEEE LCN Workshop on Network Measurements, in conjunction with the 34th IEEE LCN Thread-Index: AcmWv+n8xGbJEnhsRQ6GSkTNvaKxWw== From: To: X-OriginalArrivalTime: 24 Feb 2009 20:38:57.0193 (UTC) FILETIME=[EA613990:01C996BF] Subject: [ippm] CFP: The Fourth IEEE LCN Workshop on Network Measurements, in conjunction with the 34th IEEE LCN X-BeenThere: ippm@ietf.org X-Mailman-Version: 2.1.9 Precedence: list List-Id: IETF IP Performance Metrics Working Group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Feb 2009 20:39:41 -0000 This is a multi-part message in MIME format. ------_=_NextPart_001_01C996BF.EA1841FA Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sincere apologies for duplication, if you have received it through other = channels. Call for Papers: WNM 2009 Fourth IEEE LCN Workshop on Network Measurements, in conjunction = with the 34th IEEE LCN (http://www.cnrl.colostate.edu/IEEELCN-WNM2009/) =20 October 20-23, 2009 Swiss=F4tel Z=FCrich, Schulstrasse 44, CH-8050 Z=FCrich, = Switzerland The LCN International Workshop on Network Measurements, will be = held in=20 conjunction with the IEEE Conference on Local Computer Networks = (LCN).=20 The workshop will include papers and panels dealing with latest = advances and=20 challenges facing the field. The expected audience will include = networking=20 researchers, practitioners, scientists and engineers from industry, = academia and government. LCN registration will cover workshop = attendance. The first three IEEE LCN Workshop on Network Measurements was very=20 successful in bringing together a set of participants actively = working on=20 network measurements in various domains. We will continue to = address=20 network measurements from different perspectives and different = domains. =20 Topics of Interest: Network measurements are crucial for operation, diagnosis, and=20 characterization of complex networks. Accurate characterization is=20 important for understanding the behavior of networks and for = evaluating=20 the scalability, reliability and performance of protocols. = Cross-layer=20 designs, and overlay protocols often rely on measurements. = Measurements in=20 wired and wireless domains, and end-to-end and subnet measurements = face=20 domain specific constraints while sharing common objectives. = Complex=20 dynamics of the networks and also the difficulties in performing=20 measurement itself pose many challenges. This workshop will provide = a=20 forum for researchers and practitioners interested in network = measurements=20 to discuss and exchange measurement related research in both = wireless and=20 wired domains, and also explore emerging fields of measurements = such as on=20 mobile devices. =20 High quality, previously unpublished work is solicited on the = topics=20 including, but not limited to: Measurements on homogeneous and heterogeneous networks=20 Physical layer characteristics and measurements for wireless = networks=20 Implementation and operational challenges of wireless testbeds=20 Mobility models and traffic patterns=20 Wired and wireless domain measurements=20 Measurement tools, benchmarks and data sets=20 Bandwidth, capacity and delay estimation=20 Active and passive measurements at core nodes=20 End-to-end and/or application-level measurements over the = Internet=20 Metrics for network characterization=20 Measurements on Mobile devices=20 Applications and protocols relying on network measurements Paper length should not exceed 6 pages. Papers should be submitted=20 electronically in PDF format via EDAS. Papers will go through a = thorough=20 review process. The accepted papers will appear in the IEEE LCN = conference=20 proceedings and also be available via IEEE Xplore. Proposals for panel sessions are also invited. Please send the = proposal by=20 the same deadline as for papers.=20 Important Dates: Paper registration deadline: April 6, 2009 Paper submission deadline: April 13, 2009 Notification of acceptance: June 30, 2009 Camera-ready paper due: July 28, 2009 Registration deadline: July 28, 2009 Information on registration, hotel, etc. is available at IEEE = Conference=20 on Local Computer Networks (LCN) General Chairs: Nischal M. Piratla=20 Deutsche Telekom, Inc., R&D Lab 5050 El Camino Real Los Altos 94022, USA Nischal.Piratla@telekom.de Anura P. Jayasumana=20 Computer Networking Research Laboratory Department of Electrical & Computer Engineering Colorado State University Fort Collins, CO 80523, USA Anura.Jayasumana@colostate.edu Program Committee TBA ----- Nischal M. Piratla, Ph.D. Innovation Development 5050 El Camino Real, Suite 221, Los Altos, CA 94022, USA Ernst-Reuter-Platz 7, 10587, Berlin, Germany Voice: + 1 (650) 335 4120 + 49 (30) 8353 54120 Fax: + 1 (650) 335 4101 + 49 (30) 8353 58409 =20 Aufsichtsrat: Prof. Dr. Ulrich Lehner (Vorsitzender) Vorstand: Ren=E9 Obermann (Vorsitzender), Dr. Karl-Gerhard Eick = (stellvertretender Vorsitzender), Hamid Akhavan, Dr. Manfred Balz, = Reinhard Clemens, Timotheus H=F6ttges, Thomas Sattelberger Handelsregister: Amtsgericht Bonn HRB 6794, Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr.: DE50478376 ------_=_NextPart_001_01C996BF.EA1841FA Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable CFP: The Fourth IEEE LCN Workshop on Network Measurements, in = conjunction with the 34th IEEE LCN

Sincere apologies for = duplication, if you have received it through other channels.

Call for Papers:

    WNM = 2009
    Fourth IEEE = LCN Workshop on Network Measurements, in conjunction with the 34th IEEE = LCN
     = (http://www.cnrl.colostate.edu/IEEELCN-WNM2009/)
    
     October = 20-23, 2009
     = Swiss=F4tel Z=FCrich, Schulstrasse 44, CH-8050 Z=FCrich, = Switzerland

     The LCN = International Workshop on Network Measurements, will be held in
     = conjunction with the IEEE Conference on Local Computer Networks (LCN). =
     The = workshop will include papers and panels dealing with latest advances and =
     = challenges facing the field. The expected audience will include = networking
     = researchers, practitioners, scientists and engineers from industry, =
     = academia and government.  LCN registration will cover  = workshop attendance.
     The = first three IEEE LCN Workshop on Network Measurements was very
     = successful in bringing together a set of participants actively working = on
     network = measurements in various domains. We will continue  to address =
     network = measurements from different perspectives and different domains.  =

     Topics = of Interest:

     Network = measurements are crucial for operation, diagnosis, and
     = characterization of complex networks. Accurate characterization is =
     = important for understanding the behavior of networks and for evaluating =
     the = scalability, reliability and performance of protocols. Cross-layer =
     = designs, and overlay protocols often rely on measurements. Measurements = in
     wired = and wireless domains, and end-to-end and subnet measurements face =
     domain = specific constraints while sharing common objectives. Complex
     = dynamics of the networks and also the difficulties in performing
     = measurement itself pose many challenges. This workshop will provide a =
     forum = for researchers and practitioners interested in network measurements =
     to = discuss and exchange measurement related research in both wireless and =
     wired = domains, and also explore emerging fields of measurements such as on =
     mobile = devices.
 
     High = quality, previously unpublished work is solicited on the topics
     = including, but not limited to:

       Measurements on homogeneous = and heterogeneous networks
       Physical layer characteristics = and measurements for wireless networks
       Implementation and operational = challenges of wireless testbeds
       Mobility models and traffic = patterns
       Wired and wireless domain = measurements
       Measurement tools, benchmarks = and data sets
       Bandwidth, capacity and delay = estimation
       Active and passive = measurements at core nodes
       End-to-end and/or = application-level measurements over the Internet
       Metrics for network = characterization
       Measurements on Mobile devices =
       Applications and protocols = relying on network measurements

     Paper = length should not exceed 6 pages. Papers should be submitted
     = electronically in PDF format via EDAS.  Papers will go through a = thorough
     review = process. The accepted papers will appear in the IEEE LCN conference =
     = proceedings and also be available via IEEE Xplore.
     = Proposals for panel sessions are also invited. Please send the proposal = by
     the = same deadline as for papers.

     = Important Dates:

     Paper = registration deadline: April 6,  2009
     Paper = submission deadline:   April 13, 2009
     = Notification of acceptance:  June  30, 2009
     = Camera-ready paper due:      July  28, = 2009
     = Registration deadline:       July  28, = 2009

     = Information on registration, hotel, etc.  is available at IEEE = Conference
     on = Local Computer Networks (LCN)

     General = Chairs:

           = Nischal M. Piratla
           = Deutsche Telekom, Inc.,
           = R&D Lab
           5050 = El Camino Real
           Los = Altos 94022, USA
           = Nischal.Piratla@telekom.de

           Anura P. Jayasumana
           = Computer Networking Research Laboratory
           = Department of Electrical & Computer Engineering
           = Colorado State University
           Fort = Collins, CO 80523, USA
           = Anura.Jayasumana@colostate.edu


      = Program Committee

          TBA

-----
Nischal M. Piratla, Ph.D.
Innovation Development
5050 El Camino Real, Suite 221, Los = Altos, CA 94022, USA
Ernst-Reuter-Platz 7, 10587, Berlin, = Germany

Voice: + 1 (650) 335 4120
         &nbs= p;  + 49 (30) 8353 54120
Fax:     + 1 (650) = 335 4101
         &nbs= p;   + 49 (30) 8353 58409
         &nbs= p; =20
Aufsichtsrat: Prof. Dr. Ulrich = Lehner (Vorsitzender)
Vorstand: Ren=E9 Obermann = (Vorsitzender), Dr. Karl-Gerhard Eick (stellvertretender Vorsitzender), = Hamid Akhavan, Dr. Manfred Balz, Reinhard Clemens, Timotheus H=F6ttges, = Thomas Sattelberger

Handelsregister: Amtsgericht Bonn = HRB 6794, Sitz der Gesellschaft: Bonn
WEEE-Reg.-Nr.: DE50478376

------_=_NextPart_001_01C996BF.EA1841FA--