RFCs Books

If you are a MIB network manager, developer or user, you need this book. It will help network managers to identify bad MIB's, developers to write correct MIB's, and users to repair MIB's. Novice or expert, there's something in this book for you.

There are many illustrations, screen shots, and examples of actual MIB's. This is one of the easiest SNMP books to read and understand because of its excellent organization. The author starts with basic concepts and builds from there. And, because this book provides such a clear and concise guide to MIB's, it is an excellent companion to "Essential SNMP" by Mauro and Schmidt.

A well written, logically organized text targeted at developers and end-users.

The author lays a strong foundation with the SNMP tutorial followed by a meticulous, step-by-step description of how to construct high quality MIBs. He has managed to balance the need to cover advanced concepts without glossing over the basic concepts. The text works as both an instructional manual and a reference.

I strongly recommend that you purchase this text. Personally, I keep it within arm's reach.

Finally the book on MIBs outlining concise MIB construction techniques using ASN.1 language. The SNMP MIB Handbook by Larry Walsh is very well written and conveys much of the same information presented in his training courses. Now everyone from product supervision to MIB developers to users of developed MIBs can have this industry information in their hands. As a Network Engineer, I find many manufacturers enterprise MIBs to be chockfull of errors as well as deficient in providing the kinds of information essential to network management. Now that a book actually details these MIB short-comings, that this book will become de-facto reading for those doing this essential development. There are many references to common and not so common developmental mistakes as well as composing MIBs to the highest standard. While it is understood that the MIB is basically a map of the available data on the device to be managed and that the device agent is part of this management, perhaps the highlights within this book will be beneficial to those developing agent software as well.
The book will help Network Engineers determine causes and fixes for poorly written MIBs. Test tools and methodology are a significant focus and apply to all levels of use and development. The information presented in this respect cannot be obtained anywhere else except through years of trouble-shooting effort.
This book is highly recommended reading for those involved in all levels of SNMP understanding, development and use.

SNMP MIB Handbook is an essential guide for understanding and implementing MIBs.

The text is well written, structured logically, and presents concise details and equal coverage for both SNMPv1 and SNMPv2 protocols.

Ample examples are provided throughout to assist Developers in understanding v1 and v2 syntax differences.

The topics covered in great detail are MIB syntax and structure
(including derived types), Traps, Indexes and Tables, and Troubleshooting.

This is a must-have book for Engineers responsible for SNMP management and development.

The SNMP MIB Handbook by Larry Walsh is a must-have book whether you need to use existing MIBs or you need to develop your own MIBs. This book is written for administrators and developers by a developer and educator. A first glance through the book might seem intimidating due to the amount of material covered. It is full of practical information that will ensure that your MIBs are written correctly and will work with the various SNMP managers out there.

There are references to the MIB-related specifications (RFCs) as well as Web sites dedicated to the support of MIB development. Also, tools for developing and verifying your MIBs are listed. Most topics are followed by at least one example and there is an enterprise-level MIB example. Where ever necessary, the differences between the SNMP messaging versions and the SMI versions are detailed. Exercises test your understanding of the material in each chapter.

This book brings together in one place the information needed to efficiently develop clean MIBs. There are hints and recommendations on how to produce the best MIBs. Extremely useful checklists ensure a good process is being used, including one for diagnosing problems and one for the whole MIB design process.

I've been a fan of Merline Lovelace and her military thrillers for a while, and I loved the incorporation of the paranormal. She makes Mark's abilities seem real and an essential part of the story. The work is sensual without being overly graphic, and Mark's sense of humor is priceless. I like the way both Taylor and Mark are strong alpha characters without the trait feeling forced and without either overwhelming the other. Kudos for a fast and wonderful read!

The Air Force Office of Special Investigations assigns Captain Taylor Chase to learn if scientist Dr. Oscar Hayes is being forcibly held on a Caribbean fortress near St. Kitts. Two months ago, he vanished while working on a top secret government project; he just resurfaced apparently held by or voluntarily joined a consortium planning to sell genetically engineered organs as human harvests on the black market.

To gain access to the island, Taylor heads to Princeton, New Jersey to try to persuade her former graduate professor at the University of Michigan Dr. Mark Wolfson to help her as he has worked closely with Hayes although she has doubts about working with him as she was his lab assistant and lover until she realized the mind games he played with her. Mark reluctantly agrees to pose as her lover. Along with his loyal husky Tikal, they head to the Eastern Caribbean where the pair must deal with their attraction enhanced by their telepathic connection as much as by preventing a billionaire's evil plan from occurring.

Known for her exhilarating military romantic suspense tales, Merline Lovelace adds a paranormal spin with Mark's ESP skills. Fans will appreciate the lead couple's banter as they argue, fuss and love mentally and physically, which makes his abilities feel genuine; all this inside a strong suspense thriller.

Harriet Klausner

This is a compilation of the best April Fools jokes created by the IETF, the group that creates the standards for how the Internet works. The best humor for the geek in your life, or a great conversation starter at a lan party. Also has commentary from Limoncelli and some other internet gods. Worth many geek points - full of lulz!!

Although Essential Email Standards is intended for the Internet messaging technician, even non-techies like myself can benefit from its exhaustive and comprehensive coverage of all the major Internet protocols and RFCs. Loshin provides the latest information on all the Internet messaging standards, as well as a complete description of the standards making process.

