File: TODO

package info (click to toggle)
yuma123 2.11-1
  • links: PTS
  • area: main
  • in suites: bullseye, buster, sid
  • size: 20,900 kB
  • sloc: ansic: 179,975; cpp: 10,968; python: 5,839; sh: 2,287; makefile: 1,021; xml: 621; exp: 592; perl: 70
file content (42 lines) | stat: -rw-r--r-- 1,886 bytes parent folder | download
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
yuma123 to-do List (2017-01-31)

This file contains the list of known items not finished in the source code.
  -- ietf-yang-library.yang implementation
  -- YANG 1.1 support (RFC 7950)
   -- new Xpath functions - re-match, deref, enum-value, bit-is-set
   -- if-feature in identities, enum, bit
   -- action statement
   -- anydata statement
   -- modifier statement
   -- ... to be continued
  -- yangcli to-do:
     -- command completion for more data types
     -- command completion based on mirror of database
  -- server bugs:
    -- ietf-netconf.yang not used internally.  hacks are used
       to advertise ietf-netconf but use yuma-netconf.
       An 'annotation' feature like deviation-stmt is needed
       to split out the implementation extensions and other
       YANG statements from the standard module.
    -- features are not advertised for ietf-netconf, 
       just capabilities
    -- openssh client hello bug: the client hello code is not
       used; not sure why the SSH application timeout occurs even
       if there is NETCONF traffic; must be doing something
       wrong in the client or server SSH code.
    -- load module chicken-and-egg bug:
      - load a module dynamically and then save some config in
        in the newly loaded module namespace.  Since there is no
        'load foo' added to the netconfd CLI or .conf file,
        this new config will be treated as unknown namespace error
        on the next reboot
    -- SIL user callback functions do not yet support a 'PASS' mode,
       so that multiple callback handlers within the same YANG
       data structure can be utilized.  
  -- server optimizations not done:
    -- save to NVstore:
      -- user hook to override output to XML file
      -- write /config/foo in sub-directories instead of
         XML. Start the XML file(s) for the next layer.
         /config/foo/bar.xml