nanog mailing list archives
Re: ticketmaster.com 403 Forbidden
From: Rich Kulawiec <rsk () gsp org>
Date: Mon, 6 Feb 2017 17:09:43 -0500
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
Current thread:
- Re: ticketmaster.com 403 Forbidden, (continued)
- Re: ticketmaster.com 403 Forbidden Benjamin Hatton (Feb 06)
- Re: ticketmaster.com 403 Forbidden Niels Bakker (Feb 06)
- Re: ticketmaster.com 403 Forbidden Ethan E. Dee (Feb 06)
- Re: ticketmaster.com 403 Forbidden mike . lyon (Feb 06)
- Re: ticketmaster.com 403 Forbidden Suresh Ramasubramanian (Feb 06)
- Re: ticketmaster.com 403 Forbidden Jon Meek (Feb 06)
- Re: ticketmaster.com 403 Forbidden Ethan E. Dee (Feb 06)
- Re: ticketmaster.com 403 Forbidden Ken Matlock (Feb 06)
- Re: ticketmaster.com 403 Forbidden Ethan E. Dee (Feb 06)
- Re: ticketmaster.com 403 Forbidden Ken Chase (Feb 06)
- Re: ticketmaster.com 403 Forbidden Rich Kulawiec (Feb 06)
- Re: ticketmaster.com 403 Forbidden Ethan E. Dee (Feb 06)
- Re: ticketmaster.com 403 Forbidden joel jaeggli (Feb 06)
- RE: ticketmaster.com 403 Forbidden Manser, Charles J (Feb 07)