Re: [bmwg] Comment on meth-18.

"Scott Poretsky" <sporetsky@allot.com> Fri, 17 July 2009 18:18 UTC

Return-Path: <sporetsky@allot.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 15AD828C2F1 for <bmwg@core3.amsl.com>; Fri, 17 Jul 2009 11:18:07 -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 nGAbWcc0OzBD for <bmwg@core3.amsl.com>; Fri, 17 Jul 2009 11:18:06 -0700 (PDT)
Received: from mailgw.allot.com (mailgw.allot.com [199.203.223.210]) by core3.amsl.com (Postfix) with ESMTP id 2F2F13A680A for <bmwg@ietf.org>; Fri, 17 Jul 2009 11:18:04 -0700 (PDT)
Received: from mail.allot.com (Not Verified[172.20.20.20]) by mailgw.allot.com with MailMarshal (v6, 4, 6, 5922) id <B4a60c05b0004>; Fri, 17 Jul 2009 21:18:03 +0300
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, 17 Jul 2009 21:07:50 +0300
Message-ID: <E1DB169CF43C174181F7147204E23D7401E36CE2@neon.ALLOT.LOCAL>
In-Reply-To: <00a301ca06f5$a52fd510$840efe90@emea.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [bmwg] Comment on meth-18.
Thread-Index: AcoFhX5d/L88OUFuStem1Mmgc3WxrgAEPfsgACVfQqAAN0SWQA==
References: <200907151948.n6FJm39K015030@klph001.kcdc.att.com><03C9BAFF80BCD047AFBDFBB5B38A688CF53BBA@spccalexcbe01.AD.SPIRENTCOM.COM> <00a301ca06f5$a52fd510$840efe90@emea.cisco.com>
From: Scott Poretsky <sporetsky@allot.com>
To: Kris Michielsen <kmichiel@cisco.com>, "McLendon, John" <John.McLendon@spirent.com>, Al Morton <acmorton@att.com>, bmwg@ietf.org
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 18:18:07 -0000

Kris,

Test equipment does not drop or discard since they do not route or
switch.  The test equipment is the last hop of the path for a packet
flow.  The test equipment receives the packets and increments counters.


Scott

-----Original Message-----
From: bmwg-bounces@ietf.org [mailto:bmwg-bounces@ietf.org] On Behalf Of
Kris Michielsen
Sent: Friday, July 17, 2009 11:46 AM
To: 'McLendon, John'; 'Al Morton'; bmwg@ietf.org
Subject: Re: [bmwg] Comment on meth-18.

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
> 

_______________________________________________
bmwg mailing list
bmwg@ietf.org
https://www.ietf.org/mailman/listinfo/bmwg