<?xml version="1.0" encoding="UTF-8"?>
<XML><RECORDS>
<RECORD>
	<REFERENCE_TYPE>3</REFERENCE_TYPE>
	<AUTHORS>
		<AUTHOR>Sheikh I. Ahamed</AUTHOR>
		<AUTHOR>Endadul Hoque</AUTHOR>
		<AUTHOR>Farzana Rahman</AUTHOR>
		<AUTHOR>Fahim Kawsar</AUTHOR>
		<AUTHOR>Tatsuo Nakajima</AUTHOR>
	</AUTHORS>
	<YEAR>2008</YEAR>
	<TITLE>YA-SRAP: Yet another serverless RFID authentication protocol</TITLE>
	<SECONDARY_TITLE>Intelligent Environments, 2008 IET 4th International Conference on</SECONDARY_TITLE>
	<PLACE_PUBLISHED>Seattle, USA</PLACE_PUBLISHED>
	<PAGES>1-8</PAGES>
	<DATE>July</DATE>
	<KEYWORDS>
		<KEYWORD>yet another serverless RFID authentication protocol</KEYWORD>
		<KEYWORD>security threat</KEYWORD>
		<KEYWORD>security assurance</KEYWORD>
		<KEYWORD>privacy protection</KEYWORD>
		<KEYWORD>cryptography</KEYWORD>
		<KEYWORD>telecommunication securityYA-SRAP</KEYWORD>
		<KEYWORD>radiofrequency identification</KEYWORD>
		<KEYWORD>message authentication</KEYWORD>
		<KEYWORD>data privacy</KEYWORD>
		<KEYWORD>cryptographic protocols</KEYWORD>
	</KEYWORDS>
	<ABSTRACT>Several security threats in RFID systems are obstacles to intermingle this technology into human lives. On the other hand ensuring flexible privacy mechanism has been a challenge due to extremely inadequate computational storage of typical RFID tags. So in order to relieve tags from responsibility, privacy protection and security assurance was guaranteed by central server. In this paper, we describe serverless, lightweight, forward secured and untraceable authentication protocol for RFID tags. This authentication protocol ensures security against almost all major attacks without the intervention of server. Furthermore it is very critical to guarantee untraceability and scalability simultaneously. Here we are proposing a scheme to make our protocols more scalable via ownership transfer. To the best of our knowledge this is incorporated in the serverless system for the first time.</ABSTRACT>
	<URL>http%3A%2F%2Fieeexplore.ieee.org%2Fxpls%2Fabs_all.jsp%3Farnumber%3D4629792</URL>
</RECORD>
</RECORDS></XML>