From owner-snmpconf@seymour39.snmp.com  Tue Jun  4 10:02:33 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA29098
	for <snmpconf-archive@odin.ietf.org>; Tue, 4 Jun 2002 10:02:32 -0400 (EDT)
Received: by seymour39.snmp.com (8.9.3/m.000221) id JAA16382
	for snmpconf-outgoing; Tue, 4 Jun 2002 09:55:13 -0400 (EDT)
Message-Id: <200206041355.JAA16375@seymour39.SNMP.COM>
X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0
to: snmpconf@snmp.com
cc: Robert David <rdavid@imperialtech.com>
Subject: snmpconf SAN Disk Management and SNMP
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
Date: Tue, 04 Jun 2002 09:55:08 -0400
From: Steve Moulton <moulton@snmp.com>
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 8bit


[forwarding submission from a non-subscriber]


To: snmpconf@snmp.com
Reply-to: Robert David <rdavid@imperialtech.com>

Can anybody direct me to tools that control and configure SAN Disks via
SNMP?

Thanks,
Robert

*************************
Imperial Technology, Inc.
Cell:             310-612-8681
Phone:        310-536-0018 x124
rdavid@imperialtech.com
http://www.imperialtech.com
http://www.sanaccelerator.com
*************************




From owner-snmpconf@seymour39.snmp.com  Thu Jun 13 17:37:44 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA01262
	for <snmpconf-archive@odin.ietf.org>; Thu, 13 Jun 2002 17:37:44 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id RAA02960
	for snmpconf-outgoing; Thu, 13 Jun 2002 17:30:41 -0400 (EDT)
Message-Id: <5.1.0.14.0.20020613172300.036ab008@mail.goldwiretech.com>
X-Sender: wayne-pop@mail.goldwiretech.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 13 Jun 2002 17:25:44 -0400
To: snmpconf@snmp.com
From: "Wayne F. Tackabury" <wayne@goldwiretech.com>
Subject: snmpconf BCP, rev 9
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

Well, since the BCP last call has come and gone, we've incorporated the one 
change request posted to the list, I found a straggler format error, 
changed the date, and reissued the BCP as draft-ietf-snmpconf-bcp-09.  It's 
gone to the internet-drafts editor as such.  It will be forwarded along as 
a wg document by the chairs to the IESG.

Find below the diffs.  It should be published real soon now, and if you're 
curious, let me know and I'll forward you a formatted copy (my web site 
I've used for this purpose in the past is down right now, or rather, being 
acquired by another ISP :).

Thanks,
Wayne

$ diff draft-ietf-snmpconf-bcp-08.nroff draft-ietf-snmpconf-bcp-09.nroff
13,14c13,14
< .ds LH RFC DRAFT Expires November 2002
< .ds RH May 2002
---
 > .ds LH RFC DRAFT Expires December 2002
 > .ds RH June 2002
29,30c29,30
< draft-ietf-snmpconf-bcp-08.txt
< May 10, 2002
---
 > draft-ietf-snmpconf-bcp-09.txt
 > June 11, 2002
732,733c732,733
<     RowStatus (see Section 3.3.1) also has important relevance as a general
<     transaction control object.
---
 >     RowStatus (see Section 3.3.1) also has important relevance as a
 >     general transaction control object.
2563,2566c2563,2566
< the devices under its control.  Some
< configuration management applications may consume data from the
< managed devices that reflect configuration, operational and
< utilization state information. The GetBulkRequest-PDU is useful
---
 > the devices under its control.  Upon receipt of the notification,
 > the management application should use getBulk or getNext to
 > retrieve the configuration from the agent and store the relevant
 > contents in the management application database. The GetBulkRequest-PDU 
is use
ful


--------

Wayne F. Tackabury              Internet: wayne@goldwiretech.com
Gold Wire Technology            Phone: (781) 398-8819
411 Waverley Oaks Rd., Ste 304
Waltham, MA  02452             Cell: (617) 699-6156



From owner-snmpconf@seymour39.snmp.com  Mon Jun 17 07:39:34 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27046
	for <snmpconf-archive@lists.ietf.org>; Mon, 17 Jun 2002 07:39:34 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id HAA06781
	for snmpconf-outgoing; Mon, 17 Jun 2002 07:32:40 -0400 (EDT)
Message-Id: <200206171131.HAA26513@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: snmpconf@snmp.com
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-snmpconf-bcp-09.txt
Date: Mon, 17 Jun 2002 07:31:27 -0400
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

--NextPart

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

	Title		: Configuring Networks and Devices with SNMP
	Author(s)	: M. MacFaden, D. Partain, J. Saperia, W. Tackabury
	Filename	: draft-ietf-snmpconf-bcp-09.txt
	Pages		: 82
	Date		: 14-Jun-02
	
This document is written for readers interested in the Internet
Standard Management Framework and its protocol, the Simple Network
Management Protocol (SNMP). In particular, it offers guidance in the
effective use of SNMP for configuration management.  This information
is relevant to vendors that build network elements, management
application developers, and those that acquire and deploy this
technology in their networks.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-snmpconf-bcp-09.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-snmpconf-bcp-09.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-snmpconf-bcp-09.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:	<20020614131216.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-snmpconf-bcp-09.txt

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

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

--OtherAccess--

--NextPart--




From owner-snmpconf@seymour39.snmp.com  Wed Jun 19 07:52:32 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14561
	for <snmpconf-archive@lists.ietf.org>; Wed, 19 Jun 2002 07:52:32 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id HAA02394
	for snmpconf-outgoing; Wed, 19 Jun 2002 07:44:18 -0400 (EDT)
Date: Wed, 19 Jun 2002 13:43:41 +0200
From: David Partain <David.Partain@ericsson.com>
Subject: New I-D:  draft-ietf-snmpconf-diffpolicy-05.txt
To: snmpconf@snmp.com
Message-id: <200206191343.41565.David.Partain@ericsson.com>
MIME-version: 1.0
Content-type: text/plain; charset=iso-8859-1
Content-transfer-encoding: 8bit
User-Agent: KMail/1.4.1
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 8bit

Greetings,

With the completion of the DiffServ MIB (RFC 3289), Harrie
and I have updated the SNMPCONF part of the picture.  I have
submitted draft-ietf-snmpconf-diffpolicy-05.txt to the Internet
Drafts folks.  The blurb is sent was:

  Title    :  The Differentiated Services Configuration MIB
  Author(s):  H. Hazewinkel, D. Partain
  Filename :  draft-ietf-snmpconf-diffpolicy-05.txt
  Pages    :  27
  Date     :  June 2002

This memo describes a MIB module that provides a conceptual
layer between high-level "network-wide" policy definitions that
affect configuration of the Differentiated Services (diffserv)
subsystem and the instance-specific information that would
include such details as the parameters for all the queues
associated with each interface in a system.  This essentially
provides an interface for configuring differentiated services
at a conceptually higher layer than that of the Differentiated
Services MIB.

If you're impatient and want it before it appears
in the I-D repositories, you can pick up a copy at
http://standards.ericsson.net/partain/documents/draft-ietf-snmpconf-diffpolicy-05.txt

Cheers,

David and Harrie



From owner-snmpconf@seymour39.snmp.com  Wed Jun 19 08:34:05 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA15850
	for <snmpconf-archive@lists.ietf.org>; Wed, 19 Jun 2002 08:33:59 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id IAA02758
	for snmpconf-outgoing; Wed, 19 Jun 2002 08:29:47 -0400 (EDT)
Message-ID: <0BF8B32B723ED5119E0B0002A551748B030548EA@corp-exc3.enterasys.com>
From: "Harrington, David" <dbh@enterasys.com>
To: "snmpconf@snmp. com (E-mail)" <snmpconf@snmp.com>
Subject: snmpconf review of pm-mib
Date: Wed, 19 Jun 2002 08:26:10 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C2178C.12EA4B00"
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C2178C.12EA4B00
Content-Type: text/plain

Hi,

Steve and I have worked out the issues I had raised and either resolved them
or agreed to disagree.

There are four additional items Steve has agreed to modify, as indicated in
his mail below. 

Thank you Steve,

dbh

-----Original Message-----
From: Steve Waldbusser [mailto:waldbusser@nextbeacon.com]
Sent: Friday, June 14, 2002 12:41 PM
To: Harrington, David
Subject: Some old business



Here are the 4 things we agreed on:

Issue 17: Add text that expresses the following:
PolicyScript is a subset of C++ in which many of the
operators are overloaded to use the "var" class. However, a programmer
programming in the PolicyScript language cannot further overload
operators because the syntax to specify an overloading is not included
in the
PolicyScript syntax.

Issue 51: Add the references to document the enumerations

Issue 52: Reference disman's work in this area.

Issue 90: Fix typo where the text that says "If 'contextEngineID' is
not present, the local system will be used." should read "If
'contextEngineID' is not present, the contextEngineID of this element
will be used."


FYI: I've appended my full annotated list which I'll also send to the
list.

Steve


P.S.
1) Fixed

2) Fixed

3) Fixed

4) Fixed

5) Changed many instances throughout document

6) Reworded extensively including renaming 'accessor function' to
'function' throughout

7) Added an example

8*) Already has two examples

9*) These are all judgement calls. I think they are important to keep
    as they each clarify on a potential misunderstanding.

10) Added the clarifying text: "within the policy script"

11-12)Changed "scheduled" to "Multi-tasked" to clarify and tried to
ensure throughout the document that there weren't similar confusions
about the use of the word 'scheduled'.

13) Merged the 2 sections

14) Changed the title of section 5.1 to Terminology

15) Extensively restructured the contents of ection 5.5 based on this
input

16) Fixed

Todo: Try to put this text into the doc:
17) Answer: PolicyScript is a subset of C++ in which many of the
operators are overloaded to use the "var" class. However, a programmer
programming in the PolicyScript language cannot further overload
operators because the syntax to specify an overloading is not in the
PolicyScript syntax.

18) I don't think we'll *have to* make changes based on SMING changes
but it we find ourselves in a circumstance where we *want to* we can
make the change. For example, we could un-subset floating point if
necessary.

19*) The wording with "For example" more naturally conveys what I want
it to convey.

20*) The original wording more naturally conveys what I want
it to convey.

21) Added clarifying text

22) Question: "Does the postfix_expr rule allow ++A++, or A++++++, or
    A++--++?"

    Answer: Yes, but the underlying language doesn't permit this. This
    is where the rule comes in that says: "The PolicyScript language
    follows the syntax and semantics of ISO C++ [19], but is limited
    to that which can be expressed in the EBNF below.". This is why I
    wrote: "This is done because while EBNF doesn't fully specify
    syntactical rules (it allows constructs that are invalid) and
    doesn't specify semantic rules, it can successfully be used to
    define the subset of the language that is required for conformance
    to this specification."

23) Question: "How does the expression rule work with a comma?
    (A=0,B=1) evaluates as what? Am I allowed to specify A[A=2, B=3]?"

    Answer: The answer is always the same: Consult the C++ spec: in
    the first case the answer is 1, in the second case it is A[3].

24) Consult the C++ spec

25) Question: "'PolicyScript: statement*' is a script with no
    statements a valid script?"

    Answer: Yes. If it is a policyCondition, it returns zero.

26) Question: "Is the index specification ($*) included in the EBNF?"
    Answer: No, it is not part of the language. It is only seen inside
    of strings.

27*) The original wording more naturally conveys what I want
it to convey.

28) dbh: "6.2.1 'The policy script runtime' discusses conversion
        operators that are not part of the language. See item #17
        above."
      Answer: Yes, they are used to specify the language but are not
      part of the language itself.

29*) I tried the best that I could, but since this is a meta-language
(to define the real language) I found myself in a trap where the
next step would be to define a meta-meta-language and then a
meta-meta-meta-language to describe that and so on. At some point
you've got to assume you've got everthing down to natural language
and common sense.

30) Answer: It is the same as in C++.

31) Question: "If I understand correctly, the following will result in
    a RTE. { J="J"; K="K"; J=K } Is that correct? the intent?"

     Answer: No, it doesn't result in an RTE. I don't see anything you
     could have read that would have supported your interpretation.

32) Answer: Yes, you got it right. It is consistent with EcmaScript
and JavaScript, which is where the "var" class is inherited from.

33) Fixed

34) Answer: They wouldn't be needed in policyScript code, I just
wanted to delimit the contents of my example script (which is an octet
string to be downloaded to the agent).

35*) If we did it that way it wouldn't be much of a QuickStart guide
because you would only read it after you had already done the hard
work. Sometimes the benefit of the forward reference outweighs the
downsides. For example, in programming texts, the "Hello World"
example usually precedes the definition of printf().

36*) Same answer as 35

37*) Question: "on a related note, 'Because Policy Script is a least
common denominator' isn't quite true. It contains elements, like $*,
that are not in all the languages referenced."

  Answer: $* is not a language construct. Certain accessor functions
  treat the substring "$*" specially when seen in an oid string. It is
  just an attribute of those accessor functions. A great analogy is
  that "%d" is not a C language construct, it is treated specially by
  the printf() function when seen in the format string. If the
  printf() function was called from Pascal, it would still act the
  same way.

38) Question: "6.3.1 - can accessor functions change the value of
    arguments that are not &references?"

    Answer: No. To quote: "Arguments without the '&' character cannot be

    modified by the function."

39) Question: "6.3.1 - are all variables in the same scope? what about
    scratchpad variables?"

    Answer: This text refers to language variables (i.e. "var
maxLength;").
    Scratchpad variables are only accessable through the scratchpad
    function calls, i.e.: getScratchpad(Global, "foo", val);

40) Question: "6.3.1 - doesn't mention the addition of $*"

    Answer: As above, "$*" isn't a language feature, it is a library
    feature.

41) Fixed

42) Question: "the return value of a PolicyAction script is
    ignored. Why? why not use the return value to indicate whether the
    script ran to completion or not?"

    Answer: I considered something like this: having the return value
    indicate whether the script encountered an error. But then I
    realized that this would "cry wolf" too often because often
    programmers exit without paying attention to return codes or just
    simply exit by hitting the last line of code.

    Instead, you can signal errors explicitely with the signalError()
    function and a management station can find policies with errors by
    checking the pmTrackingTable.

43) Question: "if the return value is ignored, why set it to zero as
    the result of an RTE or indication of a fail()?"

    Answer: This is only interesting for policyCondition scripts where
    the return value makes a difference. This rule makes sure that
    upon an error, the condition does NOT select an element. This is
    designed so that it fails gracefully.

44) Each of these forward references has been addressed.

45) Question: "section 7 - if SMING changes addressing to use
    non-OIDs, will snmpconf be able to be updated in a backwards
    compatible way?"

    Answer: The PM MIB will be fine and the language will be
    fine. Certain accessor functions would not work and would be
    augmented with new ones that would work.

46*) The original wording more naturally conveys what I want
it to convey.

47) Fixed

48*) The original wording more naturally conveys what I want
it to convey.

49) See the answer for #38

50) Fixed

Todo: put these in
51*) I didn't think this really added any value and it seemed a bit
distracting. Will anyone really be confused? I'll add it if it's
important to you.

Todo: give disman credit and blame for this so people "know why this
is done this way":
52) Section 9.1.1 provided further detail

53) Question: "'the agent' - must it be an agent? does it apply to
    mid-level managers as well?"

    Answer: The entity that implements this MIB must be an agent. It may
also
    be a mid-level manager.

54) Fixed

55*) I think this is too much off-topic detail

56) Question: "9.1.2 enum_decimal - are enums required to start with a
    letter?  How would ToInteger( 3Com(12) ) be evaluated? is the
    processing clearly defined to prevent mis-interpretation?"

    Answer: enums are only processed inside of strings. So your
    example looks like a C++ syntax error. Your example should be
    phrased as ToInteger( "3Com(12)" ) and you can probably see
    clearly now that it doesn't matter what the string begins with.

57) Question: "can unsigned64 types with the high bit set be converted
    reliably using ToInteger()?"

    Answer: Yes.

58) Question: "'unencoded' 'encoded' - what does this mean? not ASN.1
    encoded?"

    Answer: It means not encoded as an OID or a decimal number (to
    distinguish it from oids and integer processing).

59) Question: "subid: '0' | decimal_constant - why not use digit?"

    Answer: To avoid "00000" or "00001" etc.

60) Question: "never used in these encodings over the wire" - can we
replace
    "these encodings" with "the scripts"?

    Answer: It is more accurate to state this specifically for these
    accessor functions. For example, another accessor function could
    be defined which *would* accept and translate such descriptors.

61) Fixed: Changed the terminology here and in 49 other places.

62*) dbh: searchColumn - POSIX 1003.2 isn't mentioned in the References
    section

Answeer: I don't have the information that would provide a complete
reference. In the meantime, there is no ambiguity.

63) Question: searchColumn() - "or returns an error without finding a
match" -
    what are the error conditions? Since a zero means both endofView
    and error, how can a programmer determine that they have reached
    the end of the table without error?

    Answer: You can't. You'd have to do it "by hand".

64) Question: Can this script be written as
    while(searchColumn("ifType", oid, ethernet(6), 0)) ?

    Answer: Unfortunately, no. That works for the other SNMP functions
    (the ones that follow the input rules for "Form of SNMP Values")
    when the type field is set to integer yet the string is in the
    form of "blah paren number paren". In this case there's no input
    type because searchcolumn will work with any data type
    returned. That's why it transforms returned values into strings
    and then compares it to this 'pattern' argument.

    (BTW, if it worked, the proper syntax would have had "ethernet(6)"
    in a string).

