| Internet-Draft | hardware divvying | December 2024 |
| William Gardner | Expires 4 June 2025 | [Page] |
a proposal for hardware divvying (specifically in the case of RAM)¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 4 June 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
Due to permission problems and transparency of data collection, there are a lot of well intentioned programs (especially on internet connected cellphones) that cannot not be made without being predatory. However, if specific blocks of RAM are specialized for particular tasks this isnt necessarily an issue. Taking into consideration contextual audio analysis for safety and socially beneficial tasks could be something left to a block of RAM that can only be access if a program actually specifies that it needs that block of RAM. This kind of memory divvying could be standardized for all sort of temporary storage for executables, especially in the modern era where there is a lot of RAM to go around.¶