summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorA. Wilcox <AWilcox@Wilcox-Tech.com>2020-10-26 16:44:24 -0500
committerA. Wilcox <AWilcox@Wilcox-Tech.com>2020-10-26 16:44:24 -0500
commit6f33a3f4eb55b376ef929aa9a10d936377edb0ff (patch)
tree17469b37822311a25c98137827fed84c84a211b1 /doc
parent363ba115df9885d645ec87dc983c530113a2a312 (diff)
downloadnetconfapk-6f33a3f4eb55b376ef929aa9a10d936377edb0ff.tar.gz
netconfapk-6f33a3f4eb55b376ef929aa9a10d936377edb0ff.tar.bz2
netconfapk-6f33a3f4eb55b376ef929aa9a10d936377edb0ff.tar.xz
netconfapk-6f33a3f4eb55b376ef929aa9a10d936377edb0ff.zip
Start on ietf-interfaces design and implementation
Diffstat (limited to 'doc')
-rw-r--r--doc/roadmap.rst16
1 files changed, 11 insertions, 5 deletions
diff --git a/doc/roadmap.rst b/doc/roadmap.rst
index 4850948..25b6e95 100644
--- a/doc/roadmap.rst
+++ b/doc/roadmap.rst
@@ -260,20 +260,26 @@ of system network interfaces.
Outstanding TBDs
````````````````
+* How do we retrieve ``last-change``?
+
+Resolved TBDs
+`````````````
* We support ``arbitrary-names``, right? Pretty sure GRE / tuntap / etc all
let you name things whatever you want.
+ **Resolution**: No. We do not, as some Linux network tooling cannot properly
+ handle UTF-8 names.
+
* Do we support ``pre-provisioning``? It would make sense, since /e/n/i and
/e/c/n both let you just specify whatever configuration you want for whatever
interfaces you want.
-* Where do we store interface ``description``?
+ **Resolution**: Yes.
-* How do we retrieve ``last-change``?
+* Where do we store interface ``description``?
-Resolved TBDs
-`````````````
-* None.
+ **Resolution**: /e/n/i can do ``netconf-description`` keyword, /e/c/n (if
+ we support it) can do ``description_$IFACE``.