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] PA policy
- Previous message (by thread): [address-policy-wg] PA policy
- Next message (by thread): [address-policy-wg] PA policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Tore Anderson
tore at fud.no
Tue Jul 7 16:40:50 CEST 2015
Hi James, * Kennedy, James > "LIRs are allocated Provider Aggregatable (PA) address space. They > sub-allocate and assign this to *downstream networks*." > https://www.ripe.net/publications/docs/ripe-643#7 > > To me this reads networks or End Users assigned PA space must receive > transit from the LIR holding the parent allocation. I understand "downstream" to refer to the hierarchical internet number registry system here, not BGP routing topology. Otherwise, we'd all have to buy our IP-transit from the RIPE NCC, who'd in turn have to buy it from the IANA.... > Or can the LIR assign PA blocks to customers/companies that don't > receive transit, or any other technical network service for that > matter, from the LIR? That's how the policy has been implemented so far, yes. Note that the RIPE database gladly allow ASSIGNED PA inet(6)nums to get their own completely independent route(6) objects. Tore
- Previous message (by thread): [address-policy-wg] PA policy
- Next message (by thread): [address-policy-wg] PA policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]