bk99.de entertain the web since 1997

bk99.de
RFC · PKIStandard explained

RFC 8555: ACME: Managing certificates automatically

Summary

RFC 8555 standardises ACME for the automated issuance, validation and renewal of certificates. Automation made short certificate lifetimes manageable in practice. PKI reliability increasingly depends on secure renewal processes.

Ideas

  • Clients prove control over domain names through challenges.
  • Accounts sign protocol messages.
  • Orders bundle authorisations and certificate requests.

Remarks

  • RFC 8555 has the status “Proposed Standard”; current errata and successor documents should also be checked.

Recommendations

  • Automate renewal and test it before expiry.
  • Protect account keys and limit access to challenges.

References

Read the RFC at the RFC Editor

Search the Web Archive

RFC · 2026

RFC 9846: TLS 1.3: The consolidated current specification

RFC 9846 replaces RFC 8446 and consolidates TLS 1.3 with the corrections and updates published up to then. Security standards occasionally need a consolidated new edition instead of many scattered updates. Superseding the document changes the reference, not the goal of a smaller, secure protocol.

RFC · 2026

RFC 10008: HTTP QUERY: Safe, idempotent queries with content

RFC 10008 defines the HTTP method QUERY for complex, safe and idempotent queries with request content. New methods close gaps when established semantics do not fit cleanly. Explicit semantics are better than misused POST requests.

RFC · 2026

RFC 9958: Post-quantum cryptography for practitioners

RFC 9958 explains to engineers the properties, transition risks and deployment patterns of post-quantum cryptography. Cryptographic migration starts long before quantum attacks are practically available. Harvest-now-decrypt-later makes data that must stay confidential for a long time relevant today.