[193587] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: ticketmaster.com 403 Forbidden

daemon@ATHENA.MIT.EDU (Rich Kulawiec)
Mon Feb 6 17:49:18 2017

X-Original-To: nanog@nanog.org
Date: Mon, 6 Feb 2017 17:09:43 -0500
From: Rich Kulawiec <rsk@gsp.org>
To: nanog@nanog.org
In-Reply-To: <20170206173944.GR10696@sizone.org>
Errors-To: nanog-bounces@nanog.org

On Mon, Feb 06, 2017 at 12:39:44PM -0500, Ken Chase wrote:
> Seems to me this random prefix-based blocking by major sites, 
> then let's-use-nanog-to-fix-it, is not a great methodology.

You're correct.  It's not.

> What more 'official' and formalized mechanisms can we use?

RFC 2142 stipulates role addresses for a variety of functions, many of
which were in common use and some of which were considered best practices
even before they were formalized 20 years ago.  A *lot* of the traffic
here (and on other mailing lists) winds up here (and on other mailing lists)
because some incompetent/negligent operations don't support those.

---rsk

home help back first fref pref prev next nref lref last post