Define the new internet.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
Look up the words people use online, add the ones we missed, and help make the internet easier to understand.
5,641 definitions
Standards Track Interop Proof is an IETF Internet Standards term for standards track interop proof work that connects internet folklore to the standards process that real implementers, ISPs, browsers, cloud providers, and enterprises use to keep networks interoperable. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: IETF DNS technology; IETF Areas; RFC 1918 private address space.
Standards Track Map is an IETF Internet Standards term for standards track map work that connects internet folklore to the standards process that real implementers, ISPs, browsers, cloud providers, and enterprises use to keep networks interoperable. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: IETF DNS technology; IETF Areas; RFC 1918 private address space.
Standards Track Meeting Proof is an IETF Internet Standards term for standards track meeting proof work that connects internet folklore to the standards process that real implementers, ISPs, browsers, cloud providers, and enterprises use to keep networks interoperable. It helps people and agents name the signal, source, and safe next step without pretending an automation, campaign, DNS record, RFC, or network path did more than the evidence shows. Source context: IETF DNS technology; IETF Areas; RFC 1918 private address space.
Storage Autoscaling Policy is a compute control loop that changes capacity based on demand signals for persistent data and object access. It uses metrics, thresholds, and cooldowns so teams can match resources to load while keeping evidence, reliability, and public-safe operational boundaries clear.
Storage Backpressure Control is a compute stability pattern that slows incoming work when downstream capacity is limited for persistent data and object access. It uses queues, retry budgets, and admission control so teams can avoid overload cascades while keeping evidence, reliability, and public-safe operational boundaries clear.
Storage Cache Invalidation is a compute freshness process that removes or refreshes stale cached data for persistent data and object access. It uses keys, tags, timestamps, and purge events so teams can serve current results while keeping evidence, reliability, and public-safe operational boundaries clear.
Storage Capacity Forecast is a compute planning model that estimates future resource needs for persistent data and object access. It uses traffic history, growth assumptions, and utilization trends so teams can avoid surprise shortages while keeping evidence, reliability, and public-safe operational boundaries clear.
Storage Checkpoint Restore is a compute recovery workflow that resumes work from a saved state for persistent data and object access. It uses snapshots, state files, and integrity checks so teams can recover long-running work while keeping evidence, reliability, and public-safe operational boundaries clear.
Storage Cold Start Budget is a compute latency target that limits startup delay for newly scheduled execution for persistent data and object access. It uses prewarming, smaller packages, and runtime tuning so teams can keep first requests responsive while keeping evidence, reliability, and public-safe operational boundaries clear.
Storage Image Hardening is a compute security practice that reduces risk inside packaged runtime images for persistent data and object access. It uses minimal bases, patching, and vulnerability checks so teams can ship safer workloads while keeping evidence, reliability, and public-safe operational boundaries clear.