---
Dear all,
I’ve found some inconsistencies in the naming of some fields in the
Babel Information Model. I’ve already send mails about them; but I’m
afraid my mails might have fallen in limbo. The issue is minor.
Below is a patch for the fields.
Best regards,
Antonin
draft-ietf-babel-information-model.md | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/draft-ietf-babel-information-model.md b/draft-ietf-babel-information-model.md
index 7990b7a..1588797 100644
--- a/draft-ietf-babel-information-model.md
+++ b/draft-ietf-babel-information-model.md
@@ -179,8 +179,8 @@ The Information Model is hierarchically structured as follows:
+-- babel-information
+-- babel-implementation-version
+-- babel-enable
- +-- router-id
- +-- self-seqno
+ +-- babel-self-router-id
+ +-- babel-self-seqno
+-- babel-metric-comp-algorithms
+-- babel-security-supported
+-- babel-mac-algorithms
@@ -534,7 +534,7 @@ babel-mac-enable:
An implementation MAY choose
to expose this parameter as read-only ("ro").
-babel-if-mac-keys-sets:
+babel-if-mac-key-sets:
: List of references to the babel-mac entries that apply to this
interface. When an interface instance is created, all babel-mac-key-sets
instances with babel-mac-default-apply "true" will be included
@@ -828,7 +828,7 @@ babel-mac-default-apply:
applied to all new babel-interface instances, by default.
If "true", this instance is applied to
new babel-interfaces instances at the time they are created, by including
- it in the babel-interface-mac-keys list.
+ it in the babel-if-mac-key-sets list.
If "false", this instance is not applied to new babel-interfaces
instances when they are created.
An implementation MAY choose
--
2.29.1
--
last-call mailing list
last-call@xxxxxxxx
https://www.ietf.org/mailman/listinfo/last-call
