[Entmib] RE: RFC 4268 on Entity State MIB

"Wijnen, Bert (Bert)" <bwijnen@lucent.com> Tue, 13 December 2005 16:15 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmCoB-0005iE-Qy; Tue, 13 Dec 2005 11:15:19 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EmCoA-0005dK-DK for entmib@megatron.ietf.org; Tue, 13 Dec 2005 11:15:18 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15171 for <entmib@ietf.org>; Tue, 13 Dec 2005 11:13:41 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1EmCoY-0006EY-2R for entmib@ietf.org; Tue, 13 Dec 2005 11:15:43 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by ihemail1.lucent.com (8.12.11/8.12.11) with ESMTP id jBDGEKao025072; Tue, 13 Dec 2005 10:14:20 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2657.72) id <X5BRTWKR>; Tue, 13 Dec 2005 17:14:18 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15508DA09B4@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: entmib@ietf.org
Date: Tue, 13 Dec 2005 17:12:59 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain; charset="iso-8859-1"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 14582b0692e7f70ce7111d04db3781c8
Cc: "David Kessens \(E-mail\)" <david.kessens@nokia.com>
Subject: [Entmib] RE: RFC 4268 on Entity State MIB
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF Entity MIB WG <entmib.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:entmib@ietf.org>
List-Help: <mailto:entmib-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/entmib>, <mailto:entmib-request@ietf.org?subject=subscribe>
Sender: entmib-bounces@ietf.org
Errors-To: entmib-bounces@ietf.org

COngrats and Thanks to the WG and specifically the authors/editors.

With this, the ENTMIB WG has completed all her work.

So I will discuss with the WG chair to close the WG now.

Bert

> -----Original Message-----
> From: ietf-announce-bounces@ietf.org
> [mailto:ietf-announce-bounces@ietf.org]On Behalf Of
> rfc-editor@rfc-editor.org
> Sent: Friday, December 02, 2005 03:09
> To: ietf-announce@ietf.org
> Cc: entmib@ietf.org; rfc-editor@rfc-editor.org
> Subject: RFC 4268 on Entity State MIB
> 
> 
> 
> A new Request for Comments is now available in online RFC libraries.
> 
> 
>         RFC 4268
> 
>         Title:      Entity State MIB
>         Author(s):  S. Chisholm, D. Perkins
>         Status:     Standards Track
>         Date:       November 2005
>         Mailbox:    schishol@nortel.com, dperkins@snmpinfo.com
>         Pages:      19
>         Characters: 40348
>         Updates/Obsoletes/SeeAlso:    None
> 
>         I-D Tag:    draft-ietf-entmib-state-07.txt
> 
>         URL:        ftp://ftp.rfc-editor.org/in-notes/rfc4268.txt
> 
> 
> This memo defines a portion of the Management Information Base (MIB)
> for use with network management protocols in the Internet community.
> In particular, it describes extensions to the Entity MIB to
> provide information about the state of physical entities.
> 
> In addition, this memo defines a set of Textual Conventions to
> represent various states of an entity.  The intent is that these
> Textual Conventions will be imported and used in MIB modules that
> would otherwise define their own representations.
> 
> This document is a product of the Entity MIB Working Group of the
> IETF.
> 
> This is now a Proposed Standard Protocol.
> 
> This document specifies an Internet standards track protocol for
> the Internet community, and requests discussion and suggestions
> for improvements.  Please refer to the current edition of the
> "Internet Official Protocol Standards" (STD 1) for the
> standardization state and status of this protocol.  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.
> 
> 
> 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.
> 

_______________________________________________
Entmib mailing list
Entmib@ietf.org
https://www1.ietf.org/mailman/listinfo/entmib