RFC 5000 on Internet Official Protocol Standards

rfc-editor@rfc-editor.org Thu, 08 May 2008 23:25 UTC

Return-Path: <ietf-announce-bounces@ietf.org>
X-Original-To: ietf-announce-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-announce-archive@core3.amsl.com
Received: from [] (localhost []) by core3.amsl.com (Postfix) with ESMTP id E9CE53A6BB5; Thu, 8 May 2008 16:25:02 -0700 (PDT)
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id AC70C3A6BB5 for <ietf-announce@core3.amsl.com>; Thu, 8 May 2008 16:25:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[AWL=0.100, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id p-1ygHAGYZoS for <ietf-announce@core3.amsl.com>; Thu, 8 May 2008 16:24:59 -0700 (PDT)
Received: from bosco.isi.edu (bosco.isi.edu []) by core3.amsl.com (Postfix) with ESMTP id EAF293A67F2 for <ietf-announce@ietf.org>; Thu, 8 May 2008 16:24:59 -0700 (PDT)
Received: by bosco.isi.edu (Postfix, from userid 70) id 80A7D129742; Thu, 8 May 2008 16:24:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5000 on Internet Official Protocol Standards
From: rfc-editor@rfc-editor.org
Message-Id: <20080508232458.80A7D129742@bosco.isi.edu>
Date: Thu, 08 May 2008 16:24:58 -0700
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF Announcements <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org

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

        RFC 5000

        Title:      Internet Official Protocol Standards 
        Author:     RFC Editor
        Status:     Informational
        Date:       May 2008
        Mailbox:    rfc-editor@rfc-editor.org
        Pages:      75
        Characters: 222566
        Obsoletes:  RFC3700
        See Also:   STD0001

        I-D Tag:    draft-rfc-5000.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5000.txt

This document is published by the RFC Editor to provide a summary of
the current standards protocols (as of 18 February 2008).  It lists
those official protocol standards, Best Current Practice, and Experimental
RFCs that have not been obsoleted; it is not a complete index to the
RFC series.  Newly published RFCs and RFCs whose status has
changed are starred.

For an up-to-date list, see http://www.rfc-editor.org/rfcxx00.html,
which is updated daily.  This memo provides information for the Internet 

INFORMATIONAL: 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

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.

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.

The RFC Editor Team
USC/Information Sciences Institute


IETF-Announce mailing list