Update to Digital Signatures on Internet-Draft Documents
RFC 8358, “Update to Digital Signatures on Internet-Draft Documents”, is an Informational document published in March 2018 by R. Housley. It updates RFC 5485. The canonical text is published by the RFC Editor.
Abstract
RFC 5485 specifies the conventions for digital signatures on Internet-Drafts. The Cryptographic Message Syntax (CMS) is used to create a detached signature, which is stored in a separate companion file so that no existing utilities are impacted by the addition of the digital signature.
The RFC Editor recently published the first RFC that includes non- ASCII characters in a text file. The conventions specified in RFC 7997 were followed. We assume that non-ASCII characters will soon start appearing in Internet-Drafts as well. This document updates the handling of digital signatures on Internet-Drafts that contain non-ASCII characters in a text file.
This document updates RFC 5485.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 8358 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 8357 Generalized UDP Source Port for DHCP Relay
- RFC 8359 Network-Assigned Upstream Label
- RFC 8356 Experimental Codepoint Allocation for the Path Computation Element Communication Protocol
- RFC 8360 Resource Public Key Infrastructure Validation Reconsidered
- RFC 8355 Resiliency Use Cases in Source Packet Routing in Networking Networks
- RFC 8361 Transparent Interconnection of Lots of Links : Centralized Replication for Active-Active Broadcast, Unknown Unicast, and Multicast Traffic
- RFC 8354 Use Cases for IPv6 Source Packet Routing in Networking
- RFC 8362 OSPFv3 Link State Advertisement Extensibility