From owner-agentx@dorothy.peer.com  Tue Sep  7 12:53:27 1999
Received: from tangelo.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12898
	for <agentx-archive@odin.ietf.org>; Tue, 7 Sep 1999 12:53:26 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id LAA21295;
	Tue, 7 Sep 1999 11:49:39 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id JAA14949
	for agentx-list; Tue, 7 Sep 1999 09:40:08 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA14944
	for <agentx@dorothy.bmc.com>; Tue, 7 Sep 1999 09:40:04 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id LAA18675
	for <agentx@dorothy.bmc.com>; Tue, 7 Sep 1999 11:40:06 -0500 (CDT)
Received: from sigma.zk3.dec.com (brysigma.zk3.dec.com [16.141.40.6])
	by mail11.digital.com (8.9.2/8.9.2/WV2.0g) with ESMTP id MAA11790
	for <agentx@dorothy.bmc.com>; Tue, 7 Sep 1999 12:40:02 -0400 (EDT)
Received: from zk3.dec.com by sigma.zk3.dec.com (8.8.8/1.1.20.3/24Apr98-0811AM)
	id MAA0000009490; Tue, 7 Sep 1999 12:40:01 -0400 (EDT)
Message-ID: <37D53FA9.EFCD7C39@zk3.dec.com>
Date: Tue, 07 Sep 1999 12:39:05 -0400
From: Mike Daniele <daniele@zk3.dec.com>
Organization: Compaq 64-bit UNIX networking
X-Mailer: Mozilla 4.61 [en] (X11; I; OSF1 V5.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: AgentX WG <agentx@dorothy.peer.com>
Subject: Bakeoff II- October 99, Nashua, NH
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hello,

Compaq would like to host the second AgentX bakeoff.

When:     Thursday, October 14
Where:    Compaq Computer Corporation, Spitbrook Road Campus
                Nashua, NH

This site is about 40 minutes from Logan and about 30 minutes from
Manchester airport.  The Sheraton Tara hotel is within easy walking
distance, and airport shuttles routinely make the trip there.

We could actually do this just about any time during October,
so the date is [somewhat] subject to change, in an effort to
get as many implementations together as possible.

I'll send out details when I've gotten enough responses to make it
worthwhile.

Regards,
Mike






From owner-agentx@dorothy.peer.com  Tue Sep  7 13:54:03 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA14213
	for <agentx-archive@odin.ietf.org>; Tue, 7 Sep 1999 13:54:02 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id MAA05602;
	Tue, 7 Sep 1999 12:50:58 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id KAA15624
	for agentx-list; Tue, 7 Sep 1999 10:49:08 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA15618
	for <agentx@dorothy.peer.com>; Tue, 7 Sep 1999 10:49:03 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id MAA05127
	for <agentx@dorothy.peer.com>; Tue, 7 Sep 1999 12:49:04 -0500 (CDT)
Received: from [38.249.211.2] (helo=relay1.acecomm.com)
	by relay10.smtp.psi.net with smtp (Exim 1.90 #1)
	id 11OPMX-0005Kl-00; Tue, 7 Sep 1999 13:48:57 -0400
Received: from BNATALE by relay1.acecomm.com (SMI-8.6/SMI-SVR4)
	id NAA25029; Tue, 7 Sep 1999 13:59:06 -0400
Message-Id: <4.2.0.58.19990907134413.00aebd90@nips.acec.com>
X-Sender: natale@nips.acec.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 07 Sep 1999 13:53:52 -0400
To: Mike Daniele <daniele@zk3.dec.com>
From: Bob Natale <bnatale@acecomm.com>
Subject: Re: Bakeoff II- October 99, Nashua, NH
Cc: AgentX WG <agentx@dorothy.peer.com>
In-Reply-To: <37D53FA9.EFCD7C39@zk3.dec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk

At 9/7/99:12:39 PM, Mike Daniele wrote:

Hi Mike,

>Compaq would like to host the second AgentX bakeoff.

Great!  Thanks!

>When:     Thursday, October 14
>Where:    Compaq Computer Corporation, Spitbrook Road Campus
>                 Nashua, NH

That would be fine with me.  *Personally*, it will be easiest
for me if we can start late enough to allow for early am arrival
at Logan and work later into the evening [my Wednesday evenings
are dedicated to a course in Quantitative Techniques in S/W
Engineering this Fall!]--but I offer that only as a data point
for you to consider in light of everyone else's preferences
as they become known.

>This site is about 40 minutes from Logan and about 30 minutes from
>Manchester airport.  The Sheraton Tara hotel is within easy walking
>distance, and airport shuttles routinely make the trip there.

Sounds perfect.

>We could actually do this just about any time during October,
>so the date is [somewhat] subject to change,

Granted...the 14th or later will be best for me [I'm just
starting to get me head above water--bobbing up and down a
bit still, actually--following a hugh backlog that built
up during my Mother's terminal illness over the past 18 months
or so]...but again, I realize you must consider the sum of
everyone's preferences and needs and Compaq's own agenda
for use of its facilities. 

>in an effort to get as many implementations together as possible.


Right...and ACE*COMM's implementation will be (well!) represented
even if the bake-off must take place at a time when I cannot
participate.

>I'll send out details when I've gotten enough responses to make it
>worthwhile.

Thanks, again, for taking on this additional task for the WG.

Cordially,

BobN
------------ ISO 9001 Registered Quality Supplier -----------
Bob Natale         | ACE*COMM              | 301-721-3000 [v]
Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f]
bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com
------------- Free downloads at www.winsnmp.com -------------



From owner-agentx@dorothy.bmc.com  Fri Sep 10 04:33:08 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA26299
	for <agentx-archive@odin.ietf.org>; Fri, 10 Sep 1999 04:33:08 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id DAA29930;
	Fri, 10 Sep 1999 03:26:45 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id BAA04657
	for agentx-list; Fri, 10 Sep 1999 01:21:29 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA04652
	for <agentx@dorothy.bmc.com>; Fri, 10 Sep 1999 01:21:25 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id DAA29410
	for <agentx@dorothy.bmc.com>; Fri, 10 Sep 1999 03:21:30 -0500 (CDT)
Received: from nec.oleane.com  (dyn-1-1-253.Cor.dialup.oleane.fr [62.161.8.253])  by s2.smtp.oleane.net  with SMTP id KAA45557 for <agentx@dorothy.bmc.com>; Fri, 10 Sep 1999 10:21:25 +0200 (CEST)
Message-ID: <014201befb65$a1255680$0201a8c0@nec.oleane.com>
From: "Peter lewis" <peter.lewis@upperside.fr>
To: <agentx@dorothy.peer.com>
Subject: QoS Summit
Date: Fri, 10 Sep 1999 10:22:32 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

QoS Summit: key requirements for advanced applications running on future
networks. Technologies (MPLS, ATM, IntSev/DiffServ, Frame Relay).
Managing, policing, billing, charging QoS. The annual rendez-vous with
top senior specialists.
Paris, France, 16-19 November 1999

Please see details at the following web address:
http://www.upperside.fr/baqos.htm

Sorry to post this message on the list.

Thanks




From owner-agentx@dorothy.bmc.com  Tue Sep 14 12:51:50 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29409
	for <agentx-archive@odin.ietf.org>; Tue, 14 Sep 1999 12:51:49 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id LAA18439;
	Tue, 14 Sep 1999 11:46:57 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id JAA25197
	for agentx-list; Tue, 14 Sep 1999 09:37:30 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA25192
	for <agentx@peer.com>; Tue, 14 Sep 1999 09:37:26 -0700 (PDT)
Received: from ec01-hou.bmc.com (ec01-hou.bmc.com [172.17.0.150])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id LAA16313
	for <agentx@peer.com>; Tue, 14 Sep 1999 11:37:32 -0500 (CDT)
Received: by ec01-hou.bmc.com with Internet Mail Service (5.5.2448.0)
	id <RVS7ZRPY>; Tue, 14 Sep 1999 11:37:28 -0500
Message-ID: <F7E4D46ABD8FD211928E00A0C9EBD1D6AF3F77@ES01-SJC.bmc.com>
From: "Appelbaum, Muriel" <Muriel_Appelbaum@bmc.com>
To: "'agentx@peer.com'" <agentx@peer.com>
Subject: FW:   Non-member submission from [Steve Coya <scoya@ietf.org>  
Date: Tue, 14 Sep 1999 11:37:36 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk



-----Original Message-----
From: owner-agentx@dorothy.bmc.com [mailto:owner-agentx@dorothy.bmc.com]

Sent: Tuesday, September 14, 1999 7:54 AM
To: owner-agentx@dorothy.peer.com
Subject: BOUNCE agentx@dorothy.bmc.com: Non-member submission from
[Steve Coya <scoya@ietf.org>] 


From owner-agentx  Tue Sep 14 07:54:03 1999
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA24665
	for <agentx@dorothy.bmc.com>; Tue, 14 Sep 1999 07:54:03 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id JAA13742
	for <agentx@dorothy.bmc.com>; Tue, 14 Sep 1999 09:54:07 -0500 (CDT)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22517
	for <agentx@dorothy.bmc.com>; Tue, 14 Sep 1999 10:54:00 -0400 (EDT)
Date: Tue, 14 Sep 1999 10:54:18 -0400 (Eastern Daylight Time)
From: Steve Coya <scoya@ietf.org>
To: agentx@dorothy.peer.com
Subject: Last Call: Agent Extensibility (AgentX) Protocol to Proposed Standard (fwd)
Message-ID: <Pine.WNT.3.96.990914105349.-551179B-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


FYI

---------- Forwarded message ----------
From: The IESG <iesg-secretary@ietf.org>
Reply-To: iesg@ietf.org
To: IETF-Announce:  ;
Subject: Last Call: Agent Extensibility (AgentX) Protocol to Proposed
Standard

The IESG has received a request from the SNMP Agent Extensibility Working
Group to consider the following Internet-Draftrs as Proposed Standards: 

o Agent Extensibility (AgentX) Protocol
  <draft-ietf-agentx-rfc-update-01.txt>. This document will obsolete
  RFC2257, currently a Proposed Standard

o Definitions of Managed Objects for Extensible SNMP Agents
  <draft-ietf-agentx-mib-04.txt>.



The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by September 28, 1999.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-agentx-rfc-update-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-agentx-mib-04.txt



From owner-agentx@dorothy.bmc.com  Fri Sep 17 15:14:21 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA28762
	for <agentx-archive@odin.ietf.org>; Fri, 17 Sep 1999 15:14:20 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id NAA22344;
	Fri, 17 Sep 1999 13:56:55 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id LAA02710
	for agentx-list; Fri, 17 Sep 1999 11:45:05 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id LAA02704;
	Fri, 17 Sep 1999 11:45:00 -0700 (PDT)
Date: Fri, 17 Sep 1999 11:45:00 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <199909171845.LAA02704@dorothy.peer.com>
To: agentx@dorothy.peer.com
Subject: Fwd: Last Call: Agent Extensibility (AgentX) Protocol to Proposed  Standard
Cc: scoya@ietf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

Attached is a non-member post to the agentx list.  (Steve's mailing
address has changed, so I've added to the agentx "posters" list so
his messages won't get bounced in the future.)

 ------------------------------------------------------------------------
 Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 ------------------------------------------------------------------------
 Any relationship between my opinions and BMC's is probably coincidental.
 ------------------------------------------------------------------------

Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA24665
	for <agentx@dorothy.bmc.com>; Tue, 14 Sep 1999 07:54:03 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id JAA13742
	for <agentx@dorothy.bmc.com>; Tue, 14 Sep 1999 09:54:07 -0500 (CDT)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us [10.27.5.106])
	by ietf.org (8.9.1a/8.9.1a) with SMTP id KAA22517
	for <agentx@dorothy.bmc.com>; Tue, 14 Sep 1999 10:54:00 -0400 (EDT)
Date: Tue, 14 Sep 1999 10:54:18 -0400 (Eastern Daylight Time)
>From: Steve Coya <scoya@ietf.org>
To: agentx@dorothy.peer.com
Subject: Last Call: Agent Extensibility (AgentX) Protocol to Proposed  Standard (fwd)
Message-ID: <Pine.WNT.3.96.990914105349.-551179B-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


FYI

---------- Forwarded message ----------
>From: The IESG <iesg-secretary@ietf.org>
Reply-To: iesg@ietf.org
To: IETF-Announce:  ;
Subject: Last Call: Agent Extensibility (AgentX) Protocol to Proposed  Standard

The IESG has received a request from the SNMP Agent Extensibility Working
Group to consider the following Internet-Draftrs as Proposed Standards: 

o Agent Extensibility (AgentX) Protocol
  <draft-ietf-agentx-rfc-update-01.txt>. This document will obsolete
  RFC2257, currently a Proposed Standard

o Definitions of Managed Objects for Extensible SNMP Agents
  <draft-ietf-agentx-mib-04.txt>.



The IESG plans to make a decision in the next few weeks, and solicits
final comments on this action.  Please send any comments to the
iesg@ietf.org or ietf@ietf.org mailing lists by September 28, 1999.

Files can be obtained via
http://www.ietf.org/internet-drafts/draft-ietf-agentx-rfc-update-01.txt
http://www.ietf.org/internet-drafts/draft-ietf-agentx-mib-04.txt





From owner-agentx@dorothy.bmc.com  Thu Sep 23 19:04:15 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14004
	for <agentx-archive@odin.ietf.org>; Thu, 23 Sep 1999 19:04:14 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id SAA13319;
	Thu, 23 Sep 1999 18:00:12 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id PAA17064
	for agentx-list; Thu, 23 Sep 1999 15:52:09 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id PAA17056
	for agentx@dorothy.bmc.com; Thu, 23 Sep 1999 15:52:04 -0700 (PDT)
Date: Thu, 23 Sep 1999 15:52:04 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <199909232252.PAA17056@dorothy.peer.com>
To: agentx@dorothy.peer.com
Subject: AgentX implications of rfc 1905 changes
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

(Some of you may have been following the discussion on
 the snmpv3 mailing list on issue 1905-37.  Although many
 of the posts are incorrectly labeled as being for issue
 1905-32, the summary is available for your enjoyment at
 ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1905/issue1905-37.html
)

If these changes (proposed new error code) are adopted, are
corresponding changes to the agentx specifications planned?

In particular, what's the current thinking on how we can modify the
commit protocol to accomodate the "early bailout" implied by the proposed
"complexity limitation" error?  It sounds to me like it would be a new
phase after the initial TestSets have been distributed, but before any
CommitSets are issued.

 ------------------------------------------------------------------------
 Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 ------------------------------------------------------------------------
 Any relationship between my opinions and BMC's is probably coincidental.
 ------------------------------------------------------------------------


From owner-agentx@dorothy.bmc.com  Thu Sep 23 21:47:54 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA15972
	for <agentx-archive@odin.ietf.org>; Thu, 23 Sep 1999 21:47:53 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id UAA05247;
	Thu, 23 Sep 1999 20:45:10 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id SAA18568
	for agentx-list; Thu, 23 Sep 1999 18:41:31 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id SAA18563
	for <agentx@dorothy.peer.com>; Thu, 23 Sep 1999 18:41:27 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id UAA04912
	for <agentx@dorothy.peer.com>; Thu, 23 Sep 1999 20:41:28 -0500 (CDT)
Received: from [10.10.0.210] (helo=cerent.com)
	by mailhost with esmtp (Exim 3.03 #1)
	id 11UKMS-0007hp-00; Thu, 23 Sep 1999 18:41:20 -0700
Message-ID: <37EAD74E.35C324F0@cerent.com>
Date: Thu, 23 Sep 1999 18:43:42 -0700
From: Lauren Heintz <lauren.heintz@cerent.com>
Organization: Cerent Corporation
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Randy Presuhn <rpresuhn@dorothy.peer.com>
CC: agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
References: <199909232252.PAA17056@dorothy.peer.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Perhaps the person who raised the issue could make the first detailed
suggestions on what should change -- specifically, a) how could RFC1905
and the elements of procedure, etc., be rewritten/modified to resolve
the issue, and b), how would the AgentX documents be changed?

I suggest this radical approach because of the obvious lack of certainty
that the issue is even clearly understood -- as evidenced by more than a few
admissions to that fact during the course of this discussion, as well as my
own doubts.

Thanks,
Lauren


Randy Presuhn wrote:
> 
> Hi -
> 
> (Some of you may have been following the discussion on
>  the snmpv3 mailing list on issue 1905-37.  Although many
>  of the posts are incorrectly labeled as being for issue
>  1905-32, the summary is available for your enjoyment at
>  ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1905/issue1905-37.html
> )
> 
> If these changes (proposed new error code) are adopted, are
> corresponding changes to the agentx specifications planned?
> 
> In particular, what's the current thinking on how we can modify the
> commit protocol to accomodate the "early bailout" implied by the proposed
> "complexity limitation" error?  It sounds to me like it would be a new
> phase after the initial TestSets have been distributed, but before any
> CommitSets are issued.
> 
>  ------------------------------------------------------------------------
>  Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
>  Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
>  Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
>  ------------------------------------------------------------------------
>  Any relationship between my opinions and BMC's is probably coincidental.
>  ------------------------------------------------------------------------


From owner-agentx@dorothy.bmc.com  Thu Sep 23 23:03:09 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA17286
	for <agentx-archive@odin.ietf.org>; Thu, 23 Sep 1999 23:03:09 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id WAA14160;
	Thu, 23 Sep 1999 22:00:02 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id TAA18924
	for agentx-list; Thu, 23 Sep 1999 19:56:37 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id TAA18915
	for <agentx@dorothy.peer.com>; Thu, 23 Sep 1999 19:56:33 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id VAA13732
	for <agentx@dorothy.peer.com>; Thu, 23 Sep 1999 21:56:35 -0500 (CDT)
Received: from victory.redbacknetworks.com (victory.redbacknetworks.com [155.53.190.110])
	by ns3.redback.com (8.8.8/8.8.8) with ESMTP id TAA14593;
	Thu, 23 Sep 1999 19:55:32 -0700 (PDT)
Received: from rahul.net (victory.redbacknetworks.com [155.53.190.110]) by victory.redbacknetworks.com (8.8.8/8.6.9) with ESMTP id TAA03109; Thu, 23 Sep 1999 19:54:58 -0700 (PDT)
Message-ID: <37EAE801.DC45F504@rahul.net>
Date: Thu, 23 Sep 1999 19:54:58 -0700
From: Michael Thatcher <thatcher@rahul.net>
X-Mailer: Mozilla 4.61 [en] (X11; U; Linux 2.0.36 i686)
X-Accept-Language: en
MIME-Version: 1.0
To: Randy Presuhn <rpresuhn@dorothy.peer.com>
CC: agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
References: <199909232252.PAA17056@dorothy.peer.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Jez, I understood the proposal as being rejected, mostly on the grounds of
dbh's message.  I.E it is raising an old issue which was not supported in
the past and does not have concensus now.

MikeT
Randy Presuhn wrote:

> Hi -
>
> (Some of you may have been following the discussion on
>  the snmpv3 mailing list on issue 1905-37.  Although many
>  of the posts are incorrectly labeled as being for issue
>  1905-32, the summary is available for your enjoyment at
>  ftp://amethyst.bmc.com/pub/snmpv3/Update567/rfc1905/issue1905-37.html
> )
>
> If these changes (proposed new error code) are adopted, are
> corresponding changes to the agentx specifications planned?
>
> In particular, what's the current thinking on how we can modify the
> commit protocol to accomodate the "early bailout" implied by the proposed
> "complexity limitation" error?  It sounds to me like it would be a new
> phase after the initial TestSets have been distributed, but before any
> CommitSets are issued.
>
>  ------------------------------------------------------------------------
>  Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
>  Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
>  Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
>  ------------------------------------------------------------------------
>  Any relationship between my opinions and BMC's is probably coincidental.
>  ------------------------------------------------------------------------



From owner-agentx@dorothy.bmc.com  Fri Sep 24 04:49:37 1999
Received: from tangelo.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29997
	for <agentx-archive@odin.ietf.org>; Fri, 24 Sep 1999 04:49:36 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id DAA22771;
	Fri, 24 Sep 1999 03:46:14 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id BAA20456
	for agentx-list; Fri, 24 Sep 1999 01:41:29 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id BAA20451
	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 01:41:24 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id DAA21991
	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 03:41:26 -0500 (CDT)
Received: from ribble.server.csc.liv.ac.uk ([138.253.124.242])
	by mailhub2.liv.ac.uk with esmtp (Exim 2.12 #1)
	id 11UQut-0004iN-00
	for agentx@dorothy.peer.com; Fri, 24 Sep 1999 09:41:19 +0100
Received: from daves.staff.csc.liv.ac.uk (root@daves.staff.csc.liv.ac.uk [138.253.125.132])
	by ribble.server.csc.liv.ac.uk (8.8.8/LUCS-DTS-3.0M10) with ESMTP id JAA04585
	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 09:41:19 +0100 (BST)
Received: from daves.staff.csc.liv.ac.uk (daves@localhost [127.0.0.1])
	by daves.staff.csc.liv.ac.uk (8.8.7/LUCS-DTS-3.0D9) with ESMTP id JAA13052
	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 09:44:07 +0100
Message-Id: <199909240844.JAA13052@daves.staff.csc.liv.ac.uk>
X-Mailer: exmh version 2.0.2
To: agentx@dorothy.peer.com
Subject: Error handling
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 24 Sep 1999 09:44:06 +0100
From: Dave Shield <D.T.Shield@csc.liv.ac.uk>
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk

Just a couple of quick requests for clarification as regards AgentX
error handling:

    Section 7.2.5.2:
	The SNMP error index returned appears to be determined by
	the first subagent to return an error, rather than the
	lowest varbind index.  Is this understanding correct?
	   I.e. given two delegated regions (A and B) each containing
	an invalid variable (a and b), and the following scenario:

		SNMP-GET	A.a  B.b
		AgentX-GET	A.a
		AgentX-GET	B.b
		AgentX-Response Error(B.b)
		AgentX-Response Error(A.a)

	Would the resulting SNMP response have error index 2 or 1 ?


    Section 7.2.5.6
	In the case of AgentX-UndoSet failing (other than undoFailed),
	do the SNMP error and index responses refer to the original
	failed TestSet, or the later UndoSet error.
	   My reading of this section seems to imply an error status
	from the UndoSet (probably 'genErr') and an error index from
	the TestSet, which doesn't feel right somehow.

	   Also, this section seems to imply that if all AgentX-UndoSet
	responses are 'noError' (the inverse of the first line of '1'),
	then the resulting SNMP response error index is set to 0 (from
	the final 'Otherwise' clause).
	  Surely this index should refer to the TestSet VarBind that
	originally failed?  Or have I missed something here?

Dave



From owner-agentx@dorothy.bmc.com  Fri Sep 24 15:57:10 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA12081
	for <agentx-archive@odin.ietf.org>; Fri, 24 Sep 1999 15:57:10 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id OAA18397;
	Fri, 24 Sep 1999 14:54:25 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id MAA24301
	for agentx-list; Fri, 24 Sep 1999 12:48:46 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA24296
	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 12:48:42 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id OAA17173
	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 14:48:44 -0500 (CDT)
Received: from iota.zk3.dec.com (iota.zk3.dec.com [16.140.32.65])
	by mail1.digital.com (8.9.2/8.9.2/WV2.0g) with ESMTP id MAA22874;
	Fri, 24 Sep 1999 12:48:35 -0700 (PDT)
Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM)
	id PAA0000021078; Fri, 24 Sep 1999 15:48:33 -0400 (EDT)
Message-ID: <37EBD548.F1690C33@zk3.dec.com>
Date: Fri, 24 Sep 1999 15:47:20 -0400
From: Mike Daniele <daniele@zk3.dec.com>
Organization: Compaq 64-bit UNIX networking
X-Mailer: Mozilla 4.61 [en] (X11; I; OSF1 V5.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Dave Shield <D.T.Shield@csc.liv.ac.uk>
CC: agentx@dorothy.peer.com
Subject: Re: Error handling
References: <199909240844.JAA13052@daves.staff.csc.liv.ac.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Dave Shield wrote:

> Just a couple of quick requests for clarification as regards AgentX
> error handling:
>
>     Section 7.2.5.2:
>         The SNMP error index returned appears to be determined by
>         the first subagent to return an error, rather than the
>         lowest varbind index.  Is this understanding correct?
>            I.e. given two delegated regions (A and B) each containing
>         an invalid variable (a and b), and the following scenario:
>
>                 SNMP-GET        A.a  B.b
>                 AgentX-GET      A.a
>                 AgentX-GET      B.b
>                 AgentX-Response Error(B.b)
>                 AgentX-Response Error(A.a)
>
>         Would the resulting SNMP response have error index 2 or 1 ?
>

Hi,

If response B.b was received first, then probably 2.

There is no ordering defined for processing VarBinds in the SNMP RFCs,
so none is expressed in AgentX.  You may stop when you get the first failure.


>
>     Section 7.2.5.6
>         In the case of AgentX-UndoSet failing (other than undoFailed),
>         do the SNMP error and index responses refer to the original
>         failed TestSet, or the later UndoSet error.
>            My reading of this section seems to imply an error status
>         from the UndoSet (probably 'genErr') and an error index from
>         the TestSet, which doesn't feel right somehow.
>

There aren't any varbinds sent in the agentx commitset or undoset pdus,
so hence the reference to the testset pdu, which had varbinds.

>
>            Also, this section seems to imply that if all AgentX-UndoSet
>         responses are 'noError' (the inverse of the first line of '1'),
>         then the resulting SNMP response error index is set to 0 (from
>         the final 'Otherwise' clause).
>           Surely this index should refer to the TestSet VarBind that
>         originally failed?  Or have I missed something here?
>

Well, if we're processing Undos that means the test phase succeeded
for all varbinds, but a commit failed.  your point seems valid tho, we should
be returning commitfailed, not noError.  I thought this had been changed,
I'll go review my notes.

Thanks for pointing this out.

Mike

>
> Dave



From owner-agentx@dorothy.bmc.com  Fri Sep 24 18:18:22 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13549
	for <agentx-archive@odin.ietf.org>; Fri, 24 Sep 1999 18:18:22 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id RAA18599;
	Fri, 24 Sep 1999 17:13:54 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id PAA00660
	for agentx-list; Fri, 24 Sep 1999 15:11:37 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id PAA00494;
	Fri, 24 Sep 1999 15:11:27 -0700 (PDT)
Date: Fri, 24 Sep 1999 15:11:27 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <199909242211.PAA00494@dorothy.peer.com>
To: agentx@dorothy.peer.com
Subject: Fwd: Review of AgentX protocol
Cc: bill.strahm@intel.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

I'm forwarding a message from Bill Strahm.  I've added him to the
agentx "posters" list so he can post to the list without getting
bounced.

 ------------------------------------------------------------------------
 Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 ------------------------------------------------------------------------
 Any relationship between my opinions and BMC's is probably coincidental.
 ------------------------------------------------------------------------

> Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
> 	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id NAA27212
> 	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 13:59:25 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
> 	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id PAA01884
> 	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 15:59:27 -0500 (CDT)
> Received: from fmsmsx28.FM.INTEL.COM (fmsmsx28.fm.intel.com [132.233.42.28])
> 	by calliope1.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id NAA08076
> 	for <agentx@dorothy.peer.com>; Fri, 24 Sep 1999 13:59:19 -0700 (PDT)
> Received: by fmsmsx28.fm.intel.com with Internet Mail Service (5.5.2448.0)
> 	id <TPWKYGBY>; Fri, 24 Sep 1999 13:59:19 -0700
> Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB201363022@orsmsx41.jf.intel.com>
> From: "Strahm, Bill" <bill.strahm@intel.com>
> To: "'agentx@dorothy.peer.com'" <agentx@dorothy.peer.com>
> Subject: Review of AgentX protocol
> Date: Fri, 24 Sep 1999 13:59:16 -0700
> MIME-Version: 1.0
> X-Mailer: Internet Mail Service (5.5.2448.0)
> Content-Type: text/plain;
> 	charset="iso-8859-1"
> 
> I am in the process of reviewing the AgentX protocol document
> draft-ietf-agentx-rfc-update-01.txt.
> 
> I thought I could have this done by today, but with a product code freeze
> Monday...
> 
> Well I should be able to give it a careful overview over the weekend and get
> back to you on Monday or Tuesday, can I please have an extension until then
> ?
> 
> Bill Strahm
> ______________________________________________
> Bill Strahm        Programming today is a race between
> bill.strahm@       software engineers striving to build
> intel.com          bigger and better idiot-proof programs,
> (503) 264-4632     and the Universe trying to produce
>                    bigger and better idiots.  So far, the
>                    Universe is winning.--Rich Cook
> I am not speaking for Intel.  And Intel rarely speaks for me
> 


From owner-agentx@dorothy.bmc.com  Sat Sep 25 13:30:42 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA02691
	for <agentx-archive@odin.ietf.org>; Sat, 25 Sep 1999 13:30:41 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id MAA11691;
	Sat, 25 Sep 1999 12:27:47 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id KAA28133
	for agentx-list; Sat, 25 Sep 1999 10:22:41 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id KAA28128
	for <agentx@dorothy.peer.com>; Sat, 25 Sep 1999 10:22:35 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id MAA11341
	for <agentx@dorothy.peer.com>; Sat, 25 Sep 1999 12:22:37 -0500 (CDT)
Received: from [38.249.211.2] (helo=relay1.acecomm.com)
	by relay10.smtp.psi.net with smtp (Exim 1.90 #1)
	id 11UvWq-0006RY-00; Sat, 25 Sep 1999 13:22:32 -0400
Received: from natale by relay1.acecomm.com (SMI-8.6/SMI-SVR4)
	id NAA18990; Sat, 25 Sep 1999 13:32:59 -0400
Message-Id: <4.2.0.58.19990925131506.0098f8e0@nips.acec.com>
X-Sender: natale@nips.acec.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Sat, 25 Sep 1999 13:22:04 -0400
To: bill.strahm@intel.com
From: Bob Natale <bnatale@acecomm.com>
Subject: Re: Fwd: Review of AgentX protocol
Cc: agentx@dorothy.peer.com
In-Reply-To: <199909242211.PAA00494@dorothy.peer.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk


> > Date: Fri, 24 Sep 1999 13:59:16 -0700

Hi Bill,

> > I am in the process of reviewing the AgentX protocol document
> > draft-ietf-agentx-rfc-update-01.txt.

Great...thank you.

> > I thought I could have this done by today, but with a product
> > code freeze Monday...

Yes, working in this industry certainly keeps one busy!

> > Well I should be able to give it a careful overview over the
> > weekend and get back to you on Monday or Tuesday, can I please
> > have an extension until then?

I presume you really directed this question to Bert, and I can't
speak for him, but for my part I'd just as well have you take a
couple of extra days with it at a more deliberate pace than have
to rush it through to meet a target date when there are more
pressing things on your mind.

We are still tentatively planning a bake-off later this Fall
and an meeting focusing on implementation reports at the
November IETF.  Getting the specs solidly locked down as soon
as feasible would be a big help re both.

> > Bill Strahm        Programming today is a race between
> > bill.strahm@       software engineers striving to build
> > intel.com          bigger and better idiot-proof programs,
> > (503) 264-4632     and the Universe trying to produce

Cordially,

BobN
------------ ISO 9001 Registered Quality Supplier -----------
Bob Natale         | ACE*COMM              | 301-721-3000 [v]
Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f]
bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com
------------- Free downloads at www.winsnmp.com -------------



From owner-agentx@dorothy.bmc.com  Sun Sep 26 18:09:00 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA09291
	for <agentx-archive@odin.ietf.org>; Sun, 26 Sep 1999 18:09:00 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id RAA28935;
	Sun, 26 Sep 1999 17:06:05 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id OAA05900
	for agentx-list; Sun, 26 Sep 1999 14:58:33 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA05895
	for <agentx@dorothy.peer.com>; Sun, 26 Sep 1999 14:58:24 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id QAA28408
	for <agentx@dorothy.peer.com>; Sun, 26 Sep 1999 16:58:27 -0500 (CDT)
Received: from southrelay03.raleigh.ibm.com (southrelay03.raleigh.ibm.com [9.37.3.210])
	by e2.ny.us.ibm.com (8.9.3/8.9.3) with ESMTP id RAA361676
	for <agentx@dorothy.peer.com>; Sun, 26 Sep 1999 17:57:46 -0400
Received: from BLDVMA.boulder.ibm.com (bldvma.boulder.ibm.com [9.99.64.30])
	by southrelay03.raleigh.ibm.com (8.8.8m2/NCO v2.05) with SMTP id RAA64004
	for <agentx%dorothy.peer.com@relay.us.ibm.com>; Sun, 26 Sep 1999 17:58:13 -0400
Message-Id: <199909262158.RAA64004@southrelay03.raleigh.ibm.com>
Received:  by BLDVMA.boulder.ibm.com (IBM VM SMTP Level 310) via spool with SMTP id 8894 ; Sun, 26 Sep 1999 15:57:14 MDT
Date: Sun, 26 Sep 99 23:58:30 DST
From: "Bert Wijnen" <WIJNEN@vnet.ibm.com>
To: bill.strahm@intel.com
cc: bnatale@acecomm.com, agentx@dorothy.peer.com
Subject: Fwd: Review of AgentX protocol
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk

Ref:  Your note of Sat, 25 Sep 1999 13:22:04 -0400

Subject: Re:   Fwd: Review of AgentX protocol

Bill asks:
> > Well I should be able to give it a careful overview over the
> > weekend and get back to you on Monday or Tuesday, can I please
> > have an extension until then?
>
Sure, we're looking forward to your comments.

Bert


From owner-agentx@dorothy.bmc.com  Mon Sep 27 20:30:02 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18598
	for <agentx-archive@odin.ietf.org>; Mon, 27 Sep 1999 20:30:01 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id TAA12732
	for <agentx-archive@odin.ietf.org>; Mon, 27 Sep 1999 19:30:02 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id QAA24145
	for agentx-list; Mon, 27 Sep 1999 16:15:16 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id QAA24139
	for agentx@dorothy.bmc.com; Mon, 27 Sep 1999 16:15:10 -0700 (PDT)
Date: Mon, 27 Sep 1999 16:15:10 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <199909272315.QAA24139@dorothy.peer.com>
To: agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

> Date: Thu, 23 Sep 1999 19:54:58 -0700
> From: Michael Thatcher <thatcher@rahul.net>
> To: Randy Presuhn <rpresuhn@dorothy.peer.com>
> CC: agentx@dorothy.peer.com
> Subject: Re: AgentX implications of rfc 1905 changes
> References: <199909232252.PAA17056@dorothy.peer.com>
> 
> Jez, I understood the proposal as being rejected, mostly on the grounds of
> dbh's message.  I.E it is raising an old issue which was not supported in
> the past and does not have concensus now.

1905-32 remains closed, after an emphatic pronouncement by the snmpv3
WG chair.

1905-37 was re-opened at the request of several people.  The agentx WG
chair has argued in favor of it.  I think Keith and I have more or less
given up on it, since we seem to be the only ones willing to speak up
against it.

When it is adopted, the agentx protocol will require modification.

What's the plan?

 ------------------------------------------------------------------------
 Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 ------------------------------------------------------------------------
 Any relationship between my opinions and BMC's is probably coincidental.
 ------------------------------------------------------------------------


From owner-agentx@dorothy.bmc.com  Mon Sep 27 20:30:03 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA18600
	for <agentx-archive@odin.ietf.org>; Mon, 27 Sep 1999 20:30:02 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id TAA12740
	for <agentx-archive@odin.ietf.org>; Mon, 27 Sep 1999 19:30:03 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id QAA24184
	for agentx-list; Mon, 27 Sep 1999 16:23:09 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id QAA24178
	for agentx@dorothy.bmc.com; Mon, 27 Sep 1999 16:23:04 -0700 (PDT)
Date: Mon, 27 Sep 1999 16:23:04 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <199909272323.QAA24178@dorothy.peer.com>
To: agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

> Date: Thu, 23 Sep 1999 18:43:42 -0700
> From: Lauren Heintz <lauren.heintz@cerent.com>
> To: Randy Presuhn <rpresuhn@dorothy.peer.com>
> CC: agentx@dorothy.peer.com
> Subject: Re: AgentX implications of rfc 1905 changes
> References: <199909232252.PAA17056@dorothy.peer.com>
> 
> Perhaps the person who raised the issue could make the first detailed
> suggestions on what should change -- specifically, a) how could RFC1905
> and the elements of procedure, etc., be rewritten/modified to resolve
> the issue, and b), how would the AgentX documents be changed?
...

