From beepwg-bounces@dbc.mtview.ca.us Tue May 30 20:06:56 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlEEi-00035h-2C for beep-archive@lists.ietf.org; Tue, 30 May 2006 20:06:56 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlEEg-0005l8-K5 for beep-archive@lists.ietf.org; Tue, 30 May 2006 20:06:56 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k4V05Hog003649; Tue, 30 May 2006 17:05:34 -0700 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) k4V05EiV003644 for ; Tue, 30 May 2006 17:05:15 -0700 Received: from root by ciao.gmane.org with local (Exim 4.43) id 1FlECs-00044C-5h for beepwg@lists.beepcore.org; Wed, 31 May 2006 02:05:02 +0200 Received: from adsl-71-154-201-182.dsl.sndg02.sbcglobal.net ([71.154.201.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 May 2006 02:05:02 +0200 Received: from seh by adsl-71-154-201-182.dsl.sndg02.sbcglobal.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 May 2006 02:05:02 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: beepwg@lists.beepcore.org From: "Steven E. Harris" Date: Tue, 30 May 2006 16:59:45 -0700 Organization: SEH Labs Lines: 35 Message-ID: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-71-154-201-182.dsl.sndg02.sbcglobal.net User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.13 (cygwin32) Cancel-Lock: sha1:nOgDPkx3m1L+q8ewFt0Pds8g3dw= Subject: [BEEPwg] Minimal presence of MIME headers in message payload X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Per RFC 3080 Section 2.2, MIME headers may be used to describe message payload content: ,---- | A message is structured according to the rules of MIME. Accordingly, | each message may begin with "entity-headers" (c.f., MIME's Section 3 | [1]). If none, or only some, of the "entity-headers" are present: `---- In the case where /no/ headers are present, is there just a spare CRLF pair at the beginning of the payload after the BEEP header? That is, would the following message be valid? ,---- | MSG 0 1 . 0 5 | | xxxEND `---- Or could one send the same content without the spare CRLF pair? ,---- | MSG 0 1 . 0 3 | xxxEND `---- With the latter, there would be no way to know where the MIME headers end (given that they never began), so the former example seems more likely to be the only valid choice. However, this base case with no headers is hard to resolve from the MIME ABNF, nor are there any similar header-less examples shown in RFC 3080 or 3081. Clarification would be appreciated. -- Steven E. Harris _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Wed May 31 11:55:31 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlT2h-000663-1t for beep-archive@lists.ietf.org; Wed, 31 May 2006 11:55:31 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlT2e-00030I-AV for beep-archive@lists.ietf.org; Wed, 31 May 2006 11:55:31 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k4VFsW0u017892; Wed, 31 May 2006 08:54:34 -0700 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) k4VFsVuN017889 for ; Wed, 31 May 2006 08:54:31 -0700 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FlT1U-0003hW-G7 for beepwg@lists.beepcore.org; Wed, 31 May 2006 17:54:16 +0200 Received: from adsl-71-154-201-182.dsl.sndg02.sbcglobal.net ([71.154.201.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 May 2006 17:54:16 +0200 Received: from seh by adsl-71-154-201-182.dsl.sndg02.sbcglobal.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 May 2006 17:54:16 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: beepwg@lists.beepcore.org From: "Steven E. Harris" Date: Wed, 31 May 2006 08:52:59 -0700 Organization: SEH Labs Lines: 24 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-71-154-201-182.dsl.sndg02.sbcglobal.net User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.13 (cygwin32) Cancel-Lock: sha1:QEjxlzySiGslvUWGjJXBINg9cI0= Subject: [BEEPwg] Re: Minimal presence of MIME headers in message payload X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by drakken.dbc.mtview.ca.us id k4VFsW0u017892 X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a "Steven E. Harris" writes: > In the case where /no/ headers are present, is there just a spare > CRLF pair at the beginning of the payload after the BEEP header? I found a message from this mailing list in August 2000=B9 that shows a more detailed ABNF indicating the payload content requires at least one CRLF pair: mime =3D payload =3D [mime] CR LF *OCTET I have not yet found a follow-up message arguing against this definition, but it apparently did not make it into RFC 3080. Footnotes:=20 =B9 [BXXPwg] proposal for 1:N interactions Marshall Rose http://drakken.dbc.mtview.ca.us/pipermail/beepwg/2000-August/000823.htm= l --=20 Steven E. Harris _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Wed May 31 12:36:20 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlTgC-0007MR-Ko for beep-archive@lists.ietf.org; Wed, 31 May 2006 12:36:20 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlTgB-0006j0-8O for beep-archive@lists.ietf.org; Wed, 31 May 2006 12:36:20 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k4VGZJPn018495; Wed, 31 May 2006 09:35:20 -0700 Received: from [IPv6:::1] (localhost.localdomain [127.0.0.1]) k4VGZCu7018488; Wed, 31 May 2006 09:35:14 -0700 In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v750) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <3F7EFD18-D275-4E1C-AF8D-187AB831F687@dbc.mtview.ca.us> Content-Transfer-Encoding: 7bit From: Marshall Rose Subject: Re: [BEEPwg] Minimal presence of MIME headers in message payload Date: Wed, 31 May 2006 09:35:07 -0700 To: "Steven E. Harris" X-Mailer: Apple Mail (2.750) cc: beepwg@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9 > Per RFC 3080 Section 2.2, MIME headers may be used to describe message > payload content: > > ,---- > | A message is structured according to the rules of MIME. > Accordingly, > | each message may begin with "entity-headers" (c.f., MIME's Section 3 > | [1]). If none, or only some, of the "entity-headers" are present: > `---- > > In the case where /no/ headers are present, is there just a spare CRLF > pair at the beginning of the payload after the BEEP header? yes. > That is, > would the following message be valid? > > ,---- > | MSG 0 1 . 0 5 > | > | xxxEND > `---- yes. > Or could one send the same content without the spare CRLF pair? > > ,---- > | MSG 0 1 . 0 3 > | xxxEND > `---- no, for the reason you list. /mtr _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg From beepwg-bounces@dbc.mtview.ca.us Wed May 31 12:48:15 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlTrj-0005xy-SB for beep-archive@lists.ietf.org; Wed, 31 May 2006 12:48:15 -0400 Received: from drakken.dbc.mtview.ca.us ([168.143.123.173]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlTri-0007x2-Gk for beep-archive@lists.ietf.org; Wed, 31 May 2006 12:48:15 -0400 Received: from drakken.dbc.mtview.ca.us (localhost.localdomain [127.0.0.1]) by drakken.dbc.mtview.ca.us (8.12.11/8.12.8) with ESMTP id k4VGlCiY018710; Wed, 31 May 2006 09:47:13 -0700 Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) k4VGlASt018707 for ; Wed, 31 May 2006 09:47:11 -0700 Received: from list by ciao.gmane.org with local (Exim 4.43) id 1FlTqJ-0005b8-9x for beepwg@lists.beepcore.org; Wed, 31 May 2006 18:46:47 +0200 Received: from adsl-71-154-201-182.dsl.sndg02.sbcglobal.net ([71.154.201.182]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 May 2006 18:46:47 +0200 Received: from seh by adsl-71-154-201-182.dsl.sndg02.sbcglobal.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 31 May 2006 18:46:47 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: beepwg@lists.beepcore.org From: "Steven E. Harris" Date: Wed, 31 May 2006 09:46:24 -0700 Organization: SEH Labs Lines: 17 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: adsl-71-154-201-182.dsl.sndg02.sbcglobal.net User-Agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.13 (cygwin32) Cancel-Lock: sha1:y/zxyNQj/doW0mS2NGburTTftrU= Subject: [BEEPwg] Re: Minimal presence of MIME headers in message payload X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: beepwg-bounces@dbc.mtview.ca.us Errors-To: beepwg-bounces@dbc.mtview.ca.us X-Spam-Score: 0.0 (/) X-Scan-Signature: 798b2e660f1819ae38035ac1d8d5e3ab "Steven E. Harris" writes: > I have not yet found a follow-up message arguing against this > definition, but it apparently did not make it into RFC 3080. Here are a couple of more messages supporting the proposed interpretation: [BXXPwg] MIME header is gone Marshall T. Rose http://drakken.dbc.mtview.ca.us/pipermail/beepwg/2000-December/001032.html Wolfgang Hoschek http://drakken.dbc.mtview.ca.us/pipermail/beepwg/2000-December/001033.html -- Steven E. Harris _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://drakken.dbc.mtview.ca.us/mailman/listinfo/beepwg