70 likes | 231 Views
IETF BMWG Work Items. 63rd IETF Meeting – Paris, France Tuesday 8/2/05. Work Items. NETWORK LAYER TRAFFIC CONTROL MECHANISMS (WG Last Call) IGP DATA PLANE CONVERGENCE (WG Last Call) ACCELERATED STRESS TEST (BMWG Work Item) NETWORK PROTECTION MECHANISMS (Proposed WG Work Item).
E N D
IETF BMWG Work Items 63rd IETF Meeting – Paris, France Tuesday 8/2/05
Work Items • NETWORK LAYER TRAFFIC CONTROL MECHANISMS (WG Last Call) • IGP DATA PLANE CONVERGENCE (WG Last Call) • ACCELERATED STRESS TEST (BMWG Work Item) • NETWORK PROTECTION MECHANISMS (Proposed WG Work Item)
NETWORK LAYER TRAFFIC CONTROL MECHANISMS (WGLC) • Co-authors are Scott Poretsky of Reef Point, Jerry Perser, Shobha Erramilli of Qnetworx, and Sumit Khurana of Telcordia • draft-ietf-bmwg-dsmterm-11.txt, Terminology for Benchmarking Network Layer Traffic Control Mechanisms • WGLC was successfully completed for this document • Final action item was to resolve I-D Nits. This was completed in the –11 submission. • Ready for IESG? • draft-ietf-bmwg-dsm-meth-00.txt, Methodology for Benchmarking Network Layer Traffic Control Mechanisms • Will be submitted prior to IETF 64 • Anyone interested in being a co-author?
IGP DATA PLANE ROUTE CONVERGENCE (WG Last Call) • Co-authors are Scott Poretsky of Reef Point and Brent Imhoff • 3 documents completed WGLC • draft-ietf-bmwg-igp-dataplane-conv-app-07.txt, Considerations for Benchmarking IGP Data Plane Route Convergence • draft-ietf-bmwg-igp-dataplane-conv-term-07.txt, Terminology for Benchmarking IGP Data Plane Route Convergence • draft-ietf-bmwg-igp-dataplane-conv-meth-07.txt, Benchmarking Methodology for IGP Data Plane Route Convergence • 2 more changes required: • LC review identified inconsistency in Methodology and Terminology • -07 Methodology uses "throughput" and refers to RFCs 1242 and 2544. –07 Terminology uses "forwarding rate" and makes no reference to RFC. • Action is to keep the Methodology as-is and in the –08 Terminology replace occurrences for "forwarding rate" with "throughput" and reference RFCs 1242 and 2544. • Need to resolve I-D Nits • Given these two changes, Ready for IESG?
ACCELERATED STRESS (BMWG Work Item) • Co-authors are Scott Poretsky of Reef Point and Shankar Rao of Qwest • draft-ietf-bmwg-acc-bench-term-06.txt, Terminology for Accelerated Stress Benchmarking • Ready for WGLC? • At recommendation of BWMG co-chairs, Methodology divided into separate documents: • draft-ietf-bmwg-acc-bench-meth-03.txt, Methodology Guidelines for Accelerated Stress Benchmarking • Ready for WGLC? • draft-ietf-bmwg-acc-bench-meth-ebgp-00.txt, Methodology for Benchmarking Accelerated Stress with Operational EBGP Instabilities • draft-ietf-bmwg-acc-bench-meth-opsec-00.txt, Methodology for Benchmarking Accelerated Stress with Operational Security • Input provided by OpSec WG • Advantage of this format: additional technology specific methodologies could be added
NETWORK PROTECTION MECHANISMS (Proposed WG Work Item) (1 of 2) • Co-authors are Scott Poretsky of Reef Point, Jean-Louis LeRoux of France Telecom, Takumi Kimura of NTT, Shankar Rao of Qwest, and Rajiv Papneja of Isocore • draft-poretsky-protection-term-00.txt, Benchmarking Terminology for Protection Performance • At request of co-chairs, this work item provides a single Terminology document from 2 separately proposed work items for benchmarking sub-IP layer protection mechanisms • draft-poretsky-mpls-protection-meth-04.txt, Benchmarking Methodology for MPLS Protection Mechanisms • Submitted with updated terminology to match new Terminology doc • Prior revisions were reviewed by participants in MPLS WG and BMWG • Fast Reroute mechanism now RFC 4090
NETWORK PROTECTION MECHANISMS (Proposed WG Work Item) (2 of 2) • Need for this work item: • The IP network layer provides route convergence to protect data traffic against planned and unplanned failures in the internet. • BWMG has work items to address convergence benchmarking. • Technologies that function at sub-IP layers can be enabled to provide further protection of IP traffic. • The metrics for benchmarking the performance of sub-IP protection mechanisms can be measured at the IP layer, so that the results are always measured in reference to IP and independent of the specific protection mechanism being used. • Enables different protection mechanisms to be benchmarked and compared • Enables different implementations of the same protection mechanism to be benchmarked and compared • Sub-IP protection mechanisms include High Availability (HA) stateful failover. Virtual Router Redundancy Protocol (VRRP), Automatic Protection Switching (APS) for SONET/SDH, and Fast Reroute for Multi-Protocol Label Switching (MPLS). • It is intended that there can exist unique methodology documents for each sub-IP protection mechanism, such as MPLS.