Re: [OAUTH-WG] Principal -> Subject in Assertions spec?
"Richer, Justin P." <jricher@mitre.org> Wed, 16 January 2013 20:07 UTC
Return-Path: <jricher@mitre.org>
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 D256921F8B29 for <oauth@ietfa.amsl.com>; Wed, 16 Jan 2013 12:07:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.063
X-Spam-Level:
X-Spam-Status: No, score=-6.063 tagged_above=-999 required=5 tests=[AWL=0.535, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 9AGvzeNwMSsc for <oauth@ietfa.amsl.com>; Wed, 16 Jan 2013 12:07:20 -0800 (PST)
Received: from smtpksrv1.mitre.org (smtpksrv1.mitre.org [198.49.146.77]) by ietfa.amsl.com (Postfix) with ESMTP id A59FE21F8B19 for <oauth@ietf.org>; Wed, 16 Jan 2013 12:07:20 -0800 (PST)
Received: from smtpksrv1.mitre.org (localhost.localdomain [127.0.0.1]) by localhost (Postfix) with SMTP id AA1E443502B8; Wed, 16 Jan 2013 15:07:19 -0500 (EST)
Received: from IMCCAS03.MITRE.ORG (imccas03.mitre.org [129.83.29.80]) by smtpksrv1.mitre.org (Postfix) with ESMTP id 930D21F12F6; Wed, 16 Jan 2013 15:07:19 -0500 (EST)
Received: from IMCMBX01.MITRE.ORG ([169.254.1.25]) by IMCCAS03.MITRE.ORG ([129.83.29.80]) with mapi id 14.02.0318.004; Wed, 16 Jan 2013 15:07:19 -0500
From: "Richer, Justin P." <jricher@mitre.org>
To: Mike Jones <Michael.Jones@microsoft.com>, "oauth@ietf.org" <oauth@ietf.org>
Thread-Topic: Principal -> Subject in Assertions spec?
Thread-Index: Ac30IvFc/O0zg4CgRnm4qoarZkYplgAAhCXK
Date: Wed, 16 Jan 2013 20:07:18 +0000
Message-ID: <B33BFB58CCC8BE4998958016839DE27E0687A994@IMCMBX01.MITRE.ORG>
References: <4E1F6AAD24975D4BA5B168042967394366A4AFE4@TK5EX14MBXC284.redmond.corp.microsoft.com>
In-Reply-To: <4E1F6AAD24975D4BA5B168042967394366A4AFE4@TK5EX14MBXC284.redmond.corp.microsoft.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [129.83.31.51]
Content-Type: multipart/alternative; boundary="_000_B33BFB58CCC8BE4998958016839DE27E0687A994IMCMBX01MITREOR_"
MIME-Version: 1.0
Subject: Re: [OAUTH-WG] Principal -> Subject in Assertions spec?
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, 16 Jan 2013 20:07:22 -0000
+1, it's a non-normative terminology change that aligns it with related efforts. It should be a simple text replace operation. -- Justin ________________________________ From: oauth-bounces@ietf.org [oauth-bounces@ietf.org] on behalf of Mike Jones [Michael.Jones@microsoft.com] Sent: Wednesday, January 16, 2013 2:51 PM To: oauth@ietf.org Subject: [OAUTH-WG] Principal -> Subject in Assertions spec? In writing the proposed interoperability text for the Assertions specification, I noticed that the Assertions spec uses the term “Principal” to refer to the subject of the assertion, whereas both the SAML and JWT profiles use the term “Subject” for this same concept. I propose that at the same time we add the Interoperability statement, we also change the uses of the term “Principal” to “Subject” in the assertions spec so that it’s terminology usage is more consistent with the two profile specs using it. Thoughts? -- Mike
- [OAUTH-WG] Principal -> Subject in Assertions spe… Mike Jones
- Re: [OAUTH-WG] Principal -> Subject in Assertions… Richer, Justin P.
- Re: [OAUTH-WG] Principal -> Subject in Assertions… Torsten Lodderstedt