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] opposition to 2015-04
- Previous message (by thread): [address-policy-wg] opposition to 2015-04
- Next message (by thread): [address-policy-wg] opposition to 2015-04
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
apwg at c4inet.net
Mon May 30 20:31:42 CEST 2016
On Mon, May 30, 2016 at 06:55:03PM +0200, Gert Doering wrote: >"explicitly" implies that this has been, uh, explicitly written down >somewhere. Could you provide a reference? I was sure I'd read an explicit declaration that transfers due to business transactions do not fall under transfer policies in one of the alloc/assignment policy docs, however I might have been wrong and was thinking of ripe-654 which is a Organisational Document. This document, in sec 2.0 recognises transfers thus: A member must inform the RIPE NCC ifone or bothof the following changes occurs: Internet Number Resource are transferred. Such transfers may take place: Because of a change in the members business structure, for example in the case of a merger or acquisition of the members organisation. In the case of a transfer of Internet number resources from the member to another party according to RIPE Policies (section 5.5 and 6.4 of IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region , section 8 of IPv6 Address Allocation and Assignment Policy and section 4.0 of Autonomous System (AS) Number Assignment Policies ). Such a transfer may also be facilitated through the RIPE NCC Listing Service . The member changes its official legal name . Such a change may occur, for example, because of a merger or acquisition of the members organisation. So there are transfers due to M&A, name changes, and *according to transfer policy*. Three separate cases. Which also means that 2015-04, stating explicitly that M&A transfers are subject to policy, contradicts ripe-654 and would trigger a change of this document - which I hope would be subject to membership approval via GM vote. rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] opposition to 2015-04
- Next message (by thread): [address-policy-wg] opposition to 2015-04
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]