Re: RE: [Asrg] C/R Framework

Yakov Shafranovich <research@solidmatrix.com> Thu, 15 May 2003 15:50 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 LAA12972 for <asrg-archive@odin.ietf.org>; Thu, 15 May 2003 11:50:12 -0400 (EDT)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4FFHGd09822 for asrg-archive@odin.ietf.org; Thu, 15 May 2003 11:17:16 -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 h4FFHGB09819 for <asrg-web-archive@optimus.ietf.org>; Thu, 15 May 2003 11:17:16 -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 LAA12954; Thu, 15 May 2003 11:49:41 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GL16-0000Gg-00; Thu, 15 May 2003 11:51:36 -0400
Received: from ietf.org ([132.151.1.19] helo=www1.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19GL15-0000Gd-00; Thu, 15 May 2003 11:51:35 -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 h4FFD7B09578; Thu, 15 May 2003 11:13:07 -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 h4FFCgB09544 for <asrg@optimus.ietf.org>; Thu, 15 May 2003 11:12:42 -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 LAA12831 for <asrg@ietf.org>; Thu, 15 May 2003 11:45:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GKwg-0000Eo-00 for asrg@ietf.org; Thu, 15 May 2003 11:47:02 -0400
Received: from 000-253-545.area7.spcsdns.net ([68.27.230.54] helo=68.27.230.54 ident=trilluser) by ietf-mx with smtp (Exim 4.12) id 19GKwe-0000El-00 for asrg@ietf.org; Thu, 15 May 2003 11:47:01 -0400
Message-Id: <5.2.0.9.2.20030515114556.02fa07a8@std5.imagineis.com>
X-Sender: research@solidmatrix.com
X-Mailer: QUALCOMM Windows Eudora Version 5.2.0.9
To: asrg@ietf.org
From: Yakov Shafranovich <research@solidmatrix.com>
Subject: Re: RE: [Asrg] C/R Framework
In-Reply-To: <E19GJly-0002DN-00@argon.connect.org.uk>
References: <MBEKIIAKLDHKMLNFJODBAEAGFDAA.eric@purespeed.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-MimeHeaders-Plugin-Info: v2.03.00
X-GCMulti: 1
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 11:47:39 -0400

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:

---snip----

2.2.3. Long Header Fields

    Each header field is logically a single line of characters comprising
    the field name, the colon, and the field body.  For convenience
    however, and to deal with the 998/78 character limitations per line,
    the field body portion of a header field can be split into a multiple
    line representation; this is called "folding".  The general rule is
    that wherever this standard allows for folding white space (not
    simply WSP characters), a CRLF may be inserted before any WSP.  For
    example, the header field:
            Subject: This is a test
    can be represented as:
            Subject: This
             is a test
    Note: Though structured field bodies are defined in such a way that
    folding can take place between many of the lexical tokens (and even
    within some of the lexical tokens), folding SHOULD be limited to
    placing the CRLF at higher-level syntactic breaks.  For instance, if
    a field body is defined as comma-separated values, it is recommended
    that folding occur after the comma separating the structured items in
    preference to other places where the field could be folded, even if
    it is allowed elsewhere.
    The process of moving from this folded multiple-line representation
    of a header field to its single line representation is called
    "unfolding". Unfolding is accomplished by simply removing any CRLF
    that is immediately followed by WSP.  Each header field should be
    treated in its unfolded form for further syntactic and semantic
    evaluation."

---snip----

---------------------------------------------------------------------------------------------------
Yakov Shafranovich / <research@solidmatrix.com>
SolidMatrix Research, a division of SolidMatrix Technologies, Inc.
---------------------------------------------------------------------------------------------------
"One who watches the wind will never sow, and one who keeps his eyes on
the clouds will never reap" (Ecclesiastes 11:4)
---------------------------------------------------------------------------------------------------  

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