From entmib-bounces@ietf.org  Tue Feb  1 01:59:52 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 BAA03641
	for <entmib-archive@lists.ietf.org>; Tue, 1 Feb 2005 01:59:51 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cvrvu-0004HF-TA; Tue, 01 Feb 2005 01:54:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CvrrN-0003P1-Ce
	for entmib@megatron.ietf.org; Tue, 01 Feb 2005 01:50:01 -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 BAA02760
	for <entmib@ietf.org>; Tue, 1 Feb 2005 01:50:00 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cvs9S-00087h-G1
	for entmib@ietf.org; Tue, 01 Feb 2005 02:08:43 -0500
Received: from [12.44.165.2] (account margaret HELO [172.20.100.138])
	by thingmagic.com (CommuniGate Pro SMTP 4.1.8)
	with ESMTP-TLS id 271727; Tue, 01 Feb 2005 01:48:17 -0500
Mime-Version: 1.0
Message-Id: <p06200723be24959fada4@[192.168.2.2]>
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B1550649834B@nl0006exch001u.nl.lucent.com>
References: <7D5D48D2CAA3D84C813F5B154F43B1550649834B@nl0006exch001u.nl.lucent.com>
Date: Mon, 31 Jan 2005 21:15:06 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        Sharon Chisholm <schishol@nortel.com>, entmib@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: RE: [Entmib] I-D ACTION:draft-ietf-entmib-state-07.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.7 (/)
X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906
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 Sharon,

At 6:04 PM +0100 1/31/05, Wijnen, Bert (Bert) wrote:
>WG chair may want to take some time to review and fill out
>the evaluation input to AD as well.

I believe that the WG is ready to send this document to the IESG, but 
as Bert mentioned, I need to fill out a submission form for both the 
Entity MIB and the Entity State MIB before they can advance.  The 
first question is something like "Has the WG chair personally 
reviewed these documents and determined that they pass all of the I-D 
Guidelines?", so I'm working through that process.  I haven't written 
many MIBs and I'm not a MIB doctor, so checking all of the nits is a 
bit of a timely process for me.

After I officially submit the documents and the questionnaires, the 
documents will get reviewed by Bert, followed by a two week IETF Last 
Call, followed by an IESG review.  It is typically for this process 
to take several weeks.

Margaret



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


From entmib-bounces@ietf.org  Wed Feb  2 10:22: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 KAA15602
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 10:22: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 1CwMHU-0006fk-ON; Wed, 02 Feb 2005 10:19:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwM4c-00008g-Ab
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 10:05:42 -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 KAA12528
	for <entmib@ietf.org>; Wed, 2 Feb 2005 10:05:37 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwMMy-0001bV-OG
	for entmib@ietf.org; Wed, 02 Feb 2005 10:24: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 j12F57NU003653
	for <entmib@ietf.org>; Wed, 2 Feb 2005 09:05:08 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXPVB1CJ>; Wed, 2 Feb 2005 16:05:06 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05A@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Andy Bierman (E-mail)" <abierman@cisco.com>,
        "Entmib-wg (E-mail)"
	<entmib@ietf.org>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
Date: Wed, 2 Feb 2005 16:05: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: 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

Can the author/editor and/or the WG react please.
I need (if possible) an answer by tomorrow (Thursday) 11am US
eastern at the latest (that is, if we want to try and get this 
approved this week).

Bert

> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf
> Of Wijnen, Bert (Bert)
> Sent: Tuesday, February 01, 2005 01:05
> To: Entmib-wg (E-mail)
> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
> 
> 
> 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
> 

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


From entmib-bounces@ietf.org  Wed Feb  2 10:50:54 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 KAA19792
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 10:50:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwMgo-0007wb-32; Wed, 02 Feb 2005 10:45:10 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwMbI-0006U3-Gv
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 10:39:28 -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 KAA18194
	for <entmib@ietf.org>; Wed, 2 Feb 2005 10:39:24 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwMtS-0002mJ-ER
	for entmib@ietf.org; Wed, 02 Feb 2005 10:58:16 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 02 Feb 2005 07:47:55 -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-5.cisco.com (8.12.10/8.12.6) with ESMTP id j12FceF1021553;
	Wed, 2 Feb 2005 07:38:41 -0800 (PST)
