netconf-0----Page:9
1  2  3  4  5  6  7  8  9  10  11  12 

Notification Structure Issues currently defined with a mandatory container like an should this work like the container instead? NotificationType, like RpcOperationType, is the abstract base for notifications Each notification defines its own FooNotificationType as an extension to NotificationType Only the ‘notification type’ element is required to be present, like the ‘RPC method node’ element Common ‘header’ fields that are approved later by the NETMOD WG (e.g., event-class and timestamps) can be added as attributes to the element in the future

PPT Version