Sep 23, 2018 - 02:42 AM
IPv6 Forum
|
|
|
Sep 23, 2018 - 02:42 AM
|
|||
|
IPv6 Forum |
|||||
|
|
|||||
|
|
|
||||
|
||||||
|
|
|||||
 |
Events and PromotionForum Member's Login  IPv6 Forum Regional & National Chapters:· Australia
· Belgium · Brazil · California · Canada · Chad · China · Colombia · Cuba · Denmark · Egypt · Estonia · Finland · France · Germany · Ghana · Greece · Hawaii · Grenada · Hong Kong · Hungary · India · Indonesia · Iran · Ireland · Israel · Italy · Japan · Jordan · Korea (South) · Latin America · Luxembourg · Malaysia · Mexico - IPv6 Forum · Mexico - IPv6 Task Force · MidAtlantic IPv6 TF · Morocco · Netherlands · New Zealand · Nigeria · North America · Norway · Oman · Pacific Islands · Pakistan · Palestine Territory · Peru · Philippines · Poland · Portugal · Rocky Mountains v6 Task Force · Romania · Russia · Saudi Arabia · Scotland · Senegal · Serbia · Singapore · Slovenia · Spain · Sudan · Sweden · Switzerland · Taiwan · Thailand · Texas v6 Task Force · Tunisia · Turkey · United Arab Emirates · United Kingdom · Vietnam · Yemen Who's OnlineThere are 75 unregistered users and 0 registered users on-line.
You can log-in or register for a user account here. |
Link profile: Once upon a time... - The history of the Internet
Category: Start / IPv6 Resources / Training and Education Introduction: When the ARPANET was designed in the late 1960s, it was outfitted with a Network Control Protocol (NCP) that made it possible for the very different types of hosts connected to the network to talk with each other. However, it soon became clear that NCP was limiting in some ways, so work started on something better. The engineers decided that it made sense to split the monolithic NCP protocol into two parts: an Internet Protocol that allows packets to be routed between the different networks connected to the ARPANET, and a Transport Control Protocol that takes a data stream, splits it into segments and transmits the segments using the Internet Protocol. On the other side, the receiving Transport Control Protocol makes sure the segments are put together in the right order before they're delivered as a data stream to the receiving application. An important implication of this approach is that unlike, for instance, a phone connected to a wired or wireless phone network, a host connected to the ARPANET then and the Internet now must know its own address. (...) Link rating details Total votes: 0 Overall rating: 0 |
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
 |
Driving IPv6 Deployment |
IPv6 Forum president Latif Ladid offers a welcome and 
see 