From mailman-bounces@ietf.org  Sat Jan  1 08:03:04 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA17189
	for <entmib-archive@lists.ietf.org>; Sat, 1 Jan 2005 08:03:03 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CkgRN-0002YR-6l
	for entmib-archive@lists.ietf.org; Sat, 01 Jan 2005 05:24:57 -0500
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@ietf.org
To: entmib-archive@ietf.org
X-No-Archive: yes
Message-ID: <mailman.26474.1104574219.4100.mailman@lists.ietf.org>
Date: Sat, 01 Jan 2005 05:10:19 -0500
Precedence: bulk
X-BeenThere: mailman@lists.ietf.org
X-Mailman-Version: 2.1.5
List-Id: Mailman site list <mailman.lists.ietf.org>
X-List-Administrivia: yes
Sender: mailman-bounces@ietf.org
Errors-To: mailman-bounces@ietf.org
Content-Transfer-Encoding: 7bit

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, mailman-request@ietf.org) containing just the
word 'help' in the message body, and an email message will be sent to
you with instructions.

**********************************************************************

NOTE WELL:

Any submission to the IETF intended by the Contributor for publication
as all or part of an IETF Internet-Draft or RFC and any statement made
within the context of an IETF activity is considered an "IETF
Contribution". Such statements include oral statements in IETF
sessions, as well as written and electronic communications made at any
time or place, which are addressed to:

o the IETF plenary session, o any IETF working group or portion
thereof, o the IESG, or any member thereof on behalf of the IESG, o
the IAB or any member thereof on behalf of the IAB, o any IETF mailing
list, including the IETF list itself, any working group
  or design team list, or any other list functioning under IETF
auspices,
o the RFC Editor or the Internet-Drafts function

All IETF Contributions are subject to the rules of RFC 3667 and RFC
3668.

Statements made outside of an IETF session, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not IETF Contributions in the context
of this notice.

Please consult RFC 3667 for details.

*******************************************************************************


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%40lists.ietf.org


From entmib-bounces@ietf.org  Mon Jan  3 23:42:11 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA23908
	for <entmib-archive@lists.ietf.org>; Mon, 3 Jan 2005 23:42:11 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClgV7-0008IN-EA; Mon, 03 Jan 2005 23:40:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClgNx-0004tW-96
	for entmib@megatron.ietf.org; Mon, 03 Jan 2005 23:33:33 -0500
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 XAA23310
	for <entmib@ietf.org>; Mon, 3 Jan 2005 23:33:30 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ClgaF-0003PV-EM
	for entmib@ietf.org; Mon, 03 Jan 2005 23:46:15 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j044X1VA018730
	for <entmib@ietf.org>; Mon, 3 Jan 2005 20:33:01 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j044X2vk031157;
	Mon, 3 Jan 2005 20:33:02 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j044X1Bl031154; Mon, 3 Jan 2005 20:33:02 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Mon, 3 Jan 2005 20:33:01 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: entmib@ietf.org
Message-ID: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a
Subject: [Entmib] Entity MIB Publication Schedule
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

All,

I intend to post an updated version of the MIB review guidelines
shortly, and one of the normative references is the update to
RFC2737 (currently draft-ietf-entmib-v3-05.txt).  That document is a
normative reference because the PhysicalIndex and
PhysicalIndexOrZero TCs have been listed (at Juergen Schoenwaelder's
request) in Appendix B:  Commonly Used Textual Conventions.

   The following TCs are defined in ENTITY-MIB [RFC2737bis]:

   PhysicalIndex               Integer32 (1..2147483647)
   PhysicalIndexOrZero         Integer32 (0..2147483647)

I added these in the -03 guidelines draft because 2737bis had been
approved for publication, and I assumed that it would be done before
the MIB review guidelines.  I would like to leave them in, but I
don't want to have the guidelines document be help up on account of
delays in publishing 2737bis.

Can anybody offer an educated guess as to when 2737bis will be
finished?

Thanks,

Mike Heard


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


From entmib-bounces@ietf.org  Tue Jan  4 04:56:23 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA27972
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 04:56:23 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CllHh-0007gS-UV; Tue, 04 Jan 2005 04:47:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CllFg-00073U-16
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 04:45:22 -0500
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 EAA27219
	for <entmib@ietf.org>; Tue, 4 Jan 2005 04:45:18 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CllRy-0000xm-3a
	for entmib@ietf.org; Tue, 04 Jan 2005 04:58:05 -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 j049ihjw013337
	for <entmib@ietf.org>; Tue, 4 Jan 2005 03:44:44 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP4ND46>; Tue, 4 Jan 2005 10:44:42 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550604F431@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "C. M. Heard" <heard@pobox.com>
Subject: RE: [Entmib] Entity MIB Publication Schedule
Date: Tue, 4 Jan 2005 10:44:37 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: "Entmib-wg \(E-mail\)" <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

Inline

> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf
> Of C. M. Heard
> Sent: Tuesday, January 04, 2005 05:33
> To: entmib@ietf.org
> Subject: [Entmib] Entity MIB Publication Schedule
> 
> 
> All,
> 
> I intend to post an updated version of the MIB review guidelines
> shortly, and one of the normative references is the update to
> RFC2737 (currently draft-ietf-entmib-v3-05.txt).  That document is a
> normative reference because the PhysicalIndex and
> PhysicalIndexOrZero TCs have been listed (at Juergen Schoenwaelder's
> request) in Appendix B:  Commonly Used Textual Conventions.
> 
>    The following TCs are defined in ENTITY-MIB [RFC2737bis]:
> 
>    PhysicalIndex               Integer32 (1..2147483647)
>    PhysicalIndexOrZero         Integer32 (0..2147483647)
> 
> I added these in the -03 guidelines draft because 2737bis had been
> approved for publication, and I assumed that it would be done before

Not sure what you mean by "approved for publication".

During IETF Last Call a serious question (on deprecating certain objects)
came up and WG decided to take it back into the WG. So the doc has not
yet been on IESG agenda. I suspect that
- when WG agrees on new rev, I need to issue another IETF Last Call
  (so that is at least 2 weeks)
- then put it on IESG agenda (adds another 1-2 weeks), assuming no DISCUSSes
  from IESG.
- then it goes to RFC-Ed queue.

So if WG agrees REAL quick now, then they can have this potentially approved
in 4-6 weeks. The guidelines doc needs 4 week IETF Last Call, so I assume
that would also be at least 4-6 weeks before it gets approved by IESG,
so then they (theoretically) can go into RFC-Ed queue more or less at same
time.

Now... the revision 5 (current version) was posted in late october.
I think the main hold-up is the discussion on wether we should or should
not include (new) object(s) for CLEI (and similar) info or not.
And if the answer is yes... then I get the feeling (based on what I see
on the mailing list) we're still not done.

Hope this helps, Bert

> the MIB review guidelines.  I would like to leave them in, but I
> don't want to have the guidelines document be help up on account of
> delays in publishing 2737bis.
> 
> Can anybody offer an educated guess as to when 2737bis will be
> finished?
> 
> Thanks,
> 
> Mike Heard
> 
> 
> _______________________________________________
> 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-bounces@ietf.org  Tue Jan  4 08:42:14 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11152
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 08:42:14 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clono-0003H5-FE; Tue, 04 Jan 2005 08:32:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClofY-0008NR-VR
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 08:24:17 -0500
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 IAA10155
	for <entmib@ietf.org>; Tue, 4 Jan 2005 08:24:15 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Clorv-00057G-Ip
	for entmib@ietf.org; Tue, 04 Jan 2005 08:37:04 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 6263CBA83;
	Tue,  4 Jan 2005 14:23:43 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 10657-10; Tue,  4 Jan 2005 14:23:42 +0100 (CET)
Received: from james (Ia7eb.i.pppool.de [85.73.167.235])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 2649AD407;
	Tue,  4 Jan 2005 14:23:42 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1ClpvP-000214-M8; Tue, 04 Jan 2005 15:44:43 +0100
Date: Tue, 4 Jan 2005 15:44:43 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
Message-ID: <20050104144443.GA7667@james>
Mail-Followup-To: Andy Bierman <abierman@cisco.com>, entmib@ietf.org
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
Cc: entmib@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

On Mon, Jan 03, 2005 at 08:33:01PM -0800, C. M. Heard wrote:
 
> Can anybody offer an educated guess as to when 2737bis will be
> finished?

Andy, can you post an updated version? Or can you tell us what
the information still missing is that you need to get the next
ID posted?

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From entmib-bounces@ietf.org  Tue Jan  4 11:52:42 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA25748
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 11:52:42 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClrtP-0005hW-OY; Tue, 04 Jan 2005 11:50:47 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Clrqb-0004d1-KC
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 11:47:53 -0500
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 LAA25374
	for <entmib@ietf.org>; Tue, 4 Jan 2005 11:47:51 -0500 (EST)
Received: from sj-iport-2-in.cisco.com ([171.71.176.71]
	helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cls2z-0000qD-Gi
	for entmib@ietf.org; Tue, 04 Jan 2005 12:00:42 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-2.cisco.com with ESMTP; 04 Jan 2005 08:55:19 -0800
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com
	[171.71.163.17])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j04GlGl2023509;
	Tue, 4 Jan 2005 08:47:16 -0800 (PST)
Received: from abierman-xp.cisco.com (sjc-vpn1-559.cisco.com [10.21.98.47])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BCK10900;
	Tue, 4 Jan 2005 08:47:16 -0800 (PST)
Message-Id: <4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 04 Jan 2005 08:47:15 -0800
To: j.schoenwaelder@iu-bremen.de
From: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
In-Reply-To: <20050104144443.GA7667@james>
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
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

At 06:44 AM 1/4/2005, Juergen Schoenwaelder wrote:
>On Mon, Jan 03, 2005 at 08:33:01PM -0800, C. M. Heard wrote:
> 
>> Can anybody offer an educated guess as to when 2737bis will be
>> finished?
>
>Andy, can you post an updated version? Or can you tell us what
>the information still missing is that you need to get the next
>ID posted?

I'll post an update this week.
I think I understand the edits, but I'm not sure:

 - incorrect IPR text will be removed  

For entPhysicalUris object:
 - any leading and training whitespace is ignored
 - any number of whitespace characters can be present between URIs
 - whitespace can be space or horizontal tab (what else?)
 - The Generic URI citation will be removed, since it is in 
   the REFERENCE clause.
 - The CLEI references provided by Kaj will be added
 - The CLEI intro text provided by Kaj will be added
 - The object DESCRIPTION will indicate that URN namespaces
   such as the CLEI URN are registered with IANA, and that
   registry should be used for further interpretation of
   URI semantics
 - Examples provided by Kaj will be added/integrated 

Does 2737bis need a normative reference to the CLEI URN I-D?
I think so, if it's mentioned inside an OBJECT-TYPE macro.

>/js

Andy

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


From entmib-bounces@ietf.org  Tue Jan  4 12:57:59 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02383
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 12:57:59 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clsqy-0000k0-RR; Tue, 04 Jan 2005 12:52:20 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClsjX-0006Vq-8h
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 12:44:41 -0500
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 MAA01233
	for <entmib@ietf.org>; Tue, 4 Jan 2005 12:44:36 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Clsvt-0002OB-6k
	for entmib@ietf.org; Tue, 04 Jan 2005 12:57:28 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 00CB8D645;
	Tue,  4 Jan 2005 18:44:04 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 23232-06; Tue,  4 Jan 2005 18:44:03 +0100 (CET)
