IETF Logo Mail Archive

Re: [OAUTH-WG] Proposal for text for section 2

"Manger, James H" <James.H.Manger@team.telstra.com> Wed, 30 June 2010 00:07 UTC

Return-Path: <James.H.Manger@team.telstra.com>
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 DE8E53A6A51 for <oauth@core3.amsl.com>; Tue, 29 Jun 2010 17:07:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.09
X-Spam-Level:
X-Spam-Status: No, score=0.09 tagged_above=-999 required=5 tests=[AWL=0.991, BAYES_00=-2.599, HELO_EQ_AU=0.377, HOST_EQ_AU=0.327, RELAY_IS_203=0.994]
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 lB6yZPJNdTSI for <oauth@core3.amsl.com>; Tue, 29 Jun 2010 17:07:30 -0700 (PDT)
Received: from ipxbvo.tcif.telstra.com.au (ipxbvo.tcif.telstra.com.au [203.35.135.204]) by core3.amsl.com (Postfix) with ESMTP id D5DFB3A68A7 for <oauth@ietf.org>; Tue, 29 Jun 2010 17:07:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="4.53,508,1272808800"; d="scan'208";a="5115681"
Received: from unknown (HELO ipccvi.tcif.telstra.com.au) ([10.97.217.208]) by ipobvi.tcif.telstra.com.au with ESMTP; 30 Jun 2010 10:07:35 +1000
X-IronPort-AV: E=McAfee;i="5400,1158,6028"; a="3799139"
Received: from wsmsg3755.srv.dir.telstra.com ([172.49.40.196]) by ipccvi.tcif.telstra.com.au with ESMTP; 30 Jun 2010 10:07:36 +1000
Received: from WSMSG3153V.srv.dir.telstra.com ([172.49.40.159]) by WSMSG3755.srv.dir.telstra.com ([172.49.40.196]) with mapi; Wed, 30 Jun 2010 10:07:36 +1000
From: "Manger, James H" <James.H.Manger@team.telstra.com>
To: Marius Scurtescu <mscurtescu@google.com>
Date: Wed, 30 Jun 2010 10:07:34 +1000
Thread-Topic: [OAUTH-WG] Proposal for text for section 2
Thread-Index: AcsXrGDU+cOkXD6yQpS4lCbUJEfEswANljAA
Message-ID: <255B9BB34FB7D647A506DC292726F6E11265B7E474@WSMSG3153V.srv.dir.telstra.com>
References: <7C01E631FF4B654FA1E783F1C0265F8C579CC0C3@TK5EX14MBXC117.redmond.corp.microsoft.com> <7C01E631FF4B654FA1E783F1C0265F8C579D0F31@TK5EX14MBXC117.redmond.corp.microsoft.com> <255B9BB34FB7D647A506DC292726F6E11265A5FC9D@WSMSG3153V.srv.dir.telstra.com> <AANLkTilrSUMEjsF-3RHuit6aoAPRe0DAqR6Uz2ldrd_l@mail.gmail.com>
In-Reply-To: <AANLkTilrSUMEjsF-3RHuit6aoAPRe0DAqR6Uz2ldrd_l@mail.gmail.com>
Accept-Language: en-US, en-AU
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, en-AU
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "oauth@ietf.org" <oauth@ietf.org>
Subject: Re: [OAUTH-WG] Proposal for text for section 2
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, 30 Jun 2010 00:07:31 -0000

Marius,

>> For instance, why not define a SAML HTTP authentication mechanism:
>>
>>    Authorization: SAML a=<base64url-encoded SAML assertion>

> This came up in another thread, but SAML assertions could be too large
> to be passed through an HTTP header. Other than that, your suggestion
> really simplifies things.

What are the limits on HTTP headers?
I don't think there are any in the HTTP spec.
<http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-09#section-3.2>
A comment in the other thread said SPNEGO headers can be up to 12392 bytes and do not seem to be a problem.
<http://www.ietf.org/mail-archive/web/oauth/current/msg03359.html>

I is hard to support a POST-and-form-only method when there is an alternative that "really simplifies things" without more concrete information on what the actual HTTP limits are (& how hard it is to increase them), and what practical assertion sizes are.

--
James Manger

v2.46.0 | Report a Bug | By Email | System Status