PE region this practice is standard for most ISPs.
--
Cliff Albert <[EMAIL PROTECTED]>
which you are 100%
sure that it's *useless* traffic. uRPF will fix it for your own network,
but filtering bogon routes away in BGP will also make your downstream
a happier place.
The only argument from you I have seen against bogon filtering is the
fact that the lists aren't updated by certain parties.
--
Cliff Albert <[EMAIL PROTECTED]>
t seems they all got a big NO
back.
--
Cliff Albert <[EMAIL PROTECTED]>
nc).
Indeed, for such purposes it's a nice solutions.
--
Cliff Albert <[EMAIL PROTECTED]>
more-specific bogons are going around in the BGP table ?
--
Cliff Albert <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
On Fri, Dec 03, 2004 at 10:57:15AM +0100, Andre Oppermann wrote:
> If you do any bogon filtering at all then do it with some automatically
> updating system like an BGP bogon feed from Cymru.
How does the BGP bogon feed from cymru protect against more-specific
bogons ?
--
Cliff Albert &
; ASN exhaustion is IMHO just a symptom of the real problem. Enlarging
> the ASN space does not cure the disease, just makes it worse.
And this is exactly my point.
--
Cliff Albert <[EMAIL PROTECTED]>
e
> more work but provide no benefits.
This has been taken from the BIT looking glass, as this is one of the
peers present in the aut-num. As I said before an ASN doesn't have to
appear in the global routing table, but there has to be viable evidence
of the use of the ASN.
--
Cliff Albert <[EMAIL PROTECTED]>
> I can assure you that this AS number was assigned and is still used in
> full compliance with RIPE policies.
* 195.193.163.0/24195.69.144.12512945 I
As you can see there is evidence to substantiate your claim. That you
have no route: object and are advertising UUNet
active use of the ASN and conforming to the current
rules every 6 months should be a nice thing. This way old unused ASN's
can be recycled easilier.
Probably RIPE will implement such a thing when there routing registry
consistency check software is complete.
--
Cliff Albert <[EMAIL PROTECTED]>
nd having actually only 1 upstream (there
are 2 upstreams in the routing database, but in the real world there is
only 1 upstream).
--
Cliff Albert <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
On Sun, Nov 28, 2004 at 01:21:05PM +0100, Henning Brauer wrote:
> * Cliff Albert <[EMAIL PROTECTED]> [2004-11-28 13:13]:
> > Therefore I also agree with daniel that there is not really a problem
> > with the 1 ASN == 1 IPv6 Prefix.
>
> unless I miss something in th
ter, we might make do
> with 16 bit ASNs, or at least make do with them much longer.
My preference lies in making the policies a lot stricter, and actively
verifying current delegations. I see a lot of ASN's requested just for
fun with no real motive behind it.
Therefore I also agree with daniel that there is not really a problem
with the 1 ASN == 1 IPv6 Prefix.
--
Cliff Albert <[EMAIL PROTECTED]>
On Wed, Oct 13, 2004 at 02:33:53PM -0500, Bubba Parker wrote:
> A standard whois program can not tell you what IP addresses a particular AS is
> announcing.
Actually it can tell you what IP adresses a particular AS SHOULD
announce.
whois -i origin -h whois.ripe.net AS28788
--
Cliff
anything in the usual places regarding this
I see no abnormal dns requests on our caching aswell authorative
servers.
--
Cliff Albert <[EMAIL PROTECTED]>
On Mon, Oct 11, 2004 at 02:26:33PM -0400, Chaim Fried wrote:
> Anybody know of any prolonged outages at Microsoft (MSN messenger)today?
Experiencing issues all day long here in europe.
--
Cliff Albert <[EMAIL PROTECTED]>
27;t be resolved (as we found out the hard way
here in europe after the Above downtime).
--
Cliff Albert| RIPE: CA3348-RIPE | https://oisec.net/
[EMAIL PROTECTED] | 6BONE: CA2-6BONE |
PGP Fingerprint = 9ED4 1372 5053 937E F59D B35F 06A1 CC43 9A9B 1C5A
hey fit into your topology?
I think mostly any operator is using GBICs somewhere in there network.
We are using them at the edge and in the core.
--
Cliff Albert| RIPE: CA3348-RIPE | https://oisec.net/
[EMAIL PROTECTED] | 6BONE: CA2-6BONE |
PGP Fingerprint = 9E
assigned space comparisons. Makes very good reading about all this.
--
Cliff Albert| RIPE: CA3348-RIPE | https://oisec.net/
[EMAIL PROTECTED] | 6BONE: CA2-6BONE |
PGP Fingerprint = 9ED4 1372 5053 937E F59D B35F 06A1 CC43 9A9B 1C5A
signature.asc
Description: Digital signature
tream NTT/Verio
I do not receive it.
--
Cliff Albert| RIPE: CA3348-RIPE | https://oisec.net/
[EMAIL PROTECTED] | 6BONE: CA2-6BONE |
PGP Fingerprint = 9ED4 1372 5053 937E F59D B35F 06A1 CC43 9A9B 1C5A
-lists in route refresh
messages.
A more formal definition of it can be found in the following draft
(http://www.ietf.org/internet-drafts/draft-ietf-idr-route-filter-09.txt)
--
Cliff Albert| RIPE: CA33
21 matches
Mail list logo
