1 / 8

Benchmarking Methodology WG (bmwg) 69th IETF – Chicago, USA

Benchmarking Methodology WG (bmwg) 69th IETF – Chicago, USA. Wednesday, July 25, 2007, 13:00-15:00 (Salon 2) Chairs: Al Morton (acmorton@att.com)

frances-bowers
Download Presentation

Benchmarking Methodology WG (bmwg) 69th IETF – Chicago, USA

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Benchmarking Methodology WG (bmwg)69th IETF – Chicago, USA • Wednesday, July 25, 2007, 13:00-15:00 (Salon 2) • Chairs: • Al Morton (acmorton@att.com) • If you are not subscribed to the BMWG mailing list and would like to be, put a BIG asterisk (*) by your legibly-printed e-mail address when you sign the blue attendance sheet, or go to https://www1.ietf.org/mailman/listinfo/bmwg

  2. BMWG Agenda (Any Bashing needed?) • Note-Taker(s), Jabber, IPR (Yellow Sheet), Blue Sheets • WG Status (Chairs, 5 min) • IGP Dataplane Convergence Status. (Poretsky, 5 min) • Accelerated Stress Testing. (Poretsky, 10 min) • IPv6 Bechmarking (Van de Velde, 15 min) • Protection Benchmarking (Poretsky and Papneja, 15 min) • IPsec Benchmarking (Kaeo, 15 min) • Milestones Status (Chairs, 5 min) • Proposed Work (Chairs, 45 min, nominally 15 min each) • Wireless LAN Switches and LAN Meshes (Perser, Alexander) • SIP Performance Benchmarking (Gurbani,Davids,Poretsky) • MPLS-TE (Vapiwala) • (If time allows) LDP Convergence (Papneja) • (not appearing this time): Bi-Directional Forwarding Detection MPLS Benchmarking Methodology (Akhter) Multicast VPN Scalability (Dry)

  3. BMWG Activity • AD/IESG Review • <draft-ietf-bmwg-igp-dataplane-conv-term-13.txt> Rev I-Ds • <draft-ietf-bmwg-igp-dataplane-conv-meth-13.txt> • <draft-ietf-bmwg-igp-dataplane-conv-app-013.txt> • WG Last Call • <draft-ietf-bmwg-ipv6-meth-02.txt> 2nd LC ends Aug 10 • <draft-ietf-bmwg-acc-bench-term-12.txt> Revised on LC comments • <draft-ietf-bmwg-acc-bench-meth-08.txt> Revised on LC comments • I-Ds • draft-ietf-bmwg-ipsec-meth-02.txt Revised, need READERS • draft-ietf-bmwg-ipsec-term-09.txt • draft-ietf-bmwg-protection-term-02.txt Need Readers • draft-ietf-bmwg-protection-meth-02.txt Need Readers • draft-ietf-bmwg-dsmmeth-02.txt Expired

  4. BMWG Activity • Work Proposals. • draft-alexander-bmwg-wlan-switch-term-00.txt <=NEW • draft-alexander-bmwg-wlan-switch-meth-00.txt <=NEW • draft-vapiwalla-bmwg-TE-convergence-motivation-00.txt <=NEW • draft-poretsky-sip-bench-term-03.txt <=Revised • draft-poretsky-bmwg-sip-bench-meth-01.txt<=Revised • draft-sdry-bmwg-mvpnscale-01.txt <=same • draft-akhter-bmwg-mpls-meth-02.txt <=same • draft-eriksson-ldp-convergence-04.txt <=same • draft-karthik-bmwg-ldp-convergence-meth-00.txt <=same • draft-salahuddin-bmwg-bfd-motivation-00.txt <= same • Expected I-Ds • <draft-ietf-bmwg-bgpcmeth-00.txt> (I haven’t heard anything…)

  5. BMWG Activity • Expired BMWG I-Ds • <draft-ietf-bmwg-acc-bench-meth-ebgp-00.txt>, • <draft-ietf-bmwg-acc-bench-meth-opsec-00.txt>, • <draft-ietf-bmwg-benchres-method-00.txt> Pending term • RFC Editor • none • Charter Update • Meet the OLD Milestones, start new work. • Supplementary BMWG Page • See http://home.comcast.net/~acmacm/BMWG/ • New RFC: • RFC 4814 Hash and Stuffing • RFC 4883 Benchmarking Resource Reservation Sys (terms)

  6. Standard “Paragraph” (intro/security) 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.

  7. Current Milestones • Dec 2006 IPsec Device Benchmarking Terminology to AD Review • Dec 2006 IPsec Device Benchmarking Methodology to AD Review • Dec 2006 Router Accelerated Test Terminology I-D to AD Review • Dec 2006 Router Accelerated Test Method. and Considerations I-Ds to AD Review • Feb 2007 Terminology For Protection Benchmarking to AD Review • Mar 2007 IPv6 Benchmarking Methodology to AD Review • Jul 2007 Basic BGP Convergence Benchmarking Methodology to AD Review. • Jul 2007 Methodology For Protection Benchmarking to AD Review • Dec 2007 Net Traffic Control Benchmarking Methodology to AD Review. • Dec 2007 Router Accelerated Test Method for EBGP to AD Review • Dec 2007 Router Accelerated Test Method for Operational Security to AD Review

  8. Work Proposal Summary Matrix

More Related