Middleboxes: Taxonomy and Issues
By B. Carpenter, Scott W. Brim. Request for Comments, 2002
296 citations recorded by the source corpus.
Subfields: Computer Networks and Communications, Electrical and Electronic Engineering, Hardware and Architecture
View Paper: https://www.semanticscholar.org/paper/daa51b3134954e540bb1600b1393abab02be000d
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Computer Networks and Communications
In Electrical and Electronic Engineering
In Hardware and Architecture
Citations in the corpus
- Is it still possible to extend TCP? (2011, background): “We focus on TCP, not only because it is by far the most widely used transport protocol, but also because while it is known that many middleboxes modify TCP behavior [6], it is not known how prevalent such middleboxes are, nor precisely what the emergent behavior is with TCP extensions that were unfo”
- Specifying and placing chains of virtual network functions (2014, background): “ these functions are implemented on physical middle-boxes, which are network appliances that perform functions other than standard path discovery or routing decisions for forwarding packets (RFC 3234 [1]). Middle-boxes are based on specialpurpose hardware platforms that are expensive and difficult to”
- A comprehensive survey of Network Function Virtualization (2018, background): “Routing/Forwarding devices [30] Packet Routing table update and data”
- Split/Merge: System Support for Elastic Execution in Virtual Middleboxes (2013, unknown): “A middlebox is defined as “any intermediary device performing functions other than the normal, standard functions of an IP router on the datagram path between a source host and destination host” [4].”