1 / 7

Benchmarking Terminology for Routers Supporting Resource Reservation

Benchmarking Terminology for Routers Supporting Resource Reservation. Gábor Fehér , Krisztián Németh, András Korn Budapest University of Technology and Economics István Cselényi TeliaSonera. RFC Editorial remarks. draft-ietf-bmwg-benchres-term v2 :

karyn-vaughan
Download Presentation

Benchmarking Terminology for Routers Supporting Resource Reservation

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 Terminology for Routers Supporting Resource Reservation Gábor Fehér, Krisztián Németh, András Korn Budapest University of Technology and Economics István Cselényi TeliaSonera

  2. RFC Editorial remarks • draft-ietf-bmwg-benchres-term v2: • sent to the RFC editors, bounced back with some comments • Main remarks • Consistency with NSIS? • Slightly confused about diffserv • Referring to the Boomerang protocol(research paper from the same authors) • Too much opinion (prejudgments) in a terminology IETF 57 - Wien

  3. Updates based on remarks • DiffServ parts are completely removed • No support for signaling protocols utilizing DiffServ architectures(e.g. RODA) • Boomerang protocol • NSIS presents it in its analysis draft! • Anyway, no special features are mentioned • No more prejudgments IETF 57 - Wien

  4. NSIS consistency • NSIS Framework – close to Last Call! • NSIS terminology does not replace this draft, but we can be consistent with its philosophy • We think that it is NSIS conform now! • It was, so no big changes IETF 57 - Wien

  5. New version: 02 -> 03 • Most important changes • A more precise QoS Session definition (Previously Resource Reservation Session) • New terms: Reservation States/Resource Reservation Protocol • Unnecessary terms are removed • Many clarifications • BUT no change in the philosophy IETF 57 - Wien

  6. 6.1 Traffic Flow Types 6.1.1 Data Flow 6.1.2 Distinguished Data Flow 6.1.3 Best-Effort Data Flow 6.2 Resource Reservation Protocol Basics 6.2.1 QoS Session 6.2.2 Resource Reservation Protocol 6.2.3 Resource Reservation Capable Router 6.2.4 Reservation State 6.2.5 Resource Reservation Protocol Orientation 6.3 Router Load Factors 6.3.1 Best-Effort Traffic Load Factor 6.3.2 Distinguished Traffic Load Factor 6.3.3 Session Load Factor 6.3.4 Signaling Intensity Load Factor 6.3.5 Signaling Burst Load Factor 6.4 Performance Metrics 6.4.1 Signaling Message Handling Time 6.4.2 Distinguished Traffic Delay 6.4.3 Best-effort Traffic Delay 6.4.4 Signaling Message Loss 6.4.5 Session Maintenance Capacity 6.5 Scalability Limit Definitions IETF 57 - Wien

  7. Future • Need comments! • Draft was sent to the NSIS WG also IETF 57 - Wien

More Related