From: Luke Shepard <lshepard@facebook.com>
To: Dick Hardt <dick.hardt@gmail.com>
Date: Sat, 3 Jul 2010 11:28:18 -0700
Thread-Topic: [OAUTH-WG] Understanding the reasoning for Base64
Thread-Index: Acsa3X3bGj3Q7BjWR3G0imnvzYpqCg==
Message-ID: <20ACF96E-5753-4004-BE44-96BAD43FE7C9@facebook.com>
References: <AANLkTimMruKyblUWROkPMDapFKtTztOXqL64PpQxCmKO@mail.gmail.com>
 <2625894F-2979-40BD-81E1-05A6EB8723CD@facebook.com>
 <AANLkTinvLOV0f3I-aWpeAbfIpfGyxZSB2RHu52iw5mDC@mail.gmail.com>
 <AANLkTilWNneonIRX21U1RZcE80FuVSJWXU7CNm5pV275@mail.gmail.com>
 <AANLkTin-7PNLv-Hc229JJcOrIBh4fJqY5CMaLCMbmoIk@mail.gmail.com>
 <AANLkTikh_nQ8dXSp7QXJ79kCdbX1zeyPKAl_kgplb25x@mail.gmail.com>
 <3DC7AEF8-3283-4970-BB98-3D680A3E2429@gmail.com>
 <AANLkTimpvWCbCBEWdI1Id5Ig_xCUW2hvKDro5LyhufMV@mail.gmail.com>
 <FE47FED0-3850-4393-9C79-DE06F0F7B6CA@gmail.com>
 <BA564125-9FBB-4B1A-93AC-7DD1A754A5E1@facebook.com>
 <C66A9854-02EB-4CCE-8338-382AEEC7EA61@gmail.com>
 <AANLkTikiXVruhZSH3Q6rMhdZAHRBPkhE_JVhSNOhCXmN@mail.gmail.com>
 <6B008ED4-4536-4A95-89B6-917696E6AF79@gmail.com>
In-Reply-To: <6B008ED4-4536-4A95-89B6-917696E6AF79@gmail.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: multipart/alternative;
 boundary="_000_20ACF96E57534004BE4496BAD43FE7C9facebookcom_"
MIME-Version: 1.0
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Understanding the reasoning for Base64
Precedence: list

--_000_20ACF96E57534004BE4496BAD43FE7C9facebookcom_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable


>
> * We'd like the signature first (so you can left split instead of right s=
plit)

What are the advantages of left split vs right split?

Built in split function with a limit is more common, which makes the left s=
plit easier.

Size limit I am assuming? Since the size of the signature is known, this ma=
kes it safer to have it first? Makes sense to me.

Sounds like we agree on this point at least.

The main reason is that it's easier to restrict the delimiter from appearin=
g in the signature than in the payload. This way the delimiter (period) can=
 show up in the payload and a left split can still work.


--_000_20ACF96E57534004BE4496BAD43FE7C9facebookcom_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html><head></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode:=
 space; -webkit-line-break: after-white-space; "><div><blockquote type=3D"c=
ite"><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; -webkit=
-line-break: after-white-space; "><div><br></div><div><blockquote type=3D"c=
ite"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"=
margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex;=
 border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left=
-style: solid; padding-left: 1ex; position: static; z-index: auto; "><div c=
lass=3D"im">&gt;<br>
&gt; * We'd like the signature first (so you can left split instead of righ=
t split)<br>
<br>
</div>What are the advantages of left split vs right split?<br></blockquote=
><div><br></div><div>Built in split function with a limit is more common, w=
hich makes the left split easier.</div></div></blockquote><div><br></div><d=
iv>Size limit I am assuming? Since the size of the signature is known, this=
 makes it safer to have it first? Makes sense to me.</div></div></div></blo=
ckquote><br></div><div>Sounds like we agree on this point at least.</div><d=
iv><br></div><div><div>The main reason is that it's easier to restrict the =
delimiter from appearing in the signature than in the payload. This way the=
 delimiter (period) can show up in the payload and a left split can still w=
ork.</div><div><br></div></div></body></html>=

--_000_20ACF96E57534004BE4496BAD43FE7C9facebookcom_--