Received: from james (I951b.i.pppool.de [85.73.149.27])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 08A59D5F0;
	Tue,  4 Jan 2005 18:44:03 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1Clsiv-0000ju-3D; Tue, 04 Jan 2005 18:44:01 +0100
Date: Tue, 4 Jan 2005 18:44:01 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
Message-ID: <20050104174401.GA2834@james>
Mail-Followup-To: Andy Bierman <abierman@cisco.com>, entmib@ietf.org
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Cc: entmib@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

On Tue, Jan 04, 2005 at 08:47:15AM -0800, Andy Bierman wrote:
 
> Does 2737bis need a normative reference to the CLEI URN I-D?
> I think so, if it's mentioned inside an OBJECT-TYPE macro.

Probably depends on the details of the wording. If the CLEI URNs
are used as usage examples while the precise format is expressed 
in terms of general URI formats, one could argue that a suitable 
URI RFC would be normative while the specific CLEI URNs are 
informative examples. If we make the ENTITY-MIB depend on the
CLEI URN I-D, we open another can of worms and delays.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From entmib-bounces@ietf.org  Tue Jan  4 13:46:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06880
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 13:46:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Clteo-00067e-IB; Tue, 04 Jan 2005 13:43:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CltXk-0002LC-IJ
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 13:36:32 -0500
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 NAA05677
	for <entmib@ietf.org>; Tue, 4 Jan 2005 13:36:31 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cltk9-0003iD-CN
	for entmib@ietf.org; Tue, 04 Jan 2005 13:49:22 -0500
Received: from shannon.research.telcordia.com (shannon [128.96.81.11])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id
	j04IZj5u028337; Tue, 4 Jan 2005 13:35:49 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (pc22535.cc.telcordia.com
	[128.96.171.169])
	by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA06244; 
	Tue, 4 Jan 2005 13:35:42 -0500 (EST)
Message-Id: <6.1.2.0.2.20050104132350.01dc6ec0@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Tue, 04 Jan 2005 13:25:42 -0500
To: j.schoenwaelder@iu-bremen.de
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
In-Reply-To: <20050104174401.GA2834@james>
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com>
	<20050104174401.GA2834@james>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081
Cc: entmib@ietf.org, Andy Bierman <abierman@cisco.com>
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

At 12:44 PM 1/4/2005, Juergen Schoenwaelder wrote:
>On Tue, Jan 04, 2005 at 08:47:15AM -0800, Andy Bierman wrote:
>
> > Does 2737bis need a normative reference to the CLEI URN I-D?
> > I think so, if it's mentioned inside an OBJECT-TYPE macro.
>
>Probably depends on the details of the wording. If the CLEI URNs
>are used as usage examples while the precise format is expressed
>in terms of general URI formats, one could argue that a suitable
>URI RFC would be normative while the specific CLEI URNs are
>informative examples. If we make the ENTITY-MIB depend on the
>CLEI URN I-D, we open another can of worms and delays.


Since the CLEI is just an example of the use of that object
I'd suggest that the ENTITY-MIB can not depend on it,
and therefore it should not be normative, no?

kaj





>/js
>
>--
>Juergen Schoenwaelder               International University Bremen
><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany
>
>_______________________________________________
>Entmib mailing list
>Entmib@ietf.org
>https://www1.ietf.org/mailman/listinfo/entmib


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: kaj@research.telcordia.com
Tel: (732) 699-6068
Fax: (732) 336-2336

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


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


From entmib-bounces@ietf.org  Tue Jan  4 15:40:45 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16494
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 15:40:45 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClvL5-00054M-1q; Tue, 04 Jan 2005 15:31:35 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClvD9-0007jx-4E
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 15:23:23 -0500
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 PAA15264
	for <entmib@ietf.org>; Tue, 4 Jan 2005 15:23:21 -0500 (EST)
