IETF Logo Mail Archive

Re: [OAUTH-WG] Defining a maximum token length?

Moritz Maisel <maisel@sipgate.de> Wed, 10 March 2010 16:17 UTC

Return-Path: <maisel@sipgate.de>
X-Original-To: oauth@core3.amsl.com
Delivered-To: oauth@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id F1C9D3A6A2F for <oauth@core3.amsl.com>; Wed, 10 Mar 2010 08:17:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bkftQWacJvYF for <oauth@core3.amsl.com>; Wed, 10 Mar 2010 08:16:58 -0800 (PST)
Received: from mail-fx0-f213.google.com (mail-fx0-f213.google.com [209.85.220.213]) by core3.amsl.com (Postfix) with ESMTP id D63A43A6920 for <oauth@ietf.org>; Wed, 10 Mar 2010 08:16:57 -0800 (PST)
Received: by fxm5 with SMTP id 5so2782512fxm.29 for <oauth@ietf.org>; Wed, 10 Mar 2010 08:16:59 -0800 (PST)
Received: by 10.223.77.85 with SMTP id f21mr1850727fak.40.1268237818995; Wed, 10 Mar 2010 08:16:58 -0800 (PST)
Received: from halvar.netzquadrat.de (halvar.netzquadrat.de [217.10.64.190]) by mx.google.com with ESMTPS id 13sm14146807fks.30.2010.03.10.08.16.57 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 10 Mar 2010 08:16:57 -0800 (PST)
Message-ID: <4B97C5F9.1020005@sipgate.de>
Date: Wed, 10 Mar 2010 17:16:57 +0100
From: Moritz Maisel <maisel@sipgate.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.9.1.8) Gecko/20100227 Lightning/1.0b1 Thunderbird/3.0.3
MIME-Version: 1.0
To: oauth@ietf.org
References: <fd6741651003091550t5a464496r57aae9a60c516599@mail.gmail.com> <0EC5832F-DE91-437F-96FE-87638A2BCF16@jkemp.net>
In-Reply-To: <0EC5832F-DE91-437F-96FE-87638A2BCF16@jkemp.net>
X-Enigmail-Version: 1.0.1
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 8bit
Subject: Re: [OAUTH-WG] Defining a maximum token length?
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Wed, 10 Mar 2010 16:17:02 -0000

On 03/10/2010 04:42 PM, John Kemp wrote:
> One reason I can imagine is to make it possible to encode information into the token itself so that the token can be "self-contained" (mentioned also by others on this list). 
>   

Though thats an interesting option, compatibility of implementations
might be easier to achieve by strict specifications like "maximum of 256
characters".

Just to get an idea about the situation: Is the mentioned
"self-contained token" a common scenario / popular demand that needs to
be covered?

Regards,
Moritz

-- 
sipgate GmbH - Gladbacher Str. 74 - 40219 Düsseldorf
HRB Düsseldorf 39841 - Geschäftsführer: Thilo Salmon, Tim Mois
Steuernummer: 106/5724/7147, Umsatzsteuer-ID: DE219349391

www.sipgate.de - www.sipgate.at - www.sipgate.co.uk

v2.23.0 | Report a Bug | By Email