The issue comes from another WG.
Aleksey made a detailed proposal, available at
ftp://ftp.peer.com/pub/snmpv3/Update567/msgs/1999-09-23_084343.html

Since the opposition in the snmpv3 working group appears to have given
up, what is the agentx working group going to do about it?

> I suggest this radical approach because of the obvious lack of certainty
> that the issue is even clearly understood -- as evidenced by more than a few
> admissions to that fact during the course of this discussion, as well as my
> own doubts.
...


I think the summary I mailed out (see below) covers the essentials.
I really hate it, but in the absence of opposition in the snmpv3 WG,
I think we're stuck with it.

> > In particular, what's the current thinking on how we can modify the
> > commit protocol to accomodate the "early bailout" implied by the proposed
> > "complexity limitation" error?  It sounds to me like it would be a new
> > phase after the initial TestSets have been distributed, but before any
> > CommitSets are issued.
...

 ------------------------------------------------------------------------
 Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 ------------------------------------------------------------------------
 Any relationship between my opinions and BMC's is probably coincidental.
 ------------------------------------------------------------------------


From owner-agentx@dorothy.bmc.com  Mon Sep 27 21:26:29 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19772
	for <agentx-archive@odin.ietf.org>; Mon, 27 Sep 1999 21:26:28 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id UAA21739;
	Mon, 27 Sep 1999 20:21:27 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id SAA24630
	for agentx-list; Mon, 27 Sep 1999 18:20:37 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id SAA24625
	for <agentx@dorothy.peer.com>; Mon, 27 Sep 1999 18:20:33 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id UAA21598
	for <agentx@dorothy.peer.com>; Mon, 27 Sep 1999 20:20:35 -0500 (CDT)
