Re: hierarchical naming

[Frank Strauss <strauss@ibr.cs.tu-bs.de>]

Hi!

Andy> [...] First of all, hierarchical OIDs are important to retain
Andy> complex data relationships, such as the N:1 relationship between
Andy> attribute X and attribute Y for some arbitrary complex
Andy> object. This N:1 existence relationship shows up a lot in the
Andy> data we try to model in MIBs.
>> 
>> We start moving in circles: The power of a hierarchical data
>> model is not bound to any OID naming scheme. 

Andy> We are obviously not going to change each other's opinions
Andy> of the value of hierarchical naming, so I think we should
Andy> just agree to disagree, and let other people in the WG
Andy> voice their opinions on this work. 

Ok.

Andy> It's unfortunate that we don't have a coordinated effort between
Andy> EOS and SMING, because the biggest advantage of this naming
Andy> scheme is the ability to create protocol technology that can
Andy> move any type of sub-aggregate. I believe these protocol
Andy> enhancements will exist some day, but only if the SMING WG lays
Andy> the groundwork first.

I agree that along with new protocol operations, a hierarchical naming
on that enhanced protocol would allow new benefits. 

In SMIng this could probably be achieved by a new protocol mapping,
though I did not yet think about it.

 -frank