draft-ietf-ippm-rt-loss-04.txt   draft-ietf-ippm-rt-loss-05.txt 
Network Working Group A. Morton Network Working Group A. Morton
Internet-Draft AT&T Labs Internet-Draft AT&T Labs
Intended status: Standards Track April 12, 2012 Intended status: Standards Track May 8, 2012
Expires: October 14, 2012 Expires: November 9, 2012
Round-trip Packet Loss Metrics Round-trip Packet Loss Metrics
draft-ietf-ippm-rt-loss-04 draft-ietf-ippm-rt-loss-05
Abstract Abstract
Many user applications (and the transport protocols that make them Many user applications (and the transport protocols that make them
possible) require two-way communications. To assess this capability, possible) require two-way communications. To assess this capability,
and to achieve test system simplicity, round-trip loss measurements and to achieve test system simplicity, round-trip loss measurements
are frequently conducted in practice. The Two-Way Active Measurement are frequently conducted in practice. The Two-Way Active Measurement
Protocol specified in RFC 5357 establishes a round-trip loss Protocol specified in RFC 5357 establishes a round-trip loss
measurement capability for the Internet. However, there is currently measurement capability for the Internet. However, there is currently
no metric specified according to the RFC 2330 framework. no metric specified according to the RFC 2330 framework.
skipping to change at page 1, line 45 skipping to change at page 1, line 45
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on October 14, 2012. This Internet-Draft will expire on November 9, 2012.
Copyright Notice Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the Copyright (c) 2012 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
skipping to change at page 10, line 35 skipping to change at page 10, line 35
alignment of sequence numbers applied at the Dst when compared to the alignment of sequence numbers applied at the Dst when compared to the
sender numbers. Measurement implementations MUST address this sender numbers. Measurement implementations MUST address this
possible outcome. possible outcome.
8. Measurement Considerations and Calibration 8. Measurement Considerations and Calibration
Prior to conducting this measurement, the participating hosts MUST be Prior to conducting this measurement, the participating hosts MUST be
configured to send and receive test packets of the chosen Type-P. configured to send and receive test packets of the chosen Type-P.
Standard measurement protocols are capable of this task [RFC5357], Standard measurement protocols are capable of this task [RFC5357],
but any reliable method is sufficient (e.g., if the issues with ICMP but any reliable method is sufficient (e.g., if the issues with ICMP
discussed in section 2.6 of[RFC2681] can be alleviated, then ICMP discussed in Section 2.6 of[RFC2681] can be alleviated, and the
requirements of Section 4.3 and Section 4.4 above are met, then ICMP
could be used). could be used).
Two key features of the host that receives test packets and returns Two key features of the host that receives test packets and returns
them to the originating host are described in section 4.2 of them to the originating host are described in section 4.2 of
[RFC5357] . Every received test packet MUST result in a responding [RFC5357] . Every received test packet MUST result in a responding
packet, and the response MUST be generated as quickly as possible. packet, and the response MUST be generated as quickly as possible.
This implies that interface buffers will be serviced promptly, and This implies that interface buffers will be serviced promptly, and
that buffer discards will be extremely rare. These features of the that buffer discards will be extremely rare. These features of the
measurement equipment MUST be calibrated according to Section 3.7.3 measurement equipment MUST be calibrated according to Section 3.7.3
of [RFC2679], when operating under a representative measurement load of [RFC2679], when operating under a representative measurement load
 End of changes. 4 change blocks. 
5 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/