Show simple item record

dc.contributor.authorElsayed, Tameren_US
dc.contributor.authorHussein, Mohameden_US
dc.contributor.authorYoussef, Moustafaen_US
dc.contributor.authorNadeem, Tameren_US
dc.contributor.authorYoussef, Adelen_US
dc.contributor.authorIftode, Liviuen_US
dc.date.accessioned2004-05-31T23:29:10Z
dc.date.available2004-05-31T23:29:10Z
dc.date.created2003-09en_US
dc.date.issued2003-09-25en_US
dc.identifier.urihttp://hdl.handle.net/1903/1287
dc.description.abstractIn this report we present the design of the Autonomous Transport Protocol (ATP). The basic service provided by ATP is a reliable transport connection between two endpoints (identified by content identifiers) independent of their physical location. Autonomy allows dynamic endpoints relocation on different end hosts without disrupting the transport connection between them. ATP depends on the existence of an underlying Instance-Based Network (IBN) to achieve its goals. An IBN provides the flexibility of having different instances of the same content. It is up to the user of the IBN network to define the relation between these instances. An IBN allows its user to to map a content to a particular node. Application endpoints can send messages to other content-identified endpoints. Routing in the IBN is instance-based; the IBN can route a message to a specific content instance or to the nearest instance, if no exact match is found for the destination content instance. Moreover, the IBN replicates the stored contents in order to provide fault tolerance and IBN nodes along the query path can cache a content to provide fast answers to future queries. The ATP layer in the intermediate nodes between the source and destination endpoints can actively participate in the connection, for example, to buffer data for the destination endpoints during periods of unavailability. Data is transferred by a combination of active and passive operations, where the ATP layer of a node can decide whether to actively push the data to the destination or to passively wait for the destination endpoint to pull the data. The decision to whether to use the active or passive modes can be taken by a local policy on the node running the ATP protocol. (UMIACS-TR-2003-52)en_US
dc.format.extent4208596 bytes
dc.format.mimetypeapplication/postscript
dc.language.isoen_US
dc.relation.ispartofseriesUM Computer Science Department; CS-TR-4483en_US
dc.relation.ispartofseriesUMIACS; UMIACS-TR-2003-52en_US
dc.titleATP: Autonomous Transport Protocolen_US
dc.typeTechnical Reporten_US
dc.relation.isAvailableAtDigital Repository at the University of Marylanden_US
dc.relation.isAvailableAtUniversity of Maryland (College Park, Md.)en_US
dc.relation.isAvailableAtTech Reports in Computer Science and Engineeringen_US
dc.relation.isAvailableAtUMIACS Technical Reportsen_US


Files in this item

Thumbnail
Thumbnail

This item appears in the following Collection(s)

Show simple item record