Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
RFCs are mentioned because the are often the basis for actual standards. Sometimes vendor implementations don't implement everything in the RFC or they add features not in the RFC. Doing either often makes for problems if you try to mix vendor equipment (because they aren't all doing everything called for by the RFC).
Some RFCs can be difficult to understand, unless you have a lot of supporting knowledge. "Books" are often written to explain RFCs and provide examples on "how to", expecially using specific vendor equipment.
