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] IPv6 PI justification requirements
- Previous message (by thread): [address-policy-wg] IPv6 PI justification requirements
- Next message (by thread): [address-policy-wg] IPv6 PI justification requirements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Cynthia Revström
me at cynthia.re
Tue Feb 26 23:13:37 CET 2019
I just want to clarify, that the NCC wanted documentation in the form of an addressing plan (over time?) and why PA space would not work. Now I do also want to clarify that I have already told them that the reason for this is that they have multiple physical locations with servers and they want PI for their infrastructure so it is their resources and not the provider's. I have also been informed that this might be a rather unique case in regards to having multiple physical locations requiring PI space. - Cynthia On 2019-02-26 23:00, Cynthia Revström wrote: > Hello ap-wg, > > I am in the process of requesting 3x /48 of IPv6 PI for a customer, > and what confuses me is that the NCC requires way more justification > for 3x /48 of PI than for 2x /29 of PA. > > I do think that saying something like net1 will be used in the > Netherlands, net2 in London, and net3 in New York should be enough. I > mean after all, any LIR can get 512K /48s and unlike ASNs, PI space > does have a small fee attached with it. > > I can't think of a good reason why this is the case. > > Once again to make it clear, if you are a member it is easier to get 1 > million /48s than it is for a non member to get 3 /48s. > > - Cynthia > >
- Previous message (by thread): [address-policy-wg] IPv6 PI justification requirements
- Next message (by thread): [address-policy-wg] IPv6 PI justification requirements
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]