Sandelman Software Works

mcr+ietf@sandelman.ca

Huawei Technologies

william.panwei@huawei.com

Internet anima Working Group Internet-Draft This document describes an extension of the RFC8366 Voucher Artifact in order to support delegation of signing authority. The initial voucher pins a public identity, and that public indentity can then issue additional vouchers. This chain of authorization can support permission-less resale of devices, as well as guarding against business failure of the BRSKI Manufacturer Authorized Signing Authority (MASA).

The voucher artifact provides a proof from a manufacturer’s authorizing signing authority (MASA) of the intended owner of a device. This is used by an onboarding Pledge device in BRSKI (, ), and SZTP (). There are a number of criticisms of the MASA concept. They include: the MASA must be reachable to the Registar during the onboarding process. while the use of a nonceless voucher (see section 4) can permit the MASA to be offline, it still requires the public key/certificate of the Registrar to be known at issuing time. The device owner is always strongly dependent on the MASA service. the MASA must approve all transfers of ownership, impacting the rights of the supply chain distributors to transfer ownership as they see fit. if the Registrar has any nonceless vouchers, then it can not change it’s public key, nor can it change which certification authority it uses. it is not possible for a MASA to pin ownership to a Registrar by Certification Authority plus DN. the creator of an assembly of parts/components can speak for the entire assembly of parts in a transparent way.

This voucher artifact satisfies the following requirements:

A Registrar wishes to onboard devices while it is not being connected to the Internet and MASA.

An owner of a device wishes to resale it which has previously been onboarded to a third party without specific authorization from the manufacturer.

The owner/manager of a registrar wishes to be able to replace its domain registration key. Replacing the registration key would invalidate any previously acquired (nonceless) vouchers. Any devices which have not been onboarded, or which need to be factory reset, would not trust a replacement key.

An assembly may consist of a number of parts which are onboarded to a local controller during the manufacturing process. Subsequent to this, the entire assembly will be shipped to a customer who wishes to onboard all the components. The sub-components of the assembly needs to communicate with other sub-components, and so all the parts need to transparently onboarded. (This is contrasted with an assembly where the controller acts as a security gateway. Such a gateway might be a single point of failure) Assemblies may nest quite deeply.

The MASA will issue a voucher that delegates it’s signing authority for one or more devices to a specific Registrar. This is called a “delegation voucher”. This Registrar can then operate as an authorized signing authority for the manufacturer, and can subsequently issue additional vouchers binding the pledge to new Registrars. This delegation can potentially be repeated multiple times to enable second, third, or n-th level of resale. The delegation voucher may be stored by the pledge for storage, to be included by the pledge in subsequent bootstrap operations. The inclusion of the delegation voucher permits next Registrar with heuristics that permit it to find the delegated authorized signing authority (DASA). The delegation voucher pins the identity of the delegated authority using a variety of different mechanisms which are covered in .

The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “NOT RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in BCP 14 when, and only when, they appear in all capitals, as shown here. the Delegated Authorized Signing Authority (DASA) is a service that can generate vouchers for one or more pledges to provide bootstrap authority, which is separated and delegated from the manufacturer. a Delegation Voucher is an format voucher that has additional fields to provide details of the entity to which authority has been delegated. a voucher that is not the final voucher linking a pledge to its owner. a voucher that is the final voucher linking a pledge to its owner.

The following tree diagram shows the extensions to the voucher. There are a few new fields: A global enable flag to the pledge that it can be delegated (true) or not (false). With default, this flag is false, which is consistent with the voucher artifact in RFC8366. An subject-public-key-info for a public key of the new DASA A string for the rfc822Name SubjectAltName contents of the new DASA; (XXX- is it enough, should other DNs be considered?) One or a series of Intermediate Vouchers that delegate authority to the DASA. For the latter case, the series of Intermediate Vouchers constitute a nested structure, and the most inner voucher is from the MASA, which is called terminal voucher here A set of voucher identities being consistent with the series of Intermediate Vouchers Number of delegations still available. If zero or omitted, then this is a terminal voucher and may not be further delegated. In addition, the serial-number field is no longer a plain leaf, but can also be an array (See ).

This module uses the grouping that was created in to extend the definition.

