Re: [Asrg] CRI Header

Tony Hansen <tony@att.com> Thu, 05 June 2003 19:21 UTC

Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13123 for <asrg-archive@odin.ietf.org>; Thu, 5 Jun 2003 15:21:50 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h55JLLc01486 for asrg-archive@odin.ietf.org; Thu, 5 Jun 2003 15:21:21 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55JLLB01483 for <asrg-web-archive@optimus.ietf.org>; Thu, 5 Jun 2003 15:21:21 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA13100; Thu, 5 Jun 2003 15:21:19 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O0Gl-0002WM-00; Thu, 05 Jun 2003 15:19:27 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19O0Gk-0002WJ-00; Thu, 05 Jun 2003 15:19:26 -0400
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55JDJB00613; Thu, 5 Jun 2003 15:13:19 -0400
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h55J9TB00313 for <asrg@optimus.ietf.org>; Thu, 5 Jun 2003 15:09:29 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA11822 for <asrg@ietf.org>; Thu, 5 Jun 2003 15:09:23 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19O05D-0002Jm-00 for asrg@ietf.org; Thu, 05 Jun 2003 15:07:31 -0400
Received: from 75.209.219.209.transedge.com ([209.219.209.75] helo=ckmso2.proxy.att.com) by ietf-mx with esmtp (Exim 4.12) id 19O05D-0002JX-00 for asrg@ietf.org; Thu, 05 Jun 2003 15:07:31 -0400
Received: from maillennium.att.com ([135.25.114.99]) by ckmso2.proxy.att.com (AT&T IPNS/MSO-5.0) with ESMTP id h55J8run021839 for <asrg@ietf.org>; Thu, 5 Jun 2003 15:08:53 -0400
Received: from att.com (tony-ob.mt.att.com[135.91.246.200](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20030605190724gw100r9hile> (Authid: tony); Thu, 5 Jun 2003 19:07:24 +0000
Message-ID: <3EDF9560.1040805@att.com>
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030308
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Yakov Shafranovich <research@solidmatrix.com>
CC: "asrg@ietf.org" <asrg@ietf.org>
Subject: Re: [Asrg] CRI Header
References: <5.2.0.9.2.20030605105230.00b9c4c8@std5.imagineis.com>
In-Reply-To: <5.2.0.9.2.20030605105230.00b9c4c8@std5.imagineis.com>
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: asrg-admin@ietf.org
Errors-To: asrg-admin@ietf.org
X-BeenThere: asrg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=unsubscribe>
List-Id: Anti-Spam Research Group - IRTF <asrg.ietf.org>
List-Post: <mailto:asrg@ietf.org>
List-Help: <mailto:asrg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/asrg>, <mailto:asrg-request@ietf.org?subject=subscribe>
List-Archive: <https://www1.ietf.org/pipermail/asrg/>
Date: Thu, 05 Jun 2003 15:09:20 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Yakov Shafranovich wrote:
> At 11:15 PM 6/4/2003 -0400, Eric D. Williams wrote:
> 
> Both an "X-CRI" and "CRI" headers should be defined. Until the standard 
> gets approved, the "X-" headers will be used, once the standard is 
> approved then both the "X-CRI" and "CRI" headers are used. This is 
> similar to the HTTP protocol where both "gzip" and "x-gzip" are used to 
> indicate gzip encoding (RFC 2616, section 3.5).

I disagree. When you write the internet-draft, ONLY specify the CRI 
header. X- headers should only be used for doing experiments before you 
write the internet-draft. As soon as you enter the ietf-space, stick to 
the real name. x-gzip was specified to handle backward compatibility 
because there was considerable history with its use prior to the RFCs 
being written. You don't have that problem here -- there is no history 
of previous uses of X-CRI that needs to be supported.

	Tony Hansen
	tony@att.com

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