65) Reworded.

66*) See #53.

67*) The original wording more naturally conveys what I want
it to convey.

68) Reworded.

69) [This is a clarification request and 2 questions. The
clarification request resulting in a rewording].

Question: counterRate() - somewhat ambiguous about how many, and which,
timestamped values must be kept. The paragraph starting "counterRate
retrieves" says it keeps "values" so it can calculate over a longer
period than since the last invocation. The paragraph that starts "The
implementation will need" says it must retain one value older than
minInterval seconds. So, if I have a minInterval of 5 seconds, do I
need to keep the last read (less than 5 seconds ago) and one more
read?

Answer: Yes.

Question: What are the interoperability issues if I set two boxes to
have
minIntervals of 5 seconds, and vendor A keeps the most current and the
most current + 5, but vendor B keeps the most current and the most
current + 15 (discarding the current+5 and current+10 samples?).  70)
is there a way to tell how many samples have been kept?

Answer: The use of the phrase "old values" meant that it would only
delete
"from the end" (i.e. values that had expired). I've reworded this to
make the point more strongly.

70) Question: is there a way to tell how many samples have been kept?
    Answer: No

71) Question: is there a way to access the samples? their timestamps?
    Answer: No to both questions.

72*) I don't see any better way to do this.

73) Question: "Otherwise, this delta will be dividied by the number of
seconds
    elapsed between the two retrievals ..." assumes there are two
    retrieveals. What if an implementation keeps more than two? how
    will the value be calculated?

    Answer: The text specifically refers to two particular retrievals
amongst
    the many that may be stored:
       1) The most recent one (now); and,
       2) The newest retrieval that is at least minInterval old.

74) Fixed. (Rounded down)

75) Fixed. (Formatted into bullets).

76*) It is done this way simply for symmetry.

77*) I think this is an important clarification. I don't want to
delete the clarification.

78) Question: newPDU() - can a PDU that is received in a trap be read
using the
    functions described here?

    Answer: No

79) Question: 9.1.4.4 is snmpSend() synchronous or asynchronous? This is

          important to know for off-box queries.

    Answer: It is synchronous

80*) I don't think it's clear one way or another (it's really a style
issue). But this is a big thing to change at this time without a clear
mandate (things changed now won't receive the same level of review and
concensus as things changed some time ago).

81) Question: 9.2 Are the HC datatypes supported? What does
counterRate() return for a 64-bit counter delta?

Answer: Yes, they are supported. The native integer variables have 64
bits of precision and counterRate has an option for doing 32 bit or 64
bit counters as appropriate.

82) Question: "local" errors - when acting as a MLM, are these local
errors or
remote errors? Do we have remote errors?

Answer: "Local Errors" refers to errors encountered in the API that
aren't present in the protocol. For example, a timeout error.
The distinction between local and remote is the same whether the
transactions stay on the box or go over the wire.

83*) dbh: Constants for SnmpMessageProcessingModel and SnmpSecurityModel
-
    if additional security models are defined, can they be supported
    in snmpconf? A reference to the official definition of these
    values would be better than "hard-coding" the list here. Ditto for
    SNMP operation types, SNMP errors, and other constants. It's ok to
    include the constants here, but there should be a disclaimer that
    the official list is found in [wherever].

Answer: But these are the values that a script can depend on to be
pre-defined. There are no other values defined as constants. If other
security models are defined, the function library would need to be
updated to support them.

84) Fixed

85) Fixed

86*) These are only used internally, not over the wire. They are
defined this way on purpose.

87) Done: reordered all the sections in this chapter.

88*) The argument isn't compelling enough to warrant changing all 10
instances of this phrase.

89) Fixed

90) dbh: elementContext() is provided, and elementAddress() is provided,

but elementContextEngineID() is missing, which is especially notable
given that roleMatch() uses contextEngineID rather than the address.

Answer: You don't need to do this. roleMatch() uses the element,
context, and contextEngineID of "this element" by default. So
roleMatch(string, element, context, elementContextEngineID())
is the same as
roleMatch(string, element, context)

Todo:
But, I do see a bug where the text that says "If 'contextEngineID' is
not present, the local system will be used." should read "If
'contextEngineID' is not present, the contextEngineID of this element
will be used."

91) dbh: roleMatch() ues contextEngineID and doesn't permit using the
address, but nonLocalArgs favors the address over contextEngineID (the
contextEngineID in nonLocalArgs can be not-present, and commands will
be sent to the address specified, which is in keeping with SNMPv3
engineID discovery).

Answer: This is by design. NonLocalArgs is used in the SNMP
library functions as it is used to specify transport information with
which to send SNMP packets (possibly through proxies). RoleMatch()
refers to a local database of role information for local and non-local
systems. The authoritative identifier for a non-local system is the
contextEngineID, regardless of any of the transport addresses it may
be reached through (or next-hop addresses when going through a proxy).

92) Your comment initiated a major rewrite of this section.

93) Done

94) Resolved

95) Fixed.

96) Clarified

97) Question: "Contents of the scratchpad are erased on reboot." -
    doesn't this contradict the purpose of storageType?

    Answer: No. Scripts need to be able to bootstrap themselves when
    they are first installed or when an element appears. This is just
    another one of those times. Think of it as all the elements
    disappearing when the box goes down and re-appearing when it
    starts up again.

98) Fixed

99) Question: I am unclear on how to specify a modifiable parameter in
    a function call - is it the C-style (&val), where the address of
    the variable is provided, or the C++-style (val), where the
    reference is defined in the prototype?

    Answer: It is the C++ style. In the beginning of section 9 you can
    read: "In the function prototype, if the '&' character precedes
    the identifier for an argument, that argument may be modified by
    the function (e.g., "integer &result, ...)"). Arguments without
    the '&' character cannot be modified by the function.  In a
    script, modifiable arguments don't need to be preceeded by a '&'."

100) Question: "Is it an RTE if I specify getScratchpad(Global,"foo",
     "55")? The string "55" is associated with a memory location, just
     as val is, but the memory location for "55" may be read-only
     memory. Writing to it might cause a core dump. Alternately, a
     manifest constant string might be modified, making the rest of
     hte program malfunction."

     Answer: Yes, it is an RTE. I added the following text to the
     beginning of Section 9 to clarify:  "It is a RTE if a constant is
     passed to a modifiable function argument (regardless of whether
     the function actually writes to the argument)."

101) Question: 9.3.9 defines constants for use with the scratchpad
     functions. Shouldn't these constants be defined with the other
     constants?

     Answer: I think it's more modular this way and thus more
     readable. The other constants are many pages away.

102) Fixed

103) Fixed.

     Question: Are all the bits in pmTrackingPEInfo cleared at the
     start of each execution?

     Answer: The bits related to conditions(actions) are cleared at the
     beginning of execution of the condition(action). This is clearly
     spelled out in the pmTrackingPEInfo MIB object.

     Question:     How do I know whether conditionUserSignal or
     actionUserSignal will be set?

     Answer: The pmTrackingPEInfo MIB object spells out clear rules.

     Question: Assuming it
     gets set depending on whether a condition or action is being
     evaluated, does the conditionUserSignal get cleared when the
     action is evaluated, or when the next condition is evaluated?

     Answer: (Your initial assumption is correct). It is only cleared
     when the next condition is evaluated.

104*) dbh: defer() - In the description, the order of discussion is
default
     behavior, defer(1), then defer(0). is the default behavior and
     defer(0) equivalent? if so, they should be discussed together.

     Answer: I tried writing it that way and it just looked more
awkward.

105) Question: defer() - the discussion that preceds the prototype
     talks about gold is appropriate but isn't possible. It doesn't
     say anything about hitting a RTE. But the description in the
     prototype is dependent on hitting an RTE. Is it always true, and
     a restriction that any future library developers must be aware
     of, that an RTE MUST be triggered if it isn't possible to do
     something?

     Answer: No, that isn't the case. If you've been selected as the
     highest precedence policy but then discover you can't fulfill
     your responsibility, you can call fail(1, ...). Defer is used to
     provide instructions in the event that you accidently hit an RTE
     (say, divide by zero). In such an even, you can't choose to call
     fail() because you're dead. Think of defer as the Last Will and
     Testament for a policy :-)

106) Question: Can a script writer choose to voluntarily, as part of
     their logic, fail() and defer()? Is that an RTE, or just
     returning a false condition?

     Answer: You can fail(1, ...) which has the side effect of
     deferring as you die. A script's execution halts when it hits
     fail() so in fail(); defer();, defer() never runs.

     Fail and defer are functions that only provide value in an action
     script, which is only run of the corresponding condition has
     already returned true.


107) Fixed.

108) Fixed.

109) Rewritten.

[pg 4, sec 3, Overview]
There were so many good slides presented in the WG describing
the layering from independent to dependent data abstractions,
but none of that made it into the draft. (The entire overview
is less than a page.)

There is no attempt to describe how this draft addresses any
of the motherhood & apple pie goals listed in para 2.

There is no attempt (anywhere in the draft) to describe the
overall system that is defined within the draft. The draft
reads like a parts list without instructions on how to put
all the parts together.  Some of the missing details:
 - a diagram showing the components of the PM system
 - a diagram showing how the PM system fits within the overall
   managed device
 - a diagram showing how the PM system fits within the overall
   NM system as a mid-level manager
 - explanations of all the components, such as:
    - element discovery
    - element registration
    - capabilities registration
    - roles
    - policies
    - policy groups
    - policy selection
    - policy distribution
    - policy organization
    - policy conditions
    - policy actions
    - policy scheduling
    - policy script execution environment
    - element filtering
    - accessor library
    - policy validation
    - schedule group
 - how the components relate to each other
 - how the entire system fits within the SNMP Architecture

[pg 5, sec 4, Arch.]
This section would make more sense if the system was explained
first. This section doesn't really describe an architecture,
but rather the notion of policy based management (again).
It doesn't really explain the system that implementors are
supposed to create, and how operators are supposed to use it.

[pg 6, para 1, sec 4, Arch.]
The description of "this element" is confusing because there
has been no detailed explanation (and won't be) of the runtime
environment.

[pg 8, para 2, sec 5.1, Terminology]
This section should be moved to a general terms section either before
or after the overview.  The details about RTE should stay in section 5.
Some terms that need introduction:
    - element type
    - element
    - "this" element
    - system element 0.0
    - role
    - policy
    - policy group
    - policy condition
    - policy action
    - accessor function
    - schedule group
    - precedence group

[pg 8, para 4, sec 5.2, Element Discovery]
"as 1 element" -> "as one element". [done]

In the last sentence, it's not clear how this applies to
the runtime environment.  It would help to explain the runtime
environment at a high-level (iterative engine, and how it
operates on elements) somewhere in section 5.

[pg 9, sec 5.2, Element Discovery]
It isn't clear why the details of the element registration
MIB are explained, because the rest of the discussion is
about element discovery. How does NMS registration relate
to discovery?  It is confusing to mix MIB object
details in with this high level discussion.  (They should
be in a separate MIB overview section.) In general, the
MIB objects are discussed in detail before the MIB is introduced.

[pg 10, sec 5.2,1 Implementation Notes]
This section should be moved to later in the document.
because the MIB has not been introduced, and all the
implementation notes should be grouped together.

[pg 11, para 2, sec 5.3 Element Filtering]
This first paragraph contains MIB details about policy
scheduling, and should go in a section for that (added
before this one). This concept is called 'policyCondition'
everywhere but this section.

[pg 11, sec 5.3,1 Implementation Notes]
"It is an implementation-dependent matter as to how policy
conditions are scheduled."  This is pretty much the entire
description of the script invocation and scheduling details.
I think it will be difficult for script developers to port
scripts across PM implementations with this approach. There
are also many constraints placed on scheduling throughout
the document, so this statement is misleading.

[pg 11, sec 5.4 Policy Enforcement]
This concept is called 'policyAction' everywhere but this section.

[pg 12, sec 5.4,1 Implementation Notes]
I think it will be difficult for script developers to port
scripts across PM implementations without specifying scheduling
algorithms, scheduling conflict resolution, etc.)

It is not clear what by the 2nd setence "each ... pair
its own process ... run simultaneously."

The execution control flow should be explained (from engine
to condition script to action script within a specific iteration
sequence, based on registered elements, configured latencies,
system events, etc.)

[pg 12, sec 5.5, Definitions]
These terms should be moved to a general Terms section.

term "precedence policy" should be explained in the Terms section

[pg 22-23, sec. 6.3, QuickStart Guide]

The other examples of finding the gold interface or
killing all application processes that have run for > 5 min
are not very compelling.  IMO. the document doesn't effectively
demonstrate that the PM MIB can be used to perform the
initial configuration of a real managed device, such as a router.

Some code examples for readVar would be helpful.

[pg 47, sec 9.1.4, general]
These functions are very important and it would help to have
a meaningful example that used all of them.

[pg 50, sec 9.3.1, roleMatch]
Meaningful examples of this accessor function would help.

[pg 56. sec 9.3.11, defer]
The concept of precedence groups should be explained
way before here, in an accessor function description.
The whole concept is fuzzy, potentially complicated,
and never explained or shown in examples. How is
the system configured to utilize "runner-up" policies?
The mechanism should be better explained.

[pg 58. sec 9.4.1, regexp]
Example code showing meaningful usage of the match
parameter would be helpful.

[pg 58-59. sec 9.4.2, regexpReplace]
Example code would be helpful.

Are there restrictions on the value of 'replacement'?

Does an RTE occur if the string replacement causes
the 'src' string to overflow?

[pg 62. sec 9.4.9, parseIndex]
An example for each variant of the function would be helpful.

It would help in the example to show what OID fragment values
are actually stored in each var = parseIndex() call.
The example is misleading because the string ipForwardIfIndex
is not actually allowed.

[pg 64. sec 9.4.14-16, chr, ord, substr]
Meaningful code examples of these functions would help.

[pg 65. sec 9.5, Library Accessor Functions]
The full function prototypes for these POSIX functions
should be provided.

No mention of the sprintf format codes is made.

How does each and every format code variant map to a data type
in PolicyScript?

Is an RTE generated if the number of parameters passed
to sprintf does not match the format string?

Is an RTE generated if the type of a parameter passed
to sprintf does not match the format string type?

[pg 65. sec 10, Schedule Table]
There is no overall explanation of time-based scheduling.
This should be in the section on the runtime environment.
This section is out of place here.

The term 'schedule group' is used here but not defined anywhere.

The discussion of the pmScheduleTable should be in
an overview of the MIB.

[pg 68. sec 11, Definitions]
There is no overview section to introduce the MIB groups
as is customary in standard MIBs.  The MIB is harder
to read because of this omission.

A diagram showing the different groups in the MIB
and explanations of each group and its relationship
to the other groups (if relevant) would be helpful.

[pg 72, sec 11, pmPolicyPrecedenceGroup]
There are no examples of this potentially complicated
mechanism in the document. Many runtime environment
features (like this one) are explained and defined
via MIB objects, which makes them hard to figure out.

[pg 76, sec 11, pmPolicyConditionMaxLatency]
   "... may wish to re-run .. change to the role strings"
This is another execution environment tidbit scattered
in the document.  All of these should be collected
and placed outside the MIB description clauses.

[pg 77, sec 11, pmPolicyMaxIterations]
This object is allowed to change at any time, which is
difficult to implement.  If an NMS lowers this object
while a script is running in a while loop, will the
agent instantly detect the change? On the next policy
task invocation?  Within some max latency?

[pg 77-78, sec 11, pmPolicyTable gauges]
It's not clear what the underlying execution model is,
so it's also unclear what starts the counting and
stops the counting for a particular gauge value.

[pg 80, sec 11, Policy Code Table]
This long ASN.1 comment should be in a MIB overview
section instead.

[pg 83, sec 11, Element Type Registration Table]
This long ASN.1 comment should be in a MIB overview
section instead.

What happens to the running script if an entry is removed
from this table. What does the runtime do if the current
loop is the elementType removed? Is there an RTE error
code for this condition?

What happens to the running script if an entry is added
to this table that changes an element filter evaluation?

The document never actually defines what constitutes
an element type, so it's hard to tell how the agent
is supposed to auto-populate this table.

[pg 85, sec 11, pmElementTypeRegOIDPrefix]
The "0.0" system entry is not mandatory (none are),
yet there are accessor functions (like roleMatch)
that need this entry. Is this entry required or
do those accessor functions cause an RTE if they
reference the non-existent 0.0 entry?

[pg 86-87, sec 11, Role Table]
This long ASN.1 comment should be in a MIB overview
section instead.

[pg 88, sec 11, pmRoleElement]
Does this re-indexing rule apply if the element is
in on a different engine? Is there a max latency
for discovering re-indexing?  This is a tall order,
considering other text in the document says the
agent doesn't really know (and doesn't enforce)
the structure of the OID instance in any other cases.

[pg 105-106, sec 11, pmTrackingEPStatus]
What happens if this is set to forceOff while a policy
is running? Does the script complete if it was just
forced off? Does it end with an RTE?

Do other MIB status objects change elsewhere
in the pmPolicyTable when this is set to forceOff?

[pg 112, sec 14, Acknowledgements]
No mention whatsoever, or reference, is given for the
Scheduling MIB, even though several hundred lines of
text were lifted from that MIB.  The cut-and-paste
is bad enough!

[pg 116, sec 17, Intellectual Property]
I think different text is supposed to go here if the WG
knows of any claims of patented IP pertaining to this work,
and I believe BMC Software is making such a claim.

