Debian Codegraph @

rfc8177.html

raw
1 <pre>Internet Engineering Task Force (IETF) A. Lindem, Ed.
2 Request for Comments: 8177 Cisco Systems
3 Category: Standards Track Y. Qu
4 ISSN: 2070-1721 Huawei
5 D. Yeung
6 Arrcus, Inc
7 I. Chen
8 Jabil
9 J. Zhang
10 Juniper Networks
11 June 2017
12
13
14 <span class="h1">YANG Data Model for Key Chains</span>
15
16 Abstract
17
18 This document describes the key chain YANG data model. Key chains
19 are commonly used for routing protocol authentication and other
20 applications requiring symmetric keys. A key chain is a list
21 containing one or more elements containing a Key ID, key string,
22 send/accept lifetimes, and the associated authentication or
23 encryption algorithm. By properly overlapping the send and accept
24 lifetimes of multiple key chain elements, key strings and algorithms
25 may be gracefully updated. By representing them in a YANG data
26 model, key distribution can be automated.
27
28 Status of This Memo
29
30 This is an Internet Standards Track document.
31
32 This document is a product of the Internet Engineering Task Force
33 (IETF). It represents the consensus of the IETF community. It has
34 received public review and has been approved for publication by the
35 Internet Engineering Steering Group (IESG). Further information on
36 Internet Standards is available in <a href="./rfc7841#section-2">Section&nbsp;2 of RFC 7841</a>.
37
38 Information about the current status of this document, any errata,
39 and how to provide feedback on it may be obtained at
40 <a href="http://www.rfc-editor.org/info/rfc8177">http://www.rfc-editor.org/info/rfc8177</a>.
41
42
43
44
45
46
47
48
49
50
51
52 <span class="grey">Lindem, et al. Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
55
56
57 Copyright Notice
58
59 Copyright (c) 2017 IETF Trust and the persons identified as the
60 document authors. All rights reserved.
61
62 This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal
63 Provisions Relating to IETF Documents
64 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of
65 publication of this document. Please review these documents
66 carefully, as they describe your rights and restrictions with respect
67 to this document. Code Components extracted from this document must
68 include Simplified BSD License text as described in Section 4.e of
69 the Trust Legal Provisions and are provided without warranty as
70 described in the Simplified BSD License.
71
72 Table of Contents
73
74 <a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
75 <a href="#section-1.1">1.1</a>. Requirements Notation . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
76 <a href="#section-1.2">1.2</a>. Tree Diagrams . . . . . . . . . . . . . . . . . . . . . . <a href="#page-3">3</a>
77 <a href="#section-2">2</a>. Problem Statement . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
78 <a href="#section-2.1">2.1</a>. Applicability . . . . . . . . . . . . . . . . . . . . . . <a href="#page-4">4</a>
79 <a href="#section-2.2">2.2</a>. Graceful Key Rollover Using Key Chains . . . . . . . . . <a href="#page-4">4</a>
80 <a href="#section-3">3</a>. Design of the Key Chain Model . . . . . . . . . . . . . . . . <a href="#page-5">5</a>
81 <a href="#section-3.1">3.1</a>. Key Chain Operational State . . . . . . . . . . . . . . . <a href="#page-6">6</a>
82 <a href="#section-3.2">3.2</a>. Key Chain Model Features . . . . . . . . . . . . . . . . <a href="#page-6">6</a>
83 <a href="#section-3.3">3.3</a>. Key Chain Model Tree . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a>
84 <a href="#section-4">4</a>. Key Chain YANG Model . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a>
85 <a href="#section-5">5</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-16">16</a>
86 <a href="#section-6">6</a>. IANA Considerations . . . . . . . . . . . . . . . . . . . . . <a href="#page-17">17</a>
87 <a href="#section-7">7</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
88 <a href="#section-7.1">7.1</a>. Normative References . . . . . . . . . . . . . . . . . . <a href="#page-18">18</a>
89 <a href="#section-7.2">7.2</a>. Informative References . . . . . . . . . . . . . . . . . <a href="#page-19">19</a>
90 <a href="#appendix-A">Appendix A</a>. Examples . . . . . . . . . . . . . . . . . . . . . . <a href="#page-21">21</a>
91 <a href="#appendix-A.1">A.1</a>. Simple Key Chain with an Always Valid Single Key . . . . <a href="#page-21">21</a>
92 <a href="#appendix-A.2">A.2</a>. Key Chain with Keys Having Different Lifetimes . . . . . <a href="#page-21">21</a>
93 <a href="#appendix-A.3">A.3</a>. Key Chain with Independent Send and Accept Lifetimes . . <a href="#page-23">23</a>
94 Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
95 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-24">24</a>
96 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-25">25</a>
97
98
99
100
101
102
103
104
105
106
107
108 <span class="grey">Lindem, et al. Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
111
112
113 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
114
115 This document describes the key chain YANG [<a href="#ref-YANG-1.1">YANG-1.1</a>] data model.
116 Key chains are commonly used for routing protocol authentication and
117 other applications requiring symmetric keys. A key chain is a list
118 containing one or more elements containing a Key ID, key string,
119 send/accept lifetimes, and the associated authentication or
120 encryption algorithm. By properly overlapping the send and accept
121 lifetimes of multiple key chain elements, key strings and algorithms
122 may be gracefully updated. By representing them in a YANG data
123 model, key distribution can be automated.
124
125 In some applications, the protocols do not use the key chain element
126 key directly, but rather a key derivation function is used to derive
127 a short-lived key from the key chain element key (e.g., the master
128 keys used in [<a href="#ref-TCP-AO" title="&quot;The TCP Authentication Option&quot;">TCP-AO</a>]).
129
130 <span class="h3"><a class="selflink" id="section-1.1" href="#section-1.1">1.1</a>. Requirements Notation</span>
131
132 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
133 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
134 "OPTIONAL" in this document are to be interpreted as described in
135 <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a> [<a href="#ref-KEYWORDS">KEYWORDS</a>] [<a href="#ref-KEYWORDS-UPD">KEYWORDS-UPD</a>] when, and only when, they appear in
136 all capitals, as shown here.
137
138 <span class="h3"><a class="selflink" id="section-1.2" href="#section-1.2">1.2</a>. Tree Diagrams</span>
139
140 A simplified graphical representation of the complete data tree is
141 presented in <a href="#section-3.3">Section 3.3</a>. The following tree notation is used.
142
143 o Brackets "[" and "]" enclose YANG list keys. These YANG list keys
144 should not be confused with the key chain keys.
145
146 o Curly braces "{" and "}" contain names of optional features that
147 make the corresponding node conditional.
148
149 o Abbreviations before data node names: "rw" means configuration
150 (read-write), "ro" means state data (read-only), "-x" means RPC
151 operations, and "-n" means notifications.
152
153 o Symbols after data node names: "?" means an optional node, "!"
154 denotes a container with presence, and "*" denotes a "list" or
155 "leaf-list".
156
157 o Parentheses enclose choice and case nodes, and case nodes are also
158 marked with a colon (":").
159
160
161
162
163
164 <span class="grey">Lindem, et al. Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
167
168
169 o Ellipsis ("...") stands for contents of subtrees that are not
170 shown.
171
172 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Problem Statement</span>
173
174 This document describes a YANG [<a href="#ref-YANG-1.1">YANG-1.1</a>] data model for key chains.
175 Key chains have been implemented and deployed by a large percentage
176 of network equipment vendors. Providing a standard YANG model will
177 facilitate automated key distribution and non-disruptive key
178 rollover. This will aid in tightening the security of the core
179 routing infrastructure as recommended in [<a href="#ref-IAB-REPORT">IAB-REPORT</a>].
180
181 A key chain is a list containing one or more elements containing a
182 Key ID, key string, send/accept lifetimes, and the associated
183 authentication or encryption algorithm. A key chain can be used by
184 any service or application requiring authentication or encryption
185 using symmetric keys. In essence, the key chain is a reusable key
186 policy that can be referenced wherever it is required. The key chain
187 construct has been implemented by most networking vendors and
188 deployed in many networks.
189
190 A conceptual representation of a crypto key table is described in
191 [<a href="#ref-CRYPTO-KEYTABLE">CRYPTO-KEYTABLE</a>]. The crypto key table includes keys as well as
192 their corresponding lifetimes and algorithms. Additionally, the key
193 table includes key selection criteria and is designed for a
194 deployment model where the details of the applications or services
195 requiring authentication or encryption permeate into the key
196 database. The YANG key chain model described herein doesn't include
197 key selection criteria or support this deployment model. At the same
198 time, it does not preclude it. [<a href="#ref-YANG-CRYPTO-KEYTABLE">YANG-CRYPTO-KEYTABLE</a>] describes
199 augmentations to the key chain YANG model in support of key selection
200 criteria.
201
202 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Applicability</span>
203
204 Other YANG modules may reference ietf-key-chain YANG module key-chain
205 names for authentication and encryption applications. A YANG type
206 has been provided to facilitate reference to the key-chain name
207 without having to specify the complete YANG XML Path Language (XPath)
208 expression.
209
210 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Graceful Key Rollover Using Key Chains</span>
211
212 Key chains may be used to gracefully update the key string and/or
213 algorithm used by an application for authentication or encryption.
214 To achieve graceful key rollover, the receiver MAY accept all the
215
216
217
218
219
220 <span class="grey">Lindem, et al. Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
223
224
225 keys that have a valid accept lifetime, and the sender MAY send the
226 key with the most recent send lifetime. One scenario for
227 facilitating key rollover is to:
228
229 1. Distribute a key chain with a new key to all the routers or other
230 network devices in the domain of that key chain. The new key's
231 accept lifetime should be such that it is accepted during the key
232 rollover period. The send lifetime should be a time in the
233 future when it can be assured that all the routers in the domain
234 of that key are upgraded. This will have no immediate impact on
235 the keys used for transmission.
236
237 2. Assure that all the network devices have been updated with the
238 updated key chain and that their system times are roughly
239 synchronized. The system times of devices within an
240 administrative domain are commonly synchronized (e.g., using the
241 Network Time Protocol (NTP) [<a href="#ref-NTP-PROTO">NTP-PROTO</a>]). This also may be
242 automated.
243
244 3. When the send lifetime of the new key becomes valid, the network
245 devices within the domain of that key chain will use the new key
246 for transmissions.
247
248 4. At some point in the future, a new key chain with the old key
249 removed may be distributed to the network devices within the
250 domain of the key chain. However, this may be deferred until the
251 next key rollover. If this is done, the key chain will always
252 include two keys: either the current and future key (during key
253 rollovers) or the current and previous keys (between key
254 rollovers).
255
256 Since the most recent send lifetime is defined as the one with the
257 latest start-time, specification of "always" will prevent using the
258 graceful key rollover technique described above. Other key
259 configuration and usage scenarios are possible, but these are beyond
260 the scope of this document.
261
262 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Design of the Key Chain Model</span>
263
264 The ietf-key-chain module contains a list of one or more keys indexed
265 by a Key ID. For some applications (e.g., OSPFv3 [<a href="#ref-OSPFV3-AUTH">OSPFV3-AUTH</a>]), the
266 Key ID is used to identify the key chain key to be used. In addition
267 to the Key ID, each key chain key includes a key string and a
268 cryptographic algorithm. Optionally, the key chain keys include
269 send/accept lifetimes. If the send/accept lifetime is unspecified,
270 the key is always considered valid.
271
272
273
274
275
276 <span class="grey">Lindem, et al. Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
279
280
281 Note that different key values for transmission versus acceptance may
282 be supported with multiple key chain elements. The key used for
283 transmission will have a valid send-lifetime and invalid accept-
284 lifetime (e.g., has an end-time equal to the start-time). The key
285 used for acceptance will have a valid accept-lifetime and invalid
286 send-lifetime.
287
288 Due to the differences in key chain implementations across various
289 vendors, some of the data elements are optional. Finally, the crypto
290 algorithm identities are provided for reuse when configuring legacy
291 authentication and encryption not using key chains.
292
293 A key chain is identified by a unique name within the scope of the
294 network device. The "key-chain-ref" typedef SHOULD be used by other
295 YANG modules when they need to reference a configured key chain.
296
297 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a>. Key Chain Operational State</span>
298
299 The key chain operational state is included in the same tree as key
300 chain configuration consistent with Network Management Datastore
301 Architecture [<a href="#ref-NMDA" title="&quot;Network Management Datastore Architecture&quot;">NMDA</a>]. The timestamp of the last key chain
302 modification is also maintained in the operational state.
303 Additionally, the operational state includes an indication of whether
304 or not a key chain key is valid for transmission or acceptance.
305
306 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a>. Key Chain Model Features</span>
307
308 Features are used to handle differences between vendor
309 implementations. For example, not all vendors support configuration
310 of an acceptance tolerance or configuration of key strings in
311 hexadecimal. They are also used to support security requirements
312 (e.g., TCP-AO algorithms [<a href="#ref-TCP-AO-ALGORITHMS">TCP-AO-ALGORITHMS</a>]) not yet implemented by
313 vendors or implemented by only a single vendor.
314
315 It is common for an entity with sufficient permissions to read and
316 store a device's configuration, which would include the contents of
317 this model. To avoid unnecessarily seeing and storing the keys in
318 cleartext, this model provides the aes-key-wrap feature. More
319 details are described in the Security Considerations (<a href="#section-5">Section 5</a>).
320
321
322
323
324
325
326
327
328
329
330
331
332 <span class="grey">Lindem, et al. Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
335
336
337 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a>. Key Chain Model Tree</span>
338
339 +--rw key-chains
340 +--rw key-chain* [name]
341 | +--rw name string
342 | +--rw description? string
343 | +--rw accept-tolerance {accept-tolerance}?
344 | | +--rw duration? uint32
345 | +--ro last-modified-timestamp? yang:date-and-time
346 | +--rw key* [key-id]
347 | +--rw key-id uint64
348 | +--rw lifetime
349 | | +--rw (lifetime)?
350 | | +--:(send-and-accept-lifetime)
351 | | | +--rw send-accept-lifetime
352 | | | +--rw (lifetime)?
353 | | | +--:(always)
354 | | | | +--rw always? empty
355 | | | +--:(start-end-time)
356 | | | +--rw start-date-time?
357 | | | | yang:date-and-time
358 | | | +--rw (end-time)?
359 | | | +--:(infinite)
360 | | | | +--rw no-end-time? empty
361 | | | +--:(duration)
362 | | | | +--rw duration? uint32
363 | | | +--:(end-date-time)
364 | | | +--rw end-date-time?
365 | | | yang:date-and-time
366 | | +--:(independent-send-accept-lifetime)
367 | | | {independent-send-accept-lifetime}?
368 | | +--rw send-lifetime
369 | | | +--rw (lifetime)?
370 | | | +--:(always)
371 | | | | +--rw always? empty
372 | | | +--:(start-end-time)
373 | | | +--rw start-date-time?
374 | | | | yang:date-and-time
375 | | | +--rw (end-time)?
376 | | | +--:(infinite)
377 | | | | +--rw no-end-time? empty
378 | | | +--:(duration)
379 | | | | +--rw duration? uint32
380 | | | +--:(end-date-time)
381 | | | +--rw end-date-time?
382 | | | yang:date-and-time
383 | | +--rw accept-lifetime
384 | | +--rw (lifetime)?
385
386
387
388 <span class="grey">Lindem, et al. Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
391
392
393 | | +--:(always)
394 | | | +--rw always? empty
395 | | +--:(start-end-time)
396 | | +--rw start-date-time?
397 | | | yang:date-and-time
398 | | +--rw (end-time)?
399 | | +--:(infinite)
400 | | | +--rw no-end-time? empty
401 | | +--:(duration)
402 | | | +--rw duration? uint32
403 | | +--:(end-date-time)
404 | | +--rw end-date-time?
405 | | yang:date-and-time
406 | +--rw crypto-algorithm identityref
407 | +--rw key-string
408 | | +--rw (key-string-style)?
409 | | +--:(keystring)
410 | | | +--rw keystring? string
411 | | +--:(hexadecimal) {hex-key-string}?
412 | | +--rw hexadecimal-string? yang:hex-string
413 | +--ro send-lifetime-active? boolean
414 | +--ro accept-lifetime-active? boolean
415 +--rw aes-key-wrap {aes-key-wrap}?
416 +--rw enable? boolean
417
418 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Key Chain YANG Model</span>
419
420 &lt;CODE BEGINS&gt; file "[email protected]"
421 module ietf-key-chain {
422 yang-version 1.1;
423 namespace "urn:ietf:params:xml:ns:yang:ietf-key-chain";
424 prefix key-chain;
425
426 import ietf-yang-types {
427 prefix yang;
428 }
429 import ietf-netconf-acm {
430 prefix nacm;
431 }
432
433 organization
434 "IETF RTGWG - Routing Area Working Group";
435 contact
436 "WG Web: &lt;<a href="https://datatracker.ietf.org/group/rtgwg">https://datatracker.ietf.org/group/rtgwg</a>&gt;
437 WG List: &lt;mailto:[email protected]&gt;
438
439 Editor: Acee Lindem
440 &lt;mailto:[email protected]&gt;
441
442
443
444 <span class="grey">Lindem, et al. Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
447
448
449 Yingzhen Qu
450 &lt;mailto:[email protected]&gt;
451 Derek Yeung
452 &lt;mailto:[email protected]&gt;
453 Ing-Wher Chen
454 &lt;mailto:[email protected]&gt;
455 Jeffrey Zhang
456 &lt;mailto:[email protected]&gt;";
457
458 description
459 "This YANG module defines the generic configuration
460 data for key chains. It is intended that the module
461 will be extended by vendors to define vendor-specific
462 key chain configuration parameters.
463
464 Copyright (c) 2017 IETF Trust and the persons identified as
465 authors of the code. All rights reserved.
466
467 Redistribution and use in source and binary forms, with or
468 without modification, is permitted pursuant to, and subject
469 to the license terms contained in, the Simplified BSD License
470 set forth in <a href="#section-4">Section 4</a>.c of the IETF Trust's Legal Provisions
471 Relating to IETF Documents
472 (<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>).
473
474 This version of this YANG module is part of <a href="./rfc8177">RFC 8177</a>;
475 see the RFC itself for full legal notices.";
476
477 reference "<a href="./rfc8177">RFC 8177</a>";
478
479 revision 2017-06-15 {
480 description
481 "Initial RFC Revision";
482 reference "<a href="./rfc8177">RFC 8177</a>: YANG Data Model for Key Chains";
483 }
484
485 feature hex-key-string {
486 description
487 "Support hexadecimal key string.";
488 }
489
490 feature accept-tolerance {
491 description
492 "Support the tolerance or acceptance limit.";
493 }
494
495 feature independent-send-accept-lifetime {
496 description
497
498
499
500 <span class="grey">Lindem, et al. Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
503
504
505 "Support for independent send and accept key lifetimes.";
506 }
507
508 feature crypto-hmac-sha-1-12 {
509 description
510 "Support for TCP HMAC-SHA-1 12-byte digest hack.";
511 }
512
513 feature cleartext {
514 description
515 "Support for cleartext algorithm. Usage is
516 NOT RECOMMENDED.";
517 }
518
519 feature aes-cmac-prf-128 {
520 description
521 "Support for AES Cipher-based Message Authentication
522 Code Pseudorandom Function.";
523 }
524
525 feature aes-key-wrap {
526 description
527 "Support for Advanced Encryption Standard (AES) Key Wrap.";
528 }
529
530 feature replay-protection-only {
531 description
532 "Provide replay protection without any authentication
533 as required by protocols such as Bidirectional
534 Forwarding Detection (BFD).";
535 }
536 identity crypto-algorithm {
537 description
538 "Base identity of cryptographic algorithm options.";
539 }
540
541 identity hmac-sha-1-12 {
542 base crypto-algorithm;
543 if-feature "crypto-hmac-sha-1-12";
544 description
545 "The HMAC-SHA1-12 algorithm.";
546 }
547
548 identity aes-cmac-prf-128 {
549 base crypto-algorithm;
550 if-feature "aes-cmac-prf-128";
551 description
552 "The AES-CMAC-PRF-128 algorithm - required by
553
554
555
556 <span class="grey">Lindem, et al. Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
559
560
561 <a href="./rfc5926">RFC 5926</a> for TCP-AO key derivation functions.";
562 }
563
564 identity md5 {
565 base crypto-algorithm;
566 description
567 "The MD5 algorithm.";
568 }
569
570 identity sha-1 {
571 base crypto-algorithm;
572 description
573 "The SHA-1 algorithm.";
574 }
575
576 identity hmac-sha-1 {
577 base crypto-algorithm;
578 description
579 "HMAC-SHA-1 authentication algorithm.";
580 }
581
582 identity hmac-sha-256 {
583 base crypto-algorithm;
584 description
585 "HMAC-SHA-256 authentication algorithm.";
586 }
587
588 identity hmac-sha-384 {
589 base crypto-algorithm;
590 description
591 "HMAC-SHA-384 authentication algorithm.";
592 }
593
594 identity hmac-sha-512 {
595 base crypto-algorithm;
596 description
597 "HMAC-SHA-512 authentication algorithm.";
598 }
599
600 identity cleartext {
601 base crypto-algorithm;
602 if-feature "cleartext";
603 description
604 "cleartext.";
605 }
606
607 identity replay-protection-only {
608 base crypto-algorithm;
609
610
611
612 <span class="grey">Lindem, et al. Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
615
616
617 if-feature "replay-protection-only";
618 description
619 "Provide replay protection without any authentication as
620 required by protocols such as Bidirectional Forwarding
621 Detection (BFD).";
622 }
623
624 typedef key-chain-ref {
625 type leafref {
626 path
627 "/key-chain:key-chains/key-chain:key-chain/key-chain:name";
628 }
629 description
630 "This type is used by data models that need to reference
631 configured key chains.";
632 }
633
634 grouping lifetime {
635 description
636 "Key lifetime specification.";
637 choice lifetime {
638 default "always";
639 description
640 "Options for specifying key accept or send lifetimes";
641 case always {
642 leaf always {
643 type empty;
644 description
645 "Indicates key lifetime is always valid.";
646 }
647 }
648 case start-end-time {
649 leaf start-date-time {
650 type yang:date-and-time;
651 description
652 "Start time.";
653 }
654 choice end-time {
655 default "infinite";
656 description
657 "End-time setting.";
658 case infinite {
659 leaf no-end-time {
660 type empty;
661 description
662 "Indicates key lifetime end-time is infinite.";
663 }
664 }
665
666
667
668 <span class="grey">Lindem, et al. Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
671
672
673 case duration {
674 leaf duration {
675 type uint32 {
676 range "1..2147483646";
677 }
678 units "seconds";
679 description
680 "Key lifetime duration, in seconds";
681 }
682 }
683 case end-date-time {
684 leaf end-date-time {
685 type yang:date-and-time;
686 description
687 "End time.";
688 }
689 }
690 }
691 }
692 }
693 }
694
695 container key-chains {
696 description
697 "All configured key-chains on the device.";
698 list key-chain {
699 key "name";
700 description
701 "List of key-chains.";
702 leaf name {
703 type string;
704 description
705 "Name of the key-chain.";
706 }
707 leaf description {
708 type string;
709 description
710 "A description of the key-chain";
711 }
712 container accept-tolerance {
713 if-feature "accept-tolerance";
714 description
715 "Tolerance for key lifetime acceptance (seconds).";
716 leaf duration {
717 type uint32;
718 units "seconds";
719 default "0";
720 description
721
722
723
724 <span class="grey">Lindem, et al. Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
727
728
729 "Tolerance range, in seconds.";
730 }
731 }
732 leaf last-modified-timestamp {
733 type yang:date-and-time;
734 config false;
735 description
736 "Timestamp of the most recent update to the key-chain";
737 }
738 list key {
739 key "key-id";
740 description
741 "Single key in key chain.";
742 leaf key-id {
743 type uint64;
744 description
745 "Numeric value uniquely identifying the key";
746 }
747 container lifetime {
748 description
749 "Specify a key's lifetime.";
750 choice lifetime {
751 description
752 "Options for specification of send and accept
753 lifetimes.";
754 case send-and-accept-lifetime {
755 description
756 "Send and accept key have the same lifetime.";
757 container send-accept-lifetime {
758 description
759 "Single lifetime specification for both
760 send and accept lifetimes.";
761 uses lifetime;
762 }
763 }
764 case independent-send-accept-lifetime {
765 if-feature "independent-send-accept-lifetime";
766 description
767 "Independent send and accept key lifetimes.";
768 container send-lifetime {
769 description
770 "Separate lifetime specification for send
771 lifetime.";
772 uses lifetime;
773 }
774 container accept-lifetime {
775 description
776 "Separate lifetime specification for accept
777
778
779
780 <span class="grey">Lindem, et al. Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
783
784
785 lifetime.";
786 uses lifetime;
787 }
788 }
789 }
790 }
791 leaf crypto-algorithm {
792 type identityref {
793 base crypto-algorithm;
794 }
795 mandatory true;
796 description
797 "Cryptographic algorithm associated with key.";
798 }
799 container key-string {
800 description
801 "The key string.";
802 nacm:default-deny-all;
803 choice key-string-style {
804 description
805 "Key string styles";
806 case keystring {
807 leaf keystring {
808 type string;
809 description
810 "Key string in ASCII format.";
811 }
812 }
813 case hexadecimal {
814 if-feature "hex-key-string";
815 leaf hexadecimal-string {
816 type yang:hex-string;
817 description
818 "Key in hexadecimal string format. When compared
819 to ASCII, specification in hexadecimal affords
820 greater key entropy with the same number of
821 internal key-string octets. Additionally, it
822 discourages usage of well-known words or
823 numbers.";
824 }
825 }
826 }
827 }
828 leaf send-lifetime-active {
829 type boolean;
830 config false;
831 description
832 "Indicates if the send lifetime of the
833
834
835
836 <span class="grey">Lindem, et al. Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
839
840
841 key-chain key is currently active.";
842 }
843 leaf accept-lifetime-active {
844 type boolean;
845 config false;
846 description
847 "Indicates if the accept lifetime of the
848 key-chain key is currently active.";
849 }
850 }
851 }
852 container aes-key-wrap {
853 if-feature "aes-key-wrap";
854 description
855 "AES Key Wrap encryption for key-chain key-strings. The
856 encrypted key-strings are encoded as hexadecimal key
857 strings using the hex-key-string leaf.";
858 leaf enable {
859 type boolean;
860 default "false";
861 description
862 "Enable AES Key Wrap encryption.";
863 }
864 }
865 }
866 }
867 &lt;CODE ENDS&gt;
868
869 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
870
871 The YANG module defined in this document is designed to be accessed
872 via network management protocols such as NETCONF [<a href="#ref-NETCONF" title="&quot;Network Configuration Protocol (NETCONF)&quot;">NETCONF</a>] or
873 RESTCONF [<a href="#ref-RESTCONF">RESTCONF</a>]. The lowest NETCONF layer is the secure
874 transport layer, and the mandatory-to-implement secure transport is
875 Secure Shell (SSH) [<a href="#ref-NETCONF-SSH">NETCONF-SSH</a>]. The lowest RESTCONF layer is
876 HTTPS, and the mandatory-to-implement secure transport is TLS [<a href="#ref-TLS" title="&quot;The Transport Layer Security (TLS) Protocol Version 1.2&quot;">TLS</a>].
877
878 The NETCONF access control model [<a href="#ref-NETCONF-ACM">NETCONF-ACM</a>] provides the means to
879 restrict access for particular NETCONF or RESTCONF users to a pre-
880 configured subset of all available NETCONF or RESTCONF protocol
881 operations and content. The key strings are not accessible by
882 default, and NETCONF access control model [<a href="#ref-NETCONF-ACM">NETCONF-ACM</a>] rules are
883 required to configure or retrieve them.
884
885 When configured, the key strings can be encrypted using the AES Key
886 Wrap algorithm [<a href="#ref-AES-KEY-WRAP">AES-KEY-WRAP</a>]. The AES key-encryption key (KEK) is
887 not included in the YANG model and must be set or derived independent
888 of key chain configuration. When AES key encryption is used, the
889
890
891
892 <span class="grey">Lindem, et al. Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
895
896
897 hex-key-string feature is also required since the encrypted keys will
898 contain characters that are not representable in the YANG string
899 built-in type [<a href="#ref-YANG-1.1">YANG-1.1</a>]. It is RECOMMENDED that key strings be
900 encrypted using AES key encryption to prevent key chains from being
901 retrieved and stored with the key strings in cleartext. This
902 recommendation is independent of the access protection that is
903 availed from the NETCONF access control model (NACM) [<a href="#ref-NETCONF-ACM">NETCONF-ACM</a>].
904
905 The cleartext algorithm is included as a YANG feature. Usage is NOT
906 RECOMMENDED except in cases where the application and device have no
907 other alternative (e.g., a legacy network device that must
908 authenticate packets at intervals of 10 milliseconds or less for many
909 peers using Bidirectional Forwarding Detection [<a href="#ref-BFD" title="&quot;Bidirectional Forwarding Detection (BFD)&quot;">BFD</a>]). Keys used
910 with the cleartext algorithm are considered insecure and SHOULD NOT
911 be reused with more secure algorithms.
912
913 Similarly, the MD5 and SHA-1 algorithms have been proven to be
914 insecure ([<a href="#ref-Dobb96a" title="&quot;Cryptanalysis of MD5 Compress&quot;">Dobb96a</a>], [<a href="#ref-Dobb96b" title="&quot;The Status of MD5 After a Recent Attack&quot;">Dobb96b</a>], and [<a href="#ref-SHA-SEC-CON">SHA-SEC-CON</a>]), and usage is NOT
915 RECOMMENDED. Usage should be confined to deployments where it is
916 required for backward compatibility.
917
918 Implementations with keys provided via this model should store them
919 using best current security practices.
920
921 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. IANA Considerations</span>
922
923 This document registers a URI in the "IETF XML Registry"
924 [<a href="#ref-XML-REGISTRY">XML-REGISTRY</a>]. It follows the format in [<a href="#ref-XML-REGISTRY">XML-REGISTRY</a>].
925
926 URI: urn:ietf:params:xml:ns:yang:ietf-key-chain
927 Registrant Contact: The IESG.
928 XML: N/A, the requested URI is an XML namespace.
929
930 This document registers a YANG module in the "YANG Module Names"
931 registry [<a href="#ref-YANG-1.0">YANG-1.0</a>].
932
933 name: ietf-key-chain
934 namespace: urn:ietf:params:xml:ns:yang:ietf-key-chain
935 prefix: key-chain
936 reference: <a href="./rfc8177">RFC 8177</a>
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Lindem, et al. Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
951
952
953 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. References</span>
954
955 <span class="h3"><a class="selflink" id="section-7.1" href="#section-7.1">7.1</a>. Normative References</span>
956
957 [<a id="ref-KEYWORDS">KEYWORDS</a>]
958 Bradner, S., "Key words for use in RFCs to Indicate
959 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>,
960 DOI 10.17487/RFC2119, March 1997,
961 &lt;<a href="http://www.rfc-editor.org/info/rfc2119">http://www.rfc-editor.org/info/rfc2119</a>&gt;.
962
963 [<a id="ref-KEYWORDS-UPD">KEYWORDS-UPD</a>]
964 Leiba, B., "Ambiguity of Uppercase vs Lowercase in <a href="./rfc2119">RFC</a>
965 <a href="./rfc2119">2119</a> Key Words", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc8174">RFC 8174</a>, DOI 10.17487/RFC8174,
966 May 2017, &lt;<a href="http://www.rfc-editor.org/info/rfc8174">http://www.rfc-editor.org/info/rfc8174</a>&gt;.
967
968 [<a id="ref-NETCONF">NETCONF</a>] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed.,
969 and A. Bierman, Ed., "Network Configuration Protocol
970 (NETCONF)", <a href="./rfc6241">RFC 6241</a>, DOI 10.17487/RFC6241, June 2011,
971 &lt;<a href="http://www.rfc-editor.org/info/rfc6241">http://www.rfc-editor.org/info/rfc6241</a>&gt;.
972
973 [<a id="ref-NETCONF-ACM">NETCONF-ACM</a>]
974 Bierman, A. and M. Bjorklund, "Network Configuration
975 Protocol (NETCONF) Access Control Model", <a href="./rfc6536">RFC 6536</a>,
976 DOI 10.17487/RFC6536, March 2012,
977 &lt;<a href="http://www.rfc-editor.org/info/rfc6536">http://www.rfc-editor.org/info/rfc6536</a>&gt;.
978
979 [<a id="ref-NETCONF-SSH">NETCONF-SSH</a>]
980 Wasserman, M., "Using the NETCONF Protocol over Secure
981 Shell (SSH)", <a href="./rfc6242">RFC 6242</a>, DOI 10.17487/RFC6242, June 2011,
982 &lt;<a href="http://www.rfc-editor.org/info/rfc6242">http://www.rfc-editor.org/info/rfc6242</a>&gt;.
983
984 [<a id="ref-RESTCONF">RESTCONF</a>]
985 Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF
986 Protocol", <a href="./rfc8040">RFC 8040</a>, DOI 10.17487/RFC8040, January 2017,
987 &lt;<a href="http://www.rfc-editor.org/info/rfc8040">http://www.rfc-editor.org/info/rfc8040</a>&gt;.
988
989 [<a id="ref-TLS">TLS</a>] Dierks, T. and E. Rescorla, "The Transport Layer Security
990 (TLS) Protocol Version 1.2", <a href="./rfc5246">RFC 5246</a>,
991 DOI 10.17487/RFC5246, August 2008,
992 &lt;<a href="http://www.rfc-editor.org/info/rfc5246">http://www.rfc-editor.org/info/rfc5246</a>&gt;.
993
994 [<a id="ref-XML-REGISTRY">XML-REGISTRY</a>]
995 Mealling, M., "The IETF XML Registry", <a href="https://www.rfc-editor.org/bcp/bcp81">BCP 81</a>, <a href="./rfc3688">RFC 3688</a>,
996 DOI 10.17487/RFC3688, January 2004,
997 &lt;<a href="http://www.rfc-editor.org/info/rfc3688">http://www.rfc-editor.org/info/rfc3688</a>&gt;.
998
999
1000
1001
1002
1003
1004 <span class="grey">Lindem, et al. Standards Track [Page 18]</span></pre>
1005 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-19" ></span>
1006 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1007
1008
1009 [<a id="ref-YANG-1.0">YANG-1.0</a>]
1010 Bjorklund, M., Ed., "YANG - A Data Modeling Language for
1011 the Network Configuration Protocol (NETCONF)", <a href="./rfc6020">RFC 6020</a>,
1012 DOI 10.17487/RFC6020, October 2010,
1013 &lt;<a href="http://www.rfc-editor.org/info/rfc6020">http://www.rfc-editor.org/info/rfc6020</a>&gt;.
1014
1015 [<a id="ref-YANG-1.1">YANG-1.1</a>]
1016 Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language",
1017 <a href="./rfc7950">RFC 7950</a>, DOI 10.17487/RFC7950, August 2016,
1018 &lt;<a href="http://www.rfc-editor.org/info/rfc7950">http://www.rfc-editor.org/info/rfc7950</a>&gt;.
1019
1020 <span class="h3"><a class="selflink" id="section-7.2" href="#section-7.2">7.2</a>. Informative References</span>
1021
1022 [<a id="ref-AES-KEY-WRAP">AES-KEY-WRAP</a>]
1023 Housley, R. and M. Dworkin, "Advanced Encryption Standard
1024 (AES) Key Wrap with Padding Algorithm", <a href="./rfc5649">RFC 5649</a>,
1025 DOI 10.17487/RFC5649, September 2009,
1026 &lt;<a href="http://www.rfc-editor.org/info/rfc5649">http://www.rfc-editor.org/info/rfc5649</a>&gt;.
1027
1028 [<a id="ref-BFD">BFD</a>] Katz, D. and D. Ward, "Bidirectional Forwarding Detection
1029 (BFD)", <a href="./rfc5880">RFC 5880</a>, DOI 10.17487/RFC5880, June 2010,
1030 &lt;<a href="http://www.rfc-editor.org/info/rfc5880">http://www.rfc-editor.org/info/rfc5880</a>&gt;.
1031
1032 [<a id="ref-CRYPTO-KEYTABLE">CRYPTO-KEYTABLE</a>]
1033 Housley, R., Polk, T., Hartman, S., and D. Zhang,
1034 "Database of Long-Lived Symmetric Cryptographic Keys",
1035 <a href="./rfc7210">RFC 7210</a>, DOI 10.17487/RFC7210, April 2014,
1036 &lt;<a href="http://www.rfc-editor.org/info/rfc7210">http://www.rfc-editor.org/info/rfc7210</a>&gt;.
1037
1038 [<a id="ref-Dobb96a">Dobb96a</a>] Dobbertin, H., "Cryptanalysis of MD5 Compress", Technical
1039 Report Presented at the Rump Session of EuroCrypt '96, May
1040 1996.
1041
1042 [<a id="ref-Dobb96b">Dobb96b</a>] Dobbertin, H., "The Status of MD5 After a Recent Attack",
1043 CryptoBytes, Vol. 2, No. 2, Summer 1996.
1044
1045 [<a id="ref-IAB-REPORT">IAB-REPORT</a>]
1046 Andersson, L., Davies, E., and L. Zhang, "Report from the
1047 IAB workshop on Unwanted Traffic March 9-10, 2006",
1048 <a href="./rfc4948">RFC 4948</a>, DOI 10.17487/RFC4948, August 2007,
1049 &lt;<a href="http://www.rfc-editor.org/info/rfc4948">http://www.rfc-editor.org/info/rfc4948</a>&gt;.
1050
1051 [<a id="ref-NMDA">NMDA</a>] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K.,
1052 and R. Wilton, "Network Management Datastore
1053 Architecture", Work in Progress, <a href="./draft-ietf-netmod-revised-datastores-02">draft-ietf-netmod-</a>
1054 <a href="./draft-ietf-netmod-revised-datastores-02">revised-datastores-02</a>, May 2017.
1055
1056
1057
1058
1059
1060 <span class="grey">Lindem, et al. Standards Track [Page 19]</span></pre>
1061 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-20" ></span>
1062 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1063
1064
1065 [<a id="ref-NTP-PROTO">NTP-PROTO</a>]
1066 Mills, D., Martin, J., Ed., Burbank, J., and W. Kasch,
1067 "Network Time Protocol Version 4: Protocol and Algorithms
1068 Specification", <a href="./rfc5905">RFC 5905</a>, DOI 10.17487/RFC5905, June 2010,
1069 &lt;<a href="http://www.rfc-editor.org/info/rfc5905">http://www.rfc-editor.org/info/rfc5905</a>&gt;.
1070
1071 [<a id="ref-OSPFV3-AUTH">OSPFV3-AUTH</a>]
1072 Bhatia, M., Manral, V., and A. Lindem, "Supporting
1073 Authentication Trailer for OSPFv3", <a href="./rfc7166">RFC 7166</a>,
1074 DOI 10.17487/RFC7166, March 2014,
1075 &lt;<a href="http://www.rfc-editor.org/info/rfc7166">http://www.rfc-editor.org/info/rfc7166</a>&gt;.
1076
1077 [<a id="ref-SHA-SEC-CON">SHA-SEC-CON</a>]
1078 Polk, T., Chen, L., Turner, S., and P. Hoffman, "Security
1079 Considerations for the SHA-0 and SHA-1 Message-Digest
1080 Algorithms", <a href="./rfc6194">RFC 6194</a>, DOI 10.17487/RFC6194, March 2011,
1081 &lt;<a href="http://www.rfc-editor.org/info/rfc6194">http://www.rfc-editor.org/info/rfc6194</a>&gt;.
1082
1083 [<a id="ref-TCP-AO">TCP-AO</a>] Touch, J., Mankin, A., and R. Bonica, "The TCP
1084 Authentication Option", <a href="./rfc5925">RFC 5925</a>, DOI 10.17487/RFC5925,
1085 June 2010, &lt;<a href="http://www.rfc-editor.org/info/rfc5925">http://www.rfc-editor.org/info/rfc5925</a>&gt;.
1086
1087 [<a id="ref-TCP-AO-ALGORITHMS">TCP-AO-ALGORITHMS</a>]
1088 Lebovitz, G. and E. Rescorla, "Cryptographic Algorithms
1089 for the TCP Authentication Option (TCP-AO)", <a href="./rfc5926">RFC 5926</a>,
1090 DOI 10.17487/RFC5926, June 2010,
1091 &lt;<a href="http://www.rfc-editor.org/info/rfc5926">http://www.rfc-editor.org/info/rfc5926</a>&gt;.
1092
1093 [<a id="ref-YANG-CRYPTO-KEYTABLE">YANG-CRYPTO-KEYTABLE</a>]
1094 Chen, I., <a style="text-decoration: none" href='https://www.google.com/search?sitesearch=datatracker.ietf.org%2Fdoc%2Fhtml%2F&amp;q=inurl:draft-+%22YANG+Data+Model+for+RFC+7210+Key+Table%22'>"YANG Data Model for RFC 7210 Key Table"</a>, Work
1095 in Progress, <a href="./draft-chen-rtg-key-table-yang-00">draft-chen-rtg-key-table-yang-00</a>, March 2015.
1096
1097
1098
1099
1100
1101
1102
1103
1104
1105
1106
1107
1108
1109
1110
1111
1112
1113
1114
1115
1116 <span class="grey">Lindem, et al. Standards Track [Page 20]</span></pre>
1117 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-21" ></span>
1118 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1119
1120
1121 <span class="h2"><a class="selflink" id="appendix-A" href="#appendix-A">Appendix A</a>. Examples</span>
1122
1123 <span class="h3"><a class="selflink" id="appendix-A.1" href="#appendix-A.1">A.1</a>. Simple Key Chain with an Always Valid Single Key</span>
1124
1125 &lt;?xml version="1.0" encoding="utf-8"?&gt;
1126 &lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;
1127 &lt;key-chains xmlns="urn:ietf:params:xml:ns:yang:ietf-key-chain"&gt;
1128 &lt;key-chain&gt;
1129 &lt;name&gt;keychain-no-end-time&lt;/name&gt;
1130 &lt;description&gt;
1131 A key chain with a single key that is always valid for
1132 transmission and reception.
1133 &lt;/description&gt;
1134 &lt;key&gt;
1135 &lt;key-id&gt;100&lt;/key-id&gt;
1136 &lt;lifetime&gt;
1137 &lt;send-accept-lifetime&gt;
1138 &lt;always/&gt;
1139 &lt;/send-accept-lifetime&gt;
1140 &lt;/lifetime&gt;
1141 &lt;crypto-algorithm&gt;hmac-sha-256&lt;/crypto-algorithm&gt;
1142 &lt;key-string&gt;
1143 &lt;keystring&gt;keystring_in_ascii_100&lt;/keystring&gt;
1144 &lt;/key-string&gt;
1145 &lt;/key&gt;
1146 &lt;/key-chain&gt;
1147 &lt;/key-chains&gt;
1148 &lt;/data&gt;
1149
1150 <span class="h3"><a class="selflink" id="appendix-A.2" href="#appendix-A.2">A.2</a>. Key Chain with Keys Having Different Lifetimes</span>
1151
1152 &lt;?xml version="1.0" encoding="utf-8"?&gt;
1153 &lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;
1154 &lt;key-chains xmlns="urn:ietf:params:xml:ns:yang:ietf-key-chain"&gt;
1155 &lt;key-chain&gt;
1156 &lt;name&gt;keychain2&lt;/name&gt;
1157 &lt;description&gt;
1158 A key chain where each key contains a different send time
1159 and accept time and a different algorithm illustrating
1160 algorithm agility.
1161 &lt;/description&gt;
1162 &lt;key&gt;
1163 &lt;key-id&gt;35&lt;/key-id&gt;
1164 &lt;lifetime&gt;
1165 &lt;send-lifetime&gt;
1166 &lt;start-date-time&gt;2017-01-01T00:00:00Z&lt;/start-date-time&gt;
1167 &lt;end-date-time&gt;2017-02-01T00:00:00Z&lt;/end-date-time&gt;
1168 &lt;/send-lifetime&gt;
1169
1170
1171
1172 <span class="grey">Lindem, et al. Standards Track [Page 21]</span></pre>
1173 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-22" ></span>
1174 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1175
1176
1177 &lt;accept-lifetime&gt;
1178 &lt;start-date-time&gt;2016-12-31T23:59:55Z&lt;/start-date-time&gt;
1179 &lt;end-date-time&gt;2017-02-01T00:00:05Z&lt;/end-date-time&gt;
1180 &lt;/accept-lifetime&gt;
1181 &lt;/lifetime&gt;
1182 &lt;crypto-algorithm&gt;hmac-sha-256&lt;/crypto-algorithm&gt;
1183 &lt;key-string&gt;
1184 &lt;keystring&gt;keystring_in_ascii_35&lt;/keystring&gt;
1185 &lt;/key-string&gt;
1186 &lt;/key&gt;
1187 &lt;key&gt;
1188 &lt;key-id&gt;36&lt;/key-id&gt;
1189 &lt;lifetime&gt;
1190 &lt;send-lifetime&gt;
1191 &lt;start-date-time&gt;2017-02-01T00:00:00Z&lt;/start-date-time&gt;
1192 &lt;end-date-time&gt;2017-03-01T00:00:00Z&lt;/end-date-time&gt;
1193 &lt;/send-lifetime&gt;
1194 &lt;accept-lifetime&gt;
1195 &lt;start-date-time&gt;2017-01-31T23:59:55Z&lt;/start-date-time&gt;
1196 &lt;end-date-time&gt;2017-03-01T00:00:05Z&lt;/end-date-time&gt;
1197 &lt;/accept-lifetime&gt;
1198 &lt;/lifetime&gt;
1199 &lt;crypto-algorithm&gt;hmac-sha-512&lt;/crypto-algorithm&gt;
1200 &lt;key-string&gt;
1201 &lt;hexadecimal-string&gt;fe:ed:be:af:36&lt;/hexadecimal-string&gt;
1202 &lt;/key-string&gt;
1203 &lt;/key&gt;
1204 &lt;/key-chain&gt;
1205 &lt;/key-chains&gt;
1206 &lt;/data&gt;
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227
1228 <span class="grey">Lindem, et al. Standards Track [Page 22]</span></pre>
1229 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-23" ></span>
1230 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1231
1232
1233 <span class="h3"><a class="selflink" id="appendix-A.3" href="#appendix-A.3">A.3</a>. Key Chain with Independent Send and Accept Lifetimes</span>
1234
1235 &lt;?xml version="1.0" encoding="utf-8"?&gt;
1236 &lt;data xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"&gt;
1237 &lt;key-chains xmlns="urn:ietf:params:xml:ns:yang:ietf-key-chain"&gt;
1238 &lt;key-chain&gt;
1239 &lt;name&gt;keychain2&lt;/name&gt;
1240 &lt;description&gt;
1241 A key chain where each key contains different send times
1242 and accept times.
1243 &lt;/description&gt;
1244 &lt;key&gt;
1245 &lt;key-id&gt;35&lt;/key-id&gt;
1246 &lt;lifetime&gt;
1247 &lt;send-lifetime&gt;
1248 &lt;start-date-time&gt;2017-01-01T00:00:00Z&lt;/start-date-time&gt;
1249 &lt;end-date-time&gt;2017-02-01T00:00:00Z&lt;/end-date-time&gt;
1250 &lt;/send-lifetime&gt;
1251 &lt;accept-lifetime&gt;
1252 &lt;start-date-time&gt;2016-12-31T23:59:55Z&lt;/start-date-time&gt;
1253 &lt;end-date-time&gt;2017-02-01T00:00:05Z&lt;/end-date-time&gt;
1254 &lt;/accept-lifetime&gt;
1255 &lt;/lifetime&gt;
1256 &lt;crypto-algorithm&gt;hmac-sha-256&lt;/crypto-algorithm&gt;
1257 &lt;key-string&gt;
1258 &lt;keystring&gt;keystring_in_ascii_35&lt;/keystring&gt;
1259 &lt;/key-string&gt;
1260 &lt;/key&gt;
1261 &lt;key&gt;
1262 &lt;key-id&gt;36&lt;/key-id&gt;
1263 &lt;lifetime&gt;
1264 &lt;send-lifetime&gt;
1265 &lt;start-date-time&gt;2017-02-01T00:00:00Z&lt;/start-date-time&gt;
1266 &lt;end-date-time&gt;2017-03-01T00:00:00Z&lt;/end-date-time&gt;
1267 &lt;/send-lifetime&gt;
1268 &lt;accept-lifetime&gt;
1269 &lt;start-date-time&gt;2017-01-31T23:59:55Z&lt;/start-date-time&gt;
1270 &lt;end-date-time&gt;2017-03-01T00:00:05Z&lt;/end-date-time&gt;
1271 &lt;/accept-lifetime&gt;
1272 &lt;/lifetime&gt;
1273 &lt;crypto-algorithm&gt;hmac-sha-256&lt;/crypto-algorithm&gt;
1274 &lt;key-string&gt;
1275 &lt;hexadecimal-string&gt;fe:ed:be:af:36&lt;/hexadecimal-string&gt;
1276 &lt;/key-string&gt;
1277 &lt;/key&gt;
1278 &lt;/key-chain&gt;
1279 &lt;/key-chains&gt;
1280 &lt;/data&gt;
1281
1282
1283
1284 <span class="grey">Lindem, et al. Standards Track [Page 23]</span></pre>
1285 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-24" ></span>
1286 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1287
1288
1289 Contributors
1290
1291 Yi Yang
1292 SockRate
1293
1294 Email: [email protected]
1295
1296 Acknowledgments
1297
1298 Thanks to Brian Weis for fruitful discussions on security
1299 requirements.
1300
1301 Thanks to Ines Robles for Routing Directorate QA review comments.
1302
1303 Thanks to Ladislav Lhotka for YANG Doctor comments.
1304
1305 Thanks to Martin Bjorklund for additional YANG Doctor comments.
1306
1307 Thanks to Tom Petch for comments during IETF last call.
1308
1309 Thanks to Matthew Miller for comments made during the Gen-ART review.
1310
1311 Thanks to Vincent Roca for comments made during the Security
1312 Directorate review.
1313
1314 Thanks to Warren Kumari, Ben Campbell, Adam Roach, and Benoit Claise
1315 for comments received during the IESG review.
1316
1317
1318
1319
1320
1321
1322
1323
1324
1325
1326
1327
1328
1329
1330
1331
1332
1333
1334
1335
1336
1337
1338
1339
1340 <span class="grey">Lindem, et al. Standards Track [Page 24]</span></pre>
1341 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-25" ></span>
1342 <span class="grey"><a href="./rfc8177">RFC 8177</a> YANG Key Chain June 2017</span>
1343
1344
1345 Authors' Addresses
1346
1347 Acee Lindem (editor)
1348 Cisco Systems
1349 301 Midenhall Way
1350 Cary, NC 27513
1351 United States of America
1352
1353 Email: [email protected]
1354
1355
1356 Yingzhen Qu
1357 Huawei
1358
1359 Email: [email protected]
1360
1361
1362 Derek Yeung
1363 Arrcus, Inc
1364
1365 Email: [email protected]
1366
1367
1368 Ing-Wher Chen
1369 Jabil
1370
1371 Email: [email protected]
1372
1373
1374 Jeffrey Zhang
1375 Juniper Networks
1376 10 Technology Park Drive
1377 Westford, MA 01886
1378 United States of America
1379
1380 Email: [email protected]
1381
1382
1383
1384
1385
1386
1387
1388
1389
1390
1391
1392
1393
1394
1395
1396 Lindem, et al. Standards Track [Page 25]
1397 </pre>