[rfc-dist] RFC 3763 on One-way Active Measurement Protocol (OWAMP) Requirements

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Fri Apr 30 17:02:16 PDT 2004

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

        RFC 3763

        Title:      One-way Active Measurement Protocol (OWAMP)
        Author(s):  S. Shalunov, B. Teitelbaum
        Status:     Informational
        Date:       April 2004
        Mailbox:    shalunov at internet2.edu, ben at internet2.edu
        Pages:      11
        Characters: 23360
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ippm-owdp-reqs-06.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3763.txt

With growing availability of good time sources to network nodes, it
becomes increasingly possible to measure one-way IP performance
metrics with high precision.  To do so in an interoperable manner, a
common protocol for such measurements is required.  This document
specifies requirements for a one-way active measurement protocol
(OWAMP) standard.  The protocol can measure one-way delay, as well as
other unidirectional characteristics, such as one-way loss.

This document is a product of the IP Performance Metrics Working Group
of the IETF.

This memo provides information for the Internet community.  It does
not specify an Internet standard of any kind.  Distribution of this
memo is unlimited.

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.echo 
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


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list