From owner-agentx@dorothy.peer.com  Wed Jul  5 14:42:36 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13885
	for <agentx-archive@odin.ietf.org>; Wed, 5 Jul 2000 14:42:31 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e65IeoW13835;
	Wed, 5 Jul 2000 13:40:50 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA10476
	for agentx-list; Wed, 5 Jul 2000 11:33:39 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA10470;
	Wed, 5 Jul 2000 11:33:35 -0700 (PDT)
Date: Wed, 5 Jul 2000 11:33:35 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200007051833.LAA10470@dorothy.bmc.com>
To: agentx@dorothy.peer.com, disman@dorothy.peer.com
Subject: test of agentx and disman lists
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 8bit


Hi -

this is a test of the agentx and disman WG mailing lists.
please ignore.

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


From owner-agentx@dorothy.peer.com  Mon Jul 10 17:43:58 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA29486
	for <agentx-archive@odin.ietf.org>; Mon, 10 Jul 2000 17:43:57 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6ALgIZ24945;
	Mon, 10 Jul 2000 16:42:19 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA13168
	for agentx-list; Mon, 10 Jul 2000 14:37:19 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA13162
	for agentx@dorothy.bmc.com; Mon, 10 Jul 2000 14:37:16 -0700 (PDT)
Date: Mon, 10 Jul 2000 14:37:16 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200007102137.OAA13162@dorothy.bmc.com>
To: agentx@dorothy.peer.com
Subject: Agentx in Pittsburgh?
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 8bit


Hi -

Will the Agentx working group be having a session at
the IETF meeting in Pittsburgh?

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


From owner-agentx@dorothy.peer.com  Sat Jul 15 16:30:07 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25644
	for <agentx-archive@odin.ietf.org>; Sat, 15 Jul 2000 16:30:07 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6FKPwZ05981;
	Sat, 15 Jul 2000 15:25:58 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA27539
	for agentx-list; Sat, 15 Jul 2000 13:21:04 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA27531
	for agentx@dorothy.bmc.com; Sat, 15 Jul 2000 13:20:59 -0700 (PDT)
Date: Sat, 15 Jul 2000 13:20:59 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200007152020.NAA27531@dorothy.bmc.com>
To: agentx@dorothy.peer.com
Subject: fwd: agentx in Pittsburgh
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hi -

I'm forwarding a message from Bob Natele.  I've added his
new address to the agentx "posters" list, since it seems
appropriate that he should be able to post to this list.  :-)

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

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id IAA27147;
> 	Sat, 15 Jul 2000 08:54:39 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6FFtEZ24195;
> 	Sat, 15 Jul 2000 10:55:14 -0500 (CDT)
> Received: from bnatale.acecomm.com (ppp9.acec.com [38.249.211.62])
> 	by relay1.acec.com (8.9.3/8.9.3) with ESMTP id LAA22409;
> 	Sat, 15 Jul 2000 11:58:03 -0400 (EDT)
> Message-Id: <4.3.2.7.2.20000715115538.025b7da0@plymouth.acec.com>
> X-Sender: bnatale@plymouth.acec.com
> X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
> Date: Sat, 15 Jul 2000 12:00:39 -0400
> To: Randy Presuhn <rpresuhn@dorothy.bmc.com>
> From: Bob Natale <Bob.Natale@acecomm.com>
> Subject: Re: Agentx in Pittsburgh?
> Cc: agentx@dorothy.bmc.com
> In-Reply-To: <200007102137.OAA13162@dorothy.bmc.com>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> 
> At 7/10/2000:05:37 PM, Randy Presuhn wrote:
> 
> Hi Randy,
> 
> >Will the Agentx working group be having a session at
> >the IETF meeting in Pittsburgh?
> 
> Thanks for checking...no AgentX meeting is planned
> for this IETF meeting...I anticipate that we will
> meet either at the following IETF meeting (Minneapolis)
> or, at the latest, the one after that in San Diego,
> for the explicit purpose of assessing whether
> implementation and deployment experience by that
> time warrant either changes tot he specs or
> advancement of AgentX along the standards track
> (from Proposed to Draft).  I have been watching
> the progress of several AgentX implementations
> and am aware of one additional one that will be
> released shortly and it seems as though sufficient
> implementation and deployment experience will be
> available within either of the above time frames
> to warrant a WG meeting.
> 
> If you or anyone else feels that some other course
> of action would be preferable, please say so and
> we can adjust our plans.
> 
> 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.peer.com  Mon Jul 17 14:37:47 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA12589
	for <agentx-archive@odin.ietf.org>; Mon, 17 Jul 2000 14:37:47 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6HIZUZ04097;
	Mon, 17 Jul 2000 13:35:31 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA02468
	for agentx-list; Mon, 17 Jul 2000 11:29:41 -0700 (PDT)
Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA02463
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 11:29:36 -0700 (PDT)
Received: from ec03-hou.bmc.com (ec03-hou.bmc.com [172.20.4.32])
	by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e6HIUKh28777
	for <agentx@dorothy.bmc.com>; Mon, 17 Jul 2000 13:30:20 -0500 (CDT)
