<?xml version="1.0" encoding="utf-8"?>
<!-- 
     draft-rfcxml-general-template-bare-00
  
     This templates includes the bare minimum needed for the template to successfully validate 
     against the RFCXML schema.  While it validates, it is not a valid Internet-Draft. This 
     template is best used with an RNC schema-aware editor to assist with inserting valid elements 
     and attributes. 
     
     Documentation is at https://authors.ietf.org/en/templates-and-schemas
-->
<?xml-model href="rfc7991bis.rnc"?>  <!-- Required for schema validation and schema-aware editing -->

<!DOCTYPE rfc [
  <!ENTITY nbsp    "&#160;">
  <!ENTITY zwsp   "&#8203;">
  <!ENTITY nbhy   "&#8209;">
  <!ENTITY wj     "&#8288;">
]>
<!-- If further character entities are required then they should be added to the DOCTYPE above.
     Use of an external entity file is not recommended. -->

<rfc
  xmlns:xi="http://www.w3.org/2001/XInclude"
  category="info"
  docName="draft-rfcxml-general-template-standard-00"
  ipr="trust200902"
  obsoletes=""
  updates=""
  submissionType="IETF"
  xml:lang="en"
  version="3">
  <front>
    <title>hardware divvying</title>
    
    <author fullname="William 'northbot' Gardner" initials="WJG" role="editor" surname="William Gardner">
</author>
    <date year="2024"/>
  

    <abstract>
      <t>a proposal for hardware divvying (specifically in the case of RAM) </t>
    </abstract>
  </front>
  
  <middle>
    <section>
      <name>Hardware Divvying</name>
      <t>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.</t>
    </section>
  </middle>

  <back>
 </back>
</rfc>
