Descarga la app de Kindle gratis y comienza a leer libros Kindle al instante desde tu smartphone, tablet o computadora, sin necesidad de ningún dispositivo Kindle.
Lee al instante desde tu navegador con Kindle para la web.
Usando la cámara de tu celular escanea el siguiente código y descarga la aplicación Kindle.
Imagen no disponible
Color:
-
-
-
- Para ver la descarga de este video Flash Player
Seguir al autor
Aceptar
Por W. protocolos de Richard Stevens – TCP/IP Ilustrado, volumen 1: La: 2 nd (Segunda Edición) 37647th Edición
- ISBN-100201633469
- ISBN-13978-0201633467
- Edición37647th
- EditorialAddison-Wesley Professional
- Fecha de publicación1 Enero 1994
- IdiomaInglés
- Dimensiones8 x 1.75 x 9.5 pulgadas
- Número de páginas576 páginas
Productos similares que se envían cerca de ti
Opiniones editoriales
Opinión de Amazon.es
Volume two of this series, TCP/IP Illustrated, Volume 2: The Implementation, covers the implementation of TCP/IP. Volume three explores TCP for Transactions, HTTP, NNTP, and the Unix Domain Protocols.
Contraportada
TCP/IP Illustrated is a complete and detailed guide to the entire TCP/IP protocol suite-with an important difference from other books on the subject. Rather than just describing what the RFCs say the protocol suite should do, this unique book uses a popular diagnostic tool so you may actually watch the protocols in action.By forcing various conditions to occur-such as connection establishment, timeout and retransmission, and fragmentation-and then displaying the results, TCP/IP Illustrated gives you a much greater understanding of these concepts than words alone could provide. Whether you are new to TCP/IP or you have read other books on the subject, you will come away with an increased understanding of how and why TCP/IP works the way it does, as well as enhanced skill at developing applications that run over TCP/IP.
With this unique approach, TCP/IP Illustrated presents the structure and function of TCP/IP from the link layer up through the network, transport, and application layers. You will learn about the protocols that belong to each of these layers and how they operate under numerous implementations, including Sun OS 4.1.3, Solaris 2.2, System V Release 4, BSD/386TM, AIX 3.2.2, and 4.4BSD.In TCP/IP Illustrated you will find the most thorough coverage of TCP available - 8 entire chapters. You will also find coverage of the newest TCP/IP features, including multicasting, path MTU discovery, and long fat pipes.
"While all of Stevens' books are excellent, this new opus (TCP/IP Illustrated, Volume 1) is awesome. Although many books describe the TCP/IP protocols, the author provides a level of depth and real-world detail lacking from the competition."
- Unix Review
"This book (TCP/IP Illustrated, Volume 1) is a stone jewel...Written by W. Richard Stevens, this book probably provides the most comprehensive view of TCP/IP available today in print."
- Boardwatch
"The diagrams he uses are excellent and his writing style is clear and readable. Please read it (TCP/IP Illustrated, Volume 1) and keep it on your bookshelf."
- Sys Admin
"The word 'illustrated' distinguishes this book (TCP/IP Illustrated, Volume 1) from its many rivals. Stevens uses the Lawrence Berkeley Laboratories tcdump program to capture packets in promiscuous mode under a variety of OS and TCP/IP implementations. Studying tcdump output helps you understand how the various protocols work."
- Unix Review
Biografía del autor
We are deeply saddened to learn of the death of noted author W. Richard Stevens. His passing is obviously a tremendous loss for the technical community, but it is a personal one for us as well. Rich was both a gifted colleague and a valued friend who will be greatly missed. We extend our sympathies to his family.
Obituary from the Arizona Daily Star:
STEVENS, W. Richard, noted author of computer books died on September 1. He is best known for his "UNIX Network Programming" series (1990, 1998, 1999), "Advanced Programming in the UNIX Environment" (1992), and "TCP/IP Illustrated" series (1994, 1995, 1996). Richard was born in 1951 in Luanshya, Northern Rhodesia (now Zambia), where his father worked for the copper industry. The family moved to Salt Lake City, Hurley, New Mexico, Washington, DC and Phalaborwa, South Africa. Richard attended Fishburne Military School in Waynesboro, Virginia. He received a B.SC. in Aerospace Engineering from the University of Michigan in 1973, and an M.S. (1978) and Ph.D. (1982) in Systems Engineering from the University of Arizona. He moved to Tucson in 1975 and from then until 1982 he was employed at Kitt Peak National Observatory as a computer programmer. From 1982 until 1990 he was Vice President of Computing Services at Health Systems International in New Haven, CT, moving back to Tucson in 1990. Here he pursued his career as an author and consultant. He was also an avid pilot and a part-time flight instructor during the 1970's.He is survived by his loving wife of 20 years, Sally Hodges Stevens; three wonderful children, Bill, Ellen and David; sister, Claire Stevens of Las Vegas, NV; brother, Bob and wife Linda Stevens of Dallas, TX; nieces, Laura, Sarah, Collette, Christy; and nephew, Brad. He is predeceased by his parents, Royale J. Stevens (1915-1984); and Helen Patterson Stevens (1916-1997). Helen lived in Tucson from 1991-1997, and Royale lived here in the early 1930's attending Tucson High School while his father was treated for TB at the Desert Sanitorium (now TMC). The family asks that in lieu of flowers, donations be made in Richard's name to Habitat for Humanity, 2950 E. 22nd Street, Tucson, AZ 85713. A memorial service for Richard will be held at St. Phillip's in the Hills Episcopal Church on Tuesday, September 7th at 12:00 noon. Following the service there will be a reception in the Murphy Gallery of the Church. Please wear colorful clothing to the service; Richard loved colors.
W. Richard Stevens was an acknowledged UNIX and networking expert and the highly-respected author of several books. He was also a sought-after instructor and consultant.
Extracto. © Reimpreso con autorización. Reservados todos los derechos.
Introduction
This book describes the TCP/IP protocol suite, but from a different perspective than other texts on TCP/IP. Instead of just describing the protocols and what they do, we'll use a popular diagnostic tool to watch the protocols in action. Seeing how the protocols operate in varying circumstances provides a greater understanding of how they work and why certain design decisions were made. It also provides a look into the implementation of the protocols, without having to wade through thousands of lines of source code.When networking protocols were being developed in the 1960s through the 1980s, expensive, dedicated hardware was required to see the packets going "across the wire." Extreme familiarity with the protocols was also required to comprehend the packets displayed by the hardware. Functionality of the hardware analyzers was limited to that built in by the hardware designers.
Today this has changed dramatically with the ability of the ubiquitous workstation to monitor a local area network Mogul 1990. Just attach a workstation to your network, run some publicly available software (described in Appendix A), and watch what goes by on the wire. While many people consider this a tool to be used for diagnosing network problems, it is also a powerful tool for understanding how the network protocols operate, which is the goal of this book.
This book is intended for anyone wishing to understand how the TCP/IP protocols operate: programmers writing network applications, system administrators responsible for maintaining computer systems and networks utilizing TCP/IP, and users who deal with TCP/IP applications on a daily basis.
Organization of the Book
We take a bottom-up approach to the TCP/IP protocol suite. After providing a basic introduction to TCP/IP in Chapter 1, we will start at the link layer in Chapter 2 and work our way up the protocol stack. This provides the required background for later chapters for readers who aren't familiar with TCP/IP or networking in general.This book also uses a functional approach instead of following a strict bottom-to-top order. For example, Chapter 3 describes the IP layer and the IP header. But there are numerous fields in the IP header that are best described in the context of an application that uses or is affected by a particular field. Fragmentation, for example, is best understood in terms of UDP (Chapter 11), the protocol often affected by it. The time-to-live field is fully described when we look at the Traceroute program in Chapter 8, because this field is the basis for the operation of the program. Similarly, many features of ICMP are described in the later chapters, in terms of how a particular ICMP message is used by a protocol or an application.
We also don't want to save all the good stuff until the end, so we describe TCP/IP applications as soon as we have the foundation to understand them. Ping and Traceroute are described after IP and ICMP have been discussed. The applications built on UDP (multicasting, the DNS, TFTP, and BOOTP) are described after UDP has been examined. The TCP applications, however, along with network management, must be saved until the end, after we've thoroughly described TCP. This text focuses on how these applications use the TCP/IP protocols. We do not provide all the details on running these applications.
Readers
This book is self-contained and assumes no specific knowledge of networking or TCP/IP. Numerous references are provided for readers interested in additional details on specific topics.This book can be used in many ways. It can be used as a self-study reference and covered from start to finish by someone interested in all the details on the TCP/IP protocol suite. Readers with some TCP/IP background might want to skip ahead and start with Chapter 7, and then focus on the specific chapters in which they're interested. Exercises are provided at the end of the chapters, and most solutions are in Appendix D. This is to maximize the usefulness of the text as a self-study reference.
When used as part of a one- or two-semester course in computer networking, the focus should be on IP (Chapters 3 and 9), UDP (Chapter 11), and TCP (Chapters 17-24), along with some of the application chapters.
Many forward and backward references are provided throughout the text, along with a thorough index, to allow individual chapters to be studied by themselves. A list of all the acronyms used throughout the text, along with the compound term for the acronym, appears on the inside back covers.
If you have access to a network you are encouraged to obtain the software used in this book (Appendix F) and experiment on your own. Hands-on experimentation with the protocols will provide the greatest knowledge (and make it more fun).
Systems Used for Testing
Every example in the book was run on an actual network and the resulting output saved in a file for inclusion in the text. Figure 1.11 (p. 18) shows a diagram of the different hosts, routers, and networks that are used. (This figure is also duplicated on the inside front cover for easy reference while reading the book.) This collection of networks is simple enough that the topology doesn't confuse the examples, and with four systems acting as routers, we can see the error messages generated by routers.Most of the systems have a name that indicates the type of software being used: bsdi, svr4, sun, solaris, aix, slip, and so on. In this way we can identify the type of software that we're dealing with by looking at the system name in the printed output.
A wide range of different operating systems and TCP/IP implementations are used:
- BSD/386 Version 1.0 from Berkeley Software Design, Inc., on the hosts named bsdi and slip. This system is derived from the BSD Networking Software, Release 2.0. (We show the lineage of the various BSD releases in Figure 1.10 on p. 17.)
- Unix System V/386 Release 4.0 Version 2.0 from U.H. Corporation, on the host named svr4. This is vanilla SVR4 and contains the standard implementation of TCP/IP from Lachman Associates used with most versions of SVR4.
- SunOS 4.1.3 from Sun Microsystems, on the host named sun. The SunOS 4.1.x systems are probably the most widely used TCP/IP implementations. The TCP/IP code is derived from 4.2BSD and 4.3BSD.
- Solaris 2.2 from Sun Microsystems, on the host named solaris. The Solaris 2.x systems have a different implementation of TCP/IP from the earlier SunOS 4.1.x systems, and from SVR4. (This operating system is really SunOS 5.2, but is commonly called Solaris 2.2.)
- AIX 3.2.2 from IBM on the host named aix. The TCP/IP implementation is based on the 4.3BSD Reno release.
- 4.4BSD from the Computer Systems Research Group at the University of California at Berkeley, on the host vangogh.cs.berkeley.edu. This system has the latest release of TCP/IP from Berkeley. (This system isn't shown in the figure on the inside front cover, but is reachable across the Internet.) Although these are all Unix systems, TCP/IP is operating system independent, and is available on almost every popular non-Unix system. Most of this text also applies to these non-Unix implementations, although some programs (such as Traceroute) may not be provided on all systems.
Typographical Conventions
When we display interactive input and output we'll show our typed input in a bold font, and the computer output like this. Comments are added in italics.Also, we always include the name of the system as part of the shell prompt (bsdi in this example) to show on which host the command was run.
Throughout the text we'll use indented, parenthetical notes such as this to describe historical points or implementation details. We sometimes refer to the complete description of a command in the Unix manual as in ifconfig(8). This notation, the name of the command followed by a number in parentheses, is the normal way of referring to Unix commands. The number in parentheses is the section number in the Unix manual of the "manual page" for the command, where additional information can be located. Unfortunately not all Unix systems organize their manuals the same, with regard to the section numbers used for various groupings of commands. We'll use the BSD-style section numbers (which is the same for BSD-derived systems such as SunOS 4.1.3), but your manuals may be organized differently.
Acknowledgments
Although the author's name is the only one to appear on the cover, the combined effort of many people is required to produce a quality text book. First and foremost is the author's family, who put up with the long and weird hours that go into writing a book. Thank you once again, Sally, Bill, Ellen, and David.The consulting editor, Brian Kernighan, is undoubtedly the best in the business. He was the first one to read various drafts of the manuscript and mark it up with his infinite supply of red pens. His attention to detail, his continual prodding for readable prose, and his thorough reviews of the manuscript are an immense resource to a writer.
Technical reviewers provide a different point of view and keep the author honest by catching technical mistakes. Their comments, suggestions, and (most importantly) criticisms add greatly to the final product. My thanks to Steve Bellovin, Jon Crowcroft, Pete Haverlock, and Doug Schmidt for comments on the entire manuscript. Equally valuable comments were provided on portions of the manuscript by Dave Borman, Tony DeSimone, Bob Gilligan, Jeff Gitlin, John Gulbenkian, Tom Herbert, Mukesh Kacker, Barry Margolin, Paul Mockapetris, Burr Nelson, Steve Rago, James Risner, Chris Walquist, Phil Winterbottom, and Gary Wright. A special thanks to Dave Borman for his thorough review of all the TCP chapters, and to Bob Gilligan who should be listed as a coauthor for Appendix E.
An author cannot work in isolation, so I would like to thank the following persons for lots of small favors, especially by answering my numerous e-mail questions: Joe Godsil, Jim Hogue, Mike Karels, Paul Lucchina, Craig Partridge, Thomas Skibo, and Jerry Toporek.
This book is the result of my being asked lots of questions on TCP/IP for which I could find no quick, immediate answer. It was then that I realized that the easiest way to obtain the answers was to run small tests, forcing certain conditions to occur, and just watch what happens. I thank Pete Haverlock for asking the probing questions and Van Jacobson for providing so much of the publicly available software that is used in this book to answer the questions.
A book on networking needs a real network to work with along with access to the Internet. My thanks to the National Optical Astronomy Observatories (NOAO), especially Sidney Wolff, Richard Wolff, and Steve Grandi, for providing access to their networks and hosts. A special thanks to Steve Grandi for answering lots of questions and providing accounts on various hosts. My thanks also to Keith Bostic and Kirk McKusick at the U.C. Berkeley CSRG for access to the latest 4.4BSD system.
Finally, it is the publisher that pulls everything together and does whatever is required to deliver the final product to the readers. This all revolves around the editor, and John Wait is simply the best there is. Working with John and the rest of the professionals at Addison-Wesley is a pleasure. Their professionalism and attention to detail show in the end result.
Camera-ready copy of the book was produced by the author, a Troff die-hard, using the Groff package written by James Clark. I welcome electronic mail from any readers with comments, suggestions, or bug fixes.
W. Richard Stevens
rstevens@noao.edu
Tucson, Arizona
October 1993
0201633469P04062001
Detalles del producto
- Editorial : Addison-Wesley Professional; 37647th edición (1 Enero 1994)
- Idioma : Inglés
- Tapa dura : 576 páginas
- ISBN-10 : 0201633469
- ISBN-13 : 978-0201633467
- Dimensiones : 8 x 1.75 x 9.5 pulgadas
- Clasificación en los más vendidos de Amazon: nº108,020 en Libros (Ver el Top 100 en Libros)
- nº4 en TCP-IP
- nº9 en Conexión de Red
- nº3,696 en Desconocido
- Opiniones de clientes:
Información importante
Para informar un problema con este producto o vendedor, haz clic aquí.
Sobre el autor
Descubre más de los libros del autor, mira autores similares, lee blogs del autor y más
Opiniones de clientes
Las opiniones de clientes, incluidas las valoraciones de productos ayudan a que los clientes conozcan más acerca del producto y decidan si es el producto adecuado para ellos.
Para calcular la valoración global y el desglose porcentual por estrella, no utilizamos un promedio simple. En cambio, nuestro sistema considera cosas como la actualidad de la opinión y si el revisor compró el producto en Amazon. También analiza las opiniones para verificar la confiabilidad.
Más información sobre cómo funcionan las opiniones de clientes en AmazonOpiniones con imágenes
Filtrar opiniones por
- Español
- Inglés
-
Opiniones principales
Opiniones destacadas de los Estados Unidos
Ha surgido un problema al filtrar las opiniones justo en este momento. Vuelva a intentarlo en otro momento.
.
I have read TOO MANY books that use inaccurate or mismatched or generic INTERNETWORK terms. This book does an excellent job at being explicit and accurate in the use of terms and concepts, and in explaining them. Ohhhh, is that considered too academic. Well you do not want an IDIOT medical surgeon dropout doing surgery on you any more than you want an IDIOT unqualified network person working on your network.
.
I have met networking techs who do not know what a datagram is, or they get circuit and package switching concepts mixed up with connection and connectionless oriented concepts. Or they think IP is connection oriented, or they do not know what CSMA/CD and CSMA/CA are. I mean, Earth is round not flat. The sun is larger than the Earth. Paul Revere did NOT warn the British that the American were coming.
.
Ya, explicit commands or scripts or configurations are nice for a specific device or hardware or system, but ENGINEERS also need to know exactly what they are talking about and what they are doing as far as the ideas and concepts of TCP/IP. That is extremely critical!!!
.
You want a true ENGINEER, not a HOBBYIST, working on your network.
.
"What did you do?" OHHHH I connected this with that, and that with this, and configured that packet service to block this packet port and.... and I got this collision domain connected with that application... um...I had trouble getting that plug into that port, but I was able stick it in there anyway.... ummm everything should be working now...
.
That is why the Challenger space shuttle was lost and the Deepwater Horizon oil spill happened, because of the LACK of academic and technical and engineering appreciation. IDIOTS, or head honchos, doing something or giving orders or making judgement calls about something that they do not know enough about.
.
As for the down play of academics. You better know, you are not a network engineer if you do not have an actual engineering degree related to, or applicable to, the field of computer internetworking. You are just a hobbyist or at best a technician. But that is not the same as an engineer. People who down play the academic side of education or REAL engineering, do it to push the false idea that an engineering degree is not need to be an engineer.
.
TCP/IP is not a mystery. There is real 100% science and academics behind it. You just have to read and study it. Oh, also know that is exactly how TCP/IP started, with academics and the old ARPANET. The original ARPANET consisted of the University of Utah, University of California, and the Stanford Research Institute. If not for academics, TCP/IP would not exist at all!
.
Knowing what is what and what you are talking about is critical. Those who dismiss the academic side, obviously do not know what they are talking about.
This is one of the most thorough treatments of tcp/ip you'll find. I wondered what all could be mentioned in 8 chapters devoted just to tcp, but after reading this book I see tcp in a new light. I had a "working" understanding of tcp before (and I own Tanenbaum's "Computer Networks", which covers the physical layer in great detail), but there was something in the way Stevens explained the fundamental concepts about tcp that really drove home the ideas behind the design for me.
My only complaint, perhaps, is that a few of the protocols covered are quite outdated...but I'm still giving 5 stars since this book has been updated and my copy is almost 20 years old.
100% recommend the seller.
Opiniones más destacadas de otros países
But why do I have to write so much do make a review!!??....................................
You should not buy the volume 2 and 3 unless you really know what you are doing. :) For those with the programming background like myself volume 2 is very helpful to get a better understanding how certain features normally implemented (using BSD tcp stack example).