Received: by ec03-hou.bmc.com with Internet Mail Service (5.5.2650.21)
	id <3PK2NN1X>; Mon, 17 Jul 2000 13:32:57 -0500
Message-ID: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E8F7@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: "'agentx@dorothy.bmc.com'" <agentx@dorothy.peer.com>
Subject: TDomains
Date: Mon, 17 Jul 2000 13:31:10 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>



	What, if any, are the valid values of TDomain for
agentxConnTransportDomain?

	Also, the AgentxTAddress TC is of size (0..255).  Although it might
be rare, I can imagine Unix domain sockets with longer names.  Is there
therefore, an implied limit on the characters in a Unix domain socket for
AgentX?

	I believe that Unix domain sockets would have
agentxConnTransportAddress values of the form /path/to/socket as opposed to
host:/path/to/socket, since master agents will always open sockets on their
own host - is this technically correct?


	Thanks,

/|/|ike /+yers                                    Test Engineer
                                                      BMC, Inc.
I *AM* reading the manuals - just not as fast as they print 'em!


From owner-agentx@dorothy.peer.com  Mon Jul 17 15:05:45 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23154
	for <agentx-archive@odin.ietf.org>; Mon, 17 Jul 2000 15:05:44 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6HJ4TZ09662;
	Mon, 17 Jul 2000 14:04:29 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA02523
	for agentx-list; Mon, 17 Jul 2000 12:03:02 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA02516
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 12:02:57 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6HJ3UZ09453
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 14:03:30 -0500 (CDT)
Received: from fedex.cisco.com (fedex.cisco.com [171.69.18.27])
	by sj-msg-core-1.cisco.com (8.9.3/8.9.1) with ESMTP id MAA28143;
	Mon, 17 Jul 2000 12:03:54 -0700 (PDT)
Received: from cisco.com (dhcp-171-68-129-192.cisco.com [171.68.129.192])
	by fedex.cisco.com (Mirapoint)
	with ESMTP id ACZ00516 (AUTH lheintz);
	Mon, 17 Jul 2000 12:03:41 -0700 (PDT)
Message-ID: <39735868.F88A15E9@cisco.com>
Date: Mon, 17 Jul 2000 12:03:04 -0700
From: Lauren Heintz <lheintz@cisco.com>
Reply-To: lheintz@cisco.com
Organization: Cisco Systems
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
CC: "'agentx@dorothy.bmc.com'" <agentx@dorothy.peer.com>
Subject: Re: TDomains
References: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E8F7@es01-sjc.bmc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hi Mike,

"Ayers, Mike" wrote:
> 
>         What, if any, are the valid values of TDomain for
> agentxConnTransportDomain?

Whatever TDomains your system supports are valid values in this object.
These TDomain values can be defined in any MIB (standard or
proprietary).
 
>         Also, the AgentxTAddress TC is of size (0..255).  Although it might
> be rare, I can imagine Unix domain sockets with longer names.  Is there
> therefore, an implied limit on the characters in a Unix domain socket for
> AgentX?

Certainly the maximum len you can report with this object is 255 chars.
I would guess that if your implementation encounters an actual socket
with a longer name it should truncate (either to 0 or 255, or whatever
makes sense) or omit the beginning or middle or end of the value??????
Since this TC is supposed to behave according to the TDomain TC in
rfc1903
(except that zero-len values are permitted), this is a question that can
be
addressed in a broader context than the AgentX MIB alone.

Lauren


From owner-agentx@dorothy.peer.com  Mon Jul 17 15:36:16 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03550
	for <agentx-archive@odin.ietf.org>; Mon, 17 Jul 2000 15:36:16 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6HJYkZ15363;
	Mon, 17 Jul 2000 14:34:46 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id MAA02690
	for agentx-list; Mon, 17 Jul 2000 12:33:18 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id MAA02685
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 12:33:14 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6HJXlZ15187
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 14:33:48 -0500 (CDT)
Received: by zmamail03.zma.compaq.com (Postfix, from userid 12345)
	id 779AD4205; Mon, 17 Jul 2000 15:00:44 -0400 (EDT)
