[arin-ppml] prop266 - re-framing the discussion

Adam Thompson athompson at merlin.mb.ca
Fri May 3 12:39:51 EDT 2019

No.  But it would be appropriate IMHO to adopt policies that very strongly promote MANRS (or even a subset of it), and/or very strongly encourage ARIN members/customers/clients to adopt MANRS, and/or discourage non-MANRS-compliant number resource holders in some way.

Adam Thompson
Consultant, Infrastructure Services
100 - 135 Innovation Drive
Winnipeg, MB, R3T 6A8
(204) 977-6824 or 1-800-430-6404 (MB only)
athompson at merlin.mb.ca<mailto:athompson at merlin.mb.ca>

From: ARIN-PPML <arin-ppml-bounces at arin.net> On Behalf Of John Curran
Sent: Thursday, May 2, 2019 5:15 PM
To: Tom Samplonius <tsamplonius at ubn.ca>
Cc: Andrew Bagrin <abagrin at omninet.io>; arin-ppml at arin.net
Subject: Re: [arin-ppml] prop266 - re-framing the discussion

On May 2, 2019, at 4:54 PM, Tom Samplonius <tsamplonius at ubn.ca<mailto:tsamplonius at ubn.ca>> wrote:

  The Internet Society has created the MANRS initiative (https://www.manrs.org/) to encourage all networks globally to implement route security (among other things), but strangely there hasn’t been a single mention of it in any of these threads.  MANRS is the best way to address hijacking, since it prevents hijacking from even happening (along with other bad things like spoofing).

Tom -

Excellent point.   If the ISP community supports MANRS, the problem will be gone.

Is it really appropriate for the RIR system become embroiled in routing enforcement before the ISPs show widespread support for good routing hygiene?


John Curran
President and CEO
American Registry for Internet Numbers

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190503/380a5ec2/attachment-0002.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 2381 bytes
Desc: image001.png
URL: <https://lists.arin.net/pipermail/arin-ppml/attachments/20190503/380a5ec2/attachment-0002.png>

More information about the ARIN-PPML mailing list