60 likes | 100 Views
This document provides updated requirements for Online Certificate Status Protocol (OCSP) to refreshen certificate validation systems. It eliminates the burden of Certificate Revocation List (CRL) distribution and update, focusing on lightweight request/response exchanges. Changes include finishing, added missing sections, reformat, and corrections based on feedback. It discusses updates in architecture, periodic CRL downloads, OCSP protocol enhancements, and trusted responders for improved security. Addressing outstanding issues like signed requests, suspension vs. revocation differentiation, and conveying additional information via OCSP response extensions, this aims to move towards finalizing WG proposals by GGF14.
E N D
OCSP Requirements GGF13
Refreshener • OCSP = Online Certificate Status Protocol (RFC2560) • Removes(?) burden of CRL distribution and update • Clients still have to do path validation! • Lightweight request/response (HTTP)
Changes since last time • Document “finish” applied • Missing sections added • Complete reformat • Corrections based on (marginal) feedback • Last week • Additional comments from Spain
Updated architecture Periodic CRL download OCSP protocol CA Push, Delta CRLs site/organization boundary CA CA OCSPcache CRLcache OCSPclient AuthorizedResponder TrustedResponder CA OCSP client CA CA CA CA PMA TrustedResponder
Outstanding issues • Signed requests • Stronger differentiation on suspension vs revocation • Use of OCSP response extensions to convey additional (validation) information • More wording on Delta CRLs • Notion of a caution period (RFC3125)
Moving forward • Address the Spanish contributions • Move towards WG last call • Have document in public comment before GGF14