On Tue, 10 May 2016, David Miller wrote: > Every single variable name and function name dealing with this IP > option uses "srr", therefore I don't think we should adjust the > documentation either. > > "srr" covers both the loose source route option and the strict source > route option.
Now that I know where the 2nd "r" comes from, the "srr" makes sense. So yeah, SRR it is. Maybe a hint to the correct RFC would help, but if nobody else complained yet, I guess it's not really worth the commit. Thanks, Christian. -- BOFH excuse #255: Standing room only on the bus.
