trunk or access...

a phone is a switch which means it should be trunking to the other switch it's connected to to get on the lan because it will provide multi-vlan access... each phone can provide a voice and a data path, carrying traffic for two separate vlans, so by definition it is a trunk... you actually set up a separate vlan for voice specifically, and the so called access link tags frames... it is a trunk...
no... it is an access port...
or in cisco parlance it is a multi-access port...
so it's a trunk... no...

  a voice vlan  port does not forward all vlan traffic to the phone, it only tags the voice vlan, not the data frames...

   like a vlan 1 ieee scenario, whereby vlan 1 is identified because it is not tagged...

  i didn't make this shit up...

TCP segment...

this shit gets old...

The TCP segment includes 12 fields:

1. Source port  2. Destination port.  These first two fields identify the upper layer source and destination ports processed by TCP services. 3.  Sequence number usually specifies the number assigned to the first byte of data in the current message. It can also be used to identify an initial sequence number for a future transmission. 4.  Acknowledgement number, contains the sequence number of  the next byte of data the sender expects to receive.  5.  Data offset indicates the number of 32 bit words in the TCP header.  6.  Reserved-for future use. 7.  Flags- carries control information, including syn-ack bits for connection establishment, and FIN for connection termination.  8.  Window-specifies the size of the sender’s receive window (buffer space available for incoming data) 9.  Checksum-indicating header transmission damage if applicable.  10.  Urgent pointer- points to the first urgent byte in the packet 11.  Options-various tcp options, and 12. Data, contains upper layer information.