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 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Previous message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Nick Hilliard
nick at inex.ie
Wed May 20 13:56:32 CEST 2015
On 16/05/2015 03:33, David Huberman wrote: > If the RIRs don't do anything to preserve 2-byte AS numbers, then things > are going to start really breaking. s/RIRs don't do anything to preserve/vendors don't to anything to support/ ASN16 runout is inevitable and is now within sight: IANA's stock is gone. The RIRs can twiddle policy this way or that, but they can't stop runout and will find it difficult even to slow it down. If the vendors are pretending otherwise - either to themselves or their customers - then they are deluded. If RIR run-out hits before they have implemented asn32 support and shaken out all the bugs, then they will find that their kit is obsolete for new customers and this will have commercial implications for them. Nick
- Previous message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
- Next message (by thread): [address-policy-wg] 2014-03 Review Period extended until 19 May 2015 (Remove Multihoming Requirement for AS Number Assignments)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]