Re: Re declare SPF and Sender-ID to be Informational

Dave Crocker <dhc2@dcrocker.net> Fri, 09 December 2005 22:43 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekqy5-0004qb-Ow; Fri, 09 Dec 2005 17:43:57 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Ekqy3-0004oT-OE for ietf@megatron.ietf.org; Fri, 09 Dec 2005 17:43:55 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA21970 for <ietf@ietf.org>; Fri, 9 Dec 2005 17:42:51 -0500 (EST)
Received: from sb7.songbird.com ([208.184.79.137]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ekqy9-0001dE-Q5 for ietf@ietf.org; Fri, 09 Dec 2005 17:44:03 -0500
Received: from [192.168.0.3] (adsl-71-131-4-199.dsl.sntc01.pacbell.net [71.131.4.199]) (authenticated bits=0) by sb7.songbird.com (8.12.11/8.12.11) with ESMTP id jB9MhWiR006653 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 9 Dec 2005 14:43:44 -0800
Message-ID: <439A086A.10705@dcrocker.net>
Date: Fri, 09 Dec 2005 14:42:50 -0800
From: Dave Crocker <dhc2@dcrocker.net>
User-Agent: Thunderbird 1.5 (Windows/20051025)
MIME-Version: 1.0
To: John Levine <johnl@iecc.com>
References: <20051209221401.9125.qmail@xuxa.iecc.com>
In-Reply-To: <20051209221401.9125.qmail@xuxa.iecc.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-SongbirdInformation: support@songbird.com for more information
X-Songbird: Found to be clean
X-Songbird-From: dhc2@dcrocker.net
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de
Content-Transfer-Encoding: 7bit
Cc: braden@ISI.EDU, ietf@ietf.org
Subject: Re: Re declare SPF and Sender-ID to be Informational
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

>
> I'd suggest the most sensible thing to do is to reclassify both of them
> as Informational, to document what you might find in some TXT records,
> publish them, and be done with it.

Yes. This seems like exactly the right choice, since it is what is 
typically done for documenting
existing practise that is outside the IETF process.

d/

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf