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] IPv4 Maintenance Policy
- Previous message (by thread): [address-policy-wg] IPv4 Maintenance Policy
- Next message (by thread): [address-policy-wg] IPv4 Maintenance Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
McTim
dogwallah at gmail.com
Fri Apr 20 01:47:08 CEST 2012
Milton, On Thu, Apr 19, 2012 at 2:54 PM, Milton L Mueller <mueller at syr.edu> wrote: > > >> -----Original Message----- >> >> the space referred to is allocated to (or administered by if you prefer) >> ripe. reverses for this space are delegated to ripe (one single > > [Milton L Mueller] It wasn't allocated by RIPE. Read the definition of "legacy." > >>alternate service providers can't delegate from this space. > > [Milton L Mueller] They don't have to delegate, the space has already been delegated to a legacy holder. Chris is talking about the reverse delegation in the DNS. He is correct that RIPE NCC administers reverse delegation for some legacy blocks. -- Cheers, McTim "A name indicates what we seek. An address indicates where it is. A route indicates how we get there." Jon Postel
- Previous message (by thread): [address-policy-wg] IPv4 Maintenance Policy
- Next message (by thread): [address-policy-wg] IPv4 Maintenance Policy
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]