It really depends on what information you're looking for. I think RFCs
serve as a great reference to some of the deep technical aspects of many
standards and protocols.
For example, if I was curious about how exactly stub areas are signaled in
OSPF, I would refer to the RFC2328, and quickly search for the topic I was
looking for
ExternalRoutingCapability
Entire OSPF areas can be configured as "stubs" (see Section
3.6). AS-external-LSAs will not be flooded into stub areas.
This capability is represented by the E-bit in the OSPF
Options field (see Section A.2). In order to ensure
consistent configuration of stub areas, all routers
interfacing to such an area must have the E-bit clear in
their Hello packets (see Sections 9.5 and 10.5)
That took about 30 seconds to find. There are certainly some RFCs that
are worth reading all the way through ( such as the one above).
However some of them do not read so well, and serve much better as a
quick dictionary of facts about the topic.
-Yuri
On Tue, Dec 11, 2012 at 8:11 AM, Kyle Byrne <kyle_at_wtds.org> wrote:
> When reading RFCs, is there a specific part that I need to focus in on.
> There is a lot of information in these. Any help suggestions?
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
Blogs and organic groups at http://www.ccie.net
Received on Tue Dec 11 2012 - 08:36:10 ART
This archive was generated by hypermail 2.2.0 : Tue Jan 01 2013 - 09:36:53 ART