{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2025,6,19]],"date-time":"2025-06-19T04:40:07Z","timestamp":1750308007424,"version":"3.41.0"},"reference-count":37,"publisher":"Association for Computing Machinery (ACM)","issue":"3","license":[{"start":{"date-parts":[[2006,7,5]],"date-time":"2006-07-05T00:00:00Z","timestamp":1152057600000},"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":["SIGCOMM Comput. Commun. Rev."],"published-print":{"date-parts":[[2006,7,5]]},"abstract":"<jats:p>\n            We describe a system in which layer 2 switching is placed directly under the control of layer 3 routing protocols on a hop-by-hop basis. Specifically, ATM switching is controlled by IP. We couple each ATM switch with a general purpose computer running IP routing and management protocols. We define a default ATM virtual channel identifier (VCI) to be used for transmitting IP packets over ATM links. We then define mechanisms which allow specific\n            <jats:italic>flows<\/jats:italic>\n            to be transmitted on specific ATM VCIs. The resulting system obeys IP's semantics for routing and forwarding, and takes advantage of ATM's switching hardware to accelerate the forwarding of packets. While this system takes advantage of ATM hardware, the ATM signalling, routing, and management architecture (as specified by the ATM Forum) is replaced by the protocols and practices currently in use for IP routing and management.\n          <\/jats:p>","DOI":"10.1145\/1140086.1140097","type":"journal-article","created":{"date-parts":[[2006,7,24]],"date-time":"2006-07-24T17:00:26Z","timestamp":1153760426000},"page":"79-92","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":2,"title":["Flow labelled IP over ATM"],"prefix":"10.1145","volume":"36","author":[{"given":"Greg","family":"Minshall","sequence":"first","affiliation":[{"name":"Ipsilon Networks, Inc."}]},{"given":"Bob","family":"Hinden","sequence":"additional","affiliation":[{"name":"Ipsilon Networks, Inc."}]},{"given":"Eric","family":"Hoffman","sequence":"additional","affiliation":[{"name":"Ipsilon Networks, Inc."}]},{"given":"Fong Ching","family":"Liaw","sequence":"additional","affiliation":[{"name":"Ipsilon Networks, Inc."}]},{"given":"Tom","family":"Lyon","sequence":"additional","affiliation":[{"name":"Ipsilon Networks, Inc."}]},{"given":"Peter","family":"Newman","sequence":"additional","affiliation":[{"name":"Ipsilon Networks, Inc."}]}],"member":"320","published-online":{"date-parts":[[2006,7,5]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"A. Alles. ATMinternetworking May1995. http:\/\/www.cisco.com\/warp\/public\/614\/12.html.]]  A. Alles. ATMinternetworking May1995. http:\/\/www.cisco.com\/warp\/public\/614\/12.html.]]"},{"volume-title":"Inc.","year":"1983","author":"BBNInc. Speci?cations","key":"e_1_2_1_2_1"},{"volume-title":"Internet Engineering Task Force","year":"1993","author":"Bradley T.","key":"e_1_2_1_3_1"},{"volume-title":"Addison-Wesley","year":"1994","author":"William","key":"e_1_2_1_4_1"},{"key":"e_1_2_1_5_1","doi-asserted-by":"publisher","DOI":"10.1109\/49.464717"},{"key":"e_1_2_1_6_1","doi-asserted-by":"publisher","DOI":"10.1145\/144179.144199"},{"volume-title":"Ellis Horwood","year":"1991","author":"Prycker Martinde","key":"e_1_2_1_7_1"},{"volume-title":"Internet Engineering Task Force","year":"1989","author":"Deering S.","key":"e_1_2_1_8_1"},{"key":"e_1_2_1_9_1","unstructured":"S. Deeringand R. Hinden. Internetprotocol version6(ipv6)speci?cation. RequestforComments(ProposedStand ard)RFC1883 InternetEngineeringTaskForce January1996 ftp:\/\/ds.internic.net\/rfc\/rfc1883.txt.]]  S. Deeringand R. Hinden. Internetprotocol version6(ipv6)speci?cation. RequestforComments(ProposedStand ard)RFC1883 InternetEngineeringTaskForce January1996 ftp:\/\/ds.internic.net\/rfc\/rfc1883.txt.]]"},{"key":"e_1_2_1_10_1","doi-asserted-by":"publisher","DOI":"10.1109\/90.251892"},{"key":"e_1_2_1_11_1","doi-asserted-by":"publisher","DOI":"10.1109\/90.413212"},{"volume-title":"Internet Engineering Task Force","year":"1984","key":"e_1_2_1_12_1"},{"volume-title":"Upper Saddle River","year":"1996","author":"Huitema Christian","key":"e_1_2_1_13_1"},{"volume-title":"BPF","year":"1990","author":"Van","key":"e_1_2_1_14_1"},{"key":"e_1_2_1_15_1","doi-asserted-by":"publisher","DOI":"10.1145\/55483.55524"},{"key":"e_1_2_1_16_1","doi-asserted-by":"publisher","DOI":"10.1145\/360248.360253"},{"key":"e_1_2_1_17_1","doi-asserted-by":"publisher","DOI":"10.1145\/55483.55502"},{"key":"e_1_2_1_18_1","doi-asserted-by":"publisher","DOI":"10.1145\/52325.52337"},{"volume-title":"Internet Engineering Task Force","year":"1994","author":"Moy J.","key":"e_1_2_1_19_1"},{"volume-title":"Ipsilon and Sprint","year":"1996","author":"Newman P.","key":"e_1_2_1_20_1"},{"volume-title":"Ipsilon and Sprint","year":"1996","author":"Newman P.","key":"e_1_2_1_21_1"},{"key":"e_1_2_1_22_1","doi-asserted-by":"publisher","DOI":"10.1109\/INFCOM.1996.493071"},{"volume-title":"Internet Engineering Task Force","year":"1991","author":"Oran D.","key":"e_1_2_1_23_1"},{"key":"e_1_2_1_24_1","unstructured":"Craig Partridge. private communication March 1996.]]  Craig Partridge. private communication March 1996.]]"},{"key":"e_1_2_1_25_1","doi-asserted-by":"publisher","DOI":"10.1145\/217382.217413"},{"key":"e_1_2_1_26_1","doi-asserted-by":"publisher","DOI":"10.1145\/217382.217409"},{"volume-title":"Internet Engineering Task Force","year":"1982","author":"Plummer D.","key":"e_1_2_1_27_1"},{"volume-title":"Internet Engineering Task Force","year":"1981","author":"Postel J.","key":"e_1_2_1_28_1"},{"volume-title":"Internet Engineering Task Force","year":"1981","author":"Postel J.","key":"e_1_2_1_29_1"},{"key":"e_1_2_1_30_1","doi-asserted-by":"publisher","DOI":"10.17487\/rfc0793"},{"volume-title":"Internet Engineering Task Force","year":"1981","author":"Postel Jon","key":"e_1_2_1_31_1"},{"volume-title":"Internet Engineering Task Force","year":"1984","author":"Postel Jon","key":"e_1_2_1_32_1"},{"key":"e_1_2_1_33_1","unstructured":"Yakov Rekhter. private communication January 1996.]]  Yakov Rekhter. private communication January 1996.]]"},{"key":"e_1_2_1_34_1","doi-asserted-by":"publisher","DOI":"10.1145\/190314.190322"},{"key":"e_1_2_1_35_1","doi-asserted-by":"publisher","DOI":"10.1145\/1015591.1015593"},{"volume-title":"Internet Engineering Task Force","year":"1994","author":"Simpson W.","key":"e_1_2_1_36_1"},{"key":"e_1_2_1_37_1","doi-asserted-by":"publisher","DOI":"10.1109\/65.238150"}],"container-title":["ACM SIGCOMM Computer Communication Review"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1140086.1140097","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/1140086.1140097","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T15:06:32Z","timestamp":1750259192000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/1140086.1140097"}},"subtitle":["design and rationale"],"short-title":[],"issued":{"date-parts":[[2006,7,5]]},"references-count":37,"journal-issue":{"issue":"3","published-print":{"date-parts":[[2006,7,5]]}},"alternative-id":["10.1145\/1140086.1140097"],"URL":"https:\/\/doi.org\/10.1145\/1140086.1140097","relation":{},"ISSN":["0146-4833"],"issn-type":[{"type":"print","value":"0146-4833"}],"subject":[],"published":{"date-parts":[[2006,7,5]]},"assertion":[{"value":"2006-07-05","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}