Received: from [10.10.0.210] (helo=cerent.com)
	by mailhost with esmtp (Exim 3.03 #1)
	id 11VlwR-0003Vj-00; Mon, 27 Sep 1999 18:20:27 -0700
Message-ID: <37F01853.A93EFA39@cerent.com>
Date: Mon, 27 Sep 1999 18:22:27 -0700
From: Lauren Heintz <lauren.heintz@cerent.com>
Organization: Cerent Corporation
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Randy Presuhn <rpresuhn@dorothy.peer.com>, agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
References: <199909272323.QAA24178@dorothy.peer.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Randy,

Randy Presuhn wrote:

> > > It sounds to me like it would be a new
> > > phase after the initial TestSets have been distributed, but before any
> > > CommitSets are issued.

How would this help?  What would the new phase do for a given subagent that
couldn't be done in the testSet (or I guess, the commitSet) phase?

Also, in order to be able determine if a SET request is too complex or not,
might not AgentX be required to support subagent-to-subagent communication
in some cases?


   ....
   At any stage during the first phase, if it is detected that                |
   the variable binding's name specifies an existing or non-                  |
   existent variable which cannot be processed together with                  |
   other vairables in the PDU due to constrains of particular                 |
   implementation, the the value of the Response-PDU's error-status           |
   field is set to 'requestTooComplex', and the value of its error-index      |
   field is set to the index of failed variable binding. Any SNMPv2           |
   ....


Lastly, if I read the above proposed text correctly (specifically the part
that says "if it is detected"), it seems to suggest that requestTooComplex
is something that might optionally be returned.  If that's the case, then
isn't AgentX fine the way it is currently specified, and maybe the only
change "technically" needed would be to add another of those disclaimer
comments about which kinds of subagents AgentX supports and doesn't support?

Thanks,
Lauren


From owner-agentx@dorothy.bmc.com  Mon Sep 27 22:19:12 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA21304
	for <agentx-archive@odin.ietf.org>; Mon, 27 Sep 1999 22:19:12 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id VAA29592;
	Mon, 27 Sep 1999 21:15:15 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id TAA25396
	for agentx-list; Mon, 27 Sep 1999 19:13:30 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id TAA25390
	for agentx@dorothy.peer.com; Mon, 27 Sep 1999 19:13:25 -0700 (PDT)
Date: Mon, 27 Sep 1999 19:13:25 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.bmc.com>
Message-Id: <199909280213.TAA25390@dorothy.peer.com>
To: agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi -

> Date: Mon, 27 Sep 1999 18:22:27 -0700
> From: Lauren Heintz <lauren.heintz@cerent.com>
> To: Randy Presuhn <rpresuhn@dorothy.peer.com>, agentx@dorothy.peer.com
> Subject: Re: AgentX implications of rfc 1905 changes
> References: <199909272323.QAA24178@dorothy.peer.com>
...
> > > > It sounds to me like it would be a new
> > > > phase after the initial TestSets have been distributed, but before any
> > > > CommitSets are issued.
> 
> How would this help?  What would the new phase do for a given subagent that
> couldn't be done in the testSet (or I guess, the commitSet) phase?

That's one of the problems with the proposed new error code.  You'll
have to argue that point with the folks that are advocating the change.

> Also, in order to be able determine if a SET request is too complex or not,
> might not AgentX be required to support subagent-to-subagent communication
> in some cases?

Ditto.

...
> Lastly, if I read the above proposed text correctly (specifically the part
> that says "if it is detected"), it seems to suggest that requestTooComplex
> is something that might optionally be returned.  

Yes; that's another part of the proposal that I don't like.

>                                                  If that's the case, then
> isn't AgentX fine the way it is currently specified, and maybe the only
> change "technically" needed would be to add another of those disclaimer
> comments about which kinds of subagents AgentX supports and doesn't support?
...

That'd be ok with me, though I don't think that's what the folks
advocating this new error code have in mind.

 ------------------------------------------------------------------------
 Randy Presuhn           rpresuhn@dorothy.bmc.com     http://www.bmc.com/
 Voice: +1 408 616-3100  BMC Software, Inc.           965 Stewart Drive
 Fax:   +1 408 616-3101  Sunnyvale, California 94086  USA
 ------------------------------------------------------------------------
 Any relationship between my opinions and BMC's is probably coincidental.
 ------------------------------------------------------------------------


From owner-agentx@dorothy.bmc.com  Tue Sep 28 05:09:34 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA06310
	for <agentx-archive@odin.ietf.org>; Tue, 28 Sep 1999 05:09:33 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id EAA04052;
	Tue, 28 Sep 1999 04:06:08 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id CAA27392
	for agentx-list; Tue, 28 Sep 1999 02:04:48 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id CAA27383
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 02:04:37 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id EAA03861
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 04:04:36 -0500 (CDT)
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191])
	by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id LAA05741;
	Tue, 28 Sep 1999 11:03:53 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id LAA21779; Tue, 28 Sep 1999 11:03:53 +0200