[pg 118, ToC]
This should go in the front of the document.



------_=_NextPart_001_01C2178C.12EA4B00
Content-Type: text/html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=US-ASCII">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2655.35">
<TITLE>review of pm-mib</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=2>Hi,</FONT>
</P>

<P><FONT SIZE=2>Steve and I have worked out the issues I had raised and either resolved them or agreed to disagree.</FONT>
</P>

<P><FONT SIZE=2>There are four additional items Steve has agreed to modify, as indicated in his mail below. </FONT>
</P>

<P><FONT SIZE=2>Thank you Steve,</FONT>
</P>

<P><FONT SIZE=2>dbh</FONT>
</P>

<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Steve Waldbusser [<A HREF="mailto:waldbusser@nextbeacon.com">mailto:waldbusser@nextbeacon.com</A>]</FONT>
<BR><FONT SIZE=2>Sent: Friday, June 14, 2002 12:41 PM</FONT>
<BR><FONT SIZE=2>To: Harrington, David</FONT>
<BR><FONT SIZE=2>Subject: Some old business</FONT>
</P>
<BR>
<BR>

<P><FONT SIZE=2>Here are the 4 things we agreed on:</FONT>
</P>

<P><FONT SIZE=2>Issue 17: Add text that expresses the following:</FONT>
<BR><FONT SIZE=2>PolicyScript is a subset of C++ in which many of the</FONT>
<BR><FONT SIZE=2>operators are overloaded to use the &quot;var&quot; class. However, a programmer</FONT>
<BR><FONT SIZE=2>programming in the PolicyScript language cannot further overload</FONT>
<BR><FONT SIZE=2>operators because the syntax to specify an overloading is not included</FONT>
<BR><FONT SIZE=2>in the</FONT>
<BR><FONT SIZE=2>PolicyScript syntax.</FONT>
</P>

<P><FONT SIZE=2>Issue 51: Add the references to document the enumerations</FONT>
</P>

<P><FONT SIZE=2>Issue 52: Reference disman's work in this area.</FONT>
</P>

<P><FONT SIZE=2>Issue 90: Fix typo where the text that says &quot;If 'contextEngineID' is</FONT>
<BR><FONT SIZE=2>not present, the local system will be used.&quot; should read &quot;If</FONT>
<BR><FONT SIZE=2>'contextEngineID' is not present, the contextEngineID of this element</FONT>
<BR><FONT SIZE=2>will be used.&quot;</FONT>
</P>
<BR>

<P><FONT SIZE=2>FYI: I've appended my full annotated list which I'll also send to the</FONT>
<BR><FONT SIZE=2>list.</FONT>
</P>

<P><FONT SIZE=2>Steve</FONT>
</P>
<BR>

<P><FONT SIZE=2>P.S.</FONT>
<BR><FONT SIZE=2>1) Fixed</FONT>
</P>

<P><FONT SIZE=2>2) Fixed</FONT>
</P>

<P><FONT SIZE=2>3) Fixed</FONT>
</P>

<P><FONT SIZE=2>4) Fixed</FONT>
</P>

<P><FONT SIZE=2>5) Changed many instances throughout document</FONT>
</P>

<P><FONT SIZE=2>6) Reworded extensively including renaming 'accessor function' to</FONT>
<BR><FONT SIZE=2>'function' throughout</FONT>
</P>

<P><FONT SIZE=2>7) Added an example</FONT>
</P>

<P><FONT SIZE=2>8*) Already has two examples</FONT>
</P>

<P><FONT SIZE=2>9*) These are all judgement calls. I think they are important to keep</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; as they each clarify on a potential misunderstanding.</FONT>
</P>

<P><FONT SIZE=2>10) Added the clarifying text: &quot;within the policy script&quot;</FONT>
</P>

<P><FONT SIZE=2>11-12)Changed &quot;scheduled&quot; to &quot;Multi-tasked&quot; to clarify and tried to</FONT>
<BR><FONT SIZE=2>ensure throughout the document that there weren't similar confusions</FONT>
<BR><FONT SIZE=2>about the use of the word 'scheduled'.</FONT>
</P>

<P><FONT SIZE=2>13) Merged the 2 sections</FONT>
</P>

<P><FONT SIZE=2>14) Changed the title of section 5.1 to Terminology</FONT>
</P>

<P><FONT SIZE=2>15) Extensively restructured the contents of ection 5.5 based on this</FONT>
<BR><FONT SIZE=2>input</FONT>
</P>

<P><FONT SIZE=2>16) Fixed</FONT>
</P>

<P><FONT SIZE=2>Todo: Try to put this text into the doc:</FONT>
<BR><FONT SIZE=2>17) Answer: PolicyScript is a subset of C++ in which many of the</FONT>
<BR><FONT SIZE=2>operators are overloaded to use the &quot;var&quot; class. However, a programmer</FONT>
<BR><FONT SIZE=2>programming in the PolicyScript language cannot further overload</FONT>
<BR><FONT SIZE=2>operators because the syntax to specify an overloading is not in the</FONT>
<BR><FONT SIZE=2>PolicyScript syntax.</FONT>
</P>

<P><FONT SIZE=2>18) I don't think we'll *have to* make changes based on SMING changes</FONT>
<BR><FONT SIZE=2>but it we find ourselves in a circumstance where we *want to* we can</FONT>
<BR><FONT SIZE=2>make the change. For example, we could un-subset floating point if</FONT>
<BR><FONT SIZE=2>necessary.</FONT>
</P>

<P><FONT SIZE=2>19*) The wording with &quot;For example&quot; more naturally conveys what I want</FONT>
<BR><FONT SIZE=2>it to convey.</FONT>
</P>

<P><FONT SIZE=2>20*) The original wording more naturally conveys what I want</FONT>
<BR><FONT SIZE=2>it to convey.</FONT>
</P>

<P><FONT SIZE=2>21) Added clarifying text</FONT>
</P>

<P><FONT SIZE=2>22) Question: &quot;Does the postfix_expr rule allow ++A++, or A++++++, or</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; A++--++?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: Yes, but the underlying language doesn't permit this. This</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; is where the rule comes in that says: &quot;The PolicyScript language</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; follows the syntax and semantics of ISO C++ [19], but is limited</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; to that which can be expressed in the EBNF below.&quot;. This is why I</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; wrote: &quot;This is done because while EBNF doesn't fully specify</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; syntactical rules (it allows constructs that are invalid) and</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; doesn't specify semantic rules, it can successfully be used to</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; define the subset of the language that is required for conformance</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; to this specification.&quot;</FONT>
</P>

<P><FONT SIZE=2>23) Question: &quot;How does the expression rule work with a comma?</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; (A=0,B=1) evaluates as what? Am I allowed to specify A[A=2, B=3]?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: The answer is always the same: Consult the C++ spec: in</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the first case the answer is 1, in the second case it is A[3].</FONT>
</P>

<P><FONT SIZE=2>24) Consult the C++ spec</FONT>
</P>

<P><FONT SIZE=2>25) Question: &quot;'PolicyScript: statement*' is a script with no</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; statements a valid script?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: Yes. If it is a policyCondition, it returns zero.</FONT>
</P>

<P><FONT SIZE=2>26) Question: &quot;Is the index specification ($*) included in the EBNF?&quot;</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: No, it is not part of the language. It is only seen inside</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; of strings.</FONT>
</P>

<P><FONT SIZE=2>27*) The original wording more naturally conveys what I want</FONT>
<BR><FONT SIZE=2>it to convey.</FONT>
</P>

<P><FONT SIZE=2>28) dbh: &quot;6.2.1 'The policy script runtime' discusses conversion</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; operators that are not part of the language. See item #17</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; above.&quot;</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Answer: Yes, they are used to specify the language but are not</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; part of the language itself.</FONT>
</P>

<P><FONT SIZE=2>29*) I tried the best that I could, but since this is a meta-language</FONT>
<BR><FONT SIZE=2>(to define the real language) I found myself in a trap where the</FONT>
<BR><FONT SIZE=2>next step would be to define a meta-meta-language and then a</FONT>
<BR><FONT SIZE=2>meta-meta-meta-language to describe that and so on. At some point</FONT>
<BR><FONT SIZE=2>you've got to assume you've got everthing down to natural language</FONT>
<BR><FONT SIZE=2>and common sense.</FONT>
</P>

<P><FONT SIZE=2>30) Answer: It is the same as in C++.</FONT>
</P>

<P><FONT SIZE=2>31) Question: &quot;If I understand correctly, the following will result in</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; a RTE. { J=&quot;J&quot;; K=&quot;K&quot;; J=K } Is that correct? the intent?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: No, it doesn't result in an RTE. I don't see anything you</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; could have read that would have supported your interpretation.</FONT>
</P>

<P><FONT SIZE=2>32) Answer: Yes, you got it right. It is consistent with EcmaScript</FONT>
<BR><FONT SIZE=2>and JavaScript, which is where the &quot;var&quot; class is inherited from.</FONT>
</P>

<P><FONT SIZE=2>33) Fixed</FONT>
</P>

<P><FONT SIZE=2>34) Answer: They wouldn't be needed in policyScript code, I just</FONT>
<BR><FONT SIZE=2>wanted to delimit the contents of my example script (which is an octet</FONT>
<BR><FONT SIZE=2>string to be downloaded to the agent).</FONT>
</P>

<P><FONT SIZE=2>35*) If we did it that way it wouldn't be much of a QuickStart guide</FONT>
<BR><FONT SIZE=2>because you would only read it after you had already done the hard</FONT>
<BR><FONT SIZE=2>work. Sometimes the benefit of the forward reference outweighs the</FONT>
<BR><FONT SIZE=2>downsides. For example, in programming texts, the &quot;Hello World&quot;</FONT>
<BR><FONT SIZE=2>example usually precedes the definition of printf().</FONT>
</P>

<P><FONT SIZE=2>36*) Same answer as 35</FONT>
</P>

<P><FONT SIZE=2>37*) Question: &quot;on a related note, 'Because Policy Script is a least</FONT>
<BR><FONT SIZE=2>common denominator' isn't quite true. It contains elements, like $*,</FONT>
<BR><FONT SIZE=2>that are not in all the languages referenced.&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp; Answer: $* is not a language construct. Certain accessor functions</FONT>
<BR><FONT SIZE=2>&nbsp; treat the substring &quot;$*&quot; specially when seen in an oid string. It is</FONT>
<BR><FONT SIZE=2>&nbsp; just an attribute of those accessor functions. A great analogy is</FONT>
<BR><FONT SIZE=2>&nbsp; that &quot;%d&quot; is not a C language construct, it is treated specially by</FONT>
<BR><FONT SIZE=2>&nbsp; the printf() function when seen in the format string. If the</FONT>
<BR><FONT SIZE=2>&nbsp; printf() function was called from Pascal, it would still act the</FONT>
<BR><FONT SIZE=2>&nbsp; same way.</FONT>
</P>

<P><FONT SIZE=2>38) Question: &quot;6.3.1 - can accessor functions change the value of</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; arguments that are not &amp;references?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: No. To quote: &quot;Arguments without the '&amp;' character cannot be</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; modified by the function.&quot;</FONT>
</P>

<P><FONT SIZE=2>39) Question: &quot;6.3.1 - are all variables in the same scope? what about</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; scratchpad variables?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: This text refers to language variables (i.e. &quot;var</FONT>
<BR><FONT SIZE=2>maxLength;&quot;).</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Scratchpad variables are only accessable through the scratchpad</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; function calls, i.e.: getScratchpad(Global, &quot;foo&quot;, val);</FONT>
</P>

<P><FONT SIZE=2>40) Question: &quot;6.3.1 - doesn't mention the addition of $*&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: As above, &quot;$*&quot; isn't a language feature, it is a library</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; feature.</FONT>
</P>

<P><FONT SIZE=2>41) Fixed</FONT>
</P>

<P><FONT SIZE=2>42) Question: &quot;the return value of a PolicyAction script is</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; ignored. Why? why not use the return value to indicate whether the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; script ran to completion or not?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: I considered something like this: having the return value</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; indicate whether the script encountered an error. But then I</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; realized that this would &quot;cry wolf&quot; too often because often</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; programmers exit without paying attention to return codes or just</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; simply exit by hitting the last line of code.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Instead, you can signal errors explicitely with the signalError()</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; function and a management station can find policies with errors by</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; checking the pmTrackingTable.</FONT>
</P>

<P><FONT SIZE=2>43) Question: &quot;if the return value is ignored, why set it to zero as</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the result of an RTE or indication of a fail()?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: This is only interesting for policyCondition scripts where</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the return value makes a difference. This rule makes sure that</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; upon an error, the condition does NOT select an element. This is</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; designed so that it fails gracefully.</FONT>
</P>

<P><FONT SIZE=2>44) Each of these forward references has been addressed.</FONT>
</P>

<P><FONT SIZE=2>45) Question: &quot;section 7 - if SMING changes addressing to use</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; non-OIDs, will snmpconf be able to be updated in a backwards</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; compatible way?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: The PM MIB will be fine and the language will be</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; fine. Certain accessor functions would not work and would be</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; augmented with new ones that would work.</FONT>
</P>

<P><FONT SIZE=2>46*) The original wording more naturally conveys what I want</FONT>
<BR><FONT SIZE=2>it to convey.</FONT>
</P>

<P><FONT SIZE=2>47) Fixed</FONT>
</P>

<P><FONT SIZE=2>48*) The original wording more naturally conveys what I want</FONT>
<BR><FONT SIZE=2>it to convey.</FONT>
</P>

<P><FONT SIZE=2>49) See the answer for #38</FONT>
</P>

<P><FONT SIZE=2>50) Fixed</FONT>
</P>

<P><FONT SIZE=2>Todo: put these in</FONT>
<BR><FONT SIZE=2>51*) I didn't think this really added any value and it seemed a bit</FONT>
<BR><FONT SIZE=2>distracting. Will anyone really be confused? I'll add it if it's</FONT>
<BR><FONT SIZE=2>important to you.</FONT>
</P>

<P><FONT SIZE=2>Todo: give disman credit and blame for this so people &quot;know why this</FONT>
<BR><FONT SIZE=2>is done this way&quot;:</FONT>
<BR><FONT SIZE=2>52) Section 9.1.1 provided further detail</FONT>
</P>

<P><FONT SIZE=2>53) Question: &quot;'the agent' - must it be an agent? does it apply to</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; mid-level managers as well?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: The entity that implements this MIB must be an agent. It may</FONT>
<BR><FONT SIZE=2>also</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; be a mid-level manager.</FONT>
</P>

<P><FONT SIZE=2>54) Fixed</FONT>
</P>

<P><FONT SIZE=2>55*) I think this is too much off-topic detail</FONT>
</P>

<P><FONT SIZE=2>56) Question: &quot;9.1.2 enum_decimal - are enums required to start with a</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; letter?&nbsp; How would ToInteger( 3Com(12) ) be evaluated? is the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; processing clearly defined to prevent mis-interpretation?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: enums are only processed inside of strings. So your</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; example looks like a C++ syntax error. Your example should be</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; phrased as ToInteger( &quot;3Com(12)&quot; ) and you can probably see</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; clearly now that it doesn't matter what the string begins with.</FONT>
</P>

<P><FONT SIZE=2>57) Question: &quot;can unsigned64 types with the high bit set be converted</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; reliably using ToInteger()?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: Yes.</FONT>
</P>

<P><FONT SIZE=2>58) Question: &quot;'unencoded' 'encoded' - what does this mean? not ASN.1</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; encoded?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: It means not encoded as an OID or a decimal number (to</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; distinguish it from oids and integer processing).</FONT>
</P>

<P><FONT SIZE=2>59) Question: &quot;subid: '0' | decimal_constant - why not use digit?&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: To avoid &quot;00000&quot; or &quot;00001&quot; etc.</FONT>
</P>

<P><FONT SIZE=2>60) Question: &quot;never used in these encodings over the wire&quot; - can we</FONT>
<BR><FONT SIZE=2>replace</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; &quot;these encodings&quot; with &quot;the scripts&quot;?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: It is more accurate to state this specifically for these</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; accessor functions. For example, another accessor function could</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; be defined which *would* accept and translate such descriptors.</FONT>
</P>

<P><FONT SIZE=2>61) Fixed: Changed the terminology here and in 49 other places.</FONT>
</P>

<P><FONT SIZE=2>62*) dbh: searchColumn - POSIX 1003.2 isn't mentioned in the References</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; section</FONT>
</P>

<P><FONT SIZE=2>Answeer: I don't have the information that would provide a complete</FONT>
<BR><FONT SIZE=2>reference. In the meantime, there is no ambiguity.</FONT>
</P>

<P><FONT SIZE=2>63) Question: searchColumn() - &quot;or returns an error without finding a</FONT>
<BR><FONT SIZE=2>match&quot; -</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; what are the error conditions? Since a zero means both endofView</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; and error, how can a programmer determine that they have reached</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the end of the table without error?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: You can't. You'd have to do it &quot;by hand&quot;.</FONT>
</P>

<P><FONT SIZE=2>64) Question: Can this script be written as</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; while(searchColumn(&quot;ifType&quot;, oid, ethernet(6), 0)) ?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: Unfortunately, no. That works for the other SNMP functions</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; (the ones that follow the input rules for &quot;Form of SNMP Values&quot;)</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; when the type field is set to integer yet the string is in the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; form of &quot;blah paren number paren&quot;. In this case there's no input</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; type because searchcolumn will work with any data type</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; returned. That's why it transforms returned values into strings</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; and then compares it to this 'pattern' argument.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; (BTW, if it worked, the proper syntax would have had &quot;ethernet(6)&quot;</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; in a string).</FONT>
</P>

