<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE rfc [
  <!ENTITY nbsp "&#160;">
  <!ENTITY zwsp "&#8203;">
  <!ENTITY nbhy "&#8209;">
  <!ENTITY wj "&#8288;">
]>
<rfc xmlns:xi="http://www.w3.org/2001/XInclude"
     category="info"
     docName="draft-banffy-httpbis-not-a-freezer-00"
     ipr="trust200902"
     submissionType="independent"
     version="3">
  <front>
    <title abbrev="I'm Not a Freezer">The Hypertext Transfer Protocol Status Code 483 (I'm Not a Freezer)</title>
    <author fullname="Ricardo Bánffy" asciiFullname="Ricardo Banffy" initials="R." asciiInitials="R." surname="Bánffy" asciiSurname="Banffy">
      <address>
        <email>rbanffy@gmail.com</email>
      </address>
    </author>
    <date year="2026" month="November" day="15"/>
    <area>General</area>
    <workgroup>Independent Submission</workgroup>
    <keyword>HTTP</keyword>
    <keyword>status code</keyword>
    <keyword>freezer</keyword>
    <keyword>refrigeration</keyword>
    <keyword>cold storage</keyword>
    <abstract>
      <t>This document defines the Hypertext Transfer Protocol status code 483 (I'm Not a Freezer). A server returns this status code when it understands a request that requires freezing or refrigeration capabilities but is not capable of providing those capabilities.</t>
      <t>This document also clarifies the distinction between a freezer, a refrigerator, a server operating at a low temperature, a frozen software process, and an online service advertising "cold storage".</t>
    </abstract>
  </front>
  <middle>
    <section anchor="introduction">
      <name>Introduction</name>
      <t>HTTP status codes communicate the result of attempting to understand and satisfy a request. Existing status codes cover malformed requests, missing resources, unsupported media types, and servers that are temporarily unavailable.</t>
      <t>No registered status code clearly indicates that a server understood a request but cannot satisfy it because the request requires the server to be a freezer.</t>
      <t>This ambiguity can cause clients to repeat requests, select inappropriate fallback services, place perishable goods near computing equipment, or otherwise confuse information technology infrastructure with domestic or industrial refrigeration equipment.</t>
      <t>This document addresses that ambiguity by defining the 483 (I'm Not a Freezer) status code.</t>
    </section>
    <section anchor="conventions">
      <name>Conventions and Definitions</name>
      <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when, and only when, they appear in all capitals, as shown here.</t>
      <dl newline="true">
        <dt>Freezer</dt><dd>An apparatus capable of maintaining its contents at a temperature below the freezing point of water for a sustained period. Software containers, frozen processes, cold-storage services, and servers located in cold climates are not necessarily freezers.</dd>
        <dt>Refrigerator</dt><dd>An apparatus that maintains contents below ambient temperature but does not necessarily maintain them below the freezing point of water.</dd>
        <dt>Cold storage</dt><dd>A term that might refer to refrigerated physical storage, infrequently accessed data storage, an offline cryptographic wallet, or other facilities that are insufficiently warm. Use of the term does not establish freezer capability.</dd>
        <dt>Freezer-capable server</dt><dd>An HTTP server associated with equipment that can perform the freezing operation requested by the client. Merely operating inside a freezer does not necessarily make an HTTP server freezer-capable.</dd>
      </dl>
    </section>
    <section anchor="status-code">
      <name>The 483 (I'm Not a Freezer) Status Code</name>
      <t>This document extends the HTTP status-code semantics defined in <xref target="HTTP"/> with the 483 (I'm Not a Freezer) status code. The status code indicates that the server understood the request but cannot satisfy it because the requested operation requires freezing or refrigeration capabilities that the server does not possess.</t>
      <t>A server MAY return 483 when all of the following conditions apply:</t>
      <ul><li>The request can be parsed and understood.</li><li>Satisfying the request would require the server to freeze, refrigerate, chill, or preserve a physical item by reducing its temperature.</li><li>The server is not capable of performing the requested temperature-control operation.</li></ul>
      <t>A server MUST NOT return 483 merely because:</t>
      <ul><li>its operating temperature is below ambient temperature;</li><li>it uses liquid, air, immersion, or phase-change cooling;</li><li>it provides a service described as "cold storage";</li><li>one or more software processes have been frozen;</li><li>its physical location is cold;</li><li>its hostname contains words such as "freezer", "ice", "arctic", "frost", or "cold"; or</li><li>it is unresponsive in a way informally described as "frozen".</li></ul>
      <t>A 483 response SHOULD contain a representation explaining that the selected server lacks the required refrigeration capability. Where appropriate, the representation MAY identify a freezer-capable alternative.</t>
      <sourcecode type="http"><![CDATA[HTTP/1.1 483 I'm Not a Freezer
Content-Type: text/plain

This server is not a freezer and cannot satisfy the requested operation.
]]></sourcecode>
    </section>
    <section anchor="client-behavior">
      <name>Client Behavior</name>
      <t>A client receiving a 483 response SHOULD NOT automatically repeat the same request to the same server unless it has reason to believe that the server has subsequently acquired suitable refrigeration capabilities.</t>
      <t>A client MAY attempt the request against another origin if that origin is known to be freezer-capable.</t>
      <t>A client MUST NOT interpret a 483 response as evidence that the server is a refrigerator. The response communicates a lack of freezer capability and makes no claim concerning lesser, adjacent, or unrelated cooling capabilities.</t>
      <t>Clients SHOULD avoid automatically redirecting physical goods based solely on URI authority components, DNS names, electronic mail addresses, service banners, or unverified appliance metadata.</t>
    </section>
    <section anchor="applicability">
      <name>Applicability</name>
      <t>Status code 483 is applicable when a request crosses a boundary between digital instructions and physical temperature-control operations.</t>
      <t>Examples include:</t>
      <ul><li>an HTTP-controlled kitchen appliance receiving a request to freeze food;</li><li>an industrial control gateway receiving a request to preserve a sample below a specified temperature;</li><li>a logistics service receiving an instruction that requires a cold-chain facility that it does not operate; and</li><li>a general-purpose HTTP server receiving a request intended for a refrigeration appliance.</li></ul>
      <t>Status code 483 is not intended to report CPU thermal throttling, data-center cooling failures, insufficient heat dissipation, unresponsive software, immutable data, object freezing in programming languages, or process suspension.</t>
    </section>
    <section anchor="example-email">
      <name>Example: Electronic Mail Concerning Frozen Goods</name>
      <t>Consider an HTTP service that accepts electronic mail for delivery to suitable appliances. A client might inadvertently attempt to deliver a message intended for a freezer:</t>
      <sourcecode type="http"><![CDATA[POST /mail HTTP/1.1
Host: mail.example
Content-Type: message/rfc822

From: alice@example.com
To: freezer@example.com
Date: Tue, 3 Nov 2026 10:00:00 +0000
Message-ID: <peas-483@example.com>
Subject: Please freeze these peas

Dear Freezer,

Please maintain the attached peas at approximately -18 degrees
Celsius until further notice.

Regards,
Alice
]]></sourcecode>
      <t>If the selected service is not a freezer and cannot cause the requested freezing operation to occur, it MAY reject the request with status code 483:</t>
      <sourcecode type="http"><![CDATA[HTTP/1.1 483 I'm Not a Freezer
Content-Type: text/plain

This server is not a freezer and cannot satisfy the requested operation.
]]></sourcecode>
      <t>An implementation MUST NOT infer refrigeration capability solely from an electronic mail address containing the strings "freezer", "refrigerator", "cold", "ice", or similar terminology.</t>
      <t>The recipient address identifies the intended appliance but does not prove that the HTTP service handling the message controls that appliance.</t>
      <t>The domain names and electronic mail addresses in this example are reserved for documentation as described by <xref target="RFC2606"/> and do not identify operational refrigeration infrastructure.</t>
    </section>
    <section anchor="relationship-418">
      <name>Relationship to Status Code 418</name>
      <t>Status code 418 was introduced by the Hyper Text Coffee Pot Control Protocol <xref target="RFC2324"/> and is associated with an apparatus that is a teapot and therefore cannot brew coffee. Status code 483 represents a distinct condition.</t>
      <t>A teapot might be neither a freezer nor a general-purpose server. Similarly, a freezer might contain an HTTP server without becoming a teapot.</t>
      <t>An implementation choosing between 418 and 483 SHOULD consider the immediate reason that the request cannot be satisfied:</t>
      <ul><li>If the request cannot be satisfied because the responding apparatus is a teapot, 418 might be appropriate.</li><li>If the request cannot be satisfied because the responding server is not a freezer, 483 might be appropriate.</li><li>If the apparatus is both a teapot and not a freezer, the implementation SHOULD report the condition most directly relevant to the requested operation.</li></ul>
      <t>This document does not define response prioritization for combination refrigerator-freezer-teapot appliances.</t>
    </section>
    <section anchor="refrigerator-distinction">
      <name>Distinguishing Refrigerators from Freezers</name>
      <t>A refrigerator is not necessarily a freezer. An implementation MUST NOT advertise freezer capability merely because it can maintain a temperature lower than the surrounding environment.</t>
      <t>If a request specifies a target temperature, the server SHOULD evaluate its actual supported temperature range. A server that can maintain 4 degrees Celsius but cannot maintain -18 degrees Celsius can return 483 when asked to preserve frozen food at -18 degrees Celsius.</t>
      <t>This document does not allocate a separate status code meaning "I'm Only a Refrigerator". Such allocation is left for future work, preferably after an appropriate cooling-off period.</t>
    </section>
    <section anchor="intermediaries">
      <name>Intermediaries and Cold-Chain Proxies</name>
      <t>An intermediary MUST NOT replace a 483 response with a success response unless it has arranged for the requested operation to be performed by a freezer-capable service.</t>
      <t>An intermediary that forwards a request to a freezer-capable service SHOULD preserve sufficient request information to maintain traceability through the cold chain.</t>
      <t>A proxy MUST NOT claim that a request has been frozen merely because it has been buffered, queued, archived, or stored on media described as cold storage.</t>
      <t>Intermediaries SHOULD NOT select a refrigeration service based only on the service name. Capability claims ought to be authenticated before perishable or temperature-sensitive goods are redirected.</t>
    </section>
    <section anchor="caching">
      <name>Caching Considerations</name>
      <t>A 483 response is not heuristically cacheable.</t>
      <t>A 483 response can be cached when explicit freshness information permits caching, subject to <xref target="HTTP-CACHING"/>.</t>
      <t>Implementations ought to use short freshness lifetimes when refrigeration capabilities can change. A server might acquire freezer capability through appliance discovery, configuration, repair, attachment of suitable hardware, or relocation.</t>
      <t>A cache MUST include relevant request-selection information in its cache key when freezer capability depends on the requested product, target temperature, duration, physical location, or other request characteristics.</t>
    </section>
    <section anchor="security">
      <name>Security Considerations</name>
      <t>A 483 response can disclose information about the physical capabilities of a server, appliance, building, warehouse, or logistics network. Such information might assist an attacker in identifying facilities that lack refrigeration capability.</t>
      <t>Servers SHOULD avoid disclosing unnecessary details about appliance models, internal temperatures, stored contents, physical locations, maintenance schedules, or cold-chain topology.</t>
      <t>A malicious service might falsely claim freezer capability in order to receive physical goods, operational instructions, or sensitive inventory information. Clients SHOULD authenticate services before relying on claims of refrigeration capability.</t>
      <t>Implementations MUST NOT treat the presence or absence of a 483 response as proof that a physical item has been frozen, refrigerated, preserved, spoiled, thawed, or consumed.</t>
      <t>Request bodies associated with freezing operations might reveal dietary preferences, medical requirements, biological sample information, commercial inventory, or other sensitive data. Implementations SHOULD apply suitable confidentiality and access-control protections.</t>
      <t>Operators are advised not to troubleshoot servers by placing them inside domestic freezers. Condensation, restricted airflow, thermal shock, and the objections of other freezer occupants can produce undesirable results.</t>
    </section>
    <section anchor="privacy">
      <name>Privacy Considerations</name>
      <t>Requests involving refrigeration can expose information about food, medicine, scientific samples, commercial shipments, or household activity. Servers SHOULD minimize the information returned in a 483 response and SHOULD avoid echoing sensitive request content.</t>
      <t>Logs containing 483 responses SHOULD be protected according to the sensitivity of associated request metadata and content.</t>
    </section>
    <section anchor="iana">
      <name>IANA Considerations</name>
      <t>This document requests that IANA register the following entry in the "Hypertext Transfer Protocol (HTTP) Status Code Registry":</t>
      <table anchor="iana-registration"><name>Requested HTTP Status Code Registration</name><thead><tr><th>Value</th><th>Description</th><th>Reference</th></tr></thead><tbody><tr><td>483</td><td>I'm Not a Freezer</td><td>This document</td></tr></tbody></table>
      <t>If the registration request is not approved, this section can itself be considered safely stored for future use, although not necessarily below freezing.</t>
    </section>
    <section anchor="implementation">
      <name>Implementation Considerations</name>
      <t>Implementers are encouraged to use the exact reason phrase "I'm Not a Freezer" when a reason phrase is supported. Clients MUST NOT depend on the reason phrase because HTTP semantics are identified by the numeric status code.</t>
      <t>Protocol versions that do not transmit a reason phrase can use status code 483 without modification.</t>
      <t>Implementations MAY include a machine-readable problem detail describing the unsupported refrigeration operation, subject to <xref target="RFC9457"/>.</t>
      <sourcecode type="http"><![CDATA[HTTP/1.1 483 I'm Not a Freezer
Content-Type: application/problem+json
Cache-Control: no-store

{
  "type": "https://example.com/problems/not-a-freezer",
  "title": "I'm Not a Freezer",
  "status": 483,
  "detail": "The requested temperature is outside supported capabilities."
}
]]></sourcecode>
    </section>
    <section anchor="acknowledgments">
      <name>Acknowledgments</name>
      <t>The author thanks the designers of HTTP, refrigeration equipment, electronic mail, and combination appliances for creating the conditions that made this clarification necessary.</t>
      <t>The peas used in the example were not harmed during preparation of this document, although their final temperature could not be independently verified.</t>
    </section>
  </middle>
  <back>
    <references>
      <name>Normative References</name>
      <reference anchor="RFC2119" target="https://www.rfc-editor.org/info/rfc2119"><front><title>Key words for use in RFCs to Indicate Requirement Levels</title><author initials="S." surname="Bradner" fullname="S. Bradner"/><date month="March" year="1997"/></front><seriesInfo name="BCP" value="14"/><seriesInfo name="RFC" value="2119"/><seriesInfo name="DOI" value="10.17487/RFC2119"/></reference>
      <reference anchor="RFC8174" target="https://www.rfc-editor.org/info/rfc8174"><front><title>Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words</title><author initials="B." surname="Leiba" fullname="B. Leiba"/><date month="May" year="2017"/></front><seriesInfo name="BCP" value="14"/><seriesInfo name="RFC" value="8174"/><seriesInfo name="DOI" value="10.17487/RFC8174"/></reference>
      <reference anchor="HTTP" target="https://www.rfc-editor.org/info/rfc9110"><front><title>HTTP Semantics</title><author initials="R." surname="Fielding" fullname="R. Fielding"/><author initials="M." surname="Nottingham" fullname="M. Nottingham"/><author initials="J." surname="Reschke" fullname="J. Reschke"/><date month="June" year="2022"/></front><seriesInfo name="STD" value="97"/><seriesInfo name="RFC" value="9110"/><seriesInfo name="DOI" value="10.17487/RFC9110"/></reference>
      <reference anchor="HTTP-CACHING" target="https://www.rfc-editor.org/info/rfc9111"><front><title>HTTP Caching</title><author initials="R." surname="Fielding" fullname="R. Fielding"/><author initials="M." surname="Nottingham" fullname="M. Nottingham"/><author initials="J." surname="Reschke" fullname="J. Reschke"/><date month="June" year="2022"/></front><seriesInfo name="STD" value="98"/><seriesInfo name="RFC" value="9111"/><seriesInfo name="DOI" value="10.17487/RFC9111"/></reference>
      <reference anchor="RFC9457" target="https://www.rfc-editor.org/info/rfc9457"><front><title>Problem Details for HTTP APIs</title><author initials="M." surname="Nottingham" fullname="M. Nottingham"/><author initials="E." surname="Wilde" fullname="E. Wilde"/><author initials="S." surname="Dalal" fullname="S. Dalal"/><date month="July" year="2023"/></front><seriesInfo name="RFC" value="9457"/><seriesInfo name="DOI" value="10.17487/RFC9457"/></reference>
    </references>
    <references>
      <name>Informative References</name>
      <reference anchor="RFC2324" target="https://www.rfc-editor.org/info/rfc2324"><front><title>Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)</title><author initials="L." surname="Masinter" fullname="L. Masinter"/><date month="April" day="1" year="1998"/></front><seriesInfo name="RFC" value="2324"/><seriesInfo name="DOI" value="10.17487/RFC2324"/></reference>
      <reference anchor="RFC2606" target="https://www.rfc-editor.org/info/rfc2606"><front><title>Reserved Top Level DNS Names</title><author initials="D." surname="Eastlake" fullname="Donald E. Eastlake 3rd"/><author initials="A." surname="Panitz" fullname="Aliza R. Panitz"/><date month="June" year="1999"/></front><seriesInfo name="BCP" value="32"/><seriesInfo name="RFC" value="2606"/><seriesInfo name="DOI" value="10.17487/RFC2606"/></reference>
    </references>
  </back>
</rfc>
