[OAUTH-WG] The best method to get generated bearer tokens encoded

Sergey Beryozkin <sberyozkin@gmail.com> Tue, 07 April 2015 10:58 UTC

Return-Path: <sberyozkin@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 07ABB1B341D for <oauth@ietfa.amsl.com>; Tue, 7 Apr 2015 03:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] autolearn=ham
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 KCrmnMA-AHG0 for <oauth@ietfa.amsl.com>; Tue, 7 Apr 2015 03:58:02 -0700 (PDT)
Received: from mail-wi0-x22a.google.com (mail-wi0-x22a.google.com [IPv6:2a00:1450:400c:c05::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97A731B3423 for <oauth@ietf.org>; Tue, 7 Apr 2015 03:58:02 -0700 (PDT)
Received: by wiax7 with SMTP id x7so7977639wia.0 for <oauth@ietf.org>; Tue, 07 Apr 2015 03:58:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=NPrcaLG7/ZGgQbrxQKOiKaAt6/6Sy57FQ8lFgKAlXys=; b=CcuQy8jyTe1lEwn73qZQqHKjXtesfWmdWYIZNkYFHpOiA0P3tEv0SypEuYQ3YlWFoD aG/eVtghp5ZrhlZ+5TGjmEicf9fr3KjO8qxozj7mu6Y4bBOFyVd2Q3HYAcP0VaTlAUZA 3bKNH2MH0WXhuFtwGpoK0wND31bmLJUvOyrYvFn2ZZgLxaqZ9fRLLYD0SX4jU5y2CL/j PDt8Gbv03AicbTfF/02veX3PqaPWjUBc9UeQyGgdR4CYGJGCdMiDE0K4jpjjdRHvM4CI fWvRJ30qQ4f9cNFXXM2YLogVlCTufl5wbWAyz0kMqEWpjLxrC359qBZIQNJwtUU9luFU oM2w==
X-Received: by 10.180.95.102 with SMTP id dj6mr3523563wib.45.1428404281430; Tue, 07 Apr 2015 03:58:01 -0700 (PDT)
Received: from [10.36.226.2] ([80.169.137.63]) by mx.google.com with ESMTPSA id z13sm10402301wjr.44.2015.04.07.03.58.00 for <oauth@ietf.org> (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 07 Apr 2015 03:58:00 -0700 (PDT)
Message-ID: <5523B838.80105@gmail.com>
Date: Tue, 07 Apr 2015 11:58:00 +0100
From: Sergey Beryozkin <sberyozkin@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: oauth@ietf.org
References: <D26B0844-431B-4A14-8B9F-BAF1A2D55444@mit.edu> <alpine.GSO.1.10.1504032112300.22210@multics.mit.edu> <5523B7BA.4@gmail.com>
In-Reply-To: <5523B7BA.4@gmail.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/ZcJSsJxSN5BtY2CQWwvbXaBAhII>
Subject: [OAUTH-WG] The best method to get generated bearer tokens encoded
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Apr 2015 10:58:13 -0000

Hi

Would it be correct to assume that the best method for encoding the 
auto-generated bearer tokens is Base64URL ? I've spotted recently some 
of our code uses the Hex encoding which I believe is inferior compared 
to Base64URL given that the latter has a richer set of characters.

Is it a correct assumption ?

Thanks, Sergey