<?xml version="1.0" encoding="US-ASCII"?>
<!DOCTYPE rfc SYSTEM "rfc2629.dtd" [
<!ENTITY RFC2119 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2119.xml">
<!ENTITY RFC2026 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.2026.xml">
<!ENTITY RFC3802 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3802.xml">
<!ENTITY RFC1377 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.1377.xml">
]>
<?xml-stylesheet type="text/xsl" href="rfc2629.xslt" ?> <!-- used by XSLT processors -->
<!-- OPTIONS, known as processing instructions (PIs) go here. -->
<!-- For a complete list and description of PIs,
     please see http://xml.resource.org/authoring/README.html. -->
<!-- Below are generally applicable PIs that most I-Ds might want to use. -->
<?rfc strict="yes" ?> <!-- give errors regarding ID-nits and DTD validation -->
<!-- control the table of contents (ToC): -->
<?rfc toc="yes"?> <!-- generate a ToC -->
<?rfc tocdepth="2"?> <!-- the number of levels of subsections in ToC. default: 3 -->
<!-- control references: -->
<?rfc symrefs="yes"?> <!-- use symbolic references tags, i.e, [RFC2119] instead of [1] -->
<?rfc sortrefs="yes" ?> <!-- sort the reference entries alphabetically -->
<!-- control vertical white space: 
     (using these PIs as follows is recommended by the RFC Editor) -->
<?rfc compact="yes" ?> <!-- do not start each main section on a new page -->
<?rfc subcompact="no" ?> <!-- keep one blank line between list items -->
<!-- end of popular PIs -->
<rfc  category="exp" docName="draft-swl-103kprotocol-00" ipr="trust200902" updates="none" obsoletes="none">
  <front>
    <title abbrev="103K v1.0">1.0</title>
    <author fullname="Joseph Ocen" initials="ocen" surname="Ocen" role="editor">
      <organization>Strategic Wealth Limited</organization>
      <address>
        <postal>
      <street>970 Heritage Road</street>
      <city>kampala</city>
      <region>Central Region</region>
      <code>3256</code>
      <country>Uganda</country>
        </postal>
      <phone>+256785900775</phone>
<!-- <facsimile/> -->
      <email>info@expansionprotocols.com</email>
      <uri>www.expansionprotocols.com</uri>
      </address>
    </author>
    <author fullname="katerega micheal" initials="katerega" surname="katerega" role="editor">
      <organization>Strategic Wealth Limited</organization>
      <address>
        <postal>
      <street>mukono kabembe</street>
      <city>kampala</city>
      <region>central Region</region>
      <code>70751</code>
      <country>Uganda</country>
        </postal>
      <phone>+256756550013</phone>
<!-- <facsimile/> -->
      <email>8218kelmo@gmail.com</email>
<!-- <uri/> -->
      </address>
    </author>
    <date year="2022" />
<!-- <area/> -->
<!-- <workgroup/> -->
      <keyword>bytes</keyword>
      <keyword>packets</keyword>
      <keyword>datalink layer bits</keyword>
      <keyword>physical layer</keyword>
    <abstract>
      <t>
The Internet Core needs to be expandable to allow it to be usable on low-end devices with poor connectivity to be able to access internet resources in a seamless way on the application layer. this concept suggests that one way of how that can happen is through the stacking and unstacking of bits on the physical and datalink layers. Bycntainerising the input bytes into a bundle of 103bits and unstaking them on the other end of the communication layer using a different way f arrangement and encoding that can be interpreted by another protocol on the network layer. this can run parallel to the existing internet protocols and frameworks on the physical ,datalink and network layers      </t>
    </abstract>
  </front>
  <middle>
    <section title="Introduction">
      <t>
        The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
        "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
        this document are to be interpreted as described in
        <xref target="RFC2119"/>.
      </t>
      <t>
        This document is being discussed on the xyz@example.org mailing list.
      </t>
      <t>
        Add some text here. You will need to use these references somewhere within the text:
        <xref target="RFC2026"/>
        <xref target="RFC3802"/>
        <xref target="RFC1377"/>
      </t>
    </section>
    <section anchor="Acknowledgements" title="Acknowledgements">
    </section>
    <section anchor="IANA" title="IANA Considerations">
    </section>
    <section anchor="Security" title="Security Considerations">
    </section>
  </middle>
  <back>
    <references title="Normative References">
      &RFC2119;
      &RFC2026;
      &RFC3802;
      &RFC1377;
    </references>
    <references title="Informative References">
     
    </references>
  </back>
</rfc>