Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0SARejp022744 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Tue, 28 Jan 2003 11:27:40 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0SAReAa015300 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Tue, 28 Jan 2003 11:27:40 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0SAReXr015297; Tue, 28 Jan 2003 11:27:40 +0100 Date: Tue, 28 Jan 2003 11:27:40 +0100 Message-Id: <200301281027.h0SAReXr015297@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: strauss@ibr.cs.tu-bs.de CC: nmrg@ibr.cs.tu-bs.de In-reply-to: (message from Frank Strauss on 27 Jan 2003 21:19:42 +0100) Subject: Re: [nmrg] meeting plans status References: <200301271807.h0RI7mbi001280@hansa.ibr.cs.tu-bs.de> X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: >>>>> Frank Strauss writes: Frank> From the feedback upon your first topics proposal Frank> <200301101717.h0AHHqdn015190@hansa.ibr.cs.tu-bs.de> I got the Frank> impression that there is still high interest in measurements of Frank> real-world SNMP traffic. Does it make sense to share thoughts Frank> on the real problems with this effort (e.g., convincing Frank> operators to participate, attaching to the right link(s) in Frank> switched networks)? I plan to handle this topic under the subject "how do we proceed with other work items we agreed to work on in the past". I currently prefer to handle this subject at the BOF meeting since I hope to have actually more people in the BOF that might be interested and able to help. Also, I am trying to get the weekend meetings well focussed so that we really can dive into details. I have already filed a request for an NMRG BOF at IM 2003 and it is sitting in the queue of the BOF chair who needs to figure out the logistics. Once the BOF is approved, I am able to write up a more detailed agenda for the March meetings. /js -- Juergen Schoenwaelder Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0RKJgjp024701 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 27 Jan 2003 21:19:42 +0100 Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0RKJgAa005988 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 27 Jan 2003 21:19:42 +0100 Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0RKJgH4005985; Mon, 27 Jan 2003 21:19:42 +0100 From: Frank Strauss To: Juergen Schoenwaelder Cc: Network Management Research Group Subject: Re: [nmrg] meeting plans status References: <200301271807.h0RI7mbi001280@hansa.ibr.cs.tu-bs.de> Date: 27 Jan 2003 21:19:42 +0100 In-Reply-To: <200301271807.h0RI7mbi001280@hansa.ibr.cs.tu-bs.de> Message-ID: Lines: 14 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Hi! Juergen> [...] Does this plan make sense? Please comment. Sounds good to me. Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0RI7mjp005502 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 27 Jan 2003 19:07:48 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0RI7mAa001283 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 27 Jan 2003 19:07:48 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0RI7mbi001280; Mon, 27 Jan 2003 19:07:48 +0100 Date: Mon, 27 Jan 2003 19:07:48 +0100 Message-Id: <200301271807.h0RI7mbi001280@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: Network Management Research Group X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: Subject: [nmrg] meeting plans status 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Here is the list of positive (or potentially positive) responses I have received: Olivier Festor (LORIA-INRIA) Sa/So Emmanuel Nataf (LORIA-INRIA) Sa/So Juergen Schoenwaelder (University of Osnabrueck) Sa/So Frank Strauss (TU Braunschweig) Sa/So Bert Wijnen (Lucent Technologies) Sa/So 1) Aiko Pras (University of Twente) Sa/So 1) George Pavlou (University of Surrey) So David Harrington (Enterasys) Sa/So Margaret Wasserman (Wind River) Sa/So 2) 1) prefers to have Saturday a day off 2) not yet clear whether she can attend [Let me know if this list is incorrect so that I can fix it.] Given this distribution, what we could do is to have the main meeting on Sunday where we go into XML schema mapping details based on Frank's work and whatever input we receive before the meeting. On Saturday, we could sit together in a smaller group figuring out what we do with SMIng (or better discuss what we have figured out before the meeting what we do with SMIng). Since Olivier, Emmanuel (who wrote the Java SMIng implementation) and Frank are all there, we should have the critical mass in place. A discussion of what we do with the other unfinished work items could either go on the Sunday agenda or even be moved to the BOF (if we get one). Does this plan make sense? Please comment. /js -- Juergen Schoenwaelder Received: from ctron-dnm.enterasys.com (firewall-user@[12.25.1.120]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0QJ2ajo024611; Sun, 26 Jan 2003 20:02:36 +0100 Received: (from uucp@localhost) by ctron-dnm.enterasys.com (8.8.7/8.8.7) id OAA19319; Sun, 26 Jan 2003 14:15:09 -0500 (EST) Received: from unknown(134.141.79.124) by ctron-dnm.enterasys.com via smap (4.1) id xma019314; Sun, 26 Jan 03 14:14:22 -0500 Received: from NHROCCNC2.ets.enterasys.com ([134.141.79.122]) by NHROCAVG2.ets.enterasys.com with InterScan Messaging Security Suite for SMTP; Sun, 26 Jan 2003 14:02:18 -0500 Received: from nhrocmbx1.enterasys.com ([134.141.79.104]) by NHROCCNC2.ets.enterasys.com with Microsoft SMTPSVC(5.0.2195.4905); Sun, 26 Jan 2003 14:02:18 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.5762.3 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Subject: RE: [nmrg] meeting(s) in march Date: Sun, 26 Jan 2003 14:02:17 -0500 Message-ID: <6D745637A7E0F94DA070743C55CDA9BA25710E@NHROCMBX1.ets.enterasys.com> Thread-Topic: [nmrg] meeting(s) in march Thread-Index: AcLCAPMmK39GHUm9RiqdeV5kuDH3BgDbFaKQ From: "Harrington, David" To: "Juergen Schoenwaelder" , X-OriginalArrivalTime: 26 Jan 2003 19:02:18.0724 (UTC) FILETIME=[72C25240:01C2C56D] Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by agitator.ibr.cs.tu-bs.de id h0QJ2ajo024611 X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: I plan to attend both days. dbh > -----Original Message----- > From: Juergen Schoenwaelder [mailto:schoenw@ibr.cs.tu-bs.de] > Sent: Wednesday, January 22, 2003 5:27 AM > To: nmrg@ibr.cs.tu-bs.de > Subject: Re: [nmrg] meeting(s) in march > > > > >>>>> Juergen Schoenwaelder writes: > > Juergen> We now need to find agreement on how much time we want to > Juergen> spend on this. I have no problem to spend Saturday and Sunday > Juergen> but others might prefer to spend less time in order to enjoy > Juergen> the snow. We could also go for two days but limit the meeting > Juergen> time to say 6 hours per day. It also depends on whether > Juergen> people will actually be available on Saturday in Colorado > Juergen> Springs or whether they are still traveling into this > Juergen> area. Your input is welcome - otherwise I will flip a coin. > > To make the question cristal clear to everyone: > > Who will be able to attend a meeting on Saturday, March 22? > > Who will be able to attend a meeting on Sunday, March 23? > > So far only Olivier gave a clear response. Please give me your input > so that we can finalize the meeting date and to allow us to make > travel plans. > > /js > > -- > Juergen Schoenwaelder -- !! 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 !! 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.6/8.12.6/Debian-6Woody) with ESMTP id h0Q8bCjo008041; Sun, 26 Jan 2003 09:37:13 +0100 Received: by cosium01.intelliden.net with Internet Mail Service (5.5.2653.19) id ; Sun, 26 Jan 2003 01:37:06 -0700 Message-ID: <11AB6A3E2294E94DB47B67E1BC7ECFD812EF58@cosium02> From: John Strassner To: Juergen Schoenwaelder , nmrg@ibr.cs.tu-bs.de Subject: RE: [nmrg] meeting(s) in march Date: Sun, 26 Jan 2003 01:37:00 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C2C516.18710E50" X-Spam-Status: No, hits=0.2 required=5.0 tests=MIME_NULL_BLOCK,MAILTO_LINK version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: 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_01C2C516.18710E50 Content-Type: text/plain I can attend both days. 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: Wednesday, January 22, 2003 3:27 AM To: nmrg@ibr.cs.tu-bs.de Subject: Re: [nmrg] meeting(s) in march >>>>> Juergen Schoenwaelder writes: Juergen> We now need to find agreement on how much time we want to spend Juergen> on this. I have no problem to spend Saturday and Sunday but Juergen> others might prefer to spend less time in order to enjoy the Juergen> snow. We could also go for two days but limit the meeting time Juergen> to say 6 hours per day. It also depends on whether people will Juergen> actually be available on Saturday in Colorado Springs or Juergen> whether they are still traveling into this area. Your input is Juergen> welcome - otherwise I will flip a coin. To make the question cristal clear to everyone: Who will be able to attend a meeting on Saturday, March 22? Who will be able to attend a meeting on Sunday, March 23? So far only Olivier gave a clear response. Please give me your input so that we can finalize the meeting date and to allow us to make travel plans. /js -- Juergen Schoenwaelder -- !! 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 !! or look at https://www.ibr.cs.tu-bs.de/mailman/listinfo/nmrg. ------_=_NextPart_001_01C2C516.18710E50 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [nmrg] meeting(s) in march