Date: Tue, 28 Sep 1999 11:03:53 +0200
Message-Id: <199909280903.LAA21779@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: rpresuhn@dorothy.peer.com
CC: agentx@dorothy.peer.com
In-reply-to: <199909272315.QAA24139@dorothy.peer.com> (message from Randy
	Presuhn on Mon, 27 Sep 1999 16:15:10 -0700 (PDT))
Subject: Re: AgentX implications of rfc 1905 changes
References:  <199909272315.QAA24139@dorothy.peer.com>
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk


>>>>> Randy Presuhn writes:

Randy> 1905-37 was re-opened at the request of several people.  The
Randy> agentx WG chair has argued in favor of it.  I think Keith and I
Randy> have more or less given up on it, since we seem to be the only
Randy> ones willing to speak up against it.

Randy> When it is adopted, the agentx protocol will require
Randy> modification.

Randy> What's the plan?

Be patient.

/js

-- 
Juergen Schoenwaelder      Technical University Braunschweig
<schoenw@ibr.cs.tu-bs.de>  Dept. Operating Systems & Computer Networks
Phone: +49 531 391 3289    Bueltenweg 74/75, 38106 Braunschweig, Germany
Fax:   +49 531 391 5936    <URL:http://www.ibr.cs.tu-bs.de/~schoenw/>




