Re: [apps-discuss] possibleTrace fields registry

Nico Williams <nico@cryptonector.com> Tue, 17 January 2012 20:44 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C8DF021F873A for <apps-discuss@ietfa.amsl.com>; Tue, 17 Jan 2012 12:44:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level:
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id sV9H8IvxNZZS for <apps-discuss@ietfa.amsl.com>; Tue, 17 Jan 2012 12:44:56 -0800 (PST)
Received: from homiemail-a74.g.dreamhost.com (caiajhbdccah.dreamhost.com [208.97.132.207]) by ietfa.amsl.com (Postfix) with ESMTP id 2F54821F8734 for <apps-discuss@ietf.org>; Tue, 17 Jan 2012 12:44:56 -0800 (PST)
Received: from homiemail-a74.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a74.g.dreamhost.com (Postfix) with ESMTP id A4CC267C07A for <apps-discuss@ietf.org>; Tue, 17 Jan 2012 12:44:52 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; q=dns; s= cryptonector.com; b=A91cIWxaMZJ5SUFNTuFbLx7r3T1EI6eo7i1maT0o5ju5 dpZee+isFYjFK6H1h6qi3Zy9EIN5BHVJ70krFKuyVUs5/1son4wpZi0frXmkhgpD k2ytJzhicRKjaJBiHcOX3p3BzDZmGJxp21+HqjG958EkrqXv5MH9r3obXYbRGZQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=BXv2n4qEaZSm9vQAeSS0GS7+pYo=; b=RmWd9BZ3J0K /+Q7Idajwa21BEtn3Jpw0xxqNKj9czlM2HXIGBBb3qUVDR99WJVBrUx63eKFV/Sh nVYyEGuCT9VMc9FFDggFkgQdWHwsqcFa20CLAlTx124ccVp6+0TlVcu3HA7PpAIu 7i30D5ndf1M1wZ67T4LGHKu1SuN3TA4I=
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a74.g.dreamhost.com (Postfix) with ESMTPSA id 430C067C079 for <apps-discuss@ietf.org>; Tue, 17 Jan 2012 12:44:50 -0800 (PST)
Received: by pbbb2 with SMTP id b2so4394953pbb.31 for <apps-discuss@ietf.org>; Tue, 17 Jan 2012 12:44:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.68.73.196 with SMTP id n4mr37320215pbv.33.1326833089841; Tue, 17 Jan 2012 12:44:49 -0800 (PST)
Received: by 10.68.220.105 with HTTP; Tue, 17 Jan 2012 12:44:49 -0800 (PST)
In-Reply-To: <4F15A667.4030708@dcrocker.net>
References: <20120115201817.34086.qmail@joyce.lan> <4F15A667.4030708@dcrocker.net>
Date: Tue, 17 Jan 2012 14:44:49 -0600
Message-ID: <CAK3OfOjgLXR4X22yjOH24RvkXZzUDwoPHhuwsjxwt6mTJTwsSA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: dcrocker@bbiw.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Cc: apps-discuss@ietf.org
Subject: Re: [apps-discuss] possibleTrace fields registry
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Jan 2012 20:44:56 -0000

On Tue, Jan 17, 2012 at 10:48 AM, Dave CROCKER <dhc@dcrocker.net> wrote:
> RFC5321:
>
>   4.1.1.4:
>
>   When the SMTP server accepts a message either for relaying or for
>   final delivery, it inserts a trace record (also referred to
>   interchangeably as a "time stamp line" or "Received" line) at the top
>   of the mail data.
>
>
>   4.4.  Trace Information
>
>   When an SMTP server receives a message for delivery or further
>   processing, it MUST insert trace ("time stamp" or "Received")
>   information at the beginning of the message content, as discussed in
>   Section 4.1.1.4.

I read 4.4 as implying that "Received" (a.k.a. "time stamp") is an
example of known trace headers.

I read 4.1.1.4 as implying that "Received" is the only then-known trace header.

I don't read either as excluding other trace headers -- it'd be quite
a stretch to do so.

At most we have an erratum against RFC5321, but a need to update it?
just for this?  IMO: no need to update RFC5321.

Nico
--