by DAN CALLOWAY
Publlished 7 March 2010

UNITED STATES – The networking needs of XYZ Corporation have changed significantly over the last five years. As the IT manager, it is imperative that the approach I recommend to management for upgrading the network—not just for the sake of improving applications that run on it, but taking into account the aspects of improving the network from a hardware and software (protocol) perspective—be taken that will ensure a reliable, scalable, and efficient network that will not only meet the requirements—now but five years from now—of the business sector and its partners (stakeholders) in the organization who will likely need to remotely connect to the network, but which will be acceptable to everyone and that can be accomplished with the least effort and most economical means.

The approach that is often taken when upgrading a corporate network, like XYZ Corporation, is to rush into the upgrade by adding network devices of differing quality from various vendors as well as software applications in the same manner because the hardware and software is the latest and greatest on the market and does exactly what the business office wants to implement and use. This is the wrong approach because the business office and management lose sight of the fact that a lot of planning goes into upgrading a network from a hardware/software and services perspective. If the former approach is taken, then most likely at some point, the network will no longer be able to support the services needed for the business factions or the network traffic generated by the users. When the network fails, then, undoubtedly, management will look to point blame on IT for not ensuring the upgrade was successful in the first place and, in all likelihood, will seek outside assistance (an ISP or managed service) in giving advice and correcting the issue, which will be costly and will adversely affect IT’s credibility in the organization.

The approach that I would recommend to management after reviewing the corporate strategic goals and current and projected mission statements of the company would be to: (1) Confer with my department on the goals the company wanted to meet and where it was heading in the next five to ten years, and elicit from them their expert recommendations for the necessary hardware and software that would be required to achieve those goals; (2) Have an onsite technician perform a site survey of the network, documenting the physical layout of the current network from a hardware standpoint, and the applications that currently run on the network as a starting point for the upgrade project; (3) Ensure the site survey collected information on the current business plans and projected growth of the company, number of users and types of equipment needed, current Internet connectivity, what applications the network needs to support, what new services will be required now and in the future, what the security and privacy requirements are now and in the future, what the wireless network requirements (wireless or a mix of wired and wireless) are, what the reliability and uptime expectations of the new network are, and what are the budget constraints; (4) Request a formal written proposal from a prospective ISP on the requirements for and the costs associated with supporting the backbone for the network; (5) Develop a SWOT (strengths, weaknesses, opportunities, and threats) analysis of the upgrade plan; and (6) Report the findings of the site survey, written proposal of the ISP, results of the SWOT analysis, and documented proposal for the network upgrade to management for their approval. Following the approval from management, I would execute the network upgrade in five phases: (1) Requirements gathering, (2) Selection, design, and purchasing of equipment and applications, (3) Implementation of the upgrade, (4) Operation in a live environment, and (5) Review and evaluate the new network (hardware/software applications) against the original design plans to see if they are a match (“The Technology Upgrade Planning Guide,” 2010).

I would not foresee any major obstacles to implementing the network upgrade if all of the steps outlined above are executed properly and there is complete and upfront communications between the IT department and the business factions/management during all phases of requirements gathering, design selection, implementation, operation, and review.

——————————

References:

The Technology Upgrade Planning Guide. (2010). The Technology Upgrade Planning Guide. Retrieved March 8, 2010, from http://www.thebrookfieldgroup.com/news_story32.php.

Tagged with:
 

by DAN CALLOWAY
Published 11 February 2010 @ 23:42 UTC

WEAVERVILLE, NC – Abstract - Napster is a hybrid P2P networking application that has revolutionized the worldwide marketing, distribution, and availability of music MP3 files. Although Napster was originally designed to permit users across the Internet to share music on their computers with other Napster users, the evolution of this P2P networking application has opened up new possibilities for e Commerce for the music industry to take advantage of increased availability of music worldwide, which can potentially lead to increased music sales revenues for individual music organizations and the music industry as a whole.

Introduction

The P2P networking application that was chosen for this critique was Napster. This application was selected because of its applicability to any organization that has the need to share, or make available for sale, music files with others across the Internet. Music companies, such as the fictional company, XYZ Music, Inc., can easily share music with other companies who need access to music as well as obtain music files from other organizations in the music business easily, quickly, and securely without having to use other slower means such as the mail system or courier.

Background