From owner-agentx@dorothy.bmc.com  Tue Sep 28 09:44:18 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14865
	for <agentx-archive@odin.ietf.org>; Tue, 28 Sep 1999 09:44:17 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id IAA22112;
	Tue, 28 Sep 1999 08:39:06 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id GAA28734
	for agentx-list; Tue, 28 Sep 1999 06:36:51 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id GAA28726
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 06:36:46 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id IAA21502
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 08:36:48 -0500 (CDT)
Received: from [38.249.211.2] (helo=relay1.acecomm.com)
	by relay10.smtp.psi.net with smtp (Exim 1.90 #1)
	id 11VxQv-0007Ml-00; Tue, 28 Sep 1999 09:36:41 -0400
Received: from natale by relay1.acecomm.com (SMI-8.6/SMI-SVR4)
	id JAA29427; Tue, 28 Sep 1999 09:47:05 -0400
Message-Id: <4.2.0.58.19990928092155.0098bf00@nips.acec.com>
X-Sender: natale@nips.acec.com
X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 
Date: Tue, 28 Sep 1999 09:36:13 -0400
To: Randy Presuhn <rpresuhn@dorothy.peer.com>
From: Bob Natale <bnatale@acecomm.com>
Subject: Re: AgentX implications of rfc 1905 changes
Cc: agentx@dorothy.peer.com
In-Reply-To: <199909272315.QAA24139@dorothy.peer.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk

At 9/27/99:07:15 PM, Randy Presuhn wrote:

Hi Randy,

><...>
>1905-32 remains closed, after an emphatic pronouncement
>by the snmpv3 WG chair.
>
>1905-37 was re-opened at the request of several people.

Actually, I *surmise* that a lot of people associate the two
proposals closely -- albeit neither is technically dependent
upon the other -- and many casual readers (i.e., most of the
SNMPv3 list) probably assume that closing -32 equates to
closing -37 also.  While not technically accurate, that
perception is meaningful all the same.

>The agentx WG chair has argued in favor of it.

I have argued in favor of tilting the scales in favor of
Aleksey on this one, in light of the sum of arguments on
this topic over the years.  As I have stated, I do believe
he has shown more merit to it than those who oppose it
have shown harm or irrelevance in it; however, I do not
feel that promulgating it is essential to SNMP progress,
as we have always relied on pragmatism in the area it
seeks to formalize (as in many others).

>I think Keith and I have more or less given up on it,
>since we seem to be the only ones willing to speak up
>against it.

See above.  Perhaps another (I know you're doing an
awful lot of work on these items!) summary posting on
-37 in light of the definitive closing of -32 would help
in re-gauging consensus on or opposition to this proposed
change...?

>When it is adopted, the agentx protocol will require modification.

Perhaps.  OTOH, we could treat is as an SNMP-level error
that is applied by the master agent based on either:

    - its assessment of the input SNMP request, in light of
      its own runtime constraints and/or known registrations
      and/or special knowledge that a particular implementation
      approach might gather (e.g., MIB awareness);

and/or

    - its assessment of sub-agent responses to the TestSet
      phase.

Regardless...

>What's the plan?

The AgentX docs are currently in the final stages of the AD
and IESG review processes.  They were written based upon a
set of IETF SNMP docs at a point in time which did not include
any action on item 1905-37.  If and when such underlying IETF
SNMP docs change, we'll examine the AgentX specs for any
corresponding necessary changes.

Are there any strong objections to that game plan on this
issue?

Cordially,

BobN
------------ ISO 9001 Registered Quality Supplier -----------
Bob Natale         | ACE*COMM              | 301-721-3000 [v]
Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f]
bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com
------------- Free downloads at www.winsnmp.com -------------



From owner-agentx@dorothy.bmc.com  Tue Sep 28 10:21:59 1999
Received: from tangelo.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA17143
	for <agentx-archive@odin.ietf.org>; Tue, 28 Sep 1999 10:21:59 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id JAA04431;
	Tue, 28 Sep 1999 09:15:48 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id HAA28946
	for agentx-list; Tue, 28 Sep 1999 07:15:00 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA28940;
	Tue, 28 Sep 1999 07:14:56 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id JAA04111;
	Tue, 28 Sep 1999 09:14:59 -0500 (CDT)
Received: from iota.zk3.dec.com (iota.zk3.dec.com [16.140.32.65])
	by mail2.digital.com (8.9.2/8.9.2/WV2.0g) with ESMTP id HAA17732;
	Tue, 28 Sep 1999 07:14:56 -0700 (PDT)
Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM)
	id KAA0000000949; Tue, 28 Sep 1999 10:14:54 -0400 (EDT)
Message-ID: <37F0CD12.522AA68@zk3.dec.com>
Date: Tue, 28 Sep 1999 10:13:38 -0400
From: Mike Daniele <daniele@zk3.dec.com>
Organization: Compaq 64-bit UNIX networking
X-Mailer: Mozilla 4.61 [en] (X11; I; OSF1 V5.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Natale <bnatale@acecomm.com>
CC: Randy Presuhn <rpresuhn@dorothy.peer.com>, agentx@dorothy.peer.com
Subject: Re: AgentX implications of rfc 1905 changes
References: <4.2.0.58.19990928092155.0098bf00@nips.acec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Bob Natale wrote:

<much deleted>

> The AgentX docs are currently in the final stages of the AD
> and IESG review processes.  They were written based upon a
> set of IETF SNMP docs at a point in time which did not include
> any action on item 1905-37.  If and when such underlying IETF
> SNMP docs change, we'll examine the AgentX specs for any
> corresponding necessary changes.
>
> Are there any strong objections to that game plan on this
> issue?
>

None whatsoever.

I find it hard to believe that new set processing semantics and a
new error code will be added to SNMP in our lifetimes, let alone imminently.

Mike

>
> Cordially,
>
> BobN
> ------------ ISO 9001 Registered Quality Supplier -----------
> Bob Natale         | ACE*COMM              | 301-721-3000 [v]
> Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f]
> bnatale@acecomm.com| Gaithersburg MD 20878 | www.acecomm.com
> ------------- Free downloads at www.winsnmp.com -------------



