Модел TCP/IP. - Revision history

Anko: /* */

2013-01-09T15:30:30Z

Anko at 15:28, 9 January 2013

2013-01-09T15:28:45Z

Anko at 15:28, 9 January 2013

2013-01-09T15:28:04Z

Anko: /* Слоеве */

2013-01-09T15:23:40Z

Слоеве

Anko: /* Теминология */

2013-01-09T15:08:21Z

Теминология

Anko: /* Теминология */

2013-01-09T15:07:54Z

Теминология

Anko: /* Теминология */

2013-01-09T15:00:17Z

Теминология

Anko: /* Представяне */

2013-01-09T14:39:58Z

Представяне

Anko: /* Представяне */

2013-01-09T14:16:45Z

Представяне

Anko at 14:12, 9 January 2013

2013-01-09T14:12:47Z

@@ Line 168: / Line 168: @@
 RFC 1122, entitled Host Requirements, is structured in paragraphs referring to layers, but the document refers to many other architectural principles not emphasizing layering. It loosely defines a four-layer model, with the layers having names, not numbers, as follows:
 The Internet protocol suite and the layered protocol stack design were in use before the OSI model was established. Since then, the TCP/IP model has been compared with the OSI model in books and classrooms, which often results in confusion because the two models use different assumptions, including about the relative importance of strict layering.
@@ Line 175: / Line 174: @@
 This model lacks the formalism of the OSI model and associated documents, but the IETF does not use a formal model and does not consider this a limitation, as in the comment by David D. Clark, "We reject: kings, presidents and voting. We believe in: rough consensus and running code." Criticisms of this model, which have been made with respect to the OSI model, often do not consider ISO's later extensions to that model.
-For multiaccess links with their own addressing systems (e.g. Ethernet) an address mapping protocol is needed. Such protocols can be considered to be below IP but above the existing link system. While the IETF does not use the terminology, this is a subnetwork dependent convergence facility according to an extension to the OSI model, the internal organization of the network layer (IONL).[16]
+For multiaccess links with their own addressing systems (e.g. Ethernet) an address mapping protocol is needed. Such protocols can be considered to be below IP but above the existing link system. While the IETF does not use the terminology, this is a subnetwork dependent convergence facility according to an extension to the OSI model, the internal organization of the network layer (IONL).
-ICMP & IGMP operate on top of IP but do not transport data like UDP or TCP. Again, this functionality exists as layer management extensions to the OSI model, in its Management Framework (OSIRM MF) [17]
+ICMP & IGMP operate on top of IP but do not transport data like UDP or TCP. Again, this functionality exists as layer management extensions to the OSI model, in its Management Framework (OSIRM MF).
 The SSL/TLS library operates above the transport layer (uses TCP) but below application protocols. Again, there was no intention, on the part of the designers of these protocols, to comply with OSI architecture.

@@ Line 212: / Line 212: @@
 *Internet Protocol version 6 (IPv6) in 1998, and beginning production implementations in approximately 2006.
-===Transport layer===
+==Transport layer==
 Транспортният слой създава свързаност от хост до хост. Той се занимава с доставката на данни независимо от тяхната структура и техния маршрут.
@@ Line 246: / Line 246: @@
-===Application layer===
+==Application layer==
 The application layer contains the higher-level protocols used by most applications for network communication. Examples of application layer protocols include the File Transfer Protocol (FTP) and the Simple Mail Transfer Protocol (SMTP). Data coded according to application layer protocols are then encapsulated into one or (occasionally) more transport layer protocols (such as TCP or UDP), which in turn use lower layer protocols to effect actual data transfer.

@@ Line 168: / Line 168: @@
 RFC 1122, entitled Host Requirements, is structured in paragraphs referring to layers, but the document refers to many other architectural principles not emphasizing layering. It loosely defines a four-layer model, with the layers having names, not numbers, as follows:
 == ==
 The Internet protocol suite and the layered protocol stack design were in use before the OSI model was established. Since then, the TCP/IP model has been compared with the OSI model in books and classrooms, which often results in confusion because the two models use different assumptions, including about the relative importance of strict layering.
-This abstraction also allows upper layers to provide services that the lower layers cannot, or choose not, to provide. Again, the original OSI model was extended to include connectionless services (OSIRM CL).[15] For example, IP is not designed to be reliable and is a best effort delivery protocol. This means that all transport layer implementations must choose whether or not to provide reliability and to what degree. UDP provides data integrity (via a checksum) but does not guarantee delivery; TCP provides both data integrity and delivery guarantee (by retransmitting until the receiver acknowledges the reception of the packet).
+This abstraction also allows upper layers to provide services that the lower layers cannot, or choose not, to provide. Again, the original OSI model was extended to include connectionless services (OSIRM CL).For example, IP is not designed to be reliable and is a best effort delivery protocol. This means that all transport layer implementations must choose whether or not to provide reliability and to what degree. UDP provides data integrity (via a checksum) but does not guarantee delivery; TCP provides both data integrity and delivery guarantee (by retransmitting until the receiver acknowledges the reception of the packet).
 This model lacks the formalism of the OSI model and associated documents, but the IETF does not use a formal model and does not consider this a limitation, as in the comment by David D. Clark, "We reject: kings, presidents and voting. We believe in: rough consensus and running code." Criticisms of this model, which have been made with respect to the OSI model, often do not consider ISO's later extensions to that model.

@@ Line 146: / Line 146: @@
                      <--------  Datagram ------------------>
                               <-------- Segment ----------->
 ==Слоеве==

@@ Line 127: / Line 127: @@
            | LL hdr | IP hdr |         (data)              |
            |________|________|_____________________________|
-−
             <---------- Frame ----------------------------->
                      <----------Packet -------------------->
@@ Line 136: / Line 136: @@
                     | IP hdr | transport| Application Data |
                     |________|____hdr___|__________________|
-−
                      <--------  Datagram ------------------>
                               <-------- Message ----------->
@@ Line 143: / Line 143: @@
                     | IP hdr |  TCP hdr | Application Data |
                     |________|__________|__________________|
-−
                      <--------  Datagram ------------------>
                               <-------- Segment ----------->

@@ Line 81: / Line 81: @@
 *Frame (фрейм, кадър)
-Фрейм е Транспортна единица за предаване на данни в каналното ниво           A frame is the unit of transmission in a link layer
+Фрейм е Транспортна единица за предаване на данни в каналното ниво. Съставена е от служебна информация на каналното ниво, следвана от пакет.
-         Connected Network
+*Connected Network
-              A network to which a host is interfaced is often known as
+network to which a host is interfaced is often known as
-              the "local network" or the "subnetwork" relative to that
+the "local network" or the "subnetwork" relative to that
-              host.  However, these terms can cause confusion, and
+host.  However, these terms can cause confusion, and
-              therefore we use the term "connected network" in this
+therefore we use the term "connected network" in this
-              document.
+document.
-         Multihomed
+*Multihomed
-              A host is said to be multihomed if it has multiple IP
+Даден хост е multihomed, ако има няколко IP адреса
-         Physical network interface
+*Physical network interface физически интерфейс
-              This is a physical interface to a connected network and
+This is a physical interface to a connected network and
-              has a (possibly unique) link-layer address.  Multiple
+has a (possibly unique) link-layer address.  Multiple
-              physical network interfaces on a single host may share the
+physical network interfaces on a single host may share the
-              same link-layer address, but the address must be unique
+same link-layer address, but the address must be unique
-              for different hosts on the same physical network.
+for different hosts on the same physical network.
-         Logical [network] interface
+*Logical [network] interface
-              We define a logical [network] interface to be a logical
+We define a logical [network] interface to be a logical
-              path, distinguished by a unique IP address, to a connected
+path, distinguished by a unique IP address, to a connected
-              network.  See Section 3.3.4.
+нetwork.  See Section 3.3.4.
-Internet Engineering Task Force                                [Page 18]
+*MTU
+The maximum transmission unit, i.e., the size of the
-RFC1122                       INTRODUCTION                  October 1989
+largest packet that can be transmitted.
-         Specific-destination address
+Transmission on connected network:
             _______________________________________________
            | LL hdr | IP hdr |         (data)              |
