1. 1 Content-Aware Device Benchmarking Methodology/Terminology (draft-ietf-bmwg-ca-bench-meth-00) BMWG Meeting IETF-82 Taipei November 2011 Mike Hamilton mhamilton@breakingpoint.com BreakingPoint Systems

2. 2 Agenda Draft Update Resolved Questions Unresolved Questions Work To Do Markov Next Steps

3. 3 Update-BC 1. More Concise first sentence (Page 1, paragraph 1) --Modified to take suggestion 2. Examples of what devices use to make forwarding decisions(Page 3, paragraph 1) --Great idea. 3. Confusing wording on last sentence (Page 3, last paragraph) --Reworded the entire paragraph to hopefully clear the confusion 4. Out of place sentence (Page 4, paragraph 2) --Removed the sentence, but would like input on where it does belong 5. Confusing paragraph (Page 4, 2nd to last paragraph) --Totally reworded to be more succinct

4. 4 Update-BC 6. Section 3.3 relocation/deletions --Made the appropriate changes 7. Page 7, 3rd paragraph --Outstanding point. Next version will include this discussion on individual testing 8. Section 4.3 --Interesting point, but would like to add this to topic for discussion in Taipei --I'm leaning toward removing it, but leaving in the malformed (since it can be --algorithmically defined)

5. 5 Update-AM 1. Asked for examples on page 4 for specmanship --Decided to remove section. Found several examples, but it probably isn't worth discussing 2. Asked for rewording on (page 4, paragraph 2) --This sentence to be moved somewhere else, not sure where as of now though --Will also be reworded to match your suggestion. 3. Asked for explicit list of metrics (page 5, sect 2, paragraph 3) --Added current list of metrics to be captured 4. Switching order of paragraph(page 5, last paragraph) --Done. 5. Additional clarification requested (page 6, section 3) --Added 6. Section 3.2 conjunction of IPv4/IPv6 address ranges --Done.

6. 6 Update-AM 7. Section 3.3 reword --Done 8. Section 3.4 wording change --Done 9. Section 3.4(second paragraph) rewording --Done 10. Section 3.4 (3rd paragraph) insertion of words --Done 11.Page 8, first paragraph wording/additions --Done 12. Page 8, 3rd paragraph rewording of last sentance --Done

7. 7 Update-AM 13. Section 3.7.1 - missing reference to RFC 5180 for IPv6 --Added 14. Section 3.7.3 --Added more specific references 15. General SHOULD/MUST/MAY disagreements --Should be adequately addressed 16.Example Traffic Pattern Table updates (Appendix A) --Addressed.

8. 8 Resolved Questions Traffic Composition How to define a single protocol within the mix Algorithmically Malformed traffic How to define Open-source TCP/IP/UDP(sic)

9. 9 Unresolved Comments Comments from Kenneth Green and Tom Alexander First on TODO list

10. 10 Markov-Pseudo Code $MAXGEN = 10000; $NONWORD = "\n"; $w1 = $w2 = $NONWORD; # initial state open FILE, "<", "corpus.txt"; while ( ) { # read each line of input foreach (split) { push(@{$statetab{$w1}{$w2}}, $_); ($w1, $w2) = ($w2, $_);# multiple assignment } push(@{$statetab{$w1}{$w2}}, $NONWORD); # add tail $w1 = $w2 = $NONWORD; for ($i = 0; $i < $MAXGEN; $i++) { $suf = $statetab{$w1}{$w2};# array reference $r = int(rand @$suf);# @$suf is number of elems exit if (($t = $suf->[$r]) eq $NONWORD); print "$t "; ($w1, $w2) = ($w2, $t);# advance chain }

11. Markov HTML IETF #74 - NETCONF WG session 11

12. Markov Email IETF #74 - NETCONF WG session 12

13. 13 Next Steps While not perfect, certainly has made progress Work left to do Further define the traffic mix Finalize Markov algorithm Incorporate ISIC as malformed traffic