This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/address-policy-wg@ripe.net/
[address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Previous message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Job Snijders
job at instituut.net
Sat Aug 16 14:22:29 CEST 2014
On Sat, Aug 16, 2014 at 01:09:40PM +0100, Nick Hilliard wrote: > On 16/08/2014 12:31, Job Snijders wrote: > > A new AS Number should only be assigned when the End User expresses a need > > that cannot be satisfied with an existing AS Number. RIPE NCC will record, > > but not evaluate this need. > > This is an excellent idea. I have a legitimate operational need for a > large number of autonomous system numbers - slightly less than 2^32. The > rest of the internet will be left with a couple of thousand which should do > for the rest of time, assuming that they're handled sparingly. Anyways, > people can use the private assignment range if they're stuck. Already today you can request slightly less than 2^32 ASNs. For each request indicate that the requested ASN will peer with the two ASNs requested previously. > So count this as definite support for the proposal as it stands. Thank you for your support. Kind regards, Job
- Previous message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]