Jump to content

Examine individual changes

This page allows you to examine the variables generated by the Edit Filter for an individual change.

Variables generated for this change

VariableValue
Edit count of the user (user_editcount)
12488
Name of the user account (user_name)
'Daviddwd'
Age of the user account (user_age)
253329481
Groups (including implicit) the user is in (user_groups)
[ 0 => 'extendedconfirmed', 1 => '*', 2 => 'user', 3 => 'autoconfirmed' ]
Rights that the user has (user_rights)
[ 0 => 'extendedconfirmed', 1 => 'createaccount', 2 => 'read', 3 => 'edit', 4 => 'createtalk', 5 => 'writeapi', 6 => 'viewmywatchlist', 7 => 'editmywatchlist', 8 => 'viewmyprivateinfo', 9 => 'editmyprivateinfo', 10 => 'editmyoptions', 11 => 'abusefilter-log-detail', 12 => 'centralauth-merge', 13 => 'abusefilter-view', 14 => 'abusefilter-log', 15 => 'vipsscaler-test', 16 => 'collectionsaveasuserpage', 17 => 'reupload-own', 18 => 'move-rootuserpages', 19 => 'createpage', 20 => 'minoredit', 21 => 'editmyusercss', 22 => 'editmyuserjson', 23 => 'editmyuserjs', 24 => 'purge', 25 => 'sendemail', 26 => 'applychangetags', 27 => 'spamblacklistlog', 28 => 'mwoauthmanagemygrants', 29 => 'reupload', 30 => 'upload', 31 => 'move', 32 => 'collectionsaveascommunitypage', 33 => 'autoconfirmed', 34 => 'editsemiprotected', 35 => 'movestable', 36 => 'autoreview', 37 => 'skipcaptcha', 38 => 'transcode-reset', 39 => 'createpagemainns' ]
Whether the user is editing from mobile app (user_app)
false
Whether or not a user is editing through the mobile interface (user_mobile)
false
user_wpzero
false
Page ID (page_id)
41591
Page namespace (page_namespace)
0
Page title without namespace (page_title)
'Protocol data unit'
Full page title (page_prefixedtitle)
'Protocol data unit'
Action (action)
'edit'
Edit summary/reason (summary)
'Talking about fragmentation'
Old content model (old_content_model)
'wikitext'
New content model (new_content_model)
'wikitext'
Old page wikitext, before the edit (old_wikitext)
'{{Short description|Unit of information transmitted between peer entities (at the same layer) of a computer network}} {{Use American English|date = March 2019}} {{Use mdy dates|date = March 2019}} [[Image:Pdu and sdu.svg|thumb|350px|[[Medium access control]] (MAC) layer protocol data unit (PDU) becomes [[physical layer]] [[service data unit]] (SDU).]] In [[telecommunication]]s, a '''protocol data unit''' ('''PDU''') is a single unit of information transmitted among peer entities of a [[computer network]]. A PDU is composed of protocol specific control information and [[Payload (computing)|user data]]. In the layered architectures of [[communication protocol]] stacks, each layer implements protocols tailored to the specific type or mode of data exchange. For example, the [[Transmission Control Protocol]] (TCP) implements a connection-oriented transfer mode, and the PDU of this protocol is called a ''segment'', while the [[User Datagram Protocol]] (UDP) uses [[datagram]]s as protocol data unit for connection-less transfer. A layer lower in the [[Internet protocol suite]], at the [[Internet layer]], the PDU is called a [[network packet|packet]], irrespective of its payload type. ==Packet-switched data networks== {{refimprove section|date=April 2012}} In the context of [[packet switching]] data networks, a protocol data unit (PDU) is best understood in relation to a [[service data unit]] (SDU). The features or services of the network are implemented in distinct "layers". For example, sending ones and zeros across a wire, fiber, etc. is done by the physical layer, organizing the ones and zeros into chunks of data and getting them safely to the right place on the wire is done by the data link layer, passing data chunks over multiple connected networks is done by the network layer and delivery of the data to the right software application at the destination is done by the transport layer. Between the layers (and between the application and the top-most layer), the layers pass service data units across the interfaces. The higher layer understands the structure of the data in the SDU, but the lower layer at the interface does not; the lower layer treats the SDU as [[Payload (computing)|payload]], undertaking to get it to the same interface at the destination. In order to do this, the ''protocol'' (lower) layer will add to the SDU certain data it needs to perform its function. For example, it might add a port number to identify the application, a network address to help with routing, a code to identify the type of data in the packet and error-checking information. All this additional information, plus the original service data unit from the higher layer, constitutes the ''protocol data unit'' at this layer. The significance of this is that the PDU is the structured information that is passed to a matching protocol layer further along on the data's journey that allows the layer to deliver its intended function or service. The matching layer, or "peer", decodes the data to extract the original service data unit, decide if it is error-free and where to send it next, etc. Unless we have already arrived at the lowest (physical) layer, the PDU is passed to the peer using services of the next lower layer in the protocol "stack". When the PDU passes over the interface from the layer that constructed it to the layer that merely delivers it (and therefore does not understand its internal structure), it becomes a service data unit to that layer. The addition of addressing and control information (which is called encapsulation) to an SDU to form a PDU and the passing of that PDU to the next lower layer as an SDU repeats until the lowest layer is reached and the data passes over some medium as a physical signal. The above process can be likened to the mail system in which a letter (SDU) is placed in an envelope on which is written an address (addressing and control information) making it a PDU. The sending post office might look only at the post code and place the letter in a mail bag so that the address on the envelope can no longer be seen, making it now an SDU. The mail bag is labelled with the destination post code and so becomes a PDU, until it is combined with other bags in a crate, when it is now an SDU, and the crate is labelled with the region to which all the bags are to be sent, making the crate a PDU. When the crate reaches the destination matching its label, it is opened and the bags (SDUs) removed only to become PDUs when someone reads the code of the destination post office. The letters themselves are SDUs when the bags are opened but become PDUs when the address is read for final delivery. When the addressee finally opens the envelope, the top-level SDU, the letter itself, emerges. ==Examples== ===OSI model=== Protocol data units of the [[OSI model]] are:<ref>{{cite web |url=http://www.tcpipguide.com/free/t_DataEncapsulationProtocolDataUnitsPDUsandServiceDa.htm |title=Data Encapsulation, Protocol Data Units (PDUs) and Service Data Units (SDUs) |work=The TCP/IP Guide |accessdate=2012-04-05}}</ref> *The Layer 4: [[transport layer]] PDU is the [[Packet segment|segment]] or the [[datagram]]. *The Layer 3: [[network layer]] PDU is the [[Network packet|packet]]. *The Layer 2: [[data link layer]] PDU is the [[Frame (networking)|frame]]. *The Layer 1: [[physical layer]] PDU is the [[bit]] or, more generally, [[Symbol (data)|symbol]]. Given a context pertaining to a specific OSI layer, ''PDU'' is sometimes used as a synonym for its representation at that layer. ===Internet protocol suite=== Protocol data units for the [[Internet protocol suite]] are: *The [[transport layer]] PDU is the [[TCP segment]] for TCP, and the [[datagram]] for UDP. *The [[Internet layer]] PDU is the [[Network packet|packet]]. *The [[link layer]] PDU is the [[Frame (networking)|frame]]. On TCP/IP over Ethernet, the data on the physical layer is carried in [[Ethernet frame]]s. ===ATM=== [[Asynchronous transfer mode|ATM]]'s corresponding data link layer PDU is called a ''cell''. {{anchor|MPDU}} ===Media access control protocol data unit=== A '''media access control protocol data unit''' ('''MPDU''') is a message that is exchanged between [[media access control]] (MAC) entities in a communication system based on the layered [[OSI model]]. In systems where the MPDU may be larger than the [[MAC service data unit]] (MSDU), the MPDU may ''include'' multiple MSDUs as a result of [[packet aggregation]]. In systems where the MPDU is smaller than the MSDU, then one MSDU may ''generate'' multiple MPDUs as a result of [[packet segmentation]].<!--[[User:Kvng/RTH]]--> {{anchor|TPDU}} ===Transport protocol data unit=== {{expandsection|date=July 2017}} '''Transport protocol data unit''' ('''TPDU''') is a message [[Encapsulation (networking)|encapsulation]] format with several [[byte]]s of routing [[Header (computing)|header]] added to the front of the [[Payload (computing)|payload]] message. The processing [[Overhead (computing)|overhead]] of the TPDU has two components: the overhead TPDU and the overhead per byte. ==See also== * [[Distributed Interactive Simulation#Protocol data units|Distributed Interactive Simulation protocol data unit]] * [[Frame (networking)]] * [[MAC service data unit]] * [[Smart card application protocol data unit]] ==References== {{reflist}} == External links == * [http://www.cl.cam.ac.uk/~mgk25/osi-faq.txt comp.protocols.iso FAQ] (search for "PDU") [[Category:Data transmission]] [[Category:Packets (information technology)]]'
New page wikitext, after the edit (new_wikitext)
'{{Short description|Unit of information transmitted between peer entities (at the same layer) of a computer network}} {{Use American English|date = March 2019}} {{Use mdy dates|date = March 2019}} [[Image:Pdu and sdu.svg|thumb|350px|[[Medium access control]] (MAC) layer protocol data unit (PDU) becomes [[physical layer]] [[service data unit]] (SDU).]] In [[telecommunication]]s, a '''protocol data unit''' ('''PDU''') is a single unit of information transmitted among peer entities of a [[computer network]]. A PDU is composed of protocol specific control information and [[Payload (computing)|user data]]. In the layered architectures of [[communication protocol]] stacks, each layer implements protocols tailored to the specific type or mode of data exchange. For example, the [[Transmission Control Protocol]] (TCP) implements a connection-oriented transfer mode, and the PDU of this protocol is called a ''segment'', while the [[User Datagram Protocol]] (UDP) uses [[datagram]]s as protocol data unit for connection-less transfer. A layer lower in the [[Internet protocol suite]], at the [[Internet layer]], the PDU is called a [[network packet|packet]], irrespective of its payload type. ==Packet-switched data networks== {{refimprove section|date=April 2012}} In the context of [[packet switching]] data networks, a protocol data unit (PDU) is best understood in relation to a [[service data unit]] (SDU). The features or services of the network are implemented in distinct "layers". For example, sending ones and zeros across a wire, fiber, etc. is done by the physical layer, organizing the ones and zeros into chunks of data and getting them safely to the right place on the wire is done by the data link layer, passing data chunks over multiple connected networks is done by the network layer and delivery of the data to the right software application at the destination is done by the transport layer. Between the layers (and between the application and the top-most layer), the layers pass service data units across the interfaces. The higher layer understands the structure of the data in the SDU, but the lower layer at the interface does not; the lower layer treats the SDU as [[Payload (computing)|payload]], undertaking to get it to the same interface at the destination. In order to do this, the ''protocol'' (lower) layer will add to the SDU certain data it needs to perform its function; which is called [[Encapsulation (networking)|encapsulation]]. For example, it might add a port number to identify the application, a network address to help with routing, a code to identify the type of data in the packet and error-checking information. All this additional information, plus the original service data unit from the higher layer, constitutes the ''protocol data unit'' at this layer. The SDU and metadata added by the lower layer can be larger than the maximum size of that layer's PDU (known as the [[maximum transmission unit]]; MTU). When this is the case, the SDU must be split into multiple payloads of size suitable for transmission or processing by the lower later; a process known as [[IP fragmentation]]. The significance of this is that the PDU is the structured information that is passed to a matching protocol layer further along on the data's journey that allows the layer to deliver its intended function or service. The matching layer, or "peer", decodes the data to extract the original service data unit, decide if it is error-free and where to send it next, etc. Unless we have already arrived at the lowest (physical) layer, the PDU is passed to the peer using services of the next lower layer in the protocol "stack". When the PDU passes over the interface from the layer that constructed it to the layer that merely delivers it (and therefore does not understand its internal structure), it becomes a service data unit to that layer. The addition of addressing and control information ([[Encapsulation (networking)|encapsulation]]) to an SDU to form a PDU and the passing of that PDU to the next lower layer as an SDU repeats until the lowest layer is reached and the data passes over some medium as a physical signal. The above process can be likened to the mail system in which a letter (SDU) is placed in an envelope on which is written an address (addressing and control information) making it a PDU. The sending post office might look only at the post code and place the letter in a mail bag so that the address on the envelope can no longer be seen, making it now an SDU. The mail bag is labelled with the destination post code and so becomes a PDU, until it is combined with other bags in a crate, when it is now an SDU, and the crate is labelled with the region to which all the bags are to be sent, making the crate a PDU. When the crate reaches the destination matching its label, it is opened and the bags (SDUs) removed only to become PDUs when someone reads the code of the destination post office. The letters themselves are SDUs when the bags are opened but become PDUs when the address is read for final delivery. When the addressee finally opens the envelope, the top-level SDU, the letter itself, emerges. ==Examples== ===OSI model=== Protocol data units of the [[OSI model]] are:<ref>{{cite web |url=http://www.tcpipguide.com/free/t_DataEncapsulationProtocolDataUnitsPDUsandServiceDa.htm |title=Data Encapsulation, Protocol Data Units (PDUs) and Service Data Units (SDUs) |work=The TCP/IP Guide |accessdate=2012-04-05}}</ref> *The Layer 4: [[transport layer]] PDU is the [[Packet segment|segment]] or the [[datagram]]. *The Layer 3: [[network layer]] PDU is the [[Network packet|packet]]. *The Layer 2: [[data link layer]] PDU is the [[Frame (networking)|frame]]. *The Layer 1: [[physical layer]] PDU is the [[bit]] or, more generally, [[Symbol (data)|symbol]]. Given a context pertaining to a specific OSI layer, ''PDU'' is sometimes used as a synonym for its representation at that layer. When the PDU of one layer (''n''), sent as SDU to the layer one lower than it (''n-1''), plus any metadata ([[Header (computing)|headers]]/[[Trailer (computing)|trailers]]) layer ''n-1'' adds to the SDU would exceed the largest size layer ''n-1''<nowiki/>'s PDU can be, it must be broken up into multiple payloads to fit in the layer-''n-1'' PDU's. This process is called [[IP fragmentation]]. ===Internet protocol suite=== Protocol data units for the [[Internet protocol suite]] are: *The [[transport layer]] PDU is the [[TCP segment]] for TCP, and the [[datagram]] for UDP. *The [[Internet layer]] PDU is the [[Network packet|packet]]. *The [[link layer]] PDU is the [[Frame (networking)|frame]]. On TCP/IP over Ethernet, the data on the physical layer is carried in [[Ethernet frame]]s. ===ATM=== [[Asynchronous transfer mode|ATM]]'s corresponding data link layer PDU is called a ''cell''. {{anchor|MPDU}} ===Media access control protocol data unit=== A '''media access control protocol data unit''' ('''MPDU''') is a message that is exchanged between [[media access control]] (MAC) entities in a communication system based on the layered [[OSI model]]. In systems where the MPDU may be larger than the [[MAC service data unit]] (MSDU), the MPDU may ''include'' multiple MSDUs as a result of [[packet aggregation]]. In systems where the MPDU is smaller than the MSDU, then one MSDU may ''generate'' multiple MPDUs as a result of [[packet segmentation]].<!--[[User:Kvng/RTH]]--> {{anchor|TPDU}} ===Transport protocol data unit=== {{expandsection|date=July 2017}} '''Transport protocol data unit''' ('''TPDU''') is a message [[Encapsulation (networking)|encapsulation]] format with several [[byte]]s of routing [[Header (computing)|header]] added to the front of the [[Payload (computing)|payload]] message. The processing [[Overhead (computing)|overhead]] of the TPDU has two components: the overhead TPDU and the overhead per byte. ==See also== * [[Distributed Interactive Simulation#Protocol data units|Distributed Interactive Simulation protocol data unit]] * [[Frame (networking)]] * [[MAC service data unit]] * [[Smart card application protocol data unit]] *[[IP fragmentation]] ==References== {{reflist}} == External links == * [http://www.cl.cam.ac.uk/~mgk25/osi-faq.txt comp.protocols.iso FAQ] (search for "PDU") [[Category:Data transmission]] [[Category:Packets (information technology)]]'
Unified diff of changes made by edit (edit_diff)
'@@ -15,5 +15,9 @@ The features or services of the network are implemented in distinct "layers". For example, sending ones and zeros across a wire, fiber, etc. is done by the physical layer, organizing the ones and zeros into chunks of data and getting them safely to the right place on the wire is done by the data link layer, passing data chunks over multiple connected networks is done by the network layer and delivery of the data to the right software application at the destination is done by the transport layer. -Between the layers (and between the application and the top-most layer), the layers pass service data units across the interfaces. The higher layer understands the structure of the data in the SDU, but the lower layer at the interface does not; the lower layer treats the SDU as [[Payload (computing)|payload]], undertaking to get it to the same interface at the destination. In order to do this, the ''protocol'' (lower) layer will add to the SDU certain data it needs to perform its function. For example, it might add a port number to identify the application, a network address to help with routing, a code to identify the type of data in the packet and error-checking information. All this additional information, plus the original service data unit from the higher layer, constitutes the ''protocol data unit'' at this layer. The significance of this is that the PDU is the structured information that is passed to a matching protocol layer further along on the data's journey that allows the layer to deliver its intended function or service. The matching layer, or "peer", decodes the data to extract the original service data unit, decide if it is error-free and where to send it next, etc. Unless we have already arrived at the lowest (physical) layer, the PDU is passed to the peer using services of the next lower layer in the protocol "stack". When the PDU passes over the interface from the layer that constructed it to the layer that merely delivers it (and therefore does not understand its internal structure), it becomes a service data unit to that layer. The addition of addressing and control information (which is called encapsulation) to an SDU to form a PDU and the passing of that PDU to the next lower layer as an SDU repeats until the lowest layer is reached and the data passes over some medium as a physical signal. +Between the layers (and between the application and the top-most layer), the layers pass service data units across the interfaces. The higher layer understands the structure of the data in the SDU, but the lower layer at the interface does not; the lower layer treats the SDU as [[Payload (computing)|payload]], undertaking to get it to the same interface at the destination. In order to do this, the ''protocol'' (lower) layer will add to the SDU certain data it needs to perform its function; which is called [[Encapsulation (networking)|encapsulation]]. For example, it might add a port number to identify the application, a network address to help with routing, a code to identify the type of data in the packet and error-checking information. All this additional information, plus the original service data unit from the higher layer, constitutes the ''protocol data unit'' at this layer. + +The SDU and metadata added by the lower layer can be larger than the maximum size of that layer's PDU (known as the [[maximum transmission unit]]; MTU). When this is the case, the SDU must be split into multiple payloads of size suitable for transmission or processing by the lower later; a process known as [[IP fragmentation]]. + +The significance of this is that the PDU is the structured information that is passed to a matching protocol layer further along on the data's journey that allows the layer to deliver its intended function or service. The matching layer, or "peer", decodes the data to extract the original service data unit, decide if it is error-free and where to send it next, etc. Unless we have already arrived at the lowest (physical) layer, the PDU is passed to the peer using services of the next lower layer in the protocol "stack". When the PDU passes over the interface from the layer that constructed it to the layer that merely delivers it (and therefore does not understand its internal structure), it becomes a service data unit to that layer. The addition of addressing and control information ([[Encapsulation (networking)|encapsulation]]) to an SDU to form a PDU and the passing of that PDU to the next lower layer as an SDU repeats until the lowest layer is reached and the data passes over some medium as a physical signal. The above process can be likened to the mail system in which a letter (SDU) is placed in an envelope on which is written an address (addressing and control information) making it a PDU. The sending post office might look only at the post code and place the letter in a mail bag so that the address on the envelope can no longer be seen, making it now an SDU. The mail bag is labelled with the destination post code and so becomes a PDU, until it is combined with other bags in a crate, when it is now an SDU, and the crate is labelled with the region to which all the bags are to be sent, making the crate a PDU. When the crate reaches the destination matching its label, it is opened and the bags (SDUs) removed only to become PDUs when someone reads the code of the destination post office. The letters themselves are SDUs when the bags are opened but become PDUs when the address is read for final delivery. When the addressee finally opens the envelope, the top-level SDU, the letter itself, emerges. @@ -29,4 +33,6 @@ Given a context pertaining to a specific OSI layer, ''PDU'' is sometimes used as a synonym for its representation at that layer. + +When the PDU of one layer (''n''), sent as SDU to the layer one lower than it (''n-1''), plus any metadata ([[Header (computing)|headers]]/[[Trailer (computing)|trailers]]) layer ''n-1'' adds to the SDU would exceed the largest size layer ''n-1''<nowiki/>'s PDU can be, it must be broken up into multiple payloads to fit in the layer-''n-1'' PDU's. This process is called [[IP fragmentation]]. ===Internet protocol suite=== @@ -61,4 +67,5 @@ * [[MAC service data unit]] * [[Smart card application protocol data unit]] +*[[IP fragmentation]] ==References== '
New page size (new_size)
8396
Old page size (old_size)
7571
Size change in edit (edit_delta)
825
Lines added in edit (added_lines)
[ 0 => 'Between the layers (and between the application and the top-most layer), the layers pass service data units across the interfaces. The higher layer understands the structure of the data in the SDU, but the lower layer at the interface does not; the lower layer treats the SDU as [[Payload (computing)|payload]], undertaking to get it to the same interface at the destination. In order to do this, the ''protocol'' (lower) layer will add to the SDU certain data it needs to perform its function; which is called [[Encapsulation (networking)|encapsulation]]. For example, it might add a port number to identify the application, a network address to help with routing, a code to identify the type of data in the packet and error-checking information. All this additional information, plus the original service data unit from the higher layer, constitutes the ''protocol data unit'' at this layer.', 1 => '', 2 => 'The SDU and metadata added by the lower layer can be larger than the maximum size of that layer's PDU (known as the [[maximum transmission unit]]; MTU). When this is the case, the SDU must be split into multiple payloads of size suitable for transmission or processing by the lower later; a process known as [[IP fragmentation]].', 3 => '', 4 => 'The significance of this is that the PDU is the structured information that is passed to a matching protocol layer further along on the data's journey that allows the layer to deliver its intended function or service. The matching layer, or "peer", decodes the data to extract the original service data unit, decide if it is error-free and where to send it next, etc. Unless we have already arrived at the lowest (physical) layer, the PDU is passed to the peer using services of the next lower layer in the protocol "stack". When the PDU passes over the interface from the layer that constructed it to the layer that merely delivers it (and therefore does not understand its internal structure), it becomes a service data unit to that layer. The addition of addressing and control information ([[Encapsulation (networking)|encapsulation]]) to an SDU to form a PDU and the passing of that PDU to the next lower layer as an SDU repeats until the lowest layer is reached and the data passes over some medium as a physical signal.', 5 => '', 6 => 'When the PDU of one layer (''n''), sent as SDU to the layer one lower than it (''n-1''), plus any metadata ([[Header (computing)|headers]]/[[Trailer (computing)|trailers]]) layer ''n-1'' adds to the SDU would exceed the largest size layer ''n-1''<nowiki/>'s PDU can be, it must be broken up into multiple payloads to fit in the layer-''n-1'' PDU's. This process is called [[IP fragmentation]].', 7 => '*[[IP fragmentation]]' ]
Lines removed in edit (removed_lines)
[ 0 => 'Between the layers (and between the application and the top-most layer), the layers pass service data units across the interfaces. The higher layer understands the structure of the data in the SDU, but the lower layer at the interface does not; the lower layer treats the SDU as [[Payload (computing)|payload]], undertaking to get it to the same interface at the destination. In order to do this, the ''protocol'' (lower) layer will add to the SDU certain data it needs to perform its function. For example, it might add a port number to identify the application, a network address to help with routing, a code to identify the type of data in the packet and error-checking information. All this additional information, plus the original service data unit from the higher layer, constitutes the ''protocol data unit'' at this layer. The significance of this is that the PDU is the structured information that is passed to a matching protocol layer further along on the data's journey that allows the layer to deliver its intended function or service. The matching layer, or "peer", decodes the data to extract the original service data unit, decide if it is error-free and where to send it next, etc. Unless we have already arrived at the lowest (physical) layer, the PDU is passed to the peer using services of the next lower layer in the protocol "stack". When the PDU passes over the interface from the layer that constructed it to the layer that merely delivers it (and therefore does not understand its internal structure), it becomes a service data unit to that layer. The addition of addressing and control information (which is called encapsulation) to an SDU to form a PDU and the passing of that PDU to the next lower layer as an SDU repeats until the lowest layer is reached and the data passes over some medium as a physical signal.' ]
Whether or not the change was made through a Tor exit node (tor_exit_node)
false
Unix timestamp of change (timestamp)
1555300217