Bryan J Smith wrote:
On Wed, Jul 16, 2014 at 8:48 AM, Alessandro Selli
<[email protected] <mailto:[email protected]>>wrote:
It's foundational to what end? System administration? Network
administration? Security? LPIC-1 is not foundational to everything
Linux. It's foundational to an end user perspective and to basic
Linux-box setup and troubleshooting. IMHO these users need not know
about RFCs
Then why is IETF RFC 1918 part of Object 109.1 in Exam 102?
Is it?
http://www.lpi.org/linux-certifications/programs/lpic-1/exam-102/
109.1 Fundamentals of internet protocols
* *Weight: * 4
* *Description:* Candidates should demonstrate a proper understanding
of TCP/IP network fundamentals.
Key Knowledge Areas
* Demonstrate an understanding network masks.
* Knowledge of the differences between private and public "dotted
quad" IP-Addresses.
* Setting a default route.
* Knowledge about common TCP and UDP ports (20, 21, 22, 23, 25, 53,
80, 110, 119, 139, 143, 161, 443, 465, 993, 995).
* Knowledge about the differences and major features of UDP, TCP and
ICMP.
* Knowledge of the major differences between IPv4 and IPV6.
Terms and Utilities
* /etc/services
* ftp
* telnet
* host
* ping
* dig
* traceroute
* tracepath
------------------------------------------------------------------------
Does not look like one is ever going to be asked: "What RFC covers
Address Allocation for Private Internets"?
A) 822
B) 1879
C) 1918
D) 1945
E) 1771
[...]
Reverse DNS delegation zones
I'm _not_ talking about Reverse DNS delegation zones.
I'm talking about why we would avoid using CIDR /8, /16 and /24
examples for IPv4 and point out they are the Classful A, B and C subnets.
We do *not* mandate avoidance of CIDR /8, /16 and /24 IPv4 usage, we
just agreeded to leave out of the exam any question directly targeting
network classes.
I _only_ mentioned that the Classful subnets are required for many
applications and services, only one being in-addr.arpa zones. There
are many more examples.
IN-ADDR.ARPA zones deal with DNS administration (i.e.Exam 202, topic:
207.2 Create and maintain DNS zones (weight: 3)). Not with "Configure
client side DNS" (Exam 102, topic 109.4). What do you need IN-ADDR.ARPA
zones for when you have to configure /etc/hostname, /etc/hosts,
/etc/resolv.conf or /etc/nsswitch.conf? For network interface settings,
knowledge of CIDR is enough. Then, again, everyone is free to teach
more than is required.
And that includes why there are 3 different sets of private
reservations in IETF RFC1918 for IPv4, which _is_ in LPIC-1. ;)
IPv4 is, RFC-1918 is not.
What really matters is not how difficult is is to explain, but whether
there are going to be questions asked in the exam. Then, like Anselm
just pointed out, each one will be free to beef up his/her own
courseware the way they like (and can).
Any junior sysadmin should know what they are looking at when they run
"ip addr" on a system. That's my strongest, educated opinion having
dealt with junior sysadmins.
Output of ip addr is perfectly understandable with knowledge of CIDR
alone, no RFC or IN-ADDR.ARPA zones are needed.
I've always looked at LPIC-1 as the foundation of what a junior
sysadmin needs to understand to function in an Enterprise environment.
Is LPIC-1 really targeted at the Enterprise environment? Many, most
things in LPIC-1 are indeed central to use of Linux in an Enterprise
environment, but being something used in such an environment is not,
that I know, the rationale for it's inclusion in LPIC-1 objectives.
Otherwise, there'd be tons of things missing.
To this end, CIDR is enough.
Please explain how CIDR is enough to understand IETF RFC1918.
RFC-1918, *any* RFC actually, is *not* mentioned in any LPIC-1 objective.
Also please explain how the Classful subnets are going to distract,
let alone don't complement, RFC1918.
I never said they would.
I mean, there's a block reservation for each A, B and C for a reason. ;)
And there's a TCP/IP port reservation for Gopher for a reason.
Should the Gopher protocol be included in the objectives, next to the
HTTP and FTP protocols?
Regards,
Alessandro
_______________________________________________
lpi-examdev mailing list
[email protected]
http://list.lpi.org/cgi-bin/mailman/listinfo/lpi-examdev
