2018-06 Review Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up)
Dear colleagues, Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-06 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/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 <routing-wg@ripe.net> before 12 September 2019. Kind regards, Marco Schmidt Policy Officer RIPE NCC
Dear all, Thank you for putting together an impact analysis! I believe this write-up by RIPE NCC demonstrates the staff have a good understanding of the policy proposal. As one of the proposers, I believe that (short of deleting RIPE-NONAUTH entirely) this proposal is gentle and sane mechanism to incrementally clean up the un-validated RIPE-NONAUTH data source. I look forward to hearing the groups’ thoughts on how to proceed. Kind regards, Job On Wed, 14 Aug 2019 at 15:24, Marco Schmidt <mschmidt@ripe.net> wrote:
Dear colleagues,
Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase.
The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA.
The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts
The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-06
And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/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 <routing-wg@ripe.net> before 12 September 2019.
Kind regards,
Marco Schmidt Policy Officer RIPE NCC
* Job Snijders
I look forward to hearing the groups’ thoughts on how to proceed.
Doesn't require much thinking. Just do it. +1 Tore
In agreement, Tore Anderson wrote on 14/08/2019 16:47:
Doesn't require much thinking. Just do it. +1
Well said! -- Chriztoffer
Yes, I think we should go ahead with this. Kind regards, Paul Hoogsteder.
On 14 Aug 2019, at 16:00, Job Snijders <job@ntt.net> wrote:
Dear all,
Thank you for putting together an impact analysis! I believe this write-up by RIPE NCC demonstrates the staff have a good understanding of the policy proposal.
As one of the proposers, I believe that (short of deleting RIPE-NONAUTH entirely) this proposal is gentle and sane mechanism to incrementally clean up the un-validated RIPE-NONAUTH data source.
I look forward to hearing the groups’ thoughts on how to proceed.
Kind regards,
Job
On Wed, 14 Aug 2019 at 15:24, Marco Schmidt <mschmidt@ripe.net> wrote: Dear colleagues,
Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase.
The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA.
The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts
The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-06
And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/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 <routing-wg@ripe.net> before 12 September 2019.
Kind regards,
Marco Schmidt Policy Officer RIPE NCC
+1 we should do this now. On Wed, Aug 14, 2019 at 5:06 PM Paul Hoogsteder <paul@meanie.nl> wrote:
Yes, I think we should go ahead with this.
Kind regards,
Paul Hoogsteder.
On 14 Aug 2019, at 16:00, Job Snijders <job@ntt.net> wrote:
Dear all,
Thank you for putting together an impact analysis! I believe this write-up by RIPE NCC demonstrates the staff have a good understanding of the policy proposal.
As one of the proposers, I believe that (short of deleting RIPE-NONAUTH entirely) this proposal is gentle and sane mechanism to incrementally clean up the un-validated RIPE-NONAUTH data source.
I look forward to hearing the groups’ thoughts on how to proceed.
Kind regards,
Job
On Wed, 14 Aug 2019 at 15:24, Marco Schmidt <mschmidt@ripe.net> wrote:
Dear colleagues,
Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase.
The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA.
The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts
The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-06
And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/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 <routing-wg@ripe.net> before 12 September 2019.
Kind regards,
Marco Schmidt Policy Officer RIPE NCC
+1 Den 14 aug. 2019 17:18 skrev Melchior Aelmans <melchior@aelmans.eu>: +1 we should do this now. On Wed, Aug 14, 2019 at 5:06 PM Paul Hoogsteder <paul@meanie.nl<mailto:paul@meanie.nl>> wrote: Yes, I think we should go ahead with this. Kind regards, Paul Hoogsteder. On 14 Aug 2019, at 16:00, Job Snijders <job@ntt.net<mailto:job@ntt.net>> wrote: Dear all, Thank you for putting together an impact analysis! I believe this write-up by RIPE NCC demonstrates the staff have a good understanding of the policy proposal. As one of the proposers, I believe that (short of deleting RIPE-NONAUTH entirely) this proposal is gentle and sane mechanism to incrementally clean up the un-validated RIPE-NONAUTH data source. I look forward to hearing the groups’ thoughts on how to proceed. Kind regards, Job On Wed, 14 Aug 2019 at 15:24, Marco Schmidt <mschmidt@ripe.net<mailto:mschmidt@ripe.net>> wrote: Dear colleagues, Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community’s discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-06 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/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 <routing-wg@ripe.net<mailto:routing-wg@ripe.net>> before 12 September 2019. Kind regards, Marco Schmidt Policy Officer RIPE NCC
?+1 - Torunn ________________________________ Fra: routing-wg <routing-wg-bounces@ripe.net> på vegne av Andreas Larsen <andreas@1o.se> Sendt: 14. august 2019 17:28 Til: Melchior Aelmans Kopi: RIPE Routing Working Group Emne: Re: [routing-wg] 2018-06 Review Phase (RIPE NCC IRR Database Non-Authoritative Route Object Clean-up) +1 Den 14 aug. 2019 17:18 skrev Melchior Aelmans <melchior@aelmans.eu>: +1 we should do this now. On Wed, Aug 14, 2019 at 5:06 PM Paul Hoogsteder <paul@meanie.nl<mailto:paul@meanie.nl>> wrote: Yes, I think we should go ahead with this. Kind regards, Paul Hoogsteder. On 14 Aug 2019, at 16:00, Job Snijders <job@ntt.net<mailto:job@ntt.net>> wrote: Dear all, Thank you for putting together an impact analysis! I believe this write-up by RIPE NCC demonstrates the staff have a good understanding of the policy proposal. As one of the proposers, I believe that (short of deleting RIPE-NONAUTH entirely) this proposal is gentle and sane mechanism to incrementally clean up the un-validated RIPE-NONAUTH data source. I look forward to hearing the groups' thoughts on how to proceed. Kind regards, Job On Wed, 14 Aug 2019 at 15:24, Marco Schmidt <mschmidt@ripe.net<mailto:mschmidt@ripe.net>> wrote: Dear colleagues, Policy proposal 2018-06, "RIPE NCC IRR Database Non-Authoritative Route Object Clean-up", is now in the Review Phase. The goal of the proposal is to delete an non-authoritative object stored in the RIPE IRR, if it conflicts with an RPKI ROA. The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts The RIPE NCC has prepared an impact analysis on this latest proposal version to support the community's discussion. You can find the full proposal and impact analysis at: https://www.ripe.net/participate/policies/proposals/2018-06 And the draft documents at: https://www.ripe.net/participate/policies/proposals/2018-06/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 <routing-wg@ripe.net<mailto:routing-wg@ripe.net>> before 12 September 2019. Kind regards, Marco Schmidt Policy Officer RIPE NCC
Marco Schmidt wrote on 14/08/2019 17:24:
The proposal has been updated following the last round of discussion and is now at version v3.0. Some of the differences from version v2.0 include: - Provides details about the process how to identify and solve conflicts
this version addresses all the issues that I brought up previously, so looks good to go. Nick
participants (10)
-
Andreas Larsen -
Carlos Friaças -
Chriztoffer Hansen -
Job Snijders -
Marco Schmidt -
Melchior Aelmans -
Nick Hilliard -
Paul Hoogsteder -
Tore Anderson -
Torunn.Narvestad＠telenor.com