Received: from abierman-xp.cisco.com (sjc-vpn4-542.cisco.com [10.21.82.30])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BDI17116;
	Wed, 2 Feb 2005 07:38:40 -0800 (PST)
Message-Id: <4.3.2.7.2.20050202073232.025c9cd8@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 02 Feb 2005 07:38:39 -0800
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05A@nl0006exch001u.nl
	.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 73734d43604d52d23b3eba644a169745
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

At 07:05 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
>Can the author/editor and/or the WG react please.
>I need (if possible) an answer by tomorrow (Thursday) 11am US
>eastern at the latest (that is, if we want to try and get this 
>approved this week).

what are the edits? CLEI URI to CLEI URN. reference
RFC 2396 -> RFC 3986.  Any other nits?  Can't you just carry 
forward an edit list without an update?

It's not like these updates require anybody to comment.
Who's going to object to fixing a nit?


>Bert

Andy



>> -----Original Message-----
>> From: entmib-bounces@ietf.org 
>> [mailto:entmib-bounces@ietf.org]On Behalf
>> Of Wijnen, Bert (Bert)
>> Sent: Tuesday, February 01, 2005 01:05
>> To: Entmib-wg (E-mail)
>> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
>> 
>> 
>> 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
>> 

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


From entmib-bounces@ietf.org  Wed Feb  2 11:14:47 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 LAA22785
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 11:14:47 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwMsh-0003e0-13; Wed, 02 Feb 2005 10:57:27 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwMqD-0002G5-DW
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 10:54: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 KAA20214
	for <entmib@ietf.org>; Wed, 2 Feb 2005 10:54:48 -0500 (EST)
Received: from ihemail2.lucent.com ([192.11.222.163])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwN8b-0003K3-Ik
	for entmib@ietf.org; Wed, 02 Feb 2005 11:13:53 -0500
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com
	[135.85.76.62])
	by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j12FsKvj013795
	for <entmib@ietf.org>; Wed, 2 Feb 2005 09:54:20 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXPVBF9X>; Wed, 2 Feb 2005 16:54:18 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "'Andy Bierman'" <abierman@cisco.com>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
Date: Wed, 2 Feb 2005 16:54:19 +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: 057ebe9b96adec30a7efb2aeda4c26a4
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

Andy writes:
> 
> At 07:05 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
> >Can the author/editor and/or the WG react please.
> >I need (if possible) an answer by tomorrow (Thursday) 11am US
> >eastern at the latest (that is, if we want to try and get this 
> >approved this week).
> 
> what are the edits? CLEI URI to CLEI URN. reference
> RFC 2396 -> RFC 3986.  Any other nits?  Can't you just carry 
> forward an edit list without an update?
> 

I can do that if the WG agrees that that is indeed what we want to do.
I cannot just make such changes without checking back with at least
the authors/editors or the WG.

> It's not like these updates require anybody to comment.
> Who's going to object to fixing a nit?
> 
I can do those fixes with an RFC-Editor note if we agree that
is what we want to do.

Bert
> 
> >Bert
> 
> Andy
> 
> 
> 
> >> -----Original Message-----
> >> From: entmib-bounces@ietf.org 
> >> [mailto:entmib-bounces@ietf.org]On Behalf
> >> Of Wijnen, Bert (Bert)
> >> Sent: Tuesday, February 01, 2005 01:05
> >> To: Entmib-wg (E-mail)
> >> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
> >> 
> >> 
> >> 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
> >> 
> 

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


From entmib-bounces@ietf.org  Wed Feb  2 11:24: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 LAA23744
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 11:24: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 1CwN9J-0000GR-Km; Wed, 02 Feb 2005 11:14:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwN1Z-0005nt-1I
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 11:06:37 -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 LAA21472
	for <entmib@ietf.org>; Wed, 2 Feb 2005 11:06:32 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70]
	helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CwNJx-0003hj-8F
	for entmib@ietf.org; Wed, 02 Feb 2005 11:25:37 -0500
