[rfc-dist] RFC 5357 on A Two-Way Active Measurement Protocol (TWAMP)

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Mon Oct 6 15:22:14 PDT 2008


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

        
        RFC 5357

        Title:      A Two-Way Active Measurement Protocol 
                    (TWAMP) 
        Author:     K. Hedayat, R. Krzanowski,
                    A. Morton, K. Yum,
                    J. Babiarz
        Status:     Standards Track
        Date:       October 2008
        Mailbox:    khedayat at brixnet.com, 
                    roman.krzanowski at verizon.com, 
                    acmorton at att.com,  kyum at juniper.net, 
                    babiarz at nortel.com
        Pages:      26
        Characters: 61960
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-ippm-twamp-09.txt

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

The One-way Active Measurement Protocol (OWAMP), specified in RFC
4656, provides a common protocol for measuring one-way metrics between network devices.  OWAMP can be used bi-directionally to measure one-way
metrics in both directions between two network elements.  However,
it does not accommodate round-trip or two-way measurements.  This
memo specifies a Two-Way Active Measurement Protocol (TWAMP), based
on the OWAMP, that adds two-way or round-trip measurement capabilities.  The TWAMP measurement architecture is usually comprised of two hosts with specific roles, and this allows for some protocol simplifications, making it an attractive alternative in some circumstances.  [STANDARDS TRACK]

This document is a product of the IP Performance Metrics 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 unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

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


The RFC Editor Team
USC/Information Sciences Institute




More information about the rfc-dist mailing list