<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="12555" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://archives.christuniversity.in/items/show/12555?output=omeka-xml" accessDate="2026-04-08T23:41:10+00:00">
  <collection collectionId="5">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="64">
                <text>Articles</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="19">
    <name>Article</name>
    <description>Faculty Publications -Articles</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72747">
              <text>A reliable inter-domain routing framework for autonomous systems using hybrid Blockchain</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="49">
          <name>Subject</name>
          <description>The topic of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72748">
              <text>Authorized data; Blockchain; Decentralized network; Distributed ledger; Routing decisions; Tamper-proof</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72749">
              <text>Inter-domain networks face several routing challenges, such as security, scalability, and reliability concerns in existing BGP-based systems. These challenges are exacerbated by the increasing number of interconnected networks and the lack of a standardized approach for routing data between them. Hybrid Blockchain-based framework has proposed for inter-domain routing in autonomous systems in this research. The framework combines the use of traditional routing protocols with the distributed ledger technology of Blockchain. It leverages the salient features of both to create a more secure and efficient routing framework. The Blockchain component provides a decentralized and tamper-proof ledger for storing routing information, while the traditional routing protocols handle the actual exchange of data between autonomous systems. The framework is designed to enhance the security of inter-domain routing by incorporating the use of digital signatures and information sharing among participating autonomous systems. Each participating system maintains a copy of the distributed ledger and can verify the authenticity of routing information using digital signatures. It ensures that only legitimate and authorized data is transmitted between autonomous systems, mitigating the risk of malicious attacks or illegitimate routing. The proposed framework obtained 87.73 % Route calculation Speed, 90.41 % Route filtering, 93.77 % Fault tolerance, 94.10 % Load balancing, 95.54 % Hop count, 95.13 % bandwidth consumption, 93.94 % Security Management and 96.29 % Convergence time. The framework employs a consensus mechanism for updating and validating the routing information, ensuring consistency and accuracy in the routing decisions. It also reduces the reliance on a single central authority and distributes the decision-making process among participating systems.  2024 Elsevier Ltd</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72750">
              <text>Mahalingam M.S.; Kumar N.S.; Devi R.K.; Logeshwaran J.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="72751">
              <text>Computers and Electrical Engineering, Vol-123</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="72752">
              <text>Elsevier Ltd</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72753">
              <text>2025-01-01</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="72754">
              <text>&lt;a href="https://doi.org/10.1016/j.compeleceng.2024.110031" target="_blank" rel="noreferrer noopener"&gt;https://doi.org/10.1016/j.compeleceng.2024.110031&lt;/a&gt;
&lt;br /&gt;&lt;br /&gt;&lt;a href="https://www.scopus.com/inward/record.uri?eid=2-s2.0-85213291711&amp;amp;doi=10.1016%2Fj.compeleceng.2024.110031&amp;amp;partnerID=40&amp;amp;md5=c3757ab4273a3e50d8514f425ebc3483" target="_blank" rel="noreferrer noopener"&gt;https://www.scopus.com/inward/record.uri?eid=2-s2.0-85213291711&amp;amp;doi=10.1016%2fj.compeleceng.2024.110031&amp;amp;partnerID=40&amp;amp;md5=c3757ab4273a3e50d8514f425ebc3483&lt;/a&gt;</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="47">
          <name>Rights</name>
          <description>Information about rights held in and over the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72755">
              <text>Restricted Access</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="46">
          <name>Relation</name>
          <description>A related resource</description>
          <elementTextContainer>
            <elementText elementTextId="72756">
              <text>ISSN: 457906; CODEN: CPEEB</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="42">
          <name>Format</name>
          <description>The file format, physical medium, or dimensions of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72757">
              <text>Online</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72758">
              <text>English</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="51">
          <name>Type</name>
          <description>The nature or genre of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="72759">
              <text>Article</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="72760">
              <text>Mahalingam M.S., Department of Computer Science and Engineering, School of Computing, Kalasalingam Academy of Research and Education, Tamil Nadu, India; Kumar N.S., Department of Computer Science and Engineering, School of Computing, Kalasalingam Academy of Research and Education, Tamil Nadu, India; Devi R.K., School of Computer Science and Engineering, VIT - Chennai Campus, Tamil Nadu, Chennai, India; Logeshwaran J., Department of Computer Science, Christ University, Karnataka, Bengaluru, 560029, India</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
