<html><head></head><body><div class="ydpba03dbfcyahoo-style-wrap" style="font-family:Helvetica Neue, Helvetica, Arial, sans-serif;font-size:16px;"><div></div>
<div>Hi Guys</div><div><br></div><div>There are a couple of errors in this policy proposal wording. In the first bullet point on 'Arguments supporting the proposal' it says:</div><div><br></div><div>"<span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;">Presently, routing registry data can be found within both the RIPE IRR, RIPE-NONAUTH IRR, and RIPE’s RPKI ROA database. For the first two of these three sources, the community can trust that the owner of the resource gave explicit permission. This is not the case for RIPE-NONAUTH"</span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;"><br></span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;">The order of the sources doesn't match the comment about the 'first two'.</span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;"><br></span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;">Also 'both' means 'two'. This should say 'within each of' (just to be correct :) )</span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;"><br></span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;">cheers</span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;">denis</span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;"><br></span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;">co-chair DB-WG</span></span></div><div><span><span style="color: rgb(51, 51, 51); font-family: Open Sans, Helvetica, Arial, sans-serif; font-size: 14.3px;"><br></span></span></div><div><br></div>
</div><div id="ydpb0eaf8b8yahoo_quoted_9504241558" class="ydpb0eaf8b8yahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
On Wednesday, 29 May 2019, 07:31:50 CEST, Cosmin Lupu <cosmin@lupu.be> wrote:
</div>
<div><br></div>
<div><br></div>
<div><div id="ydpb0eaf8b8yiv7663608787"><div><div dir="ltr"><div>Have a look on the following proposal which is now in discussion phase<br clear="none"></div><div><br clear="none"></div><div><a shape="rect" href="https://www.ripe.net/participate/policies/proposals/2018-06" rel="nofollow" target="_blank">https://www.ripe.net/participate/policies/proposals/2018-06</a></div><div><br clear="none"></div><div><br clear="none"></div></div><br clear="none"><div class="ydpb0eaf8b8yiv7663608787yqt8281548429" id="ydpb0eaf8b8yiv7663608787yqt28958"><div class="ydpb0eaf8b8yiv7663608787gmail_quote"><div class="ydpb0eaf8b8yiv7663608787gmail_attr" dir="ltr">On Wed, May 29, 2019 at 7:16 AM Delacruz, Anthony B <<a shape="rect" href="mailto:Anthony.DeLaCruz@centurylink.com" rel="nofollow" target="_blank">Anthony.DeLaCruz@centurylink.com</a>> wrote:<br clear="none"></div><blockquote class="ydpb0eaf8b8yiv7663608787gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex;">Just referring to NONAUTH. I recycle and clean up 300K+ IP's every year and part of that is clearing reverse, blacklist, and IRR entries. RIPE has been an annoyance of mine for years with requests to get stale IRR pulled on items we own being a fight but nowhere near as bad as ALTDB that never responds to asks. The L3 now CTL IRR has been owned and managed all this time and easy to get updates. Reach out to the NOC or send in an ask to ipadmin and it'll be checked and corrected. All of them suffer even ours suffer from the litter left behind and we have efforts to clear that out, but more just comes in daily. My main concern and ask here is getting the NCC to take action and clear out items I know are wrong on space I own and can prove I own in other ways than just RPKI.<br clear="none">
<br clear="none">
-----Original Message-----<br clear="none">
From: Jared Mauch [mailto:<a shape="rect" href="mailto:jared@puck.nether.net" rel="nofollow" target="_blank">jared@puck.nether.net</a>]<br clear="none">
Sent: Tuesday, May 28, 2019 6:20 PM<br clear="none">
To: Delacruz, Anthony B<br clear="none">
Cc: <a shape="rect" href="mailto:routing-wg@ripe.net" rel="nofollow" target="_blank">routing-wg@ripe.net</a><br clear="none">
Subject: Re: [routing-wg] 2018-06 Can we have additional methods for validation or have the NCC not be so obstinate on doing removals<br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
> On May 28, 2019, at 7:09 PM, Delacruz, Anthony B <Anthony.DeLaCruz@CenturyLink.com> wrote:<br clear="none">
><br clear="none">
> I’m very appreciative for the efforts here to clean out the IRR. I am a major resource holder with IP’s and ASN’s from all the RIR and we also run an IRR. I am often frustrated that when I open a ticket with the NCC and even place an entry in whois on space I own that is clearly listed wrong in RIPE-NONAUTH IRR that it is a multi week struggle to get entries removed and they have me chase the contact that put in the entry which is often not responsive.<br clear="none">
><br clear="none">
> Since not all of my space right now is easily taken care of using RPKI for this, I would very much like to suggest additional methods be available for the NCC to consider a valid request for removal. Other IRR’s I work with we usually send the request from the MNT or POC that is on the account/orgid/lir listed with the RIR and in some cases I go as far as to set whois on the blocks with various messages like “please clear, IRR BAD, Hijacked, Recovered Space” and several other messages to make it understood the range has some reason we don’t want an IRR entry to be showing for it. Many of the dozen other IRR are quick and a pleasure to work with but the NCC is not ever easy or prompt on the cases I have put in.<br clear="none">
> This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.<br clear="none">
<br clear="none">
Is this just with RIPE-NONAUTH, or in the regular source: RIPE objects?<br clear="none">
<br clear="none">
RIPE-NONAUTH is a bit of a wild-west and I suspect most people would be best served if they stopped building filters with that set unless their customers specifically requested it.<br clear="none">
<br clear="none">
I’ll also make note that the Level3 (now CTL?) IRR has not had an owner for many years and people have had a hard time communicating about issues with objects there. I understand why cleanup is hard or unpopular (it’s like picking up litter, there’s little reward or notice that the trash was taken away).<br clear="none">
<br clear="none">
- Jared<br clear="none">
<br clear="none">
<br clear="none">
<br clear="none">
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.<br clear="none">
</blockquote></div></div></div></div></div>
</div>
</div></body></html>