Re: [bmwg] Comment on meth-18.

"Kris Michielsen" <kmichiel@cisco.com> Fri, 17 July 2009 15:47 UTC

Return-Path: <kmichiel@cisco.com>
X-Original-To: bmwg@core3.amsl.com
Delivered-To: bmwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2AE7328C1B0 for <bmwg@core3.amsl.com>; Fri, 17 Jul 2009 08:47:20 -0700 (PDT)
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 5s11u4xiNiMi for <bmwg@core3.amsl.com>; Fri, 17 Jul 2009 08:47:19 -0700 (PDT)
Received: from av-tac-bru.cisco.com (weird-brew.cisco.com [144.254.15.118]) by core3.amsl.com (Postfix) with ESMTP id D043C3A680E for <bmwg@ietf.org>; Fri, 17 Jul 2009 08:47:18 -0700 (PDT)
X-TACSUNS: Virus Scanned
Received: from strange-brew.cisco.com (localhost.cisco.com [127.0.0.1]) by av-tac-bru.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6HFjiQU024442; Fri, 17 Jul 2009 17:45:44 +0200 (CEST)
Received: from kmichielwxp (dhcp-peg2-vl21-144-254-14-157.cisco.com [144.254.14.157]) by strange-brew.cisco.com (8.13.8+Sun/8.13.8) with ESMTP id n6HFjhu8006734; Fri, 17 Jul 2009 17:45:44 +0200 (CEST)
From: Kris Michielsen <kmichiel@cisco.com>
To: "'McLendon, John'" <John.McLendon@spirent.com>, 'Al Morton' <acmorton@att.com>, bmwg@ietf.org
References: <200907151948.n6FJm39K015030@klph001.kcdc.att.com> <03C9BAFF80BCD047AFBDFBB5B38A688CF53BBA@spccalexcbe01.AD.SPIRENTCOM.COM>
Date: Fri, 17 Jul 2009 17:45:39 +0200
Message-ID: <00a301ca06f5$a52fd510$840efe90@emea.cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 11
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350
Thread-Index: AcoFhX5d/L88OUFuStem1Mmgc3WxrgAEPfsgACVfQqA=
In-Reply-To: <03C9BAFF80BCD047AFBDFBB5B38A688CF53BBA@spccalexcbe01.AD.SPIRENTCOM.COM>
Subject: Re: [bmwg] Comment on meth-18.
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/bmwg>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Jul 2009 15:47:20 -0000

John,

Thanks for reviewing the draft!

What do you think of the following suggestion?
OLD:
For Convergence Events caused by the Tester, such as an IGP cost change, the Tester may start to drop all traffic received from the
Preferred Egress Interface at the Convergence Event Instant to achieve the same result.

NEW:
For Convergence Events caused by the Tester, such as an IGP cost change, the Tester may start to discard all traffic received from
the Preferred Egress Interface at the Convergence Event Instant, or may be able to separately observe packets received from the
Preferred Egress Interface prior to the Convergence Event Instant, to achieve the same result.

Thanks,
Kris

> -----Original Message-----
> From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On 
> Behalf Of McLendon, John
> Sent: 16 July 2009 00:00
> To: Al Morton; bmwg@ietf.org
> Subject: [bmwg] Comment on meth-18.
> 
> Hi all,
> I have a comment on the following statement in Sec 4, top of pp. 9, in
> meth-18:
> 
> "For Convergence Events caused by the Tester, such as an IGP 
> cost change, the Tester may start to drop all traffic 
> received from the Preferred Egress Interface at the 
> Convergence Event Instant to achieve the same result."
> 
> The word "drop" implies that the test device forwards or 
> drops traffic.
> In my experience, test devices neither forward or drop 
> traffic. They may generate or analyze traffic, but a test 
> device dropping traffic doesn't seem helpful to the desired 
> measurement. Many test devices can bring a link down at the 
> physical layer.
> 
> J...
> 
> 
> 
> -----Original Message-----
> From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On 
> Behalf Of Al Morton
> Sent: Wednesday, July 15, 2009 3:48 PM
> To: bmwg@ietf.org
> Subject: Re: [bmwg] WGLC: draft-ietf-bmwg-igp-dataplane drafts
> 
> Comments on meth-18, all nits,
> Al (mostly as participant)
> 
> At 01:44 PM 7/14/2009, Al Morton wrote:
> >...This message begins a Last call on the IGP-Dataplane Convergence 
> >Time Benchmarking drafts.
> >
> >http://tools.ietf.org/html/draft-ietf-bmwg-igp-dataplane-conv-term-18
> >http://tools.ietf.org/html/draft-ietf-bmwg-igp-dataplane-conv-meth-18
> >http://tools.ietf.org/html/draft-ietf-bmwg-igp-dataplane-conv-app-17
> >
> >The Last Call will end on July 31, 2009.
> 
> 
> Section 4, top of page 10,
> s/At least one condition need to /At least one condition needs to /
> 
> 
> 5.7.  Measurement Accuracy
> ...  When packet jitter is much less than the convergence
>     time, it is a negligible source of error and therefor it 
> will be s/therefor/therefore/
> 
> 5.9 Tester Capabilities
> Add "Also see section 6 for method-specific capabilities."
> 
> 6.1.3.  Measurement Accuracy
> 
>     TBD
> (can't leave this TBD, if there's no obvious material, delete 
> section ?)
> 
> 
> Section 7, Reporting Format
> 
>          Maximum Packet Delay Threshold      seconds
> this is called "Forwarding Delay Threshold" in the term doc, right?
> pick one for both...
> 
> Section 9, same as terms, use the standard BMWG paragraphs...
> 
> 
>     
> 
> _______________________________________________
> bmwg mailing list
> bmwg@ietf.org
> https://www.ietf.org/mailman/listinfo/bmwg
> 
> <DIV><FONT size="1">
> 
> E-mail confidentiality.
> --------------------------------
> This e-mail contains confidential and / or privileged 
> information belonging to Spirent Communications plc, its 
> affiliates and / or subsidiaries. If you are not the intended 
> recipient, you are hereby notified that any disclosure, 
> copying, distribution and / or the taking of any action based 
> upon reliance on the contents of this transmission is 
> strictly forbidden. If you have received this message in 
> error please notify the sender by return e-mail and delete it 
> from your system. If you require assistance, please contact 
> our IT department at helpdesk@spirent.com.
> 
> Spirent Communications plc
> Northwood Park, Gatwick Road, Crawley, West Sussex, RH10 9XN, 
> United Kingdom.
> Tel No. +44 (0) 1293 767676
> Fax No. +44 (0) 1293 767677
> 
> Registered in England Number 470893
> Registered at Northwood Park, Gatwick Road, Crawley, West 
> Sussex, RH10 9XN, United Kingdom.
> 
> Or if within the US,
> 
> Spirent Communications,
> 26750 Agoura Road, Calabasas, CA, 91302, USA.
> Tel No. 1-818-676- 2300 
> 
> </FONT></DIV>
> _______________________________________________
> bmwg mailing list
> bmwg@ietf.org
> https://www.ietf.org/mailman/listinfo/bmwg
>