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] [Ext] Re: proposal to remove IPv6 PI
- Previous message (by thread): [address-policy-wg] [Ext] Re: proposal to remove IPv6 PI
- Next message (by thread): [address-policy-wg] [Ext] Re: proposal to remove IPv6 PI
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Sascha Luck [ml]
apwg at c4inet.net
Sat May 19 15:09:03 CEST 2018
On Thu, May 17, 2018 at 12:17:43AM +0000, Leo Vegoda wrote: >> but it removes the requirement that a LIR provide >> connectivity to an End User. > >Since when has this been a requirement? > >Section 2.4 of ripe-699 defines LIRs and describes them as "primarily" >providing addresses for network services that they provide. Have I >misunderstood the policy, or is there currently a requirement that LIR >provide network connectivity to the users of the addresses they assign or >sub-allocate? It's not a formal requirement but, de-facto, if the holder of PA resources wants connectivity, they have to get it from the LIR. Otherwise, why would there be a necessity for "provider-aggregateable" resources? rgds, Sascha Luck
- Previous message (by thread): [address-policy-wg] [Ext] Re: proposal to remove IPv6 PI
- Next message (by thread): [address-policy-wg] [Ext] Re: proposal to remove IPv6 PI
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]