Good advice, Chris, and others. I don't want to scare anyone, but I think if you work in the networking field, you should have scanned the following RFCs:
RFC 760: DoD Standard Internet Protocol (IP) [made obsolete by RFC 791, but still worth reading] RFC 768: User Datagram Protocol (UDP) RFC 791: Internet Protocol (IP) RFC 792: Internet Control Message Protocol (ICMP) RFC 793: Transmission Control Protocol (TCP) RFC 826: Ethernet Address Resolution Protocol (ARP) RFC 854: Telnet Protocol Specification RFC 950: Internet Standard Subnetting Procedure RFC 959: File Transfer Protocol (FTP) RFC 1001: Protocol Standard for a NetBIOS Service on TCP/UDP Transport: Concepts and Facilities RFC 1002: Protocol Standard for a NetBIOS Service on a TCP/UDP Transport: Detailed Specifications RFC 1034: Domain Names—Concepts and Facilities RFC 1058. Routing Information Protocol (RIP) RFC 1122: Requirements for Internet Hosts—Communication Layers RFC 1661: The Point-to-Point Protocol (PPP) RFC 1700: Assigned Numbers RFC 1752: The Recommendation for the IP Next Generation Protocol RFC 1757: Remote Network Monitoring (RMON) Management Information Base (MIB) RFC 1771: A Border Gateway Protocol 4 (BGP4) RFC 1812: Requirements for IP Version 4 Routers RFC 1905: Protocol Operations for Version 2 of the Simple Network Management Protocol (SNMPv2) RFC 1918: Address Allocation for Private Internets RFC 1939: Post Office Protocol (POP), Version 3 RFC 2021: Remote Network Monitoring Management Information Base Version 2 using SMIv2 (RMONv2) RFC 2060: Internet Message Access Protocol (IMAP), Version 4rev1 RFC 2236: Internet Group Management Protocol (IGMP), Version 2 RFC 2328: Open Shortest Path First (OSPF), Version 2 RFC 2390: Inverse Address Resolution Protocol (Inverse ARP) RFC 2453: Routing Information Protocol (RIP), Version 2 RFC 2460: Internet Protocol, Version 6 (IPv6) Specification RFC 2462: IPv6 Stateless Address Autoconfiguration RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers RFC 2475: An Architecture for Differentiated Service RFC 2516: A Method for Transmitting PPP over Ethernet (PPPoE) RFC 2608: Service Location Protocol (SLP), Version 2 RFC 2616: Hypertext Transfer Protocol (HTTP), Version 1.1 RFC 2821: Simple Mail Transfer Protocol (SMTP) RFC 3022: Traditional IP Network Address Translator (Traditional NAT) Howard would probably add to the list!? ;-) You certainly shouldn't memorize the RFCs, but you should understand the concepts in them. I agree with Howard that you also don't need to memorize RFC numbers. With time, you'll get to know a few of them, but why fill your brain with such info when you can find lists like mine all over the Internet. In fact, I'll add my list to my Web site...... Wow. Good idea. ;-) Stay tuned.... _______________________________ Priscilla Oppenheimer www.troubleshootingnetworks.com www.priscilla.com chris kane wrote: > > IMHO, I feel you should be familiar with RFCs. Regardless if > the exam asks > questions about them or not. In order to understand the > intended use and > possible vendor interoperability issues of implementation, you > should have > atleast scanned several of them. What's better, if you find the > RFCs a bit > hard at first, then read books such as John T. Moy's OSPF > Anatomy of an > Internet Routing Protocol. Since Moy is given great credit for > contributions > to OSPF, his book helped me understand what they did and why. > It's a nice > precursor into reading the RFC. Similarly, I like Halabi's > Internet Routing > Architectures and John W. Stewart's BGP4 Inter-Domain Routing > in the > Internet. Both of these help with clarifying BGP. > > Nothing helps understanding a routing protocol and it's > behaviors more than > trying to equipment from 2 different vendors to talk the way > you intend them > to. Although your question was in regards to the IE written > exam, think > bigger. Trying to see a bigger picture helped me to understand > how Cisco did > things. > > -chris > > > ----- Original Message ----- > From: "Howard C. Berkowitz" > To: > Sent: Friday, December 27, 2002 12:23 PM > Subject: Re: CCIE Written ..plz help [7:59829] > > > > At 11:31 AM +0000 12/27/02, irfan siddiqui wrote: > > >Hi, does anyone know if we have to memorize RFC's for the > CCIE written > exam. > > >Do they ask things like RFC's. Also if anyone has attempted > the exam > > >recently can they give any advice about wat u need to know > and wat stuff > to > > >memorize if any.I am scheduled to give the exam next week > and i still > feel > > >shaky. Thanks in advance . Irfan > > > > I've WRITTEN RFCs and don't have them memorized. That being > said, > > UNDERSTANDING key RFCs is important. If you can't easily read > a > > protocol RFC at the general, not developer level, you may not > be > > ready for the written. Yes, I agree that finite state > machines won't > > be explicitly tested on the written, but I think it's very > hard to > > understand protocol behavior without a sense of FSMs, TLVs, > etc. > > > > Memorizing the numbers of RFCs? Maybe, although it's foolish > if > > Cisco expects that. There even can be subtleties -- people > usually > > say the first RFC describing IPv4 was RFC791, but that was > the first > > practical one -- RFC760 came a little earlier. > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59844&t=59829 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
