In developing the Partner training on RHEL7, I'll give some insights I came to here.
On Tue, Jul 15, 2014 at 3:34 PM, Fabian Thorns <fab...@thorns.it> wrote: > I'd consider CIDR the only possible approach there days, too. > Yes, everything is, essentially, "classless" these days. However, one cannot just ignore the reality that the IPv4 classes *do* exist. I.e., IANA still assigns, or rather, assigned (now that they are all assigned as of 2014) IPv4 blocks by Class. So while you cover CIDR by default, you still need to point out the IPv4 A, B and C classes. This does > however not mean we shouldn't communicate clearly what we expect from > the candidates. It may be better to mention CIDR or VLSM (I personally > prefer CIDR) as our understanding of 'subnetting'than to make candidates > feel well-prepared though their subnetting knowledge is classful only... > Basically, the concept of subnetting and supernetting are no more. Everything is now CIDR. Sure it is, but when taking into consideration IPv6 prefix lengths like > /48, /56, /64, ... the number or "standard netmasks" becomes longer > anyway. So understanding the principle of classless subnetting one time > makes everything else pretty straight forward. Understanding what a subnets isand knowing how to determine if a host > belongs to a subnet or is captured by a given route is essential for > network troubleshooting. In my training, I merge IPv4 and IPv6 into one section. BAM! Done. We're at the point when a sysadmin looks at an interface, they are looking at both, and several considerations. E.g., the topics lists I include are: - Physical v. Logical v. Transport Addressing - MAC-48 (including IEEE OUI) - EUI-64 (most common today, subject to change) - MAC hex v. IPv4 dec v. IPv6 word hex nomenclature - Common CIDRs (which would include the classes) - IPv4 /8, /16, /24, IPv6 /48 and /64 (w/56 common) - Loopback (LO), including IPv4 net v. IPv6 unicast - Link Local (LL) addresses - IPv4 Private v. IPv6 Unique Local Addresses (including ULA Global ID) - UDP, TCP and transport addresses (ports/sockets) In reality, this all fits in one, single section. I honestly don't know why most people break out IPv6 today, because there's just so much overlap, and just so much reuse. Especially when the course/exam is not one on networking, but elementary knowledge. Literally, today, sysadmins need to know what loopback, link local and private/unique local are, including their reserved ranges and CIDR, along with UDP/TCP concepts, for 98% of what they do. -- bjs
_______________________________________________ lpi-examdev mailing list lpi-examdev@lpi.org http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
