Re: v6ops-routing-guidelines ID

[Danny McPherson <danny@tcb.net>]

On Mar 19, 2007, at 5:06 AM, Marc Blanchet wrote:

> - thanks for comments
> - partial response below. more later.

Thanks for the prompt reply, I look forward to your
responses on the outstanding comments as well.

> > 2.6.  Default Route
> >
> >    The default unicast route (::) may be advertised in an IGP.  It  
> > must
> >    not be advertised in an EGP unless it has been requested by the
> >    recipient.
> >
> > How does one request a default route?
>
> well, that was the suggestion text from someone who provided  
> comment on the previous version. The intent of the suggestion was  
> to avoid the use of "downstream" which is ambiguous.  Do you have  
> any suggestion for text?

I might be able too suggest something if I understand
what the goal of such a statement would be.  I don't
recall anything similar along these lines in IPv4 (I do know
how IPv4 default routes are 'advertised' and why), and I'm
not sure how it's unique here.  Note also that one's "routing
policy" could specify that any prefix be interpreted as
default.

> > Where would operators find such a list if we're recommending they
> > filter these address spaces?
>
> it currently says newer versions of the normative references (that  
> is one way one can do and find).
> Any suggestion?

My point was that if we're asking folks to follow these routing
guidelines and possibly generate and deploy policy based on
them, they'll need a source for the input from which they could.
One would think IANA and the RIRs would be a good start, but
the IRRs and similar sources would be ideal - though require
much more explicit policy expressions.

-danny