RFC 2678 on IPPM Metrics for Measuring Connectivity
RFC Editor <rfc-ed@ISI.EDU> Wed, 08 September 1999 18:17 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA24736; Wed, 8 Sep 1999 14:17:48 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA22422 for ietf-123-outbound.10@ietf.org; Wed, 8 Sep 1999 14:05:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id NAA22356 for <all-ietf@loki.ietf.org>; Wed, 8 Sep 1999 13:56:41 -0400 (EDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA23986 for <all-ietf@ietf.org>; Wed, 8 Sep 1999 13:56:40 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA18257; Wed, 8 Sep 1999 10:56:35 -0700 (PDT)
Message-Id: <199909081756.KAA18257@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2678 on IPPM Metrics for Measuring Connectivity
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 08 Sep 1999 10:56:35 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries.
RFC 2678:
Title: IPPM Metrics for Measuring Connectivity
Author(s): J. Mahdavi, V. Paxson
Status: Standards Track
Date: September 1999
Mailbox: mahdavi@psc.edu, vern@ee.lbl.gov
Pages: 10
Characters: 18087
Obsoletes: 2498
I-D Tag: RFC2498
URL: ftp://ftp.isi.edu/in-notes/rfc2678.txt
This memo defines a series of metrics for connectivity between a pair
of Internet hosts.
This document is a product of the IP Performance Metrics Working Group
of the IETF.
This is now a Proposed Standard Protocol.
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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG. Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@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@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@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.