Re: [bmwg] WGLC: draft-ietf-bmwg-igp-dataplane drafts

[Al Morton <acmorton at att.com>]

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.

Comments on terms-18,
Al (mostly as participant, as chair for section 4)

I think we now need a definition of the "Start Traffic Instant" mentioned
first in section 3.6.3.  It should be defined up-front and probably
included in Figure 1.

Section 3.5.1
s/The Offered Load SHOULD consists /The Offered Load SHOULD consist /

s/Packet Sampling Interval is too high./Packet Sampling Interval is too large./

Section 3.5.2
s/The Offered Load SHOULD consists /The Offered Load SHOULD consist /

Section 3.6.5
s/Event, traffic for all routes /Event, when traffic for all routes /

Section 3.6.6
s/Event, traffic for all routes /Event, when traffic for all routes /

Section 3.7.6
OLD
   ...The BMWG selected 5 seconds based upon RFC 2544 [Br99]
   which recommends waiting 2 seconds for residual frames to arrive
NEW
   ...The BMWG selected 5 seconds based upon RFC 2544 [Br99]
   which recommends waiting 2 seconds for residual frames to arrive
   (this is the Forwarding Delay Threshold for the last packet sent)

Section 4 Security Considerations
What's all this about SIP?
I suggest to use the "standard" BMWG paragraphs:
>    Benchmarking activities as described in this memo are limited to
>    technology characterization using controlled stimuli in a laboratory
>    environment, with dedicated address space and the constraints
>    specified in the sections above.
>
>    The benchmarking network topology will be an independent test setup
>    and MUST NOT be connected to devices that may forward the test
>    traffic into a production network, or misroute traffic to the test
>    management network.
>
>    Further, benchmarking is performed on a "black-box" basis, relying
>    solely on measurements observable external to the DUT/SUT.
>
>    Special capabilities SHOULD NOT exist in the DUT/SUT specifically for
>    benchmarking purposes.  Any implications for network security arising
>    from the DUT/SUT SHOULD be identical in the lab and in production
>    networks.