From owner-agentx@dorothy.bmc.com  Tue Sep 28 10:57:46 1999
Received: from tangelo.bmc.com ([198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19430
	for <agentx-archive@odin.ietf.org>; Tue, 28 Sep 1999 10:57:45 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id JAA17083;
	Tue, 28 Sep 1999 09:53:20 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id HAA29158
	for agentx-list; Tue, 28 Sep 1999 07:52:19 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id HAA29153
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 07:52:16 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id JAA16726
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 09:52:18 -0500 (CDT)
Received: [from mothost.mot.com (mothost.mot.com [129.188.137.101]) by motgate.mot.com (MOT-motgate 1.0) with ESMTP id JAA24104 for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 09:52:16 -0500 (CDT)]
Received: [from tt205.tt.comm.mot.com (tt205.tt.comm.mot.com [173.1.2.5]) by mothost.mot.com (MOT-mothost 2.0) with ESMTP id JAA17078 for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 09:52:16 -0500 (CDT)]
Received: from tt.comm.mot.com (tt642.tt.comm.mot.com [173.1.2.192])
	by tt205.tt.comm.mot.com (8.8.5/8.8.5) with ESMTP id JAA16775
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 09:52:16 -0500 (CDT)
Message-ID: <37F0D620.D005E85E@tt.comm.mot.com>
Date: Tue, 28 Sep 1999 09:52:16 -0500
From: Steppen Yi <steppeny@tt.comm.mot.com>
X-Mailer: Mozilla 4.08 [en] (WinNT; I)
MIME-Version: 1.0
To: agentx@dorothy.peer.com
Subject: unsubscribe
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

unsubscribe *



From owner-agentx@dorothy.bmc.com  Tue Sep 28 17:51:42 1999
Received: from tangelo.bmc.com ([198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03433
	for <agentx-archive@odin.ietf.org>; Tue, 28 Sep 1999 17:51:41 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id QAA17704;
	Tue, 28 Sep 1999 16:44:15 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id OAA06280
	for agentx-list; Tue, 28 Sep 1999 14:41:35 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA06275
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 14:41:27 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id QAA17118
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 16:41:30 -0500 (CDT)
Received: from fmsmsx19.fm.intel.com (fmsmsx19.fm.intel.com [132.233.222.210])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id RAA25995;
	Tue, 28 Sep 1999 17:42:06 GMT
Received: by fmsmsx19.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <S3Q0WGQH>; Tue, 28 Sep 1999 14:41:23 -0700
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB201363035@orsmsx41.jf.intel.com>
From: "Strahm, Bill" <bill.strahm@intel.com>
To: agentx@dorothy.peer.com
Cc: "'Bert Wijnen'" <WIJNEN@vnet.ibm.com>,
        "'Bob Natale'"
	 <bnatale@acecomm.com>,
        "'Mike Daniele[daniele@zk3.dec.com]'"
	 <Mike.Daniele[daniele@zk3.dec.com]>
Subject: Review of draft-ietf-agentx-rfc-update-01.txt
Date: Tue, 28 Sep 1999 14:41:21 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk

It looks good, I don't see any real reasons why this can not recycle at
proposed standard.

Now onto some nit picking
Issue 1:
I am very confused at a possible conflict between section 4.1 saying that
the role of the master agent is to  
" - Provides instrumentation for the MIB objects defined in RFC 1907 [17],
and for any MIB objects relevant to any administrative framework it
supports"
and later under 4.2 where it is said
"1) A general architectural division of labor between master agent and
subagent:  The master agent is MIB ignorant and SNMP omniscient, while ... "
(Ok I understand, but a little more clarification might be helpful)

Issue 2:
Page 11
last line is a header include, next page starts off with the definition...
can you  move the last line of page 11 down 
(I did say nits here)

Issue 3:
I would prefer having the AgentX PDU header (Section 6.1) placed before the
AgentX Encodings (Section 5)

Issue 4:
I would like railroad diagrams if possible for many of the Protocol
definitions, especially the SET PDUs to show what is passed and when. ( All
though the number of examples looks to be pretty good )

Issue 5:
page 34
definition of n.vb.
"-snmpTrapOID.0 must be present, as the second varbind if sysUpTime.0 was
supplied, as the first if it was not."
This seems to be cumbersome, of course I don't have any better wording :(

Issue 6:
7.1.4.1 Handling Duplicate and Overlapping Subtrees
An example here please, I think this is going to be an area of error ( real
implementors tell me if this isn't the case )
It also seems that if I register a less specific subtree, even if I have
priority 1, I will be taken over by a subAgent that registers a small subset
of my range...  Is this really the behaviour that we want ?

Issue 7:
7.1.4.2.2 Index Allocation
It doesn't look like AgentX is targetting MIBs where indexes are implemented
as TestandIncr variables.  I could see the need for a subagent to push
control of a TestandIncr variable to the Index Allocation routines... YMMV.
(PS good set of examples after this too)

Issue 8:
7.2.4 Subagent Processing of agentx-TestSet, -CommitSet, -UndoSet,
-CleanupSet-PDUs
Is there a time value that a subagent can use to cleanup after a TestSet is
performed if no other PDUs come from the Master Agent.  Or is this
implementation specific, if I don't see the next step in n amount of time,
ping the master agent and if it is still alive it will get around, if not,
then cleanup anyway ???

Issue 9:
7.2.4.1 Subagent Processing of agentx-TestSet-PDU
There has been a lot of talk on both the SNMPv3 list and here about this
issue.  I am not really certain that it has bottomed out, I will bow to
concensus of the WG to determine this (I am not sure I "FULLY" understand
the agruements Pro/Con)

Issue 10:
9 Security Considerations
Page 75
Why did you list the questions in one order, and answer them in the other
order, I think more than a simple "no" as the answer to question 2 is needed
(I know it is true however)

Also you recomend that the subagents run on the local host, but you have
defined a port (705) to potentially allow remote operation, is this an
inconsistancy ?

Bill
_____________________________________________
Bill Strahm        Programming today is a race between
bill.strahm@      software engineers striving to build
intel.com           bigger and better idiot-proof programs,
(503) 264-4632   and the Universe trying to produce
            bigger and better idiots.  So far, the
                        Universe is winning.--Rich Cook
I am not speaking for Intel.  And Intel rarely speaks for me



From owner-agentx@dorothy.bmc.com  Tue Sep 28 17:58:01 1999
Received: from tangelo.bmc.com ([198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA03544
	for <agentx-archive@odin.ietf.org>; Tue, 28 Sep 1999 17:58:00 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id QAA20334;
	Tue, 28 Sep 1999 16:55:07 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id OAA06379
	for agentx-list; Tue, 28 Sep 1999 14:54:51 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA06374
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 14:54:46 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id QAA20178
	for <agentx@dorothy.peer.com>; Tue, 28 Sep 1999 16:54:49 -0500 (CDT)
Received: from orsmsx29.jf.intel.com (orsmsx29.jf.intel.com [192.168.65.29])
	by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id OAA19239;
	Tue, 28 Sep 1999 14:54:43 -0700 (PDT)
Received: by orsmsx29.jf.intel.com with Internet Mail Service (5.5.2448.0)
	id <TPYTG474>; Tue, 28 Sep 1999 14:54:43 -0700
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB201363036@orsmsx41.jf.intel.com>
From: "Strahm, Bill" <bill.strahm@intel.com>
To: "'agentx@dorothy.peer.com'" <agentx@dorothy.peer.com>
Cc: "'ellison@world.std.com'" <ellison@world.std.com>,
        "'dfrancis@cisco.com'" <dfrancis@cisco.com>
Subject: RE: Review of draft-ietf-agentx-rfc-update-01.txt
Date: Tue, 28 Sep 1999 14:54:41 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="ISO-8859-1"
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk

One more minor issue...

It appears that Mike Daniele's address isn't correct, can this be corrected
?

Bill

______________________________________________
Bill Strahm        Programming today is a race between
bill.strahm@      software engineers striving to build
intel.com           bigger and better idiot-proof programs,
(503) 264-4632   and the Universe trying to produce
            bigger and better idiots.  So far, the
                        Universe is winning.--Rich Cook
I am not speaking for Intel.  And Intel rarely speaks for me


> -----Original Message-----
> From: Strahm, Bill [mailto:bill.strahm@intel.com]
> Sent: Tuesday, September 28, 1999 2:41 PM
> To: agentx@dorothy.peer.com
> Cc: 'Bert Wijnen'; 'Bob Natale'; 'Mike Daniele[daniele@zk3.dec.com]'
> Subject: Review of draft-ietf-agentx-rfc-update-01.txt
> 
> 
> It looks good, I don't see any real reasons why this can not 
> recycle at
> proposed standard.
> 
> Now onto some nit picking
> Issue 1:
> I am very confused at a possible conflict between section 4.1 
> saying that
> the role of the master agent is to  
> " - Provides instrumentation for the MIB objects defined in 
> RFC 1907 [17],
> and for any MIB objects relevant to any administrative framework it
> supports"
> and later under 4.2 where it is said
> "1) A general architectural division of labor between master agent and
> subagent:  The master agent is MIB ignorant and SNMP 
> omniscient, while ... "
> (Ok I understand, but a little more clarification might be helpful)
> 
> Issue 2:
> Page 11
> last line is a header include, next page starts off with the 
> definition...
> can you  move the last line of page 11 down 
> (I did say nits here)
> 
> Issue 3:
> I would prefer having the AgentX PDU header (Section 6.1) 
> placed before the
> AgentX Encodings (Section 5)
> 
> Issue 4:
> I would like railroad diagrams if possible for many of the Protocol
> definitions, especially the SET PDUs to show what is passed 
> and when. ( All
> though the number of examples looks to be pretty good )
> 
> Issue 5:
> page 34
> definition of n.vb.
> "-snmpTrapOID.0 must be present, as the second varbind if 
> sysUpTime.0 was
> supplied, as the first if it was not."
> This seems to be cumbersome, of course I don't have any 
> better wording :(
> 
> Issue 6:
> 7.1.4.1 Handling Duplicate and Overlapping Subtrees
> An example here please, I think this is going to be an area 
> of error ( real
> implementors tell me if this isn't the case )
> It also seems that if I register a less specific subtree, 
> even if I have
> priority 1, I will be taken over by a subAgent that registers 
> a small subset
> of my range...  Is this really the behaviour that we want ?
> 
> Issue 7:
> 7.1.4.2.2 Index Allocation
> It doesn't look like AgentX is targetting MIBs where indexes 
> are implemented
> as TestandIncr variables.  I could see the need for a subagent to push
> control of a TestandIncr variable to the Index Allocation 
> routines... YMMV.
> (PS good set of examples after this too)
> 
> Issue 8:
> 7.2.4 Subagent Processing of agentx-TestSet, -CommitSet, -UndoSet,
> -CleanupSet-PDUs
> Is there a time value that a subagent can use to cleanup 
> after a TestSet is
> performed if no other PDUs come from the Master Agent.  Or is this
> implementation specific, if I don't see the next step in n 
> amount of time,
> ping the master agent and if it is still alive it will get 
> around, if not,
> then cleanup anyway ???
> 
> Issue 9:
> 7.2.4.1 Subagent Processing of agentx-TestSet-PDU
> There has been a lot of talk on both the SNMPv3 list and here 
> about this
> issue.  I am not really certain that it has bottomed out, I 
> will bow to
> concensus of the WG to determine this (I am not sure I 
> "FULLY" understand
> the agruements Pro/Con)
> 
> Issue 10:
> 9 Security Considerations
> Page 75
> Why did you list the questions in one order, and answer them 
> in the other
> order, I think more than a simple "no" as the answer to 
> question 2 is needed
> (I know it is true however)
> 
> Also you recomend that the subagents run on the local host, 
> but you have
> defined a port (705) to potentially allow remote operation, is this an
> inconsistancy ?
> 
> Bill
> _____________________________________________
> Bill Strahm        Programming today is a race between
> bill.strahm@      software engineers striving to build
> intel.com           bigger and better idiot-proof programs,
> (503) 264-4632   and the Universe trying to produce
>             bigger and better idiots.  So far, the
>                         Universe is winning.--Rich Cook
> I am not speaking for Intel.  And Intel rarely speaks for me
> 


From owner-agentx@dorothy.bmc.com  Wed Sep 29 09:48:12 1999
Received: from tangelo.bmc.com ([198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA29383
	for <agentx-archive@odin.ietf.org>; Wed, 29 Sep 1999 09:48:11 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id IAA18620;
	Wed, 29 Sep 1999 08:38:31 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id GAA22717
	for agentx-list; Wed, 29 Sep 1999 06:33:14 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id GAA22712
	for <agentx@dorothy.peer.com>; Wed, 29 Sep 1999 06:33:09 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id IAA17178
	for <agentx@dorothy.peer.com>; Wed, 29 Sep 1999 08:33:12 -0500 (CDT)
Received: by mailext12.compaq.com (Postfix, from userid 60001)
	id 07AA3578DA; Wed, 29 Sep 1999 08:32:18 -0500 (CDT)
Received: from mailext12.compaq.com (localhost [127.0.0.1])
	by mailext12.compaq.com (Postfix) with ESMTP
	id 0539354601; Wed, 29 Sep 1999 08:32:18 -0500 (CDT)
Received: from mailint02.im.hou.compaq.com([not looked up])
        (peer mailint02.compaq.com[207.18.199.35])
        by mailext12.compaq.com with ESMTP
        id rcv004440; Wed, 29 Sep 1999 08:32:13 -0500 (CDT)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 60001)
	id 9A7A3BC4C8; Wed, 29 Sep 1999 08:32:50 -0500 (CDT)
Received: from mail.compaq.com (localhost [127.0.0.1])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP
	id 8EF68B2A43; Wed, 29 Sep 1999 08:32:50 -0500 (CDT)
Received: from iota.zk3.dec.com([not looked up])
        (peer iota.zk3.dec.com[16.140.32.65])
        by mail.compaq.com with ESMTP
        id rcv017816; Wed, 29 Sep 1999 08:32:46 -0500 (CDT)
Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM)
	id JAA0000017720; Wed, 29 Sep 1999 09:32:41 -0400 (EDT)
Message-ID: <37F214AC.C0677982@zk3.dec.com>
Date: Wed, 29 Sep 1999 09:31:24 -0400
From: Mike Daniele <daniele@zk3.dec.com>
Organization: Compaq 64-bit UNIX networking
X-Mailer: Mozilla 4.61 [en] (X11; I; OSF1 V5.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: "Strahm, Bill" <bill.strahm@intel.com>
Cc: agentx@dorothy.peer.com, "'Bert Wijnen'" <WIJNEN@vnet.ibm.com>,
        "'Bob Natale'" <bnatale@acecomm.com>
Subject: Re: Review of draft-ietf-agentx-rfc-update-01.txt
References: <7DAA70BEB463D211AC3E00A0C96B7AB201363035@orsmsx41.jf.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

Hi Bill,

Thank you for a timely review.  Some comments follow.

"Strahm, Bill" wrote:

> It looks good, I don't see any real reasons why this can not recycle at
> proposed standard.
>
> Now onto some nit picking
> Issue 1:
> I am very confused at a possible conflict between section 4.1 saying that
> the role of the master agent is to
> " - Provides instrumentation for the MIB objects defined in RFC 1907 [17],
> and for any MIB objects relevant to any administrative framework it
> supports"
> and later under 4.2 where it is said
> "1) A general architectural division of labor between master agent and
> subagent:  The master agent is MIB ignorant and SNMP omniscient, while ... "
> (Ok I understand, but a little more clarification might be helpful)
>

I personally think what's there is just the right amount of detail.
I don't think we've had much confusion on this point, fyi.
But if you want to suggest some additional text, please do.

>
> Issue 2:
> Page 11
> last line is a header include, next page starts off with the definition...
> can you  move the last line of page 11 down
> (I did say nits here)
>
> Issue 3:
> I would prefer having the AgentX PDU header (Section 6.1) placed before the
> AgentX Encodings (Section 5)
>
> Issue 4:
> I would like railroad diagrams if possible for many of the Protocol
> definitions, especially the SET PDUs to show what is passed and when. ( All
> though the number of examples looks to be pretty good )
>
> Issue 5:
> page 34
> definition of n.vb.
> "-snmpTrapOID.0 must be present, as the second varbind if sysUpTime.0 was
> supplied, as the first if it was not."
> This seems to be cumbersome, of course I don't have any better wording :(
>
> Issue 6:
> 7.1.4.1 Handling Duplicate and Overlapping Subtrees
> An example here please, I think this is going to be an area of error ( real
> implementors tell me if this isn't the case )

There is an example at the end of section 7.2.5.3 that goes into overlapping registrations
and who is authoratative.  This doesn't seem to have been confusing to implementors
from the feedback so far.  "Most specific wins" is common to existing non-AgentX
architectures.

>
> It also seems that if I register a less specific subtree, even if I have
> priority 1, I will be taken over by a subAgent that registers a small subset
> of my range...  Is this really the behaviour that we want ?
>

Yes!

>
> Issue 7:
> 7.1.4.2.2 Index Allocation
> It doesn't look like AgentX is targetting MIBs where indexes are implemented
> as TestandIncr variables.  I could see the need for a subagent to push
> control of a TestandIncr variable to the Index Allocation routines... YMMV.
> (PS good set of examples after this too)
>

Is that even permitted?  (An INDEX object with  read-write or read-create ACCESS?)

This would only be an issue if multiple subagents need to share such a table,
and hence register instances. (A single subagent implementing the table would simply register
the oid of the table.)  Further, since the subagents know what the value of their index objects is,
there would be no need to use AgentX index allocation.

(There would be AgentX registration considerations on the implementation.)

>
> Issue 8:
> 7.2.4 Subagent Processing of agentx-TestSet, -CommitSet, -UndoSet,
> -CleanupSet-PDUs
> Is there a time value that a subagent can use to cleanup after a TestSet is
> performed if no other PDUs come from the Master Agent.  Or is this
> implementation specific, if I don't see the next step in n amount of time,
> ping the master agent and if it is still alive it will get around, if not,
> then cleanup anyway ???
>

Implementation-specific.  Could just do cleanup when you get the next AgentX
message, or ping as you've described.  But with connection-oriented transport under us,
if the master doesn't send anything you're probably going into "loss of link" mode
anyway.

>
> Issue 9:
> 7.2.4.1 Subagent Processing of agentx-TestSet-PDU
> There has been a lot of talk on both the SNMPv3 list and here about this
> issue.  I am not really certain that it has bottomed out, I will bow to
> concensus of the WG to determine this (I am not sure I "FULLY" understand
> the agruements Pro/Con)
>

I think Bob N answered this correctly.  If and when there is a change to 1905
(or anything else that affects us), we'll figure out what to do.

Actually I think Russ just declared this closed.

>
> Issue 10:
> 9 Security Considerations
> Page 75
> Why did you list the questions in one order, and answer them in the other
> order,

For artistic effect.  To highlight that the only control mechanism there is,
is on connection establishment.


> I think more than a simple "no" as the answer to question 2 is needed
> (I know it is true however)
>

Why?  Suggestions?

>
> Also you recomend that the subagents run on the local host, but you have
> defined a port (705) to potentially allow remote operation, is this an
> inconsistancy ?
>

No, some implementations may wish to use TCP,  we simply recommend
against it.  As such, it was the architecturally correct thing to register a port number.

(This is of major help during bakeoffs and remote testing.)

Regards,
Mike

>
> Bill
> _____________________________________________
> Bill Strahm        Programming today is a race between
> bill.strahm@      software engineers striving to build
> intel.com           bigger and better idiot-proof programs,
> (503) 264-4632   and the Universe trying to produce
>             bigger and better idiots.  So far, the
>                         Universe is winning.--Rich Cook
> I am not speaking for Intel.  And Intel rarely speaks for me



From owner-agentx@dorothy.bmc.com  Wed Sep 29 12:09:07 1999
Received: from tangelo.bmc.com ([198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA05749
	for <agentx-archive@odin.ietf.org>; Wed, 29 Sep 1999 12:09:07 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id LAA09066;
	Wed, 29 Sep 1999 11:03:18 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id JAA23601
	for agentx-list; Wed, 29 Sep 1999 09:00:38 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA23596
	for <agentx@dorothy.peer.com>; Wed, 29 Sep 1999 09:00:32 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id LAA08228
	for <agentx@dorothy.peer.com>; Wed, 29 Sep 1999 11:00:35 -0500 (CDT)
Received: from fmsmsx26.fm.intel.com (fmsmsx26.fm.intel.com [132.233.42.26])
	by thalia.fm.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.6 1998/11/24 22:10:56 iwep Exp iwep $) with ESMTP id MAA07736;
	Wed, 29 Sep 1999 12:00:25 GMT
Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2448.0)
	id <S77LGMCM>; Wed, 29 Sep 1999 08:59:29 -0700
Message-ID: <7DAA70BEB463D211AC3E00A0C96B7AB20136303C@orsmsx41.jf.intel.com>
From: "Strahm, Bill" <bill.strahm@intel.com>
To: "'Mike Daniele'" <daniele@zk3.dec.com>,
        "Strahm, Bill"
	 <bill.strahm@intel.com>
Cc: agentx@dorothy.peer.com, "'Bert Wijnen'" <WIJNEN@vnet.ibm.com>,
        "'Bob Natale'" <bnatale@acecomm.com>
Subject: RE: Review of draft-ietf-agentx-rfc-update-01.txt
Date: Wed, 29 Sep 1999 08:59:28 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk

My comments are inline.

The issues that I raised have more to do with only scanning Agent X over the
last few years rather than fully reading it...

I hope that my first comment saying that I thought it was ready was taken as
my evaluation... 

Bill


> -----Original Message-----
> From: Mike Daniele [mailto:daniele@zk3.dec.com]
> Sent: Wednesday, September 29, 1999 6:31 AM
> To: Strahm, Bill
> Cc: agentx@dorothy.peer.com; 'Bert Wijnen'; 'Bob Natale'
> Subject: Re: Review of draft-ietf-agentx-rfc-update-01.txt
> 
> 
> Hi Bill,
> 
> Thank you for a timely review.  Some comments follow.
> 
> "Strahm, Bill" wrote:
> 
> > It looks good, I don't see any real reasons why this can 
> not recycle at
> > proposed standard.
> >
> > Now onto some nit picking
> > Issue 1:
> > I am very confused at a possible conflict between section 
> 4.1 saying that
> > the role of the master agent is to
> > " - Provides instrumentation for the MIB objects defined in 
> RFC 1907 [17],
> > and for any MIB objects relevant to any administrative framework it
> > supports"
> > and later under 4.2 where it is said
> > "1) A general architectural division of labor between 
> master agent and
> > subagent:  The master agent is MIB ignorant and SNMP 
> omniscient, while ... "
> > (Ok I understand, but a little more clarification might be helpful)
> >
> 
> I personally think what's there is just the right amount of detail.
> I don't think we've had much confusion on this point, fyi.
> But if you want to suggest some additional text, please do.
> 
If implementors aren't confused that is fine, I thought it was confusing the
first time I read it, then it makes sense on the second...  No problems with
me here...

> >
> > Issue 2:
> > Page 11
> > last line is a header include, next page starts off with 
> the definition...
> > can you  move the last line of page 11 down
> > (I did say nits here)
> >
> > Issue 3:
> > I would prefer having the AgentX PDU header (Section 6.1) 
> placed before the
> > AgentX Encodings (Section 5)
> >
> > Issue 4:
> > I would like railroad diagrams if possible for many of the Protocol
> > definitions, especially the SET PDUs to show what is passed 
> and when. ( All
> > though the number of examples looks to be pretty good )
> >
> > Issue 5:
> > page 34
> > definition of n.vb.
> > "-snmpTrapOID.0 must be present, as the second varbind if 
> sysUpTime.0 was
> > supplied, as the first if it was not."
> > This seems to be cumbersome, of course I don't have any 
> better wording :(
> >
> > Issue 6:
> > 7.1.4.1 Handling Duplicate and Overlapping Subtrees
> > An example here please, I think this is going to be an area 
> of error ( real
> > implementors tell me if this isn't the case )
> 
> There is an example at the end of section 7.2.5.3 that goes 
> into overlapping registrations
> and who is authoratative.  This doesn't seem to have been 
> confusing to implementors
> from the feedback so far.  "Most specific wins" is common to 
> existing non-AgentX
> architectures.
> 
Works for me... 

> >
> > It also seems that if I register a less specific subtree, 
> even if I have
> > priority 1, I will be taken over by a subAgent that 
> registers a small subset
> > of my range...  Is this really the behaviour that we want ?
> >
> 
> Yes!
> 
Works for me... just wanted to be sure...

> >
> > Issue 7:
> > 7.1.4.2.2 Index Allocation
> > It doesn't look like AgentX is targetting MIBs where 
> indexes are implemented
> > as TestandIncr variables.  I could see the need for a 
> subagent to push
> > control of a TestandIncr variable to the Index Allocation 
> routines... YMMV.
> > (PS good set of examples after this too)
> >
> 
> Is that even permitted?  (An INDEX object with  read-write or 
> read-create ACCESS?)
> 
What I was refering to was an index that was allocated through a TestandIncr
variable.  We use something like this in the RTP MIB to create rows in the
session table.  When you have successfully written to  the TestandIncr
variable a row with that index is "created" for your use in the table.  I
was wondering if there would be a way of getting the master agent to control
this behavior (or not)

> This would only be an issue if multiple subagents need to 
> share such a table,
> and hence register instances. (A single subagent implementing 
> the table would simply register
> the oid of the table.)  Further, since the subagents know 
> what the value of their index objects is,
> there would be no need to use AgentX index allocation.
> 
> (There would be AgentX registration considerations on the 
> implementation.)
> 
> >
> > Issue 8:
> > 7.2.4 Subagent Processing of agentx-TestSet, -CommitSet, -UndoSet,
> > -CleanupSet-PDUs
> > Is there a time value that a subagent can use to cleanup 
> after a TestSet is
> > performed if no other PDUs come from the Master Agent.  Or is this
> > implementation specific, if I don't see the next step in n 
> amount of time,
> > ping the master agent and if it is still alive it will get 
> around, if not,
> > then cleanup anyway ???
> >
> 
> Implementation-specific.  Could just do cleanup when you get 
> the next AgentX
> message, or ping as you've described.  But with 
> connection-oriented transport under us,
> if the master doesn't send anything you're probably going 
> into "loss of link" mode
> anyway.
> 
> >
> > Issue 9:
> > 7.2.4.1 Subagent Processing of agentx-TestSet-PDU
> > There has been a lot of talk on both the SNMPv3 list and 
> here about this
> > issue.  I am not really certain that it has bottomed out, I 
> will bow to
> > concensus of the WG to determine this (I am not sure I 
> "FULLY" understand
> > the agruements Pro/Con)
> >
> 
> I think Bob N answered this correctly.  If and when there is 
> a change to 1905
> (or anything else that affects us), we'll figure out what to do.
> 
> Actually I think Russ just declared this closed.
I saw that...

> 
> >
> > Issue 10:
> > 9 Security Considerations
> > Page 75
> > Why did you list the questions in one order, and answer 
> them in the other
> > order,
> 
> For artistic effect.  To highlight that the only control 
> mechanism there is,
> is on connection establishment.
> 
> 
> > I think more than a simple "no" as the answer to question 2 
> is needed
> > (I know it is true however)
> >
> 
> Why?  Suggestions?
> 
> >
> > Also you recomend that the subagents run on the local host, 
> but you have
> > defined a port (705) to potentially allow remote operation, 
> is this an
> > inconsistancy ?
> >
> 
> No, some implementations may wish to use TCP,  we simply recommend
> against it.  As such, it was the architecturally correct 
> thing to register a port number.
> 
> (This is of major help during bakeoffs and remote testing.)
> 
> Regards,
> Mike
> 
> >
> > Bill
> > _____________________________________________
> > Bill Strahm        Programming today is a race between
> > bill.strahm@      software engineers striving to build
> > intel.com           bigger and better idiot-proof programs,
> > (503) 264-4632   and the Universe trying to produce
> >             bigger and better idiots.  So far, the
> >                         Universe is winning.--Rich Cook
> > I am not speaking for Intel.  And Intel rarely speaks for me
> 



From owner-agentx@dorothy.bmc.com  Wed Sep 29 12:18:16 1999
Received: from tangelo.bmc.com ([198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA06098
	for <agentx-archive@odin.ietf.org>; Wed, 29 Sep 1999 12:18:15 -0400 (EDT)
Received: from dorothy.peer.com (dorothy.bmc.com [192.146.153.65])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with ESMTP id LAA12543;
	Wed, 29 Sep 1999 11:13:48 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) id JAA23703
	for agentx-list; Wed, 29 Sep 1999 09:12:58 -0700 (PDT)
Received: from tangelo.bmc.com (root@tangelo.bmc.com [172.17.7.166])
	by dorothy.peer.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id JAA23698
	for <agentx@dorothy.peer.com>; Wed, 29 Sep 1999 09:12:54 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tangelo.bmc.com (8.8.6 (PHNE_17135)/8.8.6) with SMTP id LAA12310
	for <agentx@dorothy.peer.com>; Wed, 29 Sep 1999 11:12:57 -0500 (CDT)
Received: by mailext12.compaq.com (Postfix, from userid 60001)
	id DE827579D8; Wed, 29 Sep 1999 11:12:02 -0500 (CDT)
Received: from mailext12.compaq.com (localhost [127.0.0.1])
	by mailext12.compaq.com (Postfix) with ESMTP
	id D9A0554601; Wed, 29 Sep 1999 11:12:02 -0500 (CDT)
Received: from mailint02.im.hou.compaq.com([not looked up])
        (peer mailint02.compaq.com[207.18.199.35])
        by mailext12.compaq.com with ESMTP
        id rcv021364; Wed, 29 Sep 1999 11:12:00 -0500 (CDT)
Received: by mailint02.im.hou.compaq.com (Postfix, from userid 60001)
	id 10674BC4D1; Wed, 29 Sep 1999 11:12:51 -0500 (CDT)
Received: from mail.compaq.com (localhost [127.0.0.1])
	by mailint02.im.hou.compaq.com (Postfix) with ESMTP
	id E1B70B2A43; Wed, 29 Sep 1999 11:12:50 -0500 (CDT)
Received: from iota.zk3.dec.com([not looked up])
        (peer iota.zk3.dec.com[16.140.32.65])
        by mail.compaq.com with ESMTP
        id rcv011322; Wed, 29 Sep 1999 11:12:49 -0500 (CDT)
Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM)
	id MAA0000017246; Wed, 29 Sep 1999 12:12:47 -0400 (EDT)
Message-ID: <37F23A31.6DFED0C7@zk3.dec.com>
Date: Wed, 29 Sep 1999 12:11:29 -0400
From: Mike Daniele <daniele@zk3.dec.com>
Organization: Compaq 64-bit UNIX networking
X-Mailer: Mozilla 4.61 [en] (X11; I; OSF1 V5.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: "Strahm, Bill" <bill.strahm@intel.com>
Cc: agentx@dorothy.peer.com, "'Bert Wijnen'" <WIJNEN@vnet.ibm.com>,
        "'Bob Natale'" <bnatale@acecomm.com>
Subject: Re: Review of draft-ietf-agentx-rfc-update-01.txt
References: <7DAA70BEB463D211AC3E00A0C96B7AB20136303C@orsmsx41.jf.intel.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.bmc.com
Precedence: bulk
Content-Transfer-Encoding: 7bit

> I hope that my first comment saying that I thought it was ready was taken as
>my evaluation...

Yes, thanks.

>What I was refering to was an index that was allocated through a TestandIncr
>variable.  We use something like this in the RTP MIB to create rows in the
>session table.  When you have successfully written to  the TestandIncr
>variable a row with that index is "created" for your use in the table.

Ah, I see.

>I was wondering if there would be a way of getting the master agent to control
>this behavior (or not)

No.  In general, the master agent has no idea what instances of what objects you have.
All it knows about are what OIDs you registered, and for which of those
you are authoratative.

Mike



