Return-Path: 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 7050412012D for ; Tue, 10 Sep 2019 17:42:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.997 X-Spam-Level: X-Spam-Status: No, score=-1.997 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, URIBL_BLOCKED=0.001] 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 Gx2OUf5qUXbu for ; Tue, 10 Sep 2019 17:42:26 -0700 (PDT) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) (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 3FA9612022A for ; Tue, 10 Sep 2019 17:42:26 -0700 (PDT) Received: by mail-io1-xd2e.google.com with SMTP id f12so41809331iog.12 for ; Tue, 10 Sep 2019 17:42:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=6HihxJ1/K60zWHpzMro5+QB7e41Ke/ZhBoAy9JtYsiw=; b=lspjuBnCx2zd39y/DR0nZgNgIbgLftg5pHEECtGf2Q2JKD8P/lPLvv5D1DCMIuKHx4 ppgDt4o5DOK11QaLfZf3U/HEYEQsL0aeSXW38hxDp8+d3MxSlVS6yJVHXYzwoaZdagst EWEREl31aOm50MbQYv1A6kD4BSRVhe9VuuJZHSUE3AS9nGUu7y0BOexAx3jVJwK8CP0/ SmmArdjktfGRtxcyuW4/jCPjhPJ2yasPfhHBVT4bby5vRKO1//JmfexGFPx061FPlp1v isRRG1XKeFrWvI1aOb8Ze66pBiLUlIRkP+kB7YYGUn/DpGDMOGaATIOesAngwlmsAvWH LbxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=6HihxJ1/K60zWHpzMro5+QB7e41Ke/ZhBoAy9JtYsiw=; b=VzsYxsyNOXBrtJsBGEajoUd1ghrFDXSLQxvXB91dztYg0wDdu5nKMf13jGkEbm2kys ioSXyXMTPiSdVBPoqZdj3YChyzIAo9rE/nSG3E2Wq820LjaYB4NVe6/kwUiRZmpbg2JD oUOmc5hfUpSrnMFupDmzuKcNwMrtHQ92oOhht/xQsedxGZTxyAMnVmcJ/p3YlJ0KG4Y8 0/R/SuSGJQ/r2gP3qOmepDziWk8rGfv7wsZjm1LAW+vruJ2gD7HGXboyuiYRDoHCyJIe TC8eHUYTwfZo2/Vym5+o7eyUcEQvgx6I0T5rRsYriMIVQJHEi+RUYbIDuJQIIy83v/jE e38w== X-Gm-Message-State: APjAAAXawGVKxVL3q3a/He428S5CfMDeVoZ+SmEaA3ai3Dh3KYkfbXQI sW3V7QTamf8eq1+aMWKsYNYEnp6H7gNIEpi7jNzJADX4CLY= X-Google-Smtp-Source: APXvYqw65pifOvjhhH7z74uTMgiKL2vyTqtkqLlz8yXvk3V9yrL7fPya7pMHPO+nJKKHp5HrWAeejvSqXJZaExujeKU= X-Received: by 2002:a02:683:: with SMTP id 125mr35802344jav.132.1568162545237; Tue, 10 Sep 2019 17:42:25 -0700 (PDT) MIME-Version: 1.0 References: <156816228460.22517.5277193592349076537.idtracker@ietfa.amsl.com> In-Reply-To: <156816228460.22517.5277193592349076537.idtracker@ietfa.amsl.com> From: Rifaat Shekh-Yusef Date: Tue, 10 Sep 2019 20:42:15 -0400 Message-ID: To: oauth Content-Type: multipart/alternative; boundary="00000000000075844605923c4b66" Archived-At: Subject: [OAUTH-WG] Fwd: New Version Notification for draft-yusef-oauth-nested-jwt-03.txt X-BeenThere: oauth@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: OAUTH WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Sep 2019 00:42:28 -0000 --00000000000075844605923c4b66 Content-Type: text/plain; charset="UTF-8" All, I have submitted a new version of the draft that includes a 3rd use case used by the *Network Service Mesh* project. https://networkservicemesh.io/ Regards, Rifaat ---------- Forwarded message --------- From: Date: Tue, Sep 10, 2019 at 8:38 PM Subject: New Version Notification for draft-yusef-oauth-nested-jwt-03.txt To: Rifaat Shekh-Yusef A new version of I-D, draft-yusef-oauth-nested-jwt-03.txt has been successfully submitted by Rifaat Shekh-Yusef and posted to the IETF repository. Name: draft-yusef-oauth-nested-jwt Revision: 03 Title: Nested JSON Web Token (JWT) Document date: 2019-09-10 Group: Individual Submission Pages: 6 URL: https://www.ietf.org/internet-drafts/draft-yusef-oauth-nested-jwt-03.txt Status: https://datatracker.ietf.org/doc/draft-yusef-oauth-nested-jwt/ Htmlized: https://tools.ietf.org/html/draft-yusef-oauth-nested-jwt-03 Htmlized: https://datatracker.ietf.org/doc/html/draft-yusef-oauth-nested-jwt Diff: https://www.ietf.org/rfcdiff?url2=draft-yusef-oauth-nested-jwt-03 Abstract: 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 submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat --00000000000075844605923c4b66 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
All,

I have submitted=C2=A0a new versio= n of the draft that includes a 3rd use case used by the Network Service = Mesh project.

Regards,
<= /div>
=C2=A0Rifaat

=C2=A0

---------- Forwarded me= ssage ---------
From: <internet-drafts@ietf.org>
Date: Tue, Sep = 10, 2019 at 8:38 PM
Subject: New Version Notification for draft-yusef-oa= uth-nested-jwt-03.txt
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>



A new version of I-D, draft-yusef-oauth-nested-jwt-03.txt
has been successfully submitted by Rifaat Shekh-Yusef and posted to the
IETF repository.

Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-yusef-oauth-nested-jwt<= br> Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A003
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Nested JSON Web Token (JWT)
Document date:=C2=A0 2019-09-10
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 6
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-drafts/draft-yusef-oauth-ne= sted-jwt-03.txt
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/draft-yusef-oauth-nested-jwt/
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https= ://tools.ietf.org/html/draft-yusef-oauth-nested-jwt-03
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/html/draft-yusef-oauth-nested-jwt Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://www.ietf.org/rfcdiff?url2=3Ddraft-yusef-oauth-nested-j= wt-03

Abstract:
=C2=A0 =C2=A0This specification extends the scope of the Nested JSON Web To= ken
=C2=A0 =C2=A0(JWT) to allow the enclosing JWT to contain its own Claims Set= in
=C2=A0 =C2=A0addition to the enclosed JWT.




Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

--00000000000075844605923c4b66--