University of Cambridge > > Computer Laboratory Systems Research Group Seminar > Are we stuck with the current Internet Protocol (IP)? (And does it matter if we are?)

Are we stuck with the current Internet Protocol (IP)? (And does it matter if we are?)

Add to your list(s) Download to your calendar using vCal

If you have a question about this talk, please contact Srinivasan Keshav.

The Internet Protocol version 4 (IPv4) was defined in 1981, though a version of it had existed since the mid-1970s. Today, the core protocol architecture has changed little from the original. Its intended replacement, IPv6, took around 20 years to become a full standard, and is still not as widely used as IPv4. Meanwhile, a number of deficiencies in IPv4 have been subject to retro-fitted fixes that themselves introduce new challenges. Additionally, due to concerns with ossification of IP (from a number of factors), it seems that attention has moved to other layers of the communication stack to solve existing deficiencies, or to add new functionality.

I will examine examples of communication functionality that has “other layer” (non-IP-layer) solutions, and discuss alternatives that could be implemented at the IP layer based on the Identifier Locator Network Protocol. I will use results from practical experiments with ILNP on existing IP-based infrastructure with the intention of encouraging further thinking and discussion about the question(s) that form the title of this talk.

mini-bio: Saleem Bhatti is a professor in the School of Computer Science at the University of St Andrews, UK. He is interested in the design, use and performance of computer communication systems, architectures, protocols and applications. He has a preference for practical work, using test-beds – he likes to build, test, and break things!

This talk is part of the Computer Laboratory Systems Research Group Seminar series.

Tell a friend about this talk:

This talk is included in these lists:

Note that ex-directory lists are not shown.


© 2006-2024, University of Cambridge. Contact Us | Help and Documentation | Privacy and Publicity