Napster was the original hybrid Peer-to-peer (P2P) networking MP3 file sharing application that became popular overnight. A hybrid P2P networking system has a central server that maintains information on peers and responds to requests for that information but this central server does not store individual files that are shared (Crosse, Wilson, Walsh, Cohen, & Smith, 2002). This application represents the quintessential P2P software application still in use today. The definition for P2P was first suggested by Dave Winer of UserLand Software years ago when P2P was beginning to hit the mainstream (Mitchell, B., 2010). Dave suggested that all P2P networking applications have seven key characteristics: (1) the user interface runs outside of a Web browser; (2) computers who use the system act as both servers and clients; (3) the software application is user friendly and easy to install; (4) the application allows users to create their own content and add functionality; (5) the application connects to other users; (6) the application performs a new or innovative purpose; and (7) the software application supports “cross networking” protocols, such as SOAP or XML-RPC (Mitchell, B). Napster holds true to form as a P2P networking application that meets all seven of these requirements.

What Does Napster Do?

Napster allows users within an organization and not just within a home LAN to share MP3 music files with other users across the Internet via a cross-platform application that runs outside of a Web browser. In addition to allowing users to share file content with others, it allows users to create content and make that content available for downloading while selecting the granularity with which they can securely perform this file sharing functionality. Thus Napster is not only a file server (allowing others to download content from a platform), but is a file sharing client. Napster also has a self-contained chat functionality, which permits users to communicate with one another prior to, during, and after file downloads (Mitchell, B., 2010). The chat functionality within Napster was both innovative and exciting for users when it was first developed and distributed worldwide, and it remains an innovative product even today. Napster originally referred to not only the P2P networking component but the file sharing client portion as well. Even though the P2P networking component was somewhat transparent to the user and did not affect its user popularity, Napster used a proprietary networking protocol that supported its functionality across the Internet (Mitchell, B.)

Why Does Napster Benefit From P2P Networking?

Napster benefits from hybrid P2P networking capabilities because, unlike traditional server-client networking arrangements, hybrid P2P’s distributed computing functionality allows the sharing of files, such as MP3 files, and other computer services, such as chat, via direct transfer between two computers (Crosse et al., 2002). Eliminating the need for a Server to push files to clients across the Internet, users can share the content of their hard drives and don’t have to rely on a master Server repository of MP3 files that may not be updated on a regular basis. Moreover, unlike a single Server supporting multiple clients worldwide, users’ desktop computers containing the requested MP3 files are more likely to be in an “up” status somewhere in the world on a continual basis, thus affording greater access to these files when requested.

How Does an Organization Benefit from Napster?

Organizations benefit from Napster, especially the music industry or, specifically, XYZ Music, Inc., in Napster’s ability to make music files available to a larger audience of potential users than would be possible in traditional server-client networking scenarios. Through this increased availability, the music industry and XYZ Music, Inc., could market their music to a much wider group of potential music buyers than would be possible otherwise.

What are the issues Regarding the Use of Napster?

One major issue or drawback to increased availability of MP3 music files via Napster and the hybrid P2P networking scenario, however, is the increased risk in music piracy via sharing of music without paying royalties (Crosse et al., 2002). Nonetheless, if the security measures can be worked out through the use of P2P networking, such that MP3 music files are not pirated, then the availability of and increased revenues that can be seen from a greater purchasing audience is worth the risk. A side issue with the original use of Napster was the inability of the music industry, as a whole, to regulate the downloading of or sharing of newly-created music files, which circumvented the music industry’s control of the worldwide marketing and distribution of these MP3 files (Crosse et al., 2002). These issues appear to have been worked out since Napster appeared on the scene many years ago, and Napster has enjoyed a renewed vigor in the realm of P2P networking applications.

References

Crosse, S., Wilson, E., Walsh, A., Cohen, D., & Smith, C. (2002). P2P Networks. P2P Networks. Retrieved February 11, 2010, from http://ntrg.cs.tcd.ie/undergrad/4ba2.02-03/p4.html

Mitchell, B. (2010). Overview of P2P Applications and Networks. Overview of P2P Applications and Networks. Retrieved February 11, 2010, from http://compnetworking.about.com/od/p2ppeertopeer/a/p2pintroduction_2.htm

Excerpt from the ITU Internet Report 2005 on the Internet of Things (Note: Slightly dated information)
Source:  www.itu.int/internetofthings/

RFID_Guardian-04Internet of Things is a technological revolution that represents the future of computing and communications, and its development depends on dynamic technical innovation in a number of important fields, from wireless sensors to nanotechnology.