<P><FONT SIZE=2>65) Reworded.</FONT>
</P>

<P><FONT SIZE=2>66*) See #53.</FONT>
</P>

<P><FONT SIZE=2>67*) The original wording more naturally conveys what I want</FONT>
<BR><FONT SIZE=2>it to convey.</FONT>
</P>

<P><FONT SIZE=2>68) Reworded.</FONT>
</P>

<P><FONT SIZE=2>69) [This is a clarification request and 2 questions. The</FONT>
<BR><FONT SIZE=2>clarification request resulting in a rewording].</FONT>
</P>

<P><FONT SIZE=2>Question: counterRate() - somewhat ambiguous about how many, and which,</FONT>
<BR><FONT SIZE=2>timestamped values must be kept. The paragraph starting &quot;counterRate</FONT>
<BR><FONT SIZE=2>retrieves&quot; says it keeps &quot;values&quot; so it can calculate over a longer</FONT>
<BR><FONT SIZE=2>period than since the last invocation. The paragraph that starts &quot;The</FONT>
<BR><FONT SIZE=2>implementation will need&quot; says it must retain one value older than</FONT>
<BR><FONT SIZE=2>minInterval seconds. So, if I have a minInterval of 5 seconds, do I</FONT>
<BR><FONT SIZE=2>need to keep the last read (less than 5 seconds ago) and one more</FONT>
<BR><FONT SIZE=2>read?</FONT>
</P>

<P><FONT SIZE=2>Answer: Yes.</FONT>
</P>

<P><FONT SIZE=2>Question: What are the interoperability issues if I set two boxes to</FONT>
<BR><FONT SIZE=2>have</FONT>
<BR><FONT SIZE=2>minIntervals of 5 seconds, and vendor A keeps the most current and the</FONT>
<BR><FONT SIZE=2>most current + 5, but vendor B keeps the most current and the most</FONT>
<BR><FONT SIZE=2>current + 15 (discarding the current+5 and current+10 samples?).&nbsp; 70)</FONT>
<BR><FONT SIZE=2>is there a way to tell how many samples have been kept?</FONT>
</P>

<P><FONT SIZE=2>Answer: The use of the phrase &quot;old values&quot; meant that it would only</FONT>
<BR><FONT SIZE=2>delete</FONT>
<BR><FONT SIZE=2>&quot;from the end&quot; (i.e. values that had expired). I've reworded this to</FONT>
<BR><FONT SIZE=2>make the point more strongly.</FONT>
</P>

<P><FONT SIZE=2>70) Question: is there a way to tell how many samples have been kept?</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: No</FONT>
</P>

<P><FONT SIZE=2>71) Question: is there a way to access the samples? their timestamps?</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: No to both questions.</FONT>
</P>

<P><FONT SIZE=2>72*) I don't see any better way to do this.</FONT>
</P>

<P><FONT SIZE=2>73) Question: &quot;Otherwise, this delta will be dividied by the number of</FONT>
<BR><FONT SIZE=2>seconds</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; elapsed between the two retrievals ...&quot; assumes there are two</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; retrieveals. What if an implementation keeps more than two? how</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; will the value be calculated?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: The text specifically refers to two particular retrievals</FONT>
<BR><FONT SIZE=2>amongst</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the many that may be stored:</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 1) The most recent one (now); and,</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; 2) The newest retrieval that is at least minInterval old.</FONT>
</P>

<P><FONT SIZE=2>74) Fixed. (Rounded down)</FONT>
</P>

<P><FONT SIZE=2>75) Fixed. (Formatted into bullets).</FONT>
</P>

<P><FONT SIZE=2>76*) It is done this way simply for symmetry.</FONT>
</P>

<P><FONT SIZE=2>77*) I think this is an important clarification. I don't want to</FONT>
<BR><FONT SIZE=2>delete the clarification.</FONT>
</P>

<P><FONT SIZE=2>78) Question: newPDU() - can a PDU that is received in a trap be read</FONT>
<BR><FONT SIZE=2>using the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; functions described here?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: No</FONT>
</P>

<P><FONT SIZE=2>79) Question: 9.1.4.4 is snmpSend() synchronous or asynchronous? This is</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; important to know for off-box queries.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: It is synchronous</FONT>
</P>

<P><FONT SIZE=2>80*) I don't think it's clear one way or another (it's really a style</FONT>
<BR><FONT SIZE=2>issue). But this is a big thing to change at this time without a clear</FONT>
<BR><FONT SIZE=2>mandate (things changed now won't receive the same level of review and</FONT>
<BR><FONT SIZE=2>concensus as things changed some time ago).</FONT>
</P>

<P><FONT SIZE=2>81) Question: 9.2 Are the HC datatypes supported? What does</FONT>
<BR><FONT SIZE=2>counterRate() return for a 64-bit counter delta?</FONT>
</P>

<P><FONT SIZE=2>Answer: Yes, they are supported. The native integer variables have 64</FONT>
<BR><FONT SIZE=2>bits of precision and counterRate has an option for doing 32 bit or 64</FONT>
<BR><FONT SIZE=2>bit counters as appropriate.</FONT>
</P>

<P><FONT SIZE=2>82) Question: &quot;local&quot; errors - when acting as a MLM, are these local</FONT>
<BR><FONT SIZE=2>errors or</FONT>
<BR><FONT SIZE=2>remote errors? Do we have remote errors?</FONT>
</P>

<P><FONT SIZE=2>Answer: &quot;Local Errors&quot; refers to errors encountered in the API that</FONT>
<BR><FONT SIZE=2>aren't present in the protocol. For example, a timeout error.</FONT>
<BR><FONT SIZE=2>The distinction between local and remote is the same whether the</FONT>
<BR><FONT SIZE=2>transactions stay on the box or go over the wire.</FONT>
</P>

<P><FONT SIZE=2>83*) dbh: Constants for SnmpMessageProcessingModel and SnmpSecurityModel</FONT>
<BR><FONT SIZE=2>-</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; if additional security models are defined, can they be supported</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; in snmpconf? A reference to the official definition of these</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; values would be better than &quot;hard-coding&quot; the list here. Ditto for</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; SNMP operation types, SNMP errors, and other constants. It's ok to</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; include the constants here, but there should be a disclaimer that</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the official list is found in [wherever].</FONT>
</P>

<P><FONT SIZE=2>Answer: But these are the values that a script can depend on to be</FONT>
<BR><FONT SIZE=2>pre-defined. There are no other values defined as constants. If other</FONT>
<BR><FONT SIZE=2>security models are defined, the function library would need to be</FONT>
<BR><FONT SIZE=2>updated to support them.</FONT>
</P>

<P><FONT SIZE=2>84) Fixed</FONT>
</P>

<P><FONT SIZE=2>85) Fixed</FONT>
</P>

<P><FONT SIZE=2>86*) These are only used internally, not over the wire. They are</FONT>
<BR><FONT SIZE=2>defined this way on purpose.</FONT>
</P>

<P><FONT SIZE=2>87) Done: reordered all the sections in this chapter.</FONT>
</P>

<P><FONT SIZE=2>88*) The argument isn't compelling enough to warrant changing all 10</FONT>
<BR><FONT SIZE=2>instances of this phrase.</FONT>
</P>

<P><FONT SIZE=2>89) Fixed</FONT>
</P>

<P><FONT SIZE=2>90) dbh: elementContext() is provided, and elementAddress() is provided,</FONT>
</P>

<P><FONT SIZE=2>but elementContextEngineID() is missing, which is especially notable</FONT>
<BR><FONT SIZE=2>given that roleMatch() uses contextEngineID rather than the address.</FONT>
</P>

<P><FONT SIZE=2>Answer: You don't need to do this. roleMatch() uses the element,</FONT>
<BR><FONT SIZE=2>context, and contextEngineID of &quot;this element&quot; by default. So</FONT>
<BR><FONT SIZE=2>roleMatch(string, element, context, elementContextEngineID())</FONT>
<BR><FONT SIZE=2>is the same as</FONT>
<BR><FONT SIZE=2>roleMatch(string, element, context)</FONT>
</P>

<P><FONT SIZE=2>Todo:</FONT>
<BR><FONT SIZE=2>But, I do see a bug where the text that says &quot;If 'contextEngineID' is</FONT>
<BR><FONT SIZE=2>not present, the local system will be used.&quot; should read &quot;If</FONT>
<BR><FONT SIZE=2>'contextEngineID' is not present, the contextEngineID of this element</FONT>
<BR><FONT SIZE=2>will be used.&quot;</FONT>
</P>

<P><FONT SIZE=2>91) dbh: roleMatch() ues contextEngineID and doesn't permit using the</FONT>
<BR><FONT SIZE=2>address, but nonLocalArgs favors the address over contextEngineID (the</FONT>
<BR><FONT SIZE=2>contextEngineID in nonLocalArgs can be not-present, and commands will</FONT>
<BR><FONT SIZE=2>be sent to the address specified, which is in keeping with SNMPv3</FONT>
<BR><FONT SIZE=2>engineID discovery).</FONT>
</P>

<P><FONT SIZE=2>Answer: This is by design. NonLocalArgs is used in the SNMP</FONT>
<BR><FONT SIZE=2>library functions as it is used to specify transport information with</FONT>
<BR><FONT SIZE=2>which to send SNMP packets (possibly through proxies). RoleMatch()</FONT>
<BR><FONT SIZE=2>refers to a local database of role information for local and non-local</FONT>
<BR><FONT SIZE=2>systems. The authoritative identifier for a non-local system is the</FONT>
<BR><FONT SIZE=2>contextEngineID, regardless of any of the transport addresses it may</FONT>
<BR><FONT SIZE=2>be reached through (or next-hop addresses when going through a proxy).</FONT>
</P>

<P><FONT SIZE=2>92) Your comment initiated a major rewrite of this section.</FONT>
</P>

<P><FONT SIZE=2>93) Done</FONT>
</P>

<P><FONT SIZE=2>94) Resolved</FONT>
</P>

<P><FONT SIZE=2>95) Fixed.</FONT>
</P>

<P><FONT SIZE=2>96) Clarified</FONT>
</P>

<P><FONT SIZE=2>97) Question: &quot;Contents of the scratchpad are erased on reboot.&quot; -</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; doesn't this contradict the purpose of storageType?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: No. Scripts need to be able to bootstrap themselves when</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; they are first installed or when an element appears. This is just</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; another one of those times. Think of it as all the elements</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; disappearing when the box goes down and re-appearing when it</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; starts up again.</FONT>
</P>

<P><FONT SIZE=2>98) Fixed</FONT>
</P>

<P><FONT SIZE=2>99) Question: I am unclear on how to specify a modifiable parameter in</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; a function call - is it the C-style (&amp;val), where the address of</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the variable is provided, or the C++-style (val), where the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; reference is defined in the prototype?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp; Answer: It is the C++ style. In the beginning of section 9 you can</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; read: &quot;In the function prototype, if the '&amp;' character precedes</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the identifier for an argument, that argument may be modified by</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the function (e.g., &quot;integer &amp;result, ...)&quot;). Arguments without</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; the '&amp;' character cannot be modified by the function.&nbsp; In a</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; script, modifiable arguments don't need to be preceeded by a '&amp;'.&quot;</FONT>
</P>

<P><FONT SIZE=2>100) Question: &quot;Is it an RTE if I specify getScratchpad(Global,&quot;foo&quot;,</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; &quot;55&quot;)? The string &quot;55&quot; is associated with a memory location, just</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; as val is, but the memory location for &quot;55&quot; may be read-only</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; memory. Writing to it might cause a core dump. Alternately, a</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; manifest constant string might be modified, making the rest of</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; hte program malfunction.&quot;</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: Yes, it is an RTE. I added the following text to the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; beginning of Section 9 to clarify:&nbsp; &quot;It is a RTE if a constant is</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; passed to a modifiable function argument (regardless of whether</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; the function actually writes to the argument).&quot;</FONT>
</P>

<P><FONT SIZE=2>101) Question: 9.3.9 defines constants for use with the scratchpad</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; functions. Shouldn't these constants be defined with the other</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; constants?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: I think it's more modular this way and thus more</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; readable. The other constants are many pages away.</FONT>
</P>

<P><FONT SIZE=2>102) Fixed</FONT>
</P>

<P><FONT SIZE=2>103) Fixed.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Question: Are all the bits in pmTrackingPEInfo cleared at the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; start of each execution?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: The bits related to conditions(actions) are cleared at the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; beginning of execution of the condition(action). This is clearly</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; spelled out in the pmTrackingPEInfo MIB object.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Question:&nbsp;&nbsp;&nbsp;&nbsp; How do I know whether conditionUserSignal or</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; actionUserSignal will be set?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: The pmTrackingPEInfo MIB object spells out clear rules.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Question: Assuming it</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; gets set depending on whether a condition or action is being</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; evaluated, does the conditionUserSignal get cleared when the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; action is evaluated, or when the next condition is evaluated?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: (Your initial assumption is correct). It is only cleared</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; when the next condition is evaluated.</FONT>
</P>

<P><FONT SIZE=2>104*) dbh: defer() - In the description, the order of discussion is</FONT>
<BR><FONT SIZE=2>default</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; behavior, defer(1), then defer(0). is the default behavior and</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; defer(0) equivalent? if so, they should be discussed together.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: I tried writing it that way and it just looked more</FONT>
<BR><FONT SIZE=2>awkward.</FONT>
</P>

<P><FONT SIZE=2>105) Question: defer() - the discussion that preceds the prototype</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; talks about gold is appropriate but isn't possible. It doesn't</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; say anything about hitting a RTE. But the description in the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; prototype is dependent on hitting an RTE. Is it always true, and</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; a restriction that any future library developers must be aware</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; of, that an RTE MUST be triggered if it isn't possible to do</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; something?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: No, that isn't the case. If you've been selected as the</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; highest precedence policy but then discover you can't fulfill</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; your responsibility, you can call fail(1, ...). Defer is used to</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; provide instructions in the event that you accidently hit an RTE</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; (say, divide by zero). In such an even, you can't choose to call</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; fail() because you're dead. Think of defer as the Last Will and</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Testament for a policy :-)</FONT>
</P>

<P><FONT SIZE=2>106) Question: Can a script writer choose to voluntarily, as part of</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; their logic, fail() and defer()? Is that an RTE, or just</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; returning a false condition?</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Answer: You can fail(1, ...) which has the side effect of</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; deferring as you die. A script's execution halts when it hits</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; fail() so in fail(); defer();, defer() never runs.</FONT>
</P>

<P><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; Fail and defer are functions that only provide value in an action</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; script, which is only run of the corresponding condition has</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp;&nbsp; already returned true.</FONT>
</P>
<BR>

<P><FONT SIZE=2>107) Fixed.</FONT>
</P>

<P><FONT SIZE=2>108) Fixed.</FONT>
</P>

<P><FONT SIZE=2>109) Rewritten.</FONT>
</P>

<P><FONT SIZE=2>[pg 4, sec 3, Overview]</FONT>
<BR><FONT SIZE=2>There were so many good slides presented in the WG describing</FONT>
<BR><FONT SIZE=2>the layering from independent to dependent data abstractions,</FONT>
<BR><FONT SIZE=2>but none of that made it into the draft. (The entire overview</FONT>
<BR><FONT SIZE=2>is less than a page.)</FONT>
</P>

<P><FONT SIZE=2>There is no attempt to describe how this draft addresses any</FONT>
<BR><FONT SIZE=2>of the motherhood &amp; apple pie goals listed in para 2.</FONT>
</P>

<P><FONT SIZE=2>There is no attempt (anywhere in the draft) to describe the</FONT>
<BR><FONT SIZE=2>overall system that is defined within the draft. The draft</FONT>
<BR><FONT SIZE=2>reads like a parts list without instructions on how to put</FONT>
<BR><FONT SIZE=2>all the parts together.&nbsp; Some of the missing details:</FONT>
<BR><FONT SIZE=2>&nbsp;- a diagram showing the components of the PM system</FONT>
<BR><FONT SIZE=2>&nbsp;- a diagram showing how the PM system fits within the overall</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; managed device</FONT>
<BR><FONT SIZE=2>&nbsp;- a diagram showing how the PM system fits within the overall</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; NM system as a mid-level manager</FONT>
<BR><FONT SIZE=2>&nbsp;- explanations of all the components, such as:</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - element discovery</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - element registration</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - capabilities registration</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - roles</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policies</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy groups</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy selection</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy distribution</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy organization</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy conditions</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy actions</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy scheduling</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy script execution environment</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - element filtering</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - accessor library</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy validation</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - schedule group</FONT>
<BR><FONT SIZE=2>&nbsp;- how the components relate to each other</FONT>
<BR><FONT SIZE=2>&nbsp;- how the entire system fits within the SNMP Architecture</FONT>
</P>

<P><FONT SIZE=2>[pg 5, sec 4, Arch.]</FONT>
<BR><FONT SIZE=2>This section would make more sense if the system was explained</FONT>
<BR><FONT SIZE=2>first. This section doesn't really describe an architecture,</FONT>
<BR><FONT SIZE=2>but rather the notion of policy based management (again).</FONT>
<BR><FONT SIZE=2>It doesn't really explain the system that implementors are</FONT>
<BR><FONT SIZE=2>supposed to create, and how operators are supposed to use it.</FONT>
</P>

