Re: RE: [Asrg] C/R Framework

"Jon Kyme" <jrk@merseymail.com> Thu, 15 May 2003 16:03 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 MAA13597 for <asrg-archive@odin.ietf.org>; Thu, 15 May 2003 12:03:19 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4FFUOp10721 for asrg-archive@odin.ietf.org; Thu, 15 May 2003 11:30:24 -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 h4FFUOB10718 for <asrg-web-archive@optimus.ietf.org>; Thu, 15 May 2003 11:30:24 -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 MAA13572; Thu, 15 May 2003 12:02:49 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GLDn-0000P7-00; Thu, 15 May 2003 12:04:43 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GLDn-0000P4-00; Thu, 15 May 2003 12:04:43 -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 h4FFQ3B10358; Thu, 15 May 2003 11:26:03 -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 h4FFOlB10268 for <asrg@optimus.ietf.org>; Thu, 15 May 2003 11:24:47 -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 LAA13227 for <asrg@ietf.org>; Thu, 15 May 2003 11:57:12 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GL8M-0000K8-00 for asrg@ietf.org; Thu, 15 May 2003 11:59:06 -0400
Received: from argon.connect.org.uk ([193.110.243.33]) by ietf-mx with esmtp (Exim 4.12) id 19GL8M-0000K5-00 for asrg@ietf.org; Thu, 15 May 2003 11:59:06 -0400
Received: from mmail by argon.connect.org.uk with local (connectmail/exim) id 19GL9N-00071m-00; Thu, 15 May 2003 17:00:09 +0100
In-Reply-To: <5.2.0.9.2.20030515114556.02fa07a8@std5.imagineis.com>
Subject: Re: RE: [Asrg] C/R Framework
To: Yakov Shafranovich <research@solidmatrix.com>
From: Jon Kyme <jrk@merseymail.com>
Cc: ASRG <asrg@ietf.org>
X-Mailer: [ConnectMail 3.5.4]
X-connectmail-Originating-IP: 172.25.243.3
Message-Id: <E19GL9N-00071m-00@argon.connect.org.uk>
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, 15 May 2003 17:00:09 +0100

> At 03:31 PM 5/15/2003 +0100, Jon Kyme wrote:
> 
> 
> > > So, the recipients should be listed individually...whether we can use
> a
> > > delimeter with the authenticator following..might be a better method.
> > >
> > >
> > >
> >like:
> >X-something: recipient-1 ; auth-string-1
> >X-something: recipient-2 ; auth-string-2
> >etc...
> >
> >Regarding the length of the authentication string, is there an issue
> with
> >header line length?
> 
> We can fold the headers onto extra lines - see section 2.2.3 of RFC 2822:
> 

Yes, I've read that... are we expecting much whitespace inside the
authentication string?






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