N
Nick Feamster
Researcher at University of Chicago
Publications - 354
Citations - 20379
Nick Feamster is an academic researcher from University of Chicago. The author has contributed to research in topics: The Internet & Computer science. The author has an hindex of 68, co-authored 333 publications receiving 18086 citations. Previous affiliations of Nick Feamster include University of Maryland, College Park & Princeton University.
Papers
More filters
Journal ArticleDOI
Improving network management with software defined networking
Hyojoon Kim,Nick Feamster +1 more
TL;DR: Three problems in network management are identified: enabling frequent changes to network conditions and state, providing support for network configuration in a highlevel language, and providing better visibility and control over tasks for performing network diagnosis and troubleshooting.
Journal ArticleDOI
The road to SDN: an intellectual history of programmable networks
TL;DR: The intellectual history of programmable networks, including active networks, early efforts to separate the control and data plane, and more recent work on OpenFlow and network operating systems are traced.
Journal ArticleDOI
Understanding the network-level behavior of spammers
TL;DR: It is found that most spam is being sent from a few regions of IP address space, and that spammers appear to be using transient "bots" that send only a few pieces of email over very short periods of time.
Journal ArticleDOI
How to lease the internet in your spare time
TL;DR: This work presents a high-level design for Cabo, an architecture that enables this separation of infrastructure providers and service providers and describes challenges associated with realizing this architecture.
Proceedings ArticleDOI
Design and implementation of a routing control platform
Matthew Caesar,Donald Caldwell,Nick Feamster,Jennifer Rexford,Aman Shaikh,Jacobus Van der Merwe +5 more
TL;DR: It is shown that RCP assigns routes correctly, even when the functionality is replicated and distributed, and that networks using RCP can expect comparable convergence delays to those using today's iBGP architectures.