what is the TCP FIN,RFC 793, TCP Xmas Tree?
604926
TCP Xmas Tree is a port scanning techinique. The Xmas tree scan sends a TCP frame to a remote device with the URG, PUSH, and FIN flags set. This is called a Xmas tree scan because of the alternating bits turned on and off in the flags byte (00101001), much like the lights of a Christmas tree.\n\nTCP FIN is another port scaning technique. Scaning is done by sending the connection request with FIN bit set.\n\nRFC 739 - Assigned numbers, its a RFC document.\n\nFor further info visit:\nXMas Tree: http://www.networkuptime.com/nmap/page3-5.shtml\nTCP FIN: http://www.insecure.org\nRFC 739: http://www.faqs.org/rfcs/rfc739.html
1068475
Please Do Not Throw Sausage Pizza Away\n\nApplication - email..telnet...ftp layer\nPresentation - encryptian layer\nSession - establish, manage, terminate connections between apps.\nTransfer - end to end error recovery and flow control\nNetwork - switching/routing, IP address\nData Link - encode/decode into bitsMAC address layer\nPhysical - bit stream (electrical pulses, light, or sound signal)\n\nThese are the 7 layers.  I am not sure where you got 5.  This is the correct order as well.
941535
windows tcp handler aka winsock handles all the connections of ur windows pc, winsock 2 also can have additional plugins called as lsp's. lsp or layered service providers are plugins that can be placed into ur winsock to establish a specific type of connection according to the needs of the person who decides it.
144077
The application layer of TCP/IP is the layer where applications gain access. There are many standards TCP/IP utilities and services at the Applications layer such as FTP, Telnet, SNMP and DNS. \nMicrosoft TCP/IP provides two interfaces for network applications. Windows sockets-standard application programming interface (API) under Microsoft Windows for transport protocols such as TCP/IP and IPX.
139999
Didn't you ask this same question yesterday?  If there were no standards, then parts wouldn't be interchangeable.  Also, for LAN standards, do a search on TCP/IP subnetting.
277050
You don't need instructions for TCP/IP. TCP/IP is the communication method your computer uses to talk on the Internet. Don't mess with it at all.
756917
My god, I am trying to think of a way to explain it, there are a million links if you search, but think of a million large spider webs hooked together, you do have one (Company) thats does take care of all the names, somebody has to so there would only be only one of each name, You have millions of web servers, that are computers that can have 1 to 50,000 sites on each one.\nIf you use  your telephone line and modem or high speed connection, the computer connects to the ISP's server. Once there, the ISP acts as a gateway connecting you to any computer hooked to the World Wide Web, using browsers like Internet Explorer or Netscape. \n\nNext, you type in a URL (Uniform Resource Locator) - such as www.yahoo.com. The computer translates this into a number - the IP address - that is unique to every web page and computer, making it possible for machines to recognise each other. The machines then 'talk' to each other using 'languages' called protocols. Specifically, the protocol in question is TCP/IP, which allows computers to describe data to one another over a network. \n\nEvery computer on the WWW understands these two protocols, and can therefore communicate amicably. TCP/IP is actually two different things. TCP (Transmission Control Protocol) takes the information you want to send over the Internet, and breaks it into small chunks of data called 'packets' that can include programming, text, pictures, sound or video in various combinations. IP (Internet Protocol) takes over and routes those packets through computers to get them to their destination. \n\nWhen the packets arrive at the destination computer, TCP reassembles them into what you finally see as a web page on your computer screen. TCP/IP is further broken down into specialised protocols like STMP (which works with email), Ftp (for simple file transfers) and the omnipresent 'http://' (Hypertext Transfer Protocol), which is how Web browsers work. \n\nSounds a bit intimidating? Just remember: you have gone through each of these steps every time you have logged on to the Internet! .
248815
I ran a search and this is what I came up with. Hope it helps. http://redfoxpc.no-ip.com:8080/business/RFC/main.htm
268008
http://www.thirdage.com/features/tech/netglos/ here is some net lingo
231938
An interconnected system of networks that connects computers around the world via the TCP/IP protocol.
47821
In TCP, ACK is the correct response to a SYN packet.\n\nCheck out the RFC 793, Transmission Control Protocol, which is the definition of how TCP works.
409089
tcp has guearanteed delivery service and error correction so if the packets do not reach their destination you should receive an icmp internet control message protocol such as a ttl expiration or a host unreachable error message a method known as packet switching will break the data down into segments and travel the best path available they may all go a different route or they make take some of the same routes--there may be a problem with the receiving node dude
313222
I have no idea.  This is the computer networking area.  Please resubmit your question in the appropriate area.  Thanks.
178746
TCP OPERAThttp://www.dcs.gla.ac.uk/~lewis/networkpages/m07s03TCPoperation.htm
478422
Try these:\n\nhttp://www.sockets.com/a_e.htm\nhttp://zoo.cs.yale.edu/classes/cs433/lecture/network_programming.ppt
366137
http://csdl2.computer.org/persagen/DLAbsToc.jsp?resourcePath=/dl/proceedings/&toc=comp/proceedings/icip/1995/7310/03/7310toc.xml&DOI=10.1109/ICIP.1995.537702
158555
There are several differences between the two, as RFC 4364 addresses concepts/technologies not mentioned in the older RFC.  Section 1 has been noticeably revised, Section 3 now has substantial coverage of VRFs where the older RFC had none, and  Secition 4 has been expanded considerably.  (that's as far as I've read in both, so far.)  You'll want to read both (either printed, or online) side by side to see how extensive the revisions are in the intervening 5 years from 1999 (when FRC 2547 came out) to 2004 (when 4364 was published.)