1 / 19

Realtime Application QOS Monitoring (RAQMON) 57 th IETF Session – Vienna RMON Work Group

Realtime Application QOS Monitoring (RAQMON) 57 th IETF Session – Vienna RMON Work Group. Anwar Siddiqui, Dan Romascanu, Eugene Golovinsky <draft-ietf-rmonmib-raqmon-framework-02.txt> <draft-ietf-rmonmib-raqmon-pdu-02.txt> <draft-ietf-rmonmib-raqmon-mib-01.txt>.

leontyne-durand
Download Presentation

Realtime Application QOS Monitoring (RAQMON) 57 th IETF Session – Vienna RMON Work Group

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. Realtime Application QOS Monitoring (RAQMON) 57th IETF Session – ViennaRMON Work Group • Anwar Siddiqui, Dan Romascanu, Eugene Golovinsky • <draft-ietf-rmonmib-raqmon-framework-02.txt> <draft-ietf-rmonmib-raqmon-pdu-02.txt> • <draft-ietf-rmonmib-raqmon-mib-01.txt>

  2. Changes/Updates/Modification from last drafts • Editorial Changes & clean up • Metrics Definition • Each Metrics is referenced • Architectural Definitions upfront in the document • BASIC PDU and APP PDU is merged into one RAQMON PDU • Mapping RAQMON PDU to SNMP (RDS  RRC) • Encoding RAQMON PDU by using the RAQMON RDS MIB • Congestion Awareness Section • Clarify extensibility • Enhanced Security Sections

  3. 2 Tasks (VoIP, Email Synch) 4 Simul. Tasks (VoIP, Web Collaboration, IM, FTP) RAQMON Framework Overview Simultaneous Voice, Text, Collaboration RRC MIB RMON MIB RRC MIB RMON MIB RRC RRC Proxy (SIP) Gatekeeper (h.323) MGC (MGCP) RAQMON PDU RAQMON PDU (RTCP OR SNMP) 1 Email Server Signaling over TLS 6 TLS 3 1 Task (VoIP) RSVP/NSIS 2 SRTP/RTCP DiffSrv = EF - Signaling (Time to establish session?) - Media (how did it sound?) - Host (limited by Host CPU) 4 UDP or DCCP IEEE 802.1p/Q, IEEE 802.11e 5 Communication Data Forwarding Path

  4. RAQMON Framework Overview Instant Messaging RRC MIB RMON MIB RRC MIB RMON MIB RRC RRC RAQMON PDU Proxy (SIP) AIM XMPP RAQMON PDU (RTCP OR SNMP) 1 Signaling over TLS TLS 1 Task (Instant Messaging) 1 Task (Instant Messaging) 2 Secure Text Relay Does Instant Messaging and WebEX cares about Jitter? UDP or DCCP Communication Data Forwarding Pathanwarsanwars

  5. RAQMON Framework Definition Scope of the Framework RAQMON PDU is Out of Communication Data Forwarding Path Communication Data Forwarding Path UNDERLYING TRANSPORT (RTCP, SNMP) X End Device End Device 2 1 RDS SNMP RDS RRC RAQMON MIB 1 Communication Data Forwarding Path (e.g. RTCP, HTTP, FTP, TLS, SIP, H.323) RDS/RRC RAQMON PDU Path 2

  6. Functional RAQMON Architecture IP End Device  Extensible/Programmable Data Model APPLICATION Communication Network IP PSTN Cellular Optical 1. Context-sensitive Framework  VoIP vs. Instant Messaging vs. XXXX 2. Transport Network Condition Specific Metrics  Jitter 3. Network Policy Specific RSVP Failed, Diffsrv = EF 4. Communication Session Related QoS  Session Setup Delay/Duration 5. Device Sate Specific Metrics  CPU Usage  RAQMON Data Source (RDS) Variable Metrics list Updated using RAQMON PDU  (IP Address, port) Transport Protocol Agnostic SNMP RAQMON Report Collector (RRC) # 1 RAQMON MIB Management Application

  7. RAQMON PDU Overview • One RAQMON Application level PDUs to have “common formats” for reporting statistics • RAQMON PDUs will be transported over existing protocols • RTCP (APP PT = 204 from RFC 1889 or XR Report) • SNMP (NOTIFICATION) • RDS and RRC as Peer-to-Peer entities • RDS reports what “IT” feels to be appropriate for the “application context” • RRC consumes what “IT” feels to be appropriate for the “application context” • RDS  RRC communication is “stateless” • RTCP BYE (if using RTCP between RDS/RRC) • TIMER (if using RTCP and SNMP based RRC) • Issue: MANDATORY for compliance? • RAQMON PDU may run over lossy transport • No Error correction or Recovery at RAQMON level • Complementary to IPFIX charter • RDS/RRC Sessions could be engineered to be lossless

  8. RAQMON PDU for VoIP Data Source Name (DN) Receiver Name (RN) Data Source Address (DA) Receiver Address (RA) Data Source Device Port used Receiver Device Port used Session Setup Date/Time Session Setup delay Session duration Session Setup Status End-to-End Delay (Round Trip) End-to-End Delay (One Way) Inter Arrival Jitter Total number of Packets Received Total number of Packets Sent Total number of Octets Received Total number of Octets Sent Cumulative Packet Loss Packet Loss in Fraction (in %) Source Payload Type Receiver Payload Type Source Layer 2 Priority Destination Layer 2 Priority Source Layer 3 Priority Destination Layer 3 Priority CPU utilization in Fraction (in %) Memory utilization in Fraction (in %) Application Name/version Suggested RAQMON Use Case Examples Based on Application Type • RAQMON PDU for Pagers • Data Source Name (DN) • Receiver Name (RN) • Data Source Address (DA) • Receiver Address (RA) • Data Source Device Port used • Receiver Device Port used • Session Setup Date/Time • Session duration • Session Setup Status • Total number of Packets Sent • Application Name/version • RAQMON PDU for Instant Messaging • Data Source Name (DN) • Receiver Name (RN) • Data Source Address (DA) • Receiver Address (RA) • Data Source Device Port used • Receiver Device Port used • Session Setup Date/Time • Session Setup delay • Session duration • Session Setup Status • Total number of Packets Received • Total number of Packets Sent • Cumulative Packet Loss • Source Layer 3 Priority • Destination Layer 3 Priority • CPU utilization in Fraction (in %) • Memory utilization in Fraction (in %) • Application Name/version

  9. RAQMON PDU Size - over time • Nth PDU for VoIP • Data Source Name (DN) • Receiver Name (RN) • Session Setup Duration • End-to-End Delay (Round Trip) • Inter Arrival Jitter • Total number of Packets Received • Total number of Packets Sent • Cumulative Packet Loss • Packet Loss in Fraction (in %) • CPU utilization in Fraction (in %) • Memory utilization in Fraction (in %) • 2nd PDU for VoIP • Data Source Name (DN) • Receiver Name (RN) • End-to-End Delay (Round Trip) • Inter Arrival Jitter • Total number of Packets Received • Total number of Packets Sent • Cumulative Packet Loss • Packet Loss in Fraction (in %) • CPU utilization in Fraction (in %) • Memory utilization in Fraction (in %) • 1st PDU for VoIP • Data Source Name (DN) • Receiver Name (RN) • Data Source Address (DA) • Receiver Address (RA) • Data Source Device Port used • Receiver Device Port used • Session Setup Date/Time • Session Setup delay • Session Setup Status • End-to-End Delay (Round Trip) • Inter Arrival Jitter • Total number of Packets Received • Total number of Packets Sent • Packet Loss in Fraction (in %) • Source Payload Type • Receiver Payload Type • Source Layer 2 Priority • Destination Layer 2 Priority • Source Layer 3 Priority • Destination Layer 3 Priority • CPU utilization in Fraction (in %) • Memory utilization in Fraction (in %) • Application Name/version ……………….. Avg. MTU ~ 1500 Bytes Recommended NOTIFICATION upto ~ 490 Bytes t t1 t2 tn

  10. One Single RAQMON PDU - changes in draft-02 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | V |PDT = 1|B|T|P|I| RC | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | DSRC | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SMI Enterprise Code = 0 | Report Type = 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ ……………. ……………. ……………. +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | …… | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | SMI Enterprise Code = “VENDOR”| Report Type = 0 | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ …………. …………. …………. RMON Reserved RMON Specified Names/Length “APP filled Value” Vendor Extension Vendor Specified Names/Length “App filled vendor specific Value” RAQMON PDU

  11. Version & subtype PT=204 Length RTCP APP Packet SSRC/CSRC Name=RMON (ascii) RAQMON specific and IANA Registered RAQMON PDU RAQMON PDU Transported Over RTCP or SNMP - changes in draft-02 • RAQMON PDU over RTCP • RAQMON PDUs inside RTCP APP Packets per RFC 1889 • RTCP XR reports can also be used carry RAQMON PDUs • RAQMON PDU over SNMP • Encoding RAQMON PDU by using the RAQMON RDS MIB • Map the RAQMON PDUs on SNMP Notifications transport

  12. RAQMON RDS MIB - changes in draft-02 • New – in draft-ietf-rmonmib-raqmon-pdu-02.txt • Defines mapping of RAQMON PDUs over SNMP notifications transport • raqmonDsNotificationTable - all objects accessible-for-notify • raqmonDsNotification • Mandatory objects • raqmonOneWayEndtoEndDelay • raqmonInterArrivalJitter • raqmonPacketLossFraction • Other objects in raqmonDsNotificationEntry may be added

  13. Congestion Safety - changes in draft-02 • Use TCP as Transport when possible • Scalability of RRCs may be reduced! • If TCP cannot be used following modes of operation are recommended • Constant Transmission Rate • 1 RAQMON PDU every 2 minutes (as good as TCP) • End of communication Session • “Engineered” Constant Rate  e.g. 1 PDU every 5 sec • Retransmission timers with back offs • Ping/Pongs  e.g. Process SNMP INFORMS from RRC • By restricting transmission to MTU Size • No more than 10% network bandwidth be used for RAQMON

  14. RAQMON Extensibility changes in draft-02 • RAQMON PDUs is extensible for future • SMI Enterprise Code (16 bit) • 0 Reserved for RMON WG • Vendor IDs are allowed for extension • http://www.iana.org/assignments/enterprise-numbers • Report Type (16 bit) • Allows Additional Parameters/Profiles to be added • WG can add new Report Type for SMI Enterprise ID = 0 • Vendors can add Any Report Type for Vendor Specific SMI Enterprise ID

  15. RAQMON MIB – changes in draft-02 • Update with PDU structure as defined in the framework draft • Removed all data source specific stuff • Now in the RAQMON-RDS-MIB • Conformance clauses • Clean-up • According to comments in the SF bar-review • Improved definition, DESCRIPTION clauses

  16. Backgrounder

  17. RAQMON Context Setting MG Application level priority (e.g. RSVP for S1, but no RSVP for S2) Applications Applications Streaming Media, Transaction, Bulk data transfer etc RTP / FTP/ HTTP RTP / FTP/ HTTP Various packet level priority ( TOS, DiffServ etc.) TCP/UDP TCP/UDP IP IP IP IP IP Network MAC 802.3 MAC 802.3 MAC IEEE 802.3 MAC IEEE 802.3 PHYSICAL PHYSICAL PHYSICAL PHYSICAL Router Router IP End Points Domain 2 ……. IP End Points Domain N Domain 1 Domain N+1 Multiple Equipment vendors, Multiple geographic locations, Multiple xSPs Control multiple Administrative and Provisioning domain

  18. RAQMON Network Configuration Monitoring Applications via SNMP Video/IP/IM/Voice Corporate Network Application Administrator SNMP Statistics Reported LAN/VPN INTRANET Voice over IP SNMP SNMP Regional Report Collector (Periodic Packets to populate MIB) IP Network Media Gateway SNMP Wireless Gateway Network / Application Service Provider RAQMON MIB Bluetooth

  19. Data Source Name (DN) Receiver Name (RN) Data Source Address (DA) Receiver Address (RA) Data Source Device Port used Receiver Device Port used Session Setup Date/Time Session Setup delay Session duration Session Setup Status End-to-End Delay (Round Trip) End-to-End Delay (One Way) Inter Arrival Jitter Total number of Packets Received Total number of Packets Sent Total number of Octets Received Total number of Octets Sent Cumulative Packet Loss Packet Loss in Fraction (in %) Source Payload Type Receiver Payload Type Source Layer 2 Priority Destination Layer 2 Priority Source Layer 3 Priority Destination Layer 3 Priority CPU utilization in Fraction (in %) Memory utilization in Fraction (in %) Application Name/version Parameters “pushed” from RDS to RRC Current set of suggested metrics ….. Framework Accommodates addition of new parameters to the list …..

More Related