Received: from netlx010.civ.utwente.nl (netlx010.civ.utwente.nl [130.89.1.92]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1RDGwSW006286 for <nmrg@ibr.cs.tu-bs.de>; Wed, 27 Feb 2002 14:16:59 +0100
Received: from cs.utwente.nl (utip315.cs.utwente.nl [130.89.12.84]) by netlx010.civ.utwente.nl (8.11.4/HKD) with ESMTP id g1RDGw609339 for <nmrg@ibr.cs.tu-bs.de>; Wed, 27 Feb 2002 14:16:58 +0100
Message-ID: <3C7CDC48.F75C08F0@cs.utwente.nl>
Date: Wed, 27 Feb 2002 14:16:56 +0100
From: Szabolcs Boros <boros@cs.utwente.nl>
Organization: UTwente
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: hu,en,ro,nl
MIME-Version: 1.0
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] next meeting location
References: <200202251534.g1PFY6h25097@haerke.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Hi, 

I would also like to participate. Pisa is not a problem. 

szabi






Juergen Schoenwaelder wrote:
> 
> Those who plan to attend the next NMRG meeting - would it be a problem
> for you if we move the meeting from Florence to Pisa?
> 
> Luca Deri is living in Pisa and this would make the logistics a bit
> simpler.
> 
> Please drop me a note.
> 
> /js
> 
> --
> Juergen Schoenwaelder      University of Osnabrueck
> <schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
> Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
> Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>
> 
> --
> !! This message is brought to you via the `nmrg' mailing list.
> !! Please do not reply to this message to unsubscribe. To unsubscribe or adjust
> !! your settings, send a mail message to <nmrg-request@ibr.cs.tu-bs.de>
> !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg.


Received: from cosium01.intelliden.net (cosium01.intelliden.net [12.41.186.248]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1PNQEiF013094; Tue, 26 Feb 2002 00:26:15 +0100
Received: by cosium01.intelliden.net with Internet Mail Service (5.5.2653.19) id <FP49Q1MB>; Mon, 25 Feb 2002 16:26:06 -0700
Message-ID: <C94C3F56FA66EC4DA473B081A147D85D2D60F3@cosium01.intelliden.net>
From: John Strassner <John.Strassner@intelliden.com>
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>, jp.martin-flatin@ieee.org
Cc: nmrg@ibr.cs.tu-bs.de
Subject: RE: [nmrg] 10th NMRG meeting
Date: Mon, 25 Feb 2002 16:25:59 -0700
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C1BE53.C88FE100"
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

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

------_=_NextPart_001_01C1BE53.C88FE100
Content-Type: text/plain

Hi Juergen,
Sorry, I've been on Holiday last week. I'm interested and will try to
attend.

regards,
John
 
John Strassner
Chief Strategy Officer
Intelliden Corporation
90 South Cascade Avenue
Colorado Springs, CO  80903  USA
phone: +1.719.785.0648
  FAX: +1.719.785.0644
email: john.strassner@intelliden.com 
 

-----Original Message-----
From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de] 
Sent: Monday, February 18, 2002 6:10 AM
To: jp.martin-flatin@ieee.org
Cc: nmrg@ibr.cs.tu-bs.de
Subject: Re: [nmrg] 10th NMRG meeting


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

JP> Where shall we meet?

So far, I only have received clear responses from five people:

Jean-Phillipe Martin-Flatin     yes
Marcus Brunner                  yes
Juergen Schoenwaelder           yes
Bert Wijnen                     maybe
Andrea Westerinen               yes

I would like to hear from the other folks on this list, especially
those who will be in Italy at that time. If we are only four people,
we can meet almost everywhere. If we end up being ten or so, we need
to figure out where we can get a nice and cheap meeting room.

So please, if you are not listed above, let me know ASAP whether you
plan to attend or not. Thanks,

/js

-- 
Juergen Schoenwaelder      University of Osnabrueck
<schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>


-- 
!! This message is brought to you via the `nmrg' mailing list.
!! Please do not reply to this message to unsubscribe. To unsubscribe or
adjust
!! your settings, send a mail message to <nmrg-request@ibr.cs.tu-bs.de>
!! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg.

------_=_NextPart_001_01C1BE53.C88FE100
Content-Type: text/html
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>RE: [nmrg] 10th NMRG meeting</TITLE>
</HEAD>
<BODY>

<P><FONT SIZE=3D2>Hi Juergen,</FONT>
<BR><FONT SIZE=3D2>Sorry, I've been on Holiday last week. I'm =
interested and will try to attend.</FONT>
</P>

<P><FONT SIZE=3D2>regards,</FONT>
<BR><FONT SIZE=3D2>John</FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
<BR><FONT SIZE=3D2>John Strassner</FONT>
<BR><FONT SIZE=3D2>Chief Strategy Officer</FONT>
<BR><FONT SIZE=3D2>Intelliden Corporation</FONT>
<BR><FONT SIZE=3D2>90 South Cascade Avenue</FONT>
<BR><FONT SIZE=3D2>Colorado Springs, CO&nbsp; 80903&nbsp; USA</FONT>
<BR><FONT SIZE=3D2>phone: +1.719.785.0648</FONT>
<BR><FONT SIZE=3D2>&nbsp; FAX: +1.719.785.0644</FONT>
<BR><FONT SIZE=3D2>email: john.strassner@intelliden.com </FONT>
<BR><FONT SIZE=3D2>&nbsp;</FONT>
</P>

