[sipcore] [Editorial Errata Reported] RFC8898 (6495)
RFC Errata System <rfc-editor@rfc-editor.org> Fri, 26 March 2021 05:14 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 684F03A0FED for <sipcore@ietfa.amsl.com>; Thu, 25 Mar 2021 22:14:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 rFgSj0IdHNHT for <sipcore@ietfa.amsl.com>; Thu, 25 Mar 2021 22:14:28 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1230F3A0FEC for <sipcore@ietf.org>; Thu, 25 Mar 2021 22:14:27 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 5D874F40766; Thu, 25 Mar 2021 22:14:19 -0700 (PDT)
To: rifaat.s.ietf@gmail.com, christer.holmberg@ericsson.com, victor.pascual.avila@gmail.com, superuser@gmail.com, francesca.palombini@ericsson.com, br@brianrosen.net, mahoney@nostrum.com
X-PHP-Originating-Script: 1005:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: erlee1975@gmail.com, sipcore@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210326051419.5D874F40766@rfc-editor.org>
Date: Thu, 25 Mar 2021 22:14:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/CPAYzFz56zIkGd0JhAyP5Vq6uKM>
X-Mailman-Approved-At: Fri, 26 Mar 2021 07:19:50 -0700
Subject: [sipcore] [Editorial Errata Reported] RFC8898 (6495)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipcore/>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Mar 2021 05:14:33 -0000
The following errata report has been submitted for RFC8898, "Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid6495 -------------------------------------- Type: Editorial Reported by: EungRok Lee <erlee1975@gmail.com> Section: 1.4.2 Original Text ------------- The registrar validates the access token. If the access token is a reference token, the registrar MAY perform an introspection [RFC7662], as in steps [4] and [5], in order to obtain more information about the access token and its scope, per [RFC7662]. Otherwise, after the registrar validates the token, it inspects its claims and acts upon it. Corrected Text -------------- The registrar validates the access token. If the access token is a reference token, the registrar MAY perform an introspection [RFC7662], as in steps [3] and [4], in order to obtain more information about the access token and its scope, per [RFC7662]. Otherwise, after the registrar validates the token, it inspects its claims and acts upon it. Notes ----- As you can see figure 2, introspection is processed in steps [3] and [4]. Instructions: ------------- This erratum is currently posted as "Reported". If necessary, please use "Reply All" to discuss whether it should be verified or rejected. When a decision is reached, the verifying party can log in to change the status and edit the report, if necessary. -------------------------------------- RFC8898 (draft-ietf-sipcore-sip-token-authnz-17) -------------------------------------- Title : Third-Party Token-Based Authentication and Authorization for Session Initiation Protocol (SIP) Publication Date : September 2020 Author(s) : R. Shekh-Yusef, C. Holmberg, V. Pascual Category : PROPOSED STANDARD Source : Session Initiation Protocol Core Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
- [sipcore] [Editorial Errata Reported] RFC8898 (64… RFC Errata System