Received: from tm-gw.cictr.com ([207.31.248.245] helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ClvPW-0006F9-C8
	for entmib@ietf.org; Tue, 04 Jan 2005 15:36:14 -0500
Received: from [10.0.0.171] (account margaret HELO [10.0.0.171])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 255923; Tue, 04 Jan 2005 15:22:02 -0500
Mime-Version: 1.0
Message-Id: <p0620070abe00ab0401ba@[10.0.0.171]>
In-Reply-To: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
Date: Tue, 4 Jan 2005 15:22:21 -0500
To: "C. M. Heard" <heard@pobox.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2
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 Mike,

>Can anybody offer an educated guess as to when 2737bis will be
>finished?

Given Andy's commitment to circulate an updated version this week 
that will resolve the open issues, I am hopeful that this MIB will be 
submitted to the IESG within ~3-4 weeks.  Since it should only 
require a 2-week IETF LC, it could be approved by the IESG in ~6-8 
weeks.

Margaret


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


From entmib-bounces@ietf.org  Tue Jan  4 15:42:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16723
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 15:42:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClvMP-0005t1-OF; Tue, 04 Jan 2005 15:32:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1ClvGv-00024I-KA
	for entmib@megatron.ietf.org; Tue, 04 Jan 2005 15:27:17 -0500
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 PAA15566
	for <entmib@ietf.org>; Tue, 4 Jan 2005 15:27:15 -0500 (EST)
Received: from smtpout1.bayarea.net ([209.128.95.10])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1ClvTJ-0006K7-5j
	for entmib@ietf.org; Tue, 04 Jan 2005 15:40:08 -0500
Received: from shell4.bayarea.net (shell4.bayarea.net [209.128.82.1])
	by smtpout1.bayarea.net (8.12.10/8.12.10) with ESMTP id j04KQYVA003053
	for <entmib@ietf.org>; Tue, 4 Jan 2005 12:26:34 -0800
Received: from shell4.bayarea.net (localhost [127.0.0.1])
	by shell4.bayarea.net (8.12.11/8.12.11) with ESMTP id j04KQYPd019120;
	Tue, 4 Jan 2005 12:26:34 -0800
Received: from localhost (heard@localhost)
	by shell4.bayarea.net (8.12.11/8.12.11/Submit) with ESMTP id
	j04KQYew019113; Tue, 4 Jan 2005 12:26:34 -0800
X-Authentication-Warning: shell4.bayarea.net: heard owned process doing -bs
Date: Tue, 4 Jan 2005 12:26:33 -0800 (PST)
From: "C. M. Heard" <heard@pobox.com>
X-Sender: heard@shell4.bayarea.net
To: entmib@ietf.org
Subject: Re: [Entmib] Entity MIB Publication Schedule
In-Reply-To: <p0620070abe00ab0401ba@[10.0.0.171]>
Message-ID: <Pine.LNX.4.10.10501041225090.16966-100000@shell4.bayarea.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c
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

On Tue, 4 Jan 2005, Margaret Wasserman wrote:
> >Can anybody offer an educated guess as to when 2737bis will be
> >finished?
> 
> Given Andy's commitment to circulate an updated version this week 
> that will resolve the open issues, I am hopeful that this MIB will be 
> submitted to the IESG within ~3-4 weeks.  Since it should only 
> require a 2-week IETF LC, it could be approved by the IESG in ~6-8 
> weeks.


Thanks.  I will keep an eye out for the updated draft.

Mike


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


From entmib-bounces@ietf.org  Tue Jan  4 15:52:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17328
	for <entmib-archive@lists.ietf.org>; Tue, 4 Jan 2005 15:52:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClvTU-0002al-1l; Tue, 04 Jan 2005 15:40:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1ClvKd-0004g2-An; Tue, 04 Jan 2005 15:31:07 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA15747;
	Tue, 4 Jan 2005 15:31:05 -0500 (EST)
Message-Id: <200501042031.PAA15747@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 04 Jan 2005 15:31:05 -0500
Cc: entmib@ietf.org
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-06.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Entity MIB Working Group of the IETF.

	Title		: Entity State MIB
	Author(s)	: S. Chisholm, D. Perkins
	Filename	: draft-ietf-entmib-state-06.txt
	Pages		: 19
	Date		: 2005-1-4
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-entmib-state-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-state-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-1-4153106.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-entmib-state-06.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-entmib-state-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-1-4153106.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From entmib-bounces@ietf.org  Wed Jan  5 14:00:21 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA00932
	for <entmib-archive@lists.ietf.org>; Wed, 5 Jan 2005 14:00:21 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CmGLw-0004xc-Ia; Wed, 05 Jan 2005 13:57:52 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CmGJZ-0004YM-HM
	for entmib@megatron.ietf.org; Wed, 05 Jan 2005 13:55:25 -0500
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 NAA00637
	for <entmib@ietf.org>; Wed, 5 Jan 2005 13:55:23 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CmGW3-0002TC-9v
	for entmib@ietf.org; Wed, 05 Jan 2005 14:08:28 -0500
Received: from shannon.research.telcordia.com
	(shannon-83.research.telcordia.com [128.96.83.11])
	by thumper.research.telcordia.com (8.12.9/8.12.9) with ESMTP id
	j05IsQ5u025679; Wed, 5 Jan 2005 13:54:26 -0500 (EST)
Received: from KAJ-2.research.telcordia.com (KAJ-2.cc.telcordia.com
	[128.96.208.56])
	by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id NAA13720; 
	Wed, 5 Jan 2005 13:54:25 -0500 (EST)
Message-Id: <6.1.2.0.2.20050105133434.041c3388@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 05 Jan 2005 13:54:50 -0500
To: Andy Bierman <abierman@cisco.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: Re: [Entmib] Entity MIB Publication Schedule
In-Reply-To: <6.1.2.0.2.20050104132350.01dc6ec0@128.96.81.11>
References: <Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<Pine.LNX.4.10.10501032016490.24636-100000@shell4.bayarea.net>
	<4.3.2.7.2.20050104083339.028aa0a0@fedex.cisco.com>
	<20050104174401.GA2834@james>
	<6.1.2.0.2.20050104132350.01dc6ec0@128.96.81.11>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b
Cc: entmib@ietf.org, j.schoenwaelder@iu-bremen.de
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

Andy,

As per below, a way to resolve this could be:

* refer to the Official IANA Registry of URI Schemes
    http://www.iana.org/assignments/uri-schemes
    and the Official IANA Registry of URN Namespaces
    http://www.iana.org/assignments/urn-namespaces
    for current URI/URN assignments

* include a formal URI/URN RFC as normative; a candidate
    could be:
    [RFC2396] Uniform Resource Identifiers (URI): Generic Syntax. T.
      Berners-Lee, R. Fielding, L. Masinter. August 1998. (Format:
      TXT=83639 bytes) (Updates RFC1808, RFC1738) (Updated by RFC2732)
      (Status: DRAFT STANDARD)

* include the CLEI URN as informative:
    [URNCLEI] A Uniform Resource Name (URN) Namespace for the CLEI Code,
     Kaj Tesink, Robert H. Fox, Work in progress, December 31, 2004

kaj


At 01:25 PM 1/4/2005, Kaj Tesink wrote:
>At 12:44 PM 1/4/2005, Juergen Schoenwaelder wrote:
>>On Tue, Jan 04, 2005 at 08:47:15AM -0800, Andy Bierman wrote:
>>
>> > Does 2737bis need a normative reference to the CLEI URN I-D?
>> > I think so, if it's mentioned inside an OBJECT-TYPE macro.
>>
>>Probably depends on the details of the wording. If the CLEI URNs
>>are used as usage examples while the precise format is expressed
>>in terms of general URI formats, one could argue that a suitable
>>URI RFC would be normative while the specific CLEI URNs are
>>informative examples. If we make the ENTITY-MIB depend on the
>>CLEI URN I-D, we open another can of worms and delays.
>
>
>Since the CLEI is just an example of the use of that object
>I'd suggest that the ENTITY-MIB can not depend on it,
>and therefore it should not be normative, no?
>
>kaj
>
>
>
>
>
>>/js
>>
>>--
>>Juergen Schoenwaelder               International University Bremen
>><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany
>>
>>_______________________________________________
>>Entmib mailing list
>>Entmib@ietf.org
>>https://www1.ietf.org/mailman/listinfo/entmib
>
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
>
>Kaj Tesink
>Telcordia Technologies. Inc.
>One Telcordia drive
>Piscataway, NJ 08854
>Email: kaj@research.telcordia.com
>Tel: (732) 699-6068
>Fax: (732) 336-2336
>
>_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

Kaj Tesink
Telcordia Technologies. Inc.
One Telcordia drive
Piscataway, NJ 08854
Email: kaj@research.telcordia.com
Tel: (732) 699-6068
Fax: (732) 336-2336

_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/


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


From entmib-bounces@ietf.org  Tue Jan 11 15:50:58 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26219
	for <entmib-archive@lists.ietf.org>; Tue, 11 Jan 2005 15:50:57 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoSje-0007Co-0m; Tue, 11 Jan 2005 15:35:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CoSiP-0006Op-AQ; Tue, 11 Jan 2005 15:34:09 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA24227;
	Tue, 11 Jan 2005 15:34:07 -0500 (EST)
Message-Id: <200501112034.PAA24227@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Tue, 11 Jan 2005 15:34:07 -0500
Cc: entmib@ietf.org
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-v3-06.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Entity MIB Working Group of the IETF.

	Title		: Entity MIB (Version 3)
	Author(s)	: K. McCloghrie, A. Bierman
	Filename	: draft-ietf-entmib-v3-06.txt
	Pages		: 68
	Date		: 2005-1-11
	
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 managed objects used for managing multiple
logical and physical entities managed by a single SNMP agent.  This
document specifies version 3 of the Entity MIB, which obsoletes version
2 (RFC 2737).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-06.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-entmib-v3-06.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-v3-06.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-1-11160511.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-entmib-v3-06.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-entmib-v3-06.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-1-11160511.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From entmib-bounces@ietf.org  Sun Jan 16 13:30:00 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06532
	for <entmib-archive@lists.ietf.org>; Sun, 16 Jan 2005 13:30:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqF7y-00058s-Vz; Sun, 16 Jan 2005 13:27:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqF3K-0004cV-If
	for entmib@megatron.ietf.org; Sun, 16 Jan 2005 13:23:06 -0500
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 NAA03783
	for <entmib@ietf.org>; Sun, 16 Jan 2005 13:23:03 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqFID-0007cu-4t
	for entmib@ietf.org; Sun, 16 Jan 2005 13:38:30 -0500
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 262286 for entmib@ietf.org;
	Sun, 16 Jan 2005 07:52:32 -0500
Mime-Version: 1.0
Message-Id: <p06200716be100dd6bf7e@[192.168.2.2]>
In-Reply-To: <200501112034.PAA24227@ietf.org>
References: <200501112034.PAA24227@ietf.org>
Date: Sun, 16 Jan 2005 07:50:17 -0500
To: entmib@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
Subject: [Entmib] Mini WG LAST CALL: draft-ietf-entmib-v3-06.txt
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 All,

I believe that this new version of the Entity MIB 
(draft-ietf-entmib-v3-06.txt) addresses all of the outstanding 
comments.

This document was previously sent to the IESG for publication at DS 
and was pulled back to reverse the deprecation of certain objects. 
Since the document would then need to be re-cycled at PS, we decided 
to add objects to indicate the manufacturing date of a physical 
entity and to allow the inclusion of URIs to further specify the 
physical entity.  Most of the objects in this MIB have been 
implemented in multiple, interoperable implementations and are in 
common use.

Since this document has already been through WG Last Call several 
times, I just like to do a quick check that no new problems have been 
introduced as a result of the latest edits, then I will send this 
document on to the IESG for publication.

So, if you have any objection to this document being submitted to the 
IESG in its current form for publication as a Proposed Standard RFC, 
please send them to the entmib@ietf.org mailing list by Wednesday, 
January 19th.

Thanks,
Margaret

At 3:34 PM -0500 1/11/05, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Entity MIB Working Group of the IETF.
>
>	Title		: Entity MIB (Version 3)
>	Author(s)	: K. McCloghrie, A. Bierman
>	Filename	: draft-ietf-entmib-v3-06.txt
>	Pages		: 68
>	Date		: 2005-1-11
>
>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 managed objects used for managing 
>multiple
>logical and physical entities managed by a single SNMP agent.  This
>document specifies version 3 of the Entity MIB, which obsoletes version
>2 (RFC 2737).
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-06.txt
>

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


From entmib-bounces@ietf.org  Sun Jan 16 13:31:19 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA06754
	for <entmib-archive@lists.ietf.org>; Sun, 16 Jan 2005 13:31:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqF7z-00058x-4k; Sun, 16 Jan 2005 13:27:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqF3K-0004cX-Ov
	for entmib@megatron.ietf.org; Sun, 16 Jan 2005 13:23:06 -0500
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 NAA03786
	for <entmib@ietf.org>; Sun, 16 Jan 2005 13:23:03 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqFIE-0007cu-I1
	for entmib@ietf.org; Sun, 16 Jan 2005 13:38:30 -0500
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 262288 for entmib@ietf.org;
	Sun, 16 Jan 2005 07:59:30 -0500
Mime-Version: 1.0
Message-Id: <p06200717be1013d727c6@[192.168.2.2]>
In-Reply-To: <200501042031.PAA15747@ietf.org>
References: <200501042031.PAA15747@ietf.org>
Date: Sun, 16 Jan 2005 08:00:01 -0500
To: entmib@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Subject: [Entmib] Mini WG LAST CALL:draft-ietf-entmib-state-06.txt
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


The Entity State MIB has also been updated to address the issues 
raised in WG Last Call (see below).  I've reviewed this document, and 
it seems to contain the changes that were agreed on the list.

This document has also been through several WG Last Calls and should 
be ready for submission to the IESG for Proposed Standard.

So, if you have any objections to submitting this document to the 
IESG for publication as a Proposed Standard RFC, please send them to 
the entmib@ietf.org mailing list by Wednesday, January 19th.

Thanks,
Margaret


At 3:31 PM -0500 1/4/05, Internet-Drafts@ietf.org wrote:
>A New Internet-Draft is available from the on-line Internet-Drafts 
>directories.
>This draft is a work item of the Entity MIB Working Group of the IETF.
>
>	Title		: Entity State MIB
>	Author(s)	: S. Chisholm, D. Perkins
>	Filename	: draft-ietf-entmib-state-06.txt
>	Pages		: 19
>	Date		: 2005-1-4
>
>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.
>
>A URL for this Internet-Draft is:
>http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-06.txt
>

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


From entmib-bounces@ietf.org  Mon Jan 17 15:43:28 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12992
	for <entmib-archive@lists.ietf.org>; Mon, 17 Jan 2005 15:43:28 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqdbP-0004Kc-GI; Mon, 17 Jan 2005 15:35:55 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqdZO-0003D5-Qv
	for entmib@megatron.ietf.org; Mon, 17 Jan 2005 15:33:50 -0500
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 PAA12169
	for <entmib@ietf.org>; Mon, 17 Jan 2005 15:33:48 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqdoU-0006KX-Vd
	for entmib@ietf.org; Mon, 17 Jan 2005 15:49:28 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 44523D8CA;
	Mon, 17 Jan 2005 21:33:12 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 14019-02; Mon, 17 Jan 2005 21:33:11 +0100 (CET)
Received: from james (I9141.i.pppool.de [85.73.145.65])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 64A0BDDD7;
	Mon, 17 Jan 2005 21:33:11 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1Cqoj6-0000vR-F8; Tue, 18 Jan 2005 09:28:36 +0100
Date: Tue, 18 Jan 2005 09:28:36 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] Mini WG LAST CALL: draft-ietf-entmib-v3-06.txt
Message-ID: <20050118082836.GA2593@james>
Mail-Followup-To: Margaret Wasserman <margaret@thingmagic.com>, entmib@ietf.org
References: <200501112034.PAA24227@ietf.org>
	<p06200716be100dd6bf7e@[192.168.2.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06200716be100dd6bf7e@[192.168.2.2]>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 1.9 (+)
X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955
Cc: entmib@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

On Sun, Jan 16, 2005 at 07:50:17AM -0500, Margaret Wasserman wrote:
 
> Since this document has already been through WG Last Call several 
> times, I just like to do a quick check that no new problems have been 
> introduced as a result of the latest edits, then I will send this 
> document on to the IESG for publication.
> 
> So, if you have any objection to this document being submitted to the 
> IESG in its current form for publication as a Proposed Standard RFC, 
> please send them to the entmib@ietf.org mailing list by Wednesday, 
> January 19th.

I support this document being submitted to the IESG. However, I found
a few nits that probably should be addressed (personally I do not care
when in the process):

a) The description of entPhysicalMfgDate says '0000000000000000'H is
   returned if the date is unknown. The text in section 2.12.1 says
   that the object is not instantiated if the date is unknown. 
   
   It appears to me that entPhysicalFirmwareRev, entPhysicalSoftwareRev,
   entPhysicalSerialNum, entPhysicalMfgName, and entPhysicalModelName
   all return a zero-length string if the value is unknown so I think
   the description is actually consistent with them.
   
   Hence I propose the following change to section 2.12.1:

   OLD

     This object contains the date of manufacturing of the managed
     entity.  If the manufacturing date is unknown or not supported
     the object is not instantiated.

   NEW

     This object contains the date of manufacturing of the managed
     entity. If the manufacturing date is unknown or not supported
     the object is not instantiated. The special value 
     '0000000000000000'H may also be returned in this case.

b) My smilint says the following:

   ./ENTITY-MIB:90: warning: type `PhysicalIndex' has no format
                             specification
   ./ENTITY-MIB:104: warning: type `PhysicalIndexOrZero' has no format
			      specification

   I suggest to add DISPLAY-HINT "d" clauses to the TC definitions.

