Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation

"David T. Perkins" <dperkins@dsperkins.com> Mon, 16 August 2004 17:00 UTC

Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15362 for <entmib-archive@lists.ietf.org>; Mon, 16 Aug 2004 13:00:32 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwko3-0000VQ-M9; Mon, 16 Aug 2004 12:57:59 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Bwkk1-0008WP-8P for entmib@megatron.ietf.org; Mon, 16 Aug 2004 12:53:49 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA15102 for <entmib@ietf.org>; Mon, 16 Aug 2004 12:53:46 -0400 (EDT)
Received: from shell4.bayarea.net ([209.128.82.1]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Bwkpp-0004ZX-QA for entmib@ietf.org; Mon, 16 Aug 2004 12:59:51 -0400
Received: from NB5.dsperkins.com (shell4.bayarea.net [209.128.82.1]) (authenticated bits=0) by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id i7GGrbfW009978; Mon, 16 Aug 2004 09:53:38 -0700
Message-Id: <5.2.0.9.2.20040816094625.022f49c0@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
Date: Mon, 16 Aug 2004 09:53:38 -0700
To: j.schoenwaelder@iu-bremen.de, Margaret Wasserman <margaret@thingmagic.com>
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: Re: [Entmib] CONSENSUS CHECK: Undo entAliasMapping deprecation
In-Reply-To: <20040816082053.GD1761@iu-bremen.de>
References: <p0602041fbd39fdb5fff2@[130.129.130.34]> <p0602041fbd39fdb5fff2@[130.129.130.34]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2
Cc: entmib@ietf.org
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

HI,

The below sounds like a good suggestion to me.

At 10:20 AM 8/16/2004 +0200, Juergen Schoenwaelder wrote:
>On Fri, Aug 06, 2004 at 11:41:02PM -0400, Margaret Wasserman wrote:
>
>> During the Entity MIB meeting at IETF 60 in San Diego, there was 
>> consensus in the room  for the following course of action:
>> 
>> (1) Pull the Entity State MIB document out of IESG processing 
>> (currently submitted for publication as a Draft Standard)
>> 
>> (2) Update the document to undo the deprecation of the 
>> entAliasMapping identifier, and
>> 
>> (3) Re-submit the Entity MIB to the IESG for publication as a 
>> Proposed Standard.
>> 
>> We now need to confirm this consensus on the mailing list.  Are there 
>> any objections to taking this course of action?  Other comments?
>
>Sounds like a good plan to me. But if we recycle at Proposed, why do 
>we then not simply put the entSupplPhysicalManufacturingDate and the
>entSupplPhysicalManufacturerInfo objects into the entPhysicalEntry
>where they actually belong? A new compliance statement would deal
>with these additions so existing implementations that comply to
>entity2Compliance would not be affected.
>
>/js
Regards,
/david t. perkins 


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