Received: from iota.zk3.dec.com (iota.zk3.dec.com [16.140.32.65])
	by zmamail03.zma.compaq.com (Postfix) with ESMTP
	id 51F924125; Mon, 17 Jul 2000 15:00:44 -0400 (EDT)
Received: from zk3.dec.com by iota.zk3.dec.com (8.7.6/UNX 1.7/1.1.20.3/24Apr98-0811AM)
	id PAA0000019367; Mon, 17 Jul 2000 15:00:43 -0400 (EDT)
Message-ID: <3973567F.2D9C0133@zk3.dec.com>
Date: Mon, 17 Jul 2000 14:54:56 -0400
From: Mike Daniele <daniele@zk3.dec.com>
Organization: Compaq 64-bit UNIX networking
X-Mailer: Mozilla 4.73 [en] (X11; I; OSF1 V5.0 alpha)
X-Accept-Language: en
MIME-Version: 1.0
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
Cc: "'agentx@dorothy.bmc.com'" <agentx@dorothy.peer.com>
Subject: Re: TDomains
References: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E8F7@es01-sjc.bmc.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hi Mike,

"Ayers, Mike" wrote:

>         What, if any, are the valid values of TDomain for
> agentxConnTransportDomain?
>

I don't believe there are any such values defined yet.

Since AgentX has transport mappings for TCP and UNIx-domain
sockets, those would be the TDomain/TAddress values we'd need
to define.

We chose not to do so in the AgentX MIB, because we didn't
think it was the right place to define generic TCs for addressing.

What we were hoping, is that the Ops area would sponsor
a "generic TAddress" MIB.  I believe we're getting closer.

See draft-ops-taddress-mib-00.txt.


>
>         Also, the AgentxTAddress TC is of size (0..255).  Although it might
> be rare, I can imagine Unix domain sockets with longer names.  Is there
> therefore, an implied limit on the characters in a Unix domain socket for
> AgentX?
>

Not for AgentX specifically.  The limit already exists with the TAddress
definition in RFC 1903, we just needed to permit 0 length.

Also,  I believe unix domain socket pathnames are restricted by standards
to fewer than 255 characters.  (104?).

>
>         I believe that Unix domain sockets would have
> agentxConnTransportAddress values of the form /path/to/socket as opposed to
> host:/path/to/socket, since master agents will always open sockets on their
> own host - is this technically correct?
>

I believe so.   Good clarification for the draft though!

Regards,
Mike




From owner-agentx@dorothy.peer.com  Mon Jul 17 17:08:43 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA08972
	for <agentx-archive@odin.ietf.org>; Mon, 17 Jul 2000 17:08:43 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6HL6rZ03003;
	Mon, 17 Jul 2000 16:06:54 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA02936
	for agentx-list; Mon, 17 Jul 2000 14:04:00 -0700 (PDT)
Received: from creeper.bmc.com (creeper.bmc.com [172.17.1.166])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA02931
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 14:03:54 -0700 (PDT)
Received: from ec02-hou.bmc.com (EC02-HOU.bmc.com [172.17.0.151])
	by creeper.bmc.com (8.10.2/8.8.6) with ESMTP id e6HL4Xh13950;
	Mon, 17 Jul 2000 16:04:33 -0500 (CDT)
Received: by EC02-HOU.bmc.com with Internet Mail Service (5.5.2650.21)
	id <PD5Q6K3J>; Mon, 17 Jul 2000 16:04:34 -0500
Message-ID: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E8FB@es01-sjc.bmc.com>
From: "Ayers, Mike" <Mike_Ayers@bmc.com>
To: "'Mike Daniele'" <daniele@zk3.dec.com>,
        "Ayers, Mike"
	 <Mike_Ayers@bmc.com>
Cc: "'agentx@dorothy.bmc.com'" <agentx@dorothy.peer.com>
Subject: RE: TDomains
Date: Mon, 17 Jul 2000 15:36:59 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>



> From: Mike Daniele [mailto:daniele@zk3.dec.com]
> Sent: Monday, July 17, 2000 11:55 AM
> >
> >         I believe that Unix domain sockets would have
> > agentxConnTransportAddress values of the form 
> /path/to/socket as opposed to
> > host:/path/to/socket, since master agents will always open 
> sockets on their
> > own host - is this technically correct?
> >
> 
> I believe so.   Good clarification for the draft though!
> 

	Is there an issues list for the MIB to which this can be added?


