Binary Push allows all NETCONF notifications to be sent using binary encoding instead of XML. This drastically reduces the notification message size and the server and client message processing time.
Benefits of Binary YANG Push
- IETF RFC 9254, Concise Binary Object Representation (CBOR), is used to encode the YANG notifications.
- Produces significantly smaller notification packets.
- Reduces packet processing times.
- No additional coding is required for the subscription. All other messages are encoded in XML. The client examines the incoming messages to determine the encoding used.
Zero Impact on Server Instrumentation Code.
- No special protocols or new programming requirements are needed to use CBOR encoding with Binary Push.
- The protocol operations for notifications and YANG Push are unchanged.
YANG CBOR does not require special files or generated code to support specific YANG Push reports. A small amount (200 Kbytes) is used to support an arbitrary number of YANG modules.
Faster and Smarter Parser Code uses a deterministic message framing mechanism, so processing is fast and does not require much memory. There are no cases where strings must be examined which is the case for both XML and JSON processing.
LSID is a YumaWorks adaptation of the IETF YANG SID (draft) file approach.
- It uses Localized Schema Item Identifiers (SID) instead of Global identifiers.
- The server assigns SID values to all the relevant schema nodes in this mode.
- There is no attempt to share the SID assignments across servers.
- The client must retrieve the SID mappings from the server.