From mailman-admin@ietf.org  Tue Apr  1 11:31:02 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA27200
	for <entmib-archive@lists.ietf.org>; Tue, 1 Apr 2003 11:31:01 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31GsoK30567
	for <entmib-archive@lists.ietf.org>; Tue, 1 Apr 2003 11:54:50 -0500
Date: Tue, 01 Apr 2003 11:54:50 -0500
Message-ID: <20030401165450.29326.76435.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: entmib-archive@ietf.org
X-No-Archive: yes
X-Ack: no
Sender: mailman-admin@ietf.org
Errors-To: mailman-admin@ietf.org
X-BeenThere: mailman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk

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

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

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

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


                              Note Well

All statements related to the activities of the IETF and addressed to
the IETF are subject to all provisions of Section 10 of RFC 2026,
which grants to the IETF and its participants certain licenses and
rights in such statements. Such statements include verbal statements
in IETF meetings, as well as written and electronic communications
made at any time or place, which are addressed to

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

Statements made outside of an IETF meeting, mailing list or other
function, that are clearly not intended to be input to an IETF
activity, group or function, are not subject to these provisions.

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


If you have questions, problems, comments, etc, send them to
mailman-owner@www1.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-admin@ietf.org  Thu Apr 17 20:48:04 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15360
	for <entmib-archive@lists.ietf.org>; Thu, 17 Apr 2003 20:48:04 -0400 (EDT)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3I0uE823922;
	Thu, 17 Apr 2003 20:56:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3I0t1823884
	for <entmib@optimus.ietf.org>; Thu, 17 Apr 2003 20:55:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15269
	for <entmib@ietf.org>; Thu, 17 Apr 2003 20:45:10 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196K1J-0003pK-00
	for entmib@ietf.org; Thu, 17 Apr 2003 20:46:25 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 196K1I-0003pC-00
	for entmib@ietf.org; Thu, 17 Apr 2003 20:46:24 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.43])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA01998
	for <entmib@ietf.org>; Thu, 17 Apr 2003 17:45:37 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030417204218.02d03b58@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 17 Apr 2003 20:44:07 -0400
To: entmib@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=====================_180899980==_"
Subject: [Entmib] Minutes from SF
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>,
	<mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
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>

--=====================_180899980==_
Content-Type: text/plain; charset="us-ascii"; format=flowed


Here are the minutes that I took during our Entity MIB meeting
in SF -- sorry they are a bit late.

Please let me know if there are any mistakes or omissions.

Thanks,
Margaret



--=====================_180899980==_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="Entity_MIB_Minutes_Mar03.txt"


Entity MIB (entmib) Minutes
IETF 56 San Francisco
Tuesday, March 18, 2003, 1300-1400
==================================

AGENDA:

Intro and Agenda Bashing -- Margaret Wasserman (5 min)


Document & Milestones Status -- Margaret (20 min)
        - Review outstanding milestones
        - Entity MIB Implementation Report Status
        - Next Steps


Entity State MIB -- Sharon Chisholm (20 min)
        - Open Issues
        - Next Steps


Wrap-up and Action Items -- Margaret (5 min)


Reading List:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-00.txt

MINUTES:

Entity Senor MIB Discussion:

No implementations from those in room.  Margaret to poll list.  IF
no implementations available, we will retry in 4-6 months.

Entity MIB Discussion:

Discussion of the current status of the Entity MIB and implementation 
reports.  

CONSENSUS:  Deprecate the LP mapping table and submit for DS.

Discussion of the changes since PS:  new CPU enum and new TC.

CONSENSUS:  Submit the document for DS, even with changes.

Entity State MIB discussion:

Open issues against January 03 version:
	- Dave's email address is wrong
	- Boilerplate needs updating

The document needs to be very explicit that it is a sparse augments in
both directions.  A not-applicable enum would be easier to deal with
than holes, so we will add that.

There are enums introduced that are not in the ITU documents.  Should
give explicit eplanation of what they mean -- perhaps pointer to the
alarm stuff that is their source.

Reference clauses in the TCs to ITU documents.

CONSENSUS:  Agreement to make the three changes listed above.

Editorial comment:  Some terms are used that are not explained first,
for instance reference to a stack (ITU folks might not know what 
this is), locked/unlocked (non ITU folks may not know what this is).
Would be good to add references for terminology.  

Also, there may be subtle differences for terminology about reduncancy 
(primary/secondary and active/backup).

Will try to get an update out by the end of March(?).  Then perhaps
ready for WG last call?

Andy raised issue with possible congestion/redundant traps when an
event happens that affects the whole network.  May have issues when
the a board goes down and all sub-systems also go down (sympathetic
notification issues). 

Concerned about the case of a very large box (10-20,000 interfaces).
Doesn't want to receive 20,000 link downs and 20,000 oper status
downs coming from the box.   

The sympathetic notification issue is actually separate from the
congestion issue.  It might make sense for this MIB to talk about
controlling sympathetic notifications, but the congestion issue
would need to be considered at the overall SNMP level -- maybe
a separate WG?

Issues are related to disman alarm work.  May be able to use
some mechanisms for sympathetic alarm suppression from there.
Also will look at RFC 2863.

Action Items:

Margaret to poll list for Sensor Entity MIB implementations

Andy to update Entity MIB to:
	- deprecate the LP mapping table
	- add conformance with/without CPU enum
	- new boilerplate

Margaret to post implementation reports for review (look
	at the RMON MIB reports)

