[120132] in North American Network Operators' Group

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

Re: best practices for PTR naming and whois (was, sadly, Re: Arrogant

daemon@ATHENA.MIT.EDU (Michael Thomas)
Thu Dec 10 11:43:18 2009

Date: Thu, 10 Dec 2009 08:42:28 -0800
From: Michael Thomas <mike@mtcc.com>
To: Mark Andrews <marka@isc.org>
In-Reply-To: <200912101638.nBAGc01C004456@drugs.dv.isc.org>
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

On 12/10/2009 08:38 AM, Mark Andrews wrote:
> In message<4B211DA6.9000203@mtcc.com>, Michael Thomas writes:
> To Crocker's point though: if IETF came up with a way to publish your network's
>> dynamic space (assuming that's The Problem!), would operators do that? Or is
>> this another case where the energy barrier is too high?
>>
>> Mike
>
> The way to do this is to put other data in the ip6.arpa/in-addr.arpa and
> stop trying to infer things from the PTR records.

Sigh. What is the "this" to which you refer?

The problem space here is what's important. And I think it's worth considering
that port 25 isn't the only abuse vector anymore.

Mike


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