RE: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-12 Thread Terry Baranski
At the moment there is no clear procedure for any ISP to follow to even get a best guess as to whether an advertisement should be accepted or not. What about requiring that a route appear in an RIR database period? Maybe that would be a good start. It's easy enough to do but virtually no

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-10 Thread Mr. James W. Laferriere
Hello Kia , In line On Mon, 9 Jun 2003, Kai Schlichting wrote: On 6/9/2003 at 4:06 PM, Christopher L. Morrow [EMAIL PROTECTED] wrote: Sure, you are announcing 196.1.1.0/24 and only that, fine, but are you allowed to announce that prefix? Are you Centre for Monitoring Indian

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread John Brown
Fear leads to Hate, which leads to Evil, the way of the darkside ;) RIR's are not and should not be in the business of dictating what goes into the routing table, or what label is used on what goes into the routing table. I think part of the issue here is that to many providers don't filter

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Sean Donelan
On Mon, 9 Jun 2003, Christopher L. Morrow wrote: Sorry for the latenight not-completely-operational question :) but it seems as though there is some abmiguity in the current process/procedure/rules and I'd like to atleast start some discussion on the topic. I'm not as interested in proving

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread william
Well as some of you know as of late I've been involved in investigations of number of hijacked ip blocks (about 40 and looking at more) and can tell you that for greater majority of companies (especially for companies that had /16s but even for companies that had /24) the records on internet

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Joe Abley
On Monday, Jun 9, 2003, at 02:36 Canada/Eastern, John Brown wrote: RIR's are not and should not be in the business of dictating what goes into the routing table, or what label is used on what goes into the routing table. Just the other day I heard of a new customer of an ISP in Toronto who had

RE: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Christopher L. Morrow
On Mon, 9 Jun 2003, Michel Py wrote: Chris, Christopher L. Morrow wrote: So, for an example, if I steal ASN 8143 (already stolen so its mute) and I'm 'a good guy', all I want to do is run a network no spam/abuse eminates from it, Question: if you are a 'good guy', why didn't you

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread jlewis
On Mon, 9 Jun 2003, Joe Abley wrote: The ISP in Toronto asked for an LOA, and got one, neatly presented on company letterhead, and accompanied by e-mail from the tech contact for the block confirming that the request to advertise the block was authorised. Is that enough justification

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Joe Abley
On Monday, Jun 9, 2003, at 12:53 Canada/Eastern, [EMAIL PROTECTED] wrote: Since the RIRs contain the information required to answer those questions, you'd expect them (or their data) to be involved in the process of answering them. They really don't. Thus far, when space is assigned, the RIRs

RE: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Christopher L. Morrow
On Mon, 9 Jun 2003, Michel Py wrote: Chris, Christopher L. Morrow wrote: excellent point :) the distinction between 'good' and 'bad' was just non-abuser/abuser. Certianly ARIN's requirements for ASN ownership are simple enough, be multihomed and have a 'unique' routing policy. If

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Richard A Steenbergen
On Mon, Jun 09, 2003 at 06:06:50PM +0100, Stephen J. Wilcox wrote: RIPE at least uses a hierarchical authorisation scheme which means you cannot register routes to an ASN and prefix you dont have authorisation on, where authorisation on those blocks is passed down from supernets and

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Christopher L. Morrow
On Mon, 9 Jun 2003, John Brown wrote: Fear leads to Hate, which leads to Evil, the way of the darkside ;) RIR's are not and should not be in the business of dictating what goes into the routing table, or what label is used on what goes into the routing table. Certainly not, but if the

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Jack Bates
Andy Dills wrote: What sorts of 'unique' routing policies justify an ASN? ISP has a corporate customer that decides to multi-home. While ISP is not multi-homed themselves, they must have an ASN to speak BGP and pass routing information between their corporate customer and their provider. So

Re: Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-09 Thread Kai Schlichting
On 6/9/2003 at 4:06 PM, Christopher L. Morrow [EMAIL PROTECTED] wrote: Sure, you are announcing 196.1.1.0/24 and only that, fine, but are you allowed to announce that prefix? Are you Centre for Monitoring Indian Economy ?? Or is this your direct customer and you are just the sat-link

Ettiquette and rules regarding Hijacked ASN's or IP space?

2003-06-08 Thread Christopher L. Morrow
So, with all this lifting the curtains on hijacked ASN's and ipblocks recently I have a few general question... 1) Should the rules be uniformly applied? 2) Should these rules be applied even when something 'bad' might happen? 3) How much involvment should ARIN have in enforcing these rules?