
Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id XAA02393 for nmrg-outgoing; Fri, 28 Apr 2000 23:47:00 +0200 (MET DST)
Received: from wanderer.hardaker.davis.ca.us (IDENT:root@dns2.hardaker.davis.ca.us [168.150.190.2]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id XAA02388; Fri, 28 Apr 2000 23:46:57 +0200 (MET DST)
Received: (from hardaker@localhost) by wanderer.hardaker.davis.ca.us (8.9.3/8.9.3) id OAA04352; Fri, 28 Apr 2000 14:46:55 -0700
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Cc: wjhardaker@ucdavis.edu, nmrg@ibr.cs.tu-bs.de
Subject: Re: [nmrg] snmp over tcp status
References: <200004281238.OAA03006@henkell.ibr.cs.tu-bs.de> <sd66t29ovo.fsf@wanderer.hardaker.davis.ca.us> <200004281658.SAA12685@henkell.ibr.cs.tu-bs.de>
From: Wes Hardaker <wjhardaker@ucdavis.edu>
X-URL: http://dcas.ucdavis.edu/~hardaker
X-Microsoft: Sucks
Organization: U.C.Davis, Information Technology - D.C.A.S.
X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4
Date: 28 Apr 2000 14:46:55 -0700
In-Reply-To: Juergen Schoenwaelder's message of "Fri, 28 Apr 2000 18:58:39 +0200"
Message-ID: <sd7ldh99v4.fsf@wanderer.hardaker.davis.ca.us>
Lines: 19
User-Agent: Gnus/5.0805 (Gnus v5.8.5) XEmacs/21.2 (Shinjuku)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> On Fri, 28 Apr 2000 18:58:39 +0200, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> said:

Juergen> I agree. But having an experimental RFC is still much better
Juergen> than having no official document at all.

I definitely concur there!

Juergen> And IETF people ususally over estimate the importance of the
Juergen> RFC status. What really counts is what is being implemented
Juergen> and what is finally being used.

True, although I've heard of plenty of vendors that don't like
implementing things until they get to "draft".  I've heard of many
others that implement the first document written about a subject as
well though.
-- 
Wes Hardaker
Distributed Computing Analysis and Support
University of California at Davis


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id XAA02192 for nmrg-outgoing; Fri, 28 Apr 2000 23:44:21 +0200 (MET DST)
Received: from icasun1.epfl.ch (root@icasun1.epfl.ch [128.178.151.148]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id XAA02187 for <nmrg@ibr.cs.tu-bs.de>; Fri, 28 Apr 2000 23:44:19 +0200 (MET DST)
Received: from ica.epfl.ch (jpmf@tcomhp33.epfl.ch [128.178.151.24]) by icasun1.epfl.ch (8.8.X/EPFL-8.1d for ICA) with ESMTP id XAA04001 for <nmrg@ibr.cs.tu-bs.de>; Fri, 28 Apr 2000 23:44:16 +0200 (MET DST)
Message-Id: <200004282144.XAA04001@icasun1.epfl.ch>
X-Mailer: exmh version 2.1.1 10/15/1999
From: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Reply-To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
Subject: Re: [nmrg] snmp over tcp status 
In-reply-to: Your message of "Fri, 28 Apr 2000 14:38:25 METDST." <200004281238.OAA03006@henkell.ibr.cs.tu-bs.de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Fri, 28 Apr 2000 23:44:11 +0200
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

On Fri, 28 Apr 2000 14:38:25 +0200, Juergen Schoenwaelder wrote:
> 
> I have uploaded a new revision of the document to the ID archive. It
> fixes the typos reported and it contains the updated acknowledment
> section. I think this is the final version.
> 
> ftp://ietf.org/internet-drafts/draft-irtf-nmrg-snmp-tcp-04.txt
> 
> I have also contacted the chairs of the SNMPv3 working group to figure
> out whether they think this draft should be considered by the SNMPv3
> WG. The response was that they prefer to submit this document for
> publication as Experimental RFC at this point in time.

OK

> The SNMPv3 chairs also suggested to post a message to the SNMPv3
> mailing list of our intention to submit this version as Experimental
> RFC to see whether there are any strong reactions in the larger SNMP
> community. I think this is actually a good idea. I plan to give the
> SNMP community 14 days to raise any comments on the document or our
> plan to go for Experimental RFC, unless I hear any objections against
> this plan.

Sounds very reasonable to me.

JP



Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id SAA15703 for nmrg-outgoing; Fri, 28 Apr 2000 18:58:43 +0200 (MET DST)
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 SAA15698; Fri, 28 Apr 2000 18:58:39 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id SAA12685; Fri, 28 Apr 2000 18:58:39 +0200
Date: Fri, 28 Apr 2000 18:58:39 +0200
Message-Id: <200004281658.SAA12685@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: wjhardaker@ucdavis.edu
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to: <sd66t29ovo.fsf@wanderer.hardaker.davis.ca.us> (message from Wes Hardaker on 28 Apr 2000 09:22:35 -0700)
Subject: Re: [nmrg] snmp over tcp status
References: <200004281238.OAA03006@henkell.ibr.cs.tu-bs.de> <sd66t29ovo.fsf@wanderer.hardaker.davis.ca.us>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> Wes Hardaker writes:

Wes> Judging by the amount of flack that SNMP has gotten recently in
Wes> other discussions for being only UDP based, I'd rather see it go
Wes> forward further in the standards track but I understand the
Wes> reasons behind the decision...

I agree. But having an experimental RFC is still much better than
having no official document at all.

And IETF people ususally over estimate the importance of the RFC
status. What really counts is what is being implemented and what is
finally being used.

/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/>




Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id SAA13800 for nmrg-outgoing; Fri, 28 Apr 2000 18:22:40 +0200 (MET DST)
Received: from wanderer.hardaker.davis.ca.us (IDENT:root@dns2.hardaker.davis.ca.us [168.150.190.2]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id SAA13795; Fri, 28 Apr 2000 18:22:38 +0200 (MET DST)
Received: (from hardaker@localhost) by wanderer.hardaker.davis.ca.us (8.9.3/8.9.3) id JAA04029; Fri, 28 Apr 2000 09:22:35 -0700
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Cc: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] snmp over tcp status
References: <200004281238.OAA03006@henkell.ibr.cs.tu-bs.de>
From: Wes Hardaker <wjhardaker@ucdavis.edu>
X-URL: http://dcas.ucdavis.edu/~hardaker
X-Microsoft: Sucks
Organization: U.C.Davis, Information Technology - D.C.A.S.
X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4
Date: 28 Apr 2000 09:22:35 -0700
In-Reply-To: Juergen Schoenwaelder's message of "Fri, 28 Apr 2000 14:38:25 +0200"
Message-ID: <sd66t29ovo.fsf@wanderer.hardaker.davis.ca.us>
Lines: 12
User-Agent: Gnus/5.0805 (Gnus v5.8.5) XEmacs/21.2 (Shinjuku)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> On Fri, 28 Apr 2000 14:38:25 +0200, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> said:

Juergen> The response was that they prefer to submit this document for
Juergen> publication as Experimental RFC at this point in time.

Judging by the amount of flack that SNMP has gotten recently in other
discussions for being only UDP based, I'd rather see it go forward
further in the standards track but I understand the reasons behind the 
decision...

-- 
"Ninjas aren't dangerous.  They're more afraid of you than you are of them."


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id OAA27010 for nmrg-outgoing; Fri, 28 Apr 2000 14:38:27 +0200 (MET DST)
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 OAA27005; Fri, 28 Apr 2000 14:38:25 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id OAA03006; Fri, 28 Apr 2000 14:38:25 +0200
Date: Fri, 28 Apr 2000 14:38:25 +0200
Message-Id: <200004281238.OAA03006@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] snmp over tcp status
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

I have uploaded a new revision of the document to the ID archive. It
fixes the typos reported and it contains the updated acknowledment
section. I think this is the final version.

ftp://ietf.org/internet-drafts/draft-irtf-nmrg-snmp-tcp-04.txt

I have also contacted the chairs of the SNMPv3 working group to figure
out whether they think this draft should be considered by the SNMPv3
WG. The response was that they prefer to submit this document for
publication as Experimental RFC at this point in time.

The SNMPv3 chairs also suggested to post a message to the SNMPv3
mailing list of our intention to submit this version as Experimental
RFC to see whether there are any strong reactions in the larger SNMP
community. I think this is actually a good idea. I plan to give the
SNMP community 14 days to raise any comments on the document or our
plan to go for Experimental RFC, unless I hear any objections against
this plan.

/js



Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id RAA13254 for nmrg-outgoing; Tue, 25 Apr 2000 17:51:27 +0200 (MET DST)
Received: from wanderer.hardaker.davis.ca.us (IDENT:root@wjh.ucdavis.edu [169.237.210.75]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id RAA13249; Tue, 25 Apr 2000 17:51:24 +0200 (MET DST)
Received: (from hardaker@localhost) by wanderer.hardaker.davis.ca.us (8.9.3/8.9.3) id IAA07824; Tue, 25 Apr 2000 08:51:18 -0700
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Cc: sprenkel@cs.utwente.nl, nmrg@ibr.cs.tu-bs.de, bwijnen@lucent.com
Subject: Re: [nmrg] snmp over tcp document revision
References: <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de> <38FC6B72.68CBEB9C@cs.utwente.nl> <200004190856.KAA13942@henkell.ibr.cs.tu-bs.de>
From: Wes Hardaker <wjhardaker@ucdavis.edu>
X-URL: http://dcas.ucdavis.edu/~hardaker
X-Microsoft: Sucks
Organization: U.C.Davis, Information Technology - D.C.A.S.
X-Face: #qW^}a%m*T^{A:Cp}$R\"38+d}41-Z}uU8,r%F#c#s:~Nzp0G9](s?,K49KJ]s"*7gvRgA SrAvQc4@/}L7Qc=w{)]ACO\R{LF@S{pXfojjjGg6c;q6{~C}CxC^^&~(F]`1W)%9j/iS/ IM",B1M.?{w8ckLTYD'`|kTr\i\cgY)P4
Date: 25 Apr 2000 08:51:16 -0700
In-Reply-To: Juergen Schoenwaelder's message of "Wed, 19 Apr 2000 10:56:33 +0200"
Message-ID: <sd8zy2xjpn.fsf@wanderer.hardaker.davis.ca.us>
Lines: 26
User-Agent: Gnus/5.0805 (Gnus v5.8.5) XEmacs/21.2 (Shinjuku)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> On Wed, 19 Apr 2000 10:56:33 +0200, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> said:

Ron> Do you think that Bert Helthuis should be mentioned there also?
Ron> He made an implementation based on an older version of UCD SNMP
Ron> (version 3.6.2,
Ron> http://ing.ctit.utwente.nl/WU2/d2.1/snmp-tcp/patch01.tar)

Juergen> Well, Luca also did some implementation work, although he
Juergen> focussed on the manager side if I remember right.

Just, FYI (since it really doesn't matter): Luca's code did modify
both the agent and management apps.  However, the implementation
currently done in the ucd-snmp package is not based on his work at all 
(and is done differently to allow a dynamicly expandable char array to 
handle larger packets than Luca dealt with (limit currently set to
32768)).

The agent had been completely restructured when Luca sund us his
patch, and hence we couldn't apply it as was.

He should definitely be mentioned in the document though!

-- 
Wes Hardaker
Distributed Computing Analysis and Support
University of California at Davis


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id QAA28939 for nmrg-outgoing; Wed, 19 Apr 2000 16:22:17 +0200 (MET DST)
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 QAA28925; Wed, 19 Apr 2000 16:22:12 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id QAA29316; Wed, 19 Apr 2000 16:22:12 +0200
Date: Wed, 19 Apr 2000 16:22:12 +0200
Message-Id: <200004191422.QAA29316@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: sprenkel@cs.utwente.nl
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to: <38FDB26E.C5879A25@cs.utwente.nl> (message from Ron Sprenkels on Wed, 19 Apr 2000 15:19:42 +0200)
Subject: Re: [nmrg] snmp over tcp document revision
References: <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de> <38FC6B72.68CBEB9C@cs.utwente.nl> <200004190856.KAA13942@henkell.ibr.cs.tu-bs.de> <38FDB26E.C5879A25@cs.utwente.nl>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> Ron Sprenkels writes:

>> Shall I use that instead of the current wordings?

Ron> Yes, I think those wordings would be fine.

OK. I will use the reworded text unless I hear any objections.

/js


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id PAA24762 for nmrg-outgoing; Wed, 19 Apr 2000 15:18:25 +0200 (MET DST)
Received: from prodnet.civ.utwente.nl (prodnet.civ.utwente.nl [130.89.1.19]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id PAA24742; Wed, 19 Apr 2000 15:18:23 +0200 (MET DST)
Received: from cs.utwente.nl (ut198100.inbel.utwente.nl [130.89.198.100]) by prodnet.civ.utwente.nl (8.9.3/MQT) with ESMTP id PAA13370; Wed, 19 Apr 2000 15:18:21 +0200 (METDST)
Message-ID: <38FDB26E.C5879A25@cs.utwente.nl>
Date: Wed, 19 Apr 2000 15:19:42 +0200
From: Ron Sprenkels <sprenkel@cs.utwente.nl>
X-Mailer: Mozilla 4.5 [en] (Win95; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
CC: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] snmp over tcp document revision
References: <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de> <38FC6B72.68CBEB9C@cs.utwente.nl> <200004190856.KAA13942@henkell.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

Hi,

> >> Finally, I changed the acknowledgments section to say thanks to our
> >> early implementors who made their code available. (I did not
> >> include Luca since I have no idea what status his code actually
> >> has.)
> 
> Ron> Do you think that Bert Helthuis should be mentioned there also?
> Ron> He made an implementation based on an older version of UCD SNMP
> Ron> (version 3.6.2,
> Ron> http://ing.ctit.utwente.nl/WU2/d2.1/snmp-tcp/patch01.tar)
> 
> Well, Luca also did some implementation work, although he focussed on
> the manager side if I remember right. And I think he also used some
> CMU derived package. I wanted to cite UCD and the Linux CMU agent
> because they have TCP support integrated into their distributions,
> which I think is important for other to "pick up and steal" ideas.
> 
> Here is a proposed rewording (in XML source) to address this:
> 
>   <t>
>     Additional thanks go to Luca Deri, Wes Hardaker, Bert Helthuis,
>     and Erik Schoenfelder for their prototype implementations. The
>     SNMP over TCP transport mapping is integrated in the current <eref
>     target="http://ucd-snmp.ucdavis.edu/">UCD SNMPpackage</eref> and
>     the current <eref target="http://www.gaertner.de/snmp/">Linux CMU
>     SNMP package</eref>.
>   </t>
> 
> Shall I use that instead of the current wordings?

Yes, I think those wordings would be fine.

Ron.

--------------------------------------------------------------------------
Ron Sprenkels  sprenkel@cs.utwente.nl   http://www.cs.utwente.nl/~sprenkel
University of Twente, Department of Computer Science, TSS Management group
P.O. Box 217, 7500 AE Enschede, The Netherlands.    (Tel. +31 53 489 4663)


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id KAA07288 for nmrg-outgoing; Wed, 19 Apr 2000 10:56:50 +0200 (MET DST)
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 KAA07269; Wed, 19 Apr 2000 10:56:33 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id KAA13942; Wed, 19 Apr 2000 10:56:33 +0200
Date: Wed, 19 Apr 2000 10:56:33 +0200
Message-Id: <200004190856.KAA13942@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: sprenkel@cs.utwente.nl
CC: nmrg@ibr.cs.tu-bs.de, bwijnen@lucent.com
In-reply-to: <38FC6B72.68CBEB9C@cs.utwente.nl> (message from Ron Sprenkels on Tue, 18 Apr 2000 16:04:34 +0200)
Subject: Re: [nmrg] snmp over tcp document revision
References: <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de> <38FC6B72.68CBEB9C@cs.utwente.nl>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> Ron Sprenkels writes:

Ron> It has taken me some time to read this, due to time-consuming
Ron> happy events at home :-) His name is Robin, and he was born on
Ron> April 3.

Congratulations to all of you. I have seen Robin sleeping on your Web
page. But I guess this is a transient state which only lasts for a few
hours at best. ;-)
 
>> Finally, I changed the acknowledgments section to say thanks to our
>> early implementors who made their code available. (I did not
>> include Luca since I have no idea what status his code actually
>> has.)

Ron> Do you think that Bert Helthuis should be mentioned there also?
Ron> He made an implementation based on an older version of UCD SNMP
Ron> (version 3.6.2,
Ron> http://ing.ctit.utwente.nl/WU2/d2.1/snmp-tcp/patch01.tar)

Well, Luca also did some implementation work, although he focussed on
the manager side if I remember right. And I think he also used some
CMU derived package. I wanted to cite UCD and the Linux CMU agent
because they have TCP support integrated into their distributions,
which I think is important for other to "pick up and steal" ideas.

Here is a proposed rewording (in XML source) to address this:

  <t>
    Additional thanks go to Luca Deri, Wes Hardaker, Bert Helthuis,
    and Erik Schoenfelder for their prototype implementations. The
    SNMP over TCP transport mapping is integrated in the current <eref
    target="http://ucd-snmp.ucdavis.edu/">UCD SNMPpackage</eref> and
    the current <eref target="http://www.gaertner.de/snmp/">Linux CMU
    SNMP package</eref>.
  </t>

Shall I use that instead of the current wordings?
 
Ron> Small thing: I'm not completely sure, but shouldn't 'send' in the
Ron> second line of page #6 be 'sent'?

Changed to sent.

/js


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id QAA01408 for nmrg-outgoing; Tue, 18 Apr 2000 16:04:42 +0200 (MET DST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id QAA01403; Tue, 18 Apr 2000 16:04:39 +0200 (MET DST)
Received: from cs.utwente.nl (utip074.cs.utwente.nl [130.89.12.43]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id QAA26421; Tue, 18 Apr 2000 16:04:35 +0200 (MET DST)
Message-ID: <38FC6B72.68CBEB9C@cs.utwente.nl>
Date: Tue, 18 Apr 2000 16:04:34 +0200
From: Ron Sprenkels <sprenkel@cs.utwente.nl>
Organization: University of Twente
X-Mailer: Mozilla 4.7 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
CC: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>, Bert Wijnen <bwijnen@lucent.com>
Subject: Re: [nmrg] snmp over tcp document revision
References: <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

Hi Juergen,
 
> I have updated our snmp over tcp specification. The new internet draft
> is <URL:ftp://ietf.org/internet-drafts/draft-irtf-nmrg-snmp-tcp-03.txt>.

It has taken me some time to read this, due to time-consuming happy events
at home :-) His name is Robin, and he was born on April 3. 
 
> I incorporated the changes discussed in Oslo (connection management,
> discussion of confirmed operations versus reliable transport).
> 
> I reformatted the document using the XML DTD (RFC 2629). (The idea is
> that all IDs we are producing will be written in XML so that it is
> move responsibility for these documents.)

I don't fully understand what you mean here, but anyway, I think the
formatting of the draft is very consistent everywhere now. Which, I guess,
is to be expected if the formatting is generated from an XML document. I
really like that.
 
> Finally, I changed the acknowledgments section to say thanks to our
> early implementors who made their code available. (I did not include
> Luca since I have no idea what status his code actually has.)

Do you think that Bert Helthuis should be mentioned there also? He made an
implementation  based on an older version of UCD SNMP (version 3.6.2,
http://ing.ctit.utwente.nl/WU2/d2.1/snmp-tcp/patch01.tar)
 
> Please check this revision and let us know if there are any issues
> with it. Otherwise, I would like to move this forward by submitting it
> for experimental RFC.

No issues as far as I'm concerned.

Small thing: I'm not completely sure, but shouldn't 'send' in the second
line of page #6 be 'sent'?

regards,

Ron.


--------------------------------------------------------------------------
Ron Sprenkels  sprenkel@cs.utwente.nl   http://www.cs.utwente.nl/~sprenkel
University of Twente, Department of Computer Science, TSS Management group 
P.O. Box 217, 7500 AE Enschede, The Netherlands.    (Tel. +31 53 489 4663)


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id SAA22312 for nmrg-outgoing; Thu, 13 Apr 2000 18:16:35 +0200 (MET DST)
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 SAA22291; Thu, 13 Apr 2000 18:16:27 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id SAA25690; Thu, 13 Apr 2000 18:16:27 +0200
Date: Thu, 13 Apr 2000 18:16:27 +0200
Message-Id: <200004131616.SAA25690@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: jp.martin-flatin@ieee.org
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to: <200004121722.TAA27161@icasun1.epfl.ch> (jp.martin-flatin@ieee.org)
Subject: Re: [nmrg] SCTP
References:  <200004121722.TAA27161@icasun1.epfl.ch>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> J P Martin-Flatin writes:

JP> You might be interested in reading about SCTP, which lies
JP> somewhere between TCP and UDP:

JP> draft-ietf-sigtran-sctp-08.txt
JP> draft-ietf-sigtran-sctp-applicability-00.txt

JP> Perhaps a good candidate to transport policies.

JP> Juergen, what about an SNMP over SCTP mapping?  ;-)

Go ahead if you think this makes sense.

(Personally, I have no clue how to implement something like this 
since a new transport protocol will take years to become universally
available. But this is of course not an argument for not doing a
transport mapping for SCTP or even implementing SCTP in your 
favourite kernel.)

/js


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id TAA26272 for nmrg-outgoing; Wed, 12 Apr 2000 19:22:49 +0200 (MET DST)
Received: from icasun1.epfl.ch (root@icasun1.epfl.ch [128.178.151.148]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id TAA26268 for <nmrg@ibr.cs.tu-bs.de>; Wed, 12 Apr 2000 19:22:48 +0200 (MET DST)
Received: from ica.epfl.ch (jpmf@tcomhp33.epfl.ch [128.178.151.24]) by icasun1.epfl.ch (8.8.X/EPFL-8.1d for ICA) with ESMTP id TAA27161 for <nmrg@ibr.cs.tu-bs.de>; Wed, 12 Apr 2000 19:22:46 +0200 (MET DST)
Message-Id: <200004121722.TAA27161@icasun1.epfl.ch>
X-Mailer: exmh version 2.1.1 10/15/1999
From: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
To: nmrg@ibr.cs.tu-bs.de
Reply-To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
Subject: [nmrg] SCTP
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 12 Apr 2000 19:22:45 +0200
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

Remember Bert's pointer to RUTS when we began talking about SNMP over
TCP? This is now discussed by the SIGTRAN and PILC WGs at the IETF
(Transport Area). You might be interested in reading about SCTP, which
lies somewhere between TCP and UDP:

  draft-ietf-sigtran-sctp-08.txt
  draft-ietf-sigtran-sctp-applicability-00.txt

Perhaps a good candidate to transport policies.

Juergen, what about an SNMP over SCTP mapping?   ;-)

JP



Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id KAA13882 for nmrg-outgoing; Wed, 12 Apr 2000 10:14:08 +0200 (MET DST)
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 KAA13877; Wed, 12 Apr 2000 10:14:05 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id KAA10928; Wed, 12 Apr 2000 10:14:05 +0200
Date: Wed, 12 Apr 2000 10:14:05 +0200
Message-Id: <200004120814.KAA10928@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: bwijnen@lucent.com
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to:  <2413FED0DFE6D111B3F90008C7FA61FB06BF7EEB@nl0006exch002u.nl.lucent.com> (bwijnen@lucent.com)
Subject: Re: [nmrg] RE: snmp over tcp document revision
References:  <2413FED0DFE6D111B3F90008C7FA61FB06BF7EEB@nl0006exch002u.nl.lucent.com>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

>>>>> Wijnen, Bert (Bert) writes:

Bert> Maybe it is good to feel the SNMPv3 list as to what they think
Bert> about PS.  If you want to do that, pls check with WG chairs if
Bert> they can agree that you use their mlist.

I have contacted the WG chairs and I will start a poll on the SNMPv3
list for opinions once I have green lights.

/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/>




Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id GAA28737 for nmrg-outgoing; Wed, 12 Apr 2000 06:38:42 +0200 (MET DST)
Received: from auemlsrv.firewall.lucent.com (auemail1.lucent.com [192.11.223.161]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id GAA28732; Wed, 12 Apr 2000 06:38:39 +0200 (MET DST)
Received: from auemlsrv.firewall.lucent.com (localhost [127.0.0.1]) by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id AAA27349; Wed, 12 Apr 2000 00:38:38 -0400 (EDT)
Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by auemlsrv.firewall.lucent.com (Pro-8.9.3/8.9.3) with ESMTP id AAA27334; Wed, 12 Apr 2000 00:38:36 -0400 (EDT)
Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2448.0) id <2P0YKS37>; Wed, 12 Apr 2000 06:38:34 +0200
Message-ID: <2413FED0DFE6D111B3F90008C7FA61FB06BF7EEB@nl0006exch002u.nl.lucent.com>
From: "Wijnen, Bert (Bert)" <bwijnen@lucent.com>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Subject: [nmrg] RE: snmp over tcp document revision
Date: Wed, 12 Apr 2000 06:38:31 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2448.0)
Content-Type: text/plain
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

If you want to get this on Stds track, and you think the doc is ready for
that
(as you seem to claim), then it migth be good to also post to the SNMPv3
list that
this document is in final review in NMRG group and that you plan to ask for
Experimental or PS document. If experimental ,then I would prefer to not
include the IPv6 over UDP mapping in here, because that I would like to 
see start at PS rigth away.

Maybe it is good to feel the SNMPv3 list as to what they think about PS.
If you want to do that, pls check with WG chairs if they can agree that you
use their mlist.

Bert

> ----------
> From: 	Juergen Schoenwaelder[SMTP:schoenw@ibr.cs.tu-bs.de]
> Sent: 	Friday, April 07, 2000 10:11 AM
> To: 	Network Management Research Group; Wijnen, Bert (Bert)
> Subject: 	snmp over tcp document revision
> 
> 
> I have updated our snmp over tcp specification. The new internet draft
> is <URL:ftp://ietf.org/internet-drafts/draft-irtf-nmrg-snmp-tcp-03.txt>.
> 
> I incorporated the changes discussed in Oslo (connection management,
> discussion of confirmed operations versus reliable transport). 
> 
> I reformatted the document using the XML DTD (RFC 2629). (The idea is
> that all IDs we are producing will be written in XML so that it is
> move responsibility for these documents.)
> 
> Finally, I changed the acknowledgments section to say thanks to our
> early implementors who made their code available. (I did not include
> Luca since I have no idea what status his code actually has.)
> 
> Please check this revision and let us know if there are any issues
> with it. Otherwise, I would like to move this forward by submitting it
> for experimental RFC.
> 
> Bert, there is an open action item in the IETF regarding the SNMP over
> UDP/IPv6 transport mapping. Do you think it makes sense to extend our
> document with definitions for SNMP over TCP/IPv6 and SNMP over
> UDP/IPv6 so that it can actually go onto the standards track? In this
> case, we could actually skip the experimental RFC for SNMP over TCP.
> 
> /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/>
> 
> 


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id EAA20547 for nmrg-outgoing; Sat, 8 Apr 2000 04:39:49 +0200 (MET DST)
Received: from icasun1.epfl.ch (root@icasun1.epfl.ch [128.178.151.148]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) with ESMTP id EAA20543 for <nmrg@ibr.cs.tu-bs.de>; Sat, 8 Apr 2000 04:39:47 +0200 (MET DST)
Received: from ica.epfl.ch (jpmf@tcomhp33.epfl.ch [128.178.151.24]) by icasun1.epfl.ch (8.8.X/EPFL-8.1d for ICA) with ESMTP id EAA20991 for <nmrg@ibr.cs.tu-bs.de>; Sat, 8 Apr 2000 04:39:45 +0200 (MET DST)
Message-Id: <200004080239.EAA20991@icasun1.epfl.ch>
X-Mailer: exmh version 2.1.1 10/15/1999
From: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Reply-To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
Subject: Re: [nmrg] snmp over tcp document revision 
In-reply-to: Your message of "Fri, 07 Apr 2000 10:11:16 METDST." <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 08 Apr 2000 04:39:44 +0200
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

On Fri, 7 Apr 2000 10:11:16 +0200, Juergen Schoenwaelder wrote:
> 
> Please check this revision and let us know if there are any issues
> with it.

I am happy with it.

> Otherwise, I would like to move this forward by submitting it
> for experimental RFC.

Please do.

Jean-Philippe



Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.3) id KAA07724 for nmrg-outgoing; Fri, 7 Apr 2000 10:11:19 +0200 (MET DST)
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 KAA07710; Fri, 7 Apr 2000 10:11:16 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id KAA23046; Fri, 7 Apr 2000 10:11:16 +0200
Date: Fri, 7 Apr 2000 10:11:16 +0200
Message-Id: <200004070811.KAA23046@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>, Bert Wijnen <bwijnen@lucent.com>
Subject: [nmrg] snmp over tcp document revision
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk
Status: RO

I have updated our snmp over tcp specification. The new internet draft
is <URL:ftp://ietf.org/internet-drafts/draft-irtf-nmrg-snmp-tcp-03.txt>.

I incorporated the changes discussed in Oslo (connection management,
discussion of confirmed operations versus reliable transport). 

I reformatted the document using the XML DTD (RFC 2629). (The idea is
that all IDs we are producing will be written in XML so that it is
move responsibility for these documents.)

Finally, I changed the acknowledgments section to say thanks to our
early implementors who made their code available. (I did not include
Luca since I have no idea what status his code actually has.)

Please check this revision and let us know if there are any issues
with it. Otherwise, I would like to move this forward by submitting it
for experimental RFC.

Bert, there is an open action item in the IETF regarding the SNMP over
UDP/IPv6 transport mapping. Do you think it makes sense to extend our
document with definitions for SNMP over TCP/IPv6 and SNMP over
UDP/IPv6 so that it can actually go onto the standards track? In this
case, we could actually skip the experimental RFC for SNMP over TCP.

/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/>



