[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
call for Orlando IETF agenda items
- Subject: call for Orlando IETF agenda items
- From: Robert Rockell <[email protected]> (Robert Rockell)
- Date: Fri, 30 Oct 1998 12:13:32 -0500 (EST)
- In-reply-to: <[email protected]>
I think it is time for some sort of reccommended filter policy to be
discussed, as most people out there (some of which who perform bad-route
reports, yet don't filter their downstreams) are not using filters in place.
For instance, I make the bad routing report every day in Merit's report, but
my AS never shows up in the route's originating path).
I don't know if this should be added to the soon-to-be-expired
draft-ietf-ngtrans-6bone-routing-01.tx paper, or put somewhere else, but I
think it is time that this is more strictly enforced.
Filtering via route-map on cisco products works well, but I don't know that
it is widely implemented (Backbone experience, or other reasons).
If we are going to model the 6bone after real life, I think that this is
going to be a crucial issue (especially if we are going to tackle the
multi-homing problem; without filters, no one is encouraged to work on it,
as both /48's are wandering around the backbone for a downstream in many
Sprintlink Internet Service Center
1-800-724-3329, PIN 385-8833
On Fri, 30 Oct 1998, Bob Fink wrote:
->We are now planning for the Orlando IETF meetings, so I need input on topics anyone might wish to cover at the ngtrans meeting.
->Please send your agenda suggestions either to me privately or to the ngtrans list.