I have gone through RFC 5277(NETCONF Event Notifications). I have prepared the
following summary of libnetconf's compliance, but it is not complete.
Please look for the sections in
boldface and fill in the
information that I was not able to determine on my own. Also, if you
notice any mistakes, please correct them. Feel free to retain this
table for your own information - you may find it useful if/when others
ask similar questions in the future.
(I will be posting additional messages later today for RFCs 5717, 6020, 6991, 6243 and 6470.)
Thanks in advance,
-- David
- Introduction - non-normative. No compliance issues.
- Definitions of Terms - non-normative. No compliance issues.
- Motivation - non-normative. No compliance issues.
- Event Notifications in NETCONF - Compliant. But note that support of the <create-subscription> command requires support in the server process that uses libnetconf. libnetconf alone is not sufficient.
- Notification-Related Operations - Compliant
- Subscribing to Receive Event Notifications - Compliant
- <create-subscription> - Compliant, but see my note for section 1.3
- Sending Event Notifications - Compliant
- <notification> - Compliant
- Terminating the Subscription - Compliant
- Supporting Concepts - see below for details
- Capabilities Exchange - Compliant
- Capability Identifier - Compliant
- Capability Example - non-normative. No compliance issues.
- Event Streams - I don't know about this. Is it supported?
- Event Stream Definition - non-normative. No compliance issues.
- Event Stream Content Format - I don't know about this. Is it supported?
- Default Event Stream - I don't know about this. Is it supported?
- Event Stream Sources - I don't know about this. Is it supported?
- Event Stream Discovery - I don't know about this. Is it supported?
- Name Retrieval Using <get> Operation - I don't know about this. Is it supported?
- Event Stream Subscription - I don't know about this. Is it supported?
- Filtering Event Stream Contents - I don't know about this. Is it supported?
- Notification Replay - I don't know about this. Is it supported?
- Overview - I don't know about this. Is it supported?
- Creating a Subscription with Replay - I don't know about this. Is it supported?
- Notification Management Schema - I don't know about this. Is it supported?
- Subscription Data - I don't know about this. Is it supported?
- Filter Mechanics - I don't know about this. Is it supported?
- Filtering - I don't know about this. Is it supported?
- Message Flow - I don't know about this. Is it supported?
- XML Schema for Event - I don't know about this. Is it supported?
- Filtering Examples - non-normative. No compliance issues.
- Subtree Filtering - non-normative. No compliance issues.
- XPATH Filters - non-normative. No compliance issues.
- Interleave Capability - Compliant
- Description - Compliant
- Dependencies - Compliant
- Capability Identifier - Compliant
- New Operations - Compliant
- Modifications to Existing Operations - Compliant
- Security Considerations - Compliant, but compliance is dependent on the implementation of the server and data models that use libnetconf.
- IANA Considerations - Compliant
- Acknowledgements - non-normative. No compliance issues.
- Normative References - non-normative. No compliance issues.