/|/|ike


From owner-agentx@dorothy.peer.com  Mon Jul 17 17:27:25 2000
Received: from tattler.bmc.com (fw-us-hou-1.bmc.com [198.207.223.250])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA18703
	for <agentx-archive@odin.ietf.org>; Mon, 17 Jul 2000 17:27:25 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6HLPoZ06940;
	Mon, 17 Jul 2000 16:25:50 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id OAA02998
	for agentx-list; Mon, 17 Jul 2000 14:24:20 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id OAA02993
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 14:24:15 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6HLOlZ06671
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 16:24:48 -0500 (CDT)
Received: from bnatale.acecomm.com (bnatale.acec.com [192.152.208.143])
	by relay1.acec.com (8.9.3/8.9.3) with ESMTP id RAA08373;
	Mon, 17 Jul 2000 17:27:41 -0400 (EDT)
Message-Id: <4.3.2.7.2.20000717171853.025d7c70@plymouth.acec.com>
X-Sender: bnatale@plymouth.acec.com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 17 Jul 2000 17:30:32 -0400
To: "Ayers, Mike" <Mike_Ayers@bmc.com>
From: Bob Natale <bnatale@acecomm.com>
Subject: RE: Issues list [was RE: TDomains]
Cc: agentx@dorothy.peer.com
In-Reply-To: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E8FB@es01-sjc.bmc.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>


At 7/17/2000:04:36 PM, Ayers, Mike wrote:

Hi Mike,

>> > I believe that Unix domain sockets would have
>> > agentxConnTransportAddress values of the form 
>> > ath/to/socket as opposed to host:/path/to/socket,
>> > since master agents will always open sockets on
>> > their own host - is this technically correct?
>> 
>> I believe so.   Good clarification for the draft though!
>
>Is there an issues list for the MIB to which this can be added?

It's probably a good time to start one.  After the
Pittsburgh IETF, we'll get to work in earnest on the
next level for AgentX.  This will mean (somewhat)
formal implementation and interoperability reports
and a meeting at either the Minneapolis or San Diego
IETFs to determine advanceability of the specs at
that point.

Let's start by asking Dave Keeney to confirm whether
he can continue to keep the AgentX web site...

   http://www.scguild.com/agentx/

...running and up-to-date (it's already in better
shape that the IETF AgentX web page, which can't
seem to remember the RFCs 2741 and 2742 are outputs
of this WG!...I'll contact the IETF site admin again
right now).  I'll also (hereby) ask Mark Ellison
whether he will continue as the WG's document editor
for the next round.  If both are a go, I'll ask Dave
and Mark to collaborate on keeping the list up-to-date
and posted on the AgentX web site.  Thanks.

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.peer.com  Tue Jul 18 03:01:28 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26513
	for <agentx-archive@odin.ietf.org>; Tue, 18 Jul 2000 03:01:28 -0400 (EDT)
Received: from dorothy.bmc.com (dorothy.bmc.com [192.146.153.65])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6I6wLZ08245;
	Tue, 18 Jul 2000 01:58:21 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id XAA04089
	for agentx-list; Mon, 17 Jul 2000 23:56:26 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id XAA04084
	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 23:56:22 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6I6utZ08047
	for <agentx@dorothy.peer.com>; Tue, 18 Jul 2000 01:56:55 -0500 (CDT)
Received: from hoemlsrv.firewall.lucent.com (localhost [127.0.0.1])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id CAA24642
	for <agentx@dorothy.peer.com>; Tue, 18 Jul 2000 02:57:01 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62])
	by hoemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id CAA24557
	for <agentx@dorothy.peer.com>; Tue, 18 Jul 2000 02:56:56 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2650.21)
	id <303PN92B>; Tue, 18 Jul 2000 08:56:50 +0200
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB083CE3D4@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: "Ayers, Mike" <Mike_Ayers@bmc.com>, Mike Daniele <daniele@zk3.dec.com>
Cc: "'agentx@dorothy.bmc.com'" <agentx@dorothy.peer.com>
Subject: RE: TDomains
Date: Tue, 18 Jul 2000 08:56:43 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>


Comments inline

