Re: [netmod] BBF Entity Augmentations

[Martin Bjorklund <[e-mail]>]

Hi,

"Carey, Timothy (Nokia - US)" <[e-mail]> wrote:
> Reposting to fix formatting errors in the original message - still
> looking for comments.
> 
> Hello,
> 
> In using the Entity module within the BBF, we have made several
> enhancements to the module that we would like the IETF to consider for
> inclusion in the next draft of the module as we consider these
> enhancements to be of use to the wider YANG community.
> 
> I have included the tree definitions in this email thread. If you like
> the actual YANG files please let us know and we can provide those to
> the authors.
> 
> Specifically we have done the following enhancements:
> 
> 1    Added a new generic reset action for a physical entity
> module: bbf-entity-reset-action
> augment /ent:entity-state/ent:physical-entity:
> +---x reset
> +---w input
> +---w reset-type? identityref

I think it would help to see the YANG definition for this action.

> 2    Added a parent/child entity capability for physical entities

Is this different from contained-id/contains-child that already exist?

> 3 Added a couple of common attributes for the manufacturer name and
> model
> module: bbf-entity-extension
> augment /ent:entity/ent:physical-entity:
> +--rw class? identityref
> +--rw contained-in* -> ../../ent:physical-entity/name
> +--rw parent-rel-pos? int32

These were discussed in the ML thread starting with 
https://www.ietf.org/mail-archive/web/netmod/current/msg16458.html.
However, it was never clear (at least not to me) how this would
actually work.

> +--rw mfg-name? string
> +--rw model-name? string

I can see that these would be useful.  I assume these are intended to
be used like the configurable serial-num?

> 4 Introduced a new type of identity and container for a pluggable
> transceiver

Should this identity be registered with IANA?  If it is not a standard
class registered with IANA the augmentations should probably not be
done here.

> module: bbf-entity-pluggable-transceiver
> augment /ent:entity-state/ent:physical-entity:
> +--ro pluggable-transceiver-data
> augment /ent:entity/ent:physical-entity:
> +--rw pluggable-transceiver
> 
> 5    Introduced a new reference between the interface and the port
> module: bbf-interface-port-reference
> augment /if:interfaces/if:interface:
> +--rw port-layer-if entity-ref

I can see how a config false reference from interface to physical
entity makes sense.  If this is config true, I assume it works like
/interfaces/interface/type?


/martin