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/[email protected]/
[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 ]
Saku Ytti
saku at ytti.fi
Sat Aug 16 15:33:57 CEST 2014
On 16 August 2014 15:22, Job Snijders <job at instituut.net> wrote: > 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. ACK. And if there seem to be worrying request rate, situation is unchanged, we need to address that, with today's policy and with tomorrow's policy. I personally would want to see YRC implemented, 1EUR/year/resource, 4294967296 EUR annual revenue will make it possible to finance sufficient long AS number for Nick's use cases. -- ++ytti
- 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 ]