![]() No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein. The author and publisher have taken care in the preparation of this book, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. Where those designations appear in this book, and the publisher was aware of a trademark claim, the designations have been printed with initial capital letters or in all capitals. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Patterns in Network Architecture A Return to Fundamentals JOHN DAY If only there weren't so many distracting editorial errors. This book ought to be used as a textbook! It is highly recommended to everyone working in the field. The rest of the book goes on to develop these thoughts, which in my view is a real breakthrough in clarity. Two data transfer protocols: Relaying and multiplexing protocolsĪnd error- and flow-control protocols with different policies This would seem to indicate that there are really only three fundamental types of protocols: ![]() Therefore, to guarantee reliability, there must always be an error-control protocol on top of a relaying protocol.Ģ. Relaying always creates the opportunity for PDUs to be lost. The MAC layer does relaying and multiplexing, the data link layer does "end-to-end" error control the network layer relays, the transport layer does end-to-end error control mail protocols relay, hmm no end-to-end error control and sometimes mail is lost.we can make two observations:ġ. two types of protocols tend to alternate in architectures. Rather than a shortcoming, however, I think his strong opinions and sarcastic wit are a benefit any reader can see clearly where John is coming from and can research the "other side" if it seems important. Like many others in the field, John has strong opinions and axes to grind. But I hope to hear sometime that an implementation has succeeded. And we know that the devil is always in the details. I haven't really done the hard work necessary to figure out if it really will work, and I don't expect to. While there are many things to argue over, the architecture Day describes sounds like it should work, and if it does work should be a vast improvement over the current ramshackle protocol structure. ![]() I've just finished "Patterns in Network Architecture" and I'm impressed. I have a lot of first-hand experience with where we are today and how we got here. For about a year I was the chair of of the ISO Presentation Layer committee. I was involved in the design of the ARPAnet Protocols and worked on Internet protocols. ![]()
0 Comments
Leave a Reply. |