Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements
Webcast-Catalyst9k
New Member

theory of RFC!!!!

Hi,

I wonder why people in Cisco always mention RFC like BGP,LSA OSPF etc!!!!???? ...Because I havent read in book that..

Do people in IT cisco need to know that???

And there are so many things to read too much ...sometime I guess may be book do not conteain this

Bye,

1 ACCEPTED SOLUTION

Accepted Solutions
Super Bronze

Re: theory of RFC!!!!

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.

1 REPLY
Super Bronze

Re: theory of RFC!!!!

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.

84
Views
0
Helpful
1
Replies
CreatePlease to create content