idnits 2.17.1 draft-ietf-netconf-trust-anchors-05.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 142 has weird spacing: '...on-date yan...' == Line 148 has weird spacing: '...ost-key ct:...' == Line 156 has weird spacing: '...on-date yan...' == Line 166 has weird spacing: '...on-date yan...' == Line 177 has weird spacing: '...on-date yan...' == (2 more instances...) -- The document date (June 7, 2019) is 1757 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-34) exists of draft-ietf-netconf-crypto-types-06 Summary: 0 errors (**), 0 flaws (~~), 8 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 NETCONF Working Group K. Watsen 3 Internet-Draft Watsen Networks 4 Intended status: Standards Track June 7, 2019 5 Expires: December 9, 2019 7 A YANG Data Model for a Truststore 8 draft-ietf-netconf-trust-anchors-05 10 Abstract 12 This document defines a YANG 1.1 data model for configuring global 13 sets of X.509 certificates and SSH host-keys that can be referenced 14 by other data models for trust. While the SSH host-keys are uniquely 15 for the SSH protocol, the X.509 certificates may have multiple uses, 16 including authenticating protocol peers and verifying signatures. 18 Editorial Note (To be removed by RFC Editor) 20 This draft contains many placeholder values that need to be replaced 21 with finalized values at the time of publication. This note 22 summarizes all of the substitutions that are needed. No other RFC 23 Editor instructions are specified elsewhere in this document. 25 Artwork in this document contains shorthand references to drafts in 26 progress. Please apply the following replacements: 28 o "XXXX" --> the assigned RFC value for this draft 30 o "YYYY" --> the assigned RFC value for draft-ietf-netconf-crypto- 31 types 33 Artwork in this document contains placeholder values for the date of 34 publication of this draft. Please apply the following replacement: 36 o "2019-06-07" --> the publication date of this draft 38 The following Appendix section is to be removed prior to publication: 40 o Appendix A. Change Log 42 Status of This Memo 44 This Internet-Draft is submitted in full conformance with the 45 provisions of BCP 78 and BCP 79. 47 Internet-Drafts are working documents of the Internet Engineering 48 Task Force (IETF). Note that other groups may also distribute 49 working documents as Internet-Drafts. The list of current Internet- 50 Drafts is at https://datatracker.ietf.org/drafts/current/. 52 Internet-Drafts are draft documents valid for a maximum of six months 53 and may be updated, replaced, or obsoleted by other documents at any 54 time. It is inappropriate to use Internet-Drafts as reference 55 material or to cite them other than as "work in progress." 57 This Internet-Draft will expire on December 9, 2019. 59 Copyright Notice 61 Copyright (c) 2019 IETF Trust and the persons identified as the 62 document authors. All rights reserved. 64 This document is subject to BCP 78 and the IETF Trust's Legal 65 Provisions Relating to IETF Documents 66 (https://trustee.ietf.org/license-info) in effect on the date of 67 publication of this document. Please review these documents 68 carefully, as they describe your rights and restrictions with respect 69 to this document. Code Components extracted from this document must 70 include Simplified BSD License text as described in Section 4.e of 71 the Trust Legal Provisions and are provided without warranty as 72 described in the Simplified BSD License. 74 Table of Contents 76 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 77 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 78 1.2. Tree Diagram Notation . . . . . . . . . . . . . . . . . . 3 79 2. The Trust Anchors Model . . . . . . . . . . . . . . . . . . . 3 80 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 81 2.2. Example Usage . . . . . . . . . . . . . . . . . . . . . . 4 82 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 7 83 3. Security Considerations . . . . . . . . . . . . . . . . . . . 14 84 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 85 4.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 14 86 4.2. The YANG Module Names Registry . . . . . . . . . . . . . 15 87 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 88 5.1. Normative References . . . . . . . . . . . . . . . . . . 15 89 5.2. Informative References . . . . . . . . . . . . . . . . . 15 90 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 17 91 A.1. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 17 92 A.2. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 17 93 A.3. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 17 94 A.4. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 17 95 A.5. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 17 96 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 18 97 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18 99 1. Introduction 101 This document defines a YANG 1.1 [RFC7950] data model for configuring 102 global sets of X.509 certificates and SSH host-keys that can be 103 referenced by other data models for trust. While the SSH host-keys 104 are uniquely for the SSH protocol, the X.509 certificates may be used 105 for multiple uses, including authenticating protocol peers and 106 verifying signatures. 108 This document in compliant with Network Management Datastore 109 Architecture (NMDA) [RFC8342]. For instance, to support trust 110 anchors installed during manufacturing, it is expected that such data 111 may appear only in . 113 1.1. Requirements Language 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in BCP 118 14 [RFC2119] [RFC8174] when, and only when, they appear in all 119 capitals, as shown here. 121 1.2. Tree Diagram Notation 123 Tree diagrams used in this document follow the notation defined in 124 [RFC8340]. 126 2. The Trust Anchors Model 128 2.1. Tree Diagram 130 The following tree diagram provides an overview of the "ietf- 131 truststore" module. 133 module: ietf-truststore 134 +--rw truststore 135 +--rw certificates* [name] {x509-certificates}? 136 | +--rw name string 137 | +--rw description? string 138 | +--rw certificate* [name] 139 | +--rw name string 140 | +--rw cert trust-anchor-cert-cms 141 | +---n certificate-expiration 142 | +-- expiration-date yang:date-and-time 143 +--rw host-keys* [name] {ssh-host-keys}? 144 +--rw name string 145 +--rw description? string 146 +--rw host-key* [name] 147 +--rw name string 148 +--rw host-key ct:ssh-host-key 150 grouping local-or-truststore-certs-grouping 151 +-- (local-or-truststore) 152 +--:(local) {local-definitions-supported}? 153 | +-- local-definition 154 | +-- cert* trust-anchor-cert-cms 155 | +---n certificate-expiration 156 | +-- expiration-date yang:date-and-time 157 +--:(truststore) {truststore-supported,x509-certificates}? 158 +-- truststore-reference? ts:certificates-ref 159 grouping local-or-truststore-host-keys-grouping 160 +-- (local-or-truststore) 161 +--:(local) {local-definitions-supported}? 162 | +-- local-definition 163 | +-- host-key* ct:ssh-host-key 164 | +-- cert* trust-anchor-cert-cms 165 | +---n certificate-expiration 166 | +-- expiration-date yang:date-and-time 167 +--:(truststore) {truststore-supported,ssh-host-keys}? 168 +-- truststore-reference? ts:host-keys-ref 169 grouping truststore-grouping 170 +-- certificates* [name] {x509-certificates}? 171 | +-- name? string 172 | +-- description? string 173 | +-- certificate* [name] 174 | +-- name? string 175 | +-- cert trust-anchor-cert-cms 176 | +---n certificate-expiration 177 | +-- expiration-date yang:date-and-time 178 +-- host-keys* [name] {ssh-host-keys}? 179 +-- name? string 180 +-- description? string 181 +-- host-key* [name] 182 +-- name? string 183 +-- host-key ct:ssh-host-key 185 2.2. Example Usage 187 The following example illustrates trust anchors in as 188 described by Section 5.3 in [RFC8342]. This datastore view 189 illustrates data set by the manufacturing process alongside 190 conventional configuration. This trust anchors instance has six sets 191 of pinned certificates and one set of pinned host keys. 193 197 198 199 manufacturers-root-ca-certs 200 201 Certificates built into the device for authenticating 202 manufacturer-signed objects, such as TLS server certificates, 203 vouchers, etc. Note, though listed here, these are not 204 configurable; any attempt to do so will be denied. 205 206 207 Manufacturer Root CA cert 1 208 base64encodedvalue== 209 210 211 Manufacturer Root CA cert 2 212 base64encodedvalue== 213 214 216 217 218 explicitly-trusted-server-certs 219 220 Specific server authentication certificates for explicitly 221 trusted servers. These are needed for server certificates 222 that are not signed by a CA. 223 224 225 Fred Flintstone 226 base64encodedvalue== 227 228 230 231 232 explicitly-trusted-server-ca-certs 233 234 Trust anchors (i.e. CA certs) that are used to authenticate 235 server connections. Servers are authenticated if their 236 certificate has a chain of trust to one of these CA 237 certificates. 238 239 240 ca.example.com 241 base64encodedvalue== 242 243 245 246 247 explicitly-trusted-client-certs 248 249 Specific client authentication certificates for explicitly 250 trusted clients. These are needed for client certificates 251 that are not signed by a CA. 252 253 254 George Jetson 255 base64encodedvalue== 256 257 259 260 261 explicitly-trusted-client-ca-certs 262 263 Trust anchors (i.e. CA certs) that are used to authenticate 264 client connections. Clients are authenticated if their 265 certificate has a chain of trust to one of these CA 266 certificates. 267 268 269 ca.example.com 270 base64encodedvalue== 271 272 274 275 276 common-ca-certs 277 278 Trusted certificates to authenticate common HTTPS servers. 279 These certificates are similar to those that might be 280 shipped with a web browser. 281 282 283 ex-certificate-authority 284 base64encodedvalue== 285 286 288 289 290 explicitly-trusted-ssh-host-keys 291 292 Trusted SSH host keys used to authenticate SSH servers. 293 These host keys would be analogous to those stored in 294 a known_hosts file in OpenSSH. 295 296 297 corp-fw1 298 base64encodedvalue== 299 300 302 304 The following example illustrates the "certificate-expiration" 305 notification in use with the NETCONF protocol. 307 =========== NOTE: '\' line wrapping per BCP XX (RFC XXXX) =========== 309 311 2018-05-25T00:01:00Z 312 313 314 explicitly-trusted-client-certs 315 316 George Jetson 317 318 2018-08-05T14:18:53-05:00 320 321 322 323 324 326 2.3. YANG Module 328 This YANG module imports modules from [RFC8341] and 329 [I-D.ietf-netconf-crypto-types]. 331 file "ietf-truststire@2019-06-07.yang" 332 module ietf-truststore { 333 yang-version 1.1; 334 namespace "urn:ietf:params:xml:ns:yang:ietf-truststore"; 335 prefix ts; 336 import ietf-netconf-acm { 337 prefix nacm; 338 reference 339 "RFC 8341: Network Configuration Access Control Model"; 340 } 342 import ietf-crypto-types { 343 prefix ct; 344 reference 345 "RFC YYYY: Common YANG Data Types for Cryptography"; 346 } 348 organization 349 "IETF NETCONF (Network Configuration) Working Group"; 351 contact 352 "WG Web: 353 WG List: 354 Author: Kent Watsen "; 356 description 357 "This module defines a truststore to centralize management 358 of trust anchors including both X.509 certificates and 359 SSH host keys. 361 Copyright (c) 2019 IETF Trust and the persons identified 362 as authors of the code. All rights reserved. 364 Redistribution and use in source and binary forms, with 365 or without modification, is permitted pursuant to, and 366 subject to the license terms contained in, the Simplified 367 BSD License set forth in Section 4.c of the IETF Trust's 368 Legal Provisions Relating to IETF Documents 369 (https://trustee.ietf.org/license-info). 371 This version of this YANG module is part of RFC XXXX 372 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 373 itself for full legal notices.; 375 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 376 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 377 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 378 are to be interpreted as described in BCP 14 (RFC 2119) 379 (RFC 8174) when, and only when, they appear in all 380 capitals, as shown here."; 382 revision 2019-06-07 { 383 description 384 "Initial version"; 385 reference 386 "RFC XXXX: A YANG Data Model for a Truststore"; 387 } 389 /****************/ 390 /* Features */ 391 /****************/ 393 feature truststore-supported { 394 description 395 "The 'truststore-supported' feature indicates that the 396 server supports the truststore."; 397 } 399 feature local-definitions-supported { 400 description 401 "The 'local-definitions-supported' feature indicates that 402 the server supports locally-defined trust anchors."; 403 } 405 feature x509-certificates { 406 description 407 "The 'x509-certificates' feature indicates that the server 408 implements the /truststore/certificates subtree."; 409 } 411 feature ssh-host-keys { 412 description 413 "The 'ssh-host-keys' feature indicates that the server 414 implements the /truststore/host-keys subtree."; 415 } 417 /****************/ 418 /* Typedefs */ 419 /****************/ 421 typedef certificates-ref { 422 type leafref { 423 path "/ts:truststore/ts:certificates/ts:name"; 424 } 425 description 426 "This typedef enables modules to easily define a reference 427 to a set of certificates defined in the truststore."; 428 } 430 typedef host-keys-ref { 431 type leafref { 432 path "/ts:truststore/ts:host-keys/ts:name"; 433 } 434 description 435 "This typedef enables modules to easily define a reference 436 to a set of host keys defined in the truststore."; 437 } 439 /*****************/ 440 /* Groupings */ 441 /*****************/ 443 grouping local-or-truststore-certs-grouping { 444 description 445 "A grouping that expands to allow trust anchors to be 446 either stored locally, within the using data model, or be 447 a reference to trust anchors stored in the truststore."; 448 choice local-or-truststore { 449 mandatory true; 450 case local { 451 if-feature "local-definitions-supported"; 452 container local-definition { 453 description 454 "Container to hold the local trust anchor definitions. 455 A list is defined so as to be symmetric with the 456 truststore definition."; 457 uses ct:trust-anchor-certs-grouping; 458 } 459 } 460 case truststore { 461 if-feature "truststore-supported"; 462 if-feature "x509-certificates"; 463 leaf truststore-reference { 464 type ts:certificates-ref; 465 description 466 "A reference to a set of trust anchors that exists 467 in the truststore."; 468 } 469 } 470 description 471 "A choice between an inlined definition and a definition 472 that exists in the truststore."; 473 } 474 } 476 grouping local-or-truststore-host-keys-grouping { 477 description 478 "A grouping that expands to allow trust anchors to be 479 either stored locally, within the using data model, or be 480 a reference to trust anchors stored in the truststore."; 481 choice local-or-truststore { 482 mandatory true; 483 case local { 484 if-feature "local-definitions-supported"; 485 container local-definition { 486 description 487 "Container to hold the local trust anchor definitions. 488 A list is defined so as to be symmetric with the 489 truststore definition."; 490 leaf-list host-key { 491 nacm:default-deny-write; 492 type ct:ssh-host-key; 493 description 494 "The binary data for this host key."; 495 reference 496 "RFC YYYY: Common YANG Data Types for Cryptography"; 497 } 498 uses ct:trust-anchor-certs-grouping; 499 } 500 } 501 case truststore { 502 if-feature "truststore-supported"; 503 if-feature "ssh-host-keys"; 504 leaf truststore-reference { 505 type ts:host-keys-ref; 506 description 507 "A reference to a set of trust anchors that exists 508 in the truststore."; 509 } 510 } 511 description 512 "A choice between an inlined definition and a definition 513 that exists in the truststore."; 514 } 515 } 517 grouping truststore-grouping { 518 description 519 "Grouping definition enables use in other contexts. If ever 520 done, implementations SHOULD augment new 'case' statements 521 into local-or-keystore 'choice' statements to supply leafrefs 522 to the new location."; 523 list certificates { 524 if-feature "x509-certificates"; 525 key "name"; 526 description 527 "A list of certificates. These certificates can be 528 used by a server to authenticate clients, or by a client 529 to authenticate servers. Each list of certificates 530 SHOULD be specific to a purpose, as the list as a whole 531 may be referenced by other modules. For instance, a 532 RESTCONF server's configuration might use a specific list 533 of certificates for when authenticating RESTCONF 534 client connections."; 535 leaf name { 536 type string; 537 description 538 "An arbitrary name for this list of certificates."; 539 } 540 leaf description { 541 type string; 542 description 543 "An arbitrary description for this list of 544 certificates."; 545 } 546 list certificate { 547 key "name"; 548 description 549 "A certificate."; 550 leaf name { 551 type string; 552 description 553 "An arbitrary name for this certificate. The 554 name must be unique across all lists of 555 certificates (not just this list) so that leafrefs 556 from another module can resolve to unique values."; 557 } 558 uses ct:trust-anchor-cert-grouping { 559 refine "cert" { 560 mandatory true; 561 } 562 } 563 } 564 } 565 list host-keys { 566 if-feature "ssh-host-keys"; 567 key "name"; 568 description 569 "A list of host keys. These host-keys can 570 be used by clients to authenticate SSH servers. Each 571 list of host keys SHOULD be specific to a purpose, 572 so the list as a whole may be referenced by other modules. 573 For instance, a NETCONF client's configuration might 574 point to a specific list of host keys for when 575 authenticating specific SSH servers."; 576 leaf name { 577 type string; 578 description 579 "An arbitrary name for this list of SSH 580 host keys."; 581 } 582 leaf description { 583 type string; 584 description 585 "An arbitrary description for this list of SSH 586 host keys."; 587 } 588 list host-key { 589 key "name"; 590 description 591 "A host key."; 592 leaf name { 593 type string; 594 description 595 "An arbitrary name for this host-key. Must be 596 unique across all lists of host-keys (not just 597 this list) so that a leafref to it from another module 598 can resolve to unique values."; 599 } 600 leaf host-key { 601 type ct:ssh-host-key; 602 mandatory true; 603 description 604 "The binary public key data for this host key."; 605 reference 606 "RFC YYYY: Common YANG Data Types for Cryptography"; 607 } 608 } 609 } 610 } 612 /*********************************/ 613 /* Protocol accessible nodes */ 614 /*********************************/ 616 container truststore { 617 nacm:default-deny-write; 618 description 619 "The truststore contains sets of X.509 certificates and 620 SSH host keys."; 621 uses truststore-grouping; 622 } 624 } 625 627 3. Security Considerations 629 The YANG module defined in this document is designed to be accessed 630 via YANG based management protocols, such as NETCONF [RFC6241] and 631 RESTCONF [RFC8040]. Both of these protocols have mandatory-to- 632 implement secure transport layers (e.g., SSH, TLS) with mutual 633 authentication. 635 The NETCONF access control model (NACM) [RFC8341] provides the means 636 to restrict access for particular users to a pre-configured subset of 637 all available protocol operations and content. 639 There are a number of data nodes defined in this YANG module that are 640 writable/creatable/deletable (i.e., config true, which is the 641 default). These data nodes may be considered sensitive or vulnerable 642 in some network environments. Write operations (e.g., edit-config) 643 to these data nodes without proper protection can have a negative 644 effect on network operations. These are the subtrees and data nodes 645 and their sensitivity/vulnerability: 647 /: The entire data tree defined by this module is sensitive to 648 write operations. For instance, the addition or removal of any 649 trust anchor may dramatically alter the implemented security 650 policy. For this reason, the NACM extension "default-deny- 651 write" has been set for the entire data tree. 653 None of the readable data nodes in this YANG module are considered 654 sensitive or vulnerable in network environments. 656 This module does not define any RPCs, actions, or notifications, and 657 thus the security consideration for such is not provided here. 659 4. IANA Considerations 661 4.1. The IETF XML Registry 663 This document registers one URI in the "ns" subregistry of the IETF 664 XML Registry [RFC3688]. Following the format in [RFC3688], the 665 following registration is requested: 667 URI: urn:ietf:params:xml:ns:yang:ietf-truststore 668 Registrant Contact: The NETCONF WG of the IETF. 669 XML: N/A, the requested URI is an XML namespace. 671 4.2. The YANG Module Names Registry 673 This document registers one YANG module in the YANG Module Names 674 registry [RFC6020]. Following the format in [RFC6020], the the 675 following registration is requested: 677 name: ietf-truststore 678 namespace: urn:ietf:params:xml:ns:yang:ietf-truststore 679 prefix: ta 680 reference: RFC XXXX 682 5. References 684 5.1. Normative References 686 [I-D.ietf-netconf-crypto-types] 687 Watsen, K. and H. Wang, "Common YANG Data Types for 688 Cryptography", draft-ietf-netconf-crypto-types-06 (work in 689 progress), April 2019. 691 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 692 Requirement Levels", BCP 14, RFC 2119, 693 DOI 10.17487/RFC2119, March 1997, 694 . 696 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 697 RFC 7950, DOI 10.17487/RFC7950, August 2016, 698 . 700 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 701 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 702 May 2017, . 704 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 705 Access Control Model", STD 91, RFC 8341, 706 DOI 10.17487/RFC8341, March 2018, 707 . 709 5.2. Informative References 711 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 712 DOI 10.17487/RFC3688, January 2004, 713 . 715 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 716 the Network Configuration Protocol (NETCONF)", RFC 6020, 717 DOI 10.17487/RFC6020, October 2010, 718 . 720 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 721 and A. Bierman, Ed., "Network Configuration Protocol 722 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 723 . 725 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 726 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 727 . 729 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 730 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 731 . 733 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 734 and R. Wilton, "Network Management Datastore Architecture 735 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 736 . 738 Appendix A. Change Log 740 A.1. 00 to 01 742 o Added features "x509-certificates" and "ssh-host-keys". 744 o Added nacm:default-deny-write to "trust-anchors" container. 746 A.2. 01 to 02 748 o Switched "list pinned-certificate" to use the "trust-anchor-cert- 749 grouping" from crypto-types. Effectively the same definition as 750 before. 752 A.3. 02 to 03 754 o Updated copyright date, boilerplate template, affiliation, folding 755 algorithm, and reformatted the YANG module. 757 A.4. 03 to 04 759 o Added groupings 'local-or-truststore-certs-grouping' and 'local- 760 or-truststore-host-keys-grouping', matching similar definitions in 761 the keystore draft. Note new (and incomplete) "truststore" usage! 763 o Related to above, also added features 'truststore-supported' and 764 'local-trust-anchors-supported'. 766 A.5. 04 to 05 768 o Renamed "trust-anchors" to "truststore" 770 o Removed "pinned." prefix everywhere, to match truststore rename 772 o Moved everything under a top-level 'grouping' to enable use in 773 other contexts. 775 o Renamed feature from 'local-trust-anchors-supported' to 'local- 776 definitions-supported' (same name used in keystore) 778 o Removed the "require-instance false" statement from the "*-ref" 779 typedefs. 781 o Added missing "ssh-host-keys" and "x509-certificates" if-feature 782 statements 784 Acknowledgements 786 The authors would like to thank for following for lively discussions 787 on list and in the halls (ordered by last name): Martin Bjorklund, 788 Nick Hancock, Balazs Kovacs, Eric Voit, and Liang Xia. 790 Author's Address 792 Kent Watsen 793 Watsen Networks 795 EMail: kent+ietf@watsen.net