<P><FONT SIZE=2>[pg 6, para 1, sec 4, Arch.]</FONT>
<BR><FONT SIZE=2>The description of &quot;this element&quot; is confusing because there</FONT>
<BR><FONT SIZE=2>has been no detailed explanation (and won't be) of the runtime</FONT>
<BR><FONT SIZE=2>environment.</FONT>
</P>

<P><FONT SIZE=2>[pg 8, para 2, sec 5.1, Terminology]</FONT>
<BR><FONT SIZE=2>This section should be moved to a general terms section either before</FONT>
<BR><FONT SIZE=2>or after the overview.&nbsp; The details about RTE should stay in section 5.</FONT>
<BR><FONT SIZE=2>Some terms that need introduction:</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - element type</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - element</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - &quot;this&quot; element</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - system element 0.0</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - role</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy group</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy condition</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - policy action</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - accessor function</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - schedule group</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp;&nbsp; - precedence group</FONT>
</P>

<P><FONT SIZE=2>[pg 8, para 4, sec 5.2, Element Discovery]</FONT>
<BR><FONT SIZE=2>&quot;as 1 element&quot; -&gt; &quot;as one element&quot;. [done]</FONT>
</P>

<P><FONT SIZE=2>In the last sentence, it's not clear how this applies to</FONT>
<BR><FONT SIZE=2>the runtime environment.&nbsp; It would help to explain the runtime</FONT>
<BR><FONT SIZE=2>environment at a high-level (iterative engine, and how it</FONT>
<BR><FONT SIZE=2>operates on elements) somewhere in section 5.</FONT>
</P>

<P><FONT SIZE=2>[pg 9, sec 5.2, Element Discovery]</FONT>
<BR><FONT SIZE=2>It isn't clear why the details of the element registration</FONT>
<BR><FONT SIZE=2>MIB are explained, because the rest of the discussion is</FONT>
<BR><FONT SIZE=2>about element discovery. How does NMS registration relate</FONT>
<BR><FONT SIZE=2>to discovery?&nbsp; It is confusing to mix MIB object</FONT>
<BR><FONT SIZE=2>details in with this high level discussion.&nbsp; (They should</FONT>
<BR><FONT SIZE=2>be in a separate MIB overview section.) In general, the</FONT>
<BR><FONT SIZE=2>MIB objects are discussed in detail before the MIB is introduced.</FONT>
</P>

<P><FONT SIZE=2>[pg 10, sec 5.2,1 Implementation Notes]</FONT>
<BR><FONT SIZE=2>This section should be moved to later in the document.</FONT>
<BR><FONT SIZE=2>because the MIB has not been introduced, and all the</FONT>
<BR><FONT SIZE=2>implementation notes should be grouped together.</FONT>
</P>

<P><FONT SIZE=2>[pg 11, para 2, sec 5.3 Element Filtering]</FONT>
<BR><FONT SIZE=2>This first paragraph contains MIB details about policy</FONT>
<BR><FONT SIZE=2>scheduling, and should go in a section for that (added</FONT>
<BR><FONT SIZE=2>before this one). This concept is called 'policyCondition'</FONT>
<BR><FONT SIZE=2>everywhere but this section.</FONT>
</P>

<P><FONT SIZE=2>[pg 11, sec 5.3,1 Implementation Notes]</FONT>
<BR><FONT SIZE=2>&quot;It is an implementation-dependent matter as to how policy</FONT>
<BR><FONT SIZE=2>conditions are scheduled.&quot;&nbsp; This is pretty much the entire</FONT>
<BR><FONT SIZE=2>description of the script invocation and scheduling details.</FONT>
<BR><FONT SIZE=2>I think it will be difficult for script developers to port</FONT>
<BR><FONT SIZE=2>scripts across PM implementations with this approach. There</FONT>
<BR><FONT SIZE=2>are also many constraints placed on scheduling throughout</FONT>
<BR><FONT SIZE=2>the document, so this statement is misleading.</FONT>
</P>

<P><FONT SIZE=2>[pg 11, sec 5.4 Policy Enforcement]</FONT>
<BR><FONT SIZE=2>This concept is called 'policyAction' everywhere but this section.</FONT>
</P>

<P><FONT SIZE=2>[pg 12, sec 5.4,1 Implementation Notes]</FONT>
<BR><FONT SIZE=2>I think it will be difficult for script developers to port</FONT>
<BR><FONT SIZE=2>scripts across PM implementations without specifying scheduling</FONT>
<BR><FONT SIZE=2>algorithms, scheduling conflict resolution, etc.)</FONT>
</P>

<P><FONT SIZE=2>It is not clear what by the 2nd setence &quot;each ... pair</FONT>
<BR><FONT SIZE=2>its own process ... run simultaneously.&quot;</FONT>
</P>

<P><FONT SIZE=2>The execution control flow should be explained (from engine</FONT>
<BR><FONT SIZE=2>to condition script to action script within a specific iteration</FONT>
<BR><FONT SIZE=2>sequence, based on registered elements, configured latencies,</FONT>
<BR><FONT SIZE=2>system events, etc.)</FONT>
</P>

<P><FONT SIZE=2>[pg 12, sec 5.5, Definitions]</FONT>
<BR><FONT SIZE=2>These terms should be moved to a general Terms section.</FONT>
</P>

<P><FONT SIZE=2>term &quot;precedence policy&quot; should be explained in the Terms section</FONT>
</P>

<P><FONT SIZE=2>[pg 22-23, sec. 6.3, QuickStart Guide]</FONT>
</P>

<P><FONT SIZE=2>The other examples of finding the gold interface or</FONT>
<BR><FONT SIZE=2>killing all application processes that have run for &gt; 5 min</FONT>
<BR><FONT SIZE=2>are not very compelling.&nbsp; IMO. the document doesn't effectively</FONT>
<BR><FONT SIZE=2>demonstrate that the PM MIB can be used to perform the</FONT>
<BR><FONT SIZE=2>initial configuration of a real managed device, such as a router.</FONT>
</P>

<P><FONT SIZE=2>Some code examples for readVar would be helpful.</FONT>
</P>

<P><FONT SIZE=2>[pg 47, sec 9.1.4, general]</FONT>
<BR><FONT SIZE=2>These functions are very important and it would help to have</FONT>
<BR><FONT SIZE=2>a meaningful example that used all of them.</FONT>
</P>

<P><FONT SIZE=2>[pg 50, sec 9.3.1, roleMatch]</FONT>
<BR><FONT SIZE=2>Meaningful examples of this accessor function would help.</FONT>
</P>

<P><FONT SIZE=2>[pg 56. sec 9.3.11, defer]</FONT>
<BR><FONT SIZE=2>The concept of precedence groups should be explained</FONT>
<BR><FONT SIZE=2>way before here, in an accessor function description.</FONT>
<BR><FONT SIZE=2>The whole concept is fuzzy, potentially complicated,</FONT>
<BR><FONT SIZE=2>and never explained or shown in examples. How is</FONT>
<BR><FONT SIZE=2>the system configured to utilize &quot;runner-up&quot; policies?</FONT>
<BR><FONT SIZE=2>The mechanism should be better explained.</FONT>
</P>

<P><FONT SIZE=2>[pg 58. sec 9.4.1, regexp]</FONT>
<BR><FONT SIZE=2>Example code showing meaningful usage of the match</FONT>
<BR><FONT SIZE=2>parameter would be helpful.</FONT>
</P>

<P><FONT SIZE=2>[pg 58-59. sec 9.4.2, regexpReplace]</FONT>
<BR><FONT SIZE=2>Example code would be helpful.</FONT>
</P>

<P><FONT SIZE=2>Are there restrictions on the value of 'replacement'?</FONT>
</P>

<P><FONT SIZE=2>Does an RTE occur if the string replacement causes</FONT>
<BR><FONT SIZE=2>the 'src' string to overflow?</FONT>
</P>

<P><FONT SIZE=2>[pg 62. sec 9.4.9, parseIndex]</FONT>
<BR><FONT SIZE=2>An example for each variant of the function would be helpful.</FONT>
</P>

<P><FONT SIZE=2>It would help in the example to show what OID fragment values</FONT>
<BR><FONT SIZE=2>are actually stored in each var = parseIndex() call.</FONT>
<BR><FONT SIZE=2>The example is misleading because the string ipForwardIfIndex</FONT>
<BR><FONT SIZE=2>is not actually allowed.</FONT>
</P>

<P><FONT SIZE=2>[pg 64. sec 9.4.14-16, chr, ord, substr]</FONT>
<BR><FONT SIZE=2>Meaningful code examples of these functions would help.</FONT>
</P>

<P><FONT SIZE=2>[pg 65. sec 9.5, Library Accessor Functions]</FONT>
<BR><FONT SIZE=2>The full function prototypes for these POSIX functions</FONT>
<BR><FONT SIZE=2>should be provided.</FONT>
</P>

<P><FONT SIZE=2>No mention of the sprintf format codes is made.</FONT>
</P>

<P><FONT SIZE=2>How does each and every format code variant map to a data type</FONT>
<BR><FONT SIZE=2>in PolicyScript?</FONT>
</P>

<P><FONT SIZE=2>Is an RTE generated if the number of parameters passed</FONT>
<BR><FONT SIZE=2>to sprintf does not match the format string?</FONT>
</P>

<P><FONT SIZE=2>Is an RTE generated if the type of a parameter passed</FONT>
<BR><FONT SIZE=2>to sprintf does not match the format string type?</FONT>
</P>

<P><FONT SIZE=2>[pg 65. sec 10, Schedule Table]</FONT>
<BR><FONT SIZE=2>There is no overall explanation of time-based scheduling.</FONT>
<BR><FONT SIZE=2>This should be in the section on the runtime environment.</FONT>
<BR><FONT SIZE=2>This section is out of place here.</FONT>
</P>

<P><FONT SIZE=2>The term 'schedule group' is used here but not defined anywhere.</FONT>
</P>

<P><FONT SIZE=2>The discussion of the pmScheduleTable should be in</FONT>
<BR><FONT SIZE=2>an overview of the MIB.</FONT>
</P>

<P><FONT SIZE=2>[pg 68. sec 11, Definitions]</FONT>
<BR><FONT SIZE=2>There is no overview section to introduce the MIB groups</FONT>
<BR><FONT SIZE=2>as is customary in standard MIBs.&nbsp; The MIB is harder</FONT>
<BR><FONT SIZE=2>to read because of this omission.</FONT>
</P>

<P><FONT SIZE=2>A diagram showing the different groups in the MIB</FONT>
<BR><FONT SIZE=2>and explanations of each group and its relationship</FONT>
<BR><FONT SIZE=2>to the other groups (if relevant) would be helpful.</FONT>
</P>

<P><FONT SIZE=2>[pg 72, sec 11, pmPolicyPrecedenceGroup]</FONT>
<BR><FONT SIZE=2>There are no examples of this potentially complicated</FONT>
<BR><FONT SIZE=2>mechanism in the document. Many runtime environment</FONT>
<BR><FONT SIZE=2>features (like this one) are explained and defined</FONT>
<BR><FONT SIZE=2>via MIB objects, which makes them hard to figure out.</FONT>
</P>

<P><FONT SIZE=2>[pg 76, sec 11, pmPolicyConditionMaxLatency]</FONT>
<BR><FONT SIZE=2>&nbsp;&nbsp; &quot;... may wish to re-run .. change to the role strings&quot;</FONT>
<BR><FONT SIZE=2>This is another execution environment tidbit scattered</FONT>
<BR><FONT SIZE=2>in the document.&nbsp; All of these should be collected</FONT>
<BR><FONT SIZE=2>and placed outside the MIB description clauses.</FONT>
</P>

<P><FONT SIZE=2>[pg 77, sec 11, pmPolicyMaxIterations]</FONT>
<BR><FONT SIZE=2>This object is allowed to change at any time, which is</FONT>
<BR><FONT SIZE=2>difficult to implement.&nbsp; If an NMS lowers this object</FONT>
<BR><FONT SIZE=2>while a script is running in a while loop, will the</FONT>
<BR><FONT SIZE=2>agent instantly detect the change? On the next policy</FONT>
<BR><FONT SIZE=2>task invocation?&nbsp; Within some max latency?</FONT>
</P>

<P><FONT SIZE=2>[pg 77-78, sec 11, pmPolicyTable gauges]</FONT>
<BR><FONT SIZE=2>It's not clear what the underlying execution model is,</FONT>
<BR><FONT SIZE=2>so it's also unclear what starts the counting and</FONT>
<BR><FONT SIZE=2>stops the counting for a particular gauge value.</FONT>
</P>

<P><FONT SIZE=2>[pg 80, sec 11, Policy Code Table]</FONT>
<BR><FONT SIZE=2>This long ASN.1 comment should be in a MIB overview</FONT>
<BR><FONT SIZE=2>section instead.</FONT>
</P>

<P><FONT SIZE=2>[pg 83, sec 11, Element Type Registration Table]</FONT>
<BR><FONT SIZE=2>This long ASN.1 comment should be in a MIB overview</FONT>
<BR><FONT SIZE=2>section instead.</FONT>
</P>

<P><FONT SIZE=2>What happens to the running script if an entry is removed</FONT>
<BR><FONT SIZE=2>from this table. What does the runtime do if the current</FONT>
<BR><FONT SIZE=2>loop is the elementType removed? Is there an RTE error</FONT>
<BR><FONT SIZE=2>code for this condition?</FONT>
</P>

<P><FONT SIZE=2>What happens to the running script if an entry is added</FONT>
<BR><FONT SIZE=2>to this table that changes an element filter evaluation?</FONT>
</P>

<P><FONT SIZE=2>The document never actually defines what constitutes</FONT>
<BR><FONT SIZE=2>an element type, so it's hard to tell how the agent</FONT>
<BR><FONT SIZE=2>is supposed to auto-populate this table.</FONT>
</P>

<P><FONT SIZE=2>[pg 85, sec 11, pmElementTypeRegOIDPrefix]</FONT>
<BR><FONT SIZE=2>The &quot;0.0&quot; system entry is not mandatory (none are),</FONT>
<BR><FONT SIZE=2>yet there are accessor functions (like roleMatch)</FONT>
<BR><FONT SIZE=2>that need this entry. Is this entry required or</FONT>
<BR><FONT SIZE=2>do those accessor functions cause an RTE if they</FONT>
<BR><FONT SIZE=2>reference the non-existent 0.0 entry?</FONT>
</P>

<P><FONT SIZE=2>[pg 86-87, sec 11, Role Table]</FONT>
<BR><FONT SIZE=2>This long ASN.1 comment should be in a MIB overview</FONT>
<BR><FONT SIZE=2>section instead.</FONT>
</P>

<P><FONT SIZE=2>[pg 88, sec 11, pmRoleElement]</FONT>
<BR><FONT SIZE=2>Does this re-indexing rule apply if the element is</FONT>
<BR><FONT SIZE=2>in on a different engine? Is there a max latency</FONT>
<BR><FONT SIZE=2>for discovering re-indexing?&nbsp; This is a tall order,</FONT>
<BR><FONT SIZE=2>considering other text in the document says the</FONT>
<BR><FONT SIZE=2>agent doesn't really know (and doesn't enforce)</FONT>
<BR><FONT SIZE=2>the structure of the OID instance in any other cases.</FONT>
</P>

<P><FONT SIZE=2>[pg 105-106, sec 11, pmTrackingEPStatus]</FONT>
<BR><FONT SIZE=2>What happens if this is set to forceOff while a policy</FONT>
<BR><FONT SIZE=2>is running? Does the script complete if it was just</FONT>
<BR><FONT SIZE=2>forced off? Does it end with an RTE?</FONT>
</P>

<P><FONT SIZE=2>Do other MIB status objects change elsewhere</FONT>
<BR><FONT SIZE=2>in the pmPolicyTable when this is set to forceOff?</FONT>
</P>

<P><FONT SIZE=2>[pg 112, sec 14, Acknowledgements]</FONT>
<BR><FONT SIZE=2>No mention whatsoever, or reference, is given for the</FONT>
<BR><FONT SIZE=2>Scheduling MIB, even though several hundred lines of</FONT>
<BR><FONT SIZE=2>text were lifted from that MIB.&nbsp; The cut-and-paste</FONT>
<BR><FONT SIZE=2>is bad enough!</FONT>
</P>

<P><FONT SIZE=2>[pg 116, sec 17, Intellectual Property]</FONT>
<BR><FONT SIZE=2>I think different text is supposed to go here if the WG</FONT>
<BR><FONT SIZE=2>knows of any claims of patented IP pertaining to this work,</FONT>
<BR><FONT SIZE=2>and I believe BMC Software is making such a claim.</FONT>
</P>

<P><FONT SIZE=2>[pg 118, ToC]</FONT>
<BR><FONT SIZE=2>This should go in the front of the document.</FONT>
</P>
<BR>

</BODY>
</HTML>
------_=_NextPart_001_01C2178C.12EA4B00--


From owner-snmpconf@seymour39.snmp.com  Wed Jun 19 11:33:15 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA23496
	for <snmpconf-archive@odin.ietf.org>; Wed, 19 Jun 2002 11:33:15 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id LAA06859
	for snmpconf-outgoing; Wed, 19 Jun 2002 11:29:41 -0400 (EDT)
Message-ID: <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.com>
From: "Harrington, David" <dbh@enterasys.com>
To: "snmpconf@snmp. com (E-mail)" <snmpconf@snmp.com>
Subject: snmpconf advancement
Date: Wed, 19 Jun 2002 11:24:25 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C217A5.65358366"
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C217A5.65358366
Content-Type: text/plain;
	charset="iso-8859-1"

