Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-26 Thread Gaurab Raj Upadhaya
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 2/26/15 9:40 PM, Masato Yamanishi wrote: > Owen, > > I don't want to discuss too much details since I'm acting chair, > but I'm afraid that "unique routing policy" is vague and it may > qualify some usecases that private AS may also work. Can't ag

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-26 Thread Masato Yamanishi
Understood your point. Thx. Regards, Masato Yamanishi 2015-02-26 18:19 GMT-06:00 Owen DeLong : > I’m not opposed to qualifying some cases where private AS may also work, > because in those cases, frankly, I think most organizations will either use > a private AS rather than go to the trouble of

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-26 Thread Owen DeLong
I’m not opposed to qualifying some cases where private AS may also work, because in those cases, frankly, I think most organizations will either use a private AS rather than go to the trouble of applying, or, they may have a good reason (future plans, etc.) for wanting to get a public AS and not

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-26 Thread Masato Yamanishi
Owen, I don't want to discuss too much details since I'm acting chair, but I'm afraid that "unique routing policy" is vague and it may qualify some usecases that private AS may also work. So, what is the definition or understanding for "unique routing policy" in ARIN? Masato Yamanishi Feb 26, 2

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-26 Thread Owen DeLong
Yes, I was well aware of that. Is there anything you believe to be incorrect in my comments as a result? Otherwise, I’m not sure what you are getting at. I believe a unique routing policy or multiple peers is sufficient justification. Absent that, I believe that an entity which qualifies for PI

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-26 Thread Masato Yamanishi
Owen and Usman, In following comments, did you consider we are discussing "public" AS numbers? Since we are discussing "public" AS, we should have some kind of justifications why it should be globally unique. Regards, Masato 2015-02-25 18:39 GMT-06:00 Owen DeLong : > Usman, since an AS is defi

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-25 Thread Guangliang Pan
Hi Skeeve, I don’t think the current policy mention about subsequent ASN assignment. Every ASN assignment is requested to meet the multihoming requirement. For additional ASN requests, the requestors have to provide justification to show that their new AS is independent to their existing AS. Th

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-25 Thread Owen DeLong
Usman, since an AS is defined as “A collection of prefixes with a common routing policy”, what would you use one for if not to connect to other autonomous systems? If you are connecting to a single other autonomous system, then, arguably it is impossible for your prefixes to have a distinct rout

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-25 Thread Skeeve Stevens
Agreed... and I certainly don't want to see ASN's being wasted. I am happy for their to be some restrictions - even costs... but I am willing to see what the community recommends to avoid potential issues. ...Skeeve *Skeeve Stevens - Senior IP Broker* *v4Now - *an eintellego Networks service ske

Re: [sig-policy] Requirements for Subsequent ASN Requests

2015-02-25 Thread Usman Latif
ASN is an identifier for an autonomous system - so theoretically speaking, an ASN should have no dependency on multihoming or single homing However, what we need is a better way to regulate assignment of ASNs so their allocation doesn't become wasteful.. Regards, Usman > On 26 Feb 2015, at 11: