From mailman-owner@ietf.org  Fri Feb  1 05:46:24 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA14338
	for <entmib-archive@odin.ietf.org>; Fri, 1 Feb 2002 05:46:23 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id FAA00186
	for <entmib-archive@lists.ietf.org>; Fri, 1 Feb 2002 05:46:26 -0500 (EST)
Date: Fri, 1 Feb 2002 05:46:26 -0500 (EST)
Message-Id: <200202011046.FAA00186@optimus.ietf.org>
From: mailman-owner@ietf.org
Subject: ietf.org mailing list memberships reminder
To: entmib-archive@ietf.org
X-No-Archive: yes
Precedence: bulk
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: Session Initiation Protocol <sip.ietf.org>

This is a reminder, sent out once a month, about your ietf.org mailing
list memberships.  It includes your subscription info and how to use
it to change it or unsubscribe from a list.

You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.

In addition to the URL interfaces, you can also use email to make such
changes.  For more info, send a message to the '-request' address of
the list (for example, entmib-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

If you have questions, problems, comments, etc, send them to
mailman-owner@ietf.org.  Thanks!

Passwords for entmib-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
entmib@ietf.org                          CNIo      
https://www1.ietf.org/mailman/options/entmib/entmib-archive@lists.ietf.org


From entmib-admin@ietf.org  Thu Feb  7 04:56:33 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23902
	for <entmib-archive@odin.ietf.org>; Thu, 7 Feb 2002 04:56:33 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11234;
	Thu, 7 Feb 2002 04:56:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11201
	for <entmib@optimus.ietf.org>; Thu, 7 Feb 2002 04:56:29 -0500 (EST)
Received: from mel-rto1.wanadoo.fr (smtp-out-1.wanadoo.fr [193.252.19.188])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23896
	for <entmib@ietf.org>; Thu, 7 Feb 2002 04:56:26 -0500 (EST)
From: sgonnet@edevice.com
Received: from mel-rta1.wanadoo.fr (193.252.19.150) by mel-rto1.wanadoo.fr; 7 Feb 2002 10:55:59 +0100
Received: from srvnotes (193.251.6.2) by mel-rta1.wanadoo.fr; 7 Feb 2002 10:55:27 +0100
To: entmib@ietf.org
X-Mailer: Lotus Notes Release 5.0.1 (Intl) 11 Aout 1999
Message-ID: <OFD3978788.A6A839FB-ONC1256B59.0032D814@LocalDomain>
Date: Thu, 7 Feb 2002 10:55:26 +0100
X-MIMETrack: Serialize by Router on srvnotes/EDEVICE(Release 5.07a |May 14, 2001) at 07/02/2002
 10:55:28
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Entmib] Entity mib to configure non TCP/IP devices ?
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

Hi,

eDevice offers TCP/IP connectivity solution for light devices through
Ethernet, PSTN and GSM networks. The scope of application goes from vending
machines to light VoIP terminals or utility meters, displays...

We currently look for the best and most standard way to configure and
access these legacy devices through the TCP/IP network. As our software
(i.e. the TCP/IP core) will be soon accessed through a standard MIB-II, we
think about using SNMP to extend the configuration till the non TCP/IP
device.

May the entity mib fulfill this requirement?

Is the list of legal values of PhysicalClass fixed or can we imagine to add
new values (like utility meter, vending machine, serial device...)?

Thanks for your help

Stefan GONNET
Mob : +33 6 22 04 89 03
Technical Support Engineer

************************************************************************
eDevice Technology..................The Internet Enabler
http://www.edevice.com
Parc Cadera Sud, Bat P2     33700 Merignac    FRANCE
Tel : +33 5 56 12 77 77    Fax : +33 5 56 12 90 00

420 Lexington Avenue, Suite 2300     New York, NY 10170   USA
Tel: +1 (212) 856 0000    Fax: +1 (212) 856 9339
************************************************************************
Unless otherwise specified, the recipient will use the Confidential
Information of eDevice only for the purposes of a potential business
relationship. The recipient will not copy eDevice's Confidential
Information without the prior written consent of eDevice.



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


From daemon@optimus.ietf.org  Thu Feb  7 04:56:34 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23912
	for <entmib-archive@odin.ietf.org>; Thu, 7 Feb 2002 04:56:34 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id EAA11258
	for entmib-archive@odin.ietf.org; Thu, 7 Feb 2002 04:56:36 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11234;
	Thu, 7 Feb 2002 04:56:31 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id EAA11201
	for <entmib@optimus.ietf.org>; Thu, 7 Feb 2002 04:56:29 -0500 (EST)
Received: from mel-rto1.wanadoo.fr (smtp-out-1.wanadoo.fr [193.252.19.188])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23896
	for <entmib@ietf.org>; Thu, 7 Feb 2002 04:56:26 -0500 (EST)
From: sgonnet@edevice.com
Received: from mel-rta1.wanadoo.fr (193.252.19.150) by mel-rto1.wanadoo.fr; 7 Feb 2002 10:55:59 +0100
Received: from srvnotes (193.251.6.2) by mel-rta1.wanadoo.fr; 7 Feb 2002 10:55:27 +0100
To: entmib@ietf.org
X-Mailer: Lotus Notes Release 5.0.1 (Intl) 11 Aout 1999
Message-ID: <OFD3978788.A6A839FB-ONC1256B59.0032D814@LocalDomain>
Date: Thu, 7 Feb 2002 10:55:26 +0100
X-MIMETrack: Serialize by Router on srvnotes/EDEVICE(Release 5.07a |May 14, 2001) at 07/02/2002
 10:55:28
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Subject: [Entmib] Entity mib to configure non TCP/IP devices ?
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

Hi,

eDevice offers TCP/IP connectivity solution for light devices through
Ethernet, PSTN and GSM networks. The scope of application goes from vending
machines to light VoIP terminals or utility meters, displays...

We currently look for the best and most standard way to configure and
access these legacy devices through the TCP/IP network. As our software
(i.e. the TCP/IP core) will be soon accessed through a standard MIB-II, we
think about using SNMP to extend the configuration till the non TCP/IP
device.

May the entity mib fulfill this requirement?

Is the list of legal values of PhysicalClass fixed or can we imagine to add
new values (like utility meter, vending machine, serial device...)?

Thanks for your help

Stefan GONNET
Mob : +33 6 22 04 89 03
Technical Support Engineer

************************************************************************
eDevice Technology..................The Internet Enabler
http://www.edevice.com
Parc Cadera Sud, Bat P2     33700 Merignac    FRANCE
Tel : +33 5 56 12 77 77    Fax : +33 5 56 12 90 00

420 Lexington Avenue, Suite 2300     New York, NY 10170   USA
Tel: +1 (212) 856 0000    Fax: +1 (212) 856 9339
************************************************************************
Unless otherwise specified, the recipient will use the Confidential
Information of eDevice only for the purposes of a potential business
relationship. The recipient will not copy eDevice's Confidential
Information without the prior written consent of eDevice.



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



From entmib-admin@ietf.org  Mon Feb 11 08:26:59 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00748
	for <entmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 08:26:59 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07209;
	Mon, 11 Feb 2002 08:26:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07183
	for <entmib@ns.ietf.org>; Mon, 11 Feb 2002 08:26:49 -0500 (EST)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00735
	for <entmib@ietf.org>; Mon, 11 Feb 2002 08:26:48 -0500 (EST)
Received: from hansa.ibr.cs.tu-bs.de (root@hansa.ibr.cs.tu-bs.de [134.169.34.81])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1BDQnBt002586
	for <entmib@ietf.org>; Mon, 11 Feb 2002 14:26:49 +0100
Received: from hansa.ibr.cs.tu-bs.de (localhost [127.0.0.1])
	by hansa.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -5) with ESMTP id g1BDQnhu030371
	for <entmib@ietf.org>; Mon, 11 Feb 2002 14:26:49 +0100
Received: (from schoenw@localhost)
	by hansa.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -5) id g1BDQnTa030368;
	Mon, 11 Feb 2002 14:26:49 +0100
