70 likes | 194 Views
WG RAQMON Internet-Drafts. RMON MIB WG Meeting San Diego, August 2 nd , 2004. New Round of IETF Drafts as per Last Call Comments and IETF-59 discussions. Take out RTCP transport as recommended by AVT WG Chairs Draft-ietf-rmonmib-raqmon-framework-06.txt Core architecture
E N D
WG RAQMON Internet-Drafts RMON MIB WG Meeting San Diego, August 2nd, 2004
New Round of IETF Drafts as per Last Call Comments and IETF-59 discussions • Take out RTCP transport as recommended by AVT WG Chairs • Draft-ietf-rmonmib-raqmon-framework-06.txt • Core architecture • Transport requirements • Data model • Draft-ietf-rmonmib-raqmon-pdu-06.txt • Becomes SNMP transport draft • RTCP transport out • Draft-ietf-rmonmib-raqmon-mib-04.txt • Fixes, changes, clarifications as per comments • All three drafts went through intensive formatting, editorial and syntax reviews and corrections • Thanks to Randy Presuhn • Boilerplate changes for Intellectual Property
Draft-ietf-rmonmib-raqmon-framework-06.txt • Framework and main RAQMON entities definition • Requirements • For RDS • RRC • Transport Protocol • RAQMON Data Model • Metrics definitions – by reference • Clarifications and text improvement concerning several metrics • Setup delay, jitter, packet loss, one-way end-to-end delay • Eliminate redundancies • Syntax and formatting clean-up
Comments and Open issues wrt.draft-ietf-rmonmib-raqmon-framework-06.txt • Round-trip end-to-end-delay • make distinction between a RTP2RTP interface RTD measurement, and the end-to-end delay at application layer, including jitter buffer • Proposed solution - add this parameter to the participants table in the RAQMON MIB. The information would be provisioned in the collector • OWD – measurement method ‘not practical’ • Proposed resolution – leave it as it is • No RAQMON report is mandatory • Defined by IETF standard • Technology evolves – today’s rocket science may become practical tomorrow
Jitter Terminology comments – OK RFDC 3550 method not accurate – AVT issue Application packets received Clarification comments required – OK Packets loss Does the count include discards? Yes, whenever possible Add MIB object to the RAQMON MIB? CPU and Memory Utilization Multiple processor case Report nothing? Report maximum? Comments and Open issues wrt.draft-ietf-rmonmib-raqmon-framework-06.txt (2)
Draft-ietf-rmonmib-raqmon-pdu-06.txt • RTCP transport taken out • Draft becomes a mapping to SNMP Notifications Draft • Name change • Corrections to the MIB • Jitter type object • Cumulative counters • IPv6 addresses support • use SnmpAddressString instead of Utf8String • Object names changes for clarification purposes • Eliminate information redundant with data model now defined fully in the framework draft • Syntax and formatting clean-up
Draft-ietf-rmonmib-raqmon-mib-04.txt • Updates following Last Call comments • Jitter type object • Cumulative counters • IPv6 addresses support • use SnmpAddressString instead of Utf8String • Object names changes for clarification purposes • change SYNTAX of raqmonParticpantQosCount to Gauge32 • change SYNTAX of raqmonParticpantPeerIndex to RowPointer, and rename • change SYNTAX and range of objects in raqmonQoSTable • explain VACM limitations with the RAQMON table in the security considerations section • DESCRIPTION clarifications • Syntax and formatting clean-up