IETF Logo Mail Archive

RE: [Asrg] CRI Header

"Eric Dean" <eric@purespeed.com> Fri, 06 June 2003 14:29 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 KAA25906 for <asrg-archive@odin.ietf.org>; Fri, 6 Jun 2003 10:29:27 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h56ET2B27821 for asrg-archive@odin.ietf.org; Fri, 6 Jun 2003 10:29:02 -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 h56ET2B27818 for <asrg-web-archive@optimus.ietf.org>; Fri, 6 Jun 2003 10:29:02 -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 KAA25898; Fri, 6 Jun 2003 10:28:56 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OIBL-0002Wl-00; Fri, 06 Jun 2003 10:27:03 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19OIBK-0002Wi-00; Fri, 06 Jun 2003 10:27:02 -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 h56EObB27673; Fri, 6 Jun 2003 10:24:37 -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 h56ENpB27619 for <asrg@optimus.ietf.org>; Fri, 6 Jun 2003 10:23:51 -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 KAA25773 for <asrg@ietf.org>; Fri, 6 Jun 2003 10:23:45 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19OI6K-0002Ve-00 for asrg@ietf.org; Fri, 06 Jun 2003 10:21:52 -0400
Received: from [66.77.68.8] (helo=mailgate.purespeed.com) by ietf-mx with esmtp (Exim 4.12) id 19OI6J-0002VX-00 for asrg@ietf.org; Fri, 06 Jun 2003 10:21:51 -0400
Received: from purespeed.com (mail.purespeed.com [63.210.23.8]) by mailgate.purespeed.com (Postfix Relay Hub) with ESMTP id AA37613B75; Fri, 6 Jun 2003 10:27:58 -0400 (EDT)
Received: from HOMEY [68.100.19.195] by purespeed.com (SMTPD32-7.13) id A3D15900CE; Fri, 06 Jun 2003 10:23:13 -0400
From: Eric Dean <eric@purespeed.com>
To: Tony Hansen <tony@att.com>, asrg@ietf.org
Subject: RE: [Asrg] CRI Header
Message-ID: <MBEKIIAKLDHKMLNFJODBOEMHFHAA.eric@purespeed.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0)
Importance: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400
In-Reply-To: <3EDEA101.9070502@att.com>
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: Fri, 06 Jun 2003 10:25:44 -0400
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Wow, Tony!  Thanks. We will proceed accordingly.

> -----Original Message-----
> From: asrg-admin@ietf.org [mailto:asrg-admin@ietf.org]On Behalf Of Tony
> Hansen
> Sent: Wednesday, June 04, 2003 9:47 PM
> To: asrg@ietf.org
> Subject: Re: [Asrg] CRI Header
> 
> 
> Yakov Shafranovich wrote:
> > At 03:20 PM 6/4/2003 -0600, Vernon Schryver wrote:
> >> > ...
> >> > ok..optional headers or do we introduce a new one?  There isn't an 
> >> RFC 2822
> >> > registration process that I am aware of.
> >>
> >> See draft-klyne-msghdr-registry-06.txt
> > 
> > Currently, isn't it enough just to define a header in an RFC? This has 
> > been done for a number of headers.
> 
> Yes, that's all that should be needed: write an internet-draft defining 
> the new header and get it published as an RFC. If msghdr-registry gets 
> published as an RFC before this new I-D gets published as an RFC, then 
> the new I-D will also need to have an appropriate IANA Considerations 
> section that directs IANA to add the new header to the header registry.
> 
> 	Tony Hansen
> 	tony@att.com
> 
> _______________________________________________
> Asrg mailing list
> Asrg@ietf.org
> https://www1.ietf.org/mailman/listinfo/asrg
> 
_______________________________________________
Asrg mailing list
Asrg@ietf.org
https://www1.ietf.org/mailman/listinfo/asrg

v2.23.0 | Report a Bug | By Email