RFC 3700 on Internet Official Protocol Standards

rfc-editor@rfc-editor.org Sat, 31 July 2004 00:13 UTC

Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10240; Fri, 30 Jul 2004 20:13:44 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqhXn-00088o-0n; Fri, 30 Jul 2004 20:16:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqhPH-0005rN-AY; Fri, 30 Jul 2004 20:07:23 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BqhOd-0005iF-Nu for ietf-announce@megatron.ietf.org; Fri, 30 Jul 2004 20:06:43 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA10017 for <ietf-announce@ietf.org>; Fri, 30 Jul 2004 20:06:42 -0400 (EDT)
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1BqhQx-00083t-Od for ietf-announce@ietf.org; Fri, 30 Jul 2004 20:09:08 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6V061J00520; Fri, 30 Jul 2004 17:06:01 -0700 (PDT)
Message-Id: <200407310006.i6V061J00520@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Fri, 30 Jul 2004 17:06:01 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43
Cc: rfc-editor@rfc-editor.org
Subject: RFC 3700 on Internet Official Protocol Standards
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Score: -14.6 (--------------)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86

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


        RFC 3700

        Title:      Internet Official Protocol Standards
        Author(s):  J. Reynolds, Ed., S. Ginoza, Ed.
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    jkrey@ISI.EDU, ginoza@ISI.EDU
        Pages:      54
        Characters: 148273
        Obsoletes:  3600

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3700.txt


This memo contains a snapshot of the state of standardization of
protocols used in the Internet as of July 22, 2004.  It lists
official protocol standards and Best Current Practice RFCs; it is not
a complete index to the RFC series.  The latest version of this memo
is designated STD 1.

This is now a Standard Protocol.

This memo is an Internet Standard.  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/rfc3700.txt"><ftp://ftp.isi.edu/in-notes/rfc3700.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce