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] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Previous message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
apwg at c4inet.net
Wed Sep 2 15:40:49 CEST 2015
On Wed, Sep 02, 2015 at 12:37:22AM +0200, Erik Bais wrote: >To clarify here ... although all types of number resources can >be transferred.. ( AS, IPv4, IPv6 ) there are some specific >resources ( like v4 for IXP usage ) are not allowed to be >transferred and MUST be returned.. >https://www.ripe.net/publications/docs/ripe-649#61 Hmm. -649 s6.1 doesn't actually say that IXP PI must be returned and can't be transferred. At most it could be read as implied by "A /16 will be held in reserve for exclusive use by Internet Exchange Points" Even if interpreted restrictively, this would still allow transfers to other IXPs... May I suggest, though, that this statement: "Resources are excluded from transfers when RIPE Policies mandate their return to the RIPE NCC." be moved to s2.2 "Transfer Restrictions"? IMO it's a more logical place to find it if one were looking to find out whether a resource is eligible for transfer. rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
- Next message (by thread): [address-policy-wg] 2015-04 New Policy Proposal (RIPE Resource Transfer Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]