Hi, this is issue is closed but I wonder whether this is correct. I have several questions looking at the issue on github:
- Why is this not a YANG issue? - Which workaround is better? - Why is this tagged as a NETCONF issue? If we want to support binary encodings, we need to allow modelers to define which types map to a canonical binary representation in addition to the canonical string representation. As stated in the issue description, hard-wiring some types in the encoding specifications is very limited. In terms of backwards compatibility, this issue should IMHO be tagged high (adding binary encoding for some types does not cause any backwards compatibility problem since so far we have only strings). While I do not have a solution proposal, I think this issue is worth to look at and we should not close it right now. /js -- Juergen Schoenwaelder Jacobs University Bremen gGmbH Phone: +49 421 200 3587 Campus Ring 1 | 28759 Bremen | Germany Fax: +49 421 200 3103 <https://www.jacobs-university.de/> _______________________________________________ netmod mailing list [email protected] https://www.ietf.org/mailman/listinfo/netmod
