[MIB-DOCTORS] FW: BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF Trust

"Romascanu, Dan \(Dan\)" <dromasca@avaya.com> Wed, 28 March 2007 11:27 UTC

Return-path: <mib-doctors-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWWJL-0003b5-Ho; Wed, 28 Mar 2007 07:27:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HWWJK-0003av-Fg; Wed, 28 Mar 2007 07:27:26 -0400
Received: from co300216-co-outbound.net.avaya.com ([198.152.13.100] helo=co300216-co-outbound.avaya.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HWWJ9-0003VE-HV; Wed, 28 Mar 2007 07:27:26 -0400
Received: from unknown (HELO IS0004AVEXU1.global.avaya.com) ([135.64.105.51]) by co300216-co-outbound.avaya.com with ESMTP; 28 Mar 2007 07:30:12 -0400
X-IronPort-AV: i="4.14,340,1170651600"; d="scan'208"; a="69765065:sNHT21135527"
X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0
content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Date: Wed, 28 Mar 2007 13:26:30 +0200
Message-ID: <AAB4B3D3CF0F454F98272CBE187FDE2F0C9615E3@is0004avexu1.global.avaya.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF Trust
Thread-Index: Acdwr9OvwJCqC0TRQWu4JS/K0k1wYAAe/cYQ
From: "Romascanu, Dan (Dan)" <dromasca@avaya.com>
To: mib-doctors@ietf.org, ops-area@ietf.org
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc:
Subject: [MIB-DOCTORS] FW: BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF Trust
X-BeenThere: mib-doctors@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: MIB Doctors list <mib-doctors.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/mib-doctors>
List-Post: <mailto:mib-doctors@ietf.org>
List-Help: <mailto:mib-doctors-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/mib-doctors>, <mailto:mib-doctors-request@ietf.org?subject=subscribe>
Errors-To: mib-doctors-bounces@ietf.org

 
Congratulations and thanks to Mike and to the people who supported the
fast track creation and approval of this document. 

Dan


 

-----Original Message-----
From: rfc-editor@rfc-editor.org [mailto:rfc-editor@rfc-editor.org] 
Sent: Tuesday, March 27, 2007 10:22 PM
To: ietf-announce@ietf.org; rfc-dist@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Subject: BCP 111, RFC 4841 on RFC 4181 Update to Recognize the IETF
Trust


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@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@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.

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
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
MIB-DOCTORS mailing list
MIB-DOCTORS@ietf.org
https://www1.ietf.org/mailman/listinfo/mib-doctors