[3746] in North American Network Operators' Group
Re: Customer AS
daemon@ATHENA.MIT.EDU (Alex.Bligh)
Mon Aug 19 14:39:05 1996
To: curtis@ans.net
cc: Sean Doran <smd@chops.icp.net>, Paul Ferguson <pferguso@cisco.com>,
"Chris MacFarland" <chris@computek.net>,
"Tim Crowell" <tcrowell@gte.net>, nanog@merit.edu
In-reply-to: Your message of "Mon, 19 Aug 1996 13:22:56 EDT."
<199608191723.NAA10694@brookfield.ans.net>
Date: Mon, 19 Aug 1996 19:28:04 +0100
From: "Alex.Bligh" <amb@xara.net>
Curtis,
> I agree that the majority of more specifics are mistakes. We use the
> IRR to separate out the inintentional mistakes (the redundancy in that
> statement was intentional:). This does protect us against the all too
> common case of too ignorant of CIDR to know better and registering the
> more specific in the IRR anyway (the intentional mistakes).
>
Really? I would agree that the majority of more specifics are not in
the IRR. This doesn't necessarilly mean they are mistakes. For instance
we announce a pile of more specifics from other provider aggregates
(intentionally, and with permission) where a customer is renumbering.
These get filtered by Sprint (because they are too long prefixes),
and by ANS (as they aren't in the IRR), but the idea is we propogate
these more specifics as close as possible to the major networks
as possible, so that as far as possible we aren't using the
old providers transit to transit these routes (for several
obvious reasons). We don't put advisories or more specifics in the
IRR for several reasons, not least of which because this is a temporary
arrangement, and sorting out changing guardianship of the RIPE
objects etc. etc. with the old provider who is often slow to
cooperate is simply not worth the hassle.
So I have no problem with either ANS or Sprint's filters, just
don't think *all* non-IRR entered more specifics are mistakes.
Alex Bligh
Xara Networks