Received: from sj-core-5.cisco.com (171.71.177.238)
	by sj-iport-1.cisco.com with ESMTP; 02 Feb 2005 08:15:18 -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-5.cisco.com (8.12.10/8.12.6) with ESMTP id j12G63F1002617;
	Wed, 2 Feb 2005 08:06:03 -0800 (PST)
Received: from abierman-xp.cisco.com (sjc-vpn4-542.cisco.com [10.21.82.30])
	by mira-sjc5-c.cisco.com (MOS 3.4.5-GR) with ESMTP id BDI19677;
	Wed, 2 Feb 2005 08:06:02 -0800 (PST)
Message-Id: <4.3.2.7.2.20050202080331.020cce50@fedex.cisco.com>
X-Sender: abierman@fedex.cisco.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Wed, 02 Feb 2005 08:06:02 -0800
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Andy Bierman <abierman@cisco.com>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl
	.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 37af5f8fbf6f013c5b771388e24b09e7
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

At 07:54 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
>Andy writes:
>> 
>> At 07:05 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
>> >Can the author/editor and/or the WG react please.
>> >I need (if possible) an answer by tomorrow (Thursday) 11am US
>> >eastern at the latest (that is, if we want to try and get this 
>> >approved this week).
>> 
>> what are the edits? CLEI URI to CLEI URN. reference
>> RFC 2396 -> RFC 3986.  Any other nits?  Can't you just carry 
>> forward an edit list without an update?
>> 
>
>I can do that if the WG agrees that that is indeed what we want to do.
>I cannot just make such changes without checking back with at least
>the authors/editors or the WG.
>
>> It's not like these updates require anybody to comment.
>> Who's going to object to fixing a nit?
>> 
>I can do those fixes with an RFC-Editor note if we agree that
>is what we want to do.

I am 100% in favor of fixing typos and out-of-date references.
I don't think you need to wait for the WG to comment on 
non-controversial edits.  Any WG members out there in favor of 
keeping typos and out-of-date references, please speak up now!


>Bert
>> 
>> >Bert
>> 
>> Andy

Andy


>> 
>> 
>> 
>> >> -----Original Message-----
>> >> From: entmib-bounces@ietf.org 
>> >> [mailto:entmib-bounces@ietf.org]On Behalf
>> >> Of Wijnen, Bert (Bert)
>> >> Sent: Tuesday, February 01, 2005 01:05
>> >> To: Entmib-wg (E-mail)
>> >> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
>> >> 
>> >> 
>> >> 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
>> >> 
>> 

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


From entmib-bounces@ietf.org  Wed Feb  2 11:25:54 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 LAA23878
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 11:25:54 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CwN9U-0000OI-JG; Wed, 02 Feb 2005 11:14:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwN5Z-00071p-Ax
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 11:10: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 LAA22174
	for <entmib@ietf.org>; Wed, 2 Feb 2005 11:10:40 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNNw-0003qb-NJ
	for entmib@ietf.org; Wed, 02 Feb 2005 11:29:46 -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 j12GABTw024309
	for <entmib@ietf.org>; Wed, 2 Feb 2005 10:10:11 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXPVBGPW>; Wed, 2 Feb 2005 17:10:09 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C7A060@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "'Andy Bierman'" <abierman@cisco.com>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
Date: Wed, 2 Feb 2005 17:10:09 +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: 36b1f8810cb91289d885dc8ab4fc8172
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

Sorry Andy... I think you misinterpreted (probably
my fault for not being clear) my statements.

I wanted to make sure that you as author are OK with it
(which I assumed, but an ack is always nice) and
I want the WG to know we are doing this so anyone 
knows what we're doing.

