draft-ietf-babel-yang-model-05.txt   draft-ietf-babel-yang-model-06.txt 
Babel Working Group M. Jethanandani Babel Working Group M. Jethanandani
Internet-Draft VMware Internet-Draft Kloud Services
Intended status: Standards Track B. Stark Intended status: Standards Track B. Stark
Expires: July 10, 2020 AT&T Expires: December 30, 2020 AT&T
January 7, 2020 June 28, 2020
YANG Data Model for Babel YANG Data Model for Babel
draft-ietf-babel-yang-model-05 draft-ietf-babel-yang-model-06
Abstract Abstract
This document defines a data model for the Babel routing protocol. This document defines a data model for the Babel routing protocol.
The data model is defined using the YANG data modeling language. The data model is defined using the YANG data modeling language.
Requirements Language Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
skipping to change at page 1, line 40 skipping to change at page 1, line 40
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 10, 2020. This Internet-Draft will expire on December 30, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2020 IETF Trust and the persons identified as the Copyright (c) 2020 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 8 skipping to change at page 3, line 8
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements and remove this progress. Please apply the following replacements and remove this
note before publication. note before publication.
o "XXXX" --> the assigned RFC value for this draft both in this o "XXXX" --> the assigned RFC value for this draft both in this
draft and in the YANG models under the revision statement. draft and in the YANG models under the revision statement.
o "ZZZZ" --> the assigned RFC value for Babel Information Model o "ZZZZ" --> the assigned RFC value for Babel Information Model
[I-D.ietf-babel-information-model] [I-D.ietf-babel-information-model]
o Revision date in model, in the format 2020-01-07 needs to get o Revision date in model, in the format 2020-06-28 needs to get
updated with the date the draft gets approved. The date also updated with the date the draft gets approved. The date also
needs to get reflected on the line with <CODE BEGINS>. needs to get reflected on the line with <CODE BEGINS>.
1.2. Tree Diagram Annotations 1.2. Tree Diagram Annotations
For a reference to the annotations used in tree diagrams included in For a reference to the annotations used in tree diagrams included in
this draft, please see YANG Tree Diagrams [RFC8340]. this draft, please see YANG Tree Diagrams [RFC8340].
2. Babel Module 2. Babel Module
skipping to change at page 5, line 33 skipping to change at page 5, line 33
In addition to the modules used above, this module imports In addition to the modules used above, this module imports
definitions from Common YANG Data Types [RFC6991], and references definitions from Common YANG Data Types [RFC6991], and references
HMAC: Keyed-Hashing for Message Authentication [RFC2104], Using HMAC- HMAC: Keyed-Hashing for Message Authentication [RFC2104], Using HMAC-
SHA-256, HMAC-SHA-384, and HMAC-SHA-512 [RFC4868], Datagram Transport SHA-256, HMAC-SHA-384, and HMAC-SHA-512 [RFC4868], Datagram Transport
Layer Security Version 1.2 [RFC6347], The Blake2 Cryptographic Hash Layer Security Version 1.2 [RFC6347], The Blake2 Cryptographic Hash
and Message Authentication Code (MAC) [RFC7693], Babel Information and Message Authentication Code (MAC) [RFC7693], Babel Information
Model [I-D.ietf-babel-information-model], and The Babel Routing Model [I-D.ietf-babel-information-model], and The Babel Routing
Protocol [I-D.ietf-babel-rfc6126bis]. Protocol [I-D.ietf-babel-rfc6126bis].
<CODE BEGINS> file "ietf-babel@2020-01-07.yang" <CODE BEGINS> file "ietf-babel@2020-06-28.yang"
module ietf-babel { module ietf-babel {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-babel"; namespace "urn:ietf:params:xml:ns:yang:ietf-babel";
prefix babel; prefix babel;
import ietf-yang-types { import ietf-yang-types {
prefix yt; prefix yt;
reference reference
"RFC 6991: Common YANG Data Types."; "RFC 6991: Common YANG Data Types.";
skipping to change at page 6, line 49 skipping to change at page 6, line 49
without modification, is permitted pursuant to, and subject to without modification, is permitted pursuant to, and subject to
the license terms contained in, the Simplified BSD License set the license terms contained in, the Simplified BSD License set
forth in Section 4.c of the IETF Trust's Legal Provisions forth in Section 4.c of the IETF Trust's Legal Provisions
Relating to IETF Documents Relating to IETF Documents
(https://trustee.ietf.org/license-info). (https://trustee.ietf.org/license-info).
This version of this YANG module is part of RFC XXXX This version of this YANG module is part of RFC XXXX
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself (https://www.rfc-editor.org/info/rfcXXXX); see the RFC itself
for full legal notices."; for full legal notices.";
revision 2020-01-07 { revision 2020-06-28 {
description description
"Initial version."; "Initial version.";
reference reference
"RFC XXXX: Babel YANG Data Model."; "RFC XXXX: Babel YANG Data Model.";
} }
/* /*
* Features * Features
*/ */
skipping to change at page 8, line 14 skipping to change at page 8, line 14
/* /*
* Identities * Identities
*/ */
identity metric-comp-algorithms { identity metric-comp-algorithms {
description description
"Base identity from which all Babel metric comp algorithms "Base identity from which all Babel metric comp algorithms
are derived."; are derived.";
} }
identity two-out-of-three { identity two-out-of-three {
base "metric-comp-algorithms";
if-feature two-out-of-three-supported; if-feature two-out-of-three-supported;
base "metric-comp-algorithms";
description description
"2-out-of-3 algorithm."; "2-out-of-3 algorithm.";
} }
identity etx { identity etx {
base "metric-comp-algorithms";
if-feature etx-supported; if-feature etx-supported;
base "metric-comp-algorithms";
description description
"Expected Transmission Count."; "Expected Transmission Count.";
} }
/* /*
* Babel MAC algorithms identities. * Babel MAC algorithms identities.
*/ */
identity mac-algorithms { identity mac-algorithms {
description description
"Base identity for all Babel MAC algorithms."; "Base identity for all Babel MAC algorithms.";
} }
identity hmac-sha256 { identity hmac-sha256 {
base mac-algorithms;
if-feature mac-supported; if-feature mac-supported;
if-feature hmac-sha256-supported; if-feature hmac-sha256-supported;
base mac-algorithms;
description description
"HMAC-SHA256 algorithm supported."; "HMAC-SHA256 algorithm supported.";
reference reference
"RFC 4868: Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512 "RFC 4868: Using HMAC-SHA-256, HMAC-SHA-384, and HMAC-SHA-512
with IPsec."; with IPsec.";
} }
identity blake2s { identity blake2s {
base mac-algorithms;
if-feature mac-supported; if-feature mac-supported;
if-feature blake2s-supported; if-feature blake2s-supported;
base mac-algorithms;
description description
"BLAKE2s algorithm supported."; "BLAKE2s algorithm supported.";
reference reference
"RFC 7693: The BLAKE2 Cryptographic Hash and Message "RFC 7693: The BLAKE2 Cryptographic Hash and Message
Authentication Code (MAC)."; Authentication Code (MAC).";
} }
/* /*
* Babel Cert Types * Babel Cert Types
*/ */
identity dtls-cert-types { identity dtls-cert-types {
description description
"Base identity for Babel DTLS certificate types."; "Base identity for Babel DTLS certificate types.";
} }
identity x-509 { identity x-509 {
base dtls-cert-types;
if-feature dtls-supported; if-feature dtls-supported;
if-feature x-509-supported; if-feature x-509-supported;
base dtls-cert-types;
description description
"X.509 certificate type."; "X.509 certificate type.";
} }
identity raw-public-key { identity raw-public-key {
base dtls-cert-types;
if-feature dtls-supported; if-feature dtls-supported;
if-feature raw-public-key-supported; if-feature raw-public-key-supported;
base dtls-cert-types;
description description
"Raw Public Key type."; "Raw Public Key type.";
} }
/* /*
* Babel routing protocol identity. * Babel routing protocol identity.
*/ */
identity babel { identity babel {
base "rt:routing-protocol"; base "rt:routing-protocol";
description description
skipping to change at page 30, line 44 skipping to change at page 30, line 44
Juliusz Chroboczek provided most of the example configurations for Juliusz Chroboczek provided most of the example configurations for
babel that are shown in the Appendix. babel that are shown in the Appendix.
6. References 6. References
6.1. Normative References 6.1. Normative References
[I-D.ietf-babel-rfc6126bis] [I-D.ietf-babel-rfc6126bis]
Chroboczek, J. and D. Schinazi, "The Babel Routing Chroboczek, J. and D. Schinazi, "The Babel Routing
Protocol", draft-ietf-babel-rfc6126bis-16 (work in Protocol", draft-ietf-babel-rfc6126bis-17 (work in
progress), December 2019. progress), February 2020.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA- [RFC4868] Kelly, S. and S. Frankel, "Using HMAC-SHA-256, HMAC-SHA-
384, and HMAC-SHA-512 with IPsec", RFC 4868, 384, and HMAC-SHA-512 with IPsec", RFC 4868,
DOI 10.17487/RFC4868, May 2007, DOI 10.17487/RFC4868, May 2007,
<https://www.rfc-editor.org/info/rfc4868>. <https://www.rfc-editor.org/info/rfc4868>.
skipping to change at page 38, line 7 skipping to change at page 38, line 7
<metric-algorithm>two-out-of-three</metric-algorithm> <metric-algorithm>two-out-of-three</metric-algorithm>
</interfaces> </interfaces>
</babel> </babel>
</control-plane-protocol> </control-plane-protocol>
</control-plane-protocols> </control-plane-protocols>
</routing> </routing>
</config> </config>
Authors' Addresses Authors' Addresses
Mahesh Jethanandani Mahesh Jethanandani
VMware Kloud Services
California California
USA USA
Email: mjethanandani@gmail.com Email: mjethanandani@gmail.com
Barbara Stark Barbara Stark
AT&T AT&T
Atlanta, GA Atlanta, GA
USA USA
 End of changes. 21 change blocks. 
17 lines changed or deleted 17 lines changed or added

This html diff was produced by rfcdiff 1.47. The latest version is available from http://tools.ietf.org/tools/rfcdiff/