Date: Mon, 11 Feb 2002 14:26:49 +0100
Message-Id: <200202111326.g1BDQnTa030368@hansa.ibr.cs.tu-bs.de>
X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: entmib@ietf.org
In-reply-to: message from Juergen Schoenwaelder on Thu, 13 Dec 2001 19:39:04
	+0100
Subject: Re: [Entmib] RFC 2737 additions
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


>>>>> Juergen Schoenwaelder writes:

Juergen> Here is the PhysicalIndexOrZero addition to the
Juergen> ENTITY-MIB. It is remarkably similar to the
Juergen> InterfaceIndexOrZero TC.

I just discovered that once we have this PhysicalIndexOrZero TC, we
can actually use it for entPhysicalContainedIn. (I am sending this to
the list just to get this recorded somewhere. ;-)

/js

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


From daemon@ns.ietf.org  Mon Feb 11 08:27:02 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00777
	for <entmib-archive@odin.ietf.org>; Mon, 11 Feb 2002 08:27:02 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id IAA07227
	for entmib-archive@odin.ietf.org; Mon, 11 Feb 2002 08:26:59 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07209;
	Mon, 11 Feb 2002 08:26:51 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id IAA07183
	for <entmib@ns.ietf.org>; Mon, 11 Feb 2002 08:26:49 -0500 (EST)
Received: from agitator.ibr.cs.tu-bs.de (agitator.ibr.cs.tu-bs.de [134.169.34.18])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA00735
	for <entmib@ietf.org>; Mon, 11 Feb 2002 08:26:48 -0500 (EST)
Received: from hansa.ibr.cs.tu-bs.de (root@hansa.ibr.cs.tu-bs.de [134.169.34.81])
	by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1BDQnBt002586
	for <entmib@ietf.org>; Mon, 11 Feb 2002 14:26:49 +0100
Received: from hansa.ibr.cs.tu-bs.de (localhost [127.0.0.1])
	by hansa.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -5) with ESMTP id g1BDQnhu030371
	for <entmib@ietf.org>; Mon, 11 Feb 2002 14:26:49 +0100
Received: (from schoenw@localhost)
	by hansa.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -5) id g1BDQnTa030368;
	Mon, 11 Feb 2002 14:26:49 +0100
Date: Mon, 11 Feb 2002 14:26:49 +0100
Message-Id: <200202111326.g1BDQnTa030368@hansa.ibr.cs.tu-bs.de>
X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: entmib@ietf.org
In-reply-to: message from Juergen Schoenwaelder on Thu, 13 Dec 2001 19:39:04
	+0100
Subject: Re: [Entmib] RFC 2737 additions
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


>>>>> Juergen Schoenwaelder writes:

Juergen> Here is the PhysicalIndexOrZero addition to the
Juergen> ENTITY-MIB. It is remarkably similar to the
Juergen> InterfaceIndexOrZero TC.

I just discovered that once we have this PhysicalIndexOrZero TC, we
can actually use it for entPhysicalContainedIn. (I am sending this to
the list just to get this recorded somewhere. ;-)

/js

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



From entmib-admin@ietf.org  Tue Feb 12 15:19:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24845
	for <entmib-archive@odin.ietf.org>; Tue, 12 Feb 2002 15:19:26 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA12002;
	Tue, 12 Feb 2002 15:19:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA11977
	for <entmib@optimus.ietf.org>; Tue, 12 Feb 2002 15:19:14 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24840
	for <entmib@ietf.org>; Tue, 12 Feb 2002 15:19:11 -0500 (EST)
Received: from PC2.cisco.com (sjc-vpn1-646.cisco.com [10.21.98.134]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id MAA06740; Tue, 12 Feb 2002 12:18:19 -0800 (PST)
Message-Id: <5.1.0.14.2.20020212121406.023749b0@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 12 Feb 2002 12:16:28 -0800
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] RFC 2737 additions
Cc: entmib@ietf.org
In-Reply-To: <200202111326.g1BDQnTa030368@hansa.ibr.cs.tu-bs.de>
References: <message from Juergen Schoenwaelder on Thu, 13 Dec 2001 19:39:04 +0100>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

