A profile for Resource Tagged Attestations (RTAs)
draft-ietf-sidrops-rpki-rta-00
Network Working Group G. Michaelson
Internet-Draft G. Huston
Intended status: Experimental T. Harrison
Expires: July 21, 2021 APNIC
T. Bruijnzeels
M. Hoffmann
nlnetlabs
January 17, 2021
A profile for Resource Tagged Attestations (RTAs)
draft-ietf-sidrops-rpki-rta-00
Abstract
This document defines a Cryptographic Message Syntax (CMS) profile
for a general purpose Resource Tagged Attestation (RTA), for use with
the Resource Public Key Infrastructure (RPKI). The objective is to
allow an attestation, in the form of an arbitrary digital object, to
be signed "with resources", and for validation to provide an outcome
of "valid with resources". The profile is intended to provide for
the signing of an attestation with an arbitrary set of resources.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on July 21, 2021.
Copyright Notice
Copyright (c) 2021 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
Michaelson, et al. Expires July 21, 2021 [Page 1]
Internet-Draft RTA January 2021
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used In This Document . . . . . . . . . . . . . . 3
3. RTA Profile . . . . . . . . . . . . . . . . . . . . . . . . . 3
4. The RTA ContentType . . . . . . . . . . . . . . . . . . . . . 4
5. The RTA eContent . . . . . . . . . . . . . . . . . . . . . . 4
5.1. version . . . . . . . . . . . . . . . . . . . . . . . . . 5
5.2. subjectKeyIdentifiers . . . . . . . . . . . . . . . . . . 5
5.3. resources . . . . . . . . . . . . . . . . . . . . . . . . 6
5.4. digestAlgorithm . . . . . . . . . . . . . . . . . . . . . 6
5.5. messageDigest . . . . . . . . . . . . . . . . . . . . . . 6
5.6. attestations . . . . . . . . . . . . . . . . . . . . . . 6
6. RTA Validation . . . . . . . . . . . . . . . . . . . . . . . 6
7. Need for Canonicalization . . . . . . . . . . . . . . . . . . 7
7.1. ASCII, UTF-8, and HTML File Canonicalization . . . . . . 7
7.2. XML File Canonicalization . . . . . . . . . . . . . . . . 8
7.3. No Canonicalization of Other File Formats . . . . . . . . 9
8. Standalone Use . . . . . . . . . . . . . . . . . . . . . . . 9
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
10. Security Considerations . . . . . . . . . . . . . . . . . . . 9
11. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 10
12. Revision history . . . . . . . . . . . . . . . . . . . . . . 11
13. Normative References . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction
This document defines a Cryptographic Message Syntax (CMS) [RFC5652]
profile for a general purpose Resource Tagged Attestation (RTA), for
use with the Resource Public Key Infrastructure (RPKI) [RFC6480]. An
RTA allows an arbitrary digital object to be signed "with resources,"
and for validation of the digital signature to provide an outcome of
"valid with resources." The profile is intended to provide for the
signing of a arbitrary attestation with a set of resources by the
duly delegated resource holder(s).
Show full document text