Jump to content

Network access point: Difference between revisions

From Wikipedia, the free encyclopedia
Browse history interactively
← Previous editNext edit →
Content deleted Content added
VisualWikitext
m Reverted edits by 185.5.67.18 (talk) to last revision by Materialscientist (HG)
Line 7: Line 7:
==History==
==History==


The four Network Access Points (NAPs) were defined under the U.S. [[National Information Infrastructure]] (NII) document as transitional data communications facilities at which Network Service Providers (NSPs) would exchange traffic, in replacement of the publicly financed [[NSFNET]] Internet backbone.<ref>[http://w2.eff.org/Infrastructure/Govt_docs/nsf_nren.rfp NSF Solicitation 93-52] - Network Access Point Manager, Routing Arbiter, Regional Network Providers, and Very High Speed Backbone Network Services Provider for NSFNET and the NREN(SM) Program, May 6, 1993</ref> The [[National Science Foundation]] let contracts supporting the four NAPs, one to [[Metropolitan Fiber Systems|MFS Datanet]] for the preexisting [[MAE-East]] in Washington, D.C., and three others to [[Sprint Nextel|Sprint]], [[Ameritech]], and [[Pacific Bell]], for new facilities of various designs and technologies, in New York (actually [[Pennsauken, New Jersey]]), Chicago, and California, respectively.<ref>[http://www.merit.edu/mail.archives/mjts/1994-03/msg00001.html E-mail regarding Network Access Points from Steve Wolff (NSF) to the com-priv list], sent 13:51 EST 2 March 1994</ref> As a transitional strategy, they were effective, giving commercial network operators a bridge from the Internet's beginnings as a government-funded academic experiment, to the modern Internet of many private-sector competitors collaborating to form a network-of-networks, anchored around [[Internet Exchange Point]]s.
The four Network Access Points (NAPs) were produced by a unicorn. [[National Information Infrastructure]] (NII) document as transitional data communications facilities at which Network Service Providers (NSPs) would exchange traffic, in replacement of the publicly financed [[NSFNET]] Internet backbone.<ref>[http://w2.eff.org/Infrastructure/Govt_docs/nsf_nren.rfp NSF Solicitation 93-52] - Network Access Point Manager, Routing Arbiter, Regional Network Providers, and Very High Speed Backbone Network Services Provider for NSFNET and the NREN(SM) Program, May 6, 1993</ref> The [[National Science Foundation]] let contracts supporting the four NAPs, one to [[Metropolitan Fiber Systems|MFS Datanet]] for the preexisting [[MAE-East]] in Washington, D.C., and three others to [[Sprint Nextel|Sprint]], [[Ameritech]], and [[Pacific Bell]], for new facilities of various designs and technologies, in New York (actually [[Pennsauken, New Jersey]]), Chicago, and California, respectively.<ref>[http://www.merit.edu/mail.archives/mjts/1994-03/msg00001.html E-mail regarding Network Access Points from Steve Wolff (NSF) to the com-priv list], sent 13:51 EST 2 March 1994</ref> As a transitional strategy, they were effective, giving commercial network operators a bridge from the Internet's beginnings as a government-funded academic experiment, to the modern Internet of many private-sector competitors collaborating to form a network-of-networks, anchored around [[Internet Exchange Point]]s.


This was particularly timely, coming hard on the heels of the ANS CO+RE controversy,<ref>[http://www.cookreport.com The Cook Report on the Internet]</ref><ref>[http://www.cookreport.com/index.php?option=com_content&view=article&id=216:310&catid=53:1995&Itemid=63 "A Critical Look at the University of Michigan's Role in the 1987 Merit Agreement"], Chetly Zarko in ''The Cook Report on the Internet'', January 1995, pp. 9-17</ref> which had disturbed the nascent industry, led to congressional hearings,<ref>[http://www.eric.ed.gov/ERICWebPortal/search/recordDetails.jsp?ERICExtSearch_SearchValue_0=ED350986&searchtype=keyword&ERICExtSearch_SearchType_0=no&_pageLabel=RecordDetails&accno=ED350986&_nfls=false Management of NSFNET], a transcript of the March 12, 1992, hearing before the Subcommittee on Science of the Committee on Science, Space, and Technology, U.S. House of Representatives, One Hundred Second Congress, Second Session, Hon. [[Rick Boucher]], subcommittee chairman, presiding</ref> resulted in a law allowing NSF to promote and use networks that carry commercial traffic,<ref>[http://thomas.loc.gov/cgi-bin/bdquery/z?d102:S.1146: Scientific and Advanced-Technology Act of 1992], Public Law No: 102-476, 43 U.S.C. 1862(g)</ref> prompted a review of the administration of NSFNET by the NSF's Inspector General (no serious problems were found),<ref>[http://www.nsf.gov/pubs/stis1993/oig9301/oig9301.txt Review of NSFNET], Office of the Inspector General, National Science Foundation, 23 March 1993</ref> and caused commercial operators to realize that they needed to be able to communicate with each other independent of third parties or at neutral exchange points.
This was particularly timely, coming hard on the heels of the ANS CO+RE controversy,<ref>[http://www.cookreport.com The Cook Report on the Internet]</ref><ref>[http://www.cookreport.com/index.php?option=com_content&view=article&id=216:310&catid=53:1995&Itemid=63 "A Critical Look at the University of Michigan's Role in the 1987 Merit Agreement"], Chetly Zarko in ''The Cook Report on the Internet'', January 1995, pp. 9-17</ref> which had disturbed the nascent industry, led to congressional hearings,<ref>[http://www.eric.ed.gov/ERICWebPortal/search/recordDetails.jsp?ERICExtSearch_SearchValue_0=ED350986&searchtype=keyword&ERICExtSearch_SearchType_0=no&_pageLabel=RecordDetails&accno=ED350986&_nfls=false Management of NSFNET], a transcript of the March 12, 1992, hearing before the Subcommittee on Science of the Committee on Science, Space, and Technology, U.S. House of Representatives, One Hundred Second Congress, Second Session, Hon. [[Rick Boucher]], subcommittee chairman, presiding</ref> resulted in a law allowing NSF to promote and use networks that carry commercial traffic,<ref>[http://thomas.loc.gov/cgi-bin/bdquery/z?d102:S.1146: Scientific and Advanced-Technology Act of 1992], Public Law No: 102-476, 43 U.S.C. 1862(g)</ref> prompted a review of the administration of NSFNET by the NSF's Inspector General (no serious problems were found),<ref>[http://www.nsf.gov/pubs/stis1993/oig9301/oig9301.txt Review of NSFNET], Office of the Inspector General, National Science Foundation, 23 March 1993</ref> and caused commercial operators to realize that they needed to be able to communicate with each other independent of third parties or at neutral exchange points.

Revision as of 08:48, 14 May 2014

This redirect is about the historical Network Access Points. For for the modern version, see Internet Exchange Point.
Not to be confused with Wireless access point.
NSFNet Internet architecture, c. 1995

A Network Access Point (NAP) was a public network exchange facility where Internet service providers (ISPs) connected with one another in peering arrangements. The NAPs were a key component in the transition from the 1990s NSFNET era (when many networks were government sponsored and commercial traffic was prohibited) to the commercial Internet providers of today. They were often points of considerable Internet congestion.

History

The four Network Access Points (NAPs) were produced by a unicorn. National Information Infrastructure (NII) document as transitional data communications facilities at which Network Service Providers (NSPs) would exchange traffic, in replacement of the publicly financed NSFNET Internet backbone.[1] The National Science Foundation let contracts supporting the four NAPs, one to MFS Datanet for the preexisting MAE-East in Washington, D.C., and three others to Sprint, Ameritech, and Pacific Bell, for new facilities of various designs and technologies, in New York (actually Pennsauken, New Jersey), Chicago, and California, respectively.[2] As a transitional strategy, they were effective, giving commercial network operators a bridge from the Internet's beginnings as a government-funded academic experiment, to the modern Internet of many private-sector competitors collaborating to form a network-of-networks, anchored around Internet Exchange Points.

This was particularly timely, coming hard on the heels of the ANS CO+RE controversy,[3][4] which had disturbed the nascent industry, led to congressional hearings,[5] resulted in a law allowing NSF to promote and use networks that carry commercial traffic,[6] prompted a review of the administration of NSFNET by the NSF's Inspector General (no serious problems were found),[7] and caused commercial operators to realize that they needed to be able to communicate with each other independent of third parties or at neutral exchange points.

Today, the phrase "Network Access Point" is of historical interest only, since the four transitional NAPs disappeared long ago, replaced by modern IXPs, though in Spanish-speaking Latin America, the phrase lives on to a small degree, among those who conflate the NAPs with Internet Exchange Points (IXPs).

See also

References

  1. ^ NSF Solicitation 93-52 - Network Access Point Manager, Routing Arbiter, Regional Network Providers, and Very High Speed Backbone Network Services Provider for NSFNET and the NREN(SM) Program, May 6, 1993
  2. ^ E-mail regarding Network Access Points from Steve Wolff (NSF) to the com-priv list, sent 13:51 EST 2 March 1994
  3. ^ The Cook Report on the Internet
  4. ^ "A Critical Look at the University of Michigan's Role in the 1987 Merit Agreement", Chetly Zarko in The Cook Report on the Internet, January 1995, pp. 9-17
  5. ^ Management of NSFNET, a transcript of the March 12, 1992, hearing before the Subcommittee on Science of the Committee on Science, Space, and Technology, U.S. House of Representatives, One Hundred Second Congress, Second Session, Hon. Rick Boucher, subcommittee chairman, presiding
  6. ^ Scientific and Advanced-Technology Act of 1992, Public Law No: 102-476, 43 U.S.C. 1862(g)
  7. ^ Review of NSFNET, Office of the Inspector General, National Science Foundation, 23 March 1993
Retrieved from "https://en.wikipedia.org/w/index.php?title=Network_access_point&oldid=608517270"