Abstract
The Internet protocol, IP, is one of a large number of network layer protocols. Clearly the explosive growth of the Internet alone makes IP an important factor in considering business strategy and evolution. There are, however, underlying reasons why IP has gained the status that it has. It is also important to realize that the limitations and weaknesses traditionally attributed to the Internet (congested, insecure, etc) are not necessarily intrinsic weaknesses of the TCP/IP protocol suite
-
IP is an internetworking protocol, which is designed to operate over almost all underlying networks. Therefore, there is no requirement for a homogeneous end-to-end infrastructure. End-stations may use a variety of cheap interface cards (e.g. Ethernet), but the core network may be comprised of vastly different technologies.
-
IP is connectionless, meaning that end-to-end connections do not have to be established before data can be sent. This is well suited to short-lived communications, but can also support long-lived connections (via TCP).
-
IP networks are highly scalable, with a uniformly accepted addressing scheme.
-
IP is service-independent, in that a wide range of application types are supported by a single, modular protocol suite. This means that new services are extremely easy to deploy, without requiring extensive changes to end-stations or network stacks.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
References
Braden R et al: ‘Resource ReSerVation Protocol (RSVP) — Version 1 functional specification’, RFC 2205 (September 1997) —ftp://ds.intemic.net/rfc/rfc2205.txt
Postel J: ‘Transmission control protocol’, RFC793 (September 1981) —ftp://ds.internic.net/rfc/rfc793.txt
Stevens W: ‘TCP slow start, congestion avoidance, fast retransmit, and fast recovery algorithms’, RFC 2001 (January 1997) —ftp://ds.internic.net/rfc/rfc2001.txt
Braden R et al: ‘Integrated services in the Internet architecture: an overview’, RFC 1633: (June 1994) —ftp://ds.intemic.net/rfc/rfc1633.txt
Plummer D C: ‘Ethernet Address Resolution Protocol’, RFC 826 (November 1982) —ftp://ds.internic.net/rfc/rfc826.txt
Braden R: ‘Requirements for Internet hosts — communication layers’, RFC1122 (October 1989) —ftp://ds.internic.net/rfc/rfc1122.txt
Armitage G: ‘Support for multicast over UNI 3.0/3.1 based ATM networks’, RFC 2022 (November 1996) —ftp://ds.intemic.net/rfc/rfc2022.txt
Bormann C: ‘Providing integrated services over low-bitrate links’, (May 1997) —http://www.ietf.org/internet-drafts/draft-ietf-issll-isslow-04.txt
Simpson W: ‘The point-to-point protocol (PPP)’, RFC1661 (July 1994) —ftp://ds.internic.net/rfc/rfc1661.txt
Sklower M K et al: ‘The PPP multilink protocol (MP)’, RFC1990 (August 1996) —ftp://ds.internic.net/rfc/rfc1990.txt
Richards C and Smith K: ‘The PPP bandwidth allocation protocol (BAP), the PPP bandwidth allocation control protocol (BACP)’, RFC2125 (March 1997) —ftp://ds.internic.net/rfc/rfc2125.txt
Hamzeh K et al: ‘Layer two tunneling protocol, L2TP’, (August 1997) —http://www.ietf.org/intemet-drafts/draft-ietf-pppext-l2tp-06.txt/intemet-drafts/draft-ietf-pppext-l2tp-06.txt
The IP Multicast Initiative WWW pages —http://www.ipmulticast.com/
Bates T et al: ‘Multiprotoco1 extensions for BGP-4’, RFC2283 (September 1998) —ftp://ds.internic.net/rfc/rfc2283.txt
O‘Neill A: Intemetwork futures’, in Sim S P and Davies N J (Eds): ‘The Internet and beyond’, Chapman & Hall, pp 412–440 (1998).
Shreedhar M and Varghese G: ‘Efficient fair queuing using deficit round-robin‘, Proc SiGCOMM’95, pp 231–243 (1995).
Parekh A K and Gallager R G: ‘A generalized processor sharing approach to flow control in integrated services networks: the single-node case’, IEEE/ACM Trans on Networking, 1, No 1, pp 344–357 (February 1993).
Clark D et al: ‘Supporting real-time applications in an integrated services packet network: architecture and mechanisms’, Proc Sigcom 92 (1992).
Wakeman I et al: ‘Implementing real time packet forwarding policies using streams’, Usenix 1995 Technical conference, New Orleans, pp 71–82 (1995) —http://www.cs.ucl.ac.uk/darpa/usenix-cbq.ps
White P: ‘RSVP and integrated services in the Internet: a tutorial’, IEEE Communications Magazine (May 1997).
Mankin A (Ed): ‘Resource reservation protocol (RSVP) version 1 applicability statement: Some guidelines on deployment’, RFC2208 (September 1997) —ftp://ds.internic.net/rfc/rfc2205.txt
Blake S et al: ‘An architecture for differentiated services’, RFC 2475 (December 1998).
Nichols K et al: ‘Definition of the differentiated services field (DS Field) in the IPv4 and IPv6 Headers’, RFC 2474 (December 1998).
Clark D and Wroclawski J: ‘An approach to service allocation in the intemet’, (July 1997) —http://www.ietf.org/internet-drafts/draft-clark-diff-svc-alloc-00.txt
Carter S F et al: ‘A bounded-delay service for the Internet’,intemet-draft (November 1998) —http://www.ietf.org/internet-drafts/draft-carter-bounded-delay-00.txt
IEIF Uni-directional Link Routeing pages —http://www.ietf.org/html.charters/udlrcharter.html
Deering S and Hinden R: ‘Internet protocol, Version 6 (IPv6) specification’, (July 1997) —http://www.ietf.org/intemet-drafts/draft-ietf-ipngwg-ipv6-spec-v2-00.txt
Optical Internetworking Forum —http://www.oiforum.com/
Internet Engineering Task Force —http://www.ietf.org/
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 1999 Springer Science+Business Media Dordrecht
About this chapter
Cite this chapter
O’Neill, A., Tatham, M.C., Carter, S.F., Tsirtsis, G., Dann, A.J. (1999). Internet Technology Considerations. In: King, T., Newson, D. (eds) Data Network Engineering. BT Telecommunications Series, vol 17. Springer, Boston, MA. https://doi.org/10.1007/978-1-4615-5215-4_11
Download citation
DOI: https://doi.org/10.1007/978-1-4615-5215-4_11
Publisher Name: Springer, Boston, MA
Print ISBN: 978-1-4613-7376-6
Online ISBN: 978-1-4615-5215-4
eBook Packages: Springer Book Archive