IETF Logo Mail Archive

[domainrep] rDNS identifiers

Jacob R Rideout <ietf@jacobrideout.net> Fri, 29 June 2012 18:37 UTC

Return-Path: <ietf@jacobrideout.net>
X-Original-To: domainrep@ietfa.amsl.com
Delivered-To: domainrep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7A2A321F86BD for <domainrep@ietfa.amsl.com>; Fri, 29 Jun 2012 11:37:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GuQToLoiMMNM for <domainrep@ietfa.amsl.com>; Fri, 29 Jun 2012 11:37:52 -0700 (PDT)
Received: from jacobrideout.net (jacobrideout.net [74.50.50.180]) by ietfa.amsl.com (Postfix) with ESMTP id 57BB021F86AB for <domainrep@ietf.org>; Fri, 29 Jun 2012 11:37:52 -0700 (PDT)
Received: from mail-bk0-f44.google.com (mail-bk0-f44.google.com [209.85.214.44]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by jacobrideout.net (Postfix) with ESMTPSA id 4C92140018 for <domainrep@ietf.org>; Fri, 29 Jun 2012 12:37:51 -0600 (MDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=jacobrideout.net; s=2012a; t=1340995071; bh=slLhW2bR5/oR5ifwWcqxensXNGoedXSgHTMZmG3vipc=; h=Reply-To:From:Date:Subject:To:From; b=EBPSrpCwRELj31ybScvdOAX27shIkpEsPHOkFcVNJfTR/Xjovyla6geYJzjYlH6ap eEF5fFsZVCYGQEoQHxy4KJiU4GqXTid1pR2smhbUAWejQm/Zr/5+/NeEN0avkwBee3 T23SC13RDayzhW8dQYLznusKryT03xN6VOXsEoSY=
Received: by bkty8 with SMTP id y8so3572272bkt.31 for <domainrep@ietf.org>; Fri, 29 Jun 2012 11:37:49 -0700 (PDT)
Received: by 10.204.156.137 with SMTP id x9mr1573567bkw.135.1340995069295; Fri, 29 Jun 2012 11:37:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.204.224.74 with HTTP; Fri, 29 Jun 2012 11:37:29 -0700 (PDT)
From: Jacob R Rideout <ietf@jacobrideout.net>
Date: Fri, 29 Jun 2012 12:37:29 -0600
Message-ID: <CAK+pC_-tOXvq1OSqiT6=vn+0UYGWpNogB9TQoy7vGbaQR-a+ag@mail.gmail.com>
To: domainrep@ietf.org
Content-Type: text/plain; charset="UTF-8"
Subject: [domainrep] rDNS identifiers
X-BeenThere: domainrep@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: ietf@jacobrideout.net
List-Id: Domain Reputation discussion list <domainrep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/domainrep>, <mailto:domainrep-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/domainrep>
List-Post: <mailto:domainrep@ietf.org>
List-Help: <mailto:domainrep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/domainrep>, <mailto:domainrep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jun 2012 18:37:53 -0000

I just read draft-ietf-repute-email-identifiers-04.

Has anyone on the list considered the use of the IPv4 (or v6) PTR rDNS
value as an
identifier? Or more strictly, a fully qualified domain name, that also
resolves to the
queried IP address.

I know of several filtering systems that make use of this identifier
as an identity
token to fix reputation.

Jacob Rideout
Product Manager, Anti-Spam
Return Path, Inc.

v2.23.0 | Report a Bug | By Email