
Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id KAA25666 for nmrg-outgoing; Wed, 9 May 2001 10:54:11 +0200 (MET DST)
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id KAA25645; Wed, 9 May 2001 10:54:07 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id KAA25237; Wed, 9 May 2001 10:54:06 +0200
Date: Wed, 9 May 2001 10:54:06 +0200
Message-Id: <200105090854.KAA25237@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: nmrg@ibr.cs.tu-bs.de
CC: andreaw@cisco.com
In-reply-to: <GGEOLLMKEOKMFKADFNHOEEGCDLAA.andreaw@cisco.com>
Subject: Re: [nmrg] Unable to locate a PC Projector for Saturday's Meeting
References:  <GGEOLLMKEOKMFKADFNHOEEGCDLAA.andreaw@cisco.com>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

>>>>> Andrea Westerinen writes:

Andrea> My apologies but I have been unable to get a PC-LCD projector
Andrea> for Saturday.  The Cisco office's projector is in use on
Andrea> Saturday, and the hotel charges $550 USD per day!  (Cisco
Andrea> won't ok this charge.)  We will have a projector on Sunday
Andrea> only - compliments of the IM2001 conference.  We will have a
Andrea> flip chart on both days.

Andrea> If anyone has other ideas regarding locating a projector, let
Andrea> me know and I will get the room set up on Saturday to
Andrea> accomodate it.

So unless someone happens to find a projector in his luggage, we will
just do without one on Saturday. I know that Aiko is good at making
drawings on ordinary white boards - so I expect that this will not be
a big problem.

/js

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




Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id TAA11412 for nmrg-outgoing; Tue, 8 May 2001 19:56:56 +0200 (MET DST)
Received: from sj-msg-core-2.cisco.com (sj-msg-core-2.cisco.com [171.69.24.11]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id TAA11406 for <nmrg@ibr.cs.tu-bs.de>; Tue, 8 May 2001 19:56:54 +0200 (MET DST)
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 f48HuLH15938 for <nmrg@ibr.cs.tu-bs.de>; Tue, 8 May 2001 10:56:21 -0700 (PDT)
Received: from andreawlap (andreaw-frame1.cisco.com [10.19.253.186]) by mira-sjcm-2.cisco.com (Mirapoint) with SMTP id AAB13343; Tue, 8 May 2001 10:56:16 -0700 (PDT)
From: "Andrea Westerinen" <andreaw@cisco.com>
To: "Network Management Research Group" <nmrg@ibr.cs.tu-bs.de>
Subject: [nmrg] Unable to locate a PC Projector for Saturday's Meeting
Date: Tue, 8 May 2001 10:58:13 -0700
Message-ID: <GGEOLLMKEOKMFKADFNHOEEGCDLAA.andreaw@cisco.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
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)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

My apologies but I have been unable to get a PC-LCD projector for Saturday.
The Cisco office's projector is in use on Saturday, and the hotel charges
$550 USD per day!  (Cisco won't ok this charge.)  We will have a projector
on Sunday only - compliments of the IM2001 conference.  We will have a flip
chart on both days.

If anyone has other ideas regarding locating a projector, let me know and I
will get the room set up on Saturday to accomodate it.

Andrea



Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id OAA14975 for nmrg-outgoing; Wed, 2 May 2001 14:27:41 +0200 (MET DST)
Received: from hansa.ibr.cs.tu-bs.de (IDENT:root@hansa [134.169.34.137]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id OAA14967; Wed, 2 May 2001 14:27:39 +0200 (MET DST)
Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.9.3/8.9.3) id OAA11009; Wed, 2 May 2001 14:27:38 +0200
X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: strauss set sender to strauss@ibr.cs.tu-bs.de using -f
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Aiko Pras <pras@ctit.utwente.nl>
Cc: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>, szabolcs boros <boros@cs.utwente.nl>, Bert Helthuis <helthuis@cs.utwente.nl>
Subject: Re: [nmrg] 9th nmrg meeting agenda (tentative)
References: <3AEFCFAF.A8362008@ctit.utwente.nl>
Date: 02 May 2001 14:27:38 +0200
In-Reply-To: <3AEFCFAF.A8362008@ctit.utwente.nl>
Message-ID: <ypwg0eoq6kl.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 58
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Hi!

>> Aiko, I'd like to let you know in advance of the meeting, what I had
>> in mind some time ago. Here is a part of a mail I've sent some time
>> ago when you first announced your work on the MIB lookup service...
>> 
>> This sounds interesting to me, especially if you would intend to
>> build it on top of (or even integrated with) the libsmi. ;-)

Aiko> Our current prototype is already using libsmi. We have made some stuff
Aiko> as "post-processor" around it (to make things faster). Libsmi does the
Aiko> initial conversion of MIB modules into an intermediate format. From than
Aiko> on the "post processor" uses the intermediate format. 
Aiko> It is nice, however, that you're thinking on this too and I'm looking
Aiko> forward to discuss with you (and others) how we've implemented things. 

What I have in mind, is to keep using the libsmi being the interface
that the management applications use. Just the libsmi input drivers
are extended to support some kind of an `SMI protocol'. 


>> In the early days of the libsmi design I had a similar idea:    
>> 
>> (a) a server that is built on top of the SMI library, that 
>> serves connecting clients that use the server to serve 
>> SMI related requests.
>> 
>> (b) a libsmi input driver that makes the library talks to such a
>> server (or even a list of servers, if the first one doesn't 
>> know the answer) if the configured SMIPATH is configured
>> appropriately.
>> 
>> This rough idea looked very nice to me, but soon a number of 
>> problems became visible and we shelved this plan.

Aiko> I'm interested in the problems you've found. We've identified a couple
Aiko> of problems, but have the impression we know how to deal with them. We
Aiko> could be wrong ;-(

The problems I remember were concerned with 

  - the granularity of SMI lookup requests that would cause really bad
    performance,
  - the memory management; currently libsmi return pointers to structs
    that are allocated once when a module is parsed,
  - the scoping of definitions that could be found on a number of
    servers,
  - the decision which server should be queried for lookups by OID only.

I must admit that I did not spent more detailed thoughts on these
questions, because at the time of disigning the libsmi I was lucky
enough with what we had at that time.

Later I started thinking about the possibility to retrieve and cache
just whole modules from remote servers, but again there are no
detailed plans or implementation efforts yet.

 -frank


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id MAA06706 for nmrg-outgoing; Wed, 2 May 2001 12:15:01 +0200 (MET DST)
Received: from hansa.ibr.cs.tu-bs.de (IDENT:root@hansa [134.169.34.137]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id MAA06691; Wed, 2 May 2001 12:14:58 +0200 (MET DST)
Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.9.3/8.9.3) id MAA03065; Wed, 2 May 2001 12:14:58 +0200
X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: strauss set sender to strauss@ibr.cs.tu-bs.de using -f
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Aiko Pras <pras@ctit.utwente.nl>
Cc: szabolcs boros <boros@cs.utwente.nl>, Bert Helthuis <helthuis@cs.utwente.nl>, Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de> <3AEFC364.DAA5E41D@ctit.utwente.nl> <ypwsniot8mm.fsf@hansa.ibr.cs.tu-bs.de> <3AEFD585.8BAF5BA1@ctit.utwente.nl>
Date: 02 May 2001 12:14:58 +0200
In-Reply-To: <3AEFD585.8BAF5BA1@ctit.utwente.nl>
Message-ID: <ypwr8y8qcpp.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 29
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Hi!

Thanks for the explanations. Just two comments remain:


>> What is the `numeric identity' of a module? The OID of the
>> MODULE-IDENTITY?  What is the purpose of this id?

Aiko> Correct. It is used to detect if a server has already stored
Aiko> this MIB module

I think, the module name is ok to identify a module.
And it works for SMIv1 as well.


Aiko> Note that multiple top level nodes may be associated with a single MIB
Aiko> module. In case of the if-mib the top-level nodes are:
Aiko> - 1.3.6.1.2.1.2
Aiko> - 1.3.6.1.2.1.31
Aiko> - 1.3.6.1.6.3.1.1.5.3
Aiko> - 1.3.6.1.6.3.1.1.5.4
Aiko> (I'm doing just some cut and paste and haven't realy checked this; I
Aiko> hope I didn't made errors. Is this OK to give you the idea?) 

How does your algorithm dicide to use these four OIDs and not for
example 1.3.6.1.2.1 and 1.3.6.1.6.3.1.1.5 or just 1.3.6.1?


 -frank


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id MAA06439 for nmrg-outgoing; Wed, 2 May 2001 12:09:45 +0200 (MET DST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id MAA06424; Wed, 2 May 2001 12:09:43 +0200 (MET DST)
Received: from ctit.utwente.nl (utip064.cs.utwente.nl [130.89.12.90]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id MAA18121; Wed, 2 May 2001 12:09:39 +0200 (MET DST)
Message-ID: <3AEFDCCC.FEEA464C@ctit.utwente.nl>
Date: Wed, 02 May 2001 12:09:16 +0200
From: Aiko Pras <pras@ctit.utwente.nl>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
CC: strauss@ibr.cs.tu-bs.de, boros@cs.utwente.nl, helthuis@cs.utwente.nl, nmrg@ibr.cs.tu-bs.de
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de> <3AEFC364.DAA5E41D@ctit.utwente.nl> <ypwsniot8mm.fsf@hansa.ibr.cs.tu-bs.de> <3AEFD585.8BAF5BA1@ctit.utwente.nl> <200105020953.LAA00726@henkell.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Juergen Schoenwaelder wrote:
> 
> >>>>> Aiko Pras writes:
> 
> >> What is the `numeric identity' of a module? The OID of the
> >> MODULE-IDENTITY?  What is the purpose of this id?
> 
> Aiko> Correct. It is used to detect if a server has already stored
> Aiko> this MIB module
> 
> Which version of "this MIB module"?

The last. That's why it also checks "LastUpdated".
Note that this doesn't realy work for SMIv1 modules.

With IETF MIBs we may also consider the "status" of a MIB module. That
info comes "directly" (well, you all know how easy that is) from the
IETF (we do that in the same way as we maintain
http://www.simpleweb.org/ietf/rfcs/rfcbystatus.html). Thusfar I
considered this as "a local policy", and this info is not being echanged
in the server-server messages.

Bye

Aiko


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id LAA05460 for nmrg-outgoing; Wed, 2 May 2001 11:53:51 +0200 (MET DST)
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id LAA05446; Wed, 2 May 2001 11:53:46 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id LAA00726; Wed, 2 May 2001 11:53:46 +0200
Date: Wed, 2 May 2001 11:53:46 +0200
Message-Id: <200105020953.LAA00726@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: pras@ctit.utwente.nl
CC: strauss@ibr.cs.tu-bs.de, boros@cs.utwente.nl, helthuis@cs.utwente.nl, nmrg@ibr.cs.tu-bs.de
In-reply-to: <3AEFD585.8BAF5BA1@ctit.utwente.nl> (message from Aiko Pras on Wed, 02 May 2001 11:38:13 +0200)
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de> <3AEFC364.DAA5E41D@ctit.utwente.nl> <ypwsniot8mm.fsf@hansa.ibr.cs.tu-bs.de> <3AEFD585.8BAF5BA1@ctit.utwente.nl>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

>>>>> Aiko Pras writes:

>> What is the `numeric identity' of a module? The OID of the
>> MODULE-IDENTITY?  What is the purpose of this id?

Aiko> Correct. It is used to detect if a server has already stored
Aiko> this MIB module

Which version of "this MIB module"?

/js




Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id LAA04962 for nmrg-outgoing; Wed, 2 May 2001 11:45:42 +0200 (MET DST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id LAA04292; Wed, 2 May 2001 11:38:38 +0200 (MET DST)
Received: from ctit.utwente.nl (utip064.cs.utwente.nl [130.89.12.90]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id LAA16676; Wed, 2 May 2001 11:38:35 +0200 (MET DST)
Message-ID: <3AEFD585.8BAF5BA1@ctit.utwente.nl>
Date: Wed, 02 May 2001 11:38:13 +0200
From: Aiko Pras <pras@ctit.utwente.nl>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Frank Strauss <strauss@ibr.cs.tu-bs.de>
CC: szabolcs boros <boros@cs.utwente.nl>, Bert Helthuis <helthuis@cs.utwente.nl>, Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de> <3AEFC364.DAA5E41D@ctit.utwente.nl> <ypwsniot8mm.fsf@hansa.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Hi Frank

Frank Strauss wrote:
> 
> Hi!
> 
> Aiko> 1) A paper written by Szabolcs Boros on this subject. The paper 
> Aiko>    is presented at the High Speed Networking (HSN) workshop at
> Aiko>    Balatonfured (Hungary)
> I took a rough look and have a few questions and comments:
> 
> What is the `numeric identity' of a module? The OID of the
> MODULE-IDENTITY?  What is the purpose of this id?
Correct. It is used to detect if a server has already stored this MIB
module

> What are the `top level node(s) within a module', and what is the
> purpose of this information, e.g. in IF-MIB?
The top level node(s) is (are) used by a server after it gets a request
for some item from a client. Assume the client sends the oid of the item
of which it wants information. The server checks if this oid "fits"
under one of the top-level nodes it knows about. If yes, the server
checks in his database to find the requested item.

Note that multiple top level nodes may be associated with a single MIB
module. In case of the if-mib the top-level nodes are:
- 1.3.6.1.2.1.2
- 1.3.6.1.2.1.31
- 1.3.6.1.6.3.1.1.5.3
- 1.3.6.1.6.3.1.1.5.4
(I'm doing just some cut and paste and haven't realy checked this; I
hope I didn't made errors. Is this OK to give you the idea?) 

> How do you determine the authoritative server of a module?
:-) This is not being solved be some magic algorithm, but is left to the
"owners" of the servers who establish the "friend" relationships.
Determining the authoritive server is therefore a "human policy"
decision. There are some ways you can automate this, however.
It is important, however, to remember that we want a "best effort"
service, and not a 100% guaranteed service.

> XML on page 5: attribute values have be enclosed in double quotes.
> 
> i_have messages are forwarded by servers, right? Is there any hop
> limit? Do you have any assumptions about scalability?
We had a hop limit, but have removed that. There are some simple things,
however, that control how the information within i_have messages are
flooded over all servers. We believe these "simple things" will be
sufficient, since we do not expect an infrastructure with thausands of
servers (I personaaly expect that the number will be less than 100).

> 
>  -frank

Aiko


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id LAA03075 for nmrg-outgoing; Wed, 2 May 2001 11:14:59 +0200 (MET DST)
Received: from hansa.ibr.cs.tu-bs.de (IDENT:root@hansa [134.169.34.137]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id LAA03067; Wed, 2 May 2001 11:14:57 +0200 (MET DST)
Received: (from strauss@localhost) by hansa.ibr.cs.tu-bs.de (8.9.3/8.9.3) id LAA24573; Wed, 2 May 2001 11:14:57 +0200
X-Authentication-Warning: hansa.ibr.cs.tu-bs.de: strauss set sender to strauss@ibr.cs.tu-bs.de using -f
From: Frank Strauss <strauss@ibr.cs.tu-bs.de>
To: Aiko Pras <pras@ctit.utwente.nl>, szabolcs boros <boros@cs.utwente.nl>, Bert Helthuis <helthuis@cs.utwente.nl>
Cc: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de> <3AEFC364.DAA5E41D@ctit.utwente.nl>
Date: 02 May 2001 11:14:57 +0200
In-Reply-To: <3AEFC364.DAA5E41D@ctit.utwente.nl>
Message-ID: <ypwsniot8mm.fsf@hansa.ibr.cs.tu-bs.de>
Lines: 25
User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/20.7
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Hi!

Aiko> 1) A paper written by Szabolcs Boros on this subject. The paper is
Aiko>    presented at the High Speed Networking (HSN) workshop at
Aiko>    Balatonfured (Hungary)
Aiko>    http://www.simpleweb.org/nm/research/results/publications/boros/DMIBOIS.pdf

I took a rough look and have a few questions and comments:


What is the `numeric identity' of a module? The OID of the
MODULE-IDENTITY?  What is the purpose of this id?

What are the `top level node(s) within a module', and what is the
purpose of this information, e.g. in IF-MIB?

How do you determine the authoritative server of a module?

XML on page 5: attribute values have be enclosed in double quotes.

i_have messages are forwarded by servers, right? Is there any hop
limit? Do you have any assumptions about scalability?


 -frank


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id LAA03011 for nmrg-outgoing; Wed, 2 May 2001 11:13:46 +0200 (MET DST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id LAA02999; Wed, 2 May 2001 11:13:44 +0200 (MET DST)
Received: from ctit.utwente.nl (utip064.cs.utwente.nl [130.89.12.90]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id LAA15639; Wed, 2 May 2001 11:13:41 +0200 (MET DST)
Message-ID: <3AEFCFAF.A8362008@ctit.utwente.nl>
Date: Wed, 02 May 2001 11:13:19 +0200
From: Aiko Pras <pras@ctit.utwente.nl>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Frank Strauss <strauss@ibr.cs.tu-bs.de>
CC: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>, szabolcs boros <boros@cs.utwente.nl>, Bert Helthuis <helthuis@cs.utwente.nl>
Subject: Re: [nmrg] 9th nmrg meeting agenda (tentative)
References: <200104251515.RAA06745@henkell.ibr.cs.tu-bs.de> <ypwk849ynv9.fsf@hansa.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Hi Frank

Frank Strauss wrote:
> Aiko, I'd like to let you know in advance of the meeting, what I had
> in mind some time ago. Here is a part of a mail I've sent some time
> ago when you first announced your work on the MIB lookup service...
> 
>     This sounds interesting to me, especially if you would intend to
>     build it on top of (or even integrated with) the libsmi. ;-)
Our current prototype is already using libsmi. We have made some stuff
as "post-processor" around it (to make things faster). Libsmi does the
initial conversion of MIB modules into an intermediate format. From than
on the "post processor" uses the intermediate format. 
It is nice, however, that you're thinking on this too and I'm looking
forward to discuss with you (and others) how we've implemented things. 

>     In the early days of the libsmi design I had a similar idea:    
> 
>       (a) a server that is built on top of the SMI library, that 
>           serves connecting clients that use the server to serve 
>           SMI related requests.
> 
>       (b) a libsmi input driver that makes the library talks to such a
>           server (or even a list of servers, if the first one doesn't 
>           know the answer) if the configured SMIPATH is configured
>           appropriately.
> 
>     This rough idea looked very nice to me, but soon a number of 
>     problems became visible and we shelved this plan.
I'm interested in the problems you've found. We've identified a couple
of problems, but have the impression we know how to deal with them. We
could be wrong ;-(


>     However, if your work on this topic starts, I would be interested 
>     in it.
> This is still true. I would see some benefit, if your service could be
> applicable by a libsmi input driver. However, it could be hard to 
> align both efforts.
As said before, we already use libsmi. On the other hand, things get
only more more interesting if we have multiple, independent
implementations.

See you in Seattle

Aiko


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id KAA01897 for nmrg-outgoing; Wed, 2 May 2001 10:54:54 +0200 (MET DST)
Received: from henkell.ibr.cs.tu-bs.de (schoenw@henkell [134.169.34.191]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id KAA01889; Wed, 2 May 2001 10:54:51 +0200 (MET DST)
Received: from schoenw@localhost by henkell.ibr.cs.tu-bs.de (8.7.6/tubsibr) id KAA00326; Wed, 2 May 2001 10:54:51 +0200
Date: Wed, 2 May 2001 10:54:51 +0200
Message-Id: <200105020854.KAA00326@henkell.ibr.cs.tu-bs.de>
From: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
To: pras@ctit.utwente.nl
CC: nmrg@ibr.cs.tu-bs.de
In-reply-to: <3AEFC364.DAA5E41D@ctit.utwente.nl> (message from Aiko Pras on Wed, 02 May 2001 10:20:52 +0200)
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de> <3AEFC364.DAA5E41D@ctit.utwente.nl>
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

>>>>> Aiko Pras writes:

Aiko> I do not (yet) have an Internet Draft. Depending on the
Aiko> discussion in Seattle, I'm concidering writing one. I propose
Aiko> that interested people read (one of) the following:

Aiko> 1) A paper written by Szabolcs Boros on this subject. The paper
Aiko> is presented at the High Speed Networking (HSN) workshop at
Aiko> Balatonfured (Hungary)
Aiko> http://www.simpleweb.org/nm/research/results/publications/boros/DMIBOIS.pdf

Aiko> 2) A help page on the web, which describes the client-server
Aiko> part of the service.
Aiko> http://www.simpleweb.org/ietf/mibs/oidd/help/ In particular I
Aiko> propose you take a look at the HTTP interface part
Aiko> http://www.simpleweb.org/ietf/mibs/oidd/help/http.html

Thanks. I have linked both documents on the meeting Web page as
reading material.

/js


Return-Path: <owner-nmrg@ibr.cs.tu-bs.de>
Received: by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) id KAA29978 for nmrg-outgoing; Wed, 2 May 2001 10:20:59 +0200 (MET DST)
Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by mumm.ibr.cs.tu-bs.de (8.9.3/8.9.0) with ESMTP id KAA29970; Wed, 2 May 2001 10:20:57 +0200 (MET DST)
Received: from ctit.utwente.nl (utip064.cs.utwente.nl [130.89.12.90]) by utrhcs.cs.utwente.nl (8.9.3/8.9.3) with ESMTP id KAA13402; Wed, 2 May 2001 10:20:54 +0200 (MET DST)
Message-ID: <3AEFC364.DAA5E41D@ctit.utwente.nl>
Date: Wed, 02 May 2001 10:20:52 +0200
From: Aiko Pras <pras@ctit.utwente.nl>
X-Mailer: Mozilla 4.72 [en] (WinNT; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Juergen Schoenwaelder <schoenw@ibr.cs.tu-bs.de>
CC: Network Management Research Group <nmrg@ibr.cs.tu-bs.de>, szabolcs boros <boros@cs.utwente.nl>, Bert Helthuis <helthuis@cs.utwente.nl>
Subject: Re: [nmrg] meeting preparation
References: <200104300936.LAA23754@henkell.ibr.cs.tu-bs.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-nmrg@ibr.cs.tu-bs.de
Precedence: bulk

Hi all


Juergen Schoenwaelder wrote:
> 
> I would like to ask people who have proposed agenda items to provide
> pointers where people attending the meeting can obtain some background
> information. In general, I prefer to use the Internet-Drafts 
> repository to distribute them, but I understand that sometimes this 
> does not work for several reasons.
> 
> Aiko, can we expect say an ID which describes the MIB Object
> Information Lookup Service before the NMRG meeting? Or which other
> document to you want us to study before the NMRG meeting?

I do not (yet) have an Internet Draft. Depending on the discussion in
Seattle, I'm concidering writing one. I propose that interested people
read (one of) the following:

1) A paper written by Szabolcs Boros on this subject. The paper is
   presented at the High Speed Networking (HSN) workshop at
   Balatonfured (Hungary)
http://www.simpleweb.org/nm/research/results/publications/boros/DMIBOIS.pdf

2) A help page on the web, which describes the client-server part
   of the service.
   http://www.simpleweb.org/ietf/mibs/oidd/help/
   In particular I propose you take a look at the HTTP interface part
   http://www.simpleweb.org/ietf/mibs/oidd/help/http.html


B.t.w. we liked the suggestion of Dave Pperkins and will change the
title of this work into "MIB Item LookUp Service".

See you in Seattle

Aiko