At 05:26 AM 2/11/2002, Juergen Schoenwaelder wrote:

>>>>>> Juergen Schoenwaelder writes:
>
>Juergen> Here is the PhysicalIndexOrZero addition to the
>Juergen> ENTITY-MIB. It is remarkably similar to the
>Juergen> InterfaceIndexOrZero TC.
>
>I just discovered that once we have this PhysicalIndexOrZero TC, we
>can actually use it for entPhysicalContainedIn. (I am sending this to
>the list just to get this recorded somewhere. ;-)

I thought the WG agreed in SLC not to republish RFC 2737,
due to insufficient interest in any of the proposed changes.

>/js

Andy


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


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


From daemon@optimus.ietf.org  Tue Feb 12 15:19:27 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24855
	for <entmib-archive@odin.ietf.org>; Tue, 12 Feb 2002 15:19:27 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id PAA12018
	for entmib-archive@odin.ietf.org; Tue, 12 Feb 2002 15:19:29 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA12002;
	Tue, 12 Feb 2002 15:19:15 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id PAA11977
	for <entmib@optimus.ietf.org>; Tue, 12 Feb 2002 15:19:14 -0500 (EST)
Received: from nisser.cisco.com (nisser.cisco.com [171.71.176.85])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24840
	for <entmib@ietf.org>; Tue, 12 Feb 2002 15:19:11 -0500 (EST)
Received: from PC2.cisco.com (sjc-vpn1-646.cisco.com [10.21.98.134]) by nisser.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id MAA06740; Tue, 12 Feb 2002 12:18:19 -0800 (PST)
Message-Id: <5.1.0.14.2.20020212121406.023749b0@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Tue, 12 Feb 2002 12:16:28 -0800
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] RFC 2737 additions
Cc: entmib@ietf.org
In-Reply-To: <200202111326.g1BDQnTa030368@hansa.ibr.cs.tu-bs.de>
References: <message from Juergen Schoenwaelder on Thu, 13 Dec 2001 19:39:04 +0100>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org

At 05:26 AM 2/11/2002, Juergen Schoenwaelder wrote:

>>>>>> Juergen Schoenwaelder writes:
>
>Juergen> Here is the PhysicalIndexOrZero addition to the
>Juergen> ENTITY-MIB. It is remarkably similar to the
>Juergen> InterfaceIndexOrZero TC.
>
>I just discovered that once we have this PhysicalIndexOrZero TC, we
>can actually use it for entPhysicalContainedIn. (I am sending this to
>the list just to get this recorded somewhere. ;-)

I thought the WG agreed in SLC not to republish RFC 2737,
due to insufficient interest in any of the proposed changes.

>/js

Andy


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


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



From entmib-admin@ietf.org  Fri Feb 15 13:47:49 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15269
	for <entmib-archive@odin.ietf.org>; Fri, 15 Feb 2002 13:47:49 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10096;
	Fri, 15 Feb 2002 13:47:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10076
	for <entmib@optimus.ietf.org>; Fri, 15 Feb 2002 13:47:37 -0500 (EST)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15259
	for <entmib@ietf.org>; Fri, 15 Feb 2002 13:47:33 -0500 (EST)
Received: from kenawang ([192.168.1.5])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id KAA21224
	for <entmib@ietf.org>; Fri, 15 Feb 2002 10:46:54 -0800 (PST)
Message-Id: <4.2.2.20020215133829.02fbd2d0@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 15 Feb 2002 13:47:19 -0500
To: entmib@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Entmib] Working Group Status
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


Hi All,

Our new charter has been approved and posted on the IETF
web site.  I have already sent e-mail to update our 
completed milestones.

The following milestones will be marked as "done":

	Apr 01 Evaluate status of Entity MIB and collect 
		implementation and interoperability reports
	Sep 01 Recommend to the IESG if Entity MIB can be elevated 
		to Draft Standard.
	Dec 01 Post Internet-Draft for Sensor Entity MIB

