Re: [bmwg] Comment on meth-18.

["Scott Poretsky" <sporetsky at allot.com>]

I agree with John.

-----Original Message-----
From: bmwg-bounces at ietf.org [mailto:bmwg-bounces at ietf.org] On Behalf Of
McLendon, John
Sent: Wednesday, July 15, 2009 6:00 PM
To: Al Morton; bmwg at 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 at ietf.org [mailto:bmwg-bounces at ietf.org] On Behalf Of
Al Morton
Sent: Wednesday, July 15, 2009 3:48 PM
To: bmwg at 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 at 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 at 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 at ietf.org
https://www.ietf.org/mailman/listinfo/bmwg