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:55:54 CEST 2015
On Wed, Sep 02, 2015 at 02:48:07PM +0100, Nick Hilliard wrote: >649 section 6.1 says: > >-- >This space will be used to run an IXP peering LAN; other uses are forbidden. >-- I actually read that as "This space *as assigned to this end-user*[...]" Does IXP space come out of a separate pool from any other ipv4? That section could maybe do with de-ambiguisation if only to protect the space for IXPs 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 ]