<P><FONT SIZE=3D2>-----Original Message-----</FONT>
<BR><FONT SIZE=3D2>From: Juergen Schoenwaelder [<A =
HREF=3D"mailto:schoenw@ibr.cs.tu-bs.de">mailto:schoenw@ibr.cs.tu-bs.de</=
A>] </FONT>
<BR><FONT SIZE=3D2>Sent: Monday, February 18, 2002 6:10 AM</FONT>
<BR><FONT SIZE=3D2>To: jp.martin-flatin@ieee.org</FONT>
<BR><FONT SIZE=3D2>Cc: nmrg@ibr.cs.tu-bs.de</FONT>
<BR><FONT SIZE=3D2>Subject: Re: [nmrg] 10th NMRG meeting</FONT>
</P>
<BR>

<P><FONT SIZE=3D2>&gt;&gt;&gt;&gt;&gt; J P Martin-Flatin writes:</FONT>
</P>

<P><FONT SIZE=3D2>JP&gt; Where shall we meet?</FONT>
</P>

<P><FONT SIZE=3D2>So far, I only have received clear responses from =
five people:</FONT>
</P>

<P><FONT SIZE=3D2>Jean-Phillipe Martin-Flatin&nbsp;&nbsp;&nbsp;&nbsp; =
yes</FONT>
<BR><FONT SIZE=3D2>Marcus =
Brunner&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; yes</FONT>
<BR><FONT SIZE=3D2>Juergen =
Schoenwaelder&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp=
; yes</FONT>
<BR><FONT SIZE=3D2>Bert =
Wijnen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;=
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; maybe</FONT>
<BR><FONT SIZE=3D2>Andrea =
Westerinen&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; yes</FONT>
</P>

<P><FONT SIZE=3D2>I would like to hear from the other folks on this =
list, especially</FONT>
<BR><FONT SIZE=3D2>those who will be in Italy at that time. If we are =
only four people,</FONT>
<BR><FONT SIZE=3D2>we can meet almost everywhere. If we end up being =
ten or so, we need</FONT>
<BR><FONT SIZE=3D2>to figure out where we can get a nice and cheap =
meeting room.</FONT>
</P>

<P><FONT SIZE=3D2>So please, if you are not listed above, let me know =
ASAP whether you</FONT>
<BR><FONT SIZE=3D2>plan to attend or not. Thanks,</FONT>
</P>

<P><FONT SIZE=3D2>/js</FONT>
</P>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>Juergen Schoenwaelder&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
University of Osnabrueck</FONT>
<BR><FONT =
SIZE=3D2>&lt;schoenw@inf.uos.de&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
Dept. of Mathematics and Computer Science</FONT>
<BR><FONT SIZE=3D2>Phone: +49 541 969 2483&nbsp;&nbsp;&nbsp; =
Albrechtstr. 28, 49069 Osnabrueck, Germany</FONT>
<BR><FONT SIZE=3D2>Fax:&nbsp;&nbsp; +49 541 969 2770&nbsp;&nbsp;&nbsp; =
&lt;<A HREF=3D"http://www.informatik.uni-osnabrueck.de/" =
TARGET=3D"_blank">http://www.informatik.uni-osnabrueck.de/</A>&gt;</FONT=
>
</P>
<BR>

<P><FONT SIZE=3D2>-- </FONT>
<BR><FONT SIZE=3D2>!! This message is brought to you via the `nmrg' =
mailing list.</FONT>
<BR><FONT SIZE=3D2>!! Please do not reply to this message to =
unsubscribe. To unsubscribe or adjust</FONT>
<BR><FONT SIZE=3D2>!! your settings, send a mail message to =
&lt;nmrg-request@ibr.cs.tu-bs.de&gt;</FONT>
<BR><FONT SIZE=3D2>!! or look at <A =
HREF=3D"https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg" =
TARGET=3D"_blank">https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg</A>.=
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C1BE53.C88FE100--


Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1PGI6iF029033; Mon, 25 Feb 2002 17:18:06 +0100
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g1PGI6l25788; Mon, 25 Feb 2002 17:18:06 +0100
Date: Mon, 25 Feb 2002 17:18:06 +0100
Message-Id: <200202251618.g1PGI6l25788@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: internet-drafts@ietf.org
CC: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] please post draft-irtf-nmrg-snmp-tcp-07.txt
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Please post the following document as an Internet Draft. It has been
produced by the network management IRTF research group.

http://www.ibr.cs.tu-bs.de/~schoenw/draft-irtf-nmrg-snmp-tcp-07.txt

Thank you.

/js

-- 
Juergen Schoenwaelder      University of Osnabrueck
<schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>




Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1PFksiF027553 for <nmrg@ibr.cs.tu-bs.de>; Mon, 25 Feb 2002 16:46:55 +0100
Received: from citadel.mobility.ccrle.nec.de ([192.168.156.1]) by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id g1PFluI33058 for <nmrg@ibr.cs.tu-bs.de>; Mon, 25 Feb 2002 16:47:56 +0100 (CET)
Received: from [192.168.102.79] (madrid.heidelberg.ccrle.nec.de [192.168.102.79]) by citadel.mobility.ccrle.nec.de (Postfix on SuSE eMail Server 2.0) with ESMTP id EFCE2C040 for <nmrg@ibr.cs.tu-bs.de>; Mon, 25 Feb 2002 16:46:51 +0100 (CET)
Date: Mon, 25 Feb 2002 16:59:37 +0100
From: Marcus Brunner <brunner@ccrle.nec.de>
Reply-To: brunner@ccrle.nec.de
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] next meeting location
Message-ID: <22643419.1014656377@[192.168.102.79]>
In-Reply-To: <200202251534.g1PFY6h25097@haerke.ibr.cs.tu-bs.de>
References:  <200202251534.g1PFY6h25097@haerke.ibr.cs.tu-bs.de>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

And those of you not visited Pisa it it worth anyway :-)
Marcus

--On Monday, February 25, 2002 4:34 PM +0100 Juergen Schoenwaelder 
<schoenw@ibr.cs.tu-bs.de> wrote:

>
> Those who plan to attend the next NMRG meeting - would it be a problem
> for you if we move the meeting from Florence to Pisa?
>
> Luca Deri is living in Pisa and this would make the logistics a bit
> simpler.
>
> Please drop me a note.
>
> /js
>
> --
> Juergen Schoenwaelder      University of Osnabrueck
> <schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
> Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
> Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>
>
>
> --
> !! This message is brought to you via the `nmrg' mailing list.
> !! Please do not reply to this message to unsubscribe. To unsubscribe or
> adjust !! your settings, send a mail message to
> <nmrg-request@ibr.cs.tu-bs.de> !! or look at
> https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg.



