On 2022-06-28, at 22:22, Andy Bierman <[email protected]> wrote:
> 
> During operation, the optimized encoding is used for any objects with the
> data type.  E.g., tag X for date-and-time, tag Y for ipv4-address, tag Z for 
> ipv6-address.
> The receiver is responsible for converting the special encoding to the 
> correct format
> for the YANG data type.  Storage and exposure of the optimized format are 
> possible,
> but (perhaps) not required.

Do I actually know that a yang item “has” that data type (*)?
It actually could “have” multiple of them (and usually has both a base type and 
at least one typedef).
Just wondering.

The alternative would be to trigger on the data, so any string that looks like 
2022-06-28T20:48:15Z would turn into 1(1656449295).  That has some interesting 
security considerations, though.

Grüße, Carsten

(*) I.e., name equivalence as opposed to structural equivalence.
Many YANG types are defined via a regexp (pattern)…

_______________________________________________
Anima mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/anima

Reply via email to