Chuck:
Haven't you figured it out? Keep the RFC's next to the bed so they can put
you to sleep! No, seriously though - I am from the school where we should
know the theory behind it, not necessarily the bitwise detail. If we have
the theory behind it, know who is suppose to talk first, then what kind of
replies there should be - the general flow of the process - we *should*
know when there is a problem and the general area when troubleshooting. And
then if we have to, we can go to the RFC to look at the detail.
I am with you, I don't write the underlying code for how the equipment
behaves, so I don't believe I need to be able to recall the detail from
memory.
Ed
"Chuck Larrieu" <[EMAIL PROTECTED]> wrote in message
003801c07208$abb8e560$[EMAIL PROTECTED]">news:003801c07208$abb8e560$[EMAIL PROTECTED]...
> RFC2328 ( OSPF ver 2 ) almost done. Have modified my thoughts on it. Still
> seems to be a lot of repetition, but I believe I am beginning to
appreciate
> the complexity of the protocol.
>
> Seriously, for those of us browsing RFC's as part of our preparations,
what
> is it we should be learning?
>
> As someone who probably will not be writing router code ever, at what
point
> do I turn the page or just close it down entirely?
>
> Chuck
> ----------------------
> I am Locutus, a CCIE Lab Proctor. Xx_Brain_dumps_xX are futile. Your life
as
> it has been is over ( if you hope to pass ) From this time forward, you
will
> study US!
> ( apologies to the folks at Star Trek TNG )
>
> _________________________________
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
>
_________________________________
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
