31:
264:
154:
One could combine the two protocols to form a powerful third, mastering both cable and wireless transmission, but a different super-protocol would be needed for each possible combination of protocols. It is easier to leave the base protocols alone, and design a protocol that can work on top of any of
373:
Certain protocols are designed with the specific purpose of bridging differences at the lower layers, so that common agreements are not required there. Instead, the layer provides the definitions that permit translation to occur between a range of services or technologies used below. Thus, in
206:
or platform will often have two well-defined software interfaces: one between the media and transport layers, and one between the transport layers and applications. The media-to-transport interface defines how transport protocol software makes use of particular media and hardware types and is
91:
in a stack of protocols. The lowest protocol always deals with low-level interaction with the communications hardware. Each higher layer adds additional capabilities. User applications usually deal only with the topmost layers.
159:
is an example). This will make two stacks of two protocols each. The inter-network protocol will communicate with each of the base protocol in their simpler language; the base protocols will not talk directly to each other.
378:
in this paper. As a practical matter, real interoperation is achieved by the definition and use of effective spanning layers. But there are many different ways that a spanning layer can be crafted.
524:
The
Application layer is the topmost layer of the OSI model, and it provides services that directly support user applications, such as database access, e-mail, and file transfers.
235:
environment. The application-to-transport interface defines how application programs make use of the transport layers. For example, this interface level would define how a
374:
somewhat abstract terms, at and above such a layer common standards contribute to interoperation, while below the layer translation is used. Such a layer is called a
224:
202:
In practical implementation, protocol stacks are often divided into three major sections: media, transport, and applications. A particular
495:
that defines seven protocol layers is often called a stack, as is the set of TCP/IP protocols that define communication over the
Internet.
435:
425:
545:
87:
simplifies design and evaluation. Because each protocol module usually communicates with two others, they are commonly imagined as
187:
is not the final destination, will again invoke lower-level functions. This time, the cable protocol is used to send the data to
183:. On this computer, the lower layer handlers will pass the packet up to the inter-network protocol, which, on recognizing that
508:
455:
300:
450:
216:
586:
415:
220:
84:
445:
383:
136:
123:
both have radio equipment and can communicate via the airwaves using a suitable network protocol (such as
69:
135:
are connected via a cable, using it to exchange data (again, with the help of a protocol, for example
492:
387:
362:
An important feature of many communities of interoperability based on a common protocol stack is a
555:
541:
312:
293:
228:
156:
88:
240:
203:
54:
83:
Individual protocols within a suite are often designed with a single purpose in mind. This
567:
337:
305:
148:
403:
367:
349:
317:
268:
239:
program would talk to TCP/IP transport software. Examples of these interfaces include
50:
479:
139:). However, neither of these two protocols will be able to transport information from
580:
440:
430:
321:
208:
512:
344:
236:
191:. There, the received packet is again passed to the upper protocol, which (with
179:. It, therefore, instructs the wireless protocol to transmit the data packet to
124:
17:
333:
195:
being the destination) will pass it on to a higher protocol or application on
391:
248:
35:
64:. Some of these terms are used interchangeably but strictly speaking, the
171:
is taken by the upper protocol, which (through whatever means) knows that
30:
399:
328:
77:
395:
252:
244:
420:
212:
147:, because these computers are conceptually on different networks. An
263:
262:
29:
460:
288:
232:
538:
Interoperation, Open
Interfaces, and Protocol Architecture
491:
A set of network protocol layers that work together. The
211:. For example, this interface level would define how
273:
275:Example protocol stack and corresponding layers
27:Comprehensive computer networking implementation
509:"The OSI Model, Part 10. The Application Layer"
8:
386:constitutes a spanning layer that defines a
219:. Examples of these interfaces include
471:
563:
553:
151:protocol is required to connect them.
382:In the Internet protocol stack, the
215:transport software would talk to the
7:
436:Recursive Internetwork Architecture
267:The network protocol stack used by
426:Hierarchical internetworking model
96:General protocol suite description
25:
507:Georg N. Strauß (2010-01-09).
482:. WEBOPEDIA. 24 September 1997
406:based on this spanning layer.
1:
540:. National Research Council.
456:Wireless Application Protocol
511:. Ika-Reutte. Archived from
451:Systems Network Architecture
217:network interface controller
480:"What is a protocol stack?"
167:to send a chunk of data to
603:
103:Imagine three computers:
68:is the definition of the
416:Cross-layer optimization
80:implementation of them.
446:Signalling System No. 7
384:Internet Protocol Suite
255:for Microsoft Windows.
137:Point-to-Point Protocol
70:communication protocols
390:for global routing of
380:
271:
163:A request on computer
100:T ~ ~ ~ T _____
38:
34:Protocol stack of the
371:
266:
175:is reachable through
33:
536:David Clark (1997).
402:is the community of
493:OSI Reference Model
388:best-effort service
366:, a term coined by
276:
55:computer networking
274:
272:
251:environments, and
207:associated with a
39:
587:Network protocols
355:
354:
229:Microsoft Windows
157:Internet Protocol
16:(Redirected from
594:
572:
571:
565:
561:
559:
551:
533:
527:
526:
521:
520:
504:
498:
497:
488:
487:
476:
277:
241:Berkeley sockets
204:operating system
21:
18:Networking stack
602:
601:
597:
596:
595:
593:
592:
591:
577:
576:
575:
562:
552:
548:
535:
534:
530:
518:
516:
506:
505:
501:
485:
483:
478:
477:
473:
469:
412:
360:
261:
101:
98:
62:protocol family
28:
23:
22:
15:
12:
11:
5:
600:
598:
590:
589:
579:
578:
574:
573:
546:
528:
499:
470:
468:
465:
464:
463:
458:
453:
448:
443:
438:
433:
428:
423:
418:
411:
408:
404:interoperation
376:spanning layer
364:spanning layer
359:
358:Spanning layer
356:
353:
352:
347:
341:
340:
331:
325:
324:
315:
309:
308:
303:
297:
296:
291:
285:
284:
281:
269:Amiga software
260:
257:
99:
97:
94:
85:modularization
58:protocol suite
51:implementation
43:protocol stack
26:
24:
14:
13:
10:
9:
6:
4:
3:
2:
599:
588:
585:
584:
582:
569:
557:
549:
547:9780309060363
543:
539:
532:
529:
525:
515:on 2012-03-20
514:
510:
503:
500:
496:
494:
481:
475:
472:
466:
462:
459:
457:
454:
452:
449:
447:
444:
442:
441:Service layer
439:
437:
434:
432:
431:Protocol Wars
429:
427:
424:
422:
419:
417:
414:
413:
409:
407:
405:
401:
397:
393:
389:
385:
379:
377:
370:
369:
365:
357:
351:
348:
346:
343:
342:
339:
335:
332:
330:
327:
326:
323:
319:
316:
314:
311:
310:
307:
304:
302:
299:
298:
295:
292:
290:
287:
286:
282:
279:
278:
270:
265:
258:
256:
254:
250:
246:
243:and System V
242:
238:
234:
230:
226:
222:
218:
214:
210:
209:device driver
205:
200:
198:
194:
190:
186:
182:
178:
174:
170:
166:
161:
158:
152:
150:
149:inter-network
146:
142:
138:
134:
130:
126:
122:
118:
114:
110:
106:
95:
93:
90:
86:
81:
79:
75:
71:
67:
63:
59:
56:
52:
48:
47:network stack
44:
37:
32:
19:
537:
531:
523:
517:. Retrieved
513:the original
502:
490:
484:. Retrieved
474:
381:
375:
372:
363:
361:
345:IEEE 802.3ab
201:
196:
192:
188:
184:
180:
176:
172:
168:
164:
162:
153:
144:
140:
132:
128:
120:
116:
112:
108:
104:
102:
82:
73:
65:
61:
57:
46:
42:
40:
564:|work=
368:David Clark
294:Application
237:web browser
125:IEEE 802.11
519:2010-02-21
486:2010-02-21
467:References
155:them (the
72:, and the
566:ignored (
556:cite book
392:datagrams
338:data link
306:Transport
280:Protocol
249:Unix-like
36:OSI model
581:Category
410:See also
400:Internet
350:Physical
329:Ethernet
318:Internet
259:Examples
78:software
396:Layer 3
322:network
253:Winsock
245:STREAMS
227:in the
76:is the
544:
421:DECnet
398:. The
283:Layer
213:TCP/IP
111:, and
89:layers
49:is an
74:stack
66:suite
53:of a
568:help
542:ISBN
461:X.25
334:Link
289:HTTP
231:and
225:NDIS
223:and
131:and
119:and
41:The
394:at
336:or
320:or
301:TCP
247:in
233:DOS
221:ODI
143:to
127:).
60:or
45:or
583::
560::
558:}}
554:{{
522:.
489:.
313:IP
199:.
115:.
107:,
570:)
550:.
197:C
193:C
189:C
185:B
181:B
177:B
173:C
169:C
165:A
145:C
141:A
133:C
129:B
121:B
117:A
113:C
109:B
105:A
20:)
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.