c) If I understand the MIB review guidelines correctly, then we should
   put the following into the IANA Considerations section:

      The MIB module in this document uses the following IANA-assigned
      OBJECT IDENTIFIER values recorded in the SMI Numbers registry:

      Descriptor        OBJECT IDENTIFIER value
      ----------        -----------------------
      entityMIB         { mib-2 47 }

      Editor's Note (to be removed prior to publication):  this draft
      makes no additional requests of the IANA.

   (I know that one can debate the utility of this but I do not want
   to do this here.)

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From entmib-bounces@ietf.org  Tue Jan 18 12:46:09 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14990
	for <entmib-archive@lists.ietf.org>; Tue, 18 Jan 2005 12:46:07 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqxP0-00033u-I7; Tue, 18 Jan 2005 12:44:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CqxHV-0001nW-Dz
	for entmib@megatron.ietf.org; Tue, 18 Jan 2005 12:36:41 -0500
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 MAA14209
	for <entmib@ietf.org>; Tue, 18 Jan 2005 12:36:38 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqxWm-0006Un-Bj
	for entmib@ietf.org; Tue, 18 Jan 2005 12:52:30 -0500
Received: from [10.0.0.171] (account margaret HELO [192.168.2.2])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 263329; Tue, 18 Jan 2005 12:35:10 -0500
Mime-Version: 1.0
Message-Id: <p0620073ebe12f9519217@[192.168.2.2]>
Date: Tue, 18 Jan 2005 12:35:52 -0500
To: j.schoenwaelder@iu-bremen.de
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] Mini WG LAST CALL: draft-ietf-entmib-v3-06.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 31247fb3be228bb596db9127becad0bc
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


[Failed to cc: entmib on this response the first time...]

Hi Juergen,

These changes all seem quite concrete and manageable.  Perhaps Andy
could make these changes in parallel with sending this MIB to the IESG
later this week.  Andy?

Margaret

>On Sun, Jan 16, 2005 at 07:50:17AM -0500, Margaret Wasserman wrote:
>
>>  Since this document has already been through WG Last Call several
>>  times, I just like to do a quick check that no new problems have been
>>  introduced as a result of the latest edits, then I will send this
>>  document on to the IESG for publication.
>>
>>  So, if you have any objection to this document being submitted to the
>>  IESG in its current form for publication as a Proposed Standard RFC,
>>  please send them to the entmib@ietf.org mailing list by Wednesday,
>>  January 19th.
>
>I support this document being submitted to the IESG. However, I found
>a few nits that probably should be addressed (personally I do not care
>when in the process):
>
>a) The description of entPhysicalMfgDate says '0000000000000000'H is
>    returned if the date is unknown. The text in section 2.12.1 says
>    that the object is not instantiated if the date is unknown.
>
>    It appears to me that entPhysicalFirmwareRev, entPhysicalSoftwareRev,
>    entPhysicalSerialNum, entPhysicalMfgName, and entPhysicalModelName
>    all return a zero-length string if the value is unknown so I think
>    the description is actually consistent with them.
>
>    Hence I propose the following change to section 2.12.1:
>
>    OLD
>
>      This object contains the date of manufacturing of the managed
>      entity.  If the manufacturing date is unknown or not supported
>      the object is not instantiated.
>
>    NEW
>
>      This object contains the date of manufacturing of the managed
>      entity. If the manufacturing date is unknown or not supported
>      the object is not instantiated. The special value
>      '0000000000000000'H may also be returned in this case.
>
>b) My smilint says the following:
>
>    ./ENTITY-MIB:90: warning: type `PhysicalIndex' has no format
>                              specification
>    ./ENTITY-MIB:104: warning: type `PhysicalIndexOrZero' has no format
>			      specification
>
>    I suggest to add DISPLAY-HINT "d" clauses to the TC definitions.
>
>c) If I understand the MIB review guidelines correctly, then we should
>    put the following into the IANA Considerations section:
>
>       The MIB module in this document uses the following IANA-assigned
>       OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
>
>       Descriptor        OBJECT IDENTIFIER value
>       ----------        -----------------------
>       entityMIB         { mib-2 47 }
>
>       Editor's Note (to be removed prior to publication):  this draft
>       makes no additional requests of the IANA.
>
>    (I know that one can debate the utility of this but I do not want
>    to do this here.)
>
>/js
>
>--
>Juergen Schoenwaelder		    International University Bremen
><http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 
>Bremen, Germany


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


From entmib-bounces@ietf.org  Tue Jan 18 13:16:29 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA17231
	for <entmib-archive@lists.ietf.org>; Tue, 18 Jan 2005 13:16:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CqxdK-0005KA-Sr; Tue, 18 Jan 2005 12:59:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cqxbs-0004iw-VH
	for entmib@megatron.ietf.org; Tue, 18 Jan 2005 12:57:45 -0500
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 MAA15943
	for <entmib@ietf.org>; Tue, 18 Jan 2005 12:57:41 -0500 (EST)
Received: from sj-iport-4.cisco.com ([171.68.10.86])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CqxrC-0006ya-0r
	for entmib@ietf.org; Tue, 18 Jan 2005 13:13:34 -0500
Received: from sj-core-2.cisco.com (171.71.177.254)
	by sj-iport-4.cisco.com with ESMTP; 18 Jan 2005 09:58:15 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com
	[171.71.163.17])
	by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j0IHvAl2010192;
	Tue, 18 Jan 2005 09:57:11 -0800 (PST)
Received: from abierman-xp.cisco.com (sjc-vpn1-481.cisco.com [10.21.97.225])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BCV52489;
	Tue, 18 Jan 2005 09:57:10 -0800 (PST)
Message-Id: <4.3.2.7.2.20050118095436.031c5e48@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Tue, 18 Jan 2005 09:57:10 -0800
To: Margaret Wasserman <margaret@thingmagic.com>
From: Andy Bierman <abierman@cisco.com>
Subject: Re: [Entmib] Mini WG LAST CALL: draft-ietf-entmib-v3-06.txt
In-Reply-To: <p0620073ebe12f9519217@[192.168.2.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db
Cc: entmib@ietf.org, j.schoenwaelder@iu-bremen.de
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

At 09:35 AM 1/18/2005, Margaret Wasserman wrote:

>[Failed to cc: entmib on this response the first time...]
>
>Hi Juergen,
>
>These changes all seem quite concrete and manageable.  Perhaps Andy
>could make these changes in parallel with sending this MIB to the IESG
>later this week.  Andy?

I'll get -07 done this week.
I need to figure out how to make nroff stop ending 
lines with a split hyphenated word (only ID-nit reported).


>Margaret

Andy



>>On Sun, Jan 16, 2005 at 07:50:17AM -0500, Margaret Wasserman wrote:
>>
>>> Since this document has already been through WG Last Call several
>>> times, I just like to do a quick check that no new problems have been
>>> introduced as a result of the latest edits, then I will send this
>>> document on to the IESG for publication.
>>>
>>> So, if you have any objection to this document being submitted to the
>>> IESG in its current form for publication as a Proposed Standard RFC,
>>> please send them to the entmib@ietf.org mailing list by Wednesday,
>>> January 19th.
>>
>>I support this document being submitted to the IESG. However, I found
>>a few nits that probably should be addressed (personally I do not care
>>when in the process):
>>
>>a) The description of entPhysicalMfgDate says '0000000000000000'H is
>>   returned if the date is unknown. The text in section 2.12.1 says
>>   that the object is not instantiated if the date is unknown.
>>
>>   It appears to me that entPhysicalFirmwareRev, entPhysicalSoftwareRev,
>>   entPhysicalSerialNum, entPhysicalMfgName, and entPhysicalModelName
>>   all return a zero-length string if the value is unknown so I think
>>   the description is actually consistent with them.
>>
>>   Hence I propose the following change to section 2.12.1:
>>
>>   OLD
>>
>>     This object contains the date of manufacturing of the managed
>>     entity.  If the manufacturing date is unknown or not supported
>>     the object is not instantiated.
>>
>>   NEW
>>
>>     This object contains the date of manufacturing of the managed
>>     entity. If the manufacturing date is unknown or not supported
>>     the object is not instantiated. The special value
>>     '0000000000000000'H may also be returned in this case.
>>
>>b) My smilint says the following:
>>
>>   ./ENTITY-MIB:90: warning: type `PhysicalIndex' has no format
>>                             specification
>>   ./ENTITY-MIB:104: warning: type `PhysicalIndexOrZero' has no format
>>                              specification
>>
>>   I suggest to add DISPLAY-HINT "d" clauses to the TC definitions.
>>
>>c) If I understand the MIB review guidelines correctly, then we should
>>   put the following into the IANA Considerations section:
>>
>>      The MIB module in this document uses the following IANA-assigned
>>      OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
>>
>>      Descriptor        OBJECT IDENTIFIER value
>>      ----------        -----------------------
>>      entityMIB         { mib-2 47 }
>>
>>      Editor's Note (to be removed prior to publication):  this draft
>>      makes no additional requests of the IANA.
>>
>>   (I know that one can debate the utility of this but I do not want
>>   to do this here.)
>>
>>/js
>>
>>--
>>Juergen Schoenwaelder               International University Bremen
>><http://www.eecs.iu-bremen.de/>     P.O. Box 750 561, 28725 Bremen, Germany
>
>
>_______________________________________________
>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-bounces@ietf.org  Wed Jan 19 10:10:41 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19727
	for <entmib-archive@lists.ietf.org>; Wed, 19 Jan 2005 10:10:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrHSB-0006B6-4Q; Wed, 19 Jan 2005 10:09:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CrHRC-0005sF-7h
	for entmib@megatron.ietf.org; Wed, 19 Jan 2005 10:08:02 -0500
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 KAA19408
	for <entmib@ietf.org>; Wed, 19 Jan 2005 10:07:59 -0500 (EST)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrHgf-0004kS-Gs
	for entmib@ietf.org; Wed, 19 Jan 2005 10:24:02 -0500
Received: from localhost (demetrius.iu-bremen.de [212.201.44.32])
	by hermes.iu-bremen.de (Postfix) with ESMTP id 9EBCFE89F;
	Wed, 19 Jan 2005 16:07:28 +0100 (CET)
Received: from hermes.iu-bremen.de ([212.201.44.23])
	by localhost (demetrius [212.201.44.32]) (amavisd-new,
	port 10024) with ESMTP
	id 29143-10; Wed, 19 Jan 2005 16:07:27 +0100 (CET)
Received: from james (unknown [10.50.253.208])
	(using TLSv1 with cipher RC4-SHA (128/128 bits))
	(No client certificate requested)
	by hermes.iu-bremen.de (Postfix) with ESMTP id 87F32E88E;
	Wed, 19 Jan 2005 16:07:27 +0100 (CET)
Received: from schoenw by james with local (Exim 4.34)
	id 1CrHQd-0000k0-Bz; Wed, 19 Jan 2005 16:07:27 +0100
Date: Wed, 19 Jan 2005 16:07:27 +0100
From: Juergen Schoenwaelder <j.schoenwaelder@iu-bremen.de>
To: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] Mini WG LAST CALL:draft-ietf-entmib-state-06.txt
Message-ID: <20050119150727.GA2807@james>
Mail-Followup-To: Margaret Wasserman <margaret@thingmagic.com>, entmib@ietf.org
References: <200501042031.PAA15747@ietf.org>
	<p06200717be1013d727c6@[192.168.2.2]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <p06200717be1013d727c6@[192.168.2.2]>
User-Agent: Mutt/1.5.6+20040907i
X-Virus-Scanned: by amavisd-new 20030616p5 at demetrius.iu-bremen.de
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
Cc: entmib@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: j.schoenwaelder@iu-bremen.de
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