The book is also extremely well organized and laid out, with plenty of diagrams, tables, sidebars, and notes. The only disappointing aspect of the book is the skimpy index at the end. Perhaps this is the publisher's way of encouraging readers to use the CD-ROM and Adobe PDF Reader supplied with the book.

Indeed, searching for key words and phrases with the Adobe Reader is a breeze--you just slide the CD-ROM into your computer, double click the installation file, and away you go. I found one of the RFCs I was looking for by simply clicking one of the hyperlinks embedded in the digital copy of the text.

This review concludes that Essential Email Standards succeeds in making highly technical email standards practical and easily accessible.

This is an exciting book by Alex Revel. It is a true historical book since all the material used is taken from the official reports of the RFC/RAF 56th squadron and pilot letters to their friends/relatives. The squadron history is presented month by month, from March 1916 to November 1918. All the flights are listed for each day together with greater detail about the most interesting ones (including the flight that killed Werner Voss). Statistics about squadron commanders, airplanes (including all airplane serials used by the squadron), aerodromes, victories, markings,.... are presented at the end of the book together with authors research about Balls death, the "Greentail" (the albatros pilot who fought the pilots of the squadron several times during its stay in France) plus some additional stories. Overall this book represents very exhaustive research, yet instead of being written in a form of tedious listing of historical facts, it more resembles the style of an exiting war novel.

Fighter aces are one of the most fascinating elements of military aviation history. Books detailing their exploits continue to be best-sellers. In this 1996 Grub Street volume, noted author Norman Franks concentrates on just one aspect of WWI fighter ace history, unraveling how Allied and German aces died.

In some 200-odd pages, Franks details the deaths of over 300 British, French and German aces from 1915 to 1918. Death claimed those pilots in many ways. Some, like Oswald Boelcke, died in mid-air collisions; James McCudden and others died in 'operational accidents' when their aircraft faltered. Still others fell to ground fire (Frank Luke, Edward Mannock and Manfred von Richtofen). A few were lost in mano-a-mano fights, the classic example being Lanoe Hawker vs. Richtofen. Most however were lost in the swirling, multi-bogey dogfights that characterized WWI air combat. Due to the very nature of those fights, Franks can often only indicate which opposing pilots made claims and which may have been the victor over the ace downed.

In any case, WHO DOWNED THE ACES IN WWI? is a fascinating book, part military history, part detective story. Air combat enthusiasts will want to add it to their bookshelves. Highly recommended.

For the past decade or so, my desk has been inundated by laser-printed RFCs. Picked up from the IETF site. Loose, frequently out of numerical order, and impossible to handle. Now Pete Loshin has assembled all the important security RFCs in a large, handy book. It's both well laid-out and handy. There might have been a bit more introductory material, but the accessibility of the RFCs makes this a must have. And I can recycle over a thousand sheets of paper.

A lot of people probably figure, why spend the $s for a book that's mostly RFCs--after all, they're all available online for nothing. But if you've ever spent much time working with RFCs, you probably also have a ton of them printed out and filled with Post-IT notes (like I do). It's definitely worth it to have them all printed and bound AND INDEXED. I wish I'd a thought of doing this.

It is nice to have all these RFCs(request for comments) in one book to help those who implement not to overlook some aspects of the implementation like say how to store a Java object in ldap directory service hopefully using JNDI and also how to find if your choice of ldap solution is 100% pure ldap. Not to mention understanding the real security of the ldap offered to systems, users and applications. What is the real Enterprise solution. I hoped this protocol has another friendly name like FarLook or WithinLook or even Enterprise Superman. Do not forget to consider the add-on ldap based applications, there are 30+ security apps. Good luck. ldapguru@yahoo.com

...can sometimes be a difficult task. Fortunately, the complier(s) of this big book of RFCs have done a great job at presenting the standards, in a single volume so when you are bored on a 6 hour flight, you can catch up on RFC 1617 and pour over the alias object class, or choose another and investigate what that cryptic attribute was *really* created to do, software vendors be damned :)

Overall, I think this is a great reference to have if you are an LDAP architect, developer or implementor, although not for the average person who is just looking at getting some knowledge of LDAP on the surface... Exactly what was needed!

This book is titled "Big Book of IP Telephony RFCs" and it is just that. Expect no more and no less. Plain RFCs printed on paper and sometimes condensed (not much, if you have not read the entire RFC and well, then you might even miss the omissions).
The RFCs featured are the major ones used in telephony namely (or numberly!) - 1889, 2303, 2458, 2543, 2658, 2705, 2719, 2804, 2805, 2806, 2824, 2833, 2846, 2848, 2871. So you can even read them when you are not near your computer.
So much so for the good part, now the bad:
1. Font: It is the same as that at IETF website - plain old typewriter and no variation anywhere. Adds a bit of pain to reading. While type-setting the book they could have atleast used nice font and bold face etc at some places.
2. Content page: No page numbers! It is no big deal but atleast they could have put that so it seemed more like a book.

These RFCs are *THE* source material for IPv6 addressing, and Peter Salus has collected all the relevant ones here. Also included are some chapters about topics you simply won't find anywhere else--and a killer index (though the introduction sheds no light on why the included RFCs were chosen).

If you're interested in IPv6 addressing, this is the book to buy.