Good additions to my list of core RFCs, Howard. I added the RFCs that you mentioned and a few from Kevin C that were sent offline (IPSec, HSRP, and VRRP).
Thanks for telling us about RFC 3439, "Some Internet Architectural Guidelines and Philosophy." It's great! I highly recommend it. Here's a URL: http://rfc.sunsite.dk/rfc/rfc3439.html Two concetps from the RFC strike me as relevant to discussions on this list: 1) The discussion of the unique challenges assoicated with large-scale network design. "Building such a network is a different activity (and hence requires a different skill set) than building a small to medium scale network." Large-scale systems are more prone to problems associated with amplification and coupling (see the RFC). CCIE R&S focuses on medium-scale enterprise networks and doesn't prepare us well for building large-scale networks, as you have said many times, Howard. 2) The wonderful sacrilegious discussion about layering being harmful! Everyone must read this. I plan to quote it the next time the OSI model comes up in a discussion. :-) Here's some of the best parts: "Layering of this type does have various conceptual and structuring advantages. However, in the data networking context structured layering implies that the functions of each layer are carried out completely before the protocol data unit is passed to the next layer. This means that the optimization of each layer has to be done separately. Such ordering constraints are in conflict with efficient implementation of data manipulation functions. One could accuse the layered model (e.g., TCP/IP and ISO OSI) of causing this conflict. In fact, the operations of multiplexing and segmentation both hide vital information that lower layers may need to optimize their performance. For example, layer N may duplicate lower level functionality, e.g., error recovery hop-hop versus end-to-end error recovery. In addition, different layers may need the same information (e.g., time stamp): layer N may need layer N-2 information (e.g., lower layer packet sizes), and the like [WAKEMAN]." Good stuff. Thanks, Priscilla Howard C. Berkowitz wrote: > > At 6:35 PM +0000 12/27/02, Priscilla Oppenheimer wrote: > >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 NamessConcepts and Facilities > > RFC1035 Domain Operators Guide > > >RFC 1058. Routing Information Protocol (RIP) > >RFC 1122: Requirements for Internet HostssCommunication Layers > > RFC1517-1520: these are the fundamental documents for CIDR. > > >RFC 1661: The Point-to-Point Protocol (PPP) > >RFC 1700: Assigned Numbers > > Technically, this has been made Historic and the IANA > website is > definitive. > > >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) > > 1771 is really pretty awful compared to industry > implementations. Go > to www.ietf.org, navigate to the IDR Working Group, and get the > latest draft of the BGP revision (draft 18 or 19, last I looked) > > >RFC 1812: Requirements for IP Version 4 Routers > > > > 1878 Variable Length Subnet Table For IPv4. T. Pummill, B. > Manning. > December 1995. > > >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 > > RFC2072, Router Renumbering Guide. *cough, cough* > > >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 > > > > 2650 Using RPSL in Practice. D. Meyer, J. Schmitz, C. Orange, M. > Prior, C. Alaettinoglu. August 1999. > >>> starting point for WHY BGP does what it does > > >RFC 2821: Simple Mail Transfer Protocol (SMTP) > > > > >RFC 3022: Traditional IP Network Address Translator > (Traditional NAT) > > > > 3439 Some Internet Architectural Guidelines and Philosophy. R. > Bush, > D. Meyer. December 2002. > > > > >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.... > > > > I will add the caveat that Cisco sometimes has asked for > numbers, and > don't necessarily keep them updated. > > A stray aside -- Priscilla, you know the people, and some > others on > the list may as well. A group of us were driving from San > Diego to > Los Angeles for Cisco University, and, rather late, checked > into the > hotel. John Livengood asked for my room number, and I said "I > can't > remember offhand, but it's one of the CIDR RFCs." > > I dug out the key and it was 1518. John told me I was weird. > > Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=59893&t=59829 -------------------------------------------------- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