On Sun, Jan 16, 2005 at 08:00:01AM -0500, Margaret Wasserman wrote:

> The Entity State MIB has also been updated to address the issues 
> raised in WG Last Call (see below).  I've reviewed this document, and 
> it seems to contain the changes that were agreed on the list.
> 
> This document has also been through several WG Last Calls and should 
> be ready for submission to the IESG for Proposed Standard.
> 
> So, if you have any objections to submitting this document to the 
> IESG for publication as a Proposed Standard RFC, please send them to 
> the entmib@ietf.org mailing list by Wednesday, January 19th.

I have checked <draft-ietf-entmib-state-06.txt> and I support
the document being submitted to the IESG. I have some editorial
nits that probably should be addressed before submitting the
document to that the IESG to reduce confusion/trouble/delay
later on.

- IANA Considerations section is missing. See the MIB guidelines
  document about what to put there.

- Reference [RFC2737] should probably be referring to the updated
  ENTITY-MIB (or at least a comment to the RFC Ed. concerning this
  should be added).

- Citations such as [Alarm-MIB] should be replaced with [RFC3877].

- The following sentence in section 3.2. does not read well:

   [...] If there are active alarms, then
   the alarmActiveTable in the Alarm MIB [Alarm MIB] should be searched
   for alarmActiveResourceId that match this entPhysicalIndex.

  Here is a first proposal to improve the wording:

   [...] If there are active alarms, then
   the alarmActiveTable in the Alarm MIB [RFC3877] should be searched
   for rows whose alarmActiveResourceId matches this entPhysicalIndex.

  I think it is important to be clear that there can be multiple
  matching rows.

- The following sentence in section 3.2. is probably not quite right:

   Alternatively, if the alarmActiveTable is queried first and an
   active alarm with a value of alarmActiveResourceId that matches
   this entPhysicalIndex is found, then entStateAlarm can be used to
   quickly determine if there are additional active alarms against
   this physical entity.

  My understanding is that entStateAlarm allows me to detect what kind
  of alarms I have but not how many. So if there are multiple alarms
  of the same severity, then entStateAlarm will not really allow me to
  detect that "there are additional active alarms against this physical
  entity".

   Alternatively, if the alarmActiveTable is queried first and an
   active alarm with a value of alarmActiveResourceId that matches
   this entPhysicalIndex is found, then entStateAlarm can be used to
   quickly determine if there are additional active alarms with a
   different severity against this physical entity.

- Security considerations:

  I suggest to insert "(entStateAdmin)" into the first sentence
  directly after "management object" and remove the second paragraph.

  In addition, I suggest to move the last and next to last paragraph
  directly below the first paragraph in this section so that the MIB
  specific stuff stays together and is not mixed with the more general
  "why you should use SNMPv3" statement.

  Putting things together, I suggest the following text for the
  security considerations section:

   There is one management object (entStateAdmin) defined in this MIB
   that has a MAX-ACCESS clause of read-write. The object may be
   considered sensitive or vulnerable in some network environments.
   The support for SET operations in a non-secure environment without
   proper protection can have a negative effect on network operations.

   Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
   can cause disruption of services ranging from those running on a
   port to those on an entire device, depending on the type of entity.
   Access to this object should be properly protected.

   Access to the objects defined in this MIB allows one to figure out
   what the active and standby resources in a network are. This
   information can be used to optimize attacks on networks so even
   read-only access to this MIB should be properly protected.

   SNMP versions prior to SNMPv3 did not include adequate security.
   Even if the network itself is secure (for example by using IPSec),
   even then, there is no control as to who on the secure network is
   allowed to access and GET/SET (read/change/create/delete) the
   objects in this MIB module.

   It is RECOMMENDED that implementers consider the security features
   as provided by the SNMPv3 framework (see [RFC3410], section 8),
   including full support for the SNMPv3 cryptographic mechanisms (for
   authentication and privacy).

   Further, deployment of SNMP versions prior to SNMPv3 is NOT
   RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
   enable cryptographic security.  It is then a customer/operator
   responsibility to ensure that the SNMP entity giving access to an
   instance of this MIB module is properly configured to give access to
   the objects only to those principals (entities) that have legitimate
   rights to indeed GET or SET (change/create/delete) them.

/js

-- 
Juergen Schoenwaelder		    International University Bremen
<http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 Bremen, Germany

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


From entmib-bounces@ietf.org  Thu Jan 20 16:33:12 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA08865
	for <entmib-archive@lists.ietf.org>; Thu, 20 Jan 2005 16:33:12 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrjZ9-0004T9-AK; Thu, 20 Jan 2005 16:10:07 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrjIx-00055o-I6; Thu, 20 Jan 2005 15:53:23 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04835;
	Thu, 20 Jan 2005 15:53:21 -0500 (EST)
Message-Id: <200501202053.PAA04835@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Thu, 20 Jan 2005 15:53:21 -0500
Cc: entmib@ietf.org
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-v3-07.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Entity MIB Working Group of the IETF.

	Title		: Entity MIB (Version 3)
	Author(s)	: K. McCloghrie, A. Bierman
	Filename	: draft-ietf-entmib-v3-07.txt
	Pages		: 68
	Date		: 2005-1-20
	
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 managed objects used for
     managing multiple logical and physical entities managed by a single
     SNMP agent.  This document specifies version 3 of the Entity MIB,
     which obsoletes version 2 (RFC 2737).

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-entmib-v3-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-v3-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-1-20161735.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-entmib-v3-07.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-entmib-v3-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-1-20161735.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From entmib-bounces@ietf.org  Thu Jan 20 21:51:01 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA09126
	for <entmib-archive@lists.ietf.org>; Thu, 20 Jan 2005 21:51:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrojI-0002vS-1E; Thu, 20 Jan 2005 21:40:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Croe1-0002Ga-15; Thu, 20 Jan 2005 21:35:29 -0500
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 VAA08390;
	Thu, 20 Jan 2005 21:35:25 -0500 (EST)
Received: from sj-iport-3-in.cisco.com ([171.71.176.72]
	helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Crotm-0004C3-Qx; Thu, 20 Jan 2005 21:51:47 -0500
Received: from sj-core-1.cisco.com (171.71.177.237)
	by sj-iport-3.cisco.com with ESMTP; 20 Jan 2005 19:43:18 +0000
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
Received: from mira-sjc5-c.cisco.com (IDENT:mirapoint@mira-sjc5-c.cisco.com
	[171.71.163.17])
	by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j0L2ZKM8010677;
	Thu, 20 Jan 2005 18:35:21 -0800 (PST)
Received: from [192.168.1.2] (sjc-vpn4-374.cisco.com [10.21.81.118])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BCY37315;
	Thu, 20 Jan 2005 18:35:21 -0800 (PST)
Message-ID: <41F06A68.3070102@cisco.com>
Date: Fri, 21 Jan 2005 08:05:20 +0530
From: Subrahmanya Hegde <subrah@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
	rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Internet-Drafts@ietf.org
Subject: Re: [Entmib] I-D ACTION:draft-ietf-entmib-v3-07.txt
References: <200501202053.PAA04835@ietf.org>
In-Reply-To: <200501202053.PAA04835@ietf.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 87a3f533bb300b99e2a18357f3c1563d
Content-Transfer-Encoding: 7bit
Cc: entmib@ietf.org, i-d-announce@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: subrah@cisco.com
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
Content-Transfer-Encoding: 7bit

Hi
  Section 2.12.3 specifies
...
Note that this table is deprecated in
      version 3 of the Entity MIB.

this comment is related to entLPMappingTable .
But it appears entLPMappingTable is not deprecated..
I think the comment need to be removed

Subra



Internet-Drafts@ietf.org wrote:

> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Entity MIB Working Group of the IETF.
> 
> 	Title		: Entity MIB (Version 3)
> 	Author(s)	: K. McCloghrie, A. Bierman
> 	Filename	: draft-ietf-entmib-v3-07.txt
> 	Pages		: 68
> 	Date		: 2005-1-20
> 	
> 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 managed objects used for
>      managing multiple logical and physical entities managed by a single
>      SNMP agent.  This document specifies version 3 of the Entity MIB,
>      which obsoletes version 2 (RFC 2737).
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-07.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
> You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
> to change your subscription settings.
> 
> 
> Internet-Drafts are also available by anonymous FTP. Login with the username
> "anonymous" and a password of your e-mail address. After logging in,
> type "cd internet-drafts" and then
> 	"get draft-ietf-entmib-v3-07.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-entmib-v3-07.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> -------------------------------------------------------------------------
> CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
> -------------------------------------------------------------------------
> In order to maintain computing infrastructure integrity, Cisco Systems
> Enterprise Messaging Services and InfoSec teams have set a mail policy
> disallowing executable attachments in email.
> 
> This message contained an executable attachment type that is prohibited 
> by this policy. The attachment has been removed from this message and 
> copied to quarantine by our systems. It will be held in quarantine for
> seven days in the event that the content needs to be retrieved.
> 
> Please be aware many viruses attempt to look like legitimate email or 
> notifications from anti-virus systems. We will clearly mark a seperation
> between our notifications and the original email as follows:
> 
>   "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"
> 
> For further reference information about viruses and email antivirus 
> efforts within Cisco, please visit:
> 
> http://wwwin.cisco.com/it/ems/services/antiviral
> 
> If your concern isn't addressed by the information in this notification 
> or the above web page, you may open a support request:
> 
> http://wwwin.cisco.com/support/
> 
> Select "Messaging", "Email-Related", "Mail Routing"
> 
> Please include in the text of your case the following information:
> 
> * Full headers of the message. Documentation on displaying the full 
> headers is available at this URL:
> 
> http://wwwin.cisco.com/support/library/faqs/solution002471.html 
> 
> * This unique quarantine identifier: j0KLW3oj006720
> 
> If the matter is urgent, you may follow up by calling one of the below 
> referenced numbers. Please make every effort to provide the above 
> requested information via the support web tool prior to calling as it 
> will greatly aid the resolution of your issue.
> 
> Americas:
> 1 408 526 8888
> 
> Asiapac
> +61 2 8446 8888
> 
> EMEA
> +31 20 485 4888
> 
> Japan
> +81 3 5549 6888
> 
> US (Toll Free)
> 1| 800| 888| 8187| (ext.68888)
> 
> Thank you for your cooperation,
> 
> Enterprise Messaging Services
> Cisco Systems, Inc
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> 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-bounces@ietf.org  Fri Jan 21 08:52:32 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10883
	for <entmib-archive@lists.ietf.org>; Fri, 21 Jan 2005 08:52:32 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Crz9V-0006FU-Ea; Fri, 21 Jan 2005 08:48:41 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Crz35-00053t-2O; Fri, 21 Jan 2005 08:42:03 -0500
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 IAA09936;
	Fri, 21 Jan 2005 08:42:00 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CrzIw-0003OL-Kz; Fri, 21 Jan 2005 08:58:27 -0500
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 265430; Fri, 21 Jan 2005 08:40:29 -0500
Mime-Version: 1.0
Message-Id: <p06200705be16b6c6b68a@[192.168.2.2]>
In-Reply-To: <41F06A68.3070102@cisco.com>
References: <200501202053.PAA04835@ietf.org> <41F06A68.3070102@cisco.com>
Date: Fri, 21 Jan 2005 08:40:52 -0500
To: subrah@cisco.com, Internet-Drafts@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] I-D ACTION:draft-ietf-entmib-v3-07.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: b1c41982e167b872076d0018e4e1dc3c
Cc: entmib@ietf.org, i-d-announce@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