Bert
> -----Original Message-----
> From: Andy Bierman [mailto:abierman@cisco.com]
> Sent: Wednesday, February 02, 2005 17:06
> To: Wijnen, Bert (Bert)
> Cc: Entmib-wg (E-mail)
> Subject: RE: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
> 
> 
> At 07:54 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
> >Andy writes:
> >> 
> >> At 07:05 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
> >> >Can the author/editor and/or the WG react please.
> >> >I need (if possible) an answer by tomorrow (Thursday) 11am US
> >> >eastern at the latest (that is, if we want to try and get this 
> >> >approved this week).
> >> 
> >> what are the edits? CLEI URI to CLEI URN. reference
> >> RFC 2396 -> RFC 3986.  Any other nits?  Can't you just carry 
> >> forward an edit list without an update?
> >> 
> >
> >I can do that if the WG agrees that that is indeed what we 
> want to do.
> >I cannot just make such changes without checking back with at least
> >the authors/editors or the WG.
> >
> >> It's not like these updates require anybody to comment.
> >> Who's going to object to fixing a nit?
> >> 
> >I can do those fixes with an RFC-Editor note if we agree that
> >is what we want to do.
> 
> I am 100% in favor of fixing typos and out-of-date references.
> I don't think you need to wait for the WG to comment on 
> non-controversial edits.  Any WG members out there in favor of 
> keeping typos and out-of-date references, please speak up now!
> 
> 
> >Bert
> >> 
> >> >Bert
> >> 
> >> Andy
> 
> Andy
> 
> 
> >> 
> >> 
> >> 
> >> >> -----Original Message-----
> >> >> From: entmib-bounces@ietf.org 
> >> >> [mailto:entmib-bounces@ietf.org]On Behalf
> >> >> Of Wijnen, Bert (Bert)
> >> >> Sent: Tuesday, February 01, 2005 01:05
> >> >> To: Entmib-wg (E-mail)
> >> >> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
> >> >> 
> >> >> 
> >> >> 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
> >> >> 
> >> 
> 

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


From entmib-bounces@ietf.org  Wed Feb  2 11:47:07 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 LAA26851
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 11:47: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 1CwNcw-0001rm-Pj; Wed, 02 Feb 2005 11:45:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwNTt-0006ph-So
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 11:35: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 LAA25295
	for <entmib@ietf.org>; Wed, 2 Feb 2005 11:35:49 -0500 (EST)
Received: from thumper.research.telcordia.com ([128.96.41.1])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNmH-0004hA-EV
	for entmib@ietf.org; Wed, 02 Feb 2005 11:54:54 -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
	j12GZ65u008843; Wed, 2 Feb 2005 11:35:06 -0500 (EST)
Received: from KAJ-2.research.telcordia.com
	(chood-2-1560897ud.cc.telcordia.com [128.96.171.154] (may be forged))
	by shannon.research.telcordia.com (8.9.3/8.9.3) with ESMTP id LAA05658; 
	Wed, 2 Feb 2005 11:35:02 -0500 (EST)
Message-Id: <6.1.2.0.2.20050202113127.048f8ba8@128.96.81.11>
X-Sender: kaj@128.96.81.11
X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0
Date: Wed, 02 Feb 2005 11:34:46 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Kaj Tesink <kaj@research.telcordia.com>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl
	.lucent.com>
References: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl.lucent.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Spam-Score: 0.0 (/)
X-Scan-Signature: a1852b4f554b02e7e4548cc7928acc1f
Cc: "Entmib-wg \(E-mail\)" <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 10:54 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
>Andy writes:
> >
> > At 07:05 AM 2/2/2005, Wijnen, Bert (Bert) wrote:
> > >Can the author/editor and/or the WG react please.
> > >I need (if possible) an answer by tomorrow (Thursday) 11am US
> > >eastern at the latest (that is, if we want to try and get this
> > >approved this week).
> >
> > what are the edits? CLEI URI to CLEI URN. reference
> > RFC 2396 -> RFC 3986.  Any other nits?  Can't you just carry
> > forward an edit list without an update?
> >
>
>I can do that if the WG agrees that that is indeed what we want to do.
>I cannot just make such changes without checking back with at least
>the authors/editors or the WG.
>
> > It's not like these updates require anybody to comment.
> > Who's going to object to fixing a nit?
> >
>I can do those fixes with an RFC-Editor note if we agree that
>is what we want to do.


as i was the troublemaker asking for this object:
agree with Andy; simple nits & no problem

kaj



