From mailnull@www1.ietf.org  Tue Apr  1 12:19:00 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 MAA01076
	for <disman-archive@odin.ietf.org>; Tue, 1 Apr 2003 12:19:00 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h31HgoZ12834
	for disman-archive@odin.ietf.org; Tue, 1 Apr 2003 12:42:50 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31HgoK12831
	for <disman-web-archive@optimus.ietf.org>; Tue, 1 Apr 2003 12:42:50 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA01049
	for <disman-web-archive@ietf.org>; Tue, 1 Apr 2003 12:18:28 -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 h31Hd8K11718;
	Tue, 1 Apr 2003 12:39:08 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h31HaoK10611
	for <disman@optimus.ietf.org>; Tue, 1 Apr 2003 12:36:50 -0500
Received: from zcars0m9.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA00557
	for <disman@ietf.org>; Tue, 1 Apr 2003 12:12:28 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.5/Switch-2.2.0) with ESMTP id h31HEsV27399
	for <disman@ietf.org>; Tue, 1 Apr 2003 12:14:54 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GDFVAC4S>; Tue, 1 Apr 2003 12:14:54 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD3406CE65F0@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: "Disman (E-mail)" <disman@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Disman] Alarm MIB Updates from Area Director Review
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Tue, 1 Apr 2003 12:14:53 -0500

hi

We are making good progress on the updated Alarm MIB to incorporate
the comments from Bert's area director review, and I just remembered
that it was suggested that the proposed edits be sent to the mailing
list for some pre-draft airing to ensure there were no issues with
them. These edits were previously discussed in the meeting in
San Francisco.

We had hoped to get the updated draft in today, but I guess we'll
wait until Thursdays now.

Summary of Area Director Review Comments
	1. Boilerplate 
	2. IANA Considerations 
	3. Time Passes ... Things Change 
	4. Data Types and Ranges
	5. SMI Nits 
	6. Resource ID
	7. Naming
	8. Storage Type

AD #1 - Boilerplate
  1.1 New MIB boilerplate is now preferred
    see www.ops.ietf.org 
    Nice thing is that it is much shorter and has far less references.
  1.2 New MIB security guidelines to be followed
    This one is a bit more elaborate than what you 
  1.3 We want MIB Copyright in the MODULE-IDENTITY in the DESCRIPTION
clause. 
     See recent    discussions on MIBS mailing list and in
           draft-ietf-ops-mib-review-guidelines-01.txt
  1.4 Page 4, you may want to add [RFC2119] reference to the text
Proposal: Make these changes

AD #1.5 - Boilerplate
  RFCs that contain MIB modules from which you IMPORT anything must be
referenced in 
  a normative way. I say this, because for example the new boilerplate no
longer
  references RFC3411, but since you IMPORT from the MIB module in that doc,
it should  
  still be listed as normative reference
Proposal: Make this change

AD #2.1 IANA Considerations
  In the IANA maintained IANA-ITU-ALARM-TC mib, need text in DESCRIPTION
clause the
  rules/guidelines for IANA on how to add/change stuff in this MIB module.
  Also need a (normative reference) to the IANA web site where this IANA
maintained 
  MIB module will be placed. 
Proposal: The IANA Considerations section contains some description, but
will add text
          specifically to DESCRIPTION Clause. Will also add reference to
IANA website.

AD #2.2 IANA Considerations
  I would change this:
         DESCRIPTION
          "Initial version, published as RFC XXXX."
         ::= { mib-2 xx }
  Into
         DESCRIPTION
          "Initial version, published as RFC XXXX."
           -- RFC-Editor assigns XXXX
         ::= { mib-2 xx } -- to be assigned by IANA
Proposal: Make this change

AD #3.1 - Time passes ... Things Change
  Copyrights need updating.
  same for dates in MIB modules.
Proposal: Update

AD #3.2 - Time passes ... Things Change
  Working group mailing list has moved
  Needs to be updated
Proposal: Update

AD #4.1 - Data Types and Ranges
  I see:
    alarmModelVarbindIndex and alarmClearMaximum are  Integer32
  Does a negative value ever make sense?
Proposal: Change to Unsigned 32

AD #4.2 - Data Types and Ranges 
  alarmActiveEngineID is SYNTAX SnmpEngineID with a description indicating
that 
  a zero length string is possible.   
  But SnmpEngineID, as specified in RFC3411 has a SIZE(5..32).
  So it cannot be a zero length string. 
  Need either A common TC of LocalSnmpEngineOrSnmpEngineID 
      SYNTAX      OCTET STRING (SIZE (0 | 5..32))
Proposal: Create this TC


AD #4.3 - Data Types and Ranges
  I see: 
    alarmActiveContextName OBJECT-TYPE
      SYNTAX      SnmpAdminString
  I wonder if it would not be (much) better to do:
    alarmActiveContextName OBJECT-TYPE
      SYNTAX      SnmpAdminString (SIZE (0..32))
  After all, a contextName can only have that size as far as I know. Or at
least, 
  we use that size in all the SNMP MIB modules we have created so far.
  Occurs in alarmClearTable also
Proposal: Add range to both

AD #5.1 - SMI Nits
  ianaItuAlarmNumbers MODULE-IDENTITY needs a REVISION clause
Proposal: Add one

AD #5.2 - SMI Nits
  I see Underscores in the IANA-ITU-ALARM-TC mib. Formally they are not
allowed.
Proposal: Remove them

AD #5.3 - SMI Nits
  In the ITU-ALARM-TC module, I see references in the TC DESCRIPTION
clauses. 
  Would it not be better to use a REFERENCE clause?
Proposal: Add REFERENCE clauses

