{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:30:32Z","timestamp":1750307432954,"version":"3.41.0"},"reference-count":10,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[2011,3,1]],"date-time":"2011-03-01T00:00:00Z","timestamp":1298937600000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["Queue"],"published-print":{"date-parts":[[2011,3]]},"abstract":"<jats:p>\n            The design of TCP\/IP began in 1973 when Robert Kahn and I started to explore the ramifications of interconnecting different kinds of packet-switched networks. We published a concept paper in May 1974, and a fairly complete specification for TCP was published in December 1974. By the end of 1975, several implementations had been completed and many problems were identified. Iteration began, and by 1977 it was concluded that TCP (by now called Transmission Control Protocol) should be split into two protocols: a simple\n            <jats:italic>Internet Protocol<\/jats:italic>\n            that carried\n            <jats:italic>datagrams<\/jats:italic>\n            end to end through packet networks interconnected through\n            <jats:italic>gateways;<\/jats:italic>\n            and a TCP that managed the flow and sequencing of packets exchanged between hosts on the contemplated Internet. This split allowed for the possibility of realtime but possibly lossy and unsequenced packet delivery to support packet voice, video, radar, and other realtime streams.\n          <\/jats:p>","DOI":"10.1145\/1952746.1959015","type":"journal-article","created":{"date-parts":[[2012,10,15]],"date-time":"2012-10-15T19:22:23Z","timestamp":1350328943000},"page":"20-20","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":1,"title":["Successful Strategies for IPv6 Rollouts. Really."],"prefix":"10.1145","volume":"9","author":[{"given":"Thomas A.","family":"Limoncelli","sequence":"first","affiliation":[{"name":"Google"}]},{"given":"Vinton G.","family":"Cerf","sequence":"additional","affiliation":[{"name":"Google"}]}],"member":"320","published-online":{"date-parts":[[2011,3,10]]},"reference":[{"key":"e_1_2_1_1_1","doi-asserted-by":"crossref","unstructured":"Cerf V. Dalal Y. Sunshine C. 1974. RFC 675. Specification Internet Transmission Control Program.  Cerf V. Dalal Y. Sunshine C. 1974. RFC 675. Specification Internet Transmission Control Program.","DOI":"10.17487\/rfc0675"},{"key":"e_1_2_1_2_1","doi-asserted-by":"publisher","DOI":"10.1109\/TCOM.1974.1092259"},{"key":"e_1_2_1_3_1","unstructured":"Donley C. Howard L. Kuarsingh V. Chandrasekaran A. Ganti V. 2010. Assessing the impact of NAT444 on network applications. IETF Internet Draft; http:\/\/tools.ietf.org\/html\/draft-donley-nat444-impacts-01.  Donley C. Howard L. Kuarsingh V. Chandrasekaran A. Ganti V. 2010. Assessing the impact of NAT444 on network applications. IETF Internet Draft; http:\/\/tools.ietf.org\/html\/draft-donley-nat444-impacts-01."},{"key":"e_1_2_1_4_1","unstructured":"Doyle J. 2009. Understanding carrier-grade NAT; http:\/\/www.networkworld.com\/community\/node\/44989.  Doyle J. 2009. Understanding carrier-grade NAT; http:\/\/www.networkworld.com\/community\/node\/44989."},{"volume-title":"Conference 2008: IPv6, Nokia, and Google; http:\/\/www.youtube.com\/watch?v=o5RbyK0m5OY.","author":"Google","key":"e_1_2_1_5_1"},{"volume-title":"Implementors Conference; http:\/\/sites.google.com\/site\/ipv6implementors\/2010\/agenda.","author":"Google","key":"e_1_2_1_6_1"},{"key":"e_1_2_1_7_1","unstructured":"Kuhne M. 2009. IPv6 monitor: an interview with Alain Durand; https:\/\/labs.ripe.net\/Members\/mirjam\/content-ipv6-monitor.  Kuhne M. 2009. IPv6 monitor: an interview with Alain Durand; https:\/\/labs.ripe.net\/Members\/mirjam\/content-ipv6-monitor."},{"volume-title":"Google: IPv6 is easy, not expensive","year":"2009","author":"Marsan C. D.","key":"e_1_2_1_8_1"},{"key":"e_1_2_1_9_1","unstructured":"Miller R. 2009. The billion-dollar HTML tag; http:\/\/www.datacenterknowledge.com\/archives\/2009\/06\/24\/the-billion-dollar-html-tag\/.  Miller R. 2009. The billion-dollar HTML tag; http:\/\/www.datacenterknowledge.com\/archives\/2009\/06\/24\/the-billion-dollar-html-tag\/."},{"key":"e_1_2_1_10_1","unstructured":"Morr D. 2010. T-Mobile is pushing IPv6. Hard; http:\/\/www.personal.psu.edu\/dvm105\/blogs\/ipv6\/2010\/06\/t-mobile-is-pushing-ipv6-hard.html.  Morr D. 2010. T-Mobile is pushing IPv6. Hard; http:\/\/www.personal.psu.edu\/dvm105\/blogs\/ipv6\/2010\/06\/t-mobile-is-pushing-ipv6-hard.html."}],"container-title":["Queue"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1952746.1959015","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1952746.1959015","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T11:39:56Z","timestamp":1750246796000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1952746.1959015"}},"subtitle":["Knowing where to begin is half the battle."],"short-title":[],"issued":{"date-parts":[[2011,3]]},"references-count":10,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2011,3]]}},"alternative-id":["10.1145\/1952746.1959015"],"URL":"https:\/\/doi.org\/10.1145\/1952746.1959015","relation":{},"ISSN":["1542-7730","1542-7749"],"issn-type":[{"type":"print","value":"1542-7730"},{"type":"electronic","value":"1542-7749"}],"subject":[],"published":{"date-parts":[[2011,3]]},"assertion":[{"value":"2011-03-10","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}