Hi,

I have been involved with snmpconf, and have reviewed the snmpconf specs
closely, but have always had reservations about some aspects of it. Others
have shared my concerns. 

Some of my concerns are:
1) useability by operators
2) useability by application developers
3) CPU impact on devices
4) scalability

I believe snmpconf could be a very good approach to standardizing management
across vendors, and bringing functional capabilities to SNMP to raise it
above the peek/poke approach, without needing to modify the protocol itself.
These have all been identified as goals of much of the O&M community.

Therefore, as one of the more vocal reviewers of snmpconf, I would like to
request that the ADs approve advancement of this to Proposed Standard, once
submitted by the chairs, so we can determine whether this is an approach
operators and vendors alike can get behind.

I would also like to personally encourage open source developers to produce
a reference implementation, probably as a mid-level manager that translates
snmpconf scripts into mib-specific SNMP commands, so operators can determine
whether the language is sufficiently easy to use, and the CPU overhead can
be measured.

Thanks,
dbh

David Harrington
Network Management Architect
Office of the CTO
Enterasys Networks
 

------_=_NextPart_001_01C217A5.65358366
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2655.35">
<TITLE>snmpconf advancement</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi,</FONT>
</P>

<P><FONT SIZE=3D2>I have been involved with snmpconf, and have reviewed =
the snmpconf specs closely, but have always had reservations about some =
aspects of it. Others have shared my concerns. </FONT></P>

<P><FONT SIZE=3D2>Some of my concerns are:</FONT>
<BR><FONT SIZE=3D2>1) useability by operators</FONT>
<BR><FONT SIZE=3D2>2) useability by application developers</FONT>
<BR><FONT SIZE=3D2>3) CPU impact on devices</FONT>
<BR><FONT SIZE=3D2>4) scalability</FONT>
</P>

<P><FONT SIZE=3D2>I believe snmpconf could be a very good approach to =
standardizing management across vendors, and bringing functional =
capabilities to SNMP to raise it above the peek/poke approach, without =
needing to modify the protocol itself. These have all been identified =
as goals of much of the O&amp;M community.</FONT></P>

<P><FONT SIZE=3D2>Therefore, as one of the more vocal reviewers of =
snmpconf, I would like to request that the ADs approve advancement of =
this to Proposed Standard, once submitted by the chairs, so we can =
determine whether this is an approach operators and vendors alike can =
get behind.</FONT></P>

<P><FONT SIZE=3D2>I would also like to personally encourage open source =
developers to produce a reference implementation, probably as a =
mid-level manager that translates snmpconf scripts into mib-specific =
SNMP commands, so operators can determine whether the language is =
sufficiently easy to use, and the CPU overhead can be =
measured.</FONT></P>

<P><FONT SIZE=3D2>Thanks,</FONT>
<BR><FONT SIZE=3D2>dbh</FONT>
</P>

<P><FONT SIZE=3D2>David Harrington</FONT>
<BR><FONT SIZE=3D2>Network Management Architect</FONT>
<BR><FONT SIZE=3D2>Office of the CTO</FONT>
<BR><FONT SIZE=3D2>Enterasys Networks</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C217A5.65358366--


From owner-snmpconf@seymour39.snmp.com  Thu Jun 20 04:50:09 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22325
	for <snmpconf-archive@odin.ietf.org>; Thu, 20 Jun 2002 04:50:08 -0400 (EDT)
Received: by seymour39.snmp.com (8.9.3/m.000221) id EAA29915
	for snmpconf-outgoing; Thu, 20 Jun 2002 04:44:36 -0400 (EDT)
Date: Thu, 20 Jun 2002 05:46:54 +0200
From: Harrie Hazewinkel <harrie@jumpy.it>
To: "Harrington, David" <dbh@enterasys.com>
cc: snmpconf@snmp.com
Subject: Re: snmpconf advancement
Message-ID: <7290503.1024552014@localhost>
In-Reply-To: <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.com>
References:  <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.co
 m>
X-Mailer: Mulberry/2.2.0b4 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 7bit



--On Wednesday, June 19, 2002 11:24 AM -0400 "Harrington, David" 
<dbh@enterasys.com> wrote:
>
> I would also like to personally encourage open source developers to
> produce a reference implementation, probably as a mid-level manager that
> translates snmpconf scripts into mib-specific SNMP commands, so operators
> can determine whether the language is sufficiently easy to use, and the
> CPU overhead can be measured.


Speaking as someone who works a lot with open-source. An open-source
implementation gets done by two groups;
   1) poeple doing it as study or hobby and
   2) poeple who can do it because there employer supports it.

So is Enterasys willing to sponsor such an effort?? Or others??



cheers,
Harrie


From owner-snmpconf@seymour39.snmp.com  Thu Jun 20 07:03:43 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA24558
	for <snmpconf-archive@odin.ietf.org>; Thu, 20 Jun 2002 07:03:43 -0400 (EDT)
Received: by seymour39.snmp.com (8.9.3/m.000221) id HAA05904
	for snmpconf-outgoing; Thu, 20 Jun 2002 07:00:16 -0400 (EDT)
Message-Id: <200206201059.GAA24011@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: snmpconf@snmp.com
From: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-snmpconf-diffpolicy-05.txt
Date: Thu, 20 Jun 2002 06:59:00 -0400
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

--NextPart

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

	Title		: The Differentiated Services Configuration MIB
	Author(s)	: H. Hazewinkel, D. Partain
	Filename	: draft-ietf-snmpconf-diffpolicy-05.txt
	Pages		: 27
	Date		: 19-Jun-02
	
This memo describes a MIB module that provides a conceptual layer
between high-level 'network-wide' policy definitions that affect
configuration of the Differentiated Services (diffserv) subsystem and
the instance-specific information that would include such details as
the parameters for all the queues associated with each interface in a
system.  This essentially provides an interface for configuring
differentiated services at a conceptually higher layer than that of
the Differentiated Services MIB.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-snmpconf-diffpolicy-05.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-snmpconf-diffpolicy-05.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-snmpconf-diffpolicy-05.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:	<20020619122614.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-snmpconf-diffpolicy-05.txt

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

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

--OtherAccess--

--NextPart--




From owner-snmpconf@seymour39.snmp.com  Thu Jun 20 15:20:28 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11014
	for <snmpconf-archive@odin.ietf.org>; Thu, 20 Jun 2002 15:20:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id PAA22995
	for snmpconf-outgoing; Thu, 20 Jun 2002 15:15:09 -0400 (EDT)
Message-ID: <3D122A52.FCB5F30C@nextbeacon.com>
Date: Thu, 20 Jun 2002 12:17:38 -0700
From: Steve Waldbusser <waldbusser@nextbeacon.com>
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: snmpconf@snmp.com
Subject: Re: snmpconf advancement
References: <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.co
	 m> <7290503.1024552014@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 7bit


I may be interested in collaborating with others on an open-source
implementation.

My game plan would be:
1. Start with the open source Javascript interpreter
2. Write the function library (this is quick and will demonstrate it is only a
small memory footprint)
3. Write the MIB code

At this point you have a running PM MIB mid-level manager/self-manager which is
probably too big to be embedded because of #1 which I presume would be large
(i.e. it isn't subsetted nor written with an embedded system in mind). But it
would be fine for a mid-level manager and for getting some experience. The next
two steps are:

A. Add a CLI function library
B. Write a PolicyScript interpreter from scratch to make it small. I think that
60K-80K is realistic.

The order of implementing A and B is subject to debate but I think that we'd
find it more interesting to do A first because this is just a toy without
access to controllable objects and SNMP doesn't hold a candle to CLI yet.

Anyone else interested?


Steve



Harrie Hazewinkel wrote:

> --On Wednesday, June 19, 2002 11:24 AM -0400 "Harrington, David"
> <dbh@enterasys.com> wrote:
> >
> > I would also like to personally encourage open source developers to
> > produce a reference implementation, probably as a mid-level manager that
> > translates snmpconf scripts into mib-specific SNMP commands, so operators
> > can determine whether the language is sufficiently easy to use, and the
> > CPU overhead can be measured.
>
> Speaking as someone who works a lot with open-source. An open-source
> implementation gets done by two groups;
>    1) poeple doing it as study or hobby and
>    2) poeple who can do it because there employer supports it.
>
> So is Enterasys willing to sponsor such an effort?? Or others??
>
> cheers,
> Harrie



From owner-snmpconf@seymour39.snmp.com  Thu Jun 20 16:08:44 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA11774
	for <snmpconf-archive@odin.ietf.org>; Thu, 20 Jun 2002 16:08:44 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id QAA24331
	for snmpconf-outgoing; Thu, 20 Jun 2002 16:02:26 -0400 (EDT)
From: "Bruce Boardman" <bboardman@nwc.com>
To: <snmpconf@snmp.com>
Subject: RE: snmpconf advancement
Date: Thu, 20 Jun 2002 16:04:20 -0400
Organization: Network Computing Magazine
Message-ID: <00fd01c21895$ad6eaae0$1d5ce680@tacdoh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_00FE_01C21874.265D0AE0"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
In-Reply-To: <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.com>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

This is a multi-part message in MIME format.

------=_NextPart_000_00FE_01C21874.265D0AE0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit

 
I'm glad to see this milestone has been reached. I'm interested in
promoting the advancement of network management an I'm hopeful that the
next step will advance the standard to a Proposed status where we'll
find out how useful (or not) SNMPconf is. 
 
Bruce Boardman - Network Management
Network Computing Magazine
c/o Syracuse University
Machinery Hall
Syracuse NY 13244
Lab 315 443-2040 M 516 448-3772
bboardman@nwc.com
 
 