AD #5.4 SMI Nits
  SMIlint complains about groups not referenced:
    `ituAlarmServiceUserGroup'
    `ituAlarmSecurityGroup'
    `ituAlarmStatisticsGroup'
    'alarmActiveStatsGroup'
    `alarmClearGroup'
    `alarmNotificationsGroup'
  Now... it is not mandatory to reference it. But see bottom of page 23 of 
  draft-ietf-ops-mib-review-guidelines-01.txt which recommends to actually
list them
Proposal: Still thinking about text in review guidelines; Keep as is for now

AD #6 - Resource ID
  When I see:     
    ResourceId ::= TEXTUAL-CONVENTION
  then I wonder... is this indeed a "resourceId" in the generic sense, or
have we 
  limited it here for the ALARM-MIB type of resources?
  In other words, would it maybe better to name it:
    AlarmResourceId ::= TEXTUAL-CONVENTION
  This to avoid conflict with other types of Resources?
Proposal: As the intention was to create a textual convention for general
use, 
          keep the name  but add some description to this effect

AD #7 - Naming
  Would      
    alarmItuTc MODULE-IDENTITY
  Be more consistent as
    ituAlarmTc MODULE-IDENTITY
Proposal: Change it

AD #8 - Storage Type
  I cannot find a StorageType object or any text in a DESCRIPTION clause 
  that explains the persistency behaviour for alarmModelTable
Proposal: Add description text indicating that he alarmModelTable is
persistent

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada



From mailman-admin@ietf.org  Tue Apr  1 12:35:18 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 MAA02544
	for <disman-archive@lists.ietf.org>; Tue, 1 Apr 2003 12:35:18 -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 h31Hx8K18497
	for <disman-archive@lists.ietf.org>; Tue, 1 Apr 2003 12:59:08 -0500
Date: Tue, 01 Apr 2003 12:59:08 -0500
Message-ID: <20030401175908.29326.74282.Mailman@www1.ietf.org>
Subject: ietf.org mailing list memberships reminder
From: mailman-owner@www1.ietf.org
To: disman-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, disman-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 disman-archive@lists.ietf.org:

List                                     Password // URL
----                                     --------  
disman@ietf.org                          hixour    
https://www1.ietf.org/mailman/options/disman/disman-archive%40lists.ietf.org


From mailnull@www1.ietf.org  Wed Apr  2 15:24:09 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 PAA07617
	for <disman-archive@odin.ietf.org>; Wed, 2 Apr 2003 15:24:09 -0500 (EST)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h32KmXL14882
	for disman-archive@odin.ietf.org; Wed, 2 Apr 2003 15:48:33 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h32KmWK14879
	for <disman-web-archive@optimus.ietf.org>; Wed, 2 Apr 2003 15:48:32 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07609
	for <disman-web-archive@ietf.org>; Wed, 2 Apr 2003 15:23:37 -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 h32KibK14624;
	Wed, 2 Apr 2003 15:44:37 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176])
	by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h32KhxK14560
	for <disman@optimus.ietf.org>; Wed, 2 Apr 2003 15:43:59 -0500
Received: from zcars0m9.nortelnetworks.com (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07027
	for <disman@ietf.org>; Wed, 2 Apr 2003 15:19:03 -0500 (EST)
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h32KLU721317
	for <disman@ietf.org>; Wed, 2 Apr 2003 15:21:31 -0500 (EST)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GDFVBANN>; Wed, 2 Apr 2003 15:21:31 -0500
Message-ID: <3549C09B853DD5119B540002A52CDD3406D611EB@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: "Disman (E-mail)" <disman@ietf.org>
X-Mailer: Internet Mail Service (5.5.2653.19)
Subject: [Disman] Alarm MIB Edits from Harrie's Review
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 2 Apr 2003 15:21:27 -0500

hi

In San Francisco we agreed that, even though we are long
past working group last call, that it would be good to go
through Harrie's detailed review of the Alarm MIB and
classify his feedback into three categories: Gating;
not gating, but requires discussion; and editorial. The
intention being that anything truly gating should be
addressed before forwarding to the IESG and that anything
purely editorial could be done without slowing the progress
of the document.

I'll respond to Harry's email in more detail later, but
we went through it and did not find anything gating. We
did find some editorial changes that we think we can
squeeze into tomorrow's update. I figured I'd give these
a pre-airing on the list as well so we can then send the
update straight into the IESG.

Here goes:

H1
> > 3.3.5 Identifying Resource under Alarm
> >
> >    This MIB provides a generic method for identifying the resource by
>
> Which MIB?? There are 2 in this document. The use of 'This MIB' happens
> also later in the document. It may be mis-leading and, therefore,
> can better be specified which MIB is ment.
Proposal: Clarify which MIB

H2 

> >    sysUptime and snmpTrapOID shall always be stored in the active alarm
>
> 'shall always' -> 'SHALL'
Proposal: Make this change

H3
> > 4.1.4 Active Alarm Resource Identifier
<clip>
> >    matched alarmModelVarbindSubtree. If no match is found, then
> >    alarmModelResourceId is simply the value of
> > alarmModelResourcePrefix.
>
> 'alarmModelResourceId' -> 'alarmActiveResourceId'.
Proposal: Make this change

H4

> >    In addition to this, the variable bindings from the Notifications
> >    that signal the alarm state transitions are stored in the active
> >    alarm table.
>
> 'active alarm table' -> 'active alarm variable table'
Proposal: make this change

H5

> >    B) Consider an alarm modelled using the bgpBackwardTransition
>
> 'B)' -> 'C)'
Proposal: Make this change

H6

> A reference to the WG web-page?? As recommended in the
> mib-reviewers id draft-ietf-ops-mib-review-guidelines-01.txt
> (also valid for the other MODULE-IDENTITY-s)
Proposal: Make this change

H7

> >    alarmActiveVariables OBJECT-TYPE
> >       DESCRIPTION
> >           "The number of variables in alarmActiveVariableTable for this
> >           alarm. Also, the number of varbinds for the notification
> >           associated with this alarm state."
>
> I believe that the part 'Also,...' makes it more unclear on the value,
> since there is a difference in varbinds between V2 or V1
> trap/notification
> PDU. I suggest dropping that. The table refered to,
> 'alarmActiveVariableTable',
> provides enough information.
Proposal: Drop second sentence

H8

> >    alarmClearIndex OBJECT-TYPE
> >       SYNTAX     Unsigned32 (1..4294967295)
> >       MAX-ACCESS not-accessible
> >       STATUS     current
> >       DESCRIPTION
> >           "A strictly monotonically increasing integer which acts
> >           as the index of entries within the named alarm list.
> >           It wraps back to 1 after it reaches its maximum value.
> >
> >           This object has the same value as the alarmActiveIndex that
> >           this alarm instance had when it was active."
> >       ::= { alarmClearEntry 1 }
>
> The value will always have the same value as the alarmActiveIndex, but I
> believe that alarms will not always be cleared in the same order as they
> are active. Thus the requirement of a 'strictly monotonically increasing
> integer' is not usefull here (maybe even not possible).
Proposal: Drop the bit about being monotonically increasing

H9

> >    alarmClearState NOTIFICATION-TYPE
> >       DESCRIPTION
> >         "An instance of the alarm indicated by
> >         alarmActiveModelPointer has been cleared against
> >         the entity indicated by alarmACtiveResourceId."
>                                          ^
> 'alarmACtiveResourceId' -> 'alarmActiveResourceId'
Proposal: Make this change

H10

> >    ituAlarmActiveServiceUser OBJECT-TYPE
> >       DESCRIPTION
> >       "Represents the SericeUser object from [X.736]."
>                              ^
> 'SericeUser' -> 'ServiceUser'
Proposal: Make this change

H11

> > 6.5 RMON Alarm Example
> >
> >   alarmModelIndex                  6
> >   alarmModelState                  2
> >   alarmModelNotificationId         RisingAlarm
> >   alarmModelVarbindIndex           0
> >   alarmModelVarbindValue           0
> >   alarmModelDescription            "RMON Rising Alarm"
> >   alarmModelSpecificPointer        0.0
> >   alarmModelRowStatus              active (1)
> >   alarmModelVarbindSubtree         alarmIndex
> >   alarmModelResourcePrefix         0.0
> >   alarmModelRowStatus              active (1)
>
> Has twice 'alarmModelRowStatus' (first need to be deleted).
Proposal: Make this change

Sharon Chisholm
Portfolio Integration
Nortel Networks
Ottawa, Canada



From mailnull@www1.ietf.org  Mon Apr  7 07:13:08 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 HAA15262
	for <disman-archive@odin.ietf.org>; Mon, 7 Apr 2003 07:13:08 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h37BHIf01359
	for disman-archive@odin.ietf.org; Mon, 7 Apr 2003 07:17:18 -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 h37BHI801356
	for <disman-web-archive@optimus.ietf.org>; Mon, 7 Apr 2003 07:17:18 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA15243
	for <disman-web-archive@ietf.org>; Mon, 7 Apr 2003 07:12:37 -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 h37BFh801286;
	Mon, 7 Apr 2003 07:15:43 -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 h37BEB801214
	for <disman@optimus.ietf.org>; Mon, 7 Apr 2003 07:14:11 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14816;
	Mon, 7 Apr 2003 07:09:29 -0400 (EDT)
Message-Id: <200304071109.HAA14816@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-alarm-mib-10.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Mon, 07 Apr 2003 07:09:29 -0400

--NextPart

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

	Title		: Alarm MIB
	Author(s)	: S. Chisholm, D. Romascanu
	Filename	: draft-ietf-disman-alarm-mib-10.txt
	Pages		: 65
	Date		: 2003-4-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 management objects used for defining
and storing alarms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-10.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-disman-alarm-mib-10.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-disman-alarm-mib-10.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:	<2003-4-4115634.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-alarm-mib-10.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-alarm-mib-10.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-4-4115634.I-D@ietf.org>

--OtherAccess--

--NextPart--




From mailnull@www1.ietf.org  Mon Apr  7 18:21:11 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 SAA09037
	for <disman-archive@odin.ietf.org>; Mon, 7 Apr 2003 18:21:11 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h37MPZs18596
	for disman-archive@odin.ietf.org; Mon, 7 Apr 2003 18:25:35 -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 h37MPZ818593
	for <disman-web-archive@optimus.ietf.org>; Mon, 7 Apr 2003 18:25:35 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09018
	for <disman-web-archive@ietf.org>; Mon, 7 Apr 2003 18:20:40 -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 h37MIK818275;
	Mon, 7 Apr 2003 18:18:24 -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 h37MHL818223
	for <disman@optimus.ietf.org>; Mon, 7 Apr 2003 18:17:21 -0400
Received: from hawk.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA08516
	for <disman@ietf.org>; Mon, 7 Apr 2003 18:12:25 -0400 (EDT)
Received: from h-69-3-241-211.snvacaid.covad.net ([69.3.241.211] helo=oemcomputer)
	by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 192etF-0006E5-00
	for disman@ietf.org; Mon, 07 Apr 2003 15:14:57 -0700
Message-ID: <00ed01c2fd53$4926fd00$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <disman@ietf.org>
References: <200304071109.HAA14816@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] last chance on draft-ietf-disman-alarm-mib-10.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Mon, 7 Apr 2003 15:16:06 -0700

Hi -

Thanks to Sharon and Dan for posting the latest revision of the
Alarm MIB internet draft.  Before returning it to our AD (Bert) and the
IESG, I'd like to verify that the WG is still happy with the updated
document.  Please take the time to read the document.  Please
post a message to the disman WG mailing when you have done
so, and indicate whether you (still) agree that it's ready for
submission as a Proposed Standard.  (See RFC 2026 section 4.1.1
for details on the requirements.)  Assuming no significant
problems are identified, I plan to hand it to Bert on Monday,
April 14, 2003.

Randy
Disman WG chair




From mailnull@www1.ietf.org  Tue Apr  8 14:58:40 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 OAA26636
	for <disman-archive@odin.ietf.org>; Tue, 8 Apr 2003 14:58:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h38J3Uf20035
	for disman-archive@odin.ietf.org; Tue, 8 Apr 2003 15:03:30 -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 h38J3T820032
	for <disman-web-archive@optimus.ietf.org>; Tue, 8 Apr 2003 15:03:29 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26613
	for <disman-web-archive@ietf.org>; Tue, 8 Apr 2003 14:58:09 -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 h38J2d819938;
	Tue, 8 Apr 2003 15:02:39 -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 h38J1q819866
	for <disman@optimus.ietf.org>; Tue, 8 Apr 2003 15:01:52 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA26526;
	Tue, 8 Apr 2003 14:56:32 -0400 (EDT)
Message-Id: <200304081856.OAA26526@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-conditionmib-07.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Tue, 08 Apr 2003 14:56:32 -0400

--NextPart

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

	Title		: Alarm Reporting Control MIB
	Author(s)	: K. Lam, A. Huynh, D. Perkins
	Filename	: draft-ietf-disman-conditionmib-07.txt
	Pages		: 14
	Date		: 2003-4-8
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for controlling the reporting of 
alarm conditions.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-disman-conditionmib-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-disman-conditionmib-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:	<2003-4-8145458.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-conditionmib-07.txt

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

Content-Type: text/plain
Content-ID:	<2003-4-8145458.I-D@ietf.org>

--OtherAccess--

--NextPart--




From mailnull@www1.ietf.org  Tue Apr  8 16:28:13 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 QAA00799
	for <disman-archive@odin.ietf.org>; Tue, 8 Apr 2003 16:28:13 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h38KX4o27034
	for disman-archive@odin.ietf.org; Tue, 8 Apr 2003 16:33:04 -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 h38KX4827031
	for <disman-web-archive@optimus.ietf.org>; Tue, 8 Apr 2003 16:33:04 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00774
	for <disman-web-archive@ietf.org>; Tue, 8 Apr 2003 16:27:42 -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 h38KWD826967;
	Tue, 8 Apr 2003 16:32:13 -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 h38KVG826891
	for <disman@optimus.ietf.org>; Tue, 8 Apr 2003 16:31:16 -0400
Received: from mallard.mail.pas.earthlink.net (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00661
	for <disman@ietf.org>; Tue, 8 Apr 2003 16:25:53 -0400 (EDT)
Received: from h-68-164-77-93.snvacaid.covad.net ([68.164.77.93] helo=oemcomputer)
	by mallard.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 192zhi-0001PM-00
	for disman@ietf.org; Tue, 08 Apr 2003 13:28:26 -0700
Message-ID: <006001c2fe0d$879df060$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <disman@ietf.org>
References: <200304081856.OAA26526@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] Last Chance: alarm report control
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Tue, 8 Apr 2003 13:29:17 -0700

Hi -

> Title : Alarm Reporting Control MIB
> Author(s) : K. Lam, A. Huynh, D. Perkins
> Filename : draft-ietf-disman-conditionmib-07.txt
> Pages : 14
> Date : 2003-4-8
>
> This memo defines a portion of the Management Information Base (MIB)
> for use with network management protocols in TCP/IP-based internets.
> In particular, it defines objects for controlling the reporting of
> alarm conditions.
>
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-07.txt

Since this was sent to the WG mailing list a while back, I'd like to handle
this at the same time as the Alarm MIB.  So, *please* take the time to
read this document (it's only 14 pages!).  I'd like to give this back to
our AD on Monday, April 14.  Please post your comments, including
"this is good stuff" to the disman WG mailing list before then.  The goal
is to publish this as a Proposed Standard; see RFC 2026 section 4.1.1
for the requirements for this maturity level.

Randy
Disman WG chair




From mailnull@www1.ietf.org  Wed Apr  9 07:23:20 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 HAA22040
	for <disman-archive@odin.ietf.org>; Wed, 9 Apr 2003 07:23:20 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h39BSV003450
	for disman-archive@odin.ietf.org; Wed, 9 Apr 2003 07:28:31 -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 h39BSV803447
	for <disman-web-archive@optimus.ietf.org>; Wed, 9 Apr 2003 07:28:31 -0400
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA22033
	for <disman-web-archive@ietf.org>; Wed, 9 Apr 2003 07:22:49 -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 h39BRC803391;
	Wed, 9 Apr 2003 07:27:12 -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 h39BOX803207
	for <disman@optimus.ietf.org>; Wed, 9 Apr 2003 07:24:33 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21823;
	Wed, 9 Apr 2003 07:18:51 -0400 (EDT)
Message-Id: <200304091118.HAA21823@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-conditionmib-07.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 09 Apr 2003 07:18:51 -0400

--NextPart

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

	Title		: Alarm Reporting Control MIB
	Author(s)	: K. Lam, A. Huynh, D. Perkins
	Filename	: draft-ietf-disman-conditionmib-07.txt
	Pages		: 14
	Date		: 2003-4-8
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for controlling the reporting of 
alarm conditions.

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

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-disman-conditionmib-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-disman-conditionmib-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:	<2003-4-8145458.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-conditionmib-07.txt

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

Content-Type: text/plain
Content-ID:	<2003-4-8145458.I-D@ietf.org>

--OtherAccess--

--NextPart--




From mailnull@www1.ietf.org  Mon Apr 14 13:16:38 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 NAA12713
	for <disman-archive@odin.ietf.org>; Mon, 14 Apr 2003 13:16:38 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3EHONP07065
	for disman-archive@odin.ietf.org; Mon, 14 Apr 2003 13:24:23 -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 h3EHOM807061
	for <disman-web-archive@optimus.ietf.org>; Mon, 14 Apr 2003 13:24:22 -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 NAA12708
	for <disman-web-archive@ietf.org>; Mon, 14 Apr 2003 13:16:08 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1957bN-0003de-00
	for disman-web-archive@ietf.org; Mon, 14 Apr 2003 13:18:41 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 1957bM-0003da-00
	for disman-web-archive@ietf.org; Mon, 14 Apr 2003 13:18:40 -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 h3EHNQ807001;
	Mon, 14 Apr 2003 13:23:27 -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 h3EHKi806917
	for <disman@optimus.ietf.org>; Mon, 14 Apr 2003 13:20:44 -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 NAA12555
	for <disman@ietf.org>; Mon, 14 Apr 2003 13:12:29 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 1957Xq-0003c9-00
	for disman@ietf.org; Mon, 14 Apr 2003 13:15:02 -0400
Received: from hawk.mail.pas.earthlink.net ([207.217.120.22])
	by ietf-mx with esmtp (Exim 4.12)
	id 1957Xq-0003bw-00
	for disman@ietf.org; Mon, 14 Apr 2003 13:15:02 -0400
Received: from h-68-164-25-172.snvacaid.covad.net ([68.164.25.172] helo=oemcomputer)
	by hawk.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 1957Xr-0002Db-00
	for disman@ietf.org; Mon, 14 Apr 2003 10:15:03 -0700
Message-ID: <006b01c302a9$8ceee1a0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] Alarm documents
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Mon, 14 Apr 2003 10:16:13 -0700

Hi -

REMINDER: I need your comments (even "I've read it" or
"I haven't bothered to look at it") *today* on the Alarm MIB
and the Alarm Report Control internet drafts.

http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-10.txt
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-07.txt

Randy




From mailnull@www1.ietf.org  Mon Apr 14 18:45:41 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 SAA25888
	for <disman-archive@odin.ietf.org>; Mon, 14 Apr 2003 18:45:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3EMrWx31272
	for disman-archive@odin.ietf.org; Mon, 14 Apr 2003 18:53:32 -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 h3EMrW831269
	for <disman-web-archive@optimus.ietf.org>; Mon, 14 Apr 2003 18:53:32 -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 SAA25882
	for <disman-web-archive@ietf.org>; Mon, 14 Apr 2003 18:45:11 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195Cjn-0005x8-00
	for disman-web-archive@ietf.org; Mon, 14 Apr 2003 18:47:43 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195Cjm-0005x4-00
	for disman-web-archive@ietf.org; Mon, 14 Apr 2003 18:47:42 -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 h3EMr3831252;
	Mon, 14 Apr 2003 18:53:03 -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 h3EMm4831136
	for <disman@optimus.ietf.org>; Mon, 14 Apr 2003 18:48:04 -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 SAA25810
	for <disman@ietf.org>; Mon, 14 Apr 2003 18:39:43 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195CeW-0005wR-00
	for disman@ietf.org; Mon, 14 Apr 2003 18:42:16 -0400
Received: from albatross.mail.pas.earthlink.net ([207.217.120.120])
	by ietf-mx with esmtp (Exim 4.12)
	id 195CeV-0005wO-00
	for disman@ietf.org; Mon, 14 Apr 2003 18:42:15 -0400
Received: from h-68-165-65-126.snvacaid.covad.net ([68.165.65.126] helo=oemcomputer)
	by albatross.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 195CeE-0001l9-00; Mon, 14 Apr 2003 15:41:58 -0700
Message-ID: <000401c302d7$371a4ac0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <mreview@ops.ietf.org>, "Andy Bierman" <abierman@cisco.com>
Cc: <kzm@cisco.com>, "Disman \(E-mail\)" <disman@ietf.org>
References: <4.3.2.7.2.20030414124409.02463c48@fedex.cisco.com>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] Re: augmenting std MIBs to use TransportAddress
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Mon, 14 Apr 2003 15:42:59 -0700

Hi -

(I'm CC-ing the disman WG list since this thread
raises questions about RFC 3014.)

> Message-Id: <4.3.2.7.2.20030414124409.02463c48@fedex.cisco.com>
> Date: Mon, 14 Apr 2003 13:04:27 -0700
> To: mreview@ops.ietf.org
> From: Andy Bierman <abierman@cisco.com>
> Subject: augmenting std MIBs to use TransportAddress
> Cc: kzm@cisco.com
>
> Hi,
>
> I have a couple of Cisco MIB reviews that are augmentations
> of the NOTIFICATION-LOG-MIB (RFC 3014) and SNMP-TARGET-MIB
> (RFC 3413).  I'm having a little trouble interpreting sec
> 3.1.2 of RFC 3419.  These augmentations are 'replacing'
> the TAddress and TDomain objects with TransportAddress
> and TransportDomain objects.  The objects getting replaced:
>
> nlmLogEntry:
>     nlmLogEngineTAddress       TAddress
>     nlmLogEngineTDomain        TDomain
>
> snmpTargetAddrEntry:
>     snmpTargetAddrTDomain      TDomain
>     snmpTargetAddrTAddress     TAddress
>
> Q1) RFC 3014 seems to imply that we should use the old objects
>     for existing TAddress/TDomain values and use the new objects
>     for new values that TAddress/TDomain doesn't cover.  I think
>     this is broken.  I am telling the MIB designer to let the
>     new objects override the old ones if they are set, and
>     use the old objects if the new ones are not set.  Is this
>     what the last paragraph of 3.1.2 is suggesting (and I'm
>     just reading it wrong)?

I believe that paragraph is refering to the Object Indentifier
*values* defined in RFC 3419, not to the TCs.  I see no reason
to replace / override the objects in 3413 or 3014, and I think
the text in 3419 confirms this belief.

> Q2) What is the IETF plan for upgrading MIBs which use the old
>     TAddress/TDomain data types to use the types in RFC 3419?

I think the last paragraph in 3419 3.1.2 answers this: they
should continue to use the definitions from RFC 2579, along
with the specific object identifier values from 3419 as needed.

> thanks,
> Andy
>
>
>

Randy




From mailnull@www1.ietf.org  Tue Apr 15 17:17:57 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 RAA12410
	for <disman-archive@odin.ietf.org>; Tue, 15 Apr 2003 17:17:57 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3FLQFm06667
	for disman-archive@odin.ietf.org; Tue, 15 Apr 2003 17:26:15 -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 h3FLQF806664
	for <disman-web-archive@optimus.ietf.org>; Tue, 15 Apr 2003 17:26:15 -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 RAA12392
	for <disman-web-archive@ietf.org>; Tue, 15 Apr 2003 17:17:27 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195XqP-0004nn-00
	for disman-web-archive@ietf.org; Tue, 15 Apr 2003 17:19:57 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195XqP-0004nk-00
	for disman-web-archive@ietf.org; Tue, 15 Apr 2003 17:19:57 -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 h3FLPX806607;
	Tue, 15 Apr 2003 17:25:34 -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 h3FLO3806523
	for <disman@optimus.ietf.org>; Tue, 15 Apr 2003 17:24:03 -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 RAA12296
	for <disman@ietf.org>; Tue, 15 Apr 2003 17:15:15 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195XoH-0004mN-00
	for disman@ietf.org; Tue, 15 Apr 2003 17:17:45 -0400
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 195XoH-0004mC-00
	for disman@ietf.org; Tue, 15 Apr 2003 17:17:45 -0400
Received: from h-68-164-29-254.snvacaid.covad.net ([68.164.29.254] helo=oemcomputer)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 195XoK-0007dG-00
	for disman@ietf.org; Tue, 15 Apr 2003 14:17:48 -0700
Message-ID: <004a01c30394$9489ae40$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] Mystery bytes in draft-ietf-disman-alarm-mib-10.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Tue, 15 Apr 2003 14:18:37 -0700

Hi -

There are a bunch of mysterious non-ascii bytes in the
alarm MIB draft.  All the places where I'd expect an
ASCII form feed, there's a 0xe1.  More worrisome,
however, are 0xe1 bytes scattered throughout the
rest of the document:

0xe1 at line 843 position 27
0xe1 at line 945 position 17
0xe1 at line 1126 position 59
0xe1 at line 1126 position 60
0xe1 at line 1126 position 61
0xe1 at line 1814 position 60
0xe1 at line 1864 position 43
0xe1 at line 1864 position 45
0xe1 at line 2179 position 4
0xe1 at line 2179 position 5
0xe1 at line 2295 position 17
0xe1 at line 2305 position 51
0xe1 at line 2364 position 31
0xe1 at line 2364 position 32
0xe1 at line 2364 position 33
0xe1 at line 2371 position 17
0xe1 at line 2507 position 17
0xe1 at line 2525 position 17
0xe1 at line 2535 position 4
0xe1 at line 2536 position 4
0xe1 at line 2537 position 4
0xe1 at line 2537 position 11
0xe1 at line 2537 position 22
0xe1 at line 2538 position 4
0xe1 at line 2541 position 4
0xe1 at line 2587 position 13
0xe1 at line 2587 position 14
0xe1 at line 2588 position 17
0xe1 at line 2600 position 7
0xe1 at line 2614 position 7
0xe1 at line 2622 position 7
0xe1 at line 2656 position 55
0xe1 at line 2793 position 7
0xe1 at line 2793 position 8
0xe1 at line 2794 position 7
0xe1 at line 2794 position 8
0xe1 at line 2795 position 7
0xe1 at line 2795 position 8
0xe1 at line 2796 position 8
0xe1 at line 2838 position 6

Randy




From mailnull@www1.ietf.org  Tue Apr 15 17:31:16 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 RAA12643
	for <disman-archive@odin.ietf.org>; Tue, 15 Apr 2003 17:31:16 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3FLdYJ08087
	for disman-archive@odin.ietf.org; Tue, 15 Apr 2003 17:39:34 -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 h3FLdY808084
	for <disman-web-archive@optimus.ietf.org>; Tue, 15 Apr 2003 17:39:34 -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 RAA12603
	for <disman-web-archive@ietf.org>; Tue, 15 Apr 2003 17:30:45 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195Y3I-0004r3-00
	for disman-web-archive@ietf.org; Tue, 15 Apr 2003 17:33:16 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195Y3I-0004r0-00
	for disman-web-archive@ietf.org; Tue, 15 Apr 2003 17:33:16 -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 h3FLd3808070;
	Tue, 15 Apr 2003 17:39:03 -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 h3FLcO808010
	for <disman@optimus.ietf.org>; Tue, 15 Apr 2003 17:38:24 -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 RAA12584
	for <disman@ietf.org>; Tue, 15 Apr 2003 17:29:36 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195Y2B-0004qc-00
	for disman@ietf.org; Tue, 15 Apr 2003 17:32:07 -0400
Received: from conure.mail.pas.earthlink.net ([207.217.120.54])
	by ietf-mx with esmtp (Exim 4.12)
	id 195Y2A-0004qZ-00
	for disman@ietf.org; Tue, 15 Apr 2003 17:32:06 -0400
Received: from h-68-164-29-254.snvacaid.covad.net ([68.164.29.254] helo=oemcomputer)
	by conure.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 195Y2I-0005vk-00
	for disman@ietf.org; Tue, 15 Apr 2003 14:32:14 -0700
Message-ID: <005e01c30396$911ed300$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] draft-ietf-disman-conditionmib-07.txt oddities
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Tue, 15 Apr 2003 14:32:50 -0700

Hi -

Some minor oddities in draft-ietf-disman-conditionmib-07.txt,
mostly lines too long due to superfluous trailing blanks and lots
of TAB characters (0x09).

line 5 too long (122 characters) (trailing spaces)
line 7 too long (74 characters) (trailing spaces)
0x09 at line 8 position 65
line 59 too long (73 characters) (trailing spaces)
line 62 too long (73 characters) (trailing spaces)
line 72 too long (73 characters) (trailing spaces)
line 117 too long (74 characters) (trailing spaces)
line 145 too long (73 characters) (trailing spaces)
0x09 at line 158 position 1
0x09 at line 222 position 30
line 241 too long (78 characters)
0x09 at line 310 position 1
line 316 too long (73 characters) (trailing spaces)
0x09 at line 318 position 1
0x09 at line 318 position 2
0x09 at line 404 position 1
0x09 at line 405 position 1
0x09 at line 406 position 1
0x09 at line 406 position 2
0x09 at line 407 position 1
0x09 at line 410 position 1
0x09 at line 410 position 2
0x09 at line 411 position 1
0x09 at line 411 position 2
0x09 at line 413 position 1
0x09 at line 413 position 2
0x09 at line 414 position 1
0x09 at line 415 position 1
0x09 at line 415 position 2
0x09 at line 416 position 1
0x09 at line 416 position 2
0x09 at line 417 position 1
0x09 at line 417 position 2
0x09 at line 418 position 1
line 451 too long (73 characters) (trailing spaces)
line 490 too long (73 characters) (trailing spaces)
0x09 at line 541 position 56
0x09 at line 558 position 35
0x09 at line 558 position 37
0x09 at line 570 position 35
0x09 at line 570 position 37
line 651 too long (78 characters)
line 652 too long (79 characters) (trailing spaces)


I'll assume that this (along with the missing pagination) will get
fixed by the RFC editor.

Randy




From mailnull@www1.ietf.org  Wed Apr 16 03:03:17 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 DAA20620
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 03:03:17 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3G7BlM25053
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 03:11:47 -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 h3G7Bl825050
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 03:11:47 -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 DAA20565
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 03:02:46 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195gyr-0007AO-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 03:05:17 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195gyr-0007AJ-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 03:05:17 -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 h3G7BD824998;
	Wed, 16 Apr 2003 03:11:13 -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 h3G75U823883
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 03:05:30 -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 CAA20482
	for <disman@ietf.org>; Wed, 16 Apr 2003 02:56:30 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195gsn-00079A-00
	for disman@ietf.org; Wed, 16 Apr 2003 02:59:01 -0400
Received: from falcon.mail.pas.earthlink.net ([207.217.120.74])
	by ietf-mx with esmtp (Exim 4.12)
	id 195gsm-000797-00
	for disman@ietf.org; Wed, 16 Apr 2003 02:59:01 -0400
Received: from h-68-164-21-202.snvacaid.covad.net ([68.164.21.202] helo=oemcomputer)
	by falcon.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 195gss-0001cg-00; Tue, 15 Apr 2003 23:59:06 -0700
Message-ID: <003801c303e5$d5cbc040$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: <bwijnen@lucent.com>
Cc: "Disman \(E-mail\)" <disman@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] Alarm and Alarm Report Control MBs
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 00:00:16 -0700

Hi Bert -

The only issues that have surfaced with regard to
draft-ietf-disman-alarm-mib-10.txt and
draft-ietf-disman-conditionmib-07.txt are minor
typographical ones.  We think your comments have
all been addressed, as well as the ones raised by Harrie
Hazewinkel.

So, as disman WG chair, I'm handing these two back
to you to take to the IESG for consideration as Proposed
Standards.

Randy




From mailnull@www1.ietf.org  Wed Apr 16 06:51:15 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 GAA24833
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 06:51:15 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3GAxnO08416
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 06:59:49 -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 h3GAxn808413
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 06:59:49 -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 GAA24825
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 06:50:44 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kXS-0000HB-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 06:53:15 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kXS-0000H8-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 06:53:14 -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 h3GAxE808394;
	Wed, 16 Apr 2003 06:59:15 -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 h3GAuL808290
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 06:56:21 -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 GAA24726
	for <disman@ietf.org>; Wed, 16 Apr 2003 06:47:17 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kU7-0000GO-00
	for disman@ietf.org; Wed, 16 Apr 2003 06:49:47 -0400
Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kU6-0000GG-00
	for disman@ietf.org; Wed, 16 Apr 2003 06:49:46 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3GAnON02388
	for <disman@ietf.org>; Wed, 16 Apr 2003 06:49:24 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R194HQD>; Wed, 16 Apr 2003 12:49:23 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550159AC14@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>
Cc: "Disman (E-mail)" <disman@ietf.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Disman] RE: Alarm and Alarm Report Control MBs
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 12:49:21 +0200

Mmm... assuming the typographical ones are the ones
posted by Randy... I'd rather see those fixed...
Is it too much to ask to quickly spin another rev of
the docs?

Thanks,
Bert 

> -----Original Message-----
> From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> Sent: woensdag 16 april 2003 9:00
> To: bwijnen@lucent.com
> Cc: Disman (E-mail)
> Subject: Alarm and Alarm Report Control MBs
> 
> 
> Hi Bert -
> 
> The only issues that have surfaced with regard to
> draft-ietf-disman-alarm-mib-10.txt and
> draft-ietf-disman-conditionmib-07.txt are minor
> typographical ones.  We think your comments have
> all been addressed, as well as the ones raised by Harrie
> Hazewinkel.
> 
> So, as disman WG chair, I'm handing these two back
> to you to take to the IESG for consideration as Proposed
> Standards.
> 
> Randy
> 
> 



From mailnull@www1.ietf.org  Wed Apr 16 06:53:09 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 GAA24899
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 06:53:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3GB1hO08567
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 07:01:43 -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 h3GB1h808564
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 07:01:43 -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 GAA24870
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 06:52:39 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kZI-0000HV-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 06:55:09 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kZI-0000HS-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 06:55:08 -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 h3GB1B808509;
	Wed, 16 Apr 2003 07:01:11 -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 h3GAuM808292
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 06:56:22 -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 GAA24728
	for <disman@ietf.org>; Wed, 16 Apr 2003 06:47:17 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kU7-0000GQ-00
	for disman@ietf.org; Wed, 16 Apr 2003 06:49:47 -0400
Received: from ihemail1.lucent.com ([192.11.222.161] helo=ihemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kU6-0000GF-00
	for disman@ietf.org; Wed, 16 Apr 2003 06:49:46 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by ihemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3GAnON02390
	for <disman@ietf.org>; Wed, 16 Apr 2003 06:49:25 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R194HQF>; Wed, 16 Apr 2003 12:49:23 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550159AC17@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>,
        "Disman (E-mail)"
	 <disman@ietf.org>
Subject: RE: [Disman] draft-ietf-disman-conditionmib-07.txt oddities
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 12:49:23 +0200

Although RFC-Editor can fix these... I'd rather see
these things fixed in a rev 08. Is that too much to ask?

Thanks,
Bert 

> -----Original Message-----
> From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> Sent: dinsdag 15 april 2003 23:33
> To: Disman (E-mail)
> Subject: [Disman] draft-ietf-disman-conditionmib-07.txt oddities
> 
> 
> Hi -
> 
> Some minor oddities in draft-ietf-disman-conditionmib-07.txt,
> mostly lines too long due to superfluous trailing blanks and lots
> of TAB characters (0x09).
> 
> line 5 too long (122 characters) (trailing spaces)
> line 7 too long (74 characters) (trailing spaces)
> 0x09 at line 8 position 65
> line 59 too long (73 characters) (trailing spaces)
> line 62 too long (73 characters) (trailing spaces)
> line 72 too long (73 characters) (trailing spaces)
> line 117 too long (74 characters) (trailing spaces)
> line 145 too long (73 characters) (trailing spaces)
> 0x09 at line 158 position 1
> 0x09 at line 222 position 30
> line 241 too long (78 characters)
> 0x09 at line 310 position 1
> line 316 too long (73 characters) (trailing spaces)
> 0x09 at line 318 position 1
> 0x09 at line 318 position 2
> 0x09 at line 404 position 1
> 0x09 at line 405 position 1
> 0x09 at line 406 position 1
> 0x09 at line 406 position 2
> 0x09 at line 407 position 1
> 0x09 at line 410 position 1
> 0x09 at line 410 position 2
> 0x09 at line 411 position 1
> 0x09 at line 411 position 2
> 0x09 at line 413 position 1
> 0x09 at line 413 position 2
> 0x09 at line 414 position 1
> 0x09 at line 415 position 1
> 0x09 at line 415 position 2
> 0x09 at line 416 position 1
> 0x09 at line 416 position 2
> 0x09 at line 417 position 1
> 0x09 at line 417 position 2
> 0x09 at line 418 position 1
> line 451 too long (73 characters) (trailing spaces)
> line 490 too long (73 characters) (trailing spaces)
> 0x09 at line 541 position 56
> 0x09 at line 558 position 35
> 0x09 at line 558 position 37
> 0x09 at line 570 position 35
> 0x09 at line 570 position 37
> line 651 too long (78 characters)
> line 652 too long (79 characters) (trailing spaces)
> 
> 
> I'll assume that this (along with the missing pagination) will get
> fixed by the RFC editor.
> 
> Randy
> 
> 



From mailnull@www1.ietf.org  Wed Apr 16 06:55:09 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 GAA24990
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 06:55:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3GB3hB08667
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 07:03:43 -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 h3GB3h808664
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 07:03:43 -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 GAA24937
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 06:54:38 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kbE-0000Ho-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 06:57:08 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kbE-0000Hl-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 06:57:08 -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 h3GB32808612;
	Wed, 16 Apr 2003 07:03:02 -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 h3GAuQ808311
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 06:56:26 -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 GAA24738
	for <disman@ietf.org>; Wed, 16 Apr 2003 06:47:21 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kUB-0000Gh-00
	for disman@ietf.org; Wed, 16 Apr 2003 06:49:51 -0400
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 195kUB-0000GJ-00
	for disman@ietf.org; Wed, 16 Apr 2003 06:49:51 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3GAnSx01842
	for <disman@ietf.org>; Wed, 16 Apr 2003 06:49:29 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R194HQ1>; Wed, 16 Apr 2003 12:49:23 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B1550159AC16@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>,
        "Disman (E-mail)"
	 <disman@ietf.org>
Subject: RE: [Disman] Mystery bytes in draft-ietf-disman-alarm-mib-10.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 12:49:23 +0200

Is it too much to ask to get these fixed in a rev 11?
I know it is gonna raise eyebrows.....

Thanks,
Bert 

> -----Original Message-----
> From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> Sent: dinsdag 15 april 2003 23:19
> To: Disman (E-mail)
> Subject: [Disman] Mystery bytes in draft-ietf-disman-alarm-mib-10.txt
> 
> 
> Hi -
> 
> There are a bunch of mysterious non-ascii bytes in the
> alarm MIB draft.  All the places where I'd expect an
> ASCII form feed, there's a 0xe1.  More worrisome,
> however, are 0xe1 bytes scattered throughout the
> rest of the document:
> 
> 0xe1 at line 843 position 27
> 0xe1 at line 945 position 17
> 0xe1 at line 1126 position 59
> 0xe1 at line 1126 position 60
> 0xe1 at line 1126 position 61
> 0xe1 at line 1814 position 60
> 0xe1 at line 1864 position 43
> 0xe1 at line 1864 position 45
> 0xe1 at line 2179 position 4
> 0xe1 at line 2179 position 5
> 0xe1 at line 2295 position 17
> 0xe1 at line 2305 position 51
> 0xe1 at line 2364 position 31
> 0xe1 at line 2364 position 32
> 0xe1 at line 2364 position 33
> 0xe1 at line 2371 position 17
> 0xe1 at line 2507 position 17
> 0xe1 at line 2525 position 17
> 0xe1 at line 2535 position 4
> 0xe1 at line 2536 position 4
> 0xe1 at line 2537 position 4
> 0xe1 at line 2537 position 11
> 0xe1 at line 2537 position 22
> 0xe1 at line 2538 position 4
> 0xe1 at line 2541 position 4
> 0xe1 at line 2587 position 13
> 0xe1 at line 2587 position 14
> 0xe1 at line 2588 position 17
> 0xe1 at line 2600 position 7
> 0xe1 at line 2614 position 7
> 0xe1 at line 2622 position 7
> 0xe1 at line 2656 position 55
> 0xe1 at line 2793 position 7
> 0xe1 at line 2793 position 8
> 0xe1 at line 2794 position 7
> 0xe1 at line 2794 position 8
> 0xe1 at line 2795 position 7
> 0xe1 at line 2795 position 8
> 0xe1 at line 2796 position 8
> 0xe1 at line 2838 position 6
> 
> Randy
> 
> 



From mailnull@www1.ietf.org  Wed Apr 16 08:13:09 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 IAA26659
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 08:13:09 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3GCLja14636
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 08:21:45 -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 h3GCLj814633
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 08:21:45 -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 IAA26645
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 08:12:38 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195loj-0000dE-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 08:15:09 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195loi-0000dB-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 08:15:08 -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 h3GCLF814599;
	Wed, 16 Apr 2003 08:21:15 -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 h3GCKW814552
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 08:20:32 -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 IAA26603
	for <disman@ietf.org>; Wed, 16 Apr 2003 08:11:26 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195lnY-0000cp-00
	for disman@ietf.org; Wed, 16 Apr 2003 08:13:56 -0400
Received: from zcars0m9.nortelnetworks.com ([47.129.242.157])
	by ietf-mx with esmtp (Exim 4.12)
	id 195lnY-0000ca-00
	for disman@ietf.org; Wed, 16 Apr 2003 08:13:56 -0400
Received: from zcard309.ca.nortel.com (zcard309.ca.nortel.com [47.129.242.69])
	by zcars0m9.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3GCDXn22729;
	Wed, 16 Apr 2003 08:13:33 -0400 (EDT)
Received: by zcard309.ca.nortel.com with Internet Mail Service (5.5.2653.19)
	id <GDFVHP3W>; Wed, 16 Apr 2003 08:13:33 -0400
Message-ID: <3549C09B853DD5119B540002A52CDD3407056239@zcard0ka.ca.nortel.com>
From: "Sharon Chisholm" <schishol@nortelnetworks.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        Randy Presuhn
	 <randy_presuhn@mindspring.com>,
        "Disman (E-mail)" <disman@ietf.org>
Subject: RE: [Disman] Mystery bytes in draft-ietf-disman-alarm-mib-10.txt
X-Mailer: Internet Mail Service (5.5.2653.19)
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 08:13:31 -0400

hi

My "new" computer does that for some reason. I'll spin
out an 11 today without the funny characters.

Sharon

-----Original Message-----
From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
Sent: Wednesday, April 16, 2003 6:49 AM
To: Randy Presuhn; Disman (E-mail)
Subject: RE: [Disman] Mystery bytes in
draft-ietf-disman-alarm-mib-10.txt


Is it too much to ask to get these fixed in a rev 11?
I know it is gonna raise eyebrows.....

Thanks,
Bert 

> -----Original Message-----
> From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> Sent: dinsdag 15 april 2003 23:19
> To: Disman (E-mail)
> Subject: [Disman] Mystery bytes in draft-ietf-disman-alarm-mib-10.txt
> 
> 
> Hi -
> 
> There are a bunch of mysterious non-ascii bytes in the
> alarm MIB draft.  All the places where I'd expect an
> ASCII form feed, there's a 0xe1.  More worrisome,
> however, are 0xe1 bytes scattered throughout the
> rest of the document:
> 
> 0xe1 at line 843 position 27
> 0xe1 at line 945 position 17
> 0xe1 at line 1126 position 59
> 0xe1 at line 1126 position 60
> 0xe1 at line 1126 position 61
> 0xe1 at line 1814 position 60
> 0xe1 at line 1864 position 43
> 0xe1 at line 1864 position 45
> 0xe1 at line 2179 position 4
> 0xe1 at line 2179 position 5
> 0xe1 at line 2295 position 17
> 0xe1 at line 2305 position 51
> 0xe1 at line 2364 position 31
> 0xe1 at line 2364 position 32
> 0xe1 at line 2364 position 33
> 0xe1 at line 2371 position 17
> 0xe1 at line 2507 position 17
> 0xe1 at line 2525 position 17
> 0xe1 at line 2535 position 4
> 0xe1 at line 2536 position 4
> 0xe1 at line 2537 position 4
> 0xe1 at line 2537 position 11
> 0xe1 at line 2537 position 22
> 0xe1 at line 2538 position 4
> 0xe1 at line 2541 position 4
> 0xe1 at line 2587 position 13
> 0xe1 at line 2587 position 14
> 0xe1 at line 2588 position 17
> 0xe1 at line 2600 position 7
> 0xe1 at line 2614 position 7
> 0xe1 at line 2622 position 7
> 0xe1 at line 2656 position 55
> 0xe1 at line 2793 position 7
> 0xe1 at line 2793 position 8
> 0xe1 at line 2794 position 7
> 0xe1 at line 2794 position 8
> 0xe1 at line 2795 position 7
> 0xe1 at line 2795 position 8
> 0xe1 at line 2796 position 8
> 0xe1 at line 2838 position 6
> 
> Randy
> 
> 



From mailnull@www1.ietf.org  Wed Apr 16 09:22:11 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 JAA00324
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 09:22:10 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3GDUnP20113
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 09:30:49 -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 h3GDUm820110
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 09:30:48 -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 JAA00295
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 09:21:40 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195mtX-0001TF-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 09:24:11 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195mtW-0001TC-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 09:24:10 -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 h3GDUA820079;
	Wed, 16 Apr 2003 09:30:10 -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 h3GDTa820036
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 09:29:36 -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 JAA00277
	for <disman@ietf.org>; Wed, 16 Apr 2003 09:20:27 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195msM-0001Sz-00
	for disman@ietf.org; Wed, 16 Apr 2003 09:22:58 -0400
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 195msL-0001Sw-00
	for disman@ietf.org; Wed, 16 Apr 2003 09:22:58 -0400
Received: from nj7460exch002h.wins.lucent.com (h135-17-42-35.lucent.com [135.17.42.35])
	by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3GDMYS21305
	for <disman@ietf.org>; Wed, 16 Apr 2003 09:22:35 -0400 (EDT)
Received: by nj7460exch002h.ho.lucent.com with Internet Mail Service (5.5.2653.19)
	id <JB29QYHG>; Wed, 16 Apr 2003 09:18:14 -0400
Message-ID: <E4BB443436F22D4AB9E84B06AB7C4CE0023CF4D4@nj7460exch004u.ho.lucent.com>
From: "Lam, Hing-Kam (Kam)" <hklam@lucent.com>
To: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>,
        Randy Presuhn
	 <randy_presuhn@mindspring.com>,
        "Disman (E-mail)" <disman@ietf.org>
Subject: RE: [Disman] draft-ietf-disman-conditionmib-07.txt oddities
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 08:47:29 -0400

Hi,

Thanks. I will fix these typos and upload a rev 08.

Regards,
Kam

> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Wednesday, April 16, 2003 6:49 AM
> To: Randy Presuhn; Disman (E-mail)
> Subject: RE: [Disman] draft-ietf-disman-conditionmib-07.txt oddities
> 
> 
> Although RFC-Editor can fix these... I'd rather see
> these things fixed in a rev 08. Is that too much to ask?
> 
> Thanks,
> Bert 
> 
> > -----Original Message-----
> > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> > Sent: dinsdag 15 april 2003 23:33
> > To: Disman (E-mail)
> > Subject: [Disman] draft-ietf-disman-conditionmib-07.txt oddities
> > 
> > 
> > Hi -
> > 
> > Some minor oddities in draft-ietf-disman-conditionmib-07.txt,
> > mostly lines too long due to superfluous trailing blanks and lots
> > of TAB characters (0x09).
> > 
> > line 5 too long (122 characters) (trailing spaces)
> > line 7 too long (74 characters) (trailing spaces)
> > 0x09 at line 8 position 65
> > line 59 too long (73 characters) (trailing spaces)
> > line 62 too long (73 characters) (trailing spaces)
> > line 72 too long (73 characters) (trailing spaces)
> > line 117 too long (74 characters) (trailing spaces)
> > line 145 too long (73 characters) (trailing spaces)
> > 0x09 at line 158 position 1
> > 0x09 at line 222 position 30
> > line 241 too long (78 characters)
> > 0x09 at line 310 position 1
> > line 316 too long (73 characters) (trailing spaces)
> > 0x09 at line 318 position 1
> > 0x09 at line 318 position 2
> > 0x09 at line 404 position 1
> > 0x09 at line 405 position 1
> > 0x09 at line 406 position 1
> > 0x09 at line 406 position 2
> > 0x09 at line 407 position 1
> > 0x09 at line 410 position 1
> > 0x09 at line 410 position 2
> > 0x09 at line 411 position 1
> > 0x09 at line 411 position 2
> > 0x09 at line 413 position 1
> > 0x09 at line 413 position 2
> > 0x09 at line 414 position 1
> > 0x09 at line 415 position 1
> > 0x09 at line 415 position 2
> > 0x09 at line 416 position 1
> > 0x09 at line 416 position 2
> > 0x09 at line 417 position 1
> > 0x09 at line 417 position 2
> > 0x09 at line 418 position 1
> > line 451 too long (73 characters) (trailing spaces)
> > line 490 too long (73 characters) (trailing spaces)
> > 0x09 at line 541 position 56
> > 0x09 at line 558 position 35
> > 0x09 at line 558 position 37
> > 0x09 at line 570 position 35
> > 0x09 at line 570 position 37
> > line 651 too long (78 characters)
> > line 652 too long (79 characters) (trailing spaces)
> > 
> > 
> > I'll assume that this (along with the missing pagination) will get
> > fixed by the RFC editor.
> > 
> > Randy
> > 
> > 
> 



From mailnull@www1.ietf.org  Wed Apr 16 13:05:41 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 NAA08514
	for <disman-archive@odin.ietf.org>; Wed, 16 Apr 2003 13:05:41 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3GHENP05900
	for disman-archive@odin.ietf.org; Wed, 16 Apr 2003 13:14:23 -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 h3GHEN805897
	for <disman-web-archive@optimus.ietf.org>; Wed, 16 Apr 2003 13:14:23 -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 NAA08502
	for <disman-web-archive@ietf.org>; Wed, 16 Apr 2003 13:05:11 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195qNo-0002fa-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 13:07:41 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 195qNo-0002fX-00
	for disman-web-archive@ietf.org; Wed, 16 Apr 2003 13:07:40 -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 h3GHDv805881;
	Wed, 16 Apr 2003 13:13:58 -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 h3GHCS805808
	for <disman@optimus.ietf.org>; Wed, 16 Apr 2003 13:12:28 -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 NAA08463
	for <disman@ietf.org>; Wed, 16 Apr 2003 13:03:16 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 195qLy-0002fJ-00
	for disman@ietf.org; Wed, 16 Apr 2003 13:05:46 -0400
Received: from pintail.mail.pas.earthlink.net ([207.217.120.122])
	by ietf-mx with esmtp (Exim 4.12)
	id 195qLt-0002fB-00
	for disman@ietf.org; Wed, 16 Apr 2003 13:05:45 -0400
Received: from h-68-164-29-76.snvacaid.covad.net ([68.164.29.76] helo=oemcomputer)
	by pintail.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 195qM2-0005sZ-00
	for disman@ietf.org; Wed, 16 Apr 2003 10:05:50 -0700
Message-ID: <008b01c3043a$99fb3fa0$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B1550159AC14@nl0006exch001u.nl.lucent.com>
Subject: Re: [Disman] RE: Alarm and Alarm Report Control MBs
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 16 Apr 2003 10:07:02 -0700

Hi Bert -

> From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> To: "Randy Presuhn" <randy_presuhn@mindspring.com>
> Cc: "Disman (E-mail)" <disman@ietf.org>
> Sent: Wednesday, April 16, 2003 3:49 AM
> Subject: [Disman] RE: Alarm and Alarm Report Control MBs
>

> Mmm... assuming the typographical ones are the ones
> posted by Randy... I'd rather see those fixed...
> Is it too much to ask to quickly spin another rev of
> the docs?
...

Ok.  I see the editors have already taken on the work.
As soon as the IDs appear, please consider them to
be on your plate.

Randy




From mailnull@www1.ietf.org  Fri Apr 18 07:20:40 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 HAA08694
	for <disman-archive@odin.ietf.org>; Fri, 18 Apr 2003 07:20:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3IBUDd07673
	for disman-archive@odin.ietf.org; Fri, 18 Apr 2003 07:30:13 -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 h3IBUD807670
	for <disman-web-archive@optimus.ietf.org>; Fri, 18 Apr 2003 07:30:13 -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 HAA08675
	for <disman-web-archive@ietf.org>; Fri, 18 Apr 2003 07:20:10 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Twx-0006Pi-00
	for disman-web-archive@ietf.org; Fri, 18 Apr 2003 07:22:35 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Twx-0006Pe-00
	for disman-web-archive@ietf.org; Fri, 18 Apr 2003 07:22:35 -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 h3IBTd807616;
	Fri, 18 Apr 2003 07:29:40 -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 h3IBPD807488
	for <disman@optimus.ietf.org>; Fri, 18 Apr 2003 07:25:13 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08317;
	Fri, 18 Apr 2003 07:15:10 -0400 (EDT)
Message-Id: <200304181115.HAA08317@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-alarm-mib-11.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Fri, 18 Apr 2003 07:15:10 -0400

--NextPart

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

	Title		: Alarm MIB
	Author(s)	: S. Chisholm, D. Romascanu
	Filename	: draft-ietf-disman-alarm-mib-11.txt
	Pages		: 65
	Date		: 2003-4-17
	
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 management objects used for defining
and storing alarms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-11.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-disman-alarm-mib-11.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-disman-alarm-mib-11.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:	<2003-4-17132041.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-alarm-mib-11.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-alarm-mib-11.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-4-17132041.I-D@ietf.org>

--OtherAccess--

--NextPart--




From mailnull@www1.ietf.org  Fri Apr 18 07:20:46 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 HAA08722
	for <disman-archive@odin.ietf.org>; Fri, 18 Apr 2003 07:20:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3IBUJK07706
	for disman-archive@odin.ietf.org; Fri, 18 Apr 2003 07:30:19 -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 h3IBUJ807703
	for <disman-web-archive@optimus.ietf.org>; Fri, 18 Apr 2003 07:30:19 -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 HAA08680
	for <disman-web-archive@ietf.org>; Fri, 18 Apr 2003 07:20:16 -0400 (EDT)
Received: from localhost ([127.0.0.1] helo=ietf-mx)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Tx3-0006Po-00
	for disman-web-archive@ietf.org; Fri, 18 Apr 2003 07:22:41 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 196Tx2-0006Pl-00
	for disman-web-archive@ietf.org; Fri, 18 Apr 2003 07:22:40 -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 h3IBTh807632;
	Fri, 18 Apr 2003 07:29:43 -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 h3IBPI807493
	for <disman@optimus.ietf.org>; Fri, 18 Apr 2003 07:25:18 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA08333;
	Fri, 18 Apr 2003 07:15:14 -0400 (EDT)
Message-Id: <200304181115.HAA08333@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-conditionmib-08.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Fri, 18 Apr 2003 07:15:14 -0400

--NextPart

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

	Title		: Alarm Reporting Control MIB
	Author(s)	: K. Lam, A. Huynh, D. Perkins
	Filename	: draft-ietf-disman-conditionmib-08.txt
	Pages		: 14
	Date		: 2003-4-17
	
This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in TCP/IP-based internets.
In particular, it defines objects for controlling the reporting of 
alarm conditions.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-conditionmib-08.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-disman-conditionmib-08.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-disman-conditionmib-08.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:	<2003-4-17132051.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-conditionmib-08.txt

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

Content-Type: text/plain
Content-ID:	<2003-4-17132051.I-D@ietf.org>

--OtherAccess--

--NextPart--




From mailnull@www1.ietf.org  Wed Apr 23 10:22:42 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 KAA20641
	for <disman-archive@odin.ietf.org>; Wed, 23 Apr 2003 10:22:42 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3NEYkI29283
	for disman-archive@odin.ietf.org; Wed, 23 Apr 2003 10:34:46 -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 h3NEYk829280
	for <disman-web-archive@optimus.ietf.org>; Wed, 23 Apr 2003 10:34:46 -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 KAA20612
	for <disman-web-archive@ietf.org>; Wed, 23 Apr 2003 10:22:11 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198LAm-0004Ec-00
	for disman-web-archive@ietf.org; Wed, 23 Apr 2003 10:24:32 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 198LAl-0004EY-00
	for disman-web-archive@ietf.org; Wed, 23 Apr 2003 10:24:31 -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 h3NEWa829229;
	Wed, 23 Apr 2003 10:32:36 -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 h3NEUU829108
	for <disman@optimus.ietf.org>; Wed, 23 Apr 2003 10:30:30 -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 KAA20526
	for <disman@ietf.org>; Wed, 23 Apr 2003 10:17:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198L6e-0004Co-00
	for disman@ietf.org; Wed, 23 Apr 2003 10:20:16 -0400
Received: from hoemail1.lucent.com ([192.11.226.161] helo=hoemail1.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198L6d-0004CZ-00
	for disman@ietf.org; Wed, 23 Apr 2003 10:20:15 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail1.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3NEK9K24622
	for <disman@ietf.org>; Wed, 23 Apr 2003 10:20:09 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R19XWHH>; Wed, 23 Apr 2003 16:20:08 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155016A3894@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Sharon Chisholm <schishol@nortelnetworks.com>,
        Randy Presuhn
	 <randy_presuhn@mindspring.com>,
        "Disman (E-mail)" <disman@ietf.org>
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Subject: [Disman] draft-ietf-disman-alarm-mib-11.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 23 Apr 2003 16:20:07 +0200

Mmm... is this just me?

- I see references to RFC2573 at several place. Should be RFC3413, no?
- I also still see references to other RFC257x docs. They should all be 341x, no?
- In the references section, it seems you still haev all the old references
  from the old MIB boiler plate. Is that intentional?
- Have we not discussed the (missing) IPR section earlier in the process?

Still need to do compile checks as well

Thanks,
Bert 

> -----Original Message-----
> From: Sharon Chisholm [mailto:schishol@nortelnetworks.com]
> Sent: woensdag 16 april 2003 14:14
> To: Wijnen, Bert (Bert); Randy Presuhn; Disman (E-mail)
> Subject: RE: [Disman] Mystery bytes in
> draft-ietf-disman-alarm-mib-10.txt
> 
> 
> hi
> 
> My "new" computer does that for some reason. I'll spin
> out an 11 today without the funny characters.
> 
> Sharon
> 
> -----Original Message-----
> From: Wijnen, Bert (Bert) [mailto:bwijnen@lucent.com]
> Sent: Wednesday, April 16, 2003 6:49 AM
> To: Randy Presuhn; Disman (E-mail)
> Subject: RE: [Disman] Mystery bytes in
> draft-ietf-disman-alarm-mib-10.txt
> 
> 
> Is it too much to ask to get these fixed in a rev 11?
> I know it is gonna raise eyebrows.....
> 
> Thanks,
> Bert 
> 
> > -----Original Message-----
> > From: Randy Presuhn [mailto:randy_presuhn@mindspring.com]
> > Sent: dinsdag 15 april 2003 23:19
> > To: Disman (E-mail)
> > Subject: [Disman] Mystery bytes in 
> draft-ietf-disman-alarm-mib-10.txt
> > 
> > 
> > Hi -
> > 
> > There are a bunch of mysterious non-ascii bytes in the
> > alarm MIB draft.  All the places where I'd expect an
> > ASCII form feed, there's a 0xe1.  More worrisome,
> > however, are 0xe1 bytes scattered throughout the
> > rest of the document:
> > 
> > 0xe1 at line 843 position 27
> > 0xe1 at line 945 position 17
> > 0xe1 at line 1126 position 59
> > 0xe1 at line 1126 position 60
> > 0xe1 at line 1126 position 61
> > 0xe1 at line 1814 position 60
> > 0xe1 at line 1864 position 43
> > 0xe1 at line 1864 position 45
> > 0xe1 at line 2179 position 4
> > 0xe1 at line 2179 position 5
> > 0xe1 at line 2295 position 17
> > 0xe1 at line 2305 position 51
> > 0xe1 at line 2364 position 31
> > 0xe1 at line 2364 position 32
> > 0xe1 at line 2364 position 33
> > 0xe1 at line 2371 position 17
> > 0xe1 at line 2507 position 17
> > 0xe1 at line 2525 position 17
> > 0xe1 at line 2535 position 4
> > 0xe1 at line 2536 position 4
> > 0xe1 at line 2537 position 4
> > 0xe1 at line 2537 position 11
> > 0xe1 at line 2537 position 22
> > 0xe1 at line 2538 position 4
> > 0xe1 at line 2541 position 4
> > 0xe1 at line 2587 position 13
> > 0xe1 at line 2587 position 14
> > 0xe1 at line 2588 position 17
> > 0xe1 at line 2600 position 7
> > 0xe1 at line 2614 position 7
> > 0xe1 at line 2622 position 7
> > 0xe1 at line 2656 position 55
> > 0xe1 at line 2793 position 7
> > 0xe1 at line 2793 position 8
> > 0xe1 at line 2794 position 7
> > 0xe1 at line 2794 position 8
> > 0xe1 at line 2795 position 7
> > 0xe1 at line 2795 position 8
> > 0xe1 at line 2796 position 8
> > 0xe1 at line 2838 position 6
> > 
> > Randy
> > 
> > 
> 



From mailnull@www1.ietf.org  Wed Apr 23 18:02:40 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 SAA09781
	for <disman-archive@odin.ietf.org>; Wed, 23 Apr 2003 18:02:40 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3NM4wx03047
	for disman-archive@odin.ietf.org; Wed, 23 Apr 2003 18:04:58 -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 h3NM4w803044
	for <disman-web-archive@optimus.ietf.org>; Wed, 23 Apr 2003 18:04:58 -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 SAA09769
	for <disman-web-archive@ietf.org>; Wed, 23 Apr 2003 18:02:10 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SLs-0000Ey-00
	for disman-web-archive@ietf.org; Wed, 23 Apr 2003 18:04:28 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 198SLs-0000Ev-00
	for disman-web-archive@ietf.org; Wed, 23 Apr 2003 18:04:28 -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 h3NM3V802989;
	Wed, 23 Apr 2003 18:03:32 -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 h3NM22802916
	for <disman@optimus.ietf.org>; Wed, 23 Apr 2003 18:02:02 -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 RAA09648
	for <disman@ietf.org>; Wed, 23 Apr 2003 17:59:14 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SJ2-0000Dx-00
	for disman@ietf.org; Wed, 23 Apr 2003 18:01:32 -0400
Received: from gull.mail.pas.earthlink.net ([207.217.120.84])
	by ietf-mx with esmtp (Exim 4.12)
	id 198SJ2-0000Du-00
	for disman@ietf.org; Wed, 23 Apr 2003 18:01:32 -0400
Received: from h-68-164-23-244.snvacaid.covad.net ([68.164.23.244] helo=oemcomputer)
	by gull.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 198SJR-0000PR-00
	for disman@ietf.org; Wed, 23 Apr 2003 15:01:57 -0700
Message-ID: <003a01c309e3$b28cbd60$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
References: <7D5D48D2CAA3D84C813F5B154F43B155016A3894@nl0006exch001u.nl.lucent.com>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1106
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
Subject: [Disman] Re: draft-ietf-disman-alarm-mib-11.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 23 Apr 2003 15:00:04 -0700

Hi -

> From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
> To: "Sharon Chisholm" <schishol@nortelnetworks.com>; "Randy Presuhn" <randy_presuhn@mindspring.com>; "Disman (E-mail)"
<disman@ietf.org>
> Sent: Wednesday, April 23, 2003 7:20 AM
> Subject: draft-ietf-disman-alarm-mib-11.txt
>

> Mmm... is this just me?
>
> - I see references to RFC2573 at several place. Should be RFC3413, no?

I agree this needs to be fixed.

> - I also still see references to other RFC257x docs. They should all be 341x, no?

They should be fixed.

> - In the references section, it seems you still haev all the old references
>   from the old MIB boiler plate. Is that intentional?

They should be retained only where mentioned for other reasons, as in 3413
which will show up in, e.g., the diagram in section 3.2.

> - Have we not discussed the (missing) IPR section earlier in the process?

Yes, it's been discussed before and should be there, particularly since we already
know of IPR disclosures with respect to this work's earlier versions.  However,
discussion with other IESG folks (cc-ing iesg@ietf.org) seemed to indicate that
some things, e.g. IPR material and full copyright notices, did not need to be in
the internet drafts and would be "automatically" added by the RFC editor.
Now I personally think that is not a good way to do things, but I do try to
abide by the IESG's decisions.  As a side note, the recent discussion on the IETF
list suggests that there is a major disconnect between the theory and practice
of I-Ds.  I think we should eather practice what we preach, or update our preaching
to match our practices.

> Still need to do compile checks as well

Of course.

Since I left BMC, I no longer have access to their tools.  I'm trusting the editors
to use the tools and mib-checking services available on the net.

Randy




From mailnull@www1.ietf.org  Thu Apr 24 16:46:46 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 QAA02611
	for <disman-archive@odin.ietf.org>; Thu, 24 Apr 2003 16:46:46 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3OKnWR09928
	for disman-archive@odin.ietf.org; Thu, 24 Apr 2003 16:49:32 -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 h3OKnW809925
	for <disman-web-archive@optimus.ietf.org>; Thu, 24 Apr 2003 16:49:32 -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 QAA02594
	for <disman-web-archive@ietf.org>; Thu, 24 Apr 2003 16:46:15 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198ndy-0001Am-00
	for disman-web-archive@ietf.org; Thu, 24 Apr 2003 16:48:34 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 198ndx-0001Ai-00
	for disman-web-archive@ietf.org; Thu, 24 Apr 2003 16:48:33 -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 h3OKkv809812;
	Thu, 24 Apr 2003 16:46:58 -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 h3OKjF809746
	for <disman@optimus.ietf.org>; Thu, 24 Apr 2003 16:45:15 -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 QAA02360
	for <disman@ietf.org>; Thu, 24 Apr 2003 16:41:58 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 198nZp-00018p-00
	for disman@ietf.org; Thu, 24 Apr 2003 16:44:17 -0400
Received: from hoemail2.lucent.com ([192.11.226.163] helo=hoemail2.firewall.lucent.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 198nZo-00018G-00
	for disman@ietf.org; Thu, 24 Apr 2003 16:44:16 -0400
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemail2.firewall.lucent.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id h3OKiC701379
	for <disman@ietf.org>; Thu, 24 Apr 2003 16:44:13 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19)
	id <2R19YT5L>; Thu, 24 Apr 2003 22:44:10 +0200
Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155016A3ADE@nl0006exch001u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Randy Presuhn <randy_presuhn@mindspring.com>,
        "Disman (E-mail)"
	 <disman@ietf.org>
Subject: RE: [Disman] Re: draft-ietf-disman-alarm-mib-11.txt
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Thu, 24 Apr 2003 22:44:08 +0200

W.r.t.
> > - Have we not discussed the (missing) IPR section earlier 
> >   in the process?
> 
> Yes, it's been discussed before and should be there, 
> particularly since we already know of IPR disclosures with
> respect to this work's earlier versions.

That is an extra reason to put the appropriate text into the
document. I would not assume that RFC-Editor will always know
(or get it right) if IPR has been claimed or not.

> However, discussion with other IESG folks (cc-ing iesg@ietf.org) 
> seemed to indicate that some things, e.g. IPR material and full
> copyright notices, did not need to be in the internet drafts
> and would be "automatically" added by the RFC editor.

New discussions indeed seem to be going in the direction that 
such things do not NEED to be in the I-D. That does not mean they
are forbidden to be included in the I-D. I personally think it is
still much better to have them in the document. It allows
everyone to see them during WG and IETF Last Call and be reminded
that if they do have IPR that they are expected (if they participated
in the work)/invited (if they are just reading about it) to report
it to IETF secretariat.

> Now I personally think that is not a good way to do things, 
> but I do try to abide by the IESG's decisions.  As a side note,
> the recent discussion on the IETF list suggests that there is
> a major disconnect between the theory and practice of I-Ds.
> I think we should eather practice what we preach, 
> or update our preaching to match our practices.
> 
Agreed. See my comments above though.

> > Still need to do compile checks as well
> 
> Of course.
> 
> Since I left BMC, I no longer have access to their tools.  
> I'm trusting the editors to use the tools and mib-checking
> services available on the net.
> 
My SMICng syntax checking revelaed some warnings/errors. I need to
check if they are serious or acceptable.

Bert
> Randy
> 
> 



From mailnull@www1.ietf.org  Tue Apr 29 16:14:28 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 QAA09017
	for <disman-archive@odin.ietf.org>; Tue, 29 Apr 2003 16:14:28 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3TKJed19614
	for disman-archive@odin.ietf.org; Tue, 29 Apr 2003 16:19:40 -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 h3TKJe819611
	for <disman-web-archive@optimus.ietf.org>; Tue, 29 Apr 2003 16:19:40 -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 QAA09005
	for <disman-web-archive@ietf.org>; Tue, 29 Apr 2003 16:13:57 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AbWM-0007a1-00
	for disman-web-archive@ietf.org; Tue, 29 Apr 2003 16:16:10 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AbWL-0007Zx-00
	for disman-web-archive@ietf.org; Tue, 29 Apr 2003 16:16:09 -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 h3TKBj819312;
	Tue, 29 Apr 2003 16:11:46 -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 h3TKA2819234
	for <disman@optimus.ietf.org>; Tue, 29 Apr 2003 16:10:02 -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 QAA08700
	for <disman@ietf.org>; Tue, 29 Apr 2003 16:04:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AbN2-0007Wc-00
	for disman@ietf.org; Tue, 29 Apr 2003 16:06:32 -0400
Received: from harrier.mail.pas.earthlink.net ([207.217.120.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AbN1-0007WS-00
	for disman@ietf.org; Tue, 29 Apr 2003 16:06:31 -0400
Received: from h-69-3-247-222.snvacaid.covad.net ([69.3.247.222] helo=oemcomputer)
	by harrier.mail.pas.earthlink.net with smtp (Exim 3.33 #1)
	id 19AbNX-0001sb-00
	for disman@ietf.org; Tue, 29 Apr 2003 13:07:03 -0700
Message-ID: <004901c30e8a$e4974360$7f1afea9@oemcomputer>
From: "Randy Presuhn" <randy_presuhn@mindspring.com>
To: "Disman \(E-mail\)" <disman@ietf.org>
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Subject: [Disman] Fw: Simple Times announcement
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Tue, 29 Apr 2003 13:06:59 -0700

Hi -

I believe this would be relevant and of interest to folks in the disman WG.

Randy

----- Original Message ----- 
From: "Harrington, David" <dbh@enterasys.com>
To: <wgchairs@ietf.org>
Sent: Tuesday, April 29, 2003 11:50 AM
Subject: FW: Simple Times announcement



Hi,

A  new issue of the Simple Times is available. This is the SNMP related newsletter. If you think your WG might be interested, please
distribute the announcement to your WG mailing list.

dbh
--- 
David Harrington
dbh@enterasys.com
co-chair, IETF SNMPv3 WG


--------------------------------------------------- 
Latest issue of the Simple-Times

Since there are quite some people who do not regularly visit the
Simple-Times website ( http://www.simple-times.org/), we would like to
announce that the latest version is from December 2002 and contains
articles on:
- IAB Network Management Workshop
    By Ran Atkinson, Extreme Networks
- GetBulk Worth Fixing
    By Marek Malowidzki, Military Communication Institute
- Net-SNMP: Old Wine in a New Wineskin?
    By Wes Hardaker, Network Associates, Dave Shield,
    Liverpool University
- Evaluating MIB II (RFC1213) Implementations
    By Henrik E. Holland, Remco van de Meent, Aiko Pras,
    University of Twente
- The Story Behind the SNMP Vulnerabilities
   By Tiina Havana, Ari Takanen, OUSPG

Juergen Schoenwaelder & Aiko Pras





From mailnull@www1.ietf.org  Wed Apr 30 06:33:18 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 GAA27807
	for <disman-archive@odin.ietf.org>; Wed, 30 Apr 2003 06:33:18 -0400 (EDT)
Received: (from mailnull@localhost)
	by www1.ietf.org (8.11.6/8.11.6) id h3UAcm703908
	for disman-archive@odin.ietf.org; Wed, 30 Apr 2003 06:38:48 -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 h3UAcm803904
	for <disman-web-archive@optimus.ietf.org>; Wed, 30 Apr 2003 06:38:48 -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 GAA27780
	for <disman-web-archive@ietf.org>; Wed, 30 Apr 2003 06:32:47 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 19AovU-0005qO-00
	for disman-web-archive@ietf.org; Wed, 30 Apr 2003 06:35:00 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org)
	by ietf-mx with esmtp (Exim 4.12)
	id 19AovT-0005qL-00
	for disman-web-archive@ietf.org; Wed, 30 Apr 2003 06:34:59 -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 h3UAZJ802806;
	Wed, 30 Apr 2003 06:35:19 -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 h3UAYm802771
	for <disman@optimus.ietf.org>; Wed, 30 Apr 2003 06:34:48 -0400
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27474;
	Wed, 30 Apr 2003 06:28:47 -0400 (EDT)
Message-Id: <200304301028.GAA27474@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: disman@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: [Disman] I-D ACTION:draft-ietf-disman-alarm-mib-12.txt
Sender: disman-admin@ietf.org
Errors-To: disman-admin@ietf.org
X-BeenThere: disman@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=unsubscribe>
List-Id: Distributed Management <disman.ietf.org>
List-Post: <mailto:disman@ietf.org>
List-Help: <mailto:disman-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/disman>,
	<mailto:disman-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/disman/>
Date: Wed, 30 Apr 2003 06:28:46 -0400

--NextPart

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

	Title		: Alarm MIB
	Author(s)	: S. Chisholm, D. Romascanu
	Filename	: draft-ietf-disman-alarm-mib-12.txt
	Pages		: 65
	Date		: 2003-4-29
	
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 management objects used for defining
and storing alarms.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-disman-alarm-mib-12.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-disman-alarm-mib-12.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-disman-alarm-mib-12.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:	<2003-4-29164337.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-disman-alarm-mib-12.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-disman-alarm-mib-12.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2003-4-29164337.I-D@ietf.org>

--OtherAccess--

--NextPart--




