We continued the theme of infrastructure from a less technical perspective than in the previous sessions by Vicente Casares. We began analyzing the internet architecture from an organizational viewpoint by familiarizing ourselves with the work of IANA (Internet Assigned Numbers Authority), responsible for Domain Names, IP addressing and protocol assignment. We also discussed the internet architecture as autonomous system and three-tier hierarchical organization and the meaning of internet exchange points (IXP's).
Next we discussed the architecture from a more technical point of view. We saw some of the high level design principles as well as a brief view into how the design has evolved through time. Then after a short break we saw a very interesting consept called the fossilized architecture. This signifies that there are certain notable technologies, namely IP, TCP and BGP that can nomore be dismissed from the technical architecture that lies behind internet. On the other hand there are also some high-penetration technologies that should be questioned such as NAT, IPSec, Firewalls and MPLS as they risk the seamless interoperation of the set of technologies that appear in the world of internet (E.g. NAT doesn't work well with IPSec etc.).
We also discussed the principle problems in today's internet listed as follows
- security
- fragility
- reliability
- mobile terminal support
- alternative data-type support
- support for heavy flows
- service quality guarantees
- scalability
- substainble models for billing
Overall, this lecture offered a nice general view to the structure of the sometimes chaotically described internet. As a whole we looked at how the basic underlying technologies have maintained their roles untill today and what kind of evolutionary changes might be expected on the subject.
Ei kommentteja:
Lähetä kommentti