From 6f33a3f4eb55b376ef929aa9a10d936377edb0ff Mon Sep 17 00:00:00 2001 From: "A. Wilcox" Date: Mon, 26 Oct 2020 16:44:24 -0500 Subject: Start on ietf-interfaces design and implementation --- doc/roadmap.rst | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) (limited to 'doc') 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``. -- cgit v1.2.3-70-g09d2