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] [Ticket#2014081101013263] Transfer from last /8
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Aleksi Suhonen
ripe-ml-2012 at ssd.axu.tm
Thu Aug 14 05:02:20 CEST 2014
Hello, On 07/11/2014 11:21 AM, Marco Schmidt wrote: > The draft document for the proposal described in 2014-03, > "Remove Multihoming Requirement for AS Number Assignments" has been > published. The impact analysis that was conducted for this proposal > has also been published. I know I'm late in the game, but I thought I'd contribute this view rather than stay silent: Remove multi homing requirement for 32bit ASNs only, keep the requirement for 16bit ASNs. I foresee new weird legacy setups run by non-ISPs that still require a unique ASN well into the future. The example I would usually use is factory floor environments, but that is probably not an applicable example here. I hope someone else's imagination can supply a valid example. Cheers, -- Aleksi Suhonen You say "potato", I say "closest-exit."
- Previous message (by thread): [address-policy-wg] [Ticket#2014081101013263] Transfer from last /8
- Next message (by thread): [address-policy-wg] 2014-03 two cents on multi homing ASN requirement
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]