file "ietf-delegated-voucher@2020-01-06.yang" module ietf-delegated-voucher { yang-version 1.1; namespace "urn:ietf:params:xml:ns:yang:ietf-delegated-voucher"; prefix "delegated"; import ietf-restconf { prefix rc; description "This import statement is only present to access the yang-data extension defined in RFC 8040."; reference "RFC 8040: RESTCONF Protocol"; } // maybe should import from constrained-voucher instead! import ietf-voucher { prefix "v"; } organization "IETF ANIMA Working Group"; contact "WG Web: WG List: Author: Michael Richardson "; description "This module extends the RFC8366 voucher format to provide a mechanism by which the authority to issue additional vouchers may be delegated to another entity The key words 'MUST', 'MUST NOT', 'REQUIRED', 'SHALL', 'SHALL NOT', 'SHOULD', 'SHOULD NOT', 'RECOMMENDED', 'MAY', and 'OPTIONAL' in the module text are to be interpreted as described in BCP 14 RFC 2119, and RFC8174."; revision "2020-01-06" { description "Initial version"; reference "RFC XXXX: Voucher Profile for Delegation Vouchers"; } rc:yang-data voucher-delegated-artifact { // YANG data template for a voucher. uses voucher-delegated-grouping; } // Grouping defined for future usage grouping voucher-delegated-grouping { description "Grouping to allow reuse/extensions in future work."; uses v:voucher-artifact-grouping { refine voucher/pinned-domain-cert { mandatory false; } augment "voucher" { description "Base the delegated voucher upon the regular one"; leaf delegation-enable-flag { type boolean; description "A global enable flag to the pledge that it can be delegated (true) or not (false). With default, this flag is false, which is consistent with the voucher artifact in RFC8366. "; } leaf pinned-delegation-cert-authority { type binary; description "An subject-public-key-info for a public key of the certificate authority that is to be trusted to issue a delegation voucher to the Registrar. This is not used by end-vouchers, and only valid when delegation-enable-flag is true."; } leaf pinned-delegation-cert-name { type binary; description "A string for the rfc822Name SubjectAltName contents which will be trusted to issue delegation vouchers. This is not used by end-vouchers, and only valid when delegation-enable-flag is true."; } leaf delegation-voucher { type binary; description "The intermediate voucher that delegates authority to the entity that signs this voucher is to be included here, and only valid when delegation-enable-flag is true."; } leaf intermediate-identities { type binary; description "A set of identities that will be needed to validate the chain of vouchers, and only valid when delegation-enable-flag is true. MAY BE REDUNDANT"; } leaf delegation-countdown { type int16; description "Number of delegations still available, and only valid when delegation-enable-flag is true. If zero or omitted, then this is a terminal voucher and may not be further delegated"; } } } } } ]]>

The defines a mechanism to return a single voucher to the pledge. This protocol requires a number of additional items to be returned to the pledge for evaluation: the series of Intermediate Vouchers that leads to the DASA, and the public keys (often as certificates) of the Registrars on the Delegation Path that leads to each Authority.

A MASA MAY delegate multiple devices to the same Registrar by putting an array of items in the “serial-number” attributes. (XXX-how to describe this in the YANG, and the detailed mechanism, are TBD)

The use of a Delegation Voucher requires changes to how the pledge evaluates the voucher that is returned to by the Registrar. There are no significant changes to the voucher-request that is made. The pledge continues to pin the identity of the Registrar to which it is connected, providing a nonce to establish freshness. A pledge which has previously stored a Delegation Voucher and DASA , SHOULD include it in its voucher request. This will be in the form of a certificate provided by the “previous” owner. This allows the Registrar to discover the previous authority for the pledge. As the pledge has no idea if it connecting to an entity that it previously has connected to, it needs to include this certificate anyway. The pledge receives a voucher from the Registrar. This voucher is called the zero voucher. It will observe that the voucher is not signed with its built-in manufacturer trust anchor and it can not verify it. The pledge will examine the voucher to look for the “delegation-voucher” and the “intermediate-identities” attributes within the voucher. A certificate from the set of intermediate-identities is expected to validate the signature on this zeroth end-entity voucher. (XXX- This attribute can be replaced by the CMS certificate chain) The contained delegation-voucher object is to be interpreted as an (Intermediate) Voucher. This first voucher is called the first voucher, or “voucher[1]”. Generically, for voucher[i], the voucher found in the delegation-voucher is called voucher[i+1]. If voucher[i] can be validated by a built-in trust anchor, then the process is done. If not, then voucher[i] is examined in a recursive process until there are no further embedded vouchers. The last voucher[n] is expected to be validated by a built-in manufacturer trust anchor. Once the top (n-th) voucher is found, then the pinned-certificate-authority is added to the working set of trust anchors. The “pinned-certificate-name” attribute is used along with the trust anchor to validate the certificate chain provided with the (n-1)th voucher. This is repeated (unwinding the recursive processing) until the zeroth voucher has been validated.

The Registrar is the component that authenticates the pledge, makes authorization decisions, and distributes vouchers. If the vouchers is delegated, then the registrar need to co-ordinate MASA and DASA.

The pledge continues to use its manufacturer issued IDevID when performing BRSKI-style onboarding. The IDevID contains an extension, the MASA URL (see section 2.3.2). The IDevID certificate is not expected to be updated when the device is resold, nor may it be practical for an intermediate owner to be able to replace the IDevID with their own. (Some devices may support having an intermediate owner replace the IDevID, in which case this section does not apply) The Registrar needs to be informed that it should not contact a MASA using the URL in the IDevID, but rather to contact the previous owner’s DASA. This can be accomplished by local override, as described in section 5.4:

The above override needs to be established on a per-device basis. It requires per-device configuration which is very much non-autonomic. There are two other alternatives: The Manufacturer could be aware of any Delegation Vouchers that it has issued for a particular device, and when contacted by the Registrar, it could redirect the Registrar to its DASA. And the DASA may redirect the Registrar to its delegated DASA, this process is recursive to the final DASA. The Pledge could provide a signed statement from the manufacturer providing the Registrar with a pointer to the DASA. Option 1 requires that the Registrar still contact the MASA, violating most of the goals from . Option 2 requires a signed artifact, and conveniently, the Delegation Voucher is exactly the item needed. The most difficult problem is that the Pledge needs to (a) store one or more Delegation Vouchers in a non-volatile storage that survives factory reset operations, (b) attach these items to the pledge’s voucher-request. The extension to the voucher-request described below provides for a contained for these Delegation Vouchers.

This case has many scenarioes in application. For example, due to the willing of some devices’ owner, or due to the creditor or bankruptcy, their devices need to resale to some third party, but they have previously been onboarded without specific authorization from the manufacturer. Aother example is for some owner, which PKI system is on the cloud initially, but later, they wish to change its CA, and it is effectively a “resale”. Then, the registrar of third party must override MASA URL, contacting this owner’s registrar for voucher. Here, the owner’s registrar is delegation authority. Furthurly, the pledges may be resaled many times, and when onboarding, they will receive all vouchers in order with the sale chain, firstly masa vouchour, then 1st intermidate, 2nd intermidate, till to the final dealer. In this case, the pledge’s authorization form a signed voucher chain. In addition, for a pledge, resale can’t be forever, so the delegation voucher need specify the limit number of resales with “delegation-countdown”. The following illustrates a delegation voucher for a pledge: { “ietf-delegated-voucher:voucher”: { “created-on”: “2020-07-14T06:28:31Z”, “expire-on”: “2022-07-31T01:61:80Z”, “assertion”: “logged”, “serial-number”: “JADA123456789”, “delegation-enable-flag”: true, “pinned-delegation-cert-authority”: “base64encodedvalue”, “pinned-delegation-cert-name”: “base64encodedvalue”, “delegation-voucher”: “base64encodedvalue”, “intermediate-identities”: “intermediateId1”, “delegation-countdown”: 1, } }

In some application, many pledges which come from multiple componet manufactures, need to be assemblied together in the first sale, In this time, the owner is assembly controller, so the pledge’s voucher need to include these delegation options. In addition, there are also transparent assembly, for exmale rail wagon scenario. Firstly, the assembly onboards normally to get all pledges’ vouchers, then this assembly acts as intermidate registrar, who “sell” these pledges to every rail wagon registrar.

TBD

YYY

As described in the Security Considerations section of (section 7.4), the YANG module specified in this document defines the schema for data that is subsequently encapsulated by a CMS signed-data content type, as described in Section 5 of . As such, all of the YANG modeled data is protected from modification. The use of YANG to define data structures, via the ‘yang-data’ statement, is relatively new and distinct from the traditional use of YANG to define an API accessed by network management protocols such as NETCONF and RESTCONF . For this reason, these guidelines do not follow template described by Section 3.7 of .

This document requires the following IANA actions:

This document registers a URI in the “IETF XML Registry” . IANA is asked to register the following:

This document registers a YANG module in the “YANG Module Names” registry . IANA is asked to register the following:

Hello.

RFC 2119 specifies common key words that may be used in protocol specifications. This document aims to reduce the ambiguity by clarifying that only UPPERCASE usage of the key words have the defined special meanings. This document defines a strategy to securely assign a pledge to an owner using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher".This document defines an artifact format as a YANG-defined JSON document that has been signed using a Cryptographic Message Syntax (CMS) structure. Other YANG-derived formats are possible. The voucher artifact is normally generated by the pledge's manufacturer (i.e., the Manufacturer Authorized Signing Authority (MASA)).This document only defines the voucher artifact, leaving it to other documents to describe specialized protocols for accessing it. This document specifies automated bootstrapping of an Autonomic Control Plane. To do this a Secure Key Infrastructure is bootstrapped. This is done using manufacturer-installed X.509 certificates, in combination with a manufacturer's authorizing service, both online and offline. We call this process the Bootstrapping Remote Secure Key Infrastructure (BRSKI) protocol. Bootstrapping a new device can occur using a routable address and a cloud service, or using only link-local connectivity, or on limited/ disconnected networks. Support for deployment models with less stringent security requirements is included. Bootstrapping is complete when the cryptographic identity of the new key infrastructure is successfully deployed to the device. The established secure connection can be used to deploy a locally issued certificate to the device as well. This document defines a strategy to securely assign a pledge to an owner, using an artifact signed, directly or indirectly, by the pledge's manufacturer. This artifact is known as a "voucher". This document builds upon the work in [RFC8366], encoding the resulting artifact in CBOR. Use with two signature technologies are described. Additionally, this document explains how constrained vouchers may be transported as an extension to the [I-D.ietf-ace-coap-est] protocol. In many standards track documents several words are used to signify the requirements in the specification. These words are often capitalized. This document defines these words as they should be interpreted in IETF documents. This document specifies an Internet Best Current Practices for the Internet Community, and requests discussion and suggestions for improvements. This document describes an IANA maintained registry for IETF standards which use Extensible Markup Language (XML) related items such as Namespaces, Document Type Declarations (DTDs), Schemas, and Resource Description Framework (RDF) Schemas. This document presents a technique to securely provision a networking device when it is booting in a factory-default state. Variations in the solution enable it to be used on both public and private networks. The provisioning steps are able to update the boot image, commit an initial configuration, and execute arbitrary scripts to address auxiliary needs. The updated device is subsequently able to establish secure connections with other systems. For instance, a device may establish NETCONF (RFC 6241) and/or RESTCONF (RFC 8040) connections with deployment-specific network management systems. This document describes an HTTP-based protocol that provides a programmatic interface for accessing data defined in YANG, using the datastore concepts defined in the Network Configuration Protocol (NETCONF). This document describes the Cryptographic Message Syntax (CMS). This syntax is used to digitally sign, digest, authenticate, or encrypt arbitrary message content. [STANDARDS-TRACK] The Network Configuration Protocol (NETCONF) defined in this document provides mechanisms to install, manipulate, and delete the configuration of network devices. It uses an Extensible Markup Language (XML)-based data encoding for the configuration data as well as the protocol messages. The NETCONF protocol operations are realized as remote procedure calls (RPCs). This document obsoletes RFC 4741. [STANDARDS-TRACK] This memo provides guidelines for authors and reviewers of specifications containing YANG modules. Recommendations and procedures are defined, which are intended to increase interoperability and usability of Network Configuration Protocol (NETCONF) and RESTCONF protocol implementations that utilize YANG modules. This document obsoletes RFC 6087. YANG is a data modeling language used to model configuration and state data manipulated by the Network Configuration Protocol (NETCONF), NETCONF remote procedure calls, and NETCONF notifications. [STANDARDS-TRACK]

RFC Editor, please remove this section. This section lists references in the YANG. , .