IETF Logo Mail Archive

Re: [ietf-smtp] Proper definition of the term "email payload".

Dave Crocker <dhc@dcrocker.net> Mon, 01 April 2019 14:31 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6D7120152 for <ietf-smtp@ietfa.amsl.com>; Mon, 1 Apr 2019 07:31:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.801
X-Spam-Level:
X-Spam-Status: No, score=-0.801 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=dcrocker.net
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T8ZVK02x2teq for <ietf-smtp@ietfa.amsl.com>; Mon, 1 Apr 2019 07:31:17 -0700 (PDT)
Received: from simon.songbird.com (simon.songbird.com [72.52.113.5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3864E120195 for <ietf-smtp@ietf.org>; Mon, 1 Apr 2019 07:31:06 -0700 (PDT)
Received: from [192.168.1.85] (108-226-162-63.lightspeed.sntcca.sbcglobal.net [108.226.162.63]) (authenticated bits=0) by simon.songbird.com (8.14.4/8.14.4/Debian-4.1ubuntu1.1) with ESMTP id x31EWmca011980 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT) for <ietf-smtp@ietf.org>; Mon, 1 Apr 2019 07:32:48 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dcrocker.net; s=default; t=1554129168; bh=98JBv+wkmaxiGyj5vVKRXuF66+ZybPiSC6tGGbcQlrE=; h=Subject:To:References:Reply-To:From:Date:In-Reply-To:From; b=Rtu86M5ePjjcF7VyUF9jfLhcQuqk1zQhdgKW4splUrpybMoPDDJA8SSJN+Q+N7zFP Xy2AHV5koeyNTuH/8asxlEaFrzZl5XVlzPL+/vkHO4mEK6HIlMF7WzDRYcf+62MhrU z/BGiW6iH4hxxNDPU+63fup3+Yg5carEIQTLKv6U=
To: ietf-smtp@ietf.org
References: <20190401000943.57BB2143638@mail.wooz.org> <FCBB7422-295F-4E58-AC4E-42A6894C6406@python.org> <75720834-0bdc-deba-40fc-24f17d5a6752@msapiro.net> <CAOEezJQo=TQcBqVGypW4YD4rLT0JNnfa1zZ9eh1gjQz9Cz8htA@mail.gmail.com> <221B317451ECA8F7674E1AE6@PSB> <6029.1554092559@turing-police>
Reply-To: dcrocker@bbiw.net
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
Message-ID: <9bcaa2ee-9b36-8e12-521e-4c2748a0050a@dcrocker.net>
Date: Mon, 01 Apr 2019 07:30:55 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <6029.1554092559@turing-police>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/1Gg_u8ChU3DbwtFIIIREMKvaJeM>
Subject: Re: [ietf-smtp] Proper definition of the term "email payload".
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2019 14:31:19 -0000

On 3/31/2019 9:22 PM, Valdis Klētnieks wrote:
> And then there's "payload" as seen from the Ethernet, IP, and TCP
> layers...

So.  It's payloads, all the way down...


d/
-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net

v2.23.0 | Report a Bug | By Email