|
Barbara, >This is non-normative language, in the abstract of RFC 4191.
Normative references to RFC 4191 purely apply to the protocol, and do not apply
to non-normative statements in that RFC about how one might or might not
configure the elements of that protocol. The goal >of
not having too many routes advertised is worthy, and does need to be given
serious consideration in the design of any algorithm that would derive the
routes in an automated manner. Sure, we can grant you that the Abstract is non-normative
language . However, there is still Normative language in section 4
for RFC 4191 I have shown below. [The
preference values (both Default Router Preferences and Route Preferences)
SHOULD NOT be routing metrics or automatically derived from
metrics: the preference values SHOULD be configured.] A minor point first. When did any admin automate
configuration of RA on a router? Since an RA is manually configured on a
router it makes sense to manually configure any extensions to the RA like the
MSR. Anyhow, as I said before, the SP doesn’t even have all
the routing and prefix information available for what’s what multi-homed
devices will be deployed in the home, the MSR cannot even be derived by the SP,
let alone the SP automating derivation and sending of the MSR. Hemant |