--------------------------------------
Dr. Marcus Brunner
Network Laboratories
NEC Europe Ltd.

E-Mail: brunner@ccrle.nec.de
WWW:    http://www.ccrle.nec.de/
personal home page: http://www.brubers.org/marcus




Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1PFY6iF026907; Mon, 25 Feb 2002 16:34:06 +0100
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g1PFY6h25097; Mon, 25 Feb 2002 16:34:06 +0100
Date: Mon, 25 Feb 2002 16:34:06 +0100
Message-Id: <200202251534.g1PFY6h25097@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] next meeting location
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Those who plan to attend the next NMRG meeting - would it be a problem
for you if we move the meeting from Florence to Pisa?

Luca Deri is living in Pisa and this would make the logistics a bit
simpler.

Please drop me a note.

/js

-- 
Juergen Schoenwaelder      University of Osnabrueck
<schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>




Received: from wanderer.hardakers.net (IDENT:3M+WX+oSwMQv8r2GgNNMm0Vi4lwLSwYq@dns2.hardaker.davis.ca.us [168.150.190.2]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1KHaTO5012382; Wed, 20 Feb 2002 18:36:32 +0100
Received: (from hardaker@localhost) by wanderer.hardakers.net (8.11.6/8.11.6) id g1KHaNA02113; Wed, 20 Feb 2002 09:36:23 -0800
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
Cc: jp.martin-flatin@ieee.org, nmrg@ibr.cs.tu-bs.de
Subject: Re: [nmrg] 10th NMRG meeting
References: <3C6B97C1.6010806@ieee.org> <200202141635.g1EGZ3V30972@haerke.ibr.cs.tu-bs.de> <3C6D880E.8060500@ieee.org> <200202181310.g1IDA1429658@haerke.ibr.cs.tu-bs.de>
From: Wes Hardaker <wes@hardakers.net>
Organization: Network Associates - NAI Labs
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: Wed, 20 Feb 2002 09:36:22 -0800
In-Reply-To: <200202181310.g1IDA1429658@haerke.ibr.cs.tu-bs.de> (Juergen Schoenwaelder's message of "Mon, 18 Feb 2002 14:10:01 +0100")
Message-ID: <sdu1scqcmh.fsf@wanderer.hardakers.net>
Lines: 20
User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.5 (bamboo, i686-pc-linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

>>>>> On Mon, 18 Feb 2002 14:10:01 +0100, Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de> said:

Juergen> So far, I only have received clear responses from five people:

Juergen> Jean-Phillipe Martin-Flatin     yes
Juergen> Marcus Brunner                  yes
Juergen> Juergen Schoenwaelder           yes
Juergen> Bert Wijnen                     maybe
Juergen> Andrea Westerinen               yes

Juergen> I would like to hear from the other folks on this list, especially
Juergen> those who will be in Italy at that time.

If it helps your notion of clear responses, I can't make it all the
way to Italy that month.  Sorry.  "no"

-- 
Wes Hardaker
NAI Labs
Network Associates


Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1KAWxO5024095; Wed, 20 Feb 2002 11:32:59 +0100
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g1KAWxT32130; Wed, 20 Feb 2002 11:32:59 +0100
Date: Wed, 20 Feb 2002 11:32:59 +0100
Message-Id: <200202201032.g1KAWxT32130@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: dperkins@dsperkins.com
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to: <5.0.2.1.2.20020219132531.028218d0@mail4.bayarea.net> (dperkins@dsperkins.com)
Subject: Re: [nmrg] 10th NMRG meeting
References:  <5.0.2.1.2.20020219132531.028218d0@mail4.bayarea.net>
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

>>>>> David T Perkins writes:

David> [...] I believe the best use of the nmrg at NOMS would be on
David> alarming, since several experts on alarming (which are not part
David> of the nmrg) are attending the NOMS meeting, and it would be
David> quite beneficial to get their participation.

Do you plan to attend NOMS / the next NMRG meeting?

What are the experts on alarming we should invite to participate?

/js


Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1KAUxO5024013; Wed, 20 Feb 2002 11:30:59 +0100
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g1KAUxI32106; Wed, 20 Feb 2002 11:30:59 +0100
Date: Wed, 20 Feb 2002 11:30:59 +0100
Message-Id: <200202201030.g1KAUxI32106@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: david.durham@intel.com
CC: jp.martin-flatin@ieee.org, nmrg@ibr.cs.tu-bs.de
In-reply-to: <10C8636AE359D4119118009027AE99870DA5DDFF@FMSMSX34> (david.durham@intel.com)
Subject: Re: [nmrg] 10th NMRG meeting
References:  <10C8636AE359D4119118009027AE99870DA5DDFF@FMSMSX34>
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

>>>>> Durham, David writes:

David> You might want to add to the agenda technologies for dealing
David> with DoS attacks and other management related security
David> issues. Eg. SNMP is currently undergoing a maelstrom of CERT
David> advisories and other bad press due to its troubling
David> susceptibilities. CERT is advising people to shut SNMP off!

Obviously, many implementations do not do proper bounds checking when
decoding BER messages. Surprisingly, it took almost a decade until
some folks wrote a decent test suite which makes the problem obvious.
I actually believe that this is a good think because vendors are now
busy to actually fix their code bases and so the problem will more or
less go away when people upgrade their SNMP agents.

The more interesting observation here is that although it was not a
secret that many agents are broken wrt. bounds checking, it tooks
years to actually get enough pressure to fix them (well - at least the
BER decoding). Furthermore, there are companies selling SNMP test
suites which obviously did not catch these problems, although it was
no problem for some students to figure them out.

Lets hope that vendors learn by providing the same quality control to
network management software as they do elsewhere and by giving more
boxes to students for more aggressive testing. :-)

/js


Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1JLhoO5032018 for <nmrg@ibr.cs.tu-bs.de>; Tue, 19 Feb 2002 22:43:51 +0100
Received: from dperkins-nb2.dsperkins.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id NAA29929; Tue, 19 Feb 2002 13:43:39 -0800 (PST)
Message-Id: <5.0.2.1.2.20020219132531.028218d0@mail4.bayarea.net>
X-Sender: dperkins@mail4.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 19 Feb 2002 13:43:10 -0800
To: "Durham, David" <david.durham@intel.com>, "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>, IRTF Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
From: "David T. Perkins" <dperkins@dsperkins.com>
Subject: RE: [nmrg] 10th NMRG meeting
In-Reply-To: <10C8636AE359D4119118009027AE99870DA5DDFF@FMSMSX34>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

HI,

Did you read the CERT advisory? The problems were with implementation
(the code that was written) and not with the protocol definition. 
Where the CERT advisory might need to be discussed is in the POISON
group with regards to advancement. 
The problems were "off by one" problems, and lack of code path
verification when BER encoding errors were encountered.

If we to add another topic (which I advise that we don't), then
we should talk about security based on sessions so that SNMP can
use existing security infrastructures that are being using on
network devices (such as tacacs+, radius, and ssh). Of course the
security experts believe that tacacs, radius, and ssh I are not
good enough. However, even though I have great interest in this
area (as well as in DoS), I believe the best use of the nmrg
at NOMS would be on alarming, since several experts on alarming
(which are not part of the nmrg) are attending the NOMS meeting,
and it would be quite beneficial to get their participation. 

At 11:08 AM 2/19/2002 -0800, Durham, David wrote:
>You might want to add to the agenda technologies for dealing with DoS
>attacks and other management related security issues. Eg. SNMP is currently
>undergoing a maelstrom of CERT advisories and other bad press due to its
>troubling susceptibilities. CERT is advising people to shut SNMP off!
>-Dave
>
>http://www.internetwk.com/story/INW20020213S0002
>-- 
>!! This message is brought to you via the `nmrg' mailing list.
>!! Please do not reply to this message to unsubscribe. To unsubscribe or adjust
>!! your settings, send a mail message to <nmrg-request@ibr.cs.tu-bs.de>
>!! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg. 

Regards,
/david t. perkins



Received: from ganymede.or.intel.com (jffdns01.or.intel.com [134.134.248.3]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1JJ8nO5026689 for <nmrg@ibr.cs.tu-bs.de>; Tue, 19 Feb 2002 20:08:50 +0100
Received: from orsmsxvs040.jf.intel.com (orsmsxvs040.jf.intel.com [192.168.65.206]) by ganymede.or.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.50 2002/02/08 23:45:02 root Exp $) with SMTP id TAA15977 for <nmrg@ibr.cs.tu-bs.de>; Tue, 19 Feb 2002 19:08:43 GMT
Received: from orsmsx26.jf.intel.com ([192.168.65.26]) by orsmsxvs040.jf.intel.com (NAVGW 2.5.1.16) with SMTP id M2002021911135711444 ; Tue, 19 Feb 2002 11:13:57 -0800
Received: by orsmsx26.jf.intel.com with Internet Mail Service (5.5.2653.19) id <1YPKYBZJ>; Tue, 19 Feb 2002 11:08:43 -0800
Message-ID: <10C8636AE359D4119118009027AE99870DA5DDFF@FMSMSX34>
From: "Durham, David" <david.durham@intel.com>
To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>, IRTF Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: RE: [nmrg] 10th NMRG meeting
Date: Tue, 19 Feb 2002 11:08:42 -0800
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

You might want to add to the agenda technologies for dealing with DoS
attacks and other management related security issues. Eg. SNMP is currently
undergoing a maelstrom of CERT advisories and other bad press due to its
troubling susceptibilities. CERT is advising people to shut SNMP off!
-Dave

http://www.internetwk.com/story/INW20020213S0002


Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1IDA1O5023159; Mon, 18 Feb 2002 14:10:02 +0100
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g1IDA1429658; Mon, 18 Feb 2002 14:10:01 +0100
Date: Mon, 18 Feb 2002 14:10:01 +0100
Message-Id: <200202181310.g1IDA1429658@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
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: <3C6D880E.8060500@ieee.org> (jp.martin-flatin@ieee.org)
Subject: Re: [nmrg] 10th NMRG meeting
References: <3C6B97C1.6010806@ieee.org> <200202141635.g1EGZ3V30972@haerke.ibr.cs.tu-bs.de> <3C6D880E.8060500@ieee.org>
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

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

JP> Where shall we meet?

So far, I only have received clear responses from five people:

Jean-Phillipe Martin-Flatin     yes
Marcus Brunner                  yes
Juergen Schoenwaelder           yes
Bert Wijnen                     maybe
Andrea Westerinen               yes

I would like to hear from the other folks on this list, especially
those who will be in Italy at that time. If we are only four people,
we can meet almost everywhere. If we end up being ten or so, we need
to figure out where we can get a nice and cheap meeting room.

So please, if you are not listed above, let me know ASAP whether you
plan to attend or not. Thanks,

/js

-- 
Juergen Schoenwaelder      University of Osnabrueck
<schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>




Received: from mta11n.bluewin.ch (mta11n.bluewin.ch [195.186.1.211]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1FMGX3t017416 for <nmrg@ibr.cs.tu-bs.de>; Fri, 15 Feb 2002 23:16:33 +0100
Received: from ieee.org (62.202.33.66) by mta11n.bluewin.ch (Bluewin AG 6.0.040) id 3C68E8E0000F57B7 for nmrg@ibr.cs.tu-bs.de; Fri, 15 Feb 2002 23:16:28 +0100
Message-ID: <3C6D880E.8060500@ieee.org>
Date: Fri, 15 Feb 2002 23:13:34 +0100
From: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
Reply-To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221
X-Accept-Language: en-us
MIME-Version: 1.0
To: IRTF Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] 10th NMRG meeting
References: <3C6B97C1.6010806@ieee.org> <200202141635.g1EGZ3V30972@haerke.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

To keep the discussion focused, I suggest we dedicate Friday and Saturday 
morning to one of Dave's topics, and Saturday afternoon to Juergen's topic. 
I'll talk about UIMs on another occasion.

Both of Dave's proposals are of interest to me. Do you have a preference?

Where shall we meet?

JP

Juergen Schoenwaelder wrote:

> Regarding topics, I have seen the following proposals:
> 
> Dave Perkins: alarms & alarm management
> Dave Perkins: convergence of entity mib model and M.3100 models
> Jean-Philippe: update on universal information modeling
> 
> I would like to add another topic:
> 
>      Why is network management different?




Received: from yamato.ccrle.nec.de (yamato.ccrle.nec.de [195.37.70.1]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1FIQB3t010523 for <nmrg@ibr.cs.tu-bs.de>; Fri, 15 Feb 2002 19:26:11 +0100
Received: from citadel.mobility.ccrle.nec.de ([192.168.156.1]) by yamato.ccrle.nec.de (8.11.6/8.10.1) with ESMTP id g1FIR5j53716; Fri, 15 Feb 2002 19:27:06 +0100 (CET)
Received: from [192.168.102.178] (belem.heidelberg.ccrle.nec.de [192.168.102.178]) by citadel.mobility.ccrle.nec.de (Postfix on SuSE eMail Server 2.0) with ESMTP id E31C4C040; Fri, 15 Feb 2002 19:26:10 +0100 (CET)
Date: Fri, 15 Feb 2002 19:24:08 +0100
From: Marcus Brunner <brunner@ccrle.nec.de>
Reply-To: brunner@ccrle.nec.de
To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>, IRTF Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] 10th NMRG meeting
Message-ID: <5110408.1013801048@[192.168.102.178]>
In-Reply-To: <3C6B97C1.6010806@ieee.org>
References:  <3C6B97C1.6010806@ieee.org>
X-Mailer: Mulberry/2.1.0 (Win32)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Fine with me.
Marcus

--On Donnerstag, 14. Februar 2002 11:56 +0100 "J.P. Martin-Flatin" 
<jp.martin-flatin@ieee.org> wrote:

> Hi,
>
> I suggest we organize the 10th NMRG meeting on April 19-20, right after
> NOMS. During our mid-January discussion, we agreed that we needed two
> days to discuss the issues raised by David Perkins. On Mon 15, there are
> tutorials during the whole day. The IM 2003 TPC meeting will take most of
> Mon 15 afternoon and several of us will attend it, so we must avoid this
> time. Personally, I can't make it the week-end before NOMS, but I am free
> after NOMS. On Fri 19, only the morning is taken by tutorials for those
> who are interested. So, I think the best dates are 19-20.
>
> Are you happy with these dates? Please answer soon: I need to confirm my
> airfares ASAP because there are very few flights to Florence from here.
>
> Thanks
> JP
>
> --
> !! This message is brought to you via the `nmrg' mailing list.
> !! Please do not reply to this message to unsubscribe. To unsubscribe or
> adjust !! your settings, send a mail message to
> <nmrg-request@ibr.cs.tu-bs.de> !! or look at
> https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg.
>



--------------------------------------
Dr. Marcus Brunner
Network Laboratories
NEC Europe Ltd.

E-Mail: brunner@ccrle.nec.de
WWW:    http://www.ccrle.nec.de/
personal home page: http://www.brubers.org/marcus




Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1F7dZ3t018780 for <nmrg@ibr.cs.tu-bs.de>; Fri, 15 Feb 2002 08:39:36 +0100
Received: from mira-sjcm-2.cisco.com (mira-sjcm-2.cisco.com [171.69.24.14]) by sj-msg-core-2.cisco.com (8.11.3/8.9.1) with ESMTP id g1F7dTE15464; Thu, 14 Feb 2002 23:39:29 -0800 (PST)
Received: from ANDREAWW2K (andreaw-frame1.cisco.com [10.19.253.186]) by mira-sjcm-2.cisco.com (Mirapoint) with SMTP id ABT09327; Thu, 14 Feb 2002 23:39:10 -0800 (PST)
From: "Andrea Westerinen" <andreaw@cisco.com>
To: "David T. Perkins" <dperkins@dsperkins.com>, <nmrg@ibr.cs.tu-bs.de>
Subject: RE: [nmrg] Thoughts about configuration...
Date: Thu, 14 Feb 2002 23:42:17 -0800
Message-ID: <GGEOLLMKEOKMFKADFNHOOEMKEJAA.andreaw@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
In-Reply-To: <5.0.2.1.2.20020212104546.02938430@mail4.bayarea.net>
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

David, Another aspect to this is policy.  You may want to distinguish some
of the referential integrity issues as "alertable problems" and others as
"informational notification" or "no notification."

The approach that CIM takes is to define a group and membership (via
associations) separate from the collected objects.  This is your "down
reference" scenario - however, your framework can enforce cleanup if the
group goes away (ie, all its associations go away).

And, having a concept of "preprovisioning" in your mgmt framework also
mitigates these problems.

Andrea

-----Original Message-----
From: nmrg-admin@ibr.cs.tu-bs.de [mailto:nmrg-admin@ibr.cs.tu-bs.de]On
Behalf Of David T. Perkins
Sent: Tuesday, February 12, 2002 11:20 AM
To: nmrg@ibr.cs.tu-bs.de
Subject: [nmrg] Thoughts about configuration...


HI,

In some present work, I've noticed two major patterns in defining
configuration info and wanted to present them to get some feedback.

At the high level, the very simple configuration question is
"how do you specify group membership"?

There are many examples in configuration of network devices where
one "creates a group", and then "adds" or "deletes" members. I've
run across two approaches.

1) members are specified as a property of the group. (lets say that
   the group has "down pointers" (or "down references") to members)
2) candidates for group membership specify as one of their properties
   the name of the group that they are a member. (lets say that
   that the member has an "up pointer" (or "up references") to the
   group)

Now the fun stuff.
The next concern is "referential integrity", that is, can a reference
be made to a non-existing member or group? This becomes complicated
when a network system allows "hot removal and insertion", and
"pre-provisioning". For example, consider a device that functions
as a bridge that allows VLANs to be created. A VLAN is configured
to contain ports. Network traffic is bridged between ports in a
VLAN, but not to other ports on the device. Now say port 9 is configured
as a member of VLAN c1. What happens when the network interface card
containing port 9 is removed? If after removal, the system is rebooted,
does this change anything? If after removal, a different type of
network interface card is inserted? Does this change the situation?
If a port can be a member of only a single VLAN (which in this
simple example, must be the case, but when using 802.1q, this is
not required), what happens when down pointers are used and
a port is configured as a member of multiple VLANs?

There are examples of commercial products that use down pointers
and ones that use up pointers. Also, there are examples of commercial
products that have referential integrity checking, and ones that
don't. Also, note that when up pointers are used, status displays
of the group show the current members. And when down pointers are
used, status displays (sometimes, but not always) of a candidate
show group membership.

What are the implementation and usability tradeoffs with up vs
down pointers, and with using or not using referential integrity
enforcement?

Having this researched as described will help designers of
configuration interfaces (CLI, MIB, etc).

Reactions?

Regards,
/david t. perkins

--
!! This message is brought to you via the `nmrg' mailing list.
!! Please do not reply to this message to unsubscribe. To unsubscribe or
adjust
!! your settings, send a mail message to <nmrg-request@ibr.cs.tu-bs.de>
!! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg.



Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1EIUP3t022927 for <nmrg@ibr.cs.tu-bs.de>; Thu, 14 Feb 2002 19:30:26 +0100
Received: from dperkins-nb2.dsperkins.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id KAA29972; Thu, 14 Feb 2002 10:30:16 -0800 (PST)
Message-Id: <5.0.2.1.2.20020214095501.02caa5c0@mail4.bayarea.net>
X-Sender: dperkins@mail4.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Thu, 14 Feb 2002 10:29:46 -0800
To: nmrg@ibr.cs.tu-bs.de
From: "David T. Perkins" <dperkins@dsperkins.com>
In-Reply-To: <200202141635.g1EGZ3V30972@haerke.ibr.cs.tu-bs.de>
References: <3C6B97C1.6010806@ieee.org> <3C6B97C1.6010806@ieee.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [nmrg] Questions about management
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

HI,

On the question...

Juergen asked...
>     Why is network management different?
>
>I am asking myself again and again why there are so many special
>purpose technologies in the network management world and why there is
>so little reuse/adaptation of general purpose technologies and
>methodologies. Part of this discussion is probably an attempt to
>answer the question what kind of management technologies will (still?)
>be needed in 5-10 years from now. What of what we have now has the
>potential to survive, to evolve, and what is missing. Are there any
>radically new approaches out there they might impact things?

I've posed similar, but different questions, which might overlap
with yours.

Such as:
1) Q: Why is it difficult to define what needs to be managed?
   A: There are seemingly a very large number of ways to model
      a managed resource. Each resource has a potentially large
      number of attributes and actions that be associated with it.
      However, only after usage (operational experience) can one
      figure out the essential model, attributes, and actions.
      Also, only after the resource is incorporated into different
      devices and deployed in different environments can a
      standards writer develop a model that is easy to understand
      and supports management of the resource.
2) Q: Why is it difficult to create a management application (and/or
      platform)?
   A: Because there are multiple "customers" with different requirements.
      a) First "customer" is the audience of presentations where the
         management software is being used to show off the features
         of the managed device. The management software needs to be
         visually oriented (and possibly have sound), and be educational
         and somewhat entertaining. No need for scaling, just need
         to support a few devices. (Or sometimes for platforms, need
         to support a larger number of devices, but only a few attributes.)
         Don't really need to be able to do useful management.
      b) Second "customer" is the device evaluators in a "lab". They
         want the management app to help them set up one (or maybe
         a small number of devices) so that they can try out the device.
         Want "wizards" to help with configuration and basic trouble
         shooting. Don't need to be able to set all configuration
         attributes.
      c) Third "customer" is operators for a limited usage trial. They
         want the management app to help them set up the one (or more
         devices) and monitor the status of the device. Maybe keep some
         basic statistics. Possibly need some help in automation of
         configuration changes (this depends on what service the
         device performs). In general, it is OK to be somewhat dependent
         on human interaction for config changes, and monitoring of
         operation.
      d) Fourth "customer" is the operators of the device in a large
         scale deployment. They want the device to integrate with
         existing automation. The more that can be automated, the better.
         The management application for the device generally have no
         display (them self) because they are feeding "higher level"
         applications that have a display. Need attributes that
         help in capacity planning, and ones that help in predicting
         device or component failure. Device security is important.

3) Q: Who are the engineers that implement management in a device?
   A: Generally, at an organization where the technology is "leading
      edge", the technology is much more important than the management
      of the device. The result is that the best and brightest engineers
      are working on the technology, and not the management. The
      "management engineers" are generally the least experienced
      members of the team and socially rank just above the "test
      engineers". Note that to "apply management" for a device,
      the "management engineer" must become an expert in each of
      the technologies being used in the device. This is hard.

Comments?

Regards,
/david t. perkins
 
      



Received: from haerke.ibr.cs.tu-bs.de (IDENT:root@haerke.ibr.cs.tu-bs.de [134.169.34.84]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1EGZ33t018491; Thu, 14 Feb 2002 17:35:03 +0100
Received: (from schoenw@localhost) by haerke.ibr.cs.tu-bs.de (8.11.6/8.11.6) id g1EGZ3V30972; Thu, 14 Feb 2002 17:35:03 +0100
Date: Thu, 14 Feb 2002 17:35:03 +0100
Message-Id: <200202141635.g1EGZ3V30972@haerke.ibr.cs.tu-bs.de>
X-Authentication-Warning: haerke.ibr.cs.tu-bs.de: schoenw set sender to schoenw@ibr.cs.tu-bs.de using -f
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: <3C6B97C1.6010806@ieee.org> (jp.martin-flatin@ieee.org)
Subject: Re: [nmrg] 10th NMRG meeting
References:  <3C6B97C1.6010806@ieee.org>
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

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

J> I suggest we organize the 10th NMRG meeting on April 19-20, right
J> after NOMS. 

This proposal is fine with me.

So please, can people on this list please send a note whether they
plan to attend so that I can try to figure out the logistics we
need?

Regarding topics, I have seen the following proposals:

Dave Perkins:	alarms & alarm management
Dave Perkins:	convergence of entity mib model and M.3100 models
Jean-Philippe:	update on universal information modeling

I would like to add another topic:

     Why is network management different?

I am asking myself again and again why there are so many special
purpose technologies in the network management world and why there is
so little reuse/adaptation of general purpose technologies and
methodologies. Part of this discussion is probably an attempt to
answer the question what kind of management technologies will (still?)
be needed in 5-10 years from now. What of what we have now has the
potential to survive, to evolve, and what is missing. Are there any
radically new approaches out there they might impact things?

/js

-- 
Juergen Schoenwaelder      University of Osnabrueck
<schoenw@inf.uos.de>       Dept. of Mathematics and Computer Science
Phone: +49 541 969 2483    Albrechtstr. 28, 49069 Osnabrueck, Germany
Fax:   +49 541 969 2770    <http://www.informatik.uni-osnabrueck.de/>




Received: from mta13n.bluewin.ch (mta13n.bluewin.ch [195.186.1.206]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1EAww3t005061 for <nmrg@ibr.cs.tu-bs.de>; Thu, 14 Feb 2002 11:58:59 +0100
Received: from ieee.org (62.202.42.101) by mta13n.bluewin.ch (Bluewin AG 6.0.040) id 3C5AB3A700289C25 for nmrg@ibr.cs.tu-bs.de; Thu, 14 Feb 2002 11:58:57 +0100
Message-ID: <3C6B97C1.6010806@ieee.org>
Date: Thu, 14 Feb 2002 11:56:01 +0100
From: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
Reply-To: "J.P. Martin-Flatin" <jp.martin-flatin@ieee.org>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.7) Gecko/20011221
X-Accept-Language: en-us
MIME-Version: 1.0
To: IRTF Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [nmrg] 10th NMRG meeting
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

Hi,

I suggest we organize the 10th NMRG meeting on April 19-20, right after 
NOMS. During our mid-January discussion, we agreed that we needed two days 
to discuss the issues raised by David Perkins. On Mon 15, there are 
tutorials during the whole day. The IM 2003 TPC meeting will take most of 
Mon 15 afternoon and several of us will attend it, so we must avoid this 
time. Personally, I can't make it the week-end before NOMS, but I am free 
after NOMS. On Fri 19, only the morning is taken by tutorials for those who 
are interested. So, I think the best dates are 19-20.

Are you happy with these dates? Please answer soon: I need to confirm my 
airfares ASAP because there are very few flights to Florence from here.

Thanks
JP



Received: from riverstonenet.com (mail.riverstonenet.com [63.113.148.10]) by agitator.ibr.cs.tu-bs.de (8.12.1/8.12.1/Debian -2) with ESMTP id g1CJKBTS018723 for <nmrg@ibr.cs.tu-bs.de>; Tue, 12 Feb 2002 20:20:13 +0100
Received: from dperkins-nb2.dsperkins.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id LAA02011; Tue, 12 Feb 2002 11:20:03 -0800 (PST)
Message-Id: <5.0.2.1.2.20020212104546.02938430@mail4.bayarea.net>
X-Sender: dperkins@mail4.bayarea.net
X-Mailer: QUALCOMM Windows Eudora Version 5.0.2
Date: Tue, 12 Feb 2002 11:19:34 -0800
To: nmrg@ibr.cs.tu-bs.de
From: "David T. Perkins" <dperkins@dsperkins.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Subject: [nmrg] Thoughts about configuration...
Sender: nmrg-admin@ibr.cs.tu-bs.de
Errors-To: nmrg-admin@ibr.cs.tu-bs.de
X-BeenThere: nmrg@ibr.cs.tu-bs.de
X-Mailman-Version: 2.0.6
Precedence: bulk
List-Help: <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=help>
List-Post: <mailto:nmrg@ibr.cs.tu-bs.de>
List-Subscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=subscribe>
List-Id: Network Management Research Group <nmrg.ibr.cs.tu-bs.de>
List-Unsubscribe: <https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg>, <mailto:nmrg-request@ibr.cs.tu-bs.de?subject=unsubscribe>
List-Archive: <https://www.ibr.cs.tu-bs.de/pipermail/nmrg/>

HI,

In some present work, I've noticed two major patterns in defining
configuration info and wanted to present them to get some feedback.

At the high level, the very simple configuration question is
"how do you specify group membership"?

There are many examples in configuration of network devices where
one "creates a group", and then "adds" or "deletes" members. I've
run across two approaches.

1) members are specified as a property of the group. (lets say that
   the group has "down pointers" (or "down references") to members)
2) candidates for group membership specify as one of their properties
   the name of the group that they are a member. (lets say that
   that the member has an "up pointer" (or "up references") to the
   group)

Now the fun stuff. 
The next concern is "referential integrity", that is, can a reference
be made to a non-existing member or group? This becomes complicated
when a network system allows "hot removal and insertion", and 
"pre-provisioning". For example, consider a device that functions
as a bridge that allows VLANs to be created. A VLAN is configured
to contain ports. Network traffic is bridged between ports in a
VLAN, but not to other ports on the device. Now say port 9 is configured
as a member of VLAN c1. What happens when the network interface card
containing port 9 is removed? If after removal, the system is rebooted,
does this change anything? If after removal, a different type of
network interface card is inserted? Does this change the situation?
If a port can be a member of only a single VLAN (which in this
simple example, must be the case, but when using 802.1q, this is
not required), what happens when down pointers are used and
a port is configured as a member of multiple VLANs?

There are examples of commercial products that use down pointers
and ones that use up pointers. Also, there are examples of commercial
products that have referential integrity checking, and ones that
don't. Also, note that when up pointers are used, status displays
of the group show the current members. And when down pointers are
used, status displays (sometimes, but not always) of a candidate
show group membership.

What are the implementation and usability tradeoffs with up vs
down pointers, and with using or not using referential integrity
enforcement?

Having this researched as described will help designers of
configuration interfaces (CLI, MIB, etc).

Reactions?

Regards,
/david t. perkins