First, a general comment on RFC's:  when there is an "Applicability 
Statement", "Framework", or "Roadmap" associated with the protocol 
specification, read them first. Some of the more complex families 
such as MPLS, IPSec, etc., also have requirements and architecture 
documents worth reading.

I would add to these:

RFC 1812 Requirements for IPv4 routers

RFC 1925 The Twelve Networking Truths.

Some RFCs are in major revision, and the drafts may be more useful. I 
would recommend BGP students go to the IDR working group page at 
http://www.ietf.org and get the most recent draft (I think it's 18, 
but it may have gone to a yet newer round). Without false modesty, 
also go to the BMWG working group page and get the latest revision of 
the "terminology for single-router BGP convergence," where we've 
cleaned up some of the more confusing BGP terminology.  We should 
have an updated draft, about ready for RFC, up within a week or two.

RFC 1517-1520 are the fundamental basis for CIDR/VLSM.  RFC 1878, 
"Variable Length Subnet Table For IPv4", has excellent conversion 
tables and examples. My RFC 2072 also gives addressing strategies for 
renumbering routers.

In fact, here's the timeline for RFCs for IP addressing:

760        791             850            1517-20
Fixed      Classful        Subnetting     CIDR/VLSM
Network    Addressing
Field

>All the April 1st RFCs notwithstanding, the following are classic RFCs that
>every network engineer should know about:

And some of the April 1 RFCs are classics that have something to 
teach. 1194 is an excellent example of how IP is mapped onto a 
specific transmission system.

>
>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)
>
>HTH
>
>Priscilla
>
>At 10:43 PM 4/1/02, D'Wayne Saunders wrote:
>>Hi,
>>          Can anyone recommend a few core rfc's that are wothwhile reading
>>  in regards
>>to cisco study.
>>tia
>>
>  >Dwayne Saunders

-- 
"What Problem are you trying to solve?"
***send Cisco questions to the list, so all can benefit -- not 
directly to me***
********************************************************************************
Howard C. Berkowitz      [EMAIL PROTECTED]
Chief Technology Officer, GettLab/Gett Communications http://www.gettlabs.com
Technical Director, CertificationZone.com http://www.certificationzone.com
"retired" Certified Cisco Systems Instructor (CID) #93005




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=40176&t=40135
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to