[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: merge/replace selection criteria
HI,
Now, we are getting into the interesting issues....
With SNMP, MIB designers must choose the attributes to identify
instances during the MIB design process. And in SNMP MIB modules,
only a single set of attributes can be specified. The problem is
that what may "work" for management app designers may be expensive
for managed system designers, or the reverse can hold. Also, there
are times when the set of attributes become "too big". Thus, it
would be desirable to be able to specify alternative lists of
attributes that will uniquely identify an instance.
Also, in some cases it is desirable to be able to specify a
selection expression not using any keys. For example, for
every Ethernet-like interface that uses DIX header encoding,
change to SNAP encoding.
Whether on not this is needed, and the format of selection
expressions (yes, Phil, I need to make REGEXs my friend), are
some of the hard decisions for this protocol.
At 03:56 PM 8/25/2003 -0600, Brendan Kelly wrote:
>> -----Original Message-----
>> From: Phil Shafer [<mailto:phil@juniper.net>mailto:phil@juniper.net]
>> Sent: Monday, August 25, 2003 3:44 PM
>> To: Paul Sangree
>> Cc: netconf@ops.ietf.org
>> Subject: Re: merge/replace selection criteria
>>
>> Paul Sangree writes:
>> >However, how does the target system know whether we are trying to change
>> >Bill's address to "123 A Street" or change John's name to "Bill
>> >Baker"? Both interpretations are valid but only one yields the desired
>> result.
>>
>> Another valid-but-wrong interpretation would be replacing all
>> users. The interpretation depends on the understanding of
>> identifiers (identifying elements), but how should this be
>> expressed inside the protocol? Or does it need to be, given
>> that code handling users will either know what the identifiers
>> are or learn them from the schema file?
>>
>> FWIW, early on, Junoscript had an attribute that indicated that an
>> element was an identifier. Developers generally found it somehow
>> confusing and we whacked it.
>>
>I would like to see the elements that are key identifiers defined with attributes as Junoscript did. This will allow the other software applications to easily identify objects in the XML instance.
>
>> Thanks,
>> Phil
>>
>> --
>> to unsubscribe send a message to netconf-request@ops.ietf.org with
>> the word 'unsubscribe' in a single line as the message text body.
>> archive: <http://ops.ietf.org/lists/netconf/>http://ops.ietf.org/lists/netconf/
>
>Thanks
> Brendan
Regards,
/david t. perkins
--
to unsubscribe send a message to netconf-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://ops.ietf.org/lists/netconf/>