idnits 2.17.1 draft-ietf-netconf-trust-anchors-06.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 144 has weird spacing: '...on-date yan...' == Line 150 has weird spacing: '...ost-key ct:...' == Line 158 has weird spacing: '...on-date yan...' == Line 176 has weird spacing: '...on-date yan...' == Line 182 has weird spacing: '...ost-key ct:...' == (1 more instance...) -- The document date (October 18, 2019) is 1653 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-10 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 October 18, 2019 5 Expires: April 20, 2020 7 A YANG Data Model for a Truststore 8 draft-ietf-netconf-trust-anchors-06 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-10-18" --> 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 April 20, 2020. 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 . . . . . . . . . . . . . . . . . . . . . . 5 82 2.3. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 8 83 3. Security Considerations . . . . . . . . . . . . . . . . . . . 14 84 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 15 85 4.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 15 86 4.2. The YANG Module Names Registry . . . . . . . . . . . . . 15 87 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 15 88 5.1. Normative References . . . . . . . . . . . . . . . . . . 15 89 5.2. Informative References . . . . . . . . . . . . . . . . . 16 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 A.6. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 18 98 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 18 99 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 18 101 1. Introduction 103 This document defines a YANG 1.1 [RFC7950] data model for configuring 104 global sets of X.509 certificates and SSH host-keys that can be 105 referenced by other data models for trust. While the SSH host-keys 106 are uniquely for the SSH protocol, the X.509 certificates may be used 107 for multiple uses, including authenticating protocol peers and 108 verifying signatures. 110 This document in compliant with Network Management Datastore 111 Architecture (NMDA) [RFC8342]. For instance, to support trust 112 anchors installed during manufacturing, it is expected that such data 113 may appear only in . 115 1.1. Requirements Language 117 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 118 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 119 "OPTIONAL" in this document are to be interpreted as described in BCP 120 14 [RFC2119] [RFC8174] when, and only when, they appear in all 121 capitals, as shown here. 123 1.2. Tree Diagram Notation 125 Tree diagrams used in this document follow the notation defined in 126 [RFC8340]. 128 2. The Trust Anchors Model 130 2.1. Tree Diagram 132 The following tree diagram provides an overview of the "ietf- 133 truststore" module. 135 module: ietf-truststore 136 +--rw truststore 137 +--rw certificates* [name] {x509-certificates}? 138 | +--rw name string 139 | +--rw description? string 140 | +--rw certificate* [name] 141 | +--rw name string 142 | +--rw cert trust-anchor-cert-cms 143 | +---n certificate-expiration 144 | +-- expiration-date yang:date-and-time 145 +--rw host-keys* [name] {ssh-host-keys}? 146 +--rw name string 147 +--rw description? string 148 +--rw host-key* [name] 149 +--rw name string 150 +--rw host-key ct:ssh-host-key 152 grouping local-or-truststore-certs-grouping 153 +-- (local-or-truststore) 154 +--:(local) {local-definitions-supported}? 155 | +-- local-definition 156 | +-- cert* trust-anchor-cert-cms 157 | +---n certificate-expiration 158 | +-- expiration-date yang:date-and-time 159 +--:(truststore) {truststore-supported,x509-certificates}? 160 +-- truststore-reference? ts:certificates-ref 161 grouping local-or-truststore-host-keys-grouping 162 +-- (local-or-truststore) 163 +--:(local) {local-definitions-supported}? 164 | +-- local-definition 165 | +-- host-key* ct:ssh-host-key 166 +--:(truststore) {truststore-supported,ssh-host-keys}? 167 +-- truststore-reference? ts:host-keys-ref 168 grouping truststore-grouping 169 +-- certificates* [name] {x509-certificates}? 170 | +-- name? string 171 | +-- description? string 172 | +-- certificate* [name] 173 | +-- name? string 174 | +-- cert trust-anchor-cert-cms 175 | +---n certificate-expiration 176 | +-- expiration-date yang:date-and-time 177 +-- host-keys* [name] {ssh-host-keys}? 178 +-- name? string 179 +-- description? string 180 +-- host-key* [name] 181 +-- name? string 182 +-- host-key ct:ssh-host-key 184 2.2. Example Usage 186 The following example illustrates trust anchors in as 187 described by Section 5.3 in [RFC8342]. This datastore view 188 illustrates data set by the manufacturing process alongside 189 conventional configuration. This trust anchors instance has six sets 190 of pinned certificates and one set of pinned host keys. 192 196 197 198 manufacturers-root-ca-certs 199 200 Certificates built into the device for authenticating 201 manufacturer-signed objects, such as TLS server certificates, 202 vouchers, etc. Note, though listed here, these are not 203 configurable; any attempt to do so will be denied. 204 205 206 Manufacturer Root CA cert 1 207 base64encodedvalue== 208 209 210 Manufacturer Root CA cert 2 211 base64encodedvalue== 212 213 215 216 217 explicitly-trusted-server-certs 218 219 Specific server authentication certificates for explicitly 220 trusted servers. These are needed for server certificates 221 that are not signed by a CA. 222 223 224 Fred Flintstone 225 base64encodedvalue== 226 227 229 230 231 explicitly-trusted-server-ca-certs 232 233 Trust anchors (i.e. CA certs) that are used to authenticate 234 server connections. Servers are authenticated if their 235 certificate has a chain of trust to one of these CA 236 certificates. 237 238 239 ca.example.com 240 base64encodedvalue== 241 242 244 245 246 explicitly-trusted-client-certs 247 248 Specific client authentication certificates for explicitly 249 trusted clients. These are needed for client certificates 250 that are not signed by a CA. 251 252 253 George Jetson 254 base64encodedvalue== 255 256 258 259 260 explicitly-trusted-client-ca-certs 261 262 Trust anchors (i.e. CA certs) that are used to authenticate 263 client connections. Clients are authenticated if their 264 certificate has a chain of trust to one of these CA 265 certificates. 266 267 268 ca.example.com 269 base64encodedvalue== 270 271 273 274 275 common-ca-certs 276 277 Trusted certificates to authenticate common HTTPS servers. 278 These certificates are similar to those that might be 279 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 XXX (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-truststore@2019-10-18.yang" 333 module ietf-truststore { 334 yang-version 1.1; 335 namespace "urn:ietf:params:xml:ns:yang:ietf-truststore"; 336 prefix ts; 338 import ietf-netconf-acm { 339 prefix nacm; 340 reference 341 "RFC 8341: Network Configuration Access Control Model"; 342 } 344 import ietf-crypto-types { 345 prefix ct; 346 reference 347 "RFC YYYY: Common YANG Data Types for Cryptography"; 348 } 350 organization 351 "IETF NETCONF (Network Configuration) Working Group"; 353 contact 354 "WG Web: 355 WG List: 356 Author: Kent Watsen "; 358 description 359 "This module defines a truststore to centralize management 360 of trust anchors including both X.509 certificates and 361 SSH host keys. 363 Copyright (c) 2019 IETF Trust and the persons identified 364 as authors of the code. All rights reserved. 366 Redistribution and use in source and binary forms, with 367 or without modification, is permitted pursuant to, and 368 subject to the license terms contained in, the Simplified 369 BSD License set forth in Section 4.c of the IETF Trust's 370 Legal Provisions Relating to IETF Documents 371 (https://trustee.ietf.org/license-info). 373 This version of this YANG module is part of RFC XXXX 374 (https://www.rfc-editor.org/info/rfcXXXX); see the RFC 375 itself for full legal notices.; 377 The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 378 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 379 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 380 are to be interpreted as described in BCP 14 (RFC 2119) 381 (RFC 8174) when, and only when, they appear in all 382 capitals, as shown here."; 384 revision 2019-10-18 { 385 description 386 "Initial version"; 387 reference 388 "RFC XXXX: A YANG Data Model for a Truststore"; 389 } 391 /****************/ 392 /* Features */ 393 /****************/ 395 feature truststore-supported { 396 description 397 "The 'truststore-supported' feature indicates that the 398 server supports the truststore (i.e., implements the 399 'ietf-truststore' module)."; 400 } 402 feature local-definitions-supported { 403 description 404 "The 'local-definitions-supported' feature indicates that 405 the server supports locally-defined trust anchors."; 406 } 408 feature x509-certificates { 409 description 410 "The 'x509-certificates' feature indicates that the server 411 implements the /truststore/certificates subtree."; 412 } 414 feature ssh-host-keys { 415 description 416 "The 'ssh-host-keys' feature indicates that the server 417 implements the /truststore/host-keys subtree."; 418 } 420 /****************/ 421 /* Typedefs */ 422 /****************/ 424 typedef certificates-ref { 425 type leafref { 426 path "/ts:truststore/ts:certificates/ts:name"; 427 } 428 description 429 "This typedef enables modules to easily define a reference 430 to a set of certificates defined in the truststore."; 431 } 433 typedef host-keys-ref { 434 type leafref { 435 path "/ts:truststore/ts:host-keys/ts:name"; 436 } 437 description 438 "This typedef enables modules to easily define a reference 439 to a set of host keys defined in the truststore."; 440 } 442 /*****************/ 443 /* Groupings */ 444 /*****************/ 446 grouping local-or-truststore-certs-grouping { 447 description 448 "A grouping that expands to allow trust anchors to be 449 either stored locally, within the using data model, or be 450 a reference to trust anchors stored in the truststore."; 451 choice local-or-truststore { 452 mandatory true; 453 case local { 454 if-feature "local-definitions-supported"; 455 container local-definition { 456 description 457 "Container to hold the local trust anchor definitions. 458 A list is defined so as to be symmetric with the 459 truststore definition."; 460 uses ct:trust-anchor-certs-grouping; 461 } 462 } 463 case truststore { 464 if-feature "truststore-supported"; 465 if-feature "x509-certificates"; 466 leaf truststore-reference { 467 type ts:certificates-ref; 468 description 469 "A reference to a set of trust anchors that exists 470 in the truststore."; 471 } 472 } 473 description 474 "A choice between an inlined definition and a definition 475 that exists in the truststore."; 476 } 477 } 479 grouping local-or-truststore-host-keys-grouping { 480 description 481 "A grouping that expands to allow trust anchors to be 482 either stored locally, within the using data model, or be 483 a reference to trust anchors stored in the truststore."; 484 choice local-or-truststore { 485 mandatory true; 486 case local { 487 if-feature "local-definitions-supported"; 488 container local-definition { 489 description 490 "Container to hold the local trust anchor definitions. 491 A list is defined so as to be symmetric with the 492 truststore definition."; 493 leaf-list host-key { 494 nacm:default-deny-write; 495 type ct:ssh-host-key; 496 description 497 "The binary public key data for this host key."; 498 reference 499 "RFC YYYY: Common YANG Data Types for Cryptography"; 500 } 501 } 502 } 503 case truststore { 504 if-feature "truststore-supported"; 505 if-feature "ssh-host-keys"; 506 leaf truststore-reference { 507 type ts:host-keys-ref; 508 description 509 "A reference to a set of trust anchors that exists 510 in the truststore."; 511 } 512 } 513 description 514 "A choice between an inlined definition and a definition 515 that exists in the truststore."; 516 } 517 } 518 grouping truststore-grouping { 519 description 520 "Grouping definition enables use in other contexts. If ever 521 done, implementations SHOULD augment new 'case' statements 522 into local-or-keystore 'choice' statements to supply leafrefs 523 to the new location."; 524 list certificates { 525 if-feature "x509-certificates"; 526 key "name"; 527 description 528 "A list of certificates. These certificates can be 529 used by a server to authenticate clients, or by a client 530 to authenticate servers. Each list of certificates 531 SHOULD be specific to a purpose, as the list as a whole 532 may be referenced by other modules. For instance, a 533 RESTCONF server's configuration might use a specific list 534 of certificates for when authenticating RESTCONF 535 client connections."; 536 leaf name { 537 type string; 538 description 539 "An arbitrary name for this list of certificates."; 540 } 541 leaf description { 542 type string; 543 description 544 "An arbitrary description for this list of 545 certificates."; 546 } 547 list certificate { 548 key "name"; 549 description 550 "A certificate."; 551 leaf name { 552 type string; 553 description 554 "An arbitrary name for this certificate. The 555 name must be unique across all lists of 556 certificates (not just this list) so that leafrefs 557 from another module can resolve to unique values."; 558 } 559 uses ct:trust-anchor-cert-grouping { 560 refine "cert" { 561 mandatory true; 562 } 563 } 564 } 565 } 566 list host-keys { 567 if-feature "ssh-host-keys"; 568 key "name"; 569 description 570 "A list of host keys. These host-keys can 571 be used by clients to authenticate SSH servers. Each 572 list of host keys SHOULD be specific to a purpose, 573 so the list as a whole may be referenced by other modules. 574 For instance, a NETCONF client's configuration might 575 point to a specific list of host keys for when 576 authenticating specific SSH servers."; 577 leaf name { 578 type string; 579 description 580 "An arbitrary name for this list of SSH 581 host keys."; 582 } 583 leaf description { 584 type string; 585 description 586 "An arbitrary description for this list of SSH 587 host keys."; 588 } 589 list host-key { 590 key "name"; 591 description 592 "A host key."; 593 leaf name { 594 type string; 595 description 596 "An arbitrary name for this host-key. Must be 597 unique across all lists of host-keys (not just 598 this list) so that a leafref to it from another module 599 can resolve to unique values."; 600 } 601 leaf host-key { 602 type ct:ssh-host-key; 603 mandatory true; 604 description 605 "The binary public key data for this host key."; 606 reference 607 "RFC YYYY: Common YANG Data Types for Cryptography"; 608 } 609 } 610 } 611 } 613 /*********************************/ 614 /* Protocol accessible nodes */ 615 /*********************************/ 617 container truststore { 618 nacm:default-deny-write; 619 description 620 "The truststore contains sets of X.509 certificates and 621 SSH host keys."; 622 uses truststore-grouping; 623 } 625 } 627 629 3. Security Considerations 631 The YANG module defined in this document is designed to be accessed 632 via YANG based management protocols, such as NETCONF [RFC6241] and 633 RESTCONF [RFC8040]. Both of these protocols have mandatory-to- 634 implement secure transport layers (e.g., SSH, TLS) with mutual 635 authentication. 637 The NETCONF access control model (NACM) [RFC8341] provides the means 638 to restrict access for particular users to a pre-configured subset of 639 all available protocol operations and content. 641 There are a number of data nodes defined in this YANG module that are 642 writable/creatable/deletable (i.e., config true, which is the 643 default). These data nodes may be considered sensitive or vulnerable 644 in some network environments. Write operations (e.g., edit-config) 645 to these data nodes without proper protection can have a negative 646 effect on network operations. These are the subtrees and data nodes 647 and their sensitivity/vulnerability: 649 /: The entire data tree defined by this module is sensitive to 650 write operations. For instance, the addition or removal of any 651 trust anchor may dramatically alter the implemented security 652 policy. For this reason, the NACM extension "default-deny- 653 write" has been set for the entire data tree. 655 None of the readable data nodes in this YANG module are considered 656 sensitive or vulnerable in network environments. 658 This module does not define any RPCs, actions, or notifications, and 659 thus the security consideration for such is not provided here. 661 4. IANA Considerations 663 4.1. The IETF XML Registry 665 This document registers one URI in the "ns" subregistry of the IETF 666 XML Registry [RFC3688]. Following the format in [RFC3688], the 667 following registration is requested: 669 URI: urn:ietf:params:xml:ns:yang:ietf-truststore 670 Registrant Contact: The NETCONF WG of the IETF. 671 XML: N/A, the requested URI is an XML namespace. 673 4.2. The YANG Module Names Registry 675 This document registers one YANG module in the YANG Module Names 676 registry [RFC6020]. Following the format in [RFC6020], the the 677 following registration is requested: 679 name: ietf-truststore 680 namespace: urn:ietf:params:xml:ns:yang:ietf-truststore 681 prefix: ta 682 reference: RFC XXXX 684 5. References 686 5.1. Normative References 688 [I-D.ietf-netconf-crypto-types] 689 Watsen, K. and H. Wang, "Common YANG Data Types for 690 Cryptography", draft-ietf-netconf-crypto-types-10 (work in 691 progress), July 2019. 693 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 694 Requirement Levels", BCP 14, RFC 2119, 695 DOI 10.17487/RFC2119, March 1997, 696 . 698 [RFC7950] Bjorklund, M., Ed., "The YANG 1.1 Data Modeling Language", 699 RFC 7950, DOI 10.17487/RFC7950, August 2016, 700 . 702 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 703 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 704 May 2017, . 706 [RFC8341] Bierman, A. and M. Bjorklund, "Network Configuration 707 Access Control Model", STD 91, RFC 8341, 708 DOI 10.17487/RFC8341, March 2018, 709 . 711 5.2. Informative References 713 [RFC3688] Mealling, M., "The IETF XML Registry", BCP 81, RFC 3688, 714 DOI 10.17487/RFC3688, January 2004, 715 . 717 [RFC6020] Bjorklund, M., Ed., "YANG - A Data Modeling Language for 718 the Network Configuration Protocol (NETCONF)", RFC 6020, 719 DOI 10.17487/RFC6020, October 2010, 720 . 722 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 723 and A. Bierman, Ed., "Network Configuration Protocol 724 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 725 . 727 [RFC8040] Bierman, A., Bjorklund, M., and K. Watsen, "RESTCONF 728 Protocol", RFC 8040, DOI 10.17487/RFC8040, January 2017, 729 . 731 [RFC8340] Bjorklund, M. and L. Berger, Ed., "YANG Tree Diagrams", 732 BCP 215, RFC 8340, DOI 10.17487/RFC8340, March 2018, 733 . 735 [RFC8342] Bjorklund, M., Schoenwaelder, J., Shafer, P., Watsen, K., 736 and R. Wilton, "Network Management Datastore Architecture 737 (NMDA)", RFC 8342, DOI 10.17487/RFC8342, March 2018, 738 . 740 Appendix A. Change Log 742 A.1. 00 to 01 744 o Added features "x509-certificates" and "ssh-host-keys". 746 o Added nacm:default-deny-write to "trust-anchors" container. 748 A.2. 01 to 02 750 o Switched "list pinned-certificate" to use the "trust-anchor-cert- 751 grouping" from crypto-types. Effectively the same definition as 752 before. 754 A.3. 02 to 03 756 o Updated copyright date, boilerplate template, affiliation, folding 757 algorithm, and reformatted the YANG module. 759 A.4. 03 to 04 761 o Added groupings 'local-or-truststore-certs-grouping' and 'local- 762 or-truststore-host-keys-grouping', matching similar definitions in 763 the keystore draft. Note new (and incomplete) "truststore" usage! 765 o Related to above, also added features 'truststore-supported' and 766 'local-trust-anchors-supported'. 768 A.5. 04 to 05 770 o Renamed "trust-anchors" to "truststore" 772 o Removed "pinned." prefix everywhere, to match truststore rename 774 o Moved everything under a top-level 'grouping' to enable use in 775 other contexts. 777 o Renamed feature from 'local-trust-anchors-supported' to 'local- 778 definitions-supported' (same name used in keystore) 780 o Removed the "require-instance false" statement from the "*-ref" 781 typedefs. 783 o Added missing "ssh-host-keys" and "x509-certificates" if-feature 784 statements 786 A.6. 04 to 05 788 o Editorial changes only. 790 Acknowledgements 792 The authors would like to thank for following for lively discussions 793 on list and in the halls (ordered by last name): Martin Bjorklund, 794 Nick Hancock, Balazs Kovacs, Eric Voit, and Liang Xia. 796 Author's Address 798 Kent Watsen 799 Watsen Networks 801 EMail: kent+ietf@watsen.net