Sharon and David to update the Entity State MIB to make
	the changes indicated above

Sharon and David to consider possible solutions for the
	congestion/sympathetic alarm problem


--=====================_180899980==_--


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


From mailnull@www1.ietf.org  Thu Apr 17 20:48:34 2003
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged))
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15386
	for <entmib-archive@odin.ietf.org>; Thu, 17 Apr 2003 20:48:34 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3I0vtG23960
	for entmib-archive@odin.ietf.org; Thu, 17 Apr 2003 20:57:55 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3I0uE823922;
	Thu, 17 Apr 2003 20:56:14 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h3I0t1823884
	for <entmib@optimus.ietf.org>; Thu, 17 Apr 2003 20:55:01 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA15269
	for <entmib@ietf.org>; Thu, 17 Apr 2003 20:45:10 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196K1J-0003pK-00
	for entmib@ietf.org; Thu, 17 Apr 2003 20:46:25 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 196K1I-0003pC-00
	for entmib@ietf.org; Thu, 17 Apr 2003 20:46:24 -0400
Received: from IDLEWYLDE.windriver.com ([147.11.233.43])
	by mail.wrs.com (8.9.3/8.9.1) with ESMTP id RAA01998
	for <entmib@ietf.org>; Thu, 17 Apr 2003 17:45:37 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030417204218.02d03b58@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 17 Apr 2003 20:44:07 -0400
To: entmib@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Mime-Version: 1.0
Content-Type: multipart/mixed;
	boundary="=====================_180899980==_"
Subject: [Entmib] Minutes from SF
Sender: entmib-admin@ietf.org
Errors-To: entmib-admin@ietf.org
X-BeenThere: entmib@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/entmib>,
	<mailto:entmib-request@ietf.org?subject=unsubscribe>
List-Id: IETF Entity MIB WG <entmib.ietf.org>
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>

--=====================_180899980==_
Content-Type: text/plain; charset="us-ascii"; format=flowed


Here are the minutes that I took during our Entity MIB meeting
in SF -- sorry they are a bit late.

Please let me know if there are any mistakes or omissions.

Thanks,
Margaret



--=====================_180899980==_
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: attachment; filename="Entity_MIB_Minutes_Mar03.txt"


Entity MIB (entmib) Minutes
IETF 56 San Francisco
Tuesday, March 18, 2003, 1300-1400
==================================

AGENDA:

Intro and Agenda Bashing -- Margaret Wasserman (5 min)


Document & Milestones Status -- Margaret (20 min)
        - Review outstanding milestones
        - Entity MIB Implementation Report Status
        - Next Steps


Entity State MIB -- Sharon Chisholm (20 min)
        - Open Issues
        - Next Steps


Wrap-up and Action Items -- Margaret (5 min)


Reading List:
http://www.ietf.org/internet-drafts/draft-ietf-entmib-v3-00.txt
http://www.ietf.org/internet-drafts/draft-ietf-entmib-state-00.txt

MINUTES:

Entity Senor MIB Discussion:

No implementations from those in room.  Margaret to poll list.  IF
no implementations available, we will retry in 4-6 months.

Entity MIB Discussion:

Discussion of the current status of the Entity MIB and implementation 
reports.  

CONSENSUS:  Deprecate the LP mapping table and submit for DS.

Discussion of the changes since PS:  new CPU enum and new TC.

CONSENSUS:  Submit the document for DS, even with changes.

Entity State MIB discussion:

Open issues against January 03 version:
	- Dave's email address is wrong
	- Boilerplate needs updating

The document needs to be very explicit that it is a sparse augments in
both directions.  A not-applicable enum would be easier to deal with
than holes, so we will add that.

There are enums introduced that are not in the ITU documents.  Should
give explicit eplanation of what they mean -- perhaps pointer to the
alarm stuff that is their source.

Reference clauses in the TCs to ITU documents.

CONSENSUS:  Agreement to make the three changes listed above.

Editorial comment:  Some terms are used that are not explained first,
for instance reference to a stack (ITU folks might not know what 
this is), locked/unlocked (non ITU folks may not know what this is).
Would be good to add references for terminology.  

Also, there may be subtle differences for terminology about reduncancy 
(primary/secondary and active/backup).

Will try to get an update out by the end of March(?).  Then perhaps
ready for WG last call?

Andy raised issue with possible congestion/redundant traps when an
event happens that affects the whole network.  May have issues when
the a board goes down and all sub-systems also go down (sympathetic
notification issues). 

Concerned about the case of a very large box (10-20,000 interfaces).
Doesn't want to receive 20,000 link downs and 20,000 oper status
downs coming from the box.   

The sympathetic notification issue is actually separate from the
congestion issue.  It might make sense for this MIB to talk about
controlling sympathetic notifications, but the congestion issue
would need to be considered at the overall SNMP level -- maybe
a separate WG?

Issues are related to disman alarm work.  May be able to use
some mechanisms for sympathetic alarm suppression from there.
Also will look at RFC 2863.

Action Items:

Margaret to poll list for Sensor Entity MIB implementations

Andy to update Entity MIB to:
	- deprecate the LP mapping table
	- add conformance with/without CPU enum
	- new boilerplate

Margaret to post implementation reports for review (look
	at the RMON MIB reports)

Sharon and David to update the Entity State MIB to make
	the changes indicated above

Sharon and David to consider possible solutions for the
	congestion/sympathetic alarm problem


--=====================_180899980==_--


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



