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]/
[members-discuss] [Ticket#2015032901000081] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
- Previous message (by thread): [members-discuss] [Ticket#2015032901000081] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
- Next message (by thread): [members-discuss] [Ticket#2015032901000081] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at netability.ie
Sun Mar 29 00:39:03 CET 2015
On 28/03/2015 23:13, Elvis Daniel Velea wrote: > Firstly, the internet is using ~65K ASNs while the supply is 2MM. We still > have 64K*65K before we should really worry about garbage collection. Elvis, a network which requires functional BGP community support cannot feasibly be run on an ASN32. I have tried it in production and it is operationally nonviable. There is no complete ASN32-compatible solution to this situation in the short or medium term. In the long term - well beyond the point of ASN16 resource exhaustion - it is possible that this situation may be resolved. However this is a long term possibility rather than the short term certainty that we are facing impending depletion of ASN16s. It is for this reason that ASN16 resource depletion and consequently garbage collection has important operational implications for RIPE NCC members who plan to run their own ASNs. Nick
- Previous message (by thread): [members-discuss] [Ticket#2015032901000081] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
- Next message (by thread): [members-discuss] [Ticket#2015032901000081] [ncc-announce] [GM] Draft RIPE NCC Charging Scheme 2016
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]