Re: [OAUTH-WG] Fwd: New Version Notification for draft-sakimura-oauth-meta-07.txt

Anthony Nadalin <tonynad@microsoft.com> Tue, 16 February 2016 23:50 UTC

Return-Path: <tonynad@microsoft.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 137991AD0AB for <oauth@ietfa.amsl.com>; Tue, 16 Feb 2016 15:50:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.11
X-Spam-Level: *
X-Spam-Status: No, score=1.11 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URI_HEX=1.122] autolearn=no
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 kpwITCTXBNeg for <oauth@ietfa.amsl.com>; Tue, 16 Feb 2016 15:50:13 -0800 (PST)
Received: from na01-by2-obe.outbound.protection.outlook.com (mail-by2on0118.outbound.protection.outlook.com [207.46.100.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CC9B31AD068 for <oauth@ietf.org>; Tue, 16 Feb 2016 15:50:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:To:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=XgOJ6YFpQ1Zlf2Yx+nhOc32hBFItSlYkB18OJTos78E=; b=VbWvncOIICjsil71mAmQ5PuhjOQB5/HWWNXxzBsE9bjeLxf+l7hl/UBqn3sL2Yv7WM7zBBFqhgaqnRRuFQJynQsEz4tpYqPGHhsXpgf4k57J0pTToSCqAHjgmSHBLj0FTsdXZH6m/wjMPv8gkyUwBjYbOqyPBr6ocgZaG15jfJg=
Received: from BN3PR0301MB1234.namprd03.prod.outlook.com (10.161.207.22) by BN3PR0301MB1235.namprd03.prod.outlook.com (10.161.207.23) with Microsoft SMTP Server (TLS) id 15.1.403.16; Tue, 16 Feb 2016 23:50:08 +0000
Received: from BN3PR0301MB1234.namprd03.prod.outlook.com ([10.161.207.22]) by BN3PR0301MB1234.namprd03.prod.outlook.com ([10.161.207.22]) with mapi id 15.01.0409.017; Tue, 16 Feb 2016 23:50:08 +0000
From: Anthony Nadalin <tonynad@microsoft.com>
To: Nat Sakimura <sakimura@gmail.com>, oauth <oauth@ietf.org>
Thread-Topic: [OAUTH-WG] Fwd: New Version Notification for draft-sakimura-oauth-meta-07.txt
Thread-Index: AQHRaEzy+Urv/eFEWE6v0zAOaJ7fPp8vV24Q
Date: Tue, 16 Feb 2016 23:50:08 +0000
Message-ID: <BN3PR0301MB123433D1ED9BF9B1118BC751A6AD0@BN3PR0301MB1234.namprd03.prod.outlook.com>
References: <20160212094043.13011.44662.idtracker@ietfa.amsl.com> <CABzCy2CP0LZGePZedXYfWfsKOauCnnZeGiConUiEG2GmEP+vdg@mail.gmail.com>
In-Reply-To: <CABzCy2CP0LZGePZedXYfWfsKOauCnnZeGiConUiEG2GmEP+vdg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:3::64b]
x-ms-office365-filtering-correlation-id: 611bdcf9-25db-4d14-44ea-08d3372be6d1
x-microsoft-exchange-diagnostics: 1; BN3PR0301MB1235; 5:bothdwLhi0KEdCgwI0Owbxsm0AEV6D2dZnCN+4GCKrbiGyt9BN/LWDYQSnosQ/OgLpo7NsWmyBrpcrxaZTSpIx3KMx0ScqeB4+eoG5XhfDCpMw76IzWLxaVhJgbfth2N02I8gYaT9VPbbticPEBbrg==; 24:EIvBBu1a1G8QH8Bki4t+7t+c/Qqv9uxqw2wTvRgyE7F9fT2n+Y2cHDQkOb8Z/yMtqqME0zwGwim5WBEYtcl6ia6S5BPMkagIM76rzr8N8cs=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BN3PR0301MB1235;
x-microsoft-antispam-prvs: <BN3PR0301MB123575061E27BAF444885C58A6AD0@BN3PR0301MB1235.namprd03.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(61425038)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(61426038)(61427038); SRVR:BN3PR0301MB1235; BCL:0; PCL:0; RULEID:; SRVR:BN3PR0301MB1235;
x-forefront-prvs: 0854128AF0
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(2473001)(22974007)(377454003)(377424004)(5002640100001)(92566002)(15975445007)(77096005)(5005710100001)(2950100001)(2900100001)(10400500002)(189998001)(5003600100002)(1220700001)(2906002)(1096002)(5001770100001)(10710500007)(2420400007)(7110500001)(107886002)(586003)(790700001)(5001960100002)(102836003)(6116002)(19300405004)(15650500001)(50986999)(19580395003)(19625215002)(106116001)(76576001)(5004730100002)(14971765001)(33656002)(19617315012)(19609705001)(74316001)(10090500001)(86362001)(10290500002)(230783001)(76176999)(54356999)(11100500001)(87936001)(19580405001)(99286002)(86612001)(40100003)(16236675004)(122556002)(5008740100001)(3826002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BN3PR0301MB1235; H:BN3PR0301MB1234.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BN3PR0301MB123433D1ED9BF9B1118BC751A6AD0BN3PR0301MB1234_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Feb 2016 23:50:08.2311 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN3PR0301MB1235
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/z0L1l-ciuLfEheCXqODMSHVd9po>
Subject: Re: [OAUTH-WG] Fwd: New Version Notification for draft-sakimura-oauth-meta-07.txt
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: <https://mailarchive.ietf.org/arch/browse/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, 16 Feb 2016 23:50:18 -0000

I really think that this is a step backwards relative to technology and what the developers would accept. The Link Relations takes us back to the XML days, I thought we have all moved on from that and at least trying to move Oauth to JSON. I think if this were adopted we might be splitting the developers into folks that are already going down the current JSON path with Oauth and those that want to go back to XML.

This just seems a very odd draft to adopt this technology.

From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Nat Sakimura
Sent: Monday, February 15, 2016 3:59 PM
To: oauth <oauth@ietf.org>
Subject: [OAUTH-WG] Fwd: New Version Notification for draft-sakimura-oauth-meta-07.txt

It now shows how to return multiple endpoints in web linking.
Also, added Resource Endpoint response header.

Best,

nat

---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: 2016年2月12日(金) 18:40
Subject: New Version Notification for draft-sakimura-oauth-meta-07.txt
To: Nov Matake <nov@matake.jp<mailto:nov@matake.jp>>, Nat Sakimura <sakimura@gmail.com<mailto:sakimura@gmail.com>>, Sascha Preibisch <Sascha.Preibisch@gmail.com<mailto:Sascha.Preibisch@gmail.com>>, Sascha Preibisch <sascha.preibisch@gmail.com<mailto:sascha.preibisch@gmail.com>>



A new version of I-D, draft-sakimura-oauth-meta-07.txt
has been successfully submitted by Nat Sakimura and posted to the
IETF repository.

Name:           draft-sakimura-oauth-meta
Revision:       07
Title:          OAuth Response Metadata
Document date:  2016-02-12
Group:          Individual Submission
Pages:          10
URL:            https://www.ietf.org/internet-drafts/draft-sakimura-oauth-meta-07.txt<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.ietf.org%2finternet-drafts%2fdraft-sakimura-oauth-meta-07.txt&data=01%7c01%7ctonynad%40microsoft.com%7c3a992d5ff4a2428804f208d336641292%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=6M10Q9X4cq%2b%2fRroR%2fHYQ9IN3P1HO06JnbuzY6P3oWtc%3d>
Status:         https://datatracker.ietf.org/doc/draft-sakimura-oauth-meta/<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fdatatracker.ietf.org%2fdoc%2fdraft-sakimura-oauth-meta%2f&data=01%7c01%7ctonynad%40microsoft.com%7c3a992d5ff4a2428804f208d336641292%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=7twEM0FztSaswtFiYslvJuadTyWbWRSDWQ6uT%2bevKwM%3d>
Htmlized:       https://tools.ietf.org/html/draft-sakimura-oauth-meta-07<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2ftools.ietf.org%2fhtml%2fdraft-sakimura-oauth-meta-07&data=01%7c01%7ctonynad%40microsoft.com%7c3a992d5ff4a2428804f208d336641292%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=kh2nH4IyNm3OAA5nkrSFzZN16Xic%2b2EDUOfr%2fG6CjVY%3d>
Diff:           https://www.ietf.org/rfcdiff?url2=draft-sakimura-oauth-meta-07<https://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fwww.ietf.org%2frfcdiff%3furl2%3ddraft-sakimura-oauth-meta-07&data=01%7c01%7ctonynad%40microsoft.com%7c3a992d5ff4a2428804f208d336641292%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=ICtk5U1e6kBPFI8ov0n06TAcqDX3HurgFTydXKD73Yo%3d>

Abstract:
   This specification defines an extensible metadata that may be
   inserted into the OAuth 2.0 responses to assist the clients to
   process those responses.  It is expressed either as a link header, or
   query parameters.  It will allow the client to learn where the
   members in the response could be used, what is the characteristics of
   the payload is, how it should be processed, and so on.  Since they
   are just additional response header/query parameters, any client that
   does not understand this extension should not break and work normally
   while supporting clients can utilize the metadata to take the
   advantage of the extension.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org<https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2ftools.ietf.org&data=01%7c01%7ctonynad%40microsoft.com%7c3a992d5ff4a2428804f208d336641292%7c72f988bf86f141af91ab2d7cd011db47%7c1&sdata=aijC6rAn01n04mDyB5lpV7tQitxIyf0drdheleR955A%3d>leR955A%3d>.

The IETF Secretariat