Implement state portion of ietf-system module

1 files changed, 31 insertions, 17 deletions

diff --git a/doc/roadmap.rst b/doc/roadmap.rst
index 19a1b2f..03f7d81 100644
--- a/doc/roadmap.rst
+++ b/doc/roadmap.rst
@@ -88,13 +88,13 @@ This feature will require in-depth discussion.
 
     * [ ] SSH key administration (``$HOME/.ssh/authorized_keys``).
 
-* [ ] State nodes
+* [X] State nodes
 
-  * [ ] Platform information.
+  * [X] Platform information.
 
-  * [ ] Current date and time.
+  * [X] Current date and time.
 
-  * [ ] Boot date and time.
+  * [X] Boot date and time.
 
 * [ ] RPCs
 
@@ -110,24 +110,14 @@ The system module allows basic administration of system configuration.
 
 Outstanding TBDs
 ````````````````
-* Where do we store the ``contact`` and ``location`` node information?
-
-* When the admin tries to set ``timezone-utf-offset``, do we make a custom
+* When the admin tries to set ``timezone-utc-offset``, do we make a custom
   zoneinfo file or do we try to match?
 
 * How do we support ``name`` of DNS resolvers?  It is mandatory.
 
-* Can musl be configured for DNS timeout seconds and resolution attempts?
-  Would Rich be open to adding this?
-
-* Do we support password-based authentication?
-
-* If we support password-based authentication, do we have a custom database or
-  do we use ``/etc/shadow``?  Should there be a group for NETCONF-allowed
-  users?  Do we support RADIUS?
+* Should there be a group for NETCONF-allowed users?
 
-* Do we calculate boot date/time naively (current time - uptime) or do we try
-  to ascertain the actual boot date/time from something like ctime of ``/run``?
+* Do we support RADIUS?
 
 Resolved TBDs
 `````````````
@@ -138,6 +128,30 @@ Resolved TBDs
   ``ntpsec``.  It has been packaged and tested for Adélie/ppc64, so it appears
   portable.
 
+* Where do we store the ``contact`` and ``location`` node information?
+
+  **Resolution**: Flat files on the disk.
+
+* Can musl be configured for DNS timeout seconds and resolution attempts?
+  Would Rich be open to adding this?
+
+  **Resolution**: Yes, musl supports these options in ``/etc/resolv.conf``.
+
+* Do we calculate boot date/time naively (current time - uptime) or do we try
+  to ascertain the actual boot date/time from something like ctime of ``/run``?
+
+  **Resolution**: Naive calculation works well.  ctime is not always
+  available and may be unreliable (systems that boot with time set to 1970).
+
+* Do we support password-based authentication?
+
+  **Resolution**: No, only key-based authentication.
+
+* If we support password-based authentication, do we have a custom database or
+  do we use ``/etc/shadow``?
+
+  **Resolution**: Not applicable; we do not support password-based
+  authentication.