[OAUTH-WG] . ?ric Vyncke's No Objection on      draft-ietf-oauth-resource-indicators-05:

nessandorae <nessandorae@gmail.com> Mon, 02 September 2019 20:21 UTC

Return-Path: <nessandorae@gmail.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 741BF120058 for <oauth@ietfa.amsl.com>; Mon, 2 Sep 2019 13:21:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.988
X-Spam-Level:
X-Spam-Status: No, score=-1.988 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_MIME_MALF=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 rwnHxxJgToPH for <oauth@ietfa.amsl.com>; Mon, 2 Sep 2019 13:20:58 -0700 (PDT)
Received: from mail-io1-xd2d.google.com (mail-io1-xd2d.google.com [IPv6:2607:f8b0:4864:20::d2d]) (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 BD8DC12004A for <oauth@ietf.org>; Mon, 2 Sep 2019 13:20:58 -0700 (PDT)
Received: by mail-io1-xd2d.google.com with SMTP id z3so31246386iog.0 for <oauth@ietf.org>; Mon, 02 Sep 2019 13:20:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:subject:importance:from:to:mime-version; bh=8qnZR49QfFeLsK7HKCH+2JlZ15mfT88UXBOxPlAGmek=; b=Y9JCLDSvwYRrg+hErg4el8wlu2VM6vY0woJjFfwYuLl5FVdRvqjCT71y4xcqvn9ede Mi54fyg3rQfD2bdBJ+IqCgKW7pUpjR50rE3vVdCH9HG4Z3s/q0jw5zvtOFeJ4WjAh+c4 NA7XhLp1MJWBHpG/tGtPPNeJFVTIfm5ZrTkLJzFuVy9SE23Fdg6adQbpsvwOvAaYYT5V BSWvZA+UgEINiQAroHeAxCmbfOEmh9g6O1A2OjUTaiRwJfrDR77ZjUs2AIJzvculAwrA HBcYiXOVaSfjOI7n4nu9hVBT8lJaqO4F/hL2cp3QsahlHFQ3WbyoM9iE5zUzIw6oGk9R WAxQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:subject:importance:from:to :mime-version; bh=8qnZR49QfFeLsK7HKCH+2JlZ15mfT88UXBOxPlAGmek=; b=q8vxUzmRZ7NMqWRnB4VA8jqhT6MalBRx5Pv0y2BYF67jA1rMl31B74rLnX2V67p9+E GxXNPrzBJ68lx2E8j2fJuWm58LWZOIFKkWiwIuVe/AkTRipS5OyAVl7EInw6xY93pXOe jIaxqAih1Eau7sW6pq8kda6BeESdJWiLxbpHrqDe4Bi+C/QC5+z+cYZpFXxkb3eRCWlX yGdZGETW6VPpdKzS7T82DQNOpLNJElBYBsG05Qg2HcN5l2ShWqqm7aMXri/gPevI8wfx rzPB8ZB4HTgRF/CsTYrkZuEOzV0C2TK3w4FXqZ9K6QtlIpraQAiHwJzhrBRSaPHdVgdf U43g==
X-Gm-Message-State: APjAAAXnA4C63WnjFtcyllVdiw1mkgiYfkjSolxYc/3ccXXQEGStgyeN xjXsrr6cAIXcj3OTIQxp3u4EnYBj4Ow=
X-Google-Smtp-Source: APXvYqwN29LmavBkqjzp5ulEFdJMltT/0/mhLX69uKyd1YsH/C3TJwY9k2sSfmDv015zC7981oQV7g==
X-Received: by 2002:a6b:f307:: with SMTP id m7mr7177782ioh.84.1567455657639; Mon, 02 Sep 2019 13:20:57 -0700 (PDT)
Received: from ?IPv6:2607:fb90:99bd:4a14:0:15:c60e:6e01? ([2607:fb90:99bd:4a14:0:15:c60e:6e01]) by smtp.gmail.com with ESMTPSA id q17sm2901920ioh.75.2019.09.02.13.20.56 for <oauth@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Sep 2019 13:20:57 -0700 (PDT)
Message-ID: <5d6d79a9.1c69fb81.d0309.d0cc@mx.google.com>
Date: Mon, 02 Sep 2019 15:20:54 -0500
Importance: normal
From: nessandorae <nessandorae@gmail.com>
To: oauth@ietf.org
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="--_com.samsung.android.email_94151092334180"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/B7rH5qDnqW-YqvMv_Qe20LL_Wh4>
Subject: [OAUTH-WG] =?iso-8859-1?q?=2E_=3Fric_Vyncke=27s_No_Objection_on?= =?iso-8859-1?q?=A0=A0=A0=A0=A0_draft-ietf-oauth-resource-indicators-05=3A?=
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 02 Sep 2019 20:21:02 -0000

google.comSent from my MetroPCS 4G LTE Android Device
-------- Original message --------From: oauth-request@ietf.org Date: 9/2/19  2:00 PM  (GMT-06:00) To: oauth@ietf.org Subject: OAuth Digest, Vol 131, Issue 2 Send OAuth mailing list submissions to	oauth@ietf.orgTo subscribe or unsubscribe via the World Wide Web, visit	https://www.ietf.org/mailman/listinfo/oauthor, via email, send a message with subject or body 'help' to	oauth-request@ietf.orgYou can reach the person managing the list at	oauth-owner@ietf.orgWhen replying, please edit your Subject line so it is more specificthan "Re: Contents of OAuth digest..."Today's Topics:   1. ?ric Vyncke's No Objection on      draft-ietf-oauth-resource-indicators-05: (with COMMENT)      (?ric Vyncke via Datatracker)   2. Re:  ?ric Vyncke's No Objection on      draft-ietf-oauth-resource-indicators-05: (with COMMENT) (ki de)   3. Fwd: New Version Notification for      draft-yusef-oauth-nested-jwt-02.txt (Rifaat Shekh-Yusef)----------------------------------------------------------------------Message: 1Date: Mon, 02 Sep 2019 02:40:31 -0700From: ?ric Vyncke via Datatracker <noreply@ietf.org>To: "The IESG" <iesg@ietf.org>Cc: draft-ietf-oauth-resource-indicators@ietf.org, Rifaat Shekh-Yusef	<rifaat.ietf@gmail.com>;, oauth-chairs@ietf.org, rifaat.ietf@gmail.com,	oauth@ietf.orgSubject: [OAUTH-WG] ?ric Vyncke's No Objection on	draft-ietf-oauth-resource-indicators-05: (with COMMENT)Message-ID:	<156741723195.13041.3519982606374763447.idtracker@ietfa.amsl.com>Content-Type: text/plain; charset="utf-8"?ric Vyncke has entered the following ballot position fordraft-ietf-oauth-resource-indicators-05: No ObjectionWhen responding, please keep the subject line intact and reply to allemail addresses included in the To and CC lines. (Feel free to cut thisintroductory paragraph, however.)Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.htmlfor more information about IESG DISCUSS and COMMENT positions.The document, along with other ballot positions, can be found here:https://datatracker.ietf.org/doc/draft-ietf-oauth-resource-indicators/----------------------------------------------------------------------COMMENT:----------------------------------------------------------------------Thank you for the hard work put into this easy to read document.Regards,-?ric== COMMENTS ==-- Section 1 --"has uncovered a need, in some circumstances" (and similar sentences in section1), it is rather vague for a standard track document... Please add some factsand data, this could be a companion document about requirements/use cases.-- Section 2 --It is rather a question of mine, why does the resource need to be a URI (whichusually bears some visible semantics) rather than an opaque string known onlyby the resource owner/server ? This is similar to Mirja's comment about privacy.------------------------------Message: 2Date: Mon, 2 Sep 2019 10:22:53 +0000From: ki de <kaycoins@outlook.com>To: ?ric Vyncke <evyncke@cisco.com>Cc: The IESG <iesg@ietf.org>;,	"draft-ietf-oauth-resource-indicators@ietf.org";	<draft-ietf-oauth-resource-indicators@ietf.org>;, "oauth@ietf.org";	<oauth@ietf.org>;, "oauth-chairs@ietf.org"; <oauth-chairs@ietf.org>Subject: Re: [OAUTH-WG]  ?ric Vyncke's No Objection on	draft-ietf-oauth-resource-indicators-05: (with COMMENT)Message-ID:	<CH2PR15MB3606603D750B0001DEDEAE16D7BE0@CH2PR15MB3606.namprd15.prod.outlook.com>;	Content-Type: text/plain; charset="utf-8"On Mon, Sep 2, 2019 at 5:40 AM ?ric Vyncke via Datatracker <noreply@ietf.org>; wrote:?ric Vyncke has entered the following ballot position fordraft-ietf-oauth-resource-indicators-05: No ObjectionWhen responding, please keep the subject line intact and reply to allemail addresses included in the To and CC lines. (Feel free to cut thisintroductory paragraph, however.)Please refer to https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fiesg%2Fstatement%2Fdiscuss-criteria.html&amp;data=02%7C01%7C%7Cda0508bc7b9a4598ae6f08d72f89a104%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637030140461915948&amp;sdata=sK56j9bwVyLlNupgEdxExdaBTTOLnI28%2FYSTJVgLpG4%3D&amp;reserved=0for more information about IESG DISCUSS and COMMENT positions.The document, along with other ballot positions, can be found here:https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatracker.ietf.org%2Fdoc%2Fdraft-ietf-oauth-resource-indicators%2F&amp;data=02%7C01%7C%7Cda0508bc7b9a4598ae6f08d72f89a104%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637030140461925959&amp;sdata=yGz0cyRb7FgYxHtHOMLTScZeIpTSQGb7pu6NOhQF2Ic%3D&amp;reserved=0----------------------------------------------------------------------COMMENT:----------------------------------------------------------------------Thank you for the hard work put into this easy to read document.Regards,-?ric== COMMENTS ==-- Section 1 --"has uncovered a need, in some circumstances" (and similar sentences in section1), it is rather vague for a standard track document... Please add some factsand data, this could be a companion document about requirements/use cases.-- Section 2 --It is rather a question of mine, why does the resource need to be a URI (whichusually bears some visible semantics) rather than an opaque string known onlyby the resource owner/server ? This is similar to Mirja's comment about privacy._______________________________________________OAuth mailing listOAuth@ietf.orghttps://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Foauth&amp;data=02%7C01%7C%7Cda0508bc7b9a4598ae6f08d72f89a104%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637030140461925959&amp;sdata=QfcbDqqJ9Z6g%2BLq8dNAAizQcLfpLxR543GBaqZwiAsw%3D&amp;reserved=0-------------- next part --------------An HTML attachment was scrubbed...URL: <https://mailarchive.ietf.org/arch/browse/oauth/attachments/20190902/3f1a298a/attachment.html>------------------------------Message: 3Date: Mon, 2 Sep 2019 11:03:20 -0400From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>To: oauth <oauth@ietf.org>Subject: [OAUTH-WG] Fwd: New Version Notification for	draft-yusef-oauth-nested-jwt-02.txtMessage-ID:	<CAGL6epLGY3dkDxg_x9m0OJC05Azu8ywS0frDahjssXSnAoOdQA@mail.gmail.com>Content-Type: text/plain; charset="utf-8"All,I have submitted a new version of the Nested JWT draft and added the STIRuse case.Please, take a look and let me know if you have any comments.Regards, Rifaat---------- Forwarded message ---------From: <internet-drafts@ietf.org>Date: Mon, Sep 2, 2019 at 10:59 AMSubject: New Version Notification for draft-yusef-oauth-nested-jwt-02.txtTo: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>A new version of I-D, draft-yusef-oauth-nested-jwt-02.txthas been successfully submitted by Rifaat Shekh-Yusef and posted to theIETF repository.Name:           draft-yusef-oauth-nested-jwtRevision:       02Title:          Nested JSON Web Token (JWT)Document date:  2019-09-02Group:          Individual SubmissionPages:          5URL:https://www.ietf.org/internet-drafts/draft-yusef-oauth-nested-jwt-02.txtStatus:https://datatracker.ietf.org/doc/draft-yusef-oauth-nested-jwt/Htmlized:       https://tools.ietf.org/html/draft-yusef-oauth-nested-jwt-02Htmlized:https://datatracker.ietf.org/doc/html/draft-yusef-oauth-nested-jwtDiff:https://www.ietf.org/rfcdiff?url2=draft-yusef-oauth-nested-jwt-02Abstract:   This specification extends the scope of the Nested JSON Web Token   (JWT) to allow the enclosing JWT to contain its own Claims Set in   addition to the enclosed JWT.Please note that it may take a couple of minutes from the time of submissionuntil the htmlized version and diff are available at tools.ietf.org.The IETF Secretariat-------------- next part --------------An HTML attachment was scrubbed...URL: <https://mailarchive.ietf.org/arch/browse/oauth/attachments/20190902/1c70a6df/attachment.html>------------------------------Subject: Digest Footer_______________________________________________OAuth mailing listOAuth@ietf.orghttps://www.ietf.org/mailman/listinfo/oauth------------------------------End of OAuth Digest, Vol 131, Issue 2*************************************