IETF Logo Mail Archive

Re: [OAUTH-WG] Updating "Identity Chaining across Trust Domains" draft name

Brian Campbell <bcampbell@pingidentity.com> Tue, 20 February 2024 20:30 UTC

Return-Path: <bcampbell@pingidentity.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 47BAFC180B7A for <oauth@ietfa.amsl.com>; Tue, 20 Feb 2024 12:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=pingidentity.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2r_1R4CB5Zrz for <oauth@ietfa.amsl.com>; Tue, 20 Feb 2024 12:30:34 -0800 (PST)
Received: from mail-il1-x12a.google.com (mail-il1-x12a.google.com [IPv6:2607:f8b0:4864:20::12a]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B2B72C14F5F8 for <oauth@ietf.org>; Tue, 20 Feb 2024 12:30:34 -0800 (PST)
Received: by mail-il1-x12a.google.com with SMTP id e9e14a558f8ab-36519980c04so7844405ab.3 for <oauth@ietf.org>; Tue, 20 Feb 2024 12:30:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=google; t=1708461033; x=1709065833; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=npYoWJbSL5DzElwhwVorwlFoD5bXBrRbefDJ4He2QUw=; b=GgBdbom/YiOSB6YIx/30vYH6tlPr1WQOma/wNaBPuu+z84CPqnNirvqSGtpPpZiLk0 1TYqCS8SQokAS0VXCWv/dVb/X7z49Kr5kt5e4S9XG4Y4uZLB1vTQV4PRSRpOPITFBbYY Nbqc5q3QkrGlt5LXyLBqQda8Bwnbpl6mujrLfKRocL6hApJAmtFJS5I8TkYX9dZHjnkK l8bWx+GcCHD8aeYwh05+R3NeKaDvjRIf/o56KtxEKn7LOaJ0ChHpjnhOsLyCJSdGAJWa K6AW2F3CZTzcLVyTcAJct6SE6EEZ4XLlHWB7rrYNw3MgyMQna11bJMUCSf1lXyK+9Zd4 QGiQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1708461033; x=1709065833; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=npYoWJbSL5DzElwhwVorwlFoD5bXBrRbefDJ4He2QUw=; b=c8PZevIYcSlvcUATLed9ZEqCf1Wh05OY0c8UTYsTAVv45gb9hCN8Vjm65oHr8hflVq R15YsGvSHCrUL2F4tqRUOUsbRGeNqSnF4X3emFyr9gtLMs/8H4eM4GCW8j+IYg3KxzqD caBUc8uM6k1nz6xb0xhH5ECo9AbmWUEgTO7rBb/uUX6iqHoZRS/3OGT9oDGqUKE+z+kt iW+Qcj0PzUGo+6u7FzLqBXYI2JyNo7L48nipyqQroq/JvuxbIZQcx2xlQnRrcj6mUBlp c3neLiUy86qXBIa35vyrNigZeinl5t9BZ3tnxr7u0f4ZwlMeDDKZe97YHTuKHnITcOKm f5JA==
X-Gm-Message-State: AOJu0YxzovpAHrXvT97kQrP29ZOVi5SxwU7TgXN12siCuUnh7Q3/9ez7 wUHTzjqovRXDPui5L5H7yFQtRKLop4pm1crnl1QX20OIVFdQbIEhrTk8YrvSwPDoYHrgYxTPnm2 L48wnlORWCbP1utZCinzAO5AYBBfcE/8EWgAAlW2D6fY6Y96XEHcEDTvbs9slaDHKQo6RAqvazV Syj/1vfGIgsPuswgTmowXVCDk=
X-Google-Smtp-Source: AGHT+IEvYVCrna3tRXF53t1Wcq2cassGebYsEiDQAp++A2tv/kFC09aUx6Je7geOySuf+g5EIx0LIJZ6H3OtghfPnK4=
X-Received: by 2002:a92:b748:0:b0:365:d80:e1b2 with SMTP id c8-20020a92b748000000b003650d80e1b2mr12441070ilm.17.1708461033500; Tue, 20 Feb 2024 12:30:33 -0800 (PST)
MIME-Version: 1.0
References: <DU5PR83MB0639E61E6C13734D2A33D821914B2@DU5PR83MB0639.EURPRD83.prod.outlook.com>
In-Reply-To: <DU5PR83MB0639E61E6C13734D2A33D821914B2@DU5PR83MB0639.EURPRD83.prod.outlook.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Tue, 20 Feb 2024 13:30:06 -0700
Message-ID: <CA+k3eCTBpsdUcow9BUTROihv4bip=uAS9hwmC0vp0gEr_cRFLw@mail.gmail.com>
To: Pieter Kasselman <pieter.kasselman=40microsoft.com@dmarc.ietf.org>
Cc: "oauth@ietf.org" <oauth@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000003d0000611d61558"
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Xd0Lhk-AWdk9R2UWv2tHRQ3-JEU>
Subject: Re: [OAUTH-WG] Updating "Identity Chaining across Trust Domains" draft name
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.39
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, 20 Feb 2024 20:30:38 -0000

(a few days later than promised) the name has been updated and the new
draft revision published
https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-chaining/01/. A
listing of other changes copied from
https://www.ietf.org/archive/id/draft-ietf-oauth-identity-chaining-01.html#appendix-D-2
is included below as well:

-01

   - limit the authorization grant format to RFC7523 JWT
   - minor example fixes
   - editorial fixes
   - added Aaron Parecki to acknowledgements
   - renamed section headers to be more explicit
   - use more specific term "JWT authorization grant"
   - changed name to "OAuth Identity and Authorization Chaining Across
   Domains"
   - move use cases to appendix and add continuous integration use case


On Fri, Feb 9, 2024 at 12:08 PM Pieter Kasselman <pieter.kasselman=
40microsoft.com@dmarc.ietf.org> wrote:

> Following the working group adoption of the “Identity Chaining across
> Trust Domains” draft (see draft-ietf-oauth-identity-chaining-00 -
> Identity Chaining across Trust Domains
> <https://datatracker.ietf.org/doc/draft-ietf-oauth-identity-chaining/>),
> the editors thought it appropriate to update the name to “OAuth Identity
> and Authorization Chaining Across Domains” to align with OAuth naming
> conventions and reflect the use of OAuth authorization protocols. There is
> a PR tracking this update that can be viewed here
> https://github.com/oauth-wg/oauth-identity-chaining/pull/76 (update name
> with minor editorial changes for consistency).
>
>
>
> If there are no strong objections, we will update the name and republish
> the draft on 16 February 2024.
>
>
>
> Cheers
>
>
>
> Pieter
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth
>

-- 
_CONFIDENTIALITY NOTICE: This email may contain confidential and privileged 
material for the sole use of the intended recipient(s). Any review, use, 
distribution or disclosure by others is strictly prohibited.  If you have 
received this communication in error, please notify the sender immediately 
by e-mail and delete the message and any file attachments from your 
computer. Thank you._

v2.23.0 | Report a Bug | By Email