We collected reports, determined that there is insufficient
experience to elevate RFC 2737 to Draft Standard, and recommended
against that elevation.  We are scheduled to gather further
information and reconsider the status of RFC 2737 in July 02.

We have an active Internet-Draft for the Sensor Entity MIB, 
thanks to Andy, Dan and KC.

There are three milestones that we should be working on
right now:

	Jan 02 Determine if the Entity MIB should be modified to 
		resolve any open issues
	Feb 02 Re-cycle the updated Entity MIB at proposed standard, 
		if necessary
	Apr 02 Submit final version of Internet-Draft for Sensor 
		Entity MIB for consideration as a Proposed Standard

At the SLC meeting, it was the clear consensus of the people
in the room that we should not update RFC 2737.  We preferred
to leave it as-is, and wait for further implementation 
experience.

Are there any objections to that plan from the list?  If not, we
will leave RFC 2737 as-is.

Are there any comments on our Sensor Entity MIB draft?  If possible,
I'd like to be ready for last call to move this document to PS, at
the end of our meeting in Minneapolis.

Thanks,
Margaret






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


From daemon@optimus.ietf.org  Fri Feb 15 13:47:50 2002
Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15279
	for <entmib-archive@odin.ietf.org>; Fri, 15 Feb 2002 13:47:49 -0500 (EST)
Received: (from daemon@localhost)
	by optimus.ietf.org (8.9.1a/8.9.1) id NAA10133
	for entmib-archive@odin.ietf.org; Fri, 15 Feb 2002 13:47:51 -0500 (EST)
Received: from optimus.ietf.org (localhost [127.0.0.1])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10096;
	Fri, 15 Feb 2002 13:47:38 -0500 (EST)
Received: from ietf.org (odin [132.151.1.176])
	by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id NAA10076
	for <entmib@optimus.ietf.org>; Fri, 15 Feb 2002 13:47:37 -0500 (EST)
Received: from mail.wrs.com (unknown-1-11.windriver.com [147.11.1.11])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15259
	for <entmib@ietf.org>; Fri, 15 Feb 2002 13:47:33 -0500 (EST)
Received: from kenawang ([192.168.1.5])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id KAA21224
	for <entmib@ietf.org>; Fri, 15 Feb 2002 10:46:54 -0800 (PST)
Message-Id: <4.2.2.20020215133829.02fbd2d0@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 
Date: Fri, 15 Feb 2002 13:47:19 -0500
To: entmib@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [Entmib] Working Group Status
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: IETF Entity MIB WG <entmib.ietf.org>
X-BeenThere: entmib@ietf.org


Hi All,

Our new charter has been approved and posted on the IETF
web site.  I have already sent e-mail to update our 
completed milestones.

The following milestones will be marked as "done":

	Apr 01 Evaluate status of Entity MIB and collect 
		implementation and interoperability reports
	Sep 01 Recommend to the IESG if Entity MIB can be elevated 
		to Draft Standard.
	Dec 01 Post Internet-Draft for Sensor Entity MIB

We collected reports, determined that there is insufficient
experience to elevate RFC 2737 to Draft Standard, and recommended
against that elevation.  We are scheduled to gather further
information and reconsider the status of RFC 2737 in July 02.

We have an active Internet-Draft for the Sensor Entity MIB, 
thanks to Andy, Dan and KC.

There are three milestones that we should be working on
right now:

	Jan 02 Determine if the Entity MIB should be modified to 
		resolve any open issues
	Feb 02 Re-cycle the updated Entity MIB at proposed standard, 
		if necessary
	Apr 02 Submit final version of Internet-Draft for Sensor 
		Entity MIB for consideration as a Proposed Standard

At the SLC meeting, it was the clear consensus of the people
in the room that we should not update RFC 2737.  We preferred
to leave it as-is, and wait for further implementation 
experience.

Are there any objections to that plan from the list?  If not, we
will leave RFC 2737 as-is.

Are there any comments on our Sensor Entity MIB draft?  If possible,
I'd like to be ready for last call to move this document to PS, at
the end of our meeting in Minneapolis.

Thanks,
Margaret






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



