Definition

network access point (NAP)

In the United States, a network access point (NAP) is one of several major Internet interconnection points that serve to tie all the Internet access providers together so that, for example, an AT&T user in Portland, Oregon can reach the Web site of a Bell South customer in Miami, Florida. Originally, four NAPs - in New York, Washington, D.C., Chicago, and San Francisco - were created and supported by the National Science Foundation as part of the transition from the original U.S. government-financed Internet to a commercially operated Internet. Since that time, several new NAPs have arrived, including WorldCom's "MAE West" site in San Jose, California and ICS Network Systems' "Big East."

The NAPs provide major switching facilities that serve the public in general. Using companies apply to use the NAP facilities and make their own intercompany peering arrangements. Much Internet traffic is handled without involving NAPs, using peering arrangements and interconnections within geographic regions. The vBNS network, a separate network supported by the National Science Foundation for research purposes, also makes use of the NAPs.

This was last updated in April 2005
Posted by: Margaret Rouse

Email Alerts

Register now to receive SearchSOA.com-related news, tips and more, delivered to your inbox.
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

More News and Tutorials

  • SOA, semantics and services combine in DoD intelligence sharing effort

    Using textual analytics and natural language processing, Modus Operandi developed a service that analyzes and parses unstructured data and pulls out events or information. Article includes tips on SOA and semantics, SOA and data models, and an SOA recipe for stone soup.Among highlights: Recognize that not everything can be or should be shared.

  • Q&A: Messaging middleware with Apache projects

    In this Q&A, Rob Davies discusses messaging middleware and the hurdles that many developers face as they first approach the subject. Davis is CTO of FuseSource and coauthor of the book "ActiveMQ in Action."

  • An SOA practices checklist for implementation roadmaps

    This article provides a master list of common practices, field proven by a number of SOA projects. Also supplied is a template that can be used as a checklist for developing SOA implementation roadmaps specific to an organization's transition project requirements.

Do you have something to add to this definition? Let us know.

Send your comments to techterms@whatis.com
Back to top