I have gone through RFC 6243 (With-defaults Capability). 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.
Based on earlier discussions, it is my understanding that RFC 6243 is supported, but I don't know the extent of this support. Is every aspect of the RFC supported? See below for what I believe to be correct and what I don't yet know.
(I will be posting additional messages later today for RFCs 6020 and 6470.)
Thanks in advance,
-- David
- Introduction - non-normative. No compliance issues.
- Terminology - non-normative. No compliance issues.
- Default-Handling Behavior
- Create and delete operations
- Client Controlled Retrieval of Default Data
- Default-Handling Basic Modes - see below
- 'report-all' Basic Mode - Is this fully supported? The capabilities report implies that is is, but does that cover every aspect of the feature?
- 'report-all' Basic Mode Retrieval - Compliant
- 'report-all' <with-defaults> Retrieval - Is this fully supported?
- 'report-all' <edit-config> and <copy-config> Behavior - Is this fully supported?
- 'trim' Basic Mode - Is this fully supported? The capabilities report implies that is is, but does that cover every aspect of the feature?
- 'trim' Basic Mode Retrieval - Compliant
- 'trim' <with-defaults> Retrieval - Is this fully supported?
- 'trim' <edit-config> and <copy-config> Behavior - Is this fully supported?
- 'explicit' Basic Mode - Is this fully supported? The capabilities report implies that is is, but does that cover every aspect of the feature?
- 'explicit' Basic Mode Retrieval - Compliant
- 'explicit' <with-defaults> Retrieval - Is this fully supported?
- 'explicit' <edit-config> and <copy-config> Behavior - Is this fully supported?
- Retrieval of Default Data - Compliant
- 'report-all' Retrieval Mode - Compliant
- 'trim' Retrieval Mode - Compliant
- 'explicit' Retrieval Mode - Compliant
- 'report-all-tagged' Retrieval Mode - Compliant
- With-defaults Capability - Compliant
- Overview - Compliant
- Dependencies - non-normative. No compliance issues.
- Capability Identifier - Compliant
- new Operations - non-normative. No compliance issues.
- Modifications to Existing Operations - Are these this fully supported?
- <get>, <get-config> and <copy-config> Operations - Is this fully supported?
- <edit-config> Operation - Is this fully supported?
- Other Operations - Is this fully supported?
- Interactions with Other Capabilities - non-normative. No compliance issues.
- YANG Module for the <with-defaults> Parameter - Is this fully supported?
- XSD for the 'default' Attribute - Is this fully supported?
- IANA Considerations - Compliant
- Security Considerations - non-normative. No compliance issues.
- Acknowledgements - non-normative. No compliance issues.
- Normative References - non-normative. No compliance issues.
- Appendix A. Usage Examples - non-normative. No compliance issues.
- Example YANG Module - non-normative. No compliance issues.
- Example Data Set - non-normative. No compliance issues.
- Protocol Operation Example
- <with-defaults> = 'report-all' - non-normative. No compliance issues.
- <with-defaults> = 'report-all-tagged' - non-normative. No compliance issues.
- <with-defaults> = 'trim' - non-normative. No compliance issues.
- <with-defaults> = 'explicit' - non-normative. No compliance issues.