<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rfc>
<rfc category="info" docName="draft-vargas-eirp-00" ipr="trust200902" submissionType="IETF" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude">
  <front>
    <title abbrev="EIRP Architecture">Encrypted Identity Routing Protocol (EIRP): A Blockchain-Orchestrated Identity-Based Routing Architecture</title>
    <author fullname="Federico Jose Vargas Cabezas" initials="F. J." surname="Vargas Cabezas">
      <organization>Accenture</organization>
      <address>
        <email>vargas.frederico.04031993@gmail.com</email>
      </address>
    </author>
    <date year="2026"/>
    <abstract>
      <t>This document proposes the Encrypted Identity Routing Protocol (EIRP), a conceptual redesign of Internet routing where public IP addresses are replaced by encrypted identities authenticated through blockchain consensus.</t>
    </abstract>
  </front>

  <middle>
    <section title="Introduction">
      <t>The Internet's foundational addressing system relies on globally visible IP addresses. EIRP introduces a paradigm shift by replacing routable IP addresses with encrypted identities authenticated through blockchain authorization.</t>
    </section>

    <section title="EIRP Architecture">
      <t>EIRP consists of four conceptual components: the Blockchain Identity Ledger (BIL), Encrypted Routing Tokens (ERT), Secure Routing Overlay (SRO), and Access-Controlled Address Resolution (ACAR).</t>
    </section>

    <section title="Security Considerations">
      <t>EIRP prevents scanning, spoofing, and unsolicited traffic by ensuring that only authorized peers may resolve routing metadata. Further analysis is required regarding blockchain consensus latency and potential side-channel attacks on identity resolution.</t>
    </section>
    
    <section title="IANA Considerations">
      <t>This document has no IANA actions.</t>
    </section>
  </middle>

  <back>
    <references title="Informative References">
      <reference anchor="IETF-Process" target="https://www.ietf.org/process/new-work/">
        <front>
          <title>IETF New Work Process</title>
          <author><organization>IETF</organization></author>
          <date year="2026"/>
        </front>
      </reference>
    </references>
  </back>
</rfc>