Talk:Network packet

message: I decided to put the definition in this page, instead of Datagram, since a lot more
pages link here, so we can avoid a redirect if a reader hits the "packet" link. Noel 09:12, 24 Aug 2003 (UTC)
replies: text: Yes. I've cleaned up the section and made it an ordered list, but I'm still not too happy with it. Maybe it's better to remove the section and link to the IPv4 packets/IPV6 packets sections instead? Ddfreyne 12:56, 29 April 2006 (UTC)
replies: text: It seems like a bad idea to treat datagram only under packet.  I have two reasons for saying that: 1) The idea of datagram is basic to the service provided by IP (in fact, it is often called "datagram service" and 2) A datagram is not really the same kind of thing as a packet, which is simply a unit of data; it is a different kind of thing, defined in all the textbooks on Internet networking that I have used by its basic property (containing enough information to get it to its destination) -- eg., Peterson & Davie, which devotes a section to datagrams; Kurose & Ross, which introduces it in its own section in the first chapter; and Comer, which also has a section on the "IPv4 Datagram".   This definition is missing here -- all that can be understood from this article is that a datagram is an unreliable packet.  --- There should be a separate article on datagrams. Ngriffeth (talk) 22:56, 9 March 2010 (UTC)
thread_title: Definition

message: Is there a name for "networks that forward packets several hops from one node to the next,
but occasionally drop packets and immmediately forget about them"?
I suppose I could call them "dumb networks that follow the end-to-end principle",
but is there a better name?
What other kinds of networks are there?
--65.70.89.241 21:19, 21 August 2006 (UTC)
thread_title:  end-to-end principle 

message: I am considering adding this to the article:
:In some radio communications, a fixed preamble is transmitted before the rest of the packet.
:This helps the automatic gain control and clock recovery in the reciever settle to reasonable values.
Is the preamble considered "the first part of" the header, or "comes before" the header?
--65.70.89.241 21:19, 21 August 2006 (UTC)
thread_title:  preamble 

message: Although the article 'transmission block' is very sparse and not very informative it should probably not be merged here, at least not without careful examination of the scope of that term. 'Packets' are a form of 'transmission blocks' by some definition perhaps, but transmission blocks are not usually packets, it would appear. A major characteristic of 'packets' or packet-mode communications is that they are sent over a shared communications medium, whereas telecom's 'transmission blocks' are sent over circuits, therefore the need for the common start/end of block markers. Kbrose (talk) 00:07, 24 February 2009 (UTC)
replies: text: I agree. Merge declined. --Alvestrand (talk) 06:22, 28 June 2009 (UTC)
thread_title:  Merge of [[Transmission block]] to this, December 2007 

message: Under "Example: IP packets," it doesnt specify where in the list the payload itself goes and what size or size range it occupies. -67.161..  —Preceding unsigned comment added by 67.161.54.63 (talk) 10:43, 28 March 2011 (UTC)
replies: text: I have clarified this. ~Kvng (talk) 15:16, 8 June 2019 (UTC)
thread_title:  Payload 

message: There was some info that did not seem immediately relevant or supportive to the topic.  This info was also unclear and unsupported.  I am removing those lines and adding here.
*From Summary:
** By using packet switched networking it is also harder to guarantee a lowest possible bitrate.
End of remarks Stephen Charles Thompson (talk) 15:41, 24 January 2012 (UTC)
thread_title:  Removed extraneous