I can attend both days.

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: Wednesday, January 22, 2003 3:27 AM
To: nmrg@ibr.cs.tu-bs.de
Subject: Re: [nmrg] meeting(s) in march



>>>>> Juergen Schoenwaelder = writes:

Juergen> We now need to find agreement on how much = time we want to spend
Juergen> on this. I have no problem to spend = Saturday and Sunday but
Juergen> others might prefer to spend less time = in order to enjoy the
Juergen> snow. We could also go for two days but = limit the meeting time
Juergen> to say 6 hours per day. It also depends = on whether people will
Juergen> actually be available on Saturday in = Colorado Springs or
Juergen> whether they are still traveling into = this area. Your input is
Juergen> welcome - otherwise I will flip a = coin.

To make the question cristal clear to = everyone:

Who will be able to attend a meeting on Saturday, = March 22?

Who will be able to attend a meeting on Sunday, March = 23?

So far only Olivier gave a clear response. Please = give me your input so that we can finalize the meeting date and to = allow us to make travel plans.

/js

--
Juergen Schoenwaelder    <http://www.informatik.uni-osnabrueck.de/schoenw/&g= t;


--
!! 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_01C2C516.18710E50-- Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0OFYEjo023119; Fri, 24 Jan 2003 16:34:14 +0100 Received: from zeus.cs.utwente.nl (zeus.cs.utwente.nl [130.89.10.12]) by utrhcs.cs.utwente.nl (8.12.5/8.12.5) with ESMTP id h0OFYCWx021253; Fri, 24 Jan 2003 16:34:12 +0100 (MET) Received: from ctit.utwente.nl (utip250 [130.89.12.39]) by zeus.cs.utwente.nl (8.12.5/8.12.5) with ESMTP id h0OFYA32020719; Fri, 24 Jan 2003 16:34:10 +0100 (MET) Message-ID: <3E315CF3.3070600@ctit.utwente.nl> Date: Fri, 24 Jan 2003 16:34:11 +0100 From: Aiko Pras User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Juergen Schoenwaelder CC: nmrg@ibr.cs.tu-bs.de Subject: Re: [nmrg] meeting(s) in march References: <200301201733.h0KHXBms018957@hansa.ibr.cs.tu-bs.de> <200301221026.h0MAQY80016953@hansa.ibr.cs.tu-bs.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Juergen Schoenwaelder wrote: > To make the question cristal clear to everyone: > > Who will be able to attend a meeting on Saturday, March 22? > > Who will be able to attend a meeting on Sunday, March 23? I'll be able to attend on both days. I like Bert's proposal to meet sunday only, however ;-) Aiko Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0ME77gQ024483 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Wed, 22 Jan 2003 15:07:07 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0ME77Aa022551 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Wed, 22 Jan 2003 15:07:07 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0ME77qM022547; Wed, 22 Jan 2003 15:07:07 +0100 Date: Wed, 22 Jan 2003 15:07:07 +0100 Message-Id: <200301221407.h0ME77qM022547@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: Network Management Research Group X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: Subject: [nmrg] more meeting info 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Someone asked where IM 2003 is located. I am not sure I posted the URL, so I do it now: http://www.im2003.org/ (Yes, this will be a very cool event with great keynotes, an outstanding technical program, lively panel discussion, in great facilities ... - but what else should I say? No, seriously, look at the program and form your own opinion.) Another question asked was who is actually invited to join the NMRG meetings. Well, certainly everybody who hangs around on this mailing list and who is willing to contribute. As usual, I am also open for suggestions who should be invited to join us and who could bring in specific expertise to make the meeting more productive. /js -- Juergen Schoenwaelder Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0MCCQgQ005801 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Wed, 22 Jan 2003 13:12:31 +0100 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0MCCKk04167; Wed, 22 Jan 2003 07:12:24 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Wed, 22 Jan 2003 13:12:19 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B155BAE1AF@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Juergen Schoenwaelder , nmrg@ibr.cs.tu-bs.de Subject: RE: [nmrg] meeting(s) in march Date: Wed, 22 Jan 2003 13:12:15 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: > To make the question cristal clear to everyone: > > Who will be able to attend a meeting on Saturday, March 22? > > Who will be able to attend a meeting on Sunday, March 23? > I can do both days, but would prefer a day off on the saturday (after a long week of IETF in SF) Bert Received: from phoebe.eim.surrey.ac.uk (phoebe.eim.surrey.ac.uk [131.227.74.4]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0MBIUgQ029736 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for ; Wed, 22 Jan 2003 12:18:31 +0100 Received: from hermes.ee.surrey.ac.uk ([131.227.88.10] ident=exim) by phoebe.eim.surrey.ac.uk with esmtp (Exim 3.33 #4) id 18bIrT-0003Fl-00 for nmrg@ibr.cs.tu-bs.de; Wed, 22 Jan 2003 11:16:03 +0000 Received: from ees2gp (helo=eim.surrey.ac.uk) by hermes.ee.surrey.ac.uk with local-esmtp (Exim 2.12 #5) id 18bIrR-0002mY-00 for nmrg@ibr.cs.tu-bs.de; Wed, 22 Jan 2003 11:16:01 +0000 To: nmrg@ibr.cs.tu-bs.de Subject: Re: [nmrg] meeting(s) in march In-Reply-To: Message from Juergen Schoenwaelder of "Wed, 22 Jan 2003 11:26:34 +0100." <200301221026.h0MAQY80016953@hansa.ibr.cs.tu-bs.de> Date: Wed, 22 Jan 2003 11:16:01 +0000 From: George Pavlou Message-Id: X-Spam-Level: X-Scanner: exiscan *18bIrT-0003Fl-00*NrvrBTVcewY* (SECM, UniS) X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: > Who will be able to attend a meeting on Saturday, March 22? > > Who will be able to attend a meeting on Sunday, March 23? I will be able to attend on Sunday. Rgs, -George Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0MAaJgQ023187 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Wed, 22 Jan 2003 11:36:19 +0100 Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0MAaJAa017369 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Wed, 22 Jan 2003 11:36:19 +0100 Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0MAaJRV017366; Wed, 22 Jan 2003 11:36:19 +0100 From: Frank Strauss To: Juergen Schoenwaelder Cc: nmrg@ibr.cs.tu-bs.de Subject: Re: [nmrg] meeting(s) in march References: <200301201733.h0KHXBms018957@hansa.ibr.cs.tu-bs.de> <200301221026.h0MAQY80016953@hansa.ibr.cs.tu-bs.de> Date: 22 Jan 2003 11:36:19 +0100 In-Reply-To: <200301221026.h0MAQY80016953@hansa.ibr.cs.tu-bs.de> Message-ID: Lines: 8 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Hi! Juergen> Who will be able to attend a meeting on Saturday, March 22? Juergen> Who will be able to attend a meeting on Sunday, March 23? Both days are fine with me. -frank Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0MAQZgQ021603 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Wed, 22 Jan 2003 11:26:35 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0MAQYAa016956 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Wed, 22 Jan 2003 11:26:35 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0MAQY80016953; Wed, 22 Jan 2003 11:26:34 +0100 Date: Wed, 22 Jan 2003 11:26:34 +0100 Message-Id: <200301221026.h0MAQY80016953@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: nmrg@ibr.cs.tu-bs.de In-reply-to: <200301201733.h0KHXBms018957@hansa.ibr.cs.tu-bs.de> (message from Juergen Schoenwaelder on Mon, 20 Jan 2003 18:33:11 +0100) Subject: Re: [nmrg] meeting(s) in march References: <200301201733.h0KHXBms018957@hansa.ibr.cs.tu-bs.de> X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: >>>>> Juergen Schoenwaelder writes: Juergen> We now need to find agreement on how much time we want to Juergen> spend on this. I have no problem to spend Saturday and Sunday Juergen> but others might prefer to spend less time in order to enjoy Juergen> the snow. We could also go for two days but limit the meeting Juergen> time to say 6 hours per day. It also depends on whether Juergen> people will actually be available on Saturday in Colorado Juergen> Springs or whether they are still traveling into this Juergen> area. Your input is welcome - otherwise I will flip a coin. To make the question cristal clear to everyone: Who will be able to attend a meeting on Saturday, March 22? Who will be able to attend a meeting on Sunday, March 23? So far only Olivier gave a clear response. Please give me your input so that we can finalize the meeting date and to allow us to make travel plans. /js -- Juergen Schoenwaelder Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0L9tkgQ032516 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Tue, 21 Jan 2003 10:55:47 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0L9tkAa026343 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Tue, 21 Jan 2003 10:55:46 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0L9tk9L026340; Tue, 21 Jan 2003 10:55:46 +0100 Date: Tue, 21 Jan 2003 10:55:46 +0100 Message-Id: <200301210955.h0L9tk9L026340@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: strauss@ibr.cs.tu-bs.de CC: david.durham@intel.com, nmrg@ibr.cs.tu-bs.de In-reply-to: (message from Frank Strauss on 20 Jan 2003 23:49:21 +0100) Subject: Re: [nmrg] nmrg plans for 2003 References: X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: >>>>> Frank Strauss writes: DaveD> [DaveD] I would certainly like to see the current sming I-Ds DaveD> completed suitable for publication. I think the SMIng documents DaveD> need to be preserved as an effective approach to deal with the DaveD> increasing entropy of the O&M data models. And, as mentioned, DaveD> there is running code available for sming. Frank> Just to avoid a false assumption: The SMIng code that is Frank> available in libsmi is based on the pre-NMRG proposal. I.e., it Frank> does not support the class construct and the separation of Frank> protocol independant data structures and protocol mappings. And Frank> it would also require some work to get it working again with Frank> the rest of the libsmi infrastructure as it developed over the Frank> past three years (yes it's really that old!). To add to this: We have experimental code which implements one of the newer specs written by a student which is however not part of the distribution and which requires work to make it production quality. But there is another implementation done in France which I think is closer to the newer SMIng specs (and written in Java). /js -- Juergen Schoenwaelder Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0KMnMgQ003298 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 20 Jan 2003 23:49:22 +0100 Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0KMnLAa023739 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 20 Jan 2003 23:49:22 +0100 Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0KMnLkD023736; Mon, 20 Jan 2003 23:49:21 +0100 From: Frank Strauss To: "Durham, David" Cc: Network Management Research Group Subject: Re: [nmrg] nmrg plans for 2003 References: Date: 20 Jan 2003 23:49:21 +0100 In-Reply-To: Message-ID: Lines: 16 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Hi! DaveD> [DaveD] I would certainly like to see the current sming I-Ds completed DaveD> suitable for publication. I think the SMIng documents need to be DaveD> preserved as an effective approach to deal with the increasing entropy DaveD> of the O&M data models. And, as mentioned, there is running code DaveD> available for sming. Just to avoid a false assumption: The SMIng code that is available in libsmi is based on the pre-NMRG proposal. I.e., it does not support the class construct and the separation of protocol independant data structures and protocol mappings. And it would also require some work to get it working again with the rest of the libsmi infrastructure as it developed over the past three years (yes it's really that old!). -frank Received: from caduceus.fm.intel.com (fmr02.intel.com [192.55.52.25]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0KJgrgP008650; Mon, 20 Jan 2003 20:42:57 +0100 Received: from talaria.fm.intel.com (talaria.fm.intel.com [10.1.192.39]) by caduceus.fm.intel.com (8.11.6/8.11.6/d: outer.mc,v 1.51 2002/09/23 20:43:23 dmccart Exp $) with ESMTP id h0KJbDf12410; Mon, 20 Jan 2003 19:37:13 GMT Received: from fmsmsxv040-1.fm.intel.com (fmsmsxvs040.fm.intel.com [132.233.42.124]) by talaria.fm.intel.com (8.11.6/8.11.6/d: inner.mc,v 1.28 2003/01/13 19:44:39 dmccart Exp $) with SMTP id h0KJikf10809; Mon, 20 Jan 2003 19:44:46 GMT Received: from fmsmsx26.fm.intel.com ([132.233.42.26]) by fmsmsxv040-1.fm.intel.com (NAVGW 2.5.2.11) with SMTP id M2003012011430830815 ; Mon, 20 Jan 2003 11:43:08 -0800 Received: by fmsmsx26.fm.intel.com with Internet Mail Service (5.5.2653.19) id ; Mon, 20 Jan 2003 11:42:47 -0800 Message-ID: From: "Durham, David" To: "Durham, David" , Olivier Festor , Juergen Schoenwaelder , Network Management Research Group Subject: RE: [nmrg] nmrg plans for 2003 Date: Mon, 20 Jan 2003 11:42:39 -0800 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) content-class: urn:content-classes:message Content-Type: text/plain; charset="iso-8859-1" X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: > -----Original Message----- > From: Olivier Festor [mailto:Olivier.Festor@loria.fr] > > 4) SMIng : Emmanuel Nataf, who actually did the SMIng JMX tool will be > at IM. He is probably interested in contributing and can meet some of > you there. He will probably stay at Colorado Springs for the NMRG > meeting if we all agree that he is authroized to participate to this > specific meeting. What do you think about that ? > > -----Original Message----- > From: Frank Strauss [mailto:strauss@ibr.cs.tu-bs.de] > > Turning the current I-D documents into something that could probably > be published as an Informational RFC might make sense. Working on an > article looks less reasonable to me. Just my thoughts. I could spend > some time on it. [DaveD] I would certainly like to see the current sming I-Ds completed suitable for publication. I think the SMIng documents need to be preserved as an effective approach to deal with the increasing entropy of the O&M data models. And, as mentioned, there is running code available for sming. Unfortunately, anything dealing with SNMP these days seems to suffer from a blight of participation. On the positive side, this may be viewed as an opportunity for a small community of individuals to make the necessary improvements to keep these standards viable. Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0KHXBgQ020618 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 20 Jan 2003 18:33:11 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0KHXBAa018960 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Mon, 20 Jan 2003 18:33:11 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0KHXBms018957; Mon, 20 Jan 2003 18:33:11 +0100 Date: Mon, 20 Jan 2003 18:33:11 +0100 Message-Id: <200301201733.h0KHXBms018957@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: Network Management Research Group X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: Subject: [nmrg] meeting(s) in march 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Given the feedback, I propose to actually hold two meetings in March. Here is what I have in mind: The first meeting will be a BOF at IM 2003. The idea here is to allow IM attendees to join us in an informal get together and to chat about what the NMRG is, what it has done, what future plans are or might be and so on. I would like to use this BOF to see whether there is any new blood out there which might be interested to work with us. The second meeting will be held the weekend before IM 2003. We could use Saturday (March 22) and Sunday (March 23) (or parts of these days). This would be a technical meeting. A draft agenda might be: 0. Welcome and agenda bashing 1. Status reports and plans to drop/finish open work items 2. Reports on recent work by various NMRG contributors 2.1 Frank's work on SMI to XML schema mappings 2.2 Frank's work on SNMP to XML translators 2.3 Juergen's work on SMI MIB metrics 2.4 Olivier's work on ... 2.5 Aiko's work on ... 2.6 ... 3. Actions plans, wrap up The idea is to get a better overview what people are doing and to challenge ideas with tough questions. Especially Frank's work seems to be ready for that. We now need to find agreement on how much time we want to spend on this. I have no problem to spend Saturday and Sunday but others might prefer to spend less time in order to enjoy the snow. We could also go for two days but limit the meeting time to say 6 hours per day. It also depends on whether people will actually be available on Saturday in Colorado Springs or whether they are still traveling into this area. Your input is welcome - otherwise I will flip a coin. /js -- Juergen Schoenwaelder Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0GHU0BF008669 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Thu, 16 Jan 2003 18:30:00 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0GHU0Aa001129 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Thu, 16 Jan 2003 18:30:00 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0GHU08c001126; Thu, 16 Jan 2003 18:30:00 +0100 Date: Thu, 16 Jan 2003 18:30:00 +0100 Message-Id: <200301161730.h0GHU08c001126@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: Network Management Research Group X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: Subject: [nmrg] rfc 3444 published 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: We finally got another document published: : Network Working Group A. Pras : Request for Comments: 3444 University of Twente : Category: Informational J. Schoenwaelder : University of Osnabrueck : January 2003 : : On the Difference between : Information Models and Data Models Thanks to all contributors. /js -- Juergen Schoenwaelder Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0GDDan0031906 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Thu, 16 Jan 2003 14:13:36 +0100 Received: from hansa.ibr.cs.tu-bs.de (strauss@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0GDDaAa028324 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Thu, 16 Jan 2003 14:13:36 +0100 Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0GDDaML028321; Thu, 16 Jan 2003 14:13:36 +0100 From: Frank Strauss To: Network Management Research Group Subject: Re: [nmrg] nmrg plans for 2003 References: <200301101717.h0AHHqdn015190@hansa.ibr.cs.tu-bs.de> Date: 16 Jan 2003 14:13:36 +0100 In-Reply-To: <200301101717.h0AHHqdn015190@hansa.ibr.cs.tu-bs.de> Message-ID: Lines: 77 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Status: No, hits=-4.4 required=5.0 tests=IN_REP_TO version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Hi! Juergen> I thought it would be a good idea to make plans what the NMRG wants Juergen> to achieve this year. In particular, we have some more or less Juergen> concrete things people signed up for or which we wanted to work on Juergen> and we need to see where we stand. Juergen> 1 NMRG Osnabrueck meeting minutes: Aiko signed up for this. Aiko, what Juergen> is the status? When can we expect them to get online? Juergen> 2 Web services followup work: Do we plan for a meeting? If yes, we Juergen> could hold a meeting next to IM 2003 since I think that many of us Juergen> will be there anyway. Comments? Though my traveling plans are unclear, *if* I'll get to IM, I'll attend the meeting. Although Aiko's and Olivier's work is at its beginning, I think it would make sense to talk about slightly improved ideas and visions, anyway. Oliver Bohle, student at TU Braunschweig, just started work on his master thesis where his task is to (1) analyze one or two typical "management problems", (2) analyze the "traditional SNMP solution", and (3) propose and evaluate a WebServices based solution. Maybe, in march there is something more I can tell about it. Juergen> 3 SMI XML work (see the smixml mailing list) and SMI XML schema work Juergen> (basically Frank's and Thorsten's work on the xsd output driver of Juergen> smidump). Should the NMRG want to get involved into this? How Juergen> relevant is it related to 2? I could tell about our SMI-to-XML-Schema mapping (presented at IM) and also on our follow-up work for an SNMP/XML gateway which is currently being developed by another student at TU Braunschweig, Jens Mueller. I'd appreciate a discussion on this stuff. Juergen> 4 The debacle of SMIng and what does the NMRG do? Any interests and Juergen> resources to finish the NMRG proposal in order to get it published Juergen> rather than completely lost? Turning the current I-D documents into something that could probably be published as an Informational RFC might make sense. Working on an article looks less reasonable to me. Just my thoughts. I could spend some time on it. Juergen> 5 Old stuff: What do we do with other unfinished documents? Do we let Juergen> them just go away or do we try to get at least something out of it? Juergen> For example, I could imagine to publish a paper on the OID Juergen> compression somewhere so that the idea is not getting lost. Anyone Juergen> interested to contribute? Sorry, no active interest. Juergen> 6 In the Pisa meeting, we decided that it would be worth to make Juergen> measurements in real networks to better understand usage patterns of Juergen> SNMP in life networks. There was some followup on this, but nothing Juergen> where we got real data. Are people still interested in this? Interested: definetely! But still skeptical, whether it's doable, since most network are switched and run in full-duplex, so that it's not trivial to attach a sniffer next to, e.g., a central NMS. Anyway, I'd appreciate the effort very much. I think, a good document reasoning the effort and explaining how it works and how it does not affect the target site's security, as well as a well structured source code base, would be important. Juergen> 7 Anything else we should look at? Perhaps doing more work on nifty Juergen> algorithms to avoid as much explicit management as possible? I'd like to discuss the issues mentioned by Olivier. Juergen> Please comment on these issues. In particular, if we want to meet next Juergen> to IM 2003, we should work out the logistics and the agenda we want to Juergen> cover soon so that people can make their travel plans accordingly. -frank Received: from macker.loria.fr (macker.loria.fr [152.81.1.70]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0FJLxmx005181; Wed, 15 Jan 2003 20:22:02 +0100 Received: from localhost.loria.fr (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 913BA77D9; Wed, 15 Jan 2003 20:21:52 +0100 (MET) X-Amavix: Anti-virus check done by McAfee X-Amavix: Scanned by Amavix Received: from loria.fr (theboss.loria.fr [152.81.15.208]) by macker.loria.fr (Postfix) with ESMTP id 5E66777D9; Wed, 15 Jan 2003 20:21:51 +0100 (MET) Message-ID: <3E25B4CA.4040007@loria.fr> Date: Wed, 15 Jan 2003 20:21:46 +0100 From: Olivier Festor Organization: The MADYNES Research Team User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.2) Gecko/20021120 Netscape/7.01 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Juergen Schoenwaelder , Network Management Research Group Cc: Olivier.Festor@loria.fr Subject: Re: [nmrg] nmrg plans for 2003 References: <200301101717.h0AHHqdn015190@hansa.ibr.cs.tu-bs.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Hello all , 2) Great for an IM co-located meeting. All I need is a fast decision on the date (before ? , after ?) because plane tickets are still affordable and I want to buy them by the end of next week. Concerning XML, we are in the same situation as Aiko, i.e. doing some work in the area of Web Services without revolutionary stuff to present so far, thus not worth discussing in the current situation. 4) SMIng : Emmanuel Nataf, who actually did the SMIng JMX tool will be at IM. He is probably interested in contributing and can meet some of you there. He will probably stay at Colorado Springs for the NMRG meeting if we all agree that he is authroized to participate to this specific meeting. What do you think about that ? 6) measurments: DEFINTIVELY INTERESTING. I dream of a model that tells me what the management cost is. 7) nifty algorithms to avoid explicit management : Yes Lets start a working group on SMI: the Structure for Management Inexistence and another on SNMP : The Structure for Non Management Proliferation :-) On this subject, we are working in Nancy on self-configuration of management agents. This problem becomes more and more important in the context of nomadic computing, multi-homed entities, ad hoc networks. I saw a first effort in the context of alarm issuance (i.e. where to send alarms) but the scope that needs to be addressed is bigger : security settings & access control : what can be seen by whoom in which context, what alarm to which manager (in a multi-homed environment, ...) . In the scope of new groups on self-configurating routers, zeroconf whatever within IETF, it is probably worth that the NMRG looks at these issues. I am willing to participate actively in this area. Best Regards, Olivier Festor Juergen Schoenwaelder wrote: >I thought it would be a good idea to make plans what the NMRG wants >to achieve this year. In particular, we have some more or less >concrete things people signed up for or which we wanted to work on >and we need to see where we stand. > >1 NMRG Osnabrueck meeting minutes: Aiko signed up for this. Aiko, what > is the status? When can we expect them to get online? > >2 Web services followup work: Do we plan for a meeting? If yes, we > could hold a meeting next to IM 2003 since I think that many of us > will be there anyway. Comments? > >3 SMI XML work (see the smixml mailing list) and SMI XML schema work > (basically Frank's and Thorsten's work on the xsd output driver of > smidump). Should the NMRG want to get involved into this? How > relevant is it related to 2? > >4 The debacle of SMIng and what does the NMRG do? Any interests and > resources to finish the NMRG proposal in order to get it published > rather than completely lost? > >5 Old stuff: What do we do with other unfinished documents? Do we let > them just go away or do we try to get at least something out of it? > For example, I could imagine to publish a paper on the OID > compression somewhere so that the idea is not getting lost. Anyone > interested to contribute? > >6 In the Pisa meeting, we decided that it would be worth to make > measurements in real networks to better understand usage patterns of > SNMP in life networks. There was some followup on this, but nothing > where we got real data. Are people still interested in this? > >7 Anything else we should look at? Perhaps doing more work on nifty > algorithms to avoid as much explicit management as possible? > >Please comment on these issues. In particular, if we want to meet next >to IM 2003, we should work out the logistics and the agenda we want to >cover soon so that people can make their travel plans accordingly. > >/js > > > Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0E9j7T3024731; Tue, 14 Jan 2003 10:45:07 +0100 Received: from zeus.cs.utwente.nl (zeus.cs.utwente.nl [130.89.10.12]) by utrhcs.cs.utwente.nl (8.12.5/8.12.5) with ESMTP id h0E9j5Wx018862; Tue, 14 Jan 2003 10:45:05 +0100 (MET) Received: from cs.utwente.nl (utip250 [130.89.12.39]) by zeus.cs.utwente.nl (8.12.5/8.12.5) with ESMTP id h0E9j13R027541; Tue, 14 Jan 2003 10:45:01 +0100 (MET) Message-ID: <3E23DC1E.5040509@cs.utwente.nl> Date: Tue, 14 Jan 2003 10:45:02 +0100 From: Aiko Pras User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.0.1) Gecko/20020823 Netscape/7.0 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Juergen Schoenwaelder CC: Network Management Research Group Subject: Re: [nmrg] nmrg plans for 2003 References: <200301101717.h0AHHqdn015190@hansa.ibr.cs.tu-bs.de> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.org/) X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: Juergen Schoenwaelder wrote: > 1 NMRG Osnabrueck meeting minutes: Aiko signed up for this. Aiko, what > is the status? When can we expect them to get online? Should be ready soon (this month) > 2 Web services followup work: Do we plan for a meeting? If yes, we > could hold a meeting next to IM 2003 since I think that many of us > will be there anyway. Comments? A meeting next to IM would be a good oppertunity. At our institute we do follow-up work, but that is still in an early stage and I don't have many things to tell. > > 3 SMI XML work (see the smixml mailing list) and SMI XML schema work > (basically Frank's and Thorsten's work on the xsd output driver of > smidump). Should the NMRG want to get involved into this? How > relevant is it related to 2? This has always been one of the NMRG activities. It still fits well. > 4 The debacle of SMIng and what does the NMRG do? Any interests and > resources to finish the NMRG proposal in order to get it published > rather than completely lost? It should somehow get published. I can not be of much help, I'm affraid ... > 5 Old stuff: What do we do with other unfinished documents? Do we let > them just go away or do we try to get at least something out of it? > For example, I could imagine to publish a paper on the OID > compression somewhere so that the idea is not getting lost. Anyone > interested to contribute? Some of that stuff would be OK for a paper. I would be interested to contribute somehow. > 6 In the Pisa meeting, we decided that it would be worth to make > measurements in real networks to better understand usage patterns of > SNMP in life networks. There was some followup on this, but nothing > where we got real data. Are people still interested in this? We do measurements in real networks (like the campusnet and the dutch research network). The problem is that not much usefull SNMP stuff is happening there. In fact the measurements should have been performed on "the same wire" as to which the management stations are connected. This is hardly do-able > 7 Anything else we should look at? Perhaps doing more work on nifty > algorithms to avoid as much explicit management as possible? Depends. If people are working on this and want to report, then let's do it. Something else: in Europe several people are working on a so-called network of excellence in this area. I believe we should try to integrate that work, as far as feasable, in our NMRG work. Aiko Received: from hoemail1.firewall.lucent.com (hoemail1.lucent.com [192.11.226.161]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0ANQ7BU006124 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Sat, 11 Jan 2003 00:26:08 +0100 Received: from nl0006exch001h.wins.lucent.com (h135-85-76-62.lucent.com [135.85.76.62]) by hoemail1.firewall.lucent.com (Switch-2.2.2/Switch-2.2.0) with ESMTP id h0ANPxO01216; Fri, 10 Jan 2003 18:26:00 -0500 (EST) Received: by nl0006exch001h.nl.lucent.com with Internet Mail Service (5.5.2653.19) id ; Sat, 11 Jan 2003 00:25:59 +0100 Message-ID: <7D5D48D2CAA3D84C813F5B154F43B15598A505@nl0006exch001u.nl.lucent.com> From: "Wijnen, Bert (Bert)" To: Juergen Schoenwaelder , Network Management Research Group Subject: RE: [nmrg] nmrg plans for 2003 Date: Sat, 11 Jan 2003 00:25:58 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: W.r.t. meeting next to IM2003, I can be there if we do it before the IM2003 (that is in between the IETF and IM meetings). I prefer not to stay for yet another weekend away from home if you were to do it after IM2003. Thanks, Bert Received: from hansa.ibr.cs.tu-bs.de (hansa.ibr.cs.tu-bs.de [134.169.34.81]) by agitator.ibr.cs.tu-bs.de (8.12.6/8.12.6/Debian-6Woody) with ESMTP id h0AHHqBU019698 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Fri, 10 Jan 2003 18:17:52 +0100 Received: from hansa.ibr.cs.tu-bs.de (schoenw@localhost [127.0.0.1]) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) with ESMTP id h0AHHqAa015193 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=FAIL); Fri, 10 Jan 2003 18:17:52 +0100 Received: (from schoenw@localhost) by hansa.ibr.cs.tu-bs.de (8.12.3/8.12.3/Debian -4) id h0AHHqdn015190; Fri, 10 Jan 2003 18:17:52 +0100 Date: Fri, 10 Jan 2003 18:17:52 +0100 Message-Id: <200301101717.h0AHHqdn015190@hansa.ibr.cs.tu-bs.de> From: Juergen Schoenwaelder To: Network Management Research Group X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20 X-Spam-Level: Subject: [nmrg] nmrg plans for 2003 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.11 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Network Management Research Group List-Unsubscribe: , List-Archive: I thought it would be a good idea to make plans what the NMRG wants to achieve this year. In particular, we have some more or less concrete things people signed up for or which we wanted to work on and we need to see where we stand. 1 NMRG Osnabrueck meeting minutes: Aiko signed up for this. Aiko, what is the status? When can we expect them to get online? 2 Web services followup work: Do we plan for a meeting? If yes, we could hold a meeting next to IM 2003 since I think that many of us will be there anyway. Comments? 3 SMI XML work (see the smixml mailing list) and SMI XML schema work (basically Frank's and Thorsten's work on the xsd output driver of smidump). Should the NMRG want to get involved into this? How relevant is it related to 2? 4 The debacle of SMIng and what does the NMRG do? Any interests and resources to finish the NMRG proposal in order to get it published rather than completely lost? 5 Old stuff: What do we do with other unfinished documents? Do we let them just go away or do we try to get at least something out of it? For example, I could imagine to publish a paper on the OID compression somewhere so that the idea is not getting lost. Anyone interested to contribute? 6 In the Pisa meeting, we decided that it would be worth to make measurements in real networks to better understand usage patterns of SNMP in life networks. There was some followup on this, but nothing where we got real data. Are people still interested in this? 7 Anything else we should look at? Perhaps doing more work on nifty algorithms to avoid as much explicit management as possible? Please comment on these issues. In particular, if we want to meet next to IM 2003, we should work out the logistics and the agenda we want to cover soon so that people can make their travel plans accordingly. /js -- Juergen Schoenwaelder