[rfc-dist] BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF Trust

[rfc-editor at rfc-editor.org ([e-mail])]

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

        BCP 111        
        RFC 4841

        Title:      RFC 4181 Update to Recognize 
                    the IETF Trust 
        Author:     C. Heard, Ed.
        Status:     Best Current Practice
        Date:       March 2007
        Mailbox:    heard at pobox.com
        Pages:      3
        Characters: 4414
        Updates:    4841
        SeeAlso:    BCP 111 

        I-D Tag:    draft-heard-rfc4181-update-00.txt

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

This document updates RFC 4181, "Guidelines for Authors and Reviewers
of MIB Documents", to recognize the creation of the IETF Trust.  This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.

This document specifies an Internet Best Current Practices for the
Internet Community, and requests discussion and suggestions for
improvements.  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 at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at 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 at 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 at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...