Cybertelecom
Cybertelecom
Federal Internet Law & Policy
An Educational Project

Layered Model of Regulation

Navigation Links:
:: Home :: Feedback ::
:: Disclaimer :: Sitemap ::

- Broadband
- Sec. 706
- Stimulus Plan
- FCC Natl BB Plan
- Dial Up
- DSL
- - Naked DSL
- - UNE
- - Net over Wireline (Info Service)
- Cable
- - Open Access
- Fiber
- Wireless
- - 3G
- - Wifi
- - WiMax
- - 700 Mhz
- Powerline
- Satellite
- Muni Broadband
- Telecom Services
- Computer Inquiries
- Network Neutrality
- Consumer Protection
- Forbearance
- Backbones
- - ICAIS
- Layers
- Interconnection
- - Negotiation
- Reciprocal Comp
- Mergers
- Federal Advisory Committees
- FCC
- Universal Service
- Statistics: Broadband

OSI Stack

7. Application

6. Presentation
5. Session
4. Transport
3. Network
2. Data Link
1. Physical
Internet Stack
Application
(DHCP, DNS, FTP, HTTP, IRC, POP3, TELNET...)
Transport
(TCP, UDP, RTP...)

Internet
(IP)

Data Link
(ATM, Ethernet, FDDI, Frame Relay, PPP...)

Physical Layer
(Ethernet physical layer, ISDN, Modems, SONET...)

Policy Layers
Content
(intellectual property, fraud, offensive content...)
Applications
(VoIP, Gambling, Email, {regardless of content} ...)
Internet
(Security, access, interconnection, market...)
Physical Infrastructure
(common carriage, markets, security, reliability.....)

OSI

"FIPS 146-1 adopted the Government Open Systems Interconnection Profile (GOSIP) which defines a common set of Open Systems Interconnection (OSI) protocols that enable systems developed by different vendors to interoperate and the users of different applications of those systems to exchange information. This change modifieds FIPS 146-1 by removing the requirement that Federal agencies specify GOSIP protocols when they acquire networking products and services and communications systems and services. This change references additional specifications that Federal agencies may use in acquiring data communications protocols. " FIPS 146-2, Profiles for Open Systems Internetworking Technologies (POSIT), NIST (May 15, 1995)

"In October 1993, NIST established the Federal Internetworking Requirements Panel to study and recommend policies on the use of networking standards by the Federal government. Based on feedback from industry, individual users, and international organizations on its draft report, the Panel submitted its final recommendations for public comment on May 1994. The Panel concluded that no single networking protocol suite meets the full range of government requirements for data internetworking. The Panel recommended that Federal government agencies select standards based on their interoperability needs, existing infrastructure, costs, marketplace products, and the degree to which the protocol has been adopted as a standard. As follow-up, NIST has proposed changes to the Federal Information Processing Standard that will remove the requirement specifying use of the Government Open Systems Interconnection Profile (GOSIP) protocols when agencies acquire networking and communication products. NIST currently is soliciting public comment on these proposed changes and will issue a final version in early 1995." - Department of Commerce, National Information Infrastructure Progress Report p 11 September 1993-1994.

See Layered Model.

 

Papers

Books

  • Janet Abbate, Inventing the Internet (MIT Press 1999) Recounting how the layered model was adopted for ARPANET
    • P 66: "The initial division between subnet and host layers had simplified the work of the network's designers; now the [Network Control Center] NCC allowed the network's users to ignore much of the operational complexity of the subnet and to view the entire communications layer as a black box operated by Bolt, Beranek and Newman [BBN]. The NCC had become a managerial reinforcement of ARPA's layering scheme."
    • P 67: "Roberts suggested separating the host functions into two layers. The first, called the "host layer," would feature a general-purpose protocol to set up communications between a pair of hosts; the second, called the "application layer," would specify protocols for network applications such as remote login or file transfer. Having spearate host and application layers would simply the host protocol and lessen the burden on the host system's programmers. Also, eliminating the need for each application to duplicate the work of setting up a host-to-host connection would make it easier to create applications programs, thereby encouraging people to add to the pool of network resources. The ARPANet model now had three layers...." This model would be reflected in the Network Control Protocol (NCP)
  • Katie Hafner and Matthew Lyon, Where Wizards Stay Up Late: The Origins of the Internet, p. 147 (1996):
    • "Whatever structure they chose, they knew they wanted it to be as open, adaptable, and accessible to inventiveness as possible. The general view was that any protocol was a potential building block, and so the best approach was to define simple protocols, each limited in scope, with the expectation that any of them might someday be joined or modified in various unanticipated ways. The protocol design philosophy adopted by the NWG broke ground for what came to be widely accepted as the “layered” approach to protocols."
Web services provided by Wyoming.com
:: Home :: About Us :: Contact Us :: Sitemap :: Discussion :: Disclaimer :: Search ::