From beepwg-admin@lists.beepcore.org Mon May 19 15:33:51 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA03162 for ; Mon, 19 May 2003 15:33:35 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4JJYDc07000; Mon, 19 May 2003 12:34:23 -0700 (PDT) Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4JJXIc06977 for ; Mon, 19 May 2003 12:33:18 -0700 (PDT) Received: from spamsicle.cisco.com (IDENT:mirapoint@spamsicle.cisco.com [161.44.172.225]) by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h4JJX6Jh006023 for ; Mon, 19 May 2003 15:33:07 -0400 (EDT) Received: from PAANDREWW2K3 (dhcp-161-44-180-172.cisco.com [161.44.180.172]) by spamsicle.cisco.com (Mirapoint) with ESMTP id AAS54363; Mon, 19 May 2003 15:33:06 -0400 (EDT) From: "Paul Andrews" To: "Beepwg" Message-ID: <007e01c31e3d$902c8160$acb42ca1@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Subject: [BEEPwg] Base64 and line breaks Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Mon, 19 May 2003 15:33:45 -0400 Content-Transfer-Encoding: 7bit Hi, I'm running into an interoperability problem regarding the base64 encoding of blob data during a SASL profile exchange. One side (the Java side) is using the mime encoding rules and inserting a line break after every 76 characters of base64 encoded data. The other side (the C side) is expecting a continuous stream of base64 data with no line breaks. Which side is right (the BEEP RFC simply states that blob data must be base64 encoded for SASL exchanges, it doesn't say whether the blob should follow mime rules for that data or not)? Thanks - Paul. _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Mon May 19 15:57:23 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA04393 for ; Mon, 19 May 2003 15:57:22 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4JK0Ac07293; Mon, 19 May 2003 13:00:10 -0700 (PDT) Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4JJx2c07257 for ; Mon, 19 May 2003 12:59:02 -0700 (PDT) Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-4.0) with ESMTP id h4JJwexn010463 for ; Mon, 19 May 2003 14:58:50 -0500 (CDT) Received: from att.com (unknown[135.210.84.40](misconfigured sender)) by maillennium.att.com (mailgw1) with SMTP id <20030519195720gw100niusre> (Authid: tony); Mon, 19 May 2003 19:57:20 +0000 Message-ID: <3EC936CE.3070300@att.com> From: Tony Hansen User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3) Gecko/20030308 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Paul Andrews CC: Beepwg Subject: Re: [BEEPwg] Base64 and line breaks References: <007e01c31e3d$902c8160$acb42ca1@cisco.com> In-Reply-To: <007e01c31e3d$902c8160$acb42ca1@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Mon, 19 May 2003 15:55:58 -0400 Content-Transfer-Encoding: 7bit The base64 spec requires that any characters that are not in the base64 alphabet are to be ignored and allows such characters to be inserted anywhere in the stream. That includes line breaks. (Your C side is wrong.) Tony Hansen tony@att.com Paul Andrews wrote: > Hi, > > I'm running into an interoperability problem regarding the base64 > encoding of blob data during a SASL profile exchange. One side (the Java > side) is using the mime encoding rules and inserting a line break after > every 76 characters of base64 encoded data. The other side (the C side) > is expecting a continuous stream of base64 data with no line breaks. > > Which side is right (the BEEP RFC simply states that blob data must be > base64 encoded for SASL exchanges, it doesn't say whether the blob > should follow mime rules for that data or not)? _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Mon May 19 21:45:11 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA12631 for ; Mon, 19 May 2003 21:45:10 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4K1m4c10072; Mon, 19 May 2003 18:48:04 -0700 (PDT) Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4K103c09746 for ; Mon, 19 May 2003 18:00:03 -0700 (PDT) Received: from esunmail ([129.147.58.120]) by brmea-mail-4.sun.com (8.12.9/8.12.9) with ESMTP id h4K0xnpd002242 for ; Mon, 19 May 2003 18:59:53 -0600 (MDT) Received: from xpa-fe1 (esunmail [129.147.58.120]) by edgemail1.Central.Sun.COM (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTP id <0HF500JFXURO2H@edgemail1.Central.Sun.COM> for beepwg@lists.beepcore.org; Mon, 19 May 2003 18:59:49 -0600 (MDT) Received: from nifty-jr.west.sun.com ([129.153.12.95]) by mail.sun.net (iPlanet Messaging Server 5.2 HotFix 1.12 (built Feb 13 2003)) with ESMTPSA id <0HF5001RVURMKI@mail.sun.net> for beepwg@lists.beepcore.org; Mon, 19 May 2003 18:59:48 -0600 (MDT) From: Chris Newman Subject: Re: [BEEPwg] Base64 and line breaks In-reply-to: <3EC936CE.3070300@att.com> To: Tony Hansen , Paul Andrews Cc: Beepwg Message-id: <2147483647.1053367029@nifty-jr.west.sun.com> MIME-version: 1.0 X-Mailer: Mulberry/3.0.3 (Mac OS X) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Content-disposition: inline X-message-flag: Outlook: the best virus distribution system around References: <007e01c31e3d$902c8160$acb42ca1@cisco.com> <3EC936CE.3070300@att.com> Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Mon, 19 May 2003 17:57:09 -0700 Content-Transfer-Encoding: 7BIT Actually most of the SASL profiles which use base64 encoding do not permit line breaks in the format. This includes RFC 3501, 1734, 2554, etc. For example, RFC 3501 has this ABNF: ----- authenticate = "AUTHENTICATE" SP auth-type *(CRLF base64) auth-type = atom ; Defined by [SASL] base64 = *(4base64-char) [base64-terminal] base64-char = ALPHA / DIGIT / "+" / "/" ; Case-sensitive base64-terminal = (2base64-char "==") / (3base64-char "=") ----- So I could argue that the failure to explicitly include the ABNF for the base64 left the specification ambiguous and it should be clarified to be consistent with other protocols that base64 encode the SASL exchange. But if there's deployed Java code which generates unnecessary characters in the base64 stream, perhaps it's too late to make it consistent with other protocols and we just need to document the more permissive syntax for BEEP... - Chris begin quotation by Tony Hansen on 2003/5/19 15:55 -0400: > The base64 spec requires that any characters that are not in the base64 > alphabet are to be ignored and allows such characters to be inserted anywhere > in the stream. That includes line breaks. (Your C side is wrong.) > > Tony Hansen > tony@att.com > > Paul Andrews wrote: >> Hi, >> >> I'm running into an interoperability problem regarding the base64 >> encoding of blob data during a SASL profile exchange. One side (the Java >> side) is using the mime encoding rules and inserting a line break after >> every 76 characters of base64 encoded data. The other side (the C side) >> is expecting a continuous stream of base64 data with no line breaks. >> >> Which side is right (the BEEP RFC simply states that blob data must be >> base64 encoded for SASL exchanges, it doesn't say whether the blob >> should follow mime rules for that data or not)? > > _______________________________________________ > BEEPwg mailing list > BEEPwg@lists.beepcore.org > http://lists.beepcore.org/mailman/listinfo/beepwg _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Tue May 20 08:52:13 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA11081 for ; Tue, 20 May 2003 08:52:13 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4KCt5c15661; Tue, 20 May 2003 05:55:06 -0700 (PDT) Received: from rtp-core-2.cisco.com (rtp-core-2.cisco.com [64.102.124.13]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4KCsYc15640 for ; Tue, 20 May 2003 05:54:34 -0700 (PDT) Received: from spamsicle.cisco.com (IDENT:mirapoint@spamsicle.cisco.com [161.44.172.225]) by rtp-core-2.cisco.com (8.12.9/8.12.6) with ESMTP id h4KCsMJh012627; Tue, 20 May 2003 08:54:22 -0400 (EDT) Received: from PAANDREWW2K3 (che-vpn-cluster-2-8.cisco.com [10.86.242.8]) by spamsicle.cisco.com (Mirapoint) with ESMTP id AAS57282; Tue, 20 May 2003 08:54:21 -0400 (EDT) From: "Paul Andrews" To: "'Chris Newman'" , "'Tony Hansen'" Cc: "'Beepwg'" Subject: RE: [BEEPwg] Base64 and line breaks Message-ID: <00d301c31ecf$071b2970$acb42ca1@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 In-Reply-To: <2147483647.1053367029@nifty-jr.west.sun.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Tue, 20 May 2003 08:55:01 -0400 Content-Transfer-Encoding: 7bit Well, this leaves an interop issue between beepcore-c+cyrus and beepcore-java. The cyrus libraries do not accept extraneous characters, whilst the java libraries insert line-breaks every 76 characters. I agree, though, that the RFC needs to be clarified. > -----Original Message----- > From: Chris Newman [mailto:Chris.Newman@Sun.COM] > Sent: Monday, May 19, 2003 8:57 PM > To: Tony Hansen; Paul Andrews > Cc: Beepwg > Subject: Re: [BEEPwg] Base64 and line breaks > > > Actually most of the SASL profiles which use base64 encoding > do not permit line > breaks in the format. > > This includes RFC 3501, 1734, 2554, etc. > > For example, RFC 3501 has this ABNF: > > ----- > authenticate = "AUTHENTICATE" SP auth-type *(CRLF base64) > > auth-type = atom > ; Defined by [SASL] > > base64 = *(4base64-char) [base64-terminal] > > base64-char = ALPHA / DIGIT / "+" / "/" > ; Case-sensitive > > base64-terminal = (2base64-char "==") / (3base64-char "=") > ----- > > So I could argue that the failure to explicitly include the > ABNF for the base64 > left the specification ambiguous and it should be clarified > to be consistent > with other protocols that base64 encode the SASL exchange. > > But if there's deployed Java code which generates unnecessary > characters in the > base64 stream, perhaps it's too late to make it consistent > with other protocols > and we just need to document the more permissive syntax for BEEP... > > - Chris > > _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg From beepwg-admin@lists.beepcore.org Tue May 20 11:12:36 2003 Received: from qawoor.dbc.mtview.ca.us (adsl-64-168-10-251.dsl.scrm01.pacbell.net [64.168.10.251]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA17212 for ; Tue, 20 May 2003 11:12:34 -0400 (EDT) Received: from qawoor.dbc.mtview.ca.us (localhost [127.0.0.1]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4KFFBc16774; Tue, 20 May 2003 08:15:11 -0700 (PDT) Received: from shego.dbc.mtview.ca.us (dhcpd254.dbc.mtview.ca.us [64.168.10.254]) by qawoor.dbc.mtview.ca.us (8.11.5/8.11.5) with ESMTP id h4KFE9c16750 for ; Tue, 20 May 2003 08:14:09 -0700 (PDT) Received: from shego.dbc.mtview.ca.us (localhost [127.0.0.1]) by shego.dbc.mtview.ca.us (8.12.6/8.12.6) with SMTP id h4KFDvH4004829; Tue, 20 May 2003 08:13:57 -0700 (PDT) From: Marshall Rose To: "Paul Andrews" Cc: Chris.Newman@Sun.COM, tony@att.com, beepwg@lists.beepcore.org Subject: Re: [BEEPwg] Base64 and line breaks Message-Id: <20030520081357.1aa3eed8.mrose+mtr.netnews@dbc.mtview.ca.us> In-Reply-To: <00d301c31ecf$071b2970$acb42ca1@cisco.com> References: <2147483647.1053367029@nifty-jr.west.sun.com> <00d301c31ecf$071b2970$acb42ca1@cisco.com> Organization: Dover Beach Consulting, Inc. X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: beepwg-admin@lists.beepcore.org Errors-To: beepwg-admin@lists.beepcore.org X-BeenThere: beepwg@lists.beepcore.org X-Mailman-Version: 2.0.6 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Mailing list for the IETF's BEEP working group List-Unsubscribe: , List-Archive: Date: Tue, 20 May 2003 08:13:57 -0700 Content-Transfer-Encoding: 7bit > Well, this leaves an interop issue between beepcore-c+cyrus and > beepcore-java. The cyrus libraries do not accept extraneous characters, > whilst the java libraries insert line-breaks every 76 characters. this probably falls under the "be liberal in what you accept, conservative in what you generate" rubic. > I agree, though, that the RFC needs to be clarified. agreed. /mtr _______________________________________________ BEEPwg mailing list BEEPwg@lists.beepcore.org http://lists.beepcore.org/mailman/listinfo/beepwg