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] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
- Previous message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
- Next message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sander Steffann
sander at steffann.nl
Fri Mar 28 15:09:37 CET 2014
Hi, > I see two solutions to this: > > - the NCC "revokes" the /16 delegation and replaces it with 255 /24 > delegations, and two /25 delegations > - you delegate 43.47.185.in-addr.arpa back to the NCC > > Neither of them is appropriate in my view. I think the first one is appropriate. If the NCC doesn't allocate the whole /16 to one organisation they cannot create a reverse delegation for it to that single organisation. They can't delegate reverse DNS to an organisation that doesn't hold that address space... So the technically correct solution is to do what you suggest first. It isn't pretty, and it would make address holders think twice before carving out a small portion of their address space to sell, but that might be a good thing :) I'll leave that for the the WG to discuss :) Cheers, Sander
- Previous message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
- Next message (by thread): [address-policy-wg] 2014-01 New Policy Proposal (Abandoning the Minimum Allocation Size for IPv4)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]