------=_NextPart_000_00FE_01C21874.265D0AE0
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C21874.22ECEA60">
<title>snmpconf advancement</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle18
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
span.GramE
	{mso-style-name:"";
	mso-gram-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I&#8217;m glad to see this =
milestone has
been reached. I&#8217;m interested in promoting the advancement of =
network management
an I&#8217;m hopeful that the next step will advance the standard to a =
Proposed
status where we&#8217;ll find out how useful (or not) <span =
class=3DSpellE>SNMPconf</span>
is. <o:p></o:p></span></font></p>

<div>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'><o:p>&nbsp;</o:p><=
/span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Bruce Boardman - =
Network
Management<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Network Computing =
Magazine<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>c/o =
</span></font><st1:place><st1:PlaceName><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>Syracuse</span></font></st1:PlaceNa=
me><font
 color=3Dnavy><span style=3D'color:navy;mso-no-proof:yes'> =
</span></font><st1:PlaceType><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>University</span></font></st1:Place=
Type></st1:place><font
color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Machinery =
Hall<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><st1:place><st1:City><font size=3D3 color=3Dnavy
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:navy;mso-no-proof:
  yes'>Syracuse</span></font></st1:City><font color=3Dnavy><span
 style=3D'color:navy;mso-no-proof:yes'> </span></font><st1:State><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>NY</span></font></st1:State><font
 color=3Dnavy><span style=3D'color:navy;mso-no-proof:yes'> =
</span></font><st1:PostalCode><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>13244</span></font></st1:PostalCode=
></st1:place><font
color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Lab 315 443-2040 =
M 516
448-3772<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>bboardman@nwc.com<=
o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><span =
style=3D'mso-spacerun:yes'>&nbsp;</span><o:p></o:p></span></font></p>

</div>

</div>

</body>

</html>

------=_NextPart_000_00FE_01C21874.265D0AE0--




From owner-snmpconf@seymour39.snmp.com  Thu Jun 20 17:38:06 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA13530
	for <snmpconf-archive@odin.ietf.org>; Thu, 20 Jun 2002 17:38:05 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id RAA27048
	for snmpconf-outgoing; Thu, 20 Jun 2002 17:34:07 -0400 (EDT)
Message-ID: <10C8636AE359D4119118009027AE998719B46D6B@fmsmsx34.fm.intel.com>
From: "Durham, David" <david.durham@intel.com>
To: "'snmpconf@snmp.com'" <snmpconf@snmp.com>
Subject: RE: snmpconf advancement
Date: Thu, 20 Jun 2002 14:32:43 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C218A2.034928D0"
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

------_=_NextPart_001_01C218A2.034928D0
Content-Type: text/plain;
	charset="iso-8859-1"

Just to be very clear, it has been precisely stated by the IESG with respect
to PIBs that the purpose of Proposed status is not to find out how useful
something is. If the usefulness of the work is in question, then the IESG
would only be consistent by progressing the work to experimental or
informational. 
 
I believe the criteria there was to ask who is implementing, and who is
using it. Demonstrating 3GPP adoption and over half-a-dozen implementations
was not even enough to achieve proposed status in the case of PIBs.
 
-Dave
-----Original Message-----
From: Bruce Boardman [mailto:bboardman@nwc.com]
Sent: Thursday, June 20, 2002 1:04 PM
To: snmpconf@snmp.com
Subject: RE: snmpconf advancement


 
I'm glad to see this milestone has been reached. I'm interested in promoting
the advancement of network management an I'm hopeful that the next step will
advance the standard to a Proposed status where we'll find out how useful
(or not) SNMPconf is. 
 
Bruce Boardman - Network Management
Network Computing Magazine
c/o Syracuse University
Machinery Hall
Syracuse NY 13244
Lab 315 443-2040 M 516 448-3772
bboardman@nwc.com
 
 

------_=_NextPart_001_01C218A2.034928D0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word" xmlns:st1 =3D=20
"urn:schemas-microsoft-com:office:smarttags"><HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<TITLE>snmpconf advancement</TITLE>

<META content=3DWord.Document name=3DProgId>
<META content=3D"MSHTML 5.50.4913.1100" name=3DGENERATOR>
<META content=3D"Microsoft Word 10" name=3DOriginator><LINK=20
href=3D"cid:filelist.xml@01C21874.22ECEA60" =
rel=3DFile-List><o:SmartTagType=20
name=3D"PostalCode"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"State"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"City"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"PlaceType"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"PlaceName"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><o:SmartTagType=20
name=3D"place"=20
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"></o:SmartTag=
Type><!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<STYLE>st1\:* {
	BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in =
1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; =
mso-paper-source: 0; }
P.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
LI.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
DIV.MsoNormal {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-style-parent: ""; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"
}
A:link {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlink {
	COLOR: blue; TEXT-DECORATION: underline; text-underline: single
}
A:visited {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
SPAN.MsoHyperlinkFollowed {
	COLOR: purple; TEXT-DECORATION: underline; text-underline: single
}
P.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
LI.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
DIV.MsoAutoSig {
	FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; =
mso-pagination: widow-orphan; mso-fareast-font-family: "Times New =
Roman"
}
P {
	FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: =
"Times New Roman"; mso-pagination: widow-orphan; =
mso-fareast-font-family: "Times New Roman"; mso-margin-top-alt: auto; =
mso-margin-bottom-alt: auto
}
SPAN.EmailStyle18 {
	COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply; =
mso-style-noshow: yes; mso-ansi-font-size: 10.0pt; mso-bidi-font-size: =
10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; =
mso-bidi-font-family: Arial
}
SPAN.SpellE {
	mso-style-name: ""; mso-spl-e: yes
}
SPAN.GramE {
	mso-style-name: ""; mso-gram-e: yes
}
DIV.Section1 {
	page: Section1
}
</STYLE>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]--></HEAD>
<BODY lang=3DEN-US style=3D"tab-interval: .5in" vLink=3Dpurple =
link=3Dblue>
<DIV><SPAN class=3D228272421-20062002><FONT face=3DArial =
color=3D#0000ff size=3D2>Just=20
to be very clear, it has been precisely stated by the IESG with respect =
to PIBs=20
that the purpose of Proposed status is not to find out how useful =
something is.=20
If the usefulness of the work&nbsp;is in question, then the IESG would =
only be=20
consistent by progressing the work to experimental or informational.=20
</FONT></SPAN></DIV>
<DIV><SPAN class=3D228272421-20062002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D228272421-20062002><FONT face=3DArial =
color=3D#0000ff size=3D2>I=20
believe the criteria there was to ask who is implementing, and who is =
using it.=20
Demonstrating 3GPP adoption and over half-a-dozen implementations was =
not even=20
enough to&nbsp;achieve proposed&nbsp;status in the case of=20
PIBs.</FONT></SPAN></DIV>
<DIV><SPAN class=3D228272421-20062002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT></SPAN>&nbsp;</DIV>
<DIV><SPAN class=3D228272421-20062002><FONT face=3DArial =
color=3D#0000ff=20
size=3D2>-Dave</FONT></SPAN></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
  <DIV class=3DOutlookMessageHeader dir=3Dltr align=3Dleft><FONT =
face=3DTahoma=20
  size=3D2>-----Original Message-----<BR><B>From:</B> Bruce Boardman=20
  [mailto:bboardman@nwc.com]<BR><B>Sent:</B> Thursday, June 20, 2002 =
1:04=20
  PM<BR><B>To:</B> snmpconf@snmp.com<BR><B>Subject:</B> RE: snmpconf=20
  advancement<BR><BR></FONT></DIV>
  <DIV class=3DSection1>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I'm glad =
to see this=20
  milestone has been reached. I'm interested in promoting the =
advancement of=20
  network management an I'm hopeful that the next step will advance the =
standard=20
  to a Proposed status where we'll find out how useful (or not) <SPAN=20
  class=3DSpellE>SNMPconf</SPAN> is. <o:p></o:p></SPAN></FONT></P>
  <DIV>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: =
yes"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: yes">Bruce =
Boardman -=20
  Network Management<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: yes">Network =
Computing=20
  Magazine<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: yes">c/o=20
  </SPAN></FONT><st1:place><st1:PlaceName><FONT color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-no-proof: =
yes">Syracuse</SPAN></FONT></st1:PlaceName><FONT=20
  color=3Dnavy><SPAN style=3D"COLOR: navy; mso-no-proof: yes">=20
  </SPAN></FONT><st1:PlaceType><FONT color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-no-proof: =
yes">University</SPAN></FONT></st1:PlaceType></st1:place><FONT=20
  color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-no-proof: =
yes"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: yes">Machinery=20
  Hall<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><st1:place><st1:City><FONT face=3D"Times New =
Roman"=20
  color=3Dnavy size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: =
yes">Syracuse</SPAN></FONT></st1:City><FONT=20
  color=3Dnavy><SPAN style=3D"COLOR: navy; mso-no-proof: yes">=20
  </SPAN></FONT><st1:State><FONT color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-no-proof: =
yes">NY</SPAN></FONT></st1:State><FONT=20
  color=3Dnavy><SPAN style=3D"COLOR: navy; mso-no-proof: yes">=20
  </SPAN></FONT><st1:PostalCode><FONT color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-no-proof: =
yes">13244</SPAN></FONT></st1:PostalCode></st1:place><FONT=20
  color=3Dnavy><SPAN=20
  style=3D"COLOR: navy; mso-no-proof: =
yes"><o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: yes">Lab 315 =
443-2040 M 516=20
  448-3772<o:p></o:p></SPAN></FONT></P>
  <P class=3DMsoAutoSig><FONT face=3D"Times New Roman" color=3Dnavy =
size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt; COLOR: navy; mso-no-proof: =
yes">bboardman@nwc.com<o:p></o:p></SPAN></FONT></P></DIV>
  <P class=3DMsoNormal><FONT face=3DArial color=3Dnavy size=3D2><SPAN=20
  style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: =
Arial"><o:p>&nbsp;</o:p></SPAN></FONT></P>
  <DIV=20
  style=3D"BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP: =
medium none; PADDING-LEFT: 4pt; PADDING-BOTTOM: 0in; BORDER-LEFT: blue =
1.5pt solid; PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
  <P class=3DMsoNormal><FONT face=3D"Times New Roman" size=3D3><SPAN=20
  style=3D"FONT-SIZE: 12pt"><SPAN=20
  style=3D"mso-spacerun: =
yes">&nbsp;</SPAN><o:p></o:p></SPAN></FONT></P></DIV></DIV></BLOCKQUOTE>=
</BODY></HTML>

------_=_NextPart_001_01C218A2.034928D0--


From owner-snmpconf@seymour39.snmp.com  Fri Jun 21 08:57:08 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10742
	for <snmpconf-archive@odin.ietf.org>; Fri, 21 Jun 2002 08:57:07 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id IAA24968
	for snmpconf-outgoing; Fri, 21 Jun 2002 08:52:15 -0400 (EDT)
From: "Bruce Boardman" <bboardman@nwc.com>
To: <snmpconf@snmp.com>
Subject: RE: snmpconf advancement
Date: Fri, 21 Jun 2002 08:54:17 -0400
Organization: Network Computing Magazine
Message-ID: <001901c21922$c3e51d30$1d5ce680@tacdoh.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_001A_01C21901.3CD37D30"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
Importance: Normal
In-Reply-To: <10C8636AE359D4119118009027AE998719B46D6B@fmsmsx34.fm.intel.com>
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

This is a multi-part message in MIME format.

------=_NextPart_000_001A_01C21901.3CD37D30
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Sorry for pulling the trigger on the wrong words. I'm not questioning
the value of the SNMPconf work to date, rather an interest in seeing it
take the next step towards realizing (or not) a better managed network. 
 
Bruce Boardman - Network Management
Network Computing Magazine
c/o Syracuse University
Machinery Hall
Syracuse NY 13244
Lab 315 443-2040 M 516 448-3772
bboardman@nwc.com
 
-----Original Message-----
From: owner-snmpconf@snmp.com [mailto:owner-snmpconf@snmp.com] On Behalf
Of Durham, David
Sent: Thursday, June 20, 2002 5:33 PM
To: 'snmpconf@snmp.com'
Subject: RE: snmpconf advancement
 
Just to be very clear, it has been precisely stated by the IESG with
respect to PIBs that the purpose of Proposed status is not to find out
how useful something is. If the usefulness of the work is in question,
then the IESG would only be consistent by progressing the work to
experimental or informational. 
 
I believe the criteria there was to ask who is implementing, and who is
using it. Demonstrating 3GPP adoption and over half-a-dozen
implementations was not even enough to achieve proposed status in the
case of PIBs.
 
-Dave
-----Original Message-----
From: Bruce Boardman [mailto:bboardman@nwc.com]
Sent: Thursday, June 20, 2002 1:04 PM
To: snmpconf@snmp.com
Subject: RE: snmpconf advancement
 
I'm glad to see this milestone has been reached. I'm interested in
promoting the advancement of network management an I'm hopeful that the
next step will advance the standard to a Proposed status where we'll
find out how useful (or not) SNMPconf is. 
 
Bruce Boardman - Network Management
Network Computing Magazine
c/o Syracuse University
Machinery Hall
Syracuse NY 13244
Lab 315 443-2040 M 516 448-3772
bboardman@nwc.com
 
 

------=_NextPart_000_001A_01C21901.3CD37D30
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:st1=3D"urn:schemas-microsoft-com:office:smarttags" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">


<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:filelist.xml@01C21901.396E0B10">
<title>snmpconf advancement</title>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"time"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PostalCode"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"date"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"place"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceName"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"PlaceType"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"City"/>
<o:SmartTagType =
namespaceuri=3D"urn:schemas-microsoft-com:office:smarttags"
 name=3D"State"/>
<!--[if gte mso 9]><xml>
 <o:OfficeDocumentSettings>
  <o:DoNotRelyOnCSS/>
 </o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
 <w:WordDocument>
  <w:SpellingState>Clean</w:SpellingState>
  <w:GrammarState>Clean</w:GrammarState>
  <w:DocumentKind>DocumentEmail</w:DocumentKind>
  <w:EnvelopeVis/>
  <w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
 </w:WordDocument>
</xml><![endif]--><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;
	mso-font-charset:0;
	mso-generic-font-family:swiss;
	mso-font-pitch:variable;
	mso-font-signature:553679495 -2147483648 8 0 66047 0;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{mso-style-parent:"";
	margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline;
	text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline;
	text-underline:single;}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
	{margin:0in;
	margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
p
	{mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	mso-pagination:widow-orphan;
	font-size:12.0pt;
	font-family:"Times New Roman";
	mso-fareast-font-family:"Times New Roman";}
span.EmailStyle19
	{mso-style-type:personal;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	mso-style-noshow:yes;
	mso-ansi-font-size:10.0pt;
	mso-bidi-font-size:10.0pt;
	font-family:Arial;
	mso-ascii-font-family:Arial;
	mso-hansi-font-family:Arial;
	mso-bidi-font-family:Arial;
	color:navy;}
span.SpellE
	{mso-style-name:"";
	mso-spl-e:yes;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.25in 1.0in 1.25in;
	mso-header-margin:.5in;
	mso-footer-margin:.5in;
	mso-paper-source:0;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
 /* Style Definitions */=20
 table.MsoNormalTable
	{mso-style-name:"Table Normal";
	mso-tstyle-rowband-size:0;
	mso-tstyle-colband-size:0;
	mso-style-noshow:yes;
	mso-style-parent:"";
	mso-padding-alt:0in 5.4pt 0in 5.4pt;
	mso-para-margin:0in;
	mso-para-margin-bottom:.0001pt;
	mso-pagination:widow-orphan;
	font-size:10.0pt;
	font-family:"Times New Roman";}
</style>
<![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:.5in'>

<div class=3DSection1>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>Sorry for pulling the trigger on =
the wrong
words. I&#8217;m not questioning the value of the <span =
class=3DSpellE>SNMPconf</span>
work to date, rather an interest in seeing it take the next step towards
realizing (or not) a better managed network. =
<o:p></o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Bruce Boardman - =
Network
Management<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Network Computing =
Magazine<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>c/o =
</span></font><st1:place><st1:PlaceName><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>Syracuse</span></font></st1:PlaceNa=
me><font
 color=3Dnavy><span style=3D'color:navy;mso-no-proof:yes'> =
</span></font><st1:PlaceType><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>University</span></font></st1:Place=
Type></st1:place><font
color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Machinery =
Hall<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><st1:place><st1:City><font size=3D3 color=3Dnavy
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:navy;mso-no-proof:
  yes'>Syracuse</span></font></st1:City><font color=3Dnavy><span
 style=3D'color:navy;mso-no-proof:yes'> </span></font><st1:State><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>NY</span></font></st1:State><font
 color=3Dnavy><span style=3D'color:navy;mso-no-proof:yes'> =
</span></font><st1:PostalCode><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>13244</span></font></st1:PostalCode=
></st1:place><font
color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Lab 315 443-2040 =
M 516
448-3772<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>bboardman@nwc.com<=
o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
font-family:Tahoma'>-----Original Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> =
owner-snmpconf@snmp.com
[mailto:owner-snmpconf@snmp.com] <b><span style=3D'font-weight:bold'>On =
Behalf Of
</span></b></span></font><st1:City><st1:place><font size=3D2 =
face=3DTahoma><span
  =
style=3D'font-size:10.0pt;font-family:Tahoma'>Durham</span></font></st1:p=
lace></st1:City><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'>, David<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> =
</span></font><st1:date
Month=3D"6" Day=3D"20" Year=3D"2002"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
 10.0pt;font-family:Tahoma'>Thursday, June 20, =
2002</span></font></st1:date><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> </span></font><st1:time
Hour=3D"17" Minute=3D"33"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
 font-family:Tahoma'>5:33 PM</span></font></st1:time><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'><br>
<b><span style=3D'font-weight:bold'>To:</span></b> =
'snmpconf@snmp.com'<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: snmpconf =
advancement</span></font></p>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><o:p>&nbsp;</o:p></span></font></p>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>Just to be very clear, it has been
precisely stated by the IESG with respect to PIBs that the purpose of =
Proposed
status is not to find out how useful something is. If the usefulness of =
the
work&nbsp;is in question, then the IESG would only be consistent by =
progressing
the work to experimental or informational. </span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>I believe the criteria there was to =
ask
who is implementing, and who is using it. Demonstrating 3GPP adoption =
and over
half-a-dozen implementations was not even enough to&nbsp;achieve
proposed&nbsp;status in the case of PIBs.</span></font><o:p></o:p></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'>&nbsp;<o:p></o:p></span></font></p>

</div>

<div>

<p class=3DMsoNormal><font size=3D2 color=3Dblue face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:blue'>-Dave</span></font><o:p></o:p></p>

</div>

<blockquote style=3D'border:none;border-left:solid blue =
1.5pt;padding:0in 0in 0in 4.0pt;
margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'=
>

<p class=3DMsoNormal style=3D'margin-bottom:12.0pt'><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'>-----Original =
Message-----<br>
<b><span style=3D'font-weight:bold'>From:</span></b> Bruce Boardman
[mailto:bboardman@nwc.com]<br>
<b><span style=3D'font-weight:bold'>Sent:</span></b> =
</span></font><st1:date
Month=3D"6" Day=3D"20" Year=3D"2002"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:
 10.0pt;font-family:Tahoma'>Thursday, June 20, =
2002</span></font></st1:date><font
size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;font-family:Tahoma'> </span></font><st1:time
Hour=3D"13" Minute=3D"4"><font size=3D2 face=3DTahoma><span =
style=3D'font-size:10.0pt;
 font-family:Tahoma'>1:04 PM</span></font></st1:time><font size=3D2 =
face=3DTahoma><span
style=3D'font-size:10.0pt;font-family:Tahoma'><br>
<b><span style=3D'font-weight:bold'>To:</span></b> snmpconf@snmp.com<br>
<b><span style=3D'font-weight:bold'>Subject:</span></b> RE: snmpconf =
advancement</span></font><o:p></o:p></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'>I'm glad to see this milestone has =
been
reached. I'm interested in promoting the advancement of network =
management an
I'm hopeful that the next step will advance the standard to a Proposed =
status
where we'll find out how useful (or not) SNMPconf is. =
<o:p></o:p></span></font></p>

<div>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'><o:p>&nbsp;</o:p><=
/span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Bruce Boardman - =
Network
Management<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Network Computing =
Magazine<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>c/o =
</span></font><st1:place><st1:PlaceName><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>Syracuse</span></font></st1:PlaceNa=
me><font
 color=3Dnavy><span style=3D'color:navy;mso-no-proof:yes'> =
</span></font><st1:PlaceType><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>University</span></font></st1:Place=
Type></st1:place><font
color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Machinery =
Hall<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><st1:place><st1:City><font size=3D3 color=3Dnavy
  face=3D"Times New Roman"><span =
style=3D'font-size:12.0pt;color:navy;mso-no-proof:
  yes'>Syracuse</span></font></st1:City><font color=3Dnavy><span
 style=3D'color:navy;mso-no-proof:yes'> </span></font><st1:State><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>NY</span></font></st1:State><font
 color=3Dnavy><span style=3D'color:navy;mso-no-proof:yes'> =
</span></font><st1:PostalCode><font
  color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'>13244</span></font></st1:PostalCode=
></st1:place><font
color=3Dnavy><span =
style=3D'color:navy;mso-no-proof:yes'><o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>Lab 315 443-2040 =
M 516
448-3772<o:p></o:p></span></font></p>

<p class=3DMsoAutoSig><font size=3D3 color=3Dnavy face=3D"Times New =
Roman"><span
style=3D'font-size:12.0pt;color:navy;mso-no-proof:yes'>bboardman@nwc.com<=
o:p></o:p></span></font></p>

</div>

<p class=3DMsoNormal><font size=3D2 color=3Dnavy face=3DArial><span =
style=3D'font-size:
10.0pt;font-family:Arial;color:navy'><o:p>&nbsp;</o:p></span></font></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in =
0in 4.0pt'>

<p class=3DMsoNormal><font size=3D3 face=3D"Times New Roman"><span =
style=3D'font-size:
12.0pt'><span =
style=3D'mso-spacerun:yes'>&nbsp;</span><o:p></o:p></span></font></p>

</div>

</blockquote>

</div>

</div>

</body>

</html>

------=_NextPart_000_001A_01C21901.3CD37D30--




From owner-snmpconf@seymour39.snmp.com  Fri Jun 21 19:41:29 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA04397
	for <snmpconf-archive@odin.ietf.org>; Fri, 21 Jun 2002 19:41:29 -0400 (EDT)
Received: by seymour39.snmp.com (8.9.3/m.000221) id TAA08848
	for snmpconf-outgoing; Fri, 21 Jun 2002 19:35:35 -0400 (EDT)
Date: Fri, 21 Jun 2002 16:33:12 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <200206212333.QAA09809@dorothy.bmc.com>
To: snmpconf@snmp.com
Subject: Re: snmpconf advancement
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 7bit

Hi -

> Message-ID: <3D122A52.FCB5F30C@nextbeacon.com>
> Date: Thu, 20 Jun 2002 12:17:38 -0700
> From: Steve Waldbusser <waldbusser@nextbeacon.com>
> To: snmpconf@snmp.com
> Subject: Re: snmpconf advancement
> References: <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.co
> 	 m> <7290503.1024552014@localhost>
...
> Anyone else interested?
...

A gentle reminder -
http://www.ietf.org/ietf/IPR/BMC-SNMPCONF.txt

 ------------------------------------------------------
 Randy Presuhn          BMC Software, Inc.  1-3141
 randy_presuhn@bmc.com  2141 North First Street
 Tel: +1 408 546-1006   San José, California 95131  USA
 ------------------------------------------------------
 My opinions and BMC's are independent variables.
 ------------------------------------------------------


From owner-snmpconf@seymour39.snmp.com  Mon Jun 24 07:47:27 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00262
	for <snmpconf-archive@odin.ietf.org>; Mon, 24 Jun 2002 07:47:27 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id HAA14429
	for snmpconf-outgoing; Mon, 24 Jun 2002 07:39:40 -0400 (EDT)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Jon Saperia <saperia@jdscons.com>
To: snmpconf@snmp.com, Randy Presuhn <rpresuhn@dorothy.bmc.com>
Subject: Re: snmpconf advancement and intellectual property.
Date: Mon, 24 Jun 2002 07:40:43 -0400
X-Mailer: KMail [version 1.3.2]
References: <200206212333.QAA09809@dorothy.bmc.com>
In-Reply-To: <200206212333.QAA09809@dorothy.bmc.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <102491874101@mx03.gis.net>
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 8bit

Randy thanks for the reminder. 

I have looked over the sections of 2026 that apply and assume the pointer 
in your note below is the 'notification'. I have asked our ADs to make 
sure I have selected the right paragraph to include in the intellectual 
property section of the Policy Module from 2026 when such claims are made 
- found in section 10.4.

If there are any other such claims, please make sure they are (re)posted 
here.

Thanks
/jon


On Friday 21 June 2002 07:33 pm, Randy Presuhn wrote:
> Hi -
>
> > Message-ID: <3D122A52.FCB5F30C@nextbeacon.com>
> > Date: Thu, 20 Jun 2002 12:17:38 -0700
> > From: Steve Waldbusser <waldbusser@nextbeacon.com>
> > To: snmpconf@snmp.com
> > Subject: Re: snmpconf advancement
> > References:
> > <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.co m>
> > <7290503.1024552014@localhost>
>
> ...
>
> > Anyone else interested?
>
> ...
>
> A gentle reminder -
> http://www.ietf.org/ietf/IPR/BMC-SNMPCONF.txt
>
>  ------------------------------------------------------
>  Randy Presuhn          BMC Software, Inc.  1-3141
>  randy_presuhn@bmc.com  2141 North First Street
>  Tel: +1 408 546-1006   San José, California 95131  USA
>  ------------------------------------------------------
>  My opinions and BMC's are independent variables.
>  ------------------------------------------------------

-- 
Jon Saperia                         
				
saperia@jdscons.com
Phone: 617-744-1079
Fax:   617-249-0874
http://www.jdscons.com/


From owner-snmpconf@seymour39.snmp.com  Mon Jun 24 07:54:10 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01376
	for <snmpconf-archive@odin.ietf.org>; Mon, 24 Jun 2002 07:54:10 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id HAA14601
	for snmpconf-outgoing; Mon, 24 Jun 2002 07:51:05 -0400 (EDT)
Content-Type: text/plain;
  charset="iso-8859-1"
From: Jon Saperia <saperia@jdscons.com>
To: snmpconf@snmp.com, Randy Presuhn <rpresuhn@dorothy.bmc.com>
Subject: Re: snmpconf advancement and intellectual property.
Date: Mon, 24 Jun 2002 07:52:14 -0400
X-Mailer: KMail [version 1.3.2]
References: <200206212333.QAA09809@dorothy.bmc.com> <102491874101@mx03.gis.net>
In-Reply-To: <102491874101@mx03.gis.net>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Message-ID: <102491943201@mx03.gis.net>
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 8bit

I have been informed that people with claims should send the claim to the  
iesg-secretary@ietf.org so that they can be properly recorded.  There is a 
web page that lists all such claims and is found at:

	
   http://www.ietf.org/ipr.html

Note that the BMC claim is already posted.

Thanks.

/jon

On Monday 24 June 2002 07:40 am, Jon Saperia wrote:
> Randy thanks for the reminder.
>
> I have looked over the sections of 2026 that apply and assume the
> pointer in your note below is the 'notification'. I have asked our ADs
> to make sure I have selected the right paragraph to include in the
> intellectual property section of the Policy Module from 2026 when such
> claims are made - found in section 10.4.
>
> If there are any other such claims, please make sure they are (re)posted
> here.
>
> Thanks
> /jon

-- 
Jon Saperia                         
				
saperia@jdscons.com
Phone: 617-744-1079
Fax:   617-249-0874
http://www.jdscons.com/


From owner-snmpconf@seymour39.snmp.com  Tue Jun 25 06:32:53 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA28494
	for <snmpconf-archive@odin.ietf.org>; Tue, 25 Jun 2002 06:32:53 -0400 (EDT)
Received: by seymour39.snmp.com (8.9.3/m.000221) id GAA17602
	for snmpconf-outgoing; Tue, 25 Jun 2002 06:29:04 -0400 (EDT)
Message-ID: <3D18467A.BD5C97F9@world.std.com>
Date: Tue, 25 Jun 2002 06:31:22 -0400
From: Mark Ellison <ellison@world.std.com>
Organization: Ellison Software Consulting, Inc.
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: snmpconf@snmp.com
Subject: Re: snmpconf advancement
References: <0BF8B32B723ED5119E0B0002A551748B030548EF@corp-exc3.enterasys.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com
Content-Transfer-Encoding: 7bit


Hi,

I've been involved with SNMP implementations since 1990 and have also
been actively involved with SNMP related working groups of the IETF.

When discussing SNMP implementation approaches with developers, I have
cited the BCP produced by this working group.  Many have found the
information contained in the BCP memo highly useful when developing the
SNMP agent component of their products.

In reviewing the PM memo it is clear to me this approach is valid and
useful within both the MLM/dual entity role and within the "higher end"
embedded environment.

I do have two considerations:

(1) The methods in the PM memo build upon the current Internet Standard
Management Framework There is a MIB contained in the PM memo, not a PIB,
so I don't understand why the recent IESG treatment of PIBs applies
here.

(2) RFC 2026 sxn 10.3.2. specifies how the IESG treats intellectual
property rights applicable to standards track documents.  I found no
specification on how the IESG treats IPR applicable to an informational
document.

Considerations notwithstanding, I believe the PM memo should be
considered for a status of Proposed Standard.

Regards,

Mark Ellison
Ellison Software Consulting, Inc.
http://www.scguild.com/Resumes/1321R.html



From owner-snmpconf@seymour39.snmp.com  Thu Jun 27 01:12:58 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23296
	for <snmpconf-archive@odin.ietf.org>; Thu, 27 Jun 2002 01:12:58 -0400 (EDT)
Received: (from majordomo@localhost)
	by seymour39.snmp.com (8.9.3/m.000221) id BAA05877
	for snmpconf-outgoing; Thu, 27 Jun 2002 01:05:23 -0400 (EDT)
Message-Id: <5.1.0.14.2.20020626215950.03476a20@127.0.0.1>
X-Sender: dperkins@127.0.0.1
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 26 Jun 2002 22:03:37 -0700
To: snmpconf@snmp.com
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: snmpconf Comments on BCP-09
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

HI,

Here are some comments on the -09 version of the BCP.
Note, the document has been much improved from the 
-05 version that I last reviewed.

21-june-2002: dtp
Comments on draft-ietf-snmpconf-bcp-09.txt


1) the draft is significantly improved over the last version that
   I reviewed. Note that I did not previously review the
   policy or MIB module.

2) several places in the document are two spaces where a single
   space should be. Need to do a search, to find them and then
   fix the source document.

3) In section 1.2, the document states that the scale of networks
   has increased, but gives no examples. I suggest the following
   replacement text:

    Scale - Networks have more network elements, and the network
    elements are larger and place more demands on the systems
    managing them. For example, consider the typical number and
    speed of interfaces in a modern core network element.
    In 1990, a core router might have 4 network interfaces
    with two being 1.5m bits/sec WAN interfaces and the 
    other two being 10m bits/sec LAN interfaces. In 2002,
    a core route might have 128 1g bits/sec
    LAN interfaces and 64 155m bits/set WAN interfaces.
    A managed metropolitan area network switch can have a port
    density much greater than the port density built into the
    expectations of the management systems that predated it.
    There are  also many more interrelationships within and
    between devices and device functions.

4) The start of the third paragraph, change
    "Management Framework is used successfully" to
    "Management Framework has been used successfully"

5) the definition of "policy-based management (in middle of the
   second para before section 2) doesn't seem too different
   from non-policy-based management. I suggest that at least
   it be modified to include the phrase "rule-based", as
   shown by
    "...is a methodology where rule-based configuration
     information is distributed..."

