Dear Joe and all others, Thank you for correcting me saying, "It is not appropriate to use this forum for such allegations."
I wrote, may be I am violating TCCC posting norms. I understand that you and some other have got the positions to correct us many times and direct us what to do when. Also, I understand that I have to use this forum for posting and keeping the professional relationship. However, I suggest not employing a double-standard when a common platform is used. The correction should start from the top and we would follow. The following email was posted (recorded here) by James on Nov 19, 2011 at 10:17 AM. If the policies are enacted later, I hope this email could make all of us aware of this and thank you for warning me. If you think the following email was necessary for the overall community for its benefit, then you should also consider changing some policies of posting so that such awareness can be gained by all. Creating a separate forum would simply make things complex and one or two extra emails of such kinds won't be detrimental. You have a good structure where many renowned and honorable people are connected, but make please no difference in posting when the truth is presented. Thank you. --- EMAIL 1 ======= [Tccc] Plethora of open access journals and an amazingly brazen example of plagiarism in one of them James P.G. Sterbenz <[email protected]> Sat, Nov 19, 2011 at 10:17 AM To: TCCC TCCC <[email protected]> Cc: "James P.G. Sterbenz" <[email protected]> Apologies in advance for the length of this, but I thought it important post full details. As we keep seeing CFPs from more and more open access journals led by people we've never heard of, I've been tempted to bring the subject up here. I'm very much in favour of open access, and along the lines of the recent discussions I think that there are three ways to do this: 1. Pressure traditional societies like the IEEE and ACM and for-profit publishers like Springer and Elsevier to further open up. My university just signed the Berlin Declaration on Open Access. 2. Convince our funding agencies to require this along the lines of the NIH. Along these lines there is a Request for Information: Public Access to Peer-Reviewed Scholarly Publications Resulting From Federally Funded Research http://www.federalregister.gov/articles/2011/11/04/2011-28623/request-for-information-public-access-to-peer-reviewed-scholarly-publications-resulting-from 3. We do it ourselves and move as editorial boards to create new *legitimate* open access journals. Some academic communities are doing this. (For the record while I support the sprit of the petition that has been discussed, I do not support the means of not volunteering to review in venues to which you submit.) Which gets to the trigger for this email. One of my PhD students discovered that our paper: "Performance Analysis of the AeroTP Transport Protocol for Highly-Dynamic Airborne Telemetry Networks" Kamakshi Sirisha Pathapati, Nguyễn Ngọc Trúc Anh, Justin P. Rohrer, and James P.G. Sterbenz, International Telemetering Conference (ITC) Oct. 2011 https://wiki.ittc.ku.edu/resilinets/ResiliNets_Publications#.E2.80.9CPerformance_Analysis_of_the_AeroTP_Transport_Protocol_for_Highly-Dynamic_Airborne_Telemetry_Networks.E2.80.9D (an abstract-reviewed conference in which we publish a number of student papers because our DoD funding sponsors are heavily involved; we put our copy online this summer after DoD clearance) has appeared as "Experimental Evaluation of AeroTP Protocol for Airborne Telemetry Networks" Arun Prasath Siva Thanu Pillai IJCSNS International Journal of Computer Science and Network Security Volume 11, issue 9 http://ijcsns.org/ This journal has a stunningly fast turnaround time; the notation at the bottom of the paper indicates that it was received 5 Sep., revised 20 Sep, and apparently online 30 Sep. I guess this is possible if there is no review. Except for the title (in part stolen from another one of our papers at the same conference) the paper appears *identical* except for the plethora of OCR transcription errors. The authors even kept the language talking about the previous work while still referencing our own papers and left the acknowledgements to my DoD contract. The scanned figures are pretty unreadable. Even a cursory examination by a human should have raised suspicion. In this case after a bit of searching on the Web I believe the author is applying to graduate schools in the US, and the motivation must have been fill up the CV. This leads to the question: Is IJCSNS a complete scam? The Web site indicates an address of Dae-Sang Office 301, Sangdo 5 dong 509-1, Dongjack Gu, Seoul 156-743, Korea. Do any of my Korean colleagues know about them? There is only one contact email for IJCSNS, but there are affiliations of the editors, so I will next try to track them down and attempt to contact them. Are all of these new open access journals popping up intended as a way for people to load their CVs with journal publications? What institutions would be naive enough to not realise they are bogus? It appears that we've got an increasing problem, and we probably all need to be vigilant on what is going on. In this case, the plagiarised paper is already in Google Scholar, so I'll have to see if there is a manual takedown process there, as well as DBLP, MS Academic Search, Citeseer, etc. Sigh. James --------------------------------------------------------------------- James P.G. Sterbenz jpgs@{ittc|eecs}.ku.edu [email protected] www.ittc.ku.edu/~jpgs 154 Nichols ITTC|EECS InfoLab21 Lancaster U +1 508 944 3067 The University of Kansas [email protected] jpgs@{acm|ieee|comsoc|computer|m.ieice}.org [email protected] gplus.to/jpgs www.facebook.com/jpgsterbenz google|skype:jpgsterbenz --- Regards, Sakib On Tue, Jan 15, 2013 at 3:13 AM, Joe Touch <[email protected]> wrote: > Hi, Anand (et al.), > > If you have a case concerning potential plagiarism that involves work > published in IEEE Xplore (either the original work or the alleged > plagiarized work), I encourage you to review the instructions available at > the IEEE Intellectual Property Rights Office: > > http://www.ieee.org/**publications_standards/** > publications/rights/index.html<http://www.ieee.org/publications_standards/publications/rights/index.html> > > They provide a FAQ on how best to resolve cases of alleged plagiarism. > > It is not appropriate to use this forum for such allegations. > > Joe Touch > IEEE ComSoc Director of Conference Operations > > > On 1/13/2013 10:51 PM, Al-Sakib Khan Pathan wrote: > >> Dear Colleagues, >> >> Though, this could be an off-topic and may violate the norms of posting to >> TCCC, I feel it is necessary to write a few lines as this is one of the >> most active groups. No reply is expected to avoid unnecessary flooding, >> but >> this is sent to a wide range of editors and researchers to be aware of >> such >> submissions. >> >> It may be okay if someone takes other person's idea partially and improves >> or uses it elsewhere giving proper credits or citations. However, the case >> of plagiarism, often with exact copy or slightly modified version has >> increased in recent days. From my given roles, I have encountered several >> such matters in various events, many of which have come out from >> especially >> South India and China. Just to understand the matter, I have mentioned the >> names of the exact places and it should not be taken as a statement >> against >> anybody but what is evident among the submissions caught. Often, such >> individuals (claimed authors) are bold enough to post their documents in >> public. >> >> Let us see someone who claims to be, "Academician, Researcher, Scholar, >> Author, Innovator, Hacker" >> (http://www.anandnayyar.com/**home.aspx<http://www.anandnayyar.com/home.aspx> >> ) >> >> Here's a blatant plagiarism case. From Editor's position, often it is not >> possible to verify such cases, hence the burden lies on the reviewers who >> commented on it and of course on the person who submitted. It can happen >> in >> apparently good journals as well. Sometimes these matters are not solved >> (I >> have communicated many for several times) and we could at best do our part >> by warning the person (which may not work). >> >> *OUR ORIGINAL paper:* >> http://networking.khu.ac.kr/**publications/data/Security%** >> 20in%20Wireless%20Sensor%**20Networks%20Issues%20and%**20Challenges.pdf<http://networking.khu.ac.kr/publications/data/Security%20in%20Wireless%20Sensor%20Networks%20Issues%20and%20Challenges.pdf> >> http://ieeexplore.ieee.org/**xpls/abs_all.jsp?arnumber=**1625756&tag=1<http://ieeexplore.ieee.org/xpls/abs_all.jsp?arnumber=1625756&tag=1> >> * >> Plagiarized Paper >> ----------------------------* >> Security Issues & Challenges in Wireless Sensor Networks >> Author: Anand Nayyar Assistant Professor Department of Computer >> Applications & IT KCL Institute of Management and Technology, Jalandhar, >> India >> [email protected] >> >> http://www.gpublication.com/**jcer/ <http://www.gpublication.com/jcer/> >> http://www.gpublication.com/**jcer/?wicket:interface=:5::<http://www.gpublication.com/jcer/?wicket:interface=:5::> >> :: >> DIRECT LINK: >> http://www.gpublication.com/**jcer/?wicket:interface=:5:** >> issuelist:5:fulltext::**ILinkListener<http://www.gpublication.com/jcer/?wicket:interface=:5:issuelist:5:fulltext::ILinkListener> >> :: >> >> Again posted in: >> http://www.anandnayyar.com/**pdf/2011/Security_Issues__** >> Challenges_in_Wireless_Sensor_**Networks.pdf<http://www.anandnayyar.com/pdf/2011/Security_Issues__Challenges_in_Wireless_Sensor_Networks.pdf> >> >> Searchable in Google. >> >> Regards, >> Sakib >> >> -- Al-Sakib Khan Pathan, Ph.D. Founding Head, NDC Laboratory<http://staff.iium.edu.my/sakib/ndclab/index.html>, KICT, IIUM Assistant Professor, Department of Computer Science Kulliyyah (Faculty) of Information and Communication Technology International Islamic University Malaysia (IIUM) Jalan Gombak, 53100, Kuala Lumpur, MALAYSIA Tel: +603-61964000 Ext. 5653, Cell: +60163910754 E-Mails: [email protected], [email protected] Personal URL: http://staff.iium.edu.my/sakib/ NDC Lab URL: http://staff.iium.edu.my/sakib/ndclab/ _______________________________________________ IEEE Communications Society Tech. Committee on Computer Communications (TCCC) - for discussions on computer networking and communication. [email protected] https://lists.cs.columbia.edu/cucslists/listinfo/tccc
