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] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
- Previous message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
- Next message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Florian Weimer
fweimer at bfk.de
Wed Apr 15 11:16:13 CEST 2009
* Piotr Strzyzewski: > We could add those two things together and make that like: /32 for every > AS owned by LIR (in simplification). This is more IETF material, IMHO. There could be a magic /5 which contains a /32 for every 27-bit AS number, and a magic /16 with a /48 for every 32 bit AS number. RIRs are only needed to handle the reverse delegation. In any case, to me it looks like multiple requests for /32s are needed only to work around route filters. If this is really the case, those filters have to go. -- Florian Weimer <fweimer at bfk.de> BFK edv-consulting GmbH http://www.bfk.de/ Kriegsstraße 100 tel: +49-721-96201-1 D-76133 Karlsruhe fax: +49-721-96201-99
- Previous message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
- Next message (by thread): [address-policy-wg] 2009-05 New Policy Proposal (Multiple IPv6 /32 Allocations for LIRs)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]