RFC 2721 on RTFM: Applicability Statement

RFC Editor <rfc-ed@ISI.EDU> Thu, 04 November 1999 19:08 UTC

Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA21081; Thu, 4 Nov 1999 14:08:57 -0500 (EST)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id OAA15657 for ietf-123-outbound.10@ietf.org; Thu, 4 Nov 1999 14:05:02 -0500 (EST)
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 NAA15605 for <all-ietf@loki.ietf.org>; Thu, 4 Nov 1999 13:57:38 -0500 (EST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15570 for <all-ietf@ietf.org>; Thu, 4 Nov 1999 13:57:38 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by boreas.isi.edu (8.8.7/8.8.6) with ESMTP id KAA24540; Thu, 4 Nov 1999 10:57:37 -0800 (PST)
Message-Id: <199911041857.KAA24540@boreas.isi.edu>
To: IETF-Announce:;
Subject: RFC 2721 on RTFM: Applicability Statement
Cc: rfc-ed@ISI.EDU
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Thu, 04 Nov 1999 10:57:37 -0800
From: RFC Editor <rfc-ed@ISI.EDU>

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


        RFC 2721:

        Title:	    RTFM: Applicability Statement
        Author(s):  N. Brownlee
        Status:     Informational
	Date:       October 1999
        Mailbox:    n.brownlee@auckland.ac.nz
        Pages:      10
        Characters: 21200
	Updates/Obsoletes/See Also: None 
        I-D Tag:    draft-ietf-rtfm-applicability-statement-04.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2721.txt


This document provides an overview covering all aspects of Realtime
Traffic Flow Measurement, including its area of applicability and its
limitations.

This document is a product of the Realtime Traffic Flow Measurement
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@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.
ftp://ftp.isi.edu/in-notes/rfc2721.txt"><ftp://ftp.isi.edu/in-notes/rfc2721.txt>