The course book covers the area sufficiently but the discussion on Path MTU Discovery is (nearly) missing (RFC 1191 covers it)
Kurose & Ross (3. edition): 4.4.1-3 The Internet Protocol (IP, ICMP, CIDR, NAT), 5.4 Link-layer Addressing (MAC Addresses, ARP, DHCP)
The Kurose&Ross book discusses some issues very briefly and nothing on the Path MTU Discovery. Again these are better available in the corresponding RFCs (see above).
How to work with IP addresses: some useful information can be found here
The course book discusses the TCP basics and Congestion Control but is not very clear in part nor detailed enough and the state-of-the-art congestion control mechanisms are discussed only briefly (e.g., NewReno Recovery, SACK Recovery, ECN) or not at all (e.g., Limited Transmit, Larger Initial Window). Also the need for Active Queue Management and RED as one of the widely used implementations of AQM are only briefly discussed. For full information on these refer to the corresponding RFCs and the RED paper (see above). For NewReno, the previous version of the RFC [RFC 2582] might be easier to follow than the current version [RFC 6582].
Kurose & Ross (3rd Edition): 3.5 Connection-Oriented Transport: TCP; 3.6 Principles of Congestion Control (excluding 3.6.3); 3.7 TCP Congestion Control
The Kurose&Ross book discusses only the basics but none of the state-of-the art congestion control mechanisms that are best available in the corresponding RFCs (see above).
The Comer book has decent discussion on the basics but IPv6 autoconfiguration is covered very briefly, but this information is available in RFC 4862.
Kurose & Ross (3rd Edition): Ch. 4.4.4 IPv6
The Kurose&Ross book discusses the basics but some issues only very briefly and some issues with old information (IPv6 Flow Label). Again these are better available in the corresponding RFCs (see above).
Content: Routing basics, Autonomous Systems, Intra and Inter AS Routing (IGP, EGP), Hierarchical Routing, Internet Routing and Routing protocols: RIP-1 and RIP-2 (RFC 1058, RFC 2453), OSPF (RFC 2328), BGP (RFC 4271)
The Comer book has decent discussion on the basics but it contains some unclear text and errors (e.g., description of RIP-2 Next Hop field usage (see correct explanation in Sec. 4.4 of RFC 2453 for RIPv2) and RIP-2 is covered quite briefly. In addition, partitioning an AS into areas, OSPF support for hierarchy within an AS (OSPF Areas) as well as description of different link state advertisement (LSA) types are not covered. Discussion on the missing OSPF features is avaiable in RFC 2328, Sections 2, 3 and 4, pp. 13-47.
Kurose & Ross (3rd edition): 4.5 Routing Algorithms, 4.6 Routing in the Internet,
Includes a brief description on OSPF areas. The discussion on Internet routing protocols is more accurate in the corresponding RFCs (see above).
Content: Broadcast and Multicast Routing Algorithms, IGMP (RFC 3376, [RFC 2236]), Overview of the Internet Multicast Routing protocols: DVMRP (RFC 1075), MOSFP (RFC 1584), CBT (RFC 2201, RFC 2189), PIM (RFC 4601, RFC 3973)
The Comer book has decent discussion on the basics though overview on the various Internet multicast protocols is very brief.
Kurose & Ross (3. edition): 4.7 Broadcast and Multicast Routing
Overview for MOSFP not available in the book.
Content: Mobility, Mobile IP (RFC 5944), Mobile IPv6 (RFC 6275)
The Comer book has decent discussion on the basics though Mobile IPv6 is missing (not required for this course).
Kurose & Ross (3. edition): 6.5 Mobility Management: Principles, 6.6, Mobile IP, 6.8 Wireless & Mobility: Impact on Higher-layer Protocols
Overview of Mobile IPv6 is not available in the book.
Content: Introduction to Multimedia Networking principles and requirements, RTP (RFC3550), RTCP (RFC3550), RTSP (RFC 2326), SIP (RFC 3261), Scheduling and Policing, Intserv (RFC 1633), RSVP (RFC 2205), Diffserv (RFC 2475, 3260)
The Comer book has quite short discussion on the topics but no additional material is required on this course. RTSP overview is missing but can be find in the Kurose&Rose book, for example. Comer book is a bit unclear on RSVP protocol resource reservations. The actual resource reservation is executed with the RESV message, not with PATH message.
Kurose & Ross (3. edition): Ch 7 (excluding 7.4.4)