draft-ietf-ippm-btc-framework-03.txt   draft-ietf-ippm-btc-framework-04.txt 
INTERNET-DRAFT Expires May 2001 INTERNET-DRAFT INTERNET-DRAFT Expires May 2001 INTERNET-DRAFT
Network Working Group Matt Mathis Network Working Group Matt Mathis
INTERNET-DRAFT Pittsburgh Supercomputing Center INTERNET-DRAFT Pittsburgh Supercomputing Center
Expiration Date: May 2001 Mark Allman Expiration Date: May 2001 Mark Allman
NASA Glenn/BBN NASA Glenn/BBN
November, 2000 December, 2000
Empirical Bulk Transfer Capacity A Framework for Defining Empirical Bulk Transfer Capacity Metrics
< draft-ietf-ippm-btc-framework-03.txt > < draft-ietf-ippm-btc-framework-04.txt >
Status of this Document Status of this Document
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at line 225 skipping to change at line 225
retransmitted via some more advanced loss recovery algorithm. A retransmitted via some more advanced loss recovery algorithm. A
BTC implementation MUST include a retransmission timer. BTC implementation MUST include a retransmission timer.
Calculating the RTO is subject to a number of details that MUST Calculating the RTO is subject to a number of details that MUST
be defined for each BTC metric. In addition, a BTC metric MUST be defined for each BTC metric. In addition, a BTC metric MUST
define when the clock is set and the granularity of the clock. define when the clock is set and the granularity of the clock.
[RFC2988] specifies the behavior of the retransmission timer. [RFC2988] specifies the behavior of the retransmission timer.
However, there are several details left to the implementer which However, there are several details left to the implementer which
MUST be specified for each BTC metric defined. MUST be specified for each BTC metric defined.
## Likewise, I envision [ABF00] making it to RFC before or around the
## time this is published as an RFC.
##
Note that as new congestion control algorithms are placed on the Note that as new congestion control algorithms are placed on the
standards track they may be incorporated into BTC metrics (e.g., the standards track they may be incorporated into BTC metrics (e.g., the
Limited Transmit algorithm [ABF00]). However, any implementation Limited Transmit algorithm [ABF00]). However, any implementation
decisions provided by the relevant RFCs should be fully specified in decisions provided by the relevant RFCs should be fully specified in
the particular BTC metric. the particular BTC metric.
3 Ancillary Metrics 3 Ancillary Metrics
The following ancillary metrics can provide additional information The following ancillary metrics can provide additional information
about the network and the behavior of the implemented congestion about the network and the behavior of the implemented congestion
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/