< draft-ietf-netconf-crypto-types-07.txt   draft-ietf-netconf-crypto-types-08.txt >
NETCONF Working Group K. Watsen NETCONF Working Group K. Watsen
Internet-Draft Watsen Networks Internet-Draft Watsen Networks
Intended status: Standards Track H. Wang Intended status: Standards Track H. Wang
Expires: December 9, 2019 Huawei Expires: December 19, 2019 Huawei
June 7, 2019 June 17, 2019
Common YANG Data Types for Cryptography Common YANG Data Types for Cryptography
draft-ietf-netconf-crypto-types-07 draft-ietf-netconf-crypto-types-08
Abstract Abstract
This document defines YANG identities, typedefs, the groupings useful This document defines YANG identities, typedefs, the groupings useful
for cryptographic applications. for cryptographic applications.
Editorial Note (To be removed by RFC Editor) Editorial Note (To be removed by RFC Editor)
This draft contains many placeholder values that need to be replaced This draft contains many placeholder values that need to be replaced
with finalized values at the time of publication. This note with finalized values at the time of publication. This note
skipping to change at page 1, line 32 skipping to change at page 1, line 32
Editor instructions are specified elsewhere in this document. Editor instructions are specified elsewhere in this document.
Artwork in this document contains shorthand references to drafts in Artwork in this document contains shorthand references to drafts in
progress. Please apply the following replacements: progress. Please apply the following replacements:
o "XXXX" --> the assigned RFC value for this draft o "XXXX" --> the assigned RFC value for this draft
Artwork in this document contains placeholder values for the date of Artwork in this document contains placeholder values for the date of
publication of this draft. Please apply the following replacement: publication of this draft. Please apply the following replacement:
o "2019-06-07" --> the publication date of this draft o "2019-06-17" --> the publication date of this draft
The following Appendix section is to be removed prior to publication: The following Appendix section is to be removed prior to publication:
o Appendix B. Change Log o Appendix B. Change Log
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/. Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 9, 2019. This Internet-Draft will expire on December 19, 2019.
Copyright Notice Copyright Notice
Copyright (c) 2019 IETF Trust and the persons identified as the Copyright (c) 2019 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of (https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 2, line 29 skipping to change at page 2, line 29
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3
2. The Crypto Types Module . . . . . . . . . . . . . . . . . . . 3 2. The Crypto Types Module . . . . . . . . . . . . . . . . . . . 3
2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3 2.1. Tree Diagram . . . . . . . . . . . . . . . . . . . . . . 3
2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 4 2.2. YANG Module . . . . . . . . . . . . . . . . . . . . . . . 5
3. Security Considerations . . . . . . . . . . . . . . . . . . . 41 3. Security Considerations . . . . . . . . . . . . . . . . . . . 41
3.1. Support for Algorithms . . . . . . . . . . . . . . . . . 42 3.1. Support for Algorithms . . . . . . . . . . . . . . . . . 41
3.2. No Support for CRMF . . . . . . . . . . . . . . . . . . . 42 3.2. No Support for CRMF . . . . . . . . . . . . . . . . . . . 42
3.3. Access to Data Nodes . . . . . . . . . . . . . . . . . . 42 3.3. Access to Data Nodes . . . . . . . . . . . . . . . . . . 42
4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43
4.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 43 4.1. The IETF XML Registry . . . . . . . . . . . . . . . . . . 43
4.2. The YANG Module Names Registry . . . . . . . . . . . . . 44 4.2. The YANG Module Names Registry . . . . . . . . . . . . . 43
5. References . . . . . . . . . . . . . . . . . . . . . . . . . 44 5. References . . . . . . . . . . . . . . . . . . . . . . . . . 44
5.1. Normative References . . . . . . . . . . . . . . . . . . 44 5.1. Normative References . . . . . . . . . . . . . . . . . . 44
5.2. Informative References . . . . . . . . . . . . . . . . . 46 5.2. Informative References . . . . . . . . . . . . . . . . . 46
Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 49 Appendix A. Examples . . . . . . . . . . . . . . . . . . . . . . 49
A.1. The "asymmetric-key-pair-with-certs-grouping" Grouping . 49 A.1. The "asymmetric-key-pair-with-certs-grouping" Grouping . 49
A.2. The "generate-certificate-signing-request" Action . . . . 53 A.2. The "generate-certificate-signing-request" Action . . . . 51
A.3. The "certificate-expiration" Notification . . . . . . . . 53 A.3. The "certificate-expiration" Notification . . . . . . . . 52
Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 54 Appendix B. Change Log . . . . . . . . . . . . . . . . . . . . . 53
B.1. I-D to 00 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.1. I-D to 00 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.2. 00 to 01 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 54 B.3. 01 to 02 . . . . . . . . . . . . . . . . . . . . . . . . 53
B.4. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 55 B.4. 02 to 03 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.5. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 55 B.5. 03 to 04 . . . . . . . . . . . . . . . . . . . . . . . . 54
B.6. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 56 B.6. 04 to 05 . . . . . . . . . . . . . . . . . . . . . . . . 55
B.7. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 56 B.7. 05 to 06 . . . . . . . . . . . . . . . . . . . . . . . . 55
B.8. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 56 B.8. 06 to 07 . . . . . . . . . . . . . . . . . . . . . . . . 55
Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 57 B.9. 07 to 08 . . . . . . . . . . . . . . . . . . . . . . . . 56
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 57 Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 56
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 56
1. Introduction 1. Introduction
This document defines a YANG 1.1 [RFC7950] module specifying This document defines a YANG 1.1 [RFC7950] module specifying
identities, typedefs, and groupings useful for cryptography. identities, typedefs, and groupings useful for cryptography.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
skipping to change at page 3, line 29 skipping to change at page 3, line 30
2. The Crypto Types Module 2. The Crypto Types Module
2.1. Tree Diagram 2.1. Tree Diagram
This section provides a tree diagram [RFC8340] for the "ietf-crypto- This section provides a tree diagram [RFC8340] for the "ietf-crypto-
types" module. Only the groupings as represented, as tree diagrams types" module. Only the groupings as represented, as tree diagrams
have no means to represent identities or typedefs. have no means to represent identities or typedefs.
module: ietf-crypto-types module: ietf-crypto-types
grouping symmetric-key-grouping:
+---- algorithm identityref
+---- (key-type)
+--:(key)
| +---- key? binary
+--:(hidden-key)
+---- hidden-key? empty
grouping public-key-grouping: grouping public-key-grouping:
+---- algorithm asymmetric-key-algorithm-ref +---- algorithm asymmetric-key-algorithm-ref
+---- public-key binary +---- public-key binary
grouping asymmetric-key-pair-grouping: grouping asymmetric-key-pair-grouping:
+---- algorithm asymmetric-key-algorithm-ref +---- algorithm asymmetric-key-algorithm-ref
+---- public-key binary +---- public-key binary
+---- private-key union +---- (private-key-type)
+--:(private-key)
| +---- private-key? binary
+--:(hidden-private-key)
+---- hidden-private-key? empty
grouping trust-anchor-cert-grouping: grouping trust-anchor-cert-grouping:
+---- cert? trust-anchor-cert-cms +---- cert? trust-anchor-cert-cms
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
grouping trust-anchor-certs-grouping: grouping trust-anchor-certs-grouping:
+---- cert* trust-anchor-cert-cms +---- cert* trust-anchor-cert-cms
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
grouping end-entity-cert-grouping: grouping end-entity-cert-grouping:
+---- cert? end-entity-cert-cms +---- cert? end-entity-cert-cms
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
grouping end-entity-certs-grouping: grouping end-entity-certs-grouping:
+---- cert* end-entity-cert-cms +---- cert* end-entity-cert-cms
skipping to change at page 4, line 4 skipping to change at page 4, line 17
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
grouping end-entity-cert-grouping: grouping end-entity-cert-grouping:
+---- cert? end-entity-cert-cms +---- cert? end-entity-cert-cms
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
grouping end-entity-certs-grouping: grouping end-entity-certs-grouping:
+---- cert* end-entity-cert-cms +---- cert* end-entity-cert-cms
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
grouping asymmetric-key-pair-with-cert-grouping: grouping asymmetric-key-pair-with-cert-grouping:
+---- algorithm +---- algorithm
| asymmetric-key-algorithm-ref | asymmetric-key-algorithm-ref
+---- public-key binary +---- public-key binary
+---- private-key union +---- (private-key-type)
| +--:(private-key)
| | +---- private-key? binary
| +--:(hidden-private-key)
| +---- hidden-private-key? empty
+---- cert? end-entity-cert-cms +---- cert? end-entity-cert-cms
+---n certificate-expiration +---n certificate-expiration
+--ro expiration-date ietf-yang-types:date-and-time +--ro expiration-date ietf-yang-types:date-and-time
+---x generate-certificate-signing-request +---x generate-certificate-signing-request
+---- input +---- input
| +---w subject binary | +---w subject binary
| +---w attributes? binary | +---w attributes? binary
+---- output +---- output
+--ro certificate-signing-request binary +--ro certificate-signing-request binary
grouping asymmetric-key-pair-with-certs-grouping: grouping asymmetric-key-pair-with-certs-grouping:
+---- algorithm +---- algorithm
| asymmetric-key-algorithm-ref | asymmetric-key-algorithm-ref
+---- public-key binary +---- public-key binary
+---- private-key union +---- (private-key-type)
| +--:(private-key)
| | +---- private-key? binary
| +--:(hidden-private-key)
| +---- hidden-private-key? empty
+---- certificates +---- certificates
| +---- certificate* [name] | +---- certificate* [name]
| +---- name string | +---- name string
| +---- cert? end-entity-cert-cms | +---- cert? end-entity-cert-cms
| +---n certificate-expiration | +---n certificate-expiration
| +--ro expiration-date ietf-yang-types:date-and-time | +--ro expiration-date ietf-yang-types:date-and-time
+---x generate-certificate-signing-request +---x generate-certificate-signing-request
+---- input +---- input
| +---w subject binary | +---w subject binary
| +---w attributes? binary | +---w attributes? binary
skipping to change at page 4, line 49 skipping to change at page 5, line 20
This module has normative references to [RFC2404], [RFC3565], This module has normative references to [RFC2404], [RFC3565],
[RFC3686], [RFC4106], [RFC4253], [RFC4279], [RFC4309], [RFC4494], [RFC3686], [RFC4106], [RFC4253], [RFC4279], [RFC4309], [RFC4494],
[RFC4543], [RFC4868], [RFC5280], [RFC5652], [RFC5656], [RFC6187], [RFC4543], [RFC4868], [RFC5280], [RFC5652], [RFC5656], [RFC6187],
[RFC6991], [RFC7919], [RFC8268], [RFC8332], [RFC8341], [RFC8422], [RFC6991], [RFC7919], [RFC8268], [RFC8332], [RFC8341], [RFC8422],
[RFC8446], and [ITU.X690.2015]. [RFC8446], and [ITU.X690.2015].
This module has an informational reference to [RFC2986], [RFC3174], This module has an informational reference to [RFC2986], [RFC3174],
[RFC4493], [RFC5915], [RFC6125], [RFC6234], [RFC6239], [RFC6507], [RFC4493], [RFC5915], [RFC6125], [RFC6234], [RFC6239], [RFC6507],
[RFC8017], [RFC8032], [RFC8439]. [RFC8017], [RFC8032], [RFC8439].
<CODE BEGINS> file "ietf-crypto-types@2019-06-07.yang" <CODE BEGINS> file "ietf-crypto-types@2019-06-17.yang"
module ietf-crypto-types { module ietf-crypto-types {
yang-version 1.1; yang-version 1.1;
namespace "urn:ietf:params:xml:ns:yang:ietf-crypto-types"; namespace "urn:ietf:params:xml:ns:yang:ietf-crypto-types";
prefix ct; prefix ct;
import ietf-yang-types { import ietf-yang-types {
prefix yang; prefix yang;
reference reference
"RFC 6991: Common YANG Data Types"; "RFC 6991: Common YANG Data Types";
skipping to change at page 6, line 5 skipping to change at page 6, line 26
(https://www.rfc-editor.org/info/rfcXXXX); see the RFC (https://www.rfc-editor.org/info/rfcXXXX); see the RFC
itself for full legal notices.; itself for full legal notices.;
The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL',
'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED',
'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document 'NOT RECOMMENDED', 'MAY', and 'OPTIONAL' in this document
are to be interpreted as described in BCP 14 (RFC 2119) are to be interpreted as described in BCP 14 (RFC 2119)
(RFC 8174) when, and only when, they appear in all (RFC 8174) when, and only when, they appear in all
capitals, as shown here."; capitals, as shown here.";
revision 2019-06-07 { revision 2019-06-17 {
description description
"Initial version"; "Initial version";
reference reference
"RFC XXXX: Common YANG Data Types for Cryptography"; "RFC XXXX: Common YANG Data Types for Cryptography";
} }
/****************/
/* Features */
/****************/
feature generate-key {
description
"Indicates that the server supports the configuration
private key values using the 'value-to-be-generated'
prefix.";
}
feature hidden-key {
description
"Indicates that the server supports the configuration
of hidden private keys, whether by the using the
'value-to-be-generated-and-hidden' value or the
'value-to-be-hidden' prefix.";
}
/**************************************/ /**************************************/
/* Identities for Hash Algorithms */ /* Identities for Hash Algorithms */
/**************************************/ /**************************************/
identity hash-algorithm { identity hash-algorithm {
description description
"A base identity for hash algorithm verification."; "A base identity for hash algorithm verification.";
} }
identity sha-224 { identity sha-224 {
skipping to change at page 33, line 19 skipping to change at page 33, line 23
reference reference
"RFC 5280: "RFC 5280:
Internet X.509 Public Key Infrastructure Certificate Internet X.509 Public Key Infrastructure Certificate
and Certificate Revocation List (CRL) Profile."; and Certificate Revocation List (CRL) Profile.";
} }
/**********************************************/ /**********************************************/
/* Groupings for keys and/or certificates */ /* Groupings for keys and/or certificates */
/**********************************************/ /**********************************************/
grouping symmetric-key-grouping {
description
"A symmetric key and algorithm.";
leaf algorithm {
type identityref {
base "ct:encryption-algorithm";
}
mandatory true;
description
"The algorithm to be used when generating the key.";
reference
"RFC CCCC: Common YANG Data Types for Cryptography";
}
choice key-type {
mandatory true;
description
"Choice between key types.";
leaf key {
nacm:default-deny-all;
type binary;
description
"The binary value of the key. The interpretation of
the value is defined by 'algorithm'. For example,
FIXME.";
reference
"RFC XXXX: FIXME";
}
leaf hidden-key {
nacm:default-deny-write;
type empty;
description
"A permanently hidden key. How such keys are created
is outside the scope of this module.";
}
}
}
grouping public-key-grouping { grouping public-key-grouping {
description description
"A public key and its associated algorithm."; "A public key and its associated algorithm.";
leaf algorithm { leaf algorithm {
nacm:default-deny-write; nacm:default-deny-write;
type asymmetric-key-algorithm-ref; type asymmetric-key-algorithm-ref;
mandatory true; mandatory true;
description description
"Identifies the key's algorithm."; "Identifies the key's algorithm.";
reference reference
skipping to change at page 34, line 4 skipping to change at page 34, line 44
"RFC 8017: Public-Key Cryptography Standards (PKCS) #1: "RFC 8017: Public-Key Cryptography Standards (PKCS) #1:
RSA Cryptography Specifications Version 2.2. RSA Cryptography Specifications Version 2.2.
RFC 5915: Elliptic Curve Private Key Structure."; RFC 5915: Elliptic Curve Private Key Structure.";
} }
} }
grouping asymmetric-key-pair-grouping { grouping asymmetric-key-pair-grouping {
description description
"A private key and its associated public key and algorithm."; "A private key and its associated public key and algorithm.";
uses public-key-grouping; uses public-key-grouping;
leaf private-key { choice private-key-type {
nacm:default-deny-all;
type union {
type binary;
type string {
pattern
'permanently-hidden'
+ '|encrypted-by:.*:[A-Za-z0-9+/]+[=]{1,3}'
+ '|value-to-be-generated(-and-hidden)?'
+ '|value-to-be-hidden:[A-Za-z0-9+/]+[=]{1,3}';
}
}
mandatory true; mandatory true;
description description
"Either the binary value of the private key or a value "Choice between key types.";
indentifing special input and output values described leaf private-key {
below. The key's value is interpreted by the 'algorithm'. nacm:default-deny-all;
For example, a DSA key is an integer, an RSA key is type binary;
represented as RSAPrivateKey as defined in RFC 8017, and description
an ECC key is represented as ECPrivateKey as defined in "The value of the binary key. The key's value is
RFC 5915. interpreted by the 'algorithm'. For example, a DSA key
is an integer, an RSA key is represented as RSAPrivateKey
Special input and output values: as defined in RFC 8017, and an ECC key is represented as
ECPrivateKey as defined in RFC 5915.";
permanently-hidden reference
"RFC 8017: Public-Key Cryptography Standards (PKCS) #1:
Primarily an output value indicating that the private RSA Cryptography Specifications Version 2.2.
key value is not available in any form. The only time RFC 5915: Elliptic Curve Private Key Structure.";
this value MAY be used as a input value is when it is }
being used to copy a manufacturer-generated value from leaf hidden-private-key {
<operational> to <running>. nacm:default-deny-write;
type empty;
encrypted-by:*:[A-Za-z0-9+/]+[=]{1,3} description
"A permanently hidden key. How such keys are created
Primarily an output value indicating that the private is outside the scope of this module.";
key is encrypted using another key, identified by the
'by' attribute. The only time this value MAY be used
as a input value is when it is being used to copy a
manufacturer-generated value from <operational> to
<running>. Following the prefix is the base64-encoded
value of the encrypted private key.
value-to-be-generated(-and-hidden)?
An input value used to request the system to generate,
and optionally hide, the public/private key pair. When
used, the 'public-key' value MUST be empty (zero bytes).
Without the optional '-and-hidden' postfix, the generated
key pair is stored in the configuration data store as if
the values had been configured by the client.
With the optional '-and-hidden' postfix, the generated
key pair is 'hidden' and thereafter be reported using
either 'permanently-hidden' or 'encrypted-by:*:'.
The server's support for 'value-to-be-generated' input
value is known by the 'generate-key' feature, and the
server's support for 'value-to-be-generated-and-hidden'
value is known by the combination of both the 'generate-
key' and 'hidden-key' features.
value-to-be-hidden:[A-Za-z0-9+/]+[=]{1,3}
An input value used to request the system to store the
provided private key such that it will thereafter be
reported using either as 'permanently-hidden' or
'encrypted-by:*:'. Following the prefix is the
base64-encoded value of the private key.
The server's support for 'value-to-be-hidden' input
value is known by the 'hidden-key' feature.";
reference
"RFC 8017: Public-Key Cryptography Standards (PKCS) #1:
RSA Cryptography Specifications Version 2.2.
RFC 5915: Elliptic Curve Private Key Structure.";
} }
} }
}
grouping trust-anchor-cert-grouping { grouping trust-anchor-cert-grouping {
description description
"A trust anchor certificate, and a notification for when "A trust anchor certificate, and a notification for when
it is about to (or already has) expire."; it is about to (or already has) expire.";
leaf cert { leaf cert {
nacm:default-deny-write; nacm:default-deny-write;
type trust-anchor-cert-cms; type trust-anchor-cert-cms;
description description
"The binary certificate data for this certificate."; "The binary certificate data for this certificate.";
skipping to change at page 52, line 5 skipping to change at page 51, line 7
} }
uses ct:asymmetric-key-pair-with-certs-grouping; uses ct:asymmetric-key-pair-with-certs-grouping;
description description
"An asymmetric key pair with associated certificates."; "An asymmetric key pair with associated certificates.";
} }
} }
} }
Given the above example usage module, the following example Given the above example usage module, the following example
illustrates some configured keys. illustrates some configured keys.
<keys xmlns="http://example.com/ns/example-crypto-types-usage"> <keys xmlns="http://example.com/ns/example-crypto-types-usage">
<key> <key>
<name>ex-key</name> <name>ex-key</name>
<algorithm <algorithm
xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">
ct:rsa2048 ct:rsa2048
</algorithm> </algorithm>
<public-key>base64encodedvalue==</public-key> <public-key>base64encodedvalue==</public-key>
<private-key>base64encodedvalue==</private-key> <private-key>base64encodedvalue==</private-key>
<certificates> <certificates>
<certificate> <certificate>
<name>ex-cert</name> <name>ex-cert</name>
<cert>base64encodedvalue==</cert> <cert>base64encodedvalue==</cert>
</certificate> </certificate>
</certificates> </certificates>
</key> </key>
<key> <key>
<name>ex-hidden-key</name> <name>ex-hidden-key</name>
<algorithm <algorithm
xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types"> xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">
ct:rsa2048 ct:rsa2048
</algorithm> </algorithm>
<public-key>base64encodedvalue==</public-key> <public-key>base64encodedvalue==</public-key>
<private-key>permanently-hidden</private-key> <hidden-private-key/>
<certificates> <certificates>
<certificate> <certificate>
<name>ex-hidden-key-cert</name> <name>ex-hidden-key-cert</name>
<cert>base64encodedvalue==</cert> <cert>base64encodedvalue==</cert>
</certificate> </certificate>
</certificates> </certificates>
</key> </key>
<key> </keys>
<name>ex-encrypted-key</name>
<algorithm
xmlns:ct="urn:ietf:params:xml:ns:yang:ietf-crypto-types">
ct:rsa2048
</algorithm>
<public-key>base64encodedvalue==</public-key>
<private-key>encrypted-by:ex-key:base64encodedvalue==</private-key>
<certificates>
<certificate>
<name>ex-encrypted-key-cert</name>
<cert>base64encodedvalue==</cert>
</certificate>
</certificates>
</key>
</keys>
A.2. The "generate-certificate-signing-request" Action A.2. The "generate-certificate-signing-request" Action
The following example illustrates the "generate-certificate-signing- The following example illustrates the "generate-certificate-signing-
request" action in use with the NETCONF protocol. request" action in use with the NETCONF protocol.
REQUEST REQUEST
<rpc message-id="101" <rpc message-id="101"
xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> xmlns="urn:ietf:params:xml:ns:netconf:base:1.0">
skipping to change at page 57, line 5 skipping to change at page 56, line 5
a failure. a failure.
B.8. 06 to 07 B.8. 06 to 07
o Added clarifications that implementations SHOULD assert that o Added clarifications that implementations SHOULD assert that
configured certificates contain the matching public key. configured certificates contain the matching public key.
o Replaced the 'generate-hidden-key' and 'install-hidden-key' o Replaced the 'generate-hidden-key' and 'install-hidden-key'
actions with special 'crypt-hash' -like input/output values. actions with special 'crypt-hash' -like input/output values.
B.9. 07 to 08
o Removed the 'generate-key and 'hidden-key' features.
o Added grouping symmetric-key-grouping
o Modified 'asymmetric-key-pair-grouping' to have a 'choice'
statement for the keystone module to augment into, as well as
replacing the 'union' with leafs (having different NACM settings.
Acknowledgements Acknowledgements
The authors would like to thank for following for lively discussions The authors would like to thank for following for lively discussions
on list and in the halls (ordered by last name): Martin Bjorklund, on list and in the halls (ordered by last name): Martin Bjorklund,
Nick Hancock, Balazs Kovacs, Juergen Schoenwaelder, Eric Voit, and Nick Hancock, Balazs Kovacs, Juergen Schoenwaelder, Eric Voit, and
Liang Xia. Liang Xia.
Authors' Addresses Authors' Addresses
Kent Watsen Kent Watsen
 End of changes. 23 change blocks. 
168 lines changed or deleted 151 lines changed or added

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