6a) In section 3.3.1, para 5, second sentence is somewhat confusing,
   since it is telling you what is wrong, but not telling you
   what is correct.
 b) in point 2, the second sentence reads pretty awkwardly.

7) There are extra lines after section 3.3.2 section head before
   the section text.

8) In section 3.3.2, second para, the first sentence should be
   changed to the following:
     Fate sharing of SNMP table data should be explicitly defined
     where possible using the SMI index qualifier AUGMENTS.

9) section 3.4.2, last para, makes a point that DNS names used
   as an index don't create a potential problem. However, unless
   the DNS definitions have been changed, DNS names can be
   upto 128 chars (and maybe international char sets make this
   worse). A DNS name consisting of close to 128 octets used
   as an index would mean that the instance could not be specified.
   This has a higher probability of a problem when two DNS
   names are used in the index.
   
10) section 3.7, this discussion about persistence is not clear,
    and it does not reflect reality. That is, when and how
    "running" configuration is written to persistent storage
    is very dependent on the system. Writing a table with
    a "StorageType" object does not change the storage model
    implemented in a device. Note the setting the value to
    "nonVolatile" does not mean that the row will be written
    to persistent storage before the operation returns. Also,
    a implementation may not allow different rows to have different
    values StorageType.
    This section is important, but also different types of
    implementations have different models for managing
    persistence of configuration data. This needs to be made
    clear.    
     
11) Section 3.10.1, second sentence, the term "context" is used,
    but this sentence does not mean "SNMP contexts". Instead,
    of context, the phrase "SNMP parameters as found in
    table snmpTargetParmsTable from RFC 2573" should be used.
    
12a) Section 3.10.2, first para, first sentence, change "informs"
     to "notifications".
  b) Second para, first sentence, change "InformRequests" to
     "notifications".
  c) Third para should be removed since it is just nonsense.
  d) Fourth para, first sentence, change "of TRAP or InformRequest
     PDUs" to "notifications".

13) Section 3.11, second paragraph, use of term "incumbent"
    is not correct here. Not sure what is the main issue being
    addressed here. In general, a management application must
    understand the semantics of configuration (that is, the
    management app must know what is valid and what is not
    valid configuration settings) and only request configuration
    settings that are believed to be valid and will succeed,
    since the actual failure can not be determined from the
    protocol returned error code.
    
14) Section 3.11, 4th and 5th paras, these look like that
    they need to be combined.
    
15) Section 3.11, last paragraph is completely nonsensical.

16) Section 3.12, last para, reference to RFC 2591 is not correct.
    Note that RFC 2591 (section 6) is incorrect (or at least
    misleading) in its description that implies that VACM
    provides per user access control. VACM does not provide
    per user, but instead provides per group granularity.
    This makes a difference, and renders the last paragraph
    in section 3.12 pretty bogus.

17) Section 3.13.1, fourth para that starts with
    "These informational object types...". Change to
    "Such informational object types...".

18) Section 3.13.1, first para after definition of PortList TC.
    Change the last word of the sentence of the para from "reset"
    to "written".

19a) Section 3.13.2, para 4 implies that only the table
    entLogicalTable from the Entity MIB (RFC 2737) can be
    used to discover values of ContextNames. However, the
    table vacmContextTable from MIB module
    SNMP-VIEW-BASED-ACM-MIB (in RFC 2575) provides a list
    of ContextName values via object vacmContextName.
    While there is not a pointer to items such as
    entLogicalType (found in entLogicalTable), a management app
    can probe each context name value to determine objects
    for the context name value.
  b) Given an update to talk about table vacmContextTable,
     point #2 is incorrect. 
  c) the first para following the two points is nonsense.
     Taken at face value, both points are incorrect.

20a) Section 4.2. This topic has already been covered. It is
    incorrectly in the "agent implementation" section, since
    it has nothing to do with agent design.
  b) in the third para, the phrase "an inform" should be
     replaced by "a notification".

21) Section 5.1.3, first para, says that an agent should
    have the capability of sending a notification "whenever
    a configuration operation is attempted or completed."
    The "attempted" should be dropped.

22) Section 6.2, second para, the phrase "access control"
    should be dropped because "authorization" is already
    specified, and the two are the same.

23a) Section 6.3 should be titled "Authentication Notifications"
     instead of "Authentication Traps".
  b) The term "trap" should be replaced by "notification" in
     all places in the text in this section.

24) Section 6.3, last sentence, repeats often incorrect 
    security warning. That is, it says to turn off generation
    of authenticationFailure notifications because a
    community string can be obtained by sniffing the
    notification (sent using SNMPv1 or SNMPv2c). However,
    this is just silly. First, the community string in
    a notification should be different than that used
    in GETs/SETs/etc. Secondly, if traffic can be sniffed,
    then when a manager does a GET/SET/etc, a community
    string can be obtained from any successful operation.
    Don't repeat urban legends.

25) Section 7.1, first para, the grammar is broken here.

26) Section 7 in whole seems too wordy for what it's saying.

27) Section 8 - example MIB. This MIB is an example of how
    not to write a MIB module! 

28) MIB module, the value of the LAST-UPDATED and REVISION
    clauses don't match. There is at least one REVISION
    clause that is missing (and possibly a second). There
    needs to be a REVISION clause that specifies when the
    module was created. And there may be a REVISION clause
    missing for the last update.

29a) MIB module, TC HvacOperation. This TC to be consistent
     with the descriptor in the MIB module maybe should have
     been named BldgHvacOperation.
  b) It is strange that there is not the enum value 'off(3)'.
     And there might need to be a value of 'fanOnly(4)'.

30) MIB module, object bldgHVACTable. Yes this is a example
     MIB module, but the text of the DESCRIPTION that
     describes to the reader about what is being done
     should be removed and moved to an ASN.1 comment.
     This is similar to showing an example C program
     that contains the line like:
         i++;
     The comment for the line SHOULD NOT be "/* increment i */",
     but should tell why this is being done.
     There are several conventions for specifying what information
     is in the DESCRIPTION clauses for tables and rows. One
     of the best is that the table contains the following
     information:
        1) a general description of the table
        2) a description of the relationship to the number of
           rows in the table with physical or logical items.
        3) a description of the relationship, if any, to
           other tables.
     For rows, the DESCRIPTION contains the following
     information:
        1) a simple description of the table, like
           "A row in the table of ...."
        2) a statement that specifies whether or not rows can
           be created and/or deleted via direct operations
           to the table, and if so, then name of RowStatus
           object (or for pre-RowStatus tables, then a description
           of what is needed for creation/deletion). For
           example, the DESCRIPTION may contain text like
           "Creation and deletion are allowed via SNMP
           operations controled by object xxxRowStatus"

31) MIB module. There are formatting problems that result in
    text of the DESCRIPTION clauses to not be indented
    appropriately.

32a) MIB module, object bldgHVACCfgTemplatePtr. It is not clear
     why RowPointer is used instead of Unsigned32 (cloning the
     data type of the index). The DESCRIPTION text is not
     clear in what it is trying to say.
  b) last paragraph in DESCRIPTION seems bogus
  
33a) MIB module, object bldgHVACFanSpeed. This object assumes
     that the speed can always be determined. It doesn't allow
     for cases when it cannot.      
  b) The last sentence in the DESCRIPTION is redundant with
     the UNITS clause.

34) MIB module, object bldgHVACCurrentTemp. The lower range
    only 0 degrees celcius. So can't get below freezing?
    This is not too realistic.

35) MIB module, object bldgHVACoolOrHeatMins. This is a counter,
    but no discontinuity object specified! Not sure that this
    is a useful object. It would be much more useful to have
    a total coolMins, total heatMins, a startTime, and value
    at startTime.

36) MIB module, object bldHVACOwner. This is completely BOGUS
    and a perversion of the RMON's OwnerStrings.

37) MIB module, object bldHVACStatus. The RowStatus TC has
    requirements of what must be specified in the DESCRIPTION
    clause. These requirements are not met.

38) MIB module. Table and row for TemplateInfo. DESCRIPTION
    clause need to be fixed.
    
39) MIB module. Object bldgHAVACCfgTemplateInfoId. Couldn't
    figure why this is needed.
    
40) MIB module, Object bldgHVACCfgTemplateInfoOwner. DESCRIPTION
    is bogus.

41) MIB module, Object bldgHVACCfgTemplateInfoStatus.
    RowStatus problem.

42) MIB module. Table and Row TemplateTable. Same problem with
    DESCRIPION.

43) MIB module. Object bldgHVACCfgTemplateTable. The DESCRIPTION
    contains "[34]", which is not allowed. A useful name is
    needed for the reference, since once the MIB module
    is extracted from the MIB module, then what "[34]" refers
    to will be lost.

44) MIB module. Objects bldgHVACCfgTemplateDesiredTemp,
    bldgHVACCfgTemplateCoolOrHeat, and
    bldgHVACCfgTemplateInfoPtr. When they can be modified
    MUST be specified in the RowStatus object.

45) MIB module. Objects bldgHVACCfgTemplateOwner and
    bldgHVACCfgTemplateStorage. Same comments as similar objects.

46) Section 8.2, first sentence. Change "sample" to "example".

-- that's all
 
Regards,
/david t. perkins



From owner-snmpconf@seymour39.snmp.com  Thu Jun 27 01:39:33 2002
Received: from seymour39.snmp.com (seymour39.snmp.com [192.147.142.39])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA23843
	for <snmpconf-archive@odin.ietf.org>; Thu, 27 Jun 2002 01:39:33 -0400 (EDT)
Received: by seymour39.snmp.com (8.9.3/m.000221) id BAA07033
	for snmpconf-outgoing; Thu, 27 Jun 2002 01:36:09 -0400 (EDT)
Date: Wed, 26 Jun 2002 22:35:32 -0700
From: Michael MacFaden <mrm@riverstonenet.com>
To: snmpconf@snmp.com
Subject: Re: snmpconf Comments on BCP-09
Message-ID: <20020627053531.GR2245@riverstonenet.com>
References: <5.1.0.14.2.20020626215950.03476a20@127.0.0.1>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5.1.0.14.2.20020626215950.03476a20@127.0.0.1>
User-Agent: Mutt/1.4i
X-Operating-System: GNU/Linux 2.4
Sender: owner-snmpconf@snmp.com
Precedence: bulk
Reply-To: snmpconf@snmp.com

On Wed, Jun 26, 2002 at 10:03:37PM -0700, David T. Perkins wrote:
>Here are some comments on the -09 version of the BCP.
>Note, the document has been much improved from the 
>-05 version that I last reviewed.

Thanks for posting your comments, we'll see what we can do
to improve the sections mentioned.

Mike


