Re: opstat model questions

elliot@ghost.uunet.ca Mon, 01 May 1995 20:55 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa10986; 1 May 95 16:55 EDT
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa10982; 1 May 95 16:55 EDT
Received: from wugate.wustl.edu by CNRI.Reston.VA.US id aa16424; 1 May 95 16:55 EDT
Received: from host (localhost [127.0.0.1]) by wugate.wustl.edu (8.6.11/8.6.11) with SMTP id PAA01487; Mon, 1 May 1995 15:55:45 -0500
Received: from ghost.uunet.ca (ghost.uunet.ca [142.77.1.100]) by wugate.wustl.edu (8.6.11/8.6.11) with SMTP id PAA01123 for <oswg-l@wugate.wustl.edu>; Mon, 1 May 1995 15:50:38 -0500
Received: from localhost by ghost.uunet.ca with SMTP id <52930-1>; Mon, 1 May 1995 16:50:30 -0400
Message-Id: <95May1.165030edt.52930-1@ghost.uunet.ca>
Date: Mon, 01 May 1995 16:50:28 -0400
Reply-To: oswg-l@wugate.wustl.edu
X-Orig-Sender: owner-oswg-l@wugate.wustl.edu
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: elliot@ghost.uunet.ca
To: oswg-l@wugate.wustl.edu
Subject: Re: opstat model questions
In-Reply-To: Your message of "Mon, 01 May 95 16:36:15 EDT." <199505012036.NAA24459@hubbub.cisco.com>
X-Listprocessor-Version: 7.1 -- ListProcessor by CREN

>I believe the example was to move one connection between physical
>interfaces, e.g., you move a link from serial 0 to serial 1. In this
>case the configuration of the link stays the same but the interface
>index changes. One thing I'd like to point out though is that your
>polling destination also changes and this might warrant some sort of
>indication in the database. Just a thought.

There's no question that the polling destination needs to be stored in
a database kept by the polling agent, but that's a question of server 
implementation and not presentation format. 

There are many technical details which servers will have to keep track
of: interface numbers, IP addresses, et cetera; these shouldn't really be
specified in the RFC.

elliot