Re: [eman] UUID required for all energy objects -> ENTITY-MIB v4?

On Fri, Oct 28, 2011 at 04:47:04PM +0200, Benoit Claise wrote:

> So it means that , whatever the entPhysicalUris MIB object contains,
> we could add a UUID (as specified to in RFC4122) to it, separated by
> a space, right?

entPhysicalUris can contain a white space separated list of URIs:

            Multiple URIs may be present and are separated by white
            space characters.  Leading and trailing white space
            characters are ignored.

There was debate around CLEI codes (the pros and cons) and the final
resolution was to support anything that can be represented as a URI.
Today we seem to like UUIDs. This can all happily co-exist (note that
entPhysicalUris does not even have the typical 255 octets size limit).

/js

-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1, 28759 Bremen, Germany
Fax:   +49 421 200 3103         <http://www.jacobs-university.de/>