Thanks, Subra.  We'll make sure that this is taken care of in the 
next revision (or in an RFC editor note if not later revision is 
needed).

Margaret

At 8:05 AM +0530 1/21/05, Subrahmanya Hegde wrote:
>Hi
>  Section 2.12.3 specifies
>...
>Note that this table is deprecated in
>      version 3 of the Entity MIB.
>
>this comment is related to entLPMappingTable .
>But it appears entLPMappingTable is not deprecated..
>I think the comment need to be removed
>
>Subra
>
>
>
>Internet-Drafts@ietf.org wrote:
>
>>  A New Internet-Draft is available from the on-line Internet-Drafts 
>>directories.
>>  This draft is a work item of the Entity MIB Working Group of the IETF.
>>  	Title		: Entity MIB (Version 3)
>>  	Author(s)	: K. McCloghrie, A. Bierman
>>  	Filename	: draft-ietf-entmib-v3-07.txt
>>  	Pages		: 68
>>  	Date		: 2005-1-20
>>
>>  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 managed objects used for
>>       managing multiple logical and physical entities managed by a single
>>       SNMP agent.  This document specifies version 3 of the Entity MIB,
>>       which obsoletes version 2 (RFC 2737).
>>  A URL for this Internet-Draft is:
>>  http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-07.txt
>>  To remove yourself from the I-D Announcement list, send a message 
>>to i-d-announce-request@ietf.org with the word unsubscribe in the 
>>body of the message.  You can also visit 
>>https://www1.ietf.org/mailman/listinfo/I-D-announce to change your 
>>subscription settings.
>>
>>  Internet-Drafts are also available by anonymous FTP. Login with the username
>>  "anonymous" and a password of your e-mail address. After logging in,
>>  type "cd internet-drafts" and then
>>  	"get draft-ietf-entmib-v3-07.txt".
>>  A list of Internet-Drafts directories can be found in
>>  http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
>>
>>  Internet-Drafts can also be obtained by e-mail.
>>  Send a message to:
>>  	mailserv@ietf.org.
>>  In the body type:
>>  	"FILE /internet-drafts/draft-ietf-entmib-v3-07.txt".
>>
>>  NOTE:	The mail server at ietf.org can return the document in
>>  	MIME-encoded form by using the "mpack" utility.  To use this
>>  	feature, insert the command "ENCODING mime" before the "FILE"
>>  	command.  To decode the response(s), you will need "munpack" or
>>  	a MIME-compliant mail reader.  Different MIME-compliant mail readers
>>  	exhibit different behavior, especially when dealing with
>>  	"multipart" MIME messages (i.e. documents which have been split
>>  	up into multiple messages), so check your local documentation on
>>  	how to manipulate these messages.
>>
>>
>>  Below is the data which will enable a MIME compliant mail reader
>>  implementation to automatically retrieve the ASCII version of the
>>  Internet-Draft.
>>  -------------------------------------------------------------------------
>>  CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY
>>  -------------------------------------------------------------------------
>>  In order to maintain computing infrastructure integrity, Cisco Systems
>>  Enterprise Messaging Services and InfoSec teams have set a mail policy
>>  disallowing executable attachments in email.
>>  This message contained an executable attachment type that is 
>>prohibited by this policy. The attachment has been removed from 
>>this message and copied to quarantine by our systems. It will be 
>>held in quarantine for
>>  seven days in the event that the content needs to be retrieved.
>>  Please be aware many viruses attempt to look like legitimate email 
>>or notifications from anti-virus systems. We will clearly mark a 
>>seperation
>>  between our notifications and the original email as follows:
>>    "CONTENT ABOVE THIS LINE IS *NOT* FROM CISCO INFORMATION TECHNOLOGY"
>>  For further reference information about viruses and email 
>>antivirus efforts within Cisco, please visit:
>>  http://wwwin.cisco.com/it/ems/services/antiviral
>>  If your concern isn't addressed by the information in this 
>>notification or the above web page, you may open a support request:
>>  http://wwwin.cisco.com/support/
>>  Select "Messaging", "Email-Related", "Mail Routing"
>>  Please include in the text of your case the following information:
>>  * Full headers of the message. Documentation on displaying the 
>>full headers is available at this URL:
>>  http://wwwin.cisco.com/support/library/faqs/solution002471.html
>>  * This unique quarantine identifier: j0KLW3oj006720
>>  If the matter is urgent, you may follow up by calling one of the 
>>below referenced numbers. Please make every effort to provide the 
>>above requested information via the support web tool prior to 
>>calling as it will greatly aid the resolution of your issue.
>>  Americas:
>>  1 408 526 8888
>>  Asiapac
>>  +61 2 8446 8888
>>  EMEA
>>  +31 20 485 4888
>>  Japan
>>  +81 3 5549 6888
>>  US (Toll Free)
>>  1| 800| 888| 8187| (ext.68888)
>>  Thank you for your cooperation,
>>  Enterprise Messaging Services
>>  Cisco Systems, Inc
>>
>>  ------------------------------------------------------------------------
>>  _______________________________________________
>>  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


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


From entmib-bounces@ietf.org  Fri Jan 21 08:59:33 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11522
	for <entmib-archive@lists.ietf.org>; Fri, 21 Jan 2005 08:59:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CrzDr-0006vn-Mb; Fri, 21 Jan 2005 08:53:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Crz9h-0006GX-3c
	for entmib@megatron.ietf.org; Fri, 21 Jan 2005 08:48:55 -0500
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 IAA10282
	for <entmib@ietf.org>; Fri, 21 Jan 2005 08:48:51 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CrzPa-0003Z4-Bh
	for entmib@ietf.org; Fri, 21 Jan 2005 09:05:18 -0500
Received: from [24.61.30.237] (account margaret HELO [192.168.2.2])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 265436; Fri, 21 Jan 2005 08:47:30 -0500
Mime-Version: 1.0
Message-Id: <p06200708be16b84c11dc@[192.168.2.2]>
In-Reply-To: <20050119150727.GA2807@james>
References: <200501042031.PAA15747@ietf.org>
	<p06200717be1013d727c6@[192.168.2.2]> <20050119150727.GA2807@james>
Date: Fri, 21 Jan 2005 08:48:11 -0500
To: j.schoenwaelder@iu-bremen.de
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: Re: [Entmib] Mini WG LAST CALL:draft-ietf-entmib-state-06.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.1 (/)
X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c
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


Thanks, Juergen!  These comments are clear and actionable, and 
addressing them will certainly improve the quality of the document.

Sharon, can you do a quick spin to make these changes, and we will 
submit the resulting
document to the IESG?

Thanks,
Margaret


At 4:07 PM +0100 1/19/05, Juergen Schoenwaelder wrote:
>On Sun, Jan 16, 2005 at 08:00:01AM -0500, Margaret Wasserman wrote:
>
>>  The Entity State MIB has also been updated to address the issues
>>  raised in WG Last Call (see below).  I've reviewed this document, and
>>  it seems to contain the changes that were agreed on the list.
>>
>>  This document has also been through several WG Last Calls and should
>>  be ready for submission to the IESG for Proposed Standard.
>>
>>  So, if you have any objections to submitting this document to the
>>  IESG for publication as a Proposed Standard RFC, please send them to
>>  the entmib@ietf.org mailing list by Wednesday, January 19th.
>
>I have checked <draft-ietf-entmib-state-06.txt> and I support
>the document being submitted to the IESG. I have some editorial
>nits that probably should be addressed before submitting the
>document to that the IESG to reduce confusion/trouble/delay
>later on.
>
>- IANA Considerations section is missing. See the MIB guidelines
>   document about what to put there.
>
>- Reference [RFC2737] should probably be referring to the updated
>   ENTITY-MIB (or at least a comment to the RFC Ed. concerning this
>   should be added).
>
>- Citations such as [Alarm-MIB] should be replaced with [RFC3877].
>
>- The following sentence in section 3.2. does not read well:
>
>    [...] If there are active alarms, then
>    the alarmActiveTable in the Alarm MIB [Alarm MIB] should be searched
>    for alarmActiveResourceId that match this entPhysicalIndex.
>
>   Here is a first proposal to improve the wording:
>
>    [...] If there are active alarms, then
>    the alarmActiveTable in the Alarm MIB [RFC3877] should be searched
>    for rows whose alarmActiveResourceId matches this entPhysicalIndex.
>
>   I think it is important to be clear that there can be multiple
>   matching rows.
>
>- The following sentence in section 3.2. is probably not quite right:
>
>    Alternatively, if the alarmActiveTable is queried first and an
>    active alarm with a value of alarmActiveResourceId that matches
>    this entPhysicalIndex is found, then entStateAlarm can be used to
>    quickly determine if there are additional active alarms against
>    this physical entity.
>
>   My understanding is that entStateAlarm allows me to detect what kind
>   of alarms I have but not how many. So if there are multiple alarms
>   of the same severity, then entStateAlarm will not really allow me to
>   detect that "there are additional active alarms against this physical
>   entity".
>
>    Alternatively, if the alarmActiveTable is queried first and an
>    active alarm with a value of alarmActiveResourceId that matches
>    this entPhysicalIndex is found, then entStateAlarm can be used to
>    quickly determine if there are additional active alarms with a
>    different severity against this physical entity.
>
>- Security considerations:
>
>   I suggest to insert "(entStateAdmin)" into the first sentence
>   directly after "management object" and remove the second paragraph.
>
>   In addition, I suggest to move the last and next to last paragraph
>   directly below the first paragraph in this section so that the MIB
>   specific stuff stays together and is not mixed with the more general
>   "why you should use SNMPv3" statement.
>
>   Putting things together, I suggest the following text for the
>   security considerations section:
>
>    There is one management object (entStateAdmin) defined in this MIB
>    that has a MAX-ACCESS clause of read-write. The object may be
>    considered sensitive or vulnerable in some network environments.
>    The support for SET operations in a non-secure environment without
>    proper protection can have a negative effect on network operations.
>
>    Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
>    can cause disruption of services ranging from those running on a
>    port to those on an entire device, depending on the type of entity.
>    Access to this object should be properly protected.
>
>    Access to the objects defined in this MIB allows one to figure out
>    what the active and standby resources in a network are. This
>    information can be used to optimize attacks on networks so even
>    read-only access to this MIB should be properly protected.
>
>    SNMP versions prior to SNMPv3 did not include adequate security.
>    Even if the network itself is secure (for example by using IPSec),
>    even then, there is no control as to who on the secure network is
>    allowed to access and GET/SET (read/change/create/delete) the
>    objects in this MIB module.
>
>    It is RECOMMENDED that implementers consider the security features
>    as provided by the SNMPv3 framework (see [RFC3410], section 8),
>    including full support for the SNMPv3 cryptographic mechanisms (for
>    authentication and privacy).
>
>    Further, deployment of SNMP versions prior to SNMPv3 is NOT
>    RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
>    enable cryptographic security.  It is then a customer/operator
>    responsibility to ensure that the SNMP entity giving access to an
>    instance of this MIB module is properly configured to give access to
>    the objects only to those principals (entities) that have legitimate
>    rights to indeed GET or SET (change/create/delete) them.
>
>/js
>
>--
>Juergen Schoenwaelder		    International University Bremen
><http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 
>Bremen, Germany
>
>_______________________________________________
>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-bounces@ietf.org  Sun Jan 23 14:31:33 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA02948
	for <entmib-archive@lists.ietf.org>; Sun, 23 Jan 2005 14:31:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CsnQJ-0007QU-BZ; Sun, 23 Jan 2005 14:29:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CsnOy-0007Cs-NR
	for entmib@megatron.ietf.org; Sun, 23 Jan 2005 14:28:00 -0500
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 OAA02739
	for <entmib@ietf.org>; Sun, 23 Jan 2005 14:27:59 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CsnfK-0000Wo-NB
	for entmib@ietf.org; Sun, 23 Jan 2005 14:44:55 -0500
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0NJRSU04841
	for <entmib@ietf.org>; Sun, 23 Jan 2005 14:27:28 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YZADJ9KV>; Sun, 23 Jan 2005 14:27:29 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4025A1C0E@zcarhxm2.corp.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: entmib@ietf.org
