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 Assignment questions
- Previous message (by thread): [address-policy-wg] PA Assignment questions
- Next message (by thread): [address-policy-wg] Anycasting Assignments for TLDs and Tier 0/1 ENUM Implemented
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Lenz
slz at baycix.de
Thu Jul 16 13:24:55 CEST 2009
Nolan, Keith schrieb: > The other issue with suggesting that we use PI Space instead of PA Space where we will not be in a position to aggregate is the PI Assignment which would be approved would be less than a /24 (as we don't need 128 addresses for Multi-homed BGP Peering), therefore wouldn't be routable on the Internet (Policy proposal 2006-05 refers to this issue and suggests the smallest PI Space should be /24) > > > So the only way to implement Multi-Home BGP Routing from Multiple locations which don't need a full /24 network is to become a LIR and create smaller /25 or /26 inetnum's with larger /24 route objects from your PA Space. And since this is a workaround, just like a company stretching the truth about their IP requirements when applying for a PI Space to get a full /24, surely a LIR should be allowed to create inetnum's for a /24 when they also need to create a /24 route object. [...] please have a look at http://www.ripe.net/ripe/policies/proposals/2006-05.html and the discussions on the ap-wg list (i think) about it in the mailinglist archive if you don't read the list on a regular basis. It's partially about your problem here. It is indeed considered a problem by some other people, too. Although the current thinking by most involved in the policy process seems to be that it's weired that you need PI space and your own routing policy for two or three boxes (or so) in the first place. In any ways, it's probably still a design problem. Why did you design a network with multiple locations and no connection between them as a normal network architect would do? It's probably none of our business here how you design your network, but that is considered a fail anyways :-) If you really have independent locations, you need independent ressources, multiple LIRs probably or multiple PI Assignments. It's a really bad habbit to slit up PA Allocations and might not work out for you in all cases, you need workarounds like Tunnels between the locations and a site announcing the aggregate so you don't run into the PA Filters ... and so on ... But again, i don't really see the problem, i'm afraid. Probably some other people on the list can. P.S.: Don't think too much about address conservation. It's overrated, we have IPv6 now :-) -- ======================================================================== = Sascha Lenz SLZ-RIPE slz at baycix.de = = Network Design & Operations = = BayCIX GmbH, Landshut * PGP public Key on demand * = ========================================================================
- Previous message (by thread): [address-policy-wg] PA Assignment questions
- Next message (by thread): [address-policy-wg] Anycasting Assignments for TLDs and Tier 0/1 ENUM Implemented
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]