Re: [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
> I don't think is objective to say that the proposal as asking the NCC > to "inject" invalids. > > The proposal is providing the information of the invalids (in this > case unallocated/unassigned) by means of RPKI. ok. i was kind of on the fence. but american press has made me oversensitive to fake language such as this; so it threw me over the edge. i do not support the proposal. randy
Re: [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
> On Feb 23, 2020, at 8:45 AM, Nick Hilliard wrote: > > JORDI PALET MARTINEZ via routing-wg wrote on 23/02/2020 13:06: >> I don't think is objective to say that the proposal as asking the NCC >> to "inject" invalids. >> The proposal is providing the information of the invalids (in this >> case unallocated/unassigned) by means of RPKI. > > Jordi, > > You're splitting hairs here. The end result is the same. I’m cornered about something like this as we’ve been down this road before with bogon lists, etc and even though it’s well intentioned by smart people(tm), the distributed legacy and cleanup has often taken years to recover. - Jared
Re: [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
On 20/02/2020 16:39, Petrit Hasani wrote: I support this proposal. Should have been done a long time ago. Regards, Hank Dear colleagues, Policy proposal 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space", is now in the Review Phase. The goal of the proposal is to ask the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. The proposal has been updated following the last round of discussion. Version 2 of the proposal includes a specification for the RIPE NCC to create all AS0 ROAs under a specific Trust Anchor. The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-08 https://www.ripe.net/participate/policies/proposals/2019-08#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-08/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussion of the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to before 20 March 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC
Re: [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
I don't think is the same, because some people may read it as "the NCC" is forcing us to do some routing thing, which is not the case. El 23/2/20 14:46, "routing-wg en nombre de Nick Hilliard" escribió: JORDI PALET MARTINEZ via routing-wg wrote on 23/02/2020 13:06: > I don't think is objective to say that the proposal as asking the NCC > to "inject" invalids. > > The proposal is providing the information of the invalids (in this > case unallocated/unassigned) by means of RPKI. Jordi, You're splitting hairs here. The end result is the same. Nick ** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
Re: [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
JORDI PALET MARTINEZ via routing-wg wrote on 23/02/2020 13:06: I don't think is objective to say that the proposal as asking the NCC to "inject" invalids. The proposal is providing the information of the invalids (in this case unallocated/unassigned) by means of RPKI. Jordi, You're splitting hairs here. The end result is the same. Nick
Re: [routing-wg] 2019-08 Review Phase (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space)
Hi Erik, I don't think is objective to say that the proposal as asking the NCC to "inject" invalids. The proposal is providing the information of the invalids (in this case unallocated/unassigned) by means of RPKI. Furthermore, because this is done via a specific TAL, operators can choose to use it or not. Regards, Jordi @jordipalet El 22/2/20 17:13, "routing-wg en nombre de Erik Bais" escribió: I agree with Job Snijders his remarks on this ML on the topic. I don't think this is a good way forward. Please keep the RIPE NCC away from injecting invalids into the RPKI system. I applaud the authors for their work, but I don't think that the downside, cost projection and possible future scope creep is worth going down this rabbit hole. I oppose this policy. regards, Erik Bais On 20/02/2020, 15:40, "routing-wg on behalf of Petrit Hasani" wrote: Dear colleagues, Policy proposal 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space", is now in the Review Phase. The goal of the proposal is to ask the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. The proposal has been updated following the last round of discussion. Version 2 of the proposal includes a specification for the RIPE NCC to create all AS0 ROAs under a specific Trust Anchor. The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2019-08 https://www.ripe.net/participate/policies/proposals/2019-08#impact-analysis And the draft documents at: https://www.ripe.net/participate/policies/proposals/2019-08/draft As per the RIPE Policy Development Process (PDP), the purpose of this four week Review Phase is to continue discussion of the proposal, taking the impact analysis into consideration, and to review the full draft RIPE Policy Document. At the end of the Review Phase, the Working Group (WG) Chairs will determine whether the WG has reached rough consensus. It is therefore important to provide your opinion, even if it is simply a restatement of your input from the previous phase. We encourage you to read the proposal, impact analysis and draft document and send any comments to before 20 March 2020. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC ** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
