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] Allocation transfer
- Previous message (by thread): [address-policy-wg] Allocation transfer
- Next message (by thread): [address-policy-wg] Allocation transfer
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Marcus Gerdon
marcus.gerdon at mainz-kom.de
Mon May 16 15:35:12 CEST 2005
Hi Dave, there are two ways possibe to accomplish this as I'd take the policies. First would be as your question was: You could apply for a (additional) /19 allocation and assign it to your customer. Later on when they've become a LIR themselves you can contact NCC for transfer of this allocation to your customers LIR. I've not found any detailed information ad hoc but in document RIPE-301 (intended for mergers, take-overs and so on) is the possibility of transferring a resource mentioned without any direct relationship to closure or merger of the originating LIR. Second is what I think would be the most 'correct' way to do this: Some time ago (if my memory's right it's about 1 1/2 years ago) RIPE added the option for assignments as 'SUB-ALLOCATION' which on a quick glance is exactly what you plan to do: hand a larger address range to another network operator for assignment to customers without him being a LIR himself. Just check document RIPE-324 for this. Just check the documents (especially 324) and maybe contact lir-help for their opinion on this. And please keep your hands off doing PI for this. Although /19 PI wouldn't make any difference to /19 PA within the routing tables, your customer won't be able to do any sub-assignments with registering them in the RIPE database using PI. I wouldn't want to get SPAM notifications for a /19 bunch of addresses only because I'm not able to add distinguished contacts for address ranges handed to customers. regards, Marcus --------------------------------------------------------- mainzkom Telekommunikation GmbH Ein Unternehmen der Tropolys-Gruppe Network Engineering and Administration mainzkom / maineotk / pulsaar Tel: +49-(0)6131/129343 | Fax: +49-(0)6131/129321 Mombacher Str. 40, 55122 Mainz, Germany --------------------------------------------------------- AS15837 | MG3031-RIPE --------------------------------------------------------- ----- Original Message ----- From: "David Bell" <dbell at redwingsat.com> To: <address-policy-wg at ripe.net> Sent: Monday, May 16, 2005 11:17 AM Subject: [address-policy-wg] Allocation transfer > Hi all, > > uk.redwing is a small LIR, providing internet via satellite. We are in the > process of hosting a new satellite platform, on behalf of another > organisation, that is projecting a requirement for a /19 in the next 12 > months. This partner is not currently an LIR, but is considering it as a > future option. > > What I am trying to determine is if uk.redwing applies for this /19 address > block, and assigns it as PA space, will it be possible in the future for us > to hand it over to our partner, if/when they become an LIR themselves. > Perhaps this is a case where PI addresses would be suitable, but I see > warnings everywhere I look regarding the use of PI space. > > My apologies if this is not the correct place to post this question, please > let me know the best place to go if I'm on the wrong list. > > > > Thanks very much, > > > Dave Bell > Redwing Satellite Solutions Ltd. > >
- Previous message (by thread): [address-policy-wg] Allocation transfer
- Next message (by thread): [address-policy-wg] Allocation transfer
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]