Hi,
The IETF draft entity model has added the following:
container sensor-data {
when 'derived-from-or-self(../class,
"iana-entity", "sensor")' {
We already know that derived-from-or-self actually only has 2 parameters so
it is expected to become
container sensor-data {
when 'derived-from-or-self(../class,
"iana-entity:sensor")' {
In order to correctly compile (using confdc) we also need to import
iana-entity for the identities defined in there. However this is leading a
circular dependency:
1. Iana-entity imports ietf-entity (to 'resolve'
entity-physical-class)
2. Ietf-entity imports iana-entity (to obtain the indentities defined
in there)
One way to solve this is to move the definition of entity-physical-class
from ietf-entity to iana-entity which would resolve the fact that
iana-entity requires an import of ietf-entity (ietf-entity needs to import
iana-entity anyhow, so it can also pick the typedef from the same module
too).
Whatever solution is chosen, the circular import needs to be resolved (or
circular imports should be allowed - after all: what has been imported can
be "tracked" removing the need to re-import something that was already
imported).
Best regards - Vriendelijke groeten,
Bart Bogaert
Broadband-Access System Architect Data
Contact number +32 3 2408310 (+32 477 673952)
NOKIA
Copernicuslaan 50, 2018 Antwerp, Belgium
Fortis 220-0002334-42
VAT BE 0404 621 642 Register of Legal Entities Antwerp
<<
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message. Any
disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited without the prior consent of its
author.
>>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