First, in order to connect everyday objects and devices to large databases and networks – and indeed to the network of networks (the internet) – a simple, unobtrusive and cost-effective system of item identification is crucial. Only then can data about things be collected and processed. Radio-frequency identification (RFID) offers this functionality. Second, data collection will benefit from the ability to detect changes in the physical status of things, using sensor technologies. Embedded intelligence in the things themselves can further enhance the power of the network by devolving information processing capabilities to the edges of the network. Finally, advances in miniaturization and nanotechnology mean that smaller and smaller things will have the ability to interact and connect. A combination of all of these developments will create an Internet of Things that connects the world’s objects in both a sensory and an intelligent manner.

Indeed, with the benefit of integrated information processing, industrial products and everyday objects will take on smart characteristics and capabilities. They may also take on electronic identities that can be queried remotely, or be equipped with sensors for detecting physical changes around them. Eventually, even particles as small as dust might be tagged and networked. Such developments will turn the merely static objects of today into newly dynamic things, embedding intelligence in our environment, and stimulating the creation of innovative eproducts and entirely new services. RFID technology, which uses radio waves to identify items, is seen as one of the pivotal enablers of the Internet of Things. Although it has sometimes been labelled as the next-generation of bar codes, RFID systems offer much more in that they can track items in real-time to yield important information about their location and status. Early applications of RFID include automatic highway toll collection, supply-chain management (for large retailers), pharmaceuticals (for the prevention of counterfeiting) and e-health (for patient monitoring). More recent applications range from sports and leisure (ski passes) to personal security (tagging children at schools). RFID tags are even being implanted under human skin for medical purposes, but also for VIP access to bars like the Baja Beach Club in Barcelona. E-government applications such as RFID in drivers’ licences, passports or cash are under consideration. RFID readers are now being embedded in mobile phones. Nokia, for instance, released its RFID-enabled phones for businesses with workforces in the field in mid-2004 and plans to launch consumer handsets by 2006. (more…)

Tagged with:
 

by DAN CALLOWAY
Posted September 25, 2009; The Chronicler’s Web

Dan Calloway_cropWEAVERVILLE, NC – What is the XMPP Protocol?

The Extensible Messaging and Presence Protocol (XMPP) is an open technology for real-time communication, which powers a wide range of applications including instant messaging, presence, multi-party chat, voice and video calls, collaboration, lightweight middleware, content syndication, and generalized routing of XML data. Several books about Jabber/XMPP technologies are available.

The core technology behind XMPP was invented by Jeremie Miller in 1998, refined in the Jabber open-source community in 1999 and 2000, and formalized by the IETF in 2002 and 2003, resulting in publication of the XMPP RFCs in 2004.

Although the core technology is stable, the XMPP community continues to define various XMPP extensions through an open standards process run by the XMPP Standards Foundation. There is also an active community of open-source and commercial developers, who produce a wide variety of XMPP-based software.

If you have any questions about the use or development of XMPP technologies, feel free to participate in one of the open discussion venues hosted by the XMPP Standards Foundation.

Source: XMPP Website

Tagged with:
 

by DONALD CALLOWAY
Posted September 24, 2009; Chronicler’s Web

CLARKSBURG, WV — As soon as Microsoft releases the final bits of a new Windows release to manufacturing — and often before — many users’ thoughts turn to what’s next.

Windows 7 and its server complement, Windows Server 2008 R2, were released to manufacturing in late July. By late August, Microsoft’s Windows client unit already was turning the crank on Windows 8 client and server.

Anders Vindberg, a Microsoft Technical Fellow in Microsoft’s Management and Services division — a “Big Brains” interview with whom I’ll be posting soon — acknowledged that planning sessions were well underway for Windows 8. And of the 12 working groups created, “eight or nine revolve around management.” (Back in April of this year, Microsoft was seeking developers interested in working on some of these management features and enhancements to Distributed File System Replication for Windows 8.)

Stephen Chapman, a tech enthusiast who runs the UX Evangelist site, has been beating the bushes for a few months now for Windows 8 information. He recently unearthed a number of job profiles of folks who have worked on and are working on various elements which may or may not make it into the final Windows 8 release. (more…)

 
Get Adobe Flash playerPlugin by wpburn.com wordpress themes

SEO Powered by Platinum SEO from Techblissonline