RFC 5277 (NETCONF Event Notifications) compliance

89 views
Skip to first unread message

David Charlap

unread,
Mar 30, 2015, 1:38:14 PM3/30/15
to libne...@googlegroups.com
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

  1. Introduction - non-normative.  No compliance issues.
    1. Definitions of Terms - non-normative.  No compliance issues.
    2. Motivation - non-normative.  No compliance issues.
    3. 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.
  2. Notification-Related Operations - Compliant
    1. Subscribing to Receive Event Notifications - Compliant
      1. <create-subscription> - Compliant, but see my note for section 1.3
    2. Sending Event Notifications - Compliant
      1. <notification> - Compliant
    3. Terminating the Subscription - Compliant
  3. Supporting Concepts - see below for details
    1. Capabilities Exchange - Compliant
      1. Capability Identifier - Compliant
      2. Capability Example - non-normative.  No compliance issues.
    2. Event Streams - I don't know about this.  Is it supported?
      1. Event Stream Definition - non-normative.  No compliance issues.
      2. Event Stream Content Format - I don't know about this.  Is it supported?
      3. Default Event Stream - I don't know about this.  Is it supported?
      4. Event Stream Sources - I don't know about this.  Is it supported?
      5. Event Stream Discovery - I don't know about this.  Is it supported?
        1. Name Retrieval Using <get> Operation - I don't know about this.  Is it supported?
        2. Event Stream Subscription - I don't know about this.  Is it supported?
          1. Filtering Event Stream Contents - I don't know about this.  Is it supported?
    3. Notification Replay - I don't know about this.  Is it supported?
      1. Overview - I don't know about this.  Is it supported?
      2. Creating a Subscription with Replay - I don't know about this.  Is it supported?
    4. Notification Management Schema - I don't know about this.  Is it supported?
    5. Subscription Data - I don't know about this.  Is it supported?
    6. Filter Mechanics - I don't know about this.  Is it supported?
      1. Filtering - I don't know about this.  Is it supported?
    7. Message Flow - I don't know about this.  Is it supported?
  4. XML Schema for Event - I don't know about this.  Is it supported?
  5. Filtering Examples - non-normative.  No compliance issues.
    1. Subtree Filtering - non-normative.  No compliance issues.
    2. XPATH Filters - non-normative.  No compliance issues.
  6. Interleave Capability - Compliant
    1. Description - Compliant
    2. Dependencies - Compliant
    3. Capability Identifier - Compliant
    4. New Operations - Compliant
    5. Modifications to Existing Operations - Compliant
  7. Security Considerations - Compliant, but compliance is dependent on the implementation of the server and data models that use libnetconf.
  8. IANA Considerations - Compliant
  9. Acknowledgements - non-normative.  No compliance issues.
  10. Normative References - non-normative.  No compliance issues.



Tomáš Čejka

unread,
Mar 30, 2015, 3:39:42 PM3/30/15
to libne...@googlegroups.com
Hello David,
I'm not sure about many of boldface things, however, "Notification Replay" is supported.
Tomas Cejka

Dne 30.3.2015 v 19:38 David Charlap napsal(a):
--
You received this message because you are subscribed to the Google Groups "libnetconf" group.
To unsubscribe from this group and stop receiving emails from it, send an email to libnetconf+...@googlegroups.com.
Visit this group at http://groups.google.com/group/libnetconf.
For more options, visit https://groups.google.com/d/optout.

Radek Krejčí

unread,
Mar 31, 2015, 9:44:54 AM3/31/15
to David Charlap, libne...@googlegroups.com
Hi David,

at the first moment, I wanted to make comments inline. But I don't need to - all answers are yes, more information can be found in libnetconf docs [1], just read it and then you can try it using Netopeer [2].

Regards,
Radek

[1] - http://libnetconf.googlecode.com/git/doc/doxygen/html/index.html
[2] - https://code.google.com/p/netopeer/



Dne 30.3.2015 v 19:38 David Charlap napsal(a):
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.

David Charlap

unread,
Mar 31, 2015, 12:45:11 PM3/31/15
to libne...@googlegroups.com, davidc...@gmail.com
Wonderful.  Thanks.

-- David
Reply all
Reply to author
Forward
0 new messages