Subject: RE: [Entmib] Mini WG LAST CALL:draft-ietf-entmib-state-06.txt
Date: Sun, 23 Jan 2005 14:27:22 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 21bf7a2f1643ae0bf20c1e010766eb78
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

Done.

-----Original Message-----
From: entmib-bounces@ietf.org [mailto:entmib-bounces@ietf.org] On Behalf Of
Margaret Wasserman
Sent: Friday, January 21, 2005 8:48 AM
To: j.schoenwaelder@iu-bremen.de
Cc: entmib@ietf.org
Subject: Re: [Entmib] Mini WG LAST CALL:draft-ietf-entmib-state-06.txt



Thanks, Juergen!  These comments are clear and actionable, and 
addressing them will certainly improve the quality of the document.

Sharon, can you do a quick spin to make these changes, and we will 
submit the resulting
document to the IESG?

Thanks,
Margaret


At 4:07 PM +0100 1/19/05, Juergen Schoenwaelder wrote:
>On Sun, Jan 16, 2005 at 08:00:01AM -0500, Margaret Wasserman wrote:
>
>>  The Entity State MIB has also been updated to address the issues  
>> raised in WG Last Call (see below).  I've reviewed this document, and  
>> it seems to contain the changes that were agreed on the list.
>>
>>  This document has also been through several WG Last Calls and should  
>> be ready for submission to the IESG for Proposed Standard.
>>
>>  So, if you have any objections to submitting this document to the  
>> IESG for publication as a Proposed Standard RFC, please send them to  
>> the entmib@ietf.org mailing list by Wednesday, January 19th.
>
>I have checked <draft-ietf-entmib-state-06.txt> and I support the 
>document being submitted to the IESG. I have some editorial nits that 
>probably should be addressed before submitting the document to that the 
>IESG to reduce confusion/trouble/delay later on.
>
>- IANA Considerations section is missing. See the MIB guidelines
>   document about what to put there.
>
>- Reference [RFC2737] should probably be referring to the updated
>   ENTITY-MIB (or at least a comment to the RFC Ed. concerning this
>   should be added).
>
>- Citations such as [Alarm-MIB] should be replaced with [RFC3877].
>
>- The following sentence in section 3.2. does not read well:
>
>    [...] If there are active alarms, then
>    the alarmActiveTable in the Alarm MIB [Alarm MIB] should be searched
>    for alarmActiveResourceId that match this entPhysicalIndex.
>
>   Here is a first proposal to improve the wording:
>
>    [...] If there are active alarms, then
>    the alarmActiveTable in the Alarm MIB [RFC3877] should be searched
>    for rows whose alarmActiveResourceId matches this entPhysicalIndex.
>
>   I think it is important to be clear that there can be multiple
>   matching rows.
>
>- The following sentence in section 3.2. is probably not quite right:
>
>    Alternatively, if the alarmActiveTable is queried first and an
>    active alarm with a value of alarmActiveResourceId that matches
>    this entPhysicalIndex is found, then entStateAlarm can be used to
>    quickly determine if there are additional active alarms against
>    this physical entity.
>
>   My understanding is that entStateAlarm allows me to detect what kind
>   of alarms I have but not how many. So if there are multiple alarms
>   of the same severity, then entStateAlarm will not really allow me to
>   detect that "there are additional active alarms against this physical
>   entity".
>
>    Alternatively, if the alarmActiveTable is queried first and an
>    active alarm with a value of alarmActiveResourceId that matches
>    this entPhysicalIndex is found, then entStateAlarm can be used to
>    quickly determine if there are additional active alarms with a
>    different severity against this physical entity.
>
>- Security considerations:
>
>   I suggest to insert "(entStateAdmin)" into the first sentence
>   directly after "management object" and remove the second paragraph.
>
>   In addition, I suggest to move the last and next to last paragraph
>   directly below the first paragraph in this section so that the MIB
>   specific stuff stays together and is not mixed with the more general
>   "why you should use SNMPv3" statement.
>
>   Putting things together, I suggest the following text for the
>   security considerations section:
>
>    There is one management object (entStateAdmin) defined in this MIB
>    that has a MAX-ACCESS clause of read-write. The object may be
>    considered sensitive or vulnerable in some network environments.
>    The support for SET operations in a non-secure environment without
>    proper protection can have a negative effect on network operations.
>
>    Note that setting the entStateAdmin to 'locked' or 'shuttingDown'
>    can cause disruption of services ranging from those running on a
>    port to those on an entire device, depending on the type of entity.
>    Access to this object should be properly protected.
>
>    Access to the objects defined in this MIB allows one to figure out
>    what the active and standby resources in a network are. This
>    information can be used to optimize attacks on networks so even
>    read-only access to this MIB should be properly protected.
>
>    SNMP versions prior to SNMPv3 did not include adequate security.
>    Even if the network itself is secure (for example by using IPSec),
>    even then, there is no control as to who on the secure network is
>    allowed to access and GET/SET (read/change/create/delete) the
>    objects in this MIB module.
>
>    It is RECOMMENDED that implementers consider the security features
>    as provided by the SNMPv3 framework (see [RFC3410], section 8),
>    including full support for the SNMPv3 cryptographic mechanisms (for
>    authentication and privacy).
>
>    Further, deployment of SNMP versions prior to SNMPv3 is NOT
>    RECOMMENDED.  Instead, it is RECOMMENDED to deploy SNMPv3 and to
>    enable cryptographic security.  It is then a customer/operator
>    responsibility to ensure that the SNMP entity giving access to an
>    instance of this MIB module is properly configured to give access to
>    the objects only to those principals (entities) that have legitimate
>    rights to indeed GET or SET (change/create/delete) them.
>
>/js
>
>--
>Juergen Schoenwaelder		    International University Bremen
><http://www.eecs.iu-bremen.de/>	    P.O. Box 750 561, 28725 
>Bremen, Germany
>
>_______________________________________________
>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


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


From entmib-bounces@ietf.org  Mon Jan 24 15:49:27 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21940
	for <entmib-archive@lists.ietf.org>; Mon, 24 Jan 2005 15:49:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtB2X-0000CO-A3; Mon, 24 Jan 2005 15:42:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtAzO-0007Ka-TP; Mon, 24 Jan 2005 15:39:10 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA21299;
	Mon, 24 Jan 2005 15:39:08 -0500 (EST)
Message-Id: <200501242039.PAA21299@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: i-d-announce@ietf.org
From: Internet-Drafts@ietf.org
Date: Mon, 24 Jan 2005 15:39:08 -0500
Cc: entmib@ietf.org
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
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

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Entity MIB Working Group of the IETF.

	Title		: Entity State MIB
	Author(s)	: S. Chisholm, D. Perkins
	Filename	: draft-ietf-entmib-state-07.txt
	Pages		: 19
	Date		: 2005-1-24
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in,
type "cd internet-drafts" and then
	"get draft-ietf-entmib-state-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-state-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body; access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID: <2005-1-24154033.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-entmib-state-07.txt

--OtherAccess
Content-Type: Message/External-body; name="draft-ietf-entmib-state-07.txt";
	site="ftp.ietf.org"; access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID: <2005-1-24154033.I-D@ietf.org>


--OtherAccess--

--NextPart
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

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

--NextPart--





From entmib-bounces@ietf.org  Mon Jan 24 17:05:36 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA07745
	for <entmib-archive@lists.ietf.org>; Mon, 24 Jan 2005 17:05:36 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CtCF2-0008Dj-Ie; Mon, 24 Jan 2005 16:59:24 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CtC86-0003aE-3f
	for entmib@megatron.ietf.org; Mon, 24 Jan 2005 16:52:14 -0500
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 QAA05186
	for <entmib@ietf.org>; Mon, 24 Jan 2005 16:52:11 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CtCOe-0000Lk-D9
	for entmib@ietf.org; Mon, 24 Jan 2005 17:09:22 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j0OLq8vj024608
	for <entmib@ietf.org>; Mon, 24 Jan 2005 15:52:09 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP45XV4>; Mon, 24 Jan 2005 22:52:06 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550639CEBA@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: entmib@ietf.org
Date: Mon, 24 Jan 2005 22:52:06 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
Subject: [Entmib] AD Review: draft-ietf-entmib-v3-07.txt
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

Here are mY AD review comments:

1. SMICng says:

     C:\bwijnen\smicng\work>smicng entmibv3.inc
     W: f(entmibv3.mi2), (655,17) Item "entPhysicalUris" should
        have SIZE specified

     *** 0 errors and 1 warning in parsing

   It might be good to add a SIZE to that object.

2. I see on Page 63:
     It is recommended that the implementers consider the security
     features as provided by the SNMPv3 framework.  Specifically, the
     use of the User-based Security Model RFC 2574 [RFC2574] and the
     View-based Access Control Model RFC 2575 [RFC2575] is recommended.

   I thought I had commented before, that the citations to RFC2574/75
   probably should be changed into RFC3414/15 

3. W.r.t. references and citations I find:

    !! Missing citation for Normative reference:
    P063 L034: [RFC2026]

    !! Missing Reference for citation: [RFC2574]
    P062 L033:      use of the User-based Security Model RFC
      2574 [RFC2574] and the

    !! Missing Reference for citation: [RFC2575]
    P062 L034:      View-based Access Control Model RFC 2575
       [RFC2575] is recommended.


   The last 2 probably because you did update the references section
   but not the citation (as per point 2 above)

   I see: [RFC CLEIURN] on page 11 and [RFCCLEIURN] on page 12
   They probably should be the same as teh reference:
   [RFCCLEIURN]

You may consider this as IETF Last Call comments,
together with the comment from Subra from last week.

so pls do not issue a new rev yet.

Bert


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


