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] clarification on RIPE Resource Transfer Policies (ripe-682) Section 2.0
- Previous message (by thread): [address-policy-wg] recantation
- Next message (by thread): [address-policy-wg] clarification on RIPE Resource Transfer Policies (ripe-682) Section 2.0
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Peter Hessler
phessler at theapt.org
Tue May 23 14:10:06 CEST 2017
Hi All https://www.ripe.net/publications/docs/ripe-682#2-0-transfers-within-the-ripe-ncc-service-region I saw this restriction: """ Allocated resources may only be transferred to another RIPE NCC member. Provider Independent resources may be transferred to: * A RIPE NCC member; or * An entity that has a contractual relationship with a RIPE NCC member in accordance with the RIPE Policy, """ Note the difference between Allocated (PA) and Provider Independent (PI). Is this split intentional? Would a proposal to unify both under the existing PI rules be welcome? -peter
- Previous message (by thread): [address-policy-wg] recantation
- Next message (by thread): [address-policy-wg] clarification on RIPE Resource Transfer Policies (ripe-682) Section 2.0
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]