November 2019 - anti-abuse-wg

2019-08 New Policy Proposal (RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space) to be discussed on Routing Working Group Mailing List
by Petrit Hasani 23 Dec '19

23 Dec '19

Dear colleagues, A new RIPE Policy proposal, 2019-08, "RPKI ROAs for Unallocated and Unassigned RIPE NCC Address Space", is now available for discussion in the Routing Working Group This proposal aims to instructs the RIPE NCC to create ROAs with origin AS0 for all unallocated and unassigned address space under its control. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-08 This proposed policy may be of interest to the Anti-Abuse working group as well. Therefore, we encourage you to review this proposal and send your comments to <routing-wg(a)ripe.net> before 29 November 2019. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

5 4

Non-ASCII characters in abuse-mailbox addresses
by Thomas Hungenberg 21 Nov '19

21 Nov '19

Hi, some abuse contacts registered with RIPE use non-ascii characters with the abuse-mailbox addresses, e.g. % Abuse contact for '195.78.76.0 - 195.78.77.255' is 'abuse(a)xn--zrich-kva.email' However, the corresponding MTA does not support SMTPUTF8: 7B579403C6: to=<abuse(a)xn--zrich-kva.email>, relay=mail.xn--zrich-kva.email[109.95.241.50]:25, delay=0.33, delays=0.01/0/0.32/0, dsn=5.6.7, status=bounced (SMTPUTF8 is required, but was not offered by host mail.xn--zrich-kva.email[109.95.241.50]) (In this particular case, sending email to the IDNA representation of the email address <abuse(a)xn--zrich-kva.email> works.) In our experience, using umlauts and other non-ascii characters in (the host part of) email addresses still cause a lot of problems in general. Even if the recipient's MX supports SMTPUTF8 correctly, MTAs on the transport way may fail to handle SMTPUTF8 messages. To prevent such problems and make sure all abuse mailboxes can be addressed, I wonder if the values of abuse-mailbox attributes should be restricted to ASCII characters only. What do you think? - Thomas

6 9

New on RIPE Labs: Better Mail Security with DANE for SMTP
by Mirjam Kuehne 20 Nov '19

20 Nov '19

Dear colleagues, What are the risks associated with SMTP and how can DANE help to overcome these? Here is a list of tips and suggestions provided by Dennis Baaten and Internet.nl: https://labs.ripe.net/Members/dennis_baaten/better-mail-security-with-dane-… Kind regards, Mirjam Kühne RIPE NCC

1 0

2019-04 Discussion Period extended until 9 December 2019 (Validation of "abuse-mailbox")
by Petrit Hasani 11 Nov '19

11 Nov '19

Dear colleagues, The Discussion Period for the policy proposal 2019-04, "Validation of "abuse-mailbox"" has been extended until 09 December 2019. This proposal aims to have the RIPE NCC validate "abuse-c:" information more often, and introduces a new validation process that requires input from resource holders. You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2019-04 We encourage you to review this proposal and send your comments to <anti-abuse-wg(a)ripe.net>. Kind regards, -- Petrit Hasani Policy Officer RIPE NCC

2 1