IETF Logo Mail Archive

Re: [OAUTH-WG] Dynamic Client Registration Requirements

"Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com> Wed, 21 August 2013 16:28 UTC

Return-Path: <hannes.tschofenig@nsn.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7905F11E8255 for <oauth@ietfa.amsl.com>; Wed, 21 Aug 2013 09:28:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.465
X-Spam-Level:
X-Spam-Status: No, score=-106.465 tagged_above=-999 required=5 tests=[AWL=0.135, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0NnLBOzUx6ZY for <oauth@ietfa.amsl.com>; Wed, 21 Aug 2013 09:28:54 -0700 (PDT)
Received: from demumfd002.nsn-inter.net (demumfd002.nsn-inter.net [93.183.12.31]) by ietfa.amsl.com (Postfix) with ESMTP id 288BB11E8110 for <oauth@ietf.org>; Wed, 21 Aug 2013 09:28:53 -0700 (PDT)
Received: from demuprx016.emea.nsn-intra.net ([10.150.129.55]) by demumfd002.nsn-inter.net (8.12.11.20060308/8.12.11) with ESMTP id r7LGSqJD025293 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 21 Aug 2013 18:28:52 +0200
Received: from USCHHTC002.nsn-intra.net ([10.159.161.15]) by demuprx016.emea.nsn-intra.net (8.12.11.20060308/8.12.11) with ESMTP id r7LGSIRm026492 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 21 Aug 2013 18:28:51 +0200
Received: from USCHHTC003.nsn-intra.net (10.159.161.16) by USCHHTC002.nsn-intra.net (10.159.161.15) with Microsoft SMTP Server (TLS) id 14.3.123.3; Wed, 21 Aug 2013 11:28:10 -0500
Received: from USCHMBX001.nsn-intra.net ([169.254.1.221]) by USCHHTC003.nsn-intra.net ([10.159.161.16]) with mapi id 14.03.0123.003; Wed, 21 Aug 2013 11:28:10 -0500
From: "Tschofenig, Hannes (NSN - FI/Espoo)" <hannes.tschofenig@nsn.com>
To: ext Anthony Nadalin <tonynad@microsoft.com>, oauth mailing list <oauth@ietf.org>
Thread-Topic: Dynamic Client Registration Requirements
Thread-Index: Ac6dtsFpKFcW5YVXRR6Mixl/Rfo9ZQA1DsLg
Date: Wed, 21 Aug 2013 16:28:10 +0000
Message-ID: <1373E8CE237FCC43BCA36C6558612D2AA272D0@USCHMBX001.nsn-intra.net>
References: <e1eb7a02625c46faa473c0e835637fb1@BY2PR03MB189.namprd03.prod.outlook.com>
In-Reply-To: <e1eb7a02625c46faa473c0e835637fb1@BY2PR03MB189.namprd03.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.159.161.111]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-purgate-type: clean
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: clean
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate-size: 712
X-purgate-ID: 151667::1377102532-0000471E-CD31C93D/0-0/0-0
Subject: Re: [OAUTH-WG] Dynamic Client Registration Requirements
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: Wed, 21 Aug 2013 16:28:59 -0000

Hi Tony, 

Could you expand a little bit on those issues: 

> 4. Multi-tenant  support (single endpoint, multiple services)

What does multiple services mean here in the context of dynamic client registration? 

> 5. Internationalization

Where do you see internationalization play a role here? 

> 6. simple provisioning schema with schema extensibility

I guess all of the schemas we use are extensible. Is there something in particular you worry about? 

> 7. self-assertion

I guess this refers to the ability of the client to upload configuration that has not been verified by anyone, i.e., the client asserts this information by itself. Right? 

Ciao
Hannes

v2.23.0 | Report a Bug | By Email