@@ Line 146: / Line 132: @@
-         B. Before IP fragmentation or after IP reassembly:
+Before IP fragmentation or after IP reassembly:
                      ______________________________________
                     | IP hdr | transport| Application Data |
@@ Line 153: / Line 139: @@
                      <--------  Datagram ------------------>
                               <-------- Message ----------->
-           or, for TCP:
+за TCP:
                      ______________________________________
                     | IP hdr |  TCP hdr | Application Data |

@@ Line 75: / Line 75: @@
 *IP Datagram
-              An IP datagram is the unit of end-to-end transmission in
+Транспортна единица с данни за предаване от крайна точка до крайна точка в IP протокола.  Съдържа IP служебна информация (хедър - header) следвана от данните на транспортното ниво (IP header следван от message). Ако няма други пояснения под datagram трябва се разбира IP datagram
-              In the description of the internet layer (Section 3), the
+*Packet (пакет)
-              unqualified term "datagram" should be understood to refer
+Транспортна единица с данни, която се изпраща между Internet слоя и каналния слой. Съдържа IP служебна информация (header) и данни. Пакета може да е цяла IP datagram или част от IP datagram.
-         Packet
+*Frame (фрейм, кадър)
-              A packet is the unit of data passed across the interface
+Фрейм е Транспортна единица за предаване на данни в каналното ниво           A frame is the unit of transmission in a link layer
                protocol, and consists of a link-layer header followed by
                a packet.

@@ Line 32: / Line 32: @@
 ==Представяне==
 <code><pre>
   ----------------------------
@@ Line 55: / Line 58: @@
               Ethernet Cable
-                  Figure 1.  Basic TCP/IP Network Node
+о - приемо-предавател
 </pre></code>
-Всеки компютър, който е свързан в Интернет работи по таза логическа структура.
+==Теминология==
 ==Слоеве==

← Older revision		Revision as of 14:16, 9 January 2013
Line 58:		Line 58:
	</pre></code>		</pre></code>

		+	Всеки компютър, който е свързан в Интернет работи по таза логическа структура.

	==Слоеве==		==Слоеве==

@@ Line 1: / Line 1: @@
-Какво с TCP/IP?
+==Какво е TCP/IP==
-TCP/IP протоколния стек включва протоколи използвани при комуникация в Интернет и подобни мрежи и е най разпространения при изграждане на WAN мрежи. Нарича се TCP/IP, защото това са най важните протоколи и са първите дефинирани в стандарта
+TCP/IP включва множество от протоколи използвани при комуникация в Интернет и подобни мрежи. TCP/IP е най-разпространения протоколен стек при изграждане на WAN мрежи. Нарича се TCP/IP, защото това са най-важните протоколи и са първите, които са били описани.
-TCP/IP осигурява връзка от край до край и дефинира как данните трябва да се форматират, адресират изпратят, маршрутизират и приемат в крайната точка.
+TCP/IP осигурява връзка от край до край и определя как данните трябва да се форматират, адресират изпратят, маршрутизират и приемат в крайната точка.
-TCP/IP модела включва следните четири нива:
+TCP/IP модела се разделя на четири логически нива:
-*Application – Приложно – На това ниво работят различните програми за мрежов достъп. Такива са програми за електронна поща, за обмен на данни, WWW.
+*Application – Приложно
 *Transport Layer – Транспортно
 *Internet Layer - Интенет
 *Network Layer – Мрежово
 ===Приложен слой===
@@ Line 33: / Line 30: @@
 *през 1989 AT&T дава за свободно ползване TCP/IP кода разработен за UNIX. В последствие различни производители го интегрират в собствените си системи
 *Many companies sold TCP/IP stacks for Windows until Microsoft released its own TCP/IP stack in Windows 95. This event was a little late in the evolution of the Internet, but it cemented TCP/IP's dominance over other protocols, which eventually disappeared.
 ==Слоеве==