>Bert
> >
> > >Bert
> >
> > Andy
> >
> >
> >
> > >> -----Original Message-----
> > >> From: entmib-bounces@ietf.org
> > >> [mailto:entmib-bounces@ietf.org]On Behalf
> > >> Of Wijnen, Bert (Bert)
> > >> Sent: Tuesday, February 01, 2005 01:05
> > >> To: Entmib-wg (E-mail)
> > >> Subject: [Entmib] FW: DISCUSS: draft-ietf-entmib-v3-07.txt
> > >>
> > >>
> > >> 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
> > >>
> >
>
>_______________________________________________
>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  Wed Feb  2 11:48: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 LAA26958
	for <entmib-archive@lists.ietf.org>; Wed, 2 Feb 2005 11:48: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 1CwNcy-0001sp-6A; Wed, 02 Feb 2005 11:45:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1CwNUo-000720-Jh
	for entmib@megatron.ietf.org; Wed, 02 Feb 2005 11:36: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 LAA25433
	for <entmib@ietf.org>; Wed, 2 Feb 2005 11:36:45 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwNnD-0004kF-Ef
	for entmib@ietf.org; Wed, 02 Feb 2005 11:55:51 -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 272777; Wed, 02 Feb 2005 11:35:07 -0500
Mime-Version: 1.0
Message-Id: <p06200703be26b1a84748@[10.0.0.171]>
In-Reply-To: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl.lucent.com>
References: <7D5D48D2CAA3D84C813F5B154F43B15503C7A05E@nl0006exch001u.nl.lucent.com>
Date: Wed, 2 Feb 2005 11:35:45 -0500
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
From: Margaret Wasserman <margaret@thingmagic.com>
Subject: RE: [Entmib] FW: DISCUSS:  draft-ietf-entmib-v3-07.txt
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
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


>I can do those fixes with an RFC-Editor note if we agree that
>is what we want to do.

Ted's suggested changes look reasonable and non-controversial to me, 
so this seems like a good way forward.

Does anyone object to this plan?

Margaret

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


From entmib-bounces@ietf.org  Thu Feb  3 11:40: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 LAA13302
	for <entmib-archive@lists.ietf.org>; Thu, 3 Feb 2005 11:40: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 1Cwjon-0007DU-74; Thu, 03 Feb 2005 11:26:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32) id 1Cwjgz-0003km-Hj
	for entmib@megatron.ietf.org; Thu, 03 Feb 2005 11:18: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 LAA10876
	for <entmib@ietf.org>; Thu, 3 Feb 2005 11:18:50 -0500 (EST)
Received: from ihemail1.lucent.com ([192.11.222.161])
	by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwjzX-0003Ry-PO
	for entmib@ietf.org; Thu, 03 Feb 2005 11:38:06 -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 j13GIHgf015306
	for <entmib@ietf.org>; Thu, 3 Feb 2005 10:18:17 -0600 (CST)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service
	(5.5.2657.72) id <ZXPVCDS0>; Thu, 3 Feb 2005 17:18:15 +0100
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15503C7A075@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "'Margaret Wasserman'" <margaret@thingmagic.com>, subrah@cisco.com
Subject: RE: [Entmib] I-D ACTION:draft-ietf-entmib-v3-07.txt
Date: Thu, 3 Feb 2005 17:17:48 +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: 156eddb66af16eef49a76ae923b15b92
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

I have added this as an RFC-Editor not in I-D tracker

> -----Original Message-----
> From: entmib-bounces@ietf.org 
> [mailto:entmib-bounces@ietf.org]On Behalf
> Of Margaret Wasserman
> Sent: Friday, January 21, 2005 14:41
> To: subrah@cisco.com; Internet-Drafts@ietf.org
> Cc: entmib@ietf.org; i-d-announce@ietf.org
> Subject: Re: [Entmib] I-D ACTION:draft-ietf-entmib-v3-07.txt
> 
> 
> 
> 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
> 

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


From entmib-bounces@ietf.org  Fri Feb  4 14:09: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 OAA24610
	for <entmib-archive@lists.ietf.org>; Fri, 4 Feb 2005 14:09:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cx8mW-00039g-Jj; Fri, 04 Feb 2005 14:06:16 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1Cx8fJ-0002Km-Kl; Fri, 04 Feb 2005 13:58:49 -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 NAA23812;
	Fri, 4 Feb 2005 13:58:28 -0500 (EST)
