[rfc-dist] RFC 4710 on Real-time Application Quality-of-Service Monitoring (RAQMON) Framework

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Thu Oct 19 18:32:07 PDT 2006

A new Request for Comments is now available in online RFC libraries.

        RFC 4710

        Title:      Real-time Application Quality-of-Service Monitoring 
                    (RAQMON) Framework 
        Author:     A. Siddiqui, D. Romascanu,
                    E. Golovinsky
        Status:     Standards Track
        Date:       October 2006
        Mailbox:    anwars at avaya.com, 
                    dromasca at avaya.com, 
                    gene at alertlogic.net
        Pages:      36
        Characters: 86403
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmonmib-raqmon-framework-16.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4710.txt

There is a need to monitor end-devices such as IP phones, pagers,
Instant Messaging clients, mobile phones, and various other handheld
computing devices.  This memo extends the remote network monitoring
(RMON) family of specifications to allow real-time quality-of-service
(QoS) monitoring of various applications that run on these devices
and allows this information to be integrated with the RMON family
using the Simple Network Management Protocol (SNMP).  This memo
defines the framework, architecture, relevant metrics, and transport
requirements for real-time QoS monitoring of applications.  [STANDARDS 

This document is a product of the Remote Network Monitoring
Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and 
suggestions for improvements.Please refer to the current edition of the 
Internet Official Protocol Standards (STD 1) for the standardization 
state and status of this protocol.  Distribution of this memo is 

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


More information about the rfc-dist mailing list