<?xml version="1.0" encoding="UTF-8"?>
<article article-type="research-article" xml:lang="en" xmlns:xlink="http://www.w3.org/1999/xlink">
<front>
<journal-meta>
<journal-id journal-id-type="publisher">global-journal-of-computer-science-and-technology</journal-id>
<journal-title-group>
<journal-title>Global Journal of Computer Science and Technology</journal-title>
</journal-title-group>
<issn publication-format="print">0975-4350</issn>
<issn publication-format="electronic">0975-4172</issn>
<publisher><publisher-name>Global Journals Publishing Group Incorporated</publisher-name></publisher>
<self-uri xlink:href="https://globaljournals.org/journal-seo-export/jats/72949.xml" />
</journal-meta>
<article-meta>
<article-id pub-id-type="publisher-id">72949</article-id>
<title-group>
<article-title>Security Issues and Solutions in Multicast Environment through Tree based Scheme</article-title>
</title-group>
<contrib-group>
<contrib contrib-type="author"><name><surname>PRIYA</surname><given-names>DR. S.SANTHI</given-names></name><xref ref-type="aff" rid="aff1" />
</contrib>
<contrib contrib-type="author"><name><surname>B.V.S.S.R.S.SASTRY</surname><given-names></given-names></name></contrib>
</contrib-group>
<aff id="aff1">INDIA, Auroras Engineering College</aff>
<pub-date publication-format="electronic" date-type="pub" iso-8601-date="2011-03-13">
<day>13</day>
<month>03</month>
<year>2011</year>
</pub-date>
<volume>11</volume>
<issue>5</issue>
<fpage>35</fpage>
<lpage>44</lpage>
<abstract><p>Multicast is the delivery of a message or information to a group of destination computers simultaneously in a single transmission from the source creating copies automatically in other network elements, such as routers, only when the topology of the network requires it. Multicasting security is hard because of Open group membership, everyone gets same packets, Senders need not be members. We first present taxonomy of multicast scenarios on the Internet and point out relevant security concerns. Next we address two major security problems of multicast communication: source authentication, and key revocation. Maintaining authenticity in multicast protocols is a much more complex problem than for unicast, in particular known solutions are prohibitively inefficient in many cases. We present a solution that is reasonable for a range of scenarios. Our approach can be regarded as a midpoint between traditional Message Authentication Codes and digital signatures. We also present an improved solution to the key revocation problem.</p></abstract>
<kwd-group kwd-group-type="author-generated">
<kwd>Multicast</kwd>
<kwd>Security</kwd>
<kwd>Authentication</kwd>
<kwd>Signature.</kwd>
</kwd-group>
<self-uri content-type="pdf" xlink:href="https://globaljournals.org/GJCST_Volume11/5-Security-Issues-and-Solutions-in-Multicast-Environment.pdf" />
<self-uri content-type="html" xlink:href="https://globaljournals.org/scholarly-articles/security-issues-and-solutions-in-multicast-environment-through-tree-based-scheme/" />
</article-meta>
</front>
<body>
<sec>
<title>Full Text</title>
<p>Multicast is the delivery of a message or information to a group of destination computers simultaneously in a single transmission from the source creating copies automatically in other network elements, such as routers, only when the topology of the network requires it. Multicasting security is hard because of Open group membership, everyone gets same pack ets, Senders need not be members. We first present taxonomy of mu lticast scenarios on the Internet and point out relevant security concerns. Next we address two major security problems of multicast communication: source authentication, and key revocation. Maintaining authenticity in multicast protocols is a much more complex problem than for unicast, in particular known solutions are prohibitively inefficient in many cases. We present a solution that is reasonable for a range of scenarios. Our approach can be regarded as a midpoi nt between traditional Message Authentication Codes and digital signatures. We also present an improved solution to the key revocation problem.</p>
</sec>
</body>
</article>