> ----------
> From: 	Mike Daniele[SMTP:daniele@zk3.dec.com]
> Sent: 	Monday, July 17, 2000 8:54 PM
> To: 	Ayers, Mike
> Cc: 	'agentx@dorothy.bmc.com'
> Subject: 	Re: TDomains
> 
> 
> Hi Mike,
> 
> "Ayers, Mike" wrote:
> 
> >         What, if any, are the valid values of TDomain for
> > agentxConnTransportDomain?
> >
> 
> I don't believe there are any such values defined yet.
> 
> Since AgentX has transport mappings for TCP and UNIx-domain
> sockets, those would be the TDomain/TAddress values we'd need
> to define.
> 
> We chose not to do so in the AgentX MIB, because we didn't
> think it was the right place to define generic TCs for addressing.
> 
> What we were hoping, is that the Ops area would sponsor
> a "generic TAddress" MIB.  I believe we're getting closer.
> 
> See draft-ops-taddress-mib-00.txt.
> 
Yep, and that document can be discussed on the mibs@ops.ietf.org
mailing list

> >
> >         Also, the AgentxTAddress TC is of size (0..255).  Although it
> might
> > be rare, I can imagine Unix domain sockets with longer names.  Is there
> > therefore, an implied limit on the characters in a Unix domain socket
> for
> > AgentX?
> >
> 
> Not for AgentX specifically.  The limit already exists with the TAddress
> definition in RFC 1903, we just needed to permit 0 length.
> 
> Also,  I believe unix domain socket pathnames are restricted by standards
> to fewer than 255 characters.  (104?).
> 
> >
> >         I believe that Unix domain sockets would have
> > agentxConnTransportAddress values of the form /path/to/socket as opposed
> to
> > host:/path/to/socket, since master agents will always open sockets on
> their
> > own host - is this technically correct?
> >
> 
> I believe so.   Good clarification for the draft though!
> 
Pls post any issues w.r.t. generic TAddress TDomain to the mibs@ops.ietf.org
mailing list.

Bert



From owner-agentx@dorothy.peer.com  Thu Jul 20 16:47:56 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA24353
	for <agentx-archive@odin.ietf.org>; Thu, 20 Jul 2000 16:47:55 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6KKfkV11044;
	Thu, 20 Jul 2000 15:41:46 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA12312
	for agentx-list; Thu, 20 Jul 2000 13:34:54 -0700 (PDT)
Received: (from rpresuhn@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id NAA12306
	for agentx@dorothy.bmc.com; Thu, 20 Jul 2000 13:34:50 -0700 (PDT)
Date: Thu, 20 Jul 2000 13:34:50 -0700 (PDT)
From: Randy Presuhn <rpresuhn@dorothy.peer.com>
Message-Id: <200007202034.NAA12306@dorothy.bmc.com>
To: agentx@dorothy.peer.com
Subject: Fwd: RE: Issues list [was RE: TDomains]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hi -

I'm forwarding a non-subscriber post to the agentx list.

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

> Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
> 	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id RAA03532
> 	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 17:13:27 -0700 (PDT)
> Received: from fw-us-hou1.bmc.com (fw-us-hou1.bmc.com [172.17.0.250])
> 	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6I0DxZ02218
> 	for <agentx@dorothy.peer.com>; Mon, 17 Jul 2000 19:13:59 -0500 (CDT)
> Received: from keeney (68.mht.dialup.G4.NET [216.177.2.68])
> 	by boston3.g4.net (8.9.3/8.9.3) with SMTP id UAA00434;
> 	Mon, 17 Jul 2000 20:13:55 -0400 (EDT)
> 	(envelope-from keeney@scguild.com)
> Message-Id: <4.1.20000717201506.04400850@pop-cnh.mv.net>
> X-Sender: keeney-ke@pop-cnh.mv.net
> X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 
> Date: Mon, 17 Jul 2000 20:24:00 -0400
> To: agentx@dorothy.bmc.com
> From: David Keeney <keeney@scguild.com>
> Subject: RE: Issues list [was RE: TDomains]
> In-Reply-To: <4.3.2.7.2.20000717171853.025d7c70@plymouth.acec.com>
> References: <F7E4D46ABD8FD211928E00A0C9EBD1D603E0E8FB@es01-sjc.bmc.com>
> Mime-Version: 1.0
> Content-Type: text/plain; charset="us-ascii"
> 
> BobN,
> 
> 
> >Let's start by asking Dave Keeney to confirm whether
> >he can continue to keep the AgentX web site...
> >
> >   http://www.scguild.com/agentx/
> 
> Yes, the Guild site is willing to continue to sponsor
> the Agentx WG web site.  The page does need some cleanup
> and all input from the agentx list is welcome.
> 
> >
> >...running and up-to-date (it's already in better
> >shape that the IETF AgentX web page, which can't
> >seem to remember the RFCs 2741 and 2742 are outputs
> >of this WG!...I'll contact the IETF site admin again
> >right now).  I'll also (hereby) ask Mark Ellison
> >whether he will continue as the WG's document editor
> >for the next round.  If both are a go, I'll ask Dave
> >and Mark to collaborate on keeping the list up-to-date
> >and posted on the AgentX web site.  Thanks.
> 
> David Keeney
> Software Contractors' Guild
> http://www.scguild.com
> ==================================
> 
> 


From owner-agentx@dorothy.peer.com  Fri Jul 21 14:53:47 2000
Received: from tattler.bmc.com (fw-us-hou-2.bmc.com [198.207.223.251])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA01346
	for <agentx-archive@odin.ietf.org>; Fri, 21 Jul 2000 14:53:45 -0400 (EDT)
Received: from dorothy.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with ESMTP id e6LIoHo15102;
	Fri, 21 Jul 2000 13:50:17 -0500 (CDT)
Received: (from root@localhost)
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) id LAA18254
	for agentx-list; Fri, 21 Jul 2000 11:48:21 -0700 (PDT)
