<< 1 >>
Rating:  Summary: Ok but not so great Review: I had high hopes for this book but after reading the book, it left me craving for more. I think its because of the subject matter itself. QoS is an elusive topic and the war of religious proportions between IP and ATM proponents make it even more vague at times. The first few chapters are a good introduction for someone new to the topic of QoS. The author(s) lost me on the Integrated Services topic. As for later chapters, for example, MPLS, the description is just so so. Definately 'Switching in IP networks' by Rekhter is a mother on that topic. Other than that, lot of editorial and spelling mistakes. Wake up Wiley Publishing! On page 83 for instance, spell checker did not catch 'theto' and 'layer 813'.
Rating:  Summary: QoS internet Review: I need the mean of QoS internet, aplications, traffic, RSVP
Rating:  Summary: QoS internet Review: QoS is one of the currently _hot_ buzzwords that upper management reads about, perhaps in InfoWeek or the like. But what does QoS mean exactly? Although this book (the only one of its kind as far as I know) is short on practical examples, it shines when defining the networking/business definitons (& lack thereof) in describing QoS. I have used this book to help define the terms we use when discussing the outcome of implementing custom prioritization on a global 25K node network. Oftentimes, in any large organization, defining a standard set of concepts is key to strategic planning - it's the old elephant/blind men story. This book helped me to define & , more importantly, manage expectations. In addition, it has proven useful in our procurement planning. If you are looking for sample configs, then go to CCO, or Bay or whatever. In fact, if you are simply looking for configs, then you probably should not be attempting many of these CoS implementations; because, unlike router configuration, these techniques could be more appropriately termed, "router tuning". I enjoyed the read & found it well written (I've edited several technical books). Other books will be written concerning this topic, as QoS is a rapidly moving target. Ferguson & Huston have set the baseline.
Rating:  Summary: Good coverage but not well written Review: The book covers the topic area well but is difficult to get through as it is not written very well. They examples are not that great either. For example, when describing how a leaky-bucket algorithm works, they never refer to the obvious physical example. I will note that all the engineers I work with in the QoS area love the book.
<< 1 >>
|