Re: The trouble with route announcement updates., "Neil J. McRae" neil@localhost

[Jacques Caron <]

Hi,

My 2 cents on the subject:
- for "smaller" peers (up to a few hundred routes), build strict 
prefix-lists based on IRR registrations. Update nightly.
- for "larger" peers, build as-path filter-list (in the form "permit _AS$") 
based on IRR registrations. Update nightly.

Always register routes in an IRR before 48 hours before announcing them.

Jacques.

At 13:55 10/10/00, Neil J. McRae wrote:

> Colleagues,
> Recently, we have found issues with the constant requirement
> to send individual new prefix/new as announcements to our peers and
> have the peers act upon them.
>
> We find out more often than not that these are not acted upon or
> that they are mis-configured causing connectivity problems to
> all our respective customers.
>
> We, at COLT, ourselves use max-prefixes to handle inbound announcements
> to our network - we did this because coping with the number of
> updates, lack of any notification or process for notification
> turned this into a full time job. We have atleast 2 or 3 new
> routes every day.
>
> I'd like to start off some discussion on some type of
> standardisation or best common practise for this type of activity
> that would make our lives easier and I suspect also improve
> connectivity throughout Europe. Comments?
>
> Regards,
> Neil.
> --
> Neil J. McRae                                C O L T  I N T E R N E T
> neil@localhost   "In this world there's two kinds of people my friend:
>                   Those with loaded guns and those who dig. You dig?"
--- Jacques Caron
    PSINet Paris Hosting Center