Received: from [204.9.221.21] (helo=thingmagic.com)
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1Cx8xm-0000nx-E3; Fri, 04 Feb 2005 14:17:57 -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 280300; Fri, 04 Feb 2005 13:56:29 -0500
Mime-Version: 1.0
Message-Id: <p06200700be2974ce5773@[10.0.0.171]>
Date: Fri, 4 Feb 2005 13:57:38 -0500
To: iesg@ietf.org, isoc-board@isoc.org, int-chairs@ietf.org, entmib@ietf.org,
        proto-team@ietf.org, edu-team@ietf.org, iab@ietf.org,
        iesg-secretary@ietf.org
From: Margaret Wasserman <margaret@thingmagic.com>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"
X-Spam-Score: 0.0 (/)
X-Scan-Signature: de4f315c9369b71d7dd5909b42224370
Subject: [Entmib] Mail Bouncing
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


[This message is sent to many lists.  Please do not reply all.]

Hi All,

I am aware that my e-mail has been bouncing off-and-on over the past 
~18 hours.  There was a major water main break in the street outside 
our building (Broadway in Kendall Square, Cambridge) and electricity 
and water were shut off overnight in a multi-block area.  Major 
services are back on-line now, but there may be some glitches through 
the weekend.

Please resend anything important that bounces, especially if you are 
expecting an action or response from me.

Sorry,
Margaret

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


From entmib-bounces@ietf.org  Sat Feb 12 07:28:46 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 HAA24507
	for <entmib-archive@lists.ietf.org>; Sat, 12 Feb 2005 07:28:46 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CzwNC-0002MO-23; Sat, 12 Feb 2005 07:27:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by megatron.ietf.org with esmtp (Exim 4.32)
	id 1CyY1Q-0004DP-1w; Tue, 08 Feb 2005 11:15:28 -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 LAA21290;
	Tue, 8 Feb 2005 11:15:26 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71])
	by ietf-mx.ietf.org with esmtp (Exim 4.33)
	id 1CyYL3-00086A-D0; Tue, 08 Feb 2005 11:35:45 -0500
Received: from apache by megatron.ietf.org with local (Exim 4.32)
	id 1CyXxO-0003EE-E6; Tue, 08 Feb 2005 11:11:18 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Message-Id: <E1CyXxO-0003EE-E6@megatron.ietf.org>
Date: Tue, 08 Feb 2005 11:11:18 -0500
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c
X-Mailman-Approved-At: Sat, 12 Feb 2005 07:27:40 -0500
Cc: entmib mailing list <entmib@ietf.org>,
        entmib chair <margaret@thingmagic.com>,
        Internet Architecture Board <iab@iab.org>,
        RFC Editor <rfc-editor@rfc-editor.org>
Subject: [Entmib] Protocol Action: 'Entity MIB (Version 3)' to Proposed 
 Standard 
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 IESG has approved the following document:

- 'Entity MIB (Version 3) '
   <draft-ietf-entmib-v3-07.txt> as a Proposed Standard

This document is the product of the Entity MIB Working Group. 

The IESG contact persons are Bert Wijnen and David Kessens.

Technical Summary
 
 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). 

Working Group Summary
 
 The working group has consensus to publish this document as a Proposed
 Standard RFC.  
 
Protocol Quality
 
 The document has been reviewed for the IESG by Bert Wijnen

RFC-Editor notes:

1. Please change all occurecces of "RFC 2396" and "[RFC2396]" into
   "RFC 3986" and "[RFC3986]"
2. Please change normative reference [RFC2396] into [RFC3986] with
   appropriate change of title and document info.
3. On page 11, 4th line from bottom, change
   OLD:
     containing a Common Language Equipment Identifier (CLEI) URI for
   NEW:
     containing a Common Language Equipment Identifier (CLEI) URN for
4. On page 15 section 2.15.2 change
   OLD:
     entity, such as a Common Language Equipment Identifier (CLEI) URI.
   NEW:
     entity, such as a Common Language Equipment Identifier (CLEI) URN.

5. On page 12, remove an incorrect sentence at end of 2st para
   OLD:
     be omitted by the agent.  Note that this table is deprecated in
     version 3 of the Entity MIB.
   NEW: 
     be omitted by the agent.


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


