FW: RE: [bmwg] Updates to MPLS Protection Meth/Term draft- Request forcomments/review

<cary_wright@agilent.com> Tue, 13 March 2007 03:45 UTC

Return-path: <bmwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQxxT-0001vC-Av; Mon, 12 Mar 2007 23:45:55 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HQxxR-0001rB-PA for bmwg@ietf.org; Mon, 12 Mar 2007 23:45:53 -0400
Received: from msgbas1x.net.asiapac.agilent.com ([192.25.42.26]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HQxxP-0003cI-ML for bmwg@ietf.org; Mon, 12 Mar 2007 23:45:53 -0400
Received: from relsgp1.sgp.agilent.com (relsgp1.sgp.agilent.com [141.183.100.45]) by msgbas1x.net.asiapac.agilent.com (Postfix) with ESMTP id 6E402843 for <bmwg@ietf.org>; Tue, 13 Mar 2007 11:45:50 +0800 (SGP)
Received: from wsgpvs01.sgp.agilent.com (wsgpvs01.sgp.agilent.com [141.183.6.23]) by relsgp1.sgp.agilent.com (Postfix) with ESMTP id 6059527EAF for <bmwg@ietf.org>; Tue, 13 Mar 2007 11:45:50 +0800 (SGT)
Received: from wsgpbh03.sgp.agilent.com ([141.183.6.65]) by wsgpvs01.sgp.agilent.com with InterScan Messaging Security Suite; Tue, 13 Mar 2007 11:45:50 +0800
Received: from wsgpmb01.sgp.agilent.com ([141.183.6.67]) by wsgpbh03.sgp.agilent.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 13 Mar 2007 11:45:50 +0800
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Subject: FW: RE: [bmwg] Updates to MPLS Protection Meth/Term draft- Request forcomments/review
Date: Tue, 13 Mar 2007 11:45:48 +0800
Message-ID: <B107F3933E266542AA79CA90C1C95E1D01A9FC66@wsgpmb01.sgp.agilent.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: RE: [bmwg] Updates to MPLS Protection Meth/Term draft- Request forcomments/review
Thread-Index: AcdiAaYtW63KhAjGRnSHOjwxwOrKQADIFdQA
From: cary_wright@agilent.com
To: bmwg@ietf.org
X-OriginalArrivalTime: 13 Mar 2007 03:45:50.0074 (UTC) FILETIME=[177D75A0:01C76522]
X-Spam-Score: 0.3 (/)
X-Scan-Signature: a0534e6179a1e260079328e8b03c7901
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1025512340=="
Errors-To: bmwg-bounces@ietf.org

I'd like to comment on the questions posed below.
 
Using accurate packet timestamping mechanisms it is feasible to measure data plane convergence much more accurately, modern measurement tools have timestamp resolution down to 10ns resolution. When using packet timestamps, the resolution and accuracy of a convergence or switchover measurement will be mostly limited by the packet frequency on the link. 1,000,000 packets per sec will provide a resolution of 1us for a data plane convergence measurement if packet timestamps are used, requiring about 50% of a GbE link's available bandwidth. 
 
I believe 1ms is an appropriate sampling interval for data plane switchover and convergence tests. This is feasible in most scenarios, and better matches the high availability expectations of modern services.
 
Regards,
Cary Wright
 
________________________________

*	To: <bmwg at ietf.org <mailto:bmwg@DOMAIN.HIDDEN> > 
*	Subject: RE: [bmwg] Updates to MPLS Protection Meth/Term draft- Request forcomments/review 
*	From: "Samir Vapiwala \(svapiwal\)" <svapiwal at cisco.com <mailto:svapiwal@DOMAIN.HIDDEN> > 
*	Date: Thu, 8 Mar 2007 09:28:28 -0500 
 
Further to Rajiv's earlier email we as MPLS Protection benchmarking Author team would like to seek input to the following unaddressed items on the mailing list so that we can get closure on these open items prior to the BMWG meeting:
 
 Since the packet smapling interval recommended in the "draft-ietf-bmwg-igp-dataplane-conv-meth-12.txt,  section 3.2.5 Convergence Time Metrics" may not be applicable to the MPLS FRR scenario where failover times have to be below 45ms, here are some of our thoughts or questions to the list: 

1.	We would like to adapt similar approach the IGP convergence as this defiinition applies to current work item 
2.	We feel that 100ms is large for MPLS FRR application, under which the target is always keeping the failover times below 45ms. 
3.	We are considering changing this number to 10ms, and would expect test tool to offer this smapling interval

Please provide your input to this suggested value so that we can have a conclusion before the next meeting.
 
 
Regards,
 
MPLS Protection Benchmarking Author Team
 
_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www1.ietf.org/mailman/listinfo/bmwg