From entmib-bounces@ietf.org  Mon Jan 31 10:20:26 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA11227
	for <entmib-archive@lists.ietf.org>; Mon, 31 Jan 2005 10:20:26 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvdHr-0003d3-1e; Mon, 31 Jan 2005 10:16:23 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvd6R-0000R7-M2
	for entmib@megatron.ietf.org; Mon, 31 Jan 2005 10:04:35 -0500
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 KAA09504
	for <entmib@ietf.org>; Mon, 31 Jan 2005 10:04:33 -0500 (EST)
Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvdOP-0005YN-4n
	for entmib@ietf.org; Mon, 31 Jan 2005 10:23:09 -0500
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0VF40D24856
	for <entmib@ietf.org>; Mon, 31 Jan 2005 10:04:00 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YZADNXNF>; Mon, 31 Jan 2005 10:04:00 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4026AF3AF@zcarhxm2.corp.nortel.com>
From: "Sharon Chisholm" <schishol@nortel.com>
To: entmib@ietf.org
Subject: FW: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
Date: Mon, 31 Jan 2005 10:03:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 25620135586de10c627e3628c432b04a
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

Resend: It seems my email address has changed to previous email bounced.

So, have we forwarded this to the IESG? I just did a quick look at the
agenda of this Friday's meeting, but didn't see it.

Sharon

-----Original Message-----
From: entmib-bounces@ietf.org [mailto:entmib-bounces@ietf.org] On Behalf Of
Internet-Drafts@ietf.org
Sent: Monday, January 24, 2005 3:39 PM
To: i-d-announce@ietf.org
Cc: entmib@ietf.org
Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt


A New Internet-Draft is available from the on-line Internet-Drafts
directories. This draft is a work item of the Entity MIB Working Group of
the IETF.

	Title		: Entity State MIB
	Author(s)	: S. Chisholm, D. Perkins
	Filename	: draft-ietf-entmib-state-07.txt
	Pages		: 19
	Date		: 2005-1-24
	
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.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-07.txt

To remove yourself from the I-D Announcement list, send a message to 
i-d-announce-request@ietf.org with the word unsubscribe in the body of the
message.  
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in, type
"cd internet-drafts" and then
	"get draft-ietf-entmib-state-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-state-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

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


From entmib-bounces@ietf.org  Mon Jan 31 12:20:39 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25795
	for <entmib-archive@lists.ietf.org>; Mon, 31 Jan 2005 12:20:39 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvfC3-00076f-5F; Mon, 31 Jan 2005 12:18:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cvez5-0002Io-7V
	for entmib@megatron.ietf.org; Mon, 31 Jan 2005 12:05:07 -0500
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 MAA23771
	for <entmib@ietf.org>; Mon, 31 Jan 2005 12:05:04 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvfH4-0000DF-GS
	for entmib@ietf.org; Mon, 31 Jan 2005 12:23:42 -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 j0VH4XdQ006961
	for <entmib@ietf.org>; Mon, 31 Jan 2005 11:04:34 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP40J41>; Mon, 31 Jan 2005 18:04:33 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550649834B@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Sharon Chisholm <schishol@nortel.com>, entmib@ietf.org
Subject: RE: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
Date: Mon, 31 Jan 2005 18:04:31 +0100
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a7d2e37451f7f22841e3b6f40c67db0f
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

Inline

> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf
> Of Sharon Chisholm
> Sent: Monday, January 31, 2005 16:04
> To: entmib@ietf.org
> Subject: FW: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
> 
> 
> hi
> 
> Resend: It seems my email address has changed to previous 
> email bounced.
> 
> So, have we forwarded this to the IESG? I just did a quick look at the
> agenda of this Friday's meeting, but didn't see it.
> 
Not sure what you mean with "this Friday's meeting".
Probably you mean the IESG telechat agenda for coming Thursday??

The doc needs AD review and then IETF Last Call and only after that
can it go to the IESG. You WG chair has (as far as I know) not
yet done a formal request for publication for this one.
WG chair may want to take some time to review and fill out
the evaluation input to AD as well.

Bert
> Sharon
> 
> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Monday, January 24, 2005 3:39 PM
> To: i-d-announce@ietf.org
> Cc: entmib@ietf.org
> Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories. This draft is a work item of the Entity MIB 
> Working Group of
> the IETF.
> 
> 	Title		: Entity State MIB
> 	Author(s)	: S. Chisholm, D. Perkins
> 	Filename	: draft-ietf-entmib-state-07.txt
> 	Pages		: 19
> 	Date		: 2005-1-24
> 	
> 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.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-07.txt
> 
> To remove yourself from the I-D Announcement list, send a message to 
> i-d-announce-request@ietf.org with the word unsubscribe in 
> the body of the
> message.  
> You can also visit 
https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in, type
"cd internet-drafts" and then
	"get draft-ietf-entmib-state-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-state-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
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-bounces@ietf.org  Mon Jan 31 13:30:20 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA03875
	for <entmib-archive@lists.ietf.org>; Mon, 31 Jan 2005 13:30:20 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CvgF1-0002bG-P1; Mon, 31 Jan 2005 13:25:39 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CvgA7-0001Ws-LO
	for entmib@megatron.ietf.org; Mon, 31 Jan 2005 13:20:35 -0500
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 NAA02735
	for <entmib@ietf.org>; Mon, 31 Jan 2005 13:20:32 -0500 (EST)
Received: from zcars04f.nortelnetworks.com ([47.129.242.57])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvgS6-0002VK-AK
	for entmib@ietf.org; Mon, 31 Jan 2005 13:39:11 -0500
Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35])
	by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with
	ESMTP id j0VIJxe23437
	for <entmib@ietf.org>; Mon, 31 Jan 2005 13:19:59 -0500 (EST)
Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19)
	id <YZADN9MJ>; Mon, 31 Jan 2005 13:20:00 -0500
Message-ID: <713043CE8B8E1348AF3C546DBE02C1B4026AF652@zcarhxm2.corp.nortel.com>
From: "Sharon Chisholm" <schishol@nortel.com>
To: entmib@ietf.org
Subject: RE: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
Date: Mon, 31 Jan 2005 13:19:48 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ff03b0075c3fc728d7d60a15b4ee1ad2
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

Ok. I guess I skipped about 10 steps ;-). I had thought the IESG took a peak
before issuing the IESG last call.

So, the correct question is then have we made a request to publish? 

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com] 
Sent: Monday, January 31, 2005 12:05 PM
To: Chisholm, Sharon [CAR:5K50:EXCH]; entmib@ietf.org
Subject: RE: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt


Inline

> -----Original Message-----
> From: entmib-bounces@ietf.org
> [mailto:entmib-bounces@ietf.org]On Behalf
> Of Sharon Chisholm
> Sent: Monday, January 31, 2005 16:04
> To: entmib@ietf.org
> Subject: FW: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
> 
> 
> hi
> 
> Resend: It seems my email address has changed to previous
> email bounced.
> 
> So, have we forwarded this to the IESG? I just did a quick look at the 
> agenda of this Friday's meeting, but didn't see it.
> 
Not sure what you mean with "this Friday's meeting".
Probably you mean the IESG telechat agenda for coming Thursday??

The doc needs AD review and then IETF Last Call and only after that can it
go to the IESG. You WG chair has (as far as I know) not yet done a formal
request for publication for this one. WG chair may want to take some time to
review and fill out the evaluation input to AD as well.

Bert
> Sharon
> 
> -----Original Message-----
> From: entmib-bounces@ietf.org
> [mailto:entmib-bounces@ietf.org] On Behalf Of
> Internet-Drafts@ietf.org
> Sent: Monday, January 24, 2005 3:39 PM
> To: i-d-announce@ietf.org
> Cc: entmib@ietf.org
> Subject: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts 
> directories. This draft is a work item of the Entity MIB Working Group 
> of the IETF.
> 
> 	Title		: Entity State MIB
> 	Author(s)	: S. Chisholm, D. Perkins
> 	Filename	: draft-ietf-entmib-state-07.txt
> 	Pages		: 19
> 	Date		: 2005-1-24
> 	
> 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.
> 
> A URL for this Internet-Draft is: 
> http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-07.txt
> 
> To remove yourself from the I-D Announcement list, send a message to
> i-d-announce-request@ietf.org with the word unsubscribe in 
> the body of the
> message.  
> You can also visit 
https://www1.ietf.org/mailman/listinfo/I-D-announce 
to change your subscription settings.


Internet-Drafts are also available by anonymous FTP. Login with the username
"anonymous" and a password of your e-mail address. After logging in, type
"cd internet-drafts" and then
	"get draft-ietf-entmib-state-07.txt".

A list of Internet-Drafts directories can be found in
http://www.ietf.org/shadow.html 
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be obtained by e-mail.

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-entmib-state-07.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

_______________________________________________
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-bounces@ietf.org  Mon Jan 31 19:32:29 2005
Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA28913
	for <entmib-archive@lists.ietf.org>; Mon, 31 Jan 2005 19:32:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvlgp-00062o-GI; Mon, 31 Jan 2005 19:14:43 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CvlXL-0004Bx-GN
	for entmib@megatron.ietf.org; Mon, 31 Jan 2005 19:04:55 -0500
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 TAA26097
	for <entmib@ietf.org>; Mon, 31 Jan 2005 19:04:52 -0500 (EST)
Received: from hoemail1.lucent.com ([192.11.226.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CvlpO-0007nt-EK
	for entmib@ietf.org; Mon, 31 Jan 2005 19:23:34 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by hoemail1.lucent.com (8.12.11/8.12.11) with ESMTP id j1104o32012372
	for <entmib@ietf.org>; Mon, 31 Jan 2005 18:04:53 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXP40PWX>; Tue, 1 Feb 2005 01:04:48 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155064983A5@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Entmib-wg (E-mail)" <entmib@ietf.org>
Date: Tue, 1 Feb 2005 01:04:38 +0100 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2657.72)
Content-Type: text/plain
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465
Subject: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
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

Feedback from IESG

-----Original Message-----
From: iesg-bounces@ietf.org [mailto:iesg-bounces@ietf.org]On Behalf Of
Ted Hardie
Sent: Monday, January 31, 2005 23:28
To: iesg@ietf.org
Subject: DISCUSS: draft-ietf-entmib-v3-07.txt


Minor, but should be fixed.  The document currently says:

entPhysicalUris OBJECT-TYPE
     SYNTAX      OCTET STRING
     MAX-ACCESS  read-write
     STATUS      current
     DESCRIPTION
             "This object contains additional identification information
             about the physical entity. The object contains URIs and
             therefore the syntax of this object must conform to RFC
             2396, section 2.

             Multiple URIs may be present and are separated by white
             space characters. Leading and trailing white space
             characters are ignored.

             If no additional identification information is known or
             supported about the physical entity the object is not
             instantiated.  A zero length octet string may also be
             returned in this case."
     REFERENCE
             "RFC 2396, Uniform Resource Identifiers (URI): Generic
             Syntax, section 2, August 1998."

This should be updated to the new URI RFC and a pointer to the
appropriate syntax restrictions.  This text also does not limit
the types of URIs which may be present.  If they are limited,
an enumerated list should be included.

The document also uses "CLEI URI" to refer to a URN in the CLEI
namespace.  That's technically correct, but it would be easier
to understand if CLEI URN was used.  Here's an example:

     The entPhysicalUris object may be used to encode for example a URI
     containing a Common Language Equipment Identifier (CLEI) URI for
     the managed physical entity. The URN name space for CLEIs is
     defined in [RFC CLEIURN], and the CLEI format is defined in
     [T1.213][T1.213a]. 

Simply swapping out (CLEI) URI for (CLEI) URN would be fine.

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