Received: from tattler.bmc.com (tattler.bmc.com [172.17.0.117])
	by dorothy.bmc.com (8.8.6 (PHNE_12836)/8.8.6) with ESMTP id LAA18246
	for <agentx@dorothy.peer.com>; Fri, 21 Jul 2000 11:48:17 -0700 (PDT)
Received: from fw-us-hou1.bmc.com (localhost [127.0.0.1])
	by tattler.bmc.com (8.10.2/8.8.6) with SMTP id e6LImmP14726
	for <agentx@dorothy.peer.com>; Fri, 21 Jul 2000 13:48:48 -0500 (CDT)
Received: from world.std.com (bnh-aa1-05.mv.com [199.125.109.5]) by mercury.mv.net (8.8.8/mem-971025) with ESMTP id OAA19246; Fri, 21 Jul 2000 14:46:18 -0400 (EDT)
Message-ID: <39789A59.E9FB9FDC@world.std.com>
Date: Fri, 21 Jul 2000 14:45:45 -0400
From: Mark Ellison <ellison@world.std.com>
Organization: Ellison Software Consulting, Inc.
X-Mailer: Mozilla 4.5 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bob Natale <bnatale@acecomm.com>
CC: Mark Ellison <ellison@world.std.com>, agentx@dorothy.peer.com,
        David Keeney <keeney@mv.mv.com>
Subject: Re: Issues list [was RE: TDomains]
References: <4.3.2.7.2.20000717171853.025d7c70@plymouth.acec.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-agentx@dorothy.peer.com
Precedence: bulk
List-Id: IETF Agentx Working Group mailing list <agentx@dorothy.bmc.com>
Content-Transfer-Encoding: 7bit


Hi Bob,

I'm happy to continue as WG editor, and will coordinate with Dave Keeney wrt to
maintaining the agentx web site current.

Regards,

Mark

Bob Natale wrote:

> At 7/17/2000:04:36 PM, Ayers, Mike wrote:
>
> Hi Mike,
>
> >> > I believe that Unix domain sockets would have
> >> > agentxConnTransportAddress values of the form
> >> > ath/to/socket as opposed to host:/path/to/socket,
> >> > since master agents will always open sockets on
> >> > their own host - is this technically correct?
> >>
> >> I believe so.   Good clarification for the draft though!
> >
> >Is there an issues list for the MIB to which this can be added?
>
> It's probably a good time to start one.  After the
> Pittsburgh IETF, we'll get to work in earnest on the
> next level for AgentX.  This will mean (somewhat)
> formal implementation and interoperability reports
> and a meeting at either the Minneapolis or San Diego
> IETFs to determine advanceability of the specs at
> that point.
>
> Let's start by asking Dave Keeney to confirm whether
> he can continue to keep the AgentX web site...
>
>    http://www.scguild.com/agentx/
>
> ...running and up-to-date (it's already in better
> shape that the IETF AgentX web page, which can't
> seem to remember the RFCs 2741 and 2742 are outputs
> of this WG!...I'll contact the IETF site admin again
> right now).  I'll also (hereby) ask Mark Ellison
> whether he will continue as the WG's document editor
> for the next round.  If both are a go, I'll ask Dave
> and Mark to collaborate on keeping the list up-to-date
> and posted on the AgentX web site.  Thanks.
>
> 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 -------------



