[sipcore] [Technical Errata Reported] RFC8688 (6586)

RFC Errata System <rfc-editor@rfc-editor.org> Tue, 18 May 2021 09:48 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 220273A1582 for <sipcore@ietfa.amsl.com>; Tue, 18 May 2021 02:48:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 KdfanOpz_LKh for <sipcore@ietfa.amsl.com>; Tue, 18 May 2021 02:48:38 -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 A55003A1578 for <sipcore@ietf.org>; Tue, 18 May 2021 02:48:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id CF8E0F407BA; Tue, 18 May 2021 02:48:37 -0700 (PDT)
To: eburger@standardstrack.com, nagdab@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: amrita_ch@yahoo.com, sipcore@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20210518094837.CF8E0F407BA@rfc-editor.org>
Date: Tue, 18 May 2021 02:48:37 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/sattjAunJl5Xrit9PwG-eMsJDrE>
Subject: [sipcore] [Technical Errata Reported] RFC8688 (6586)
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: Tue, 18 May 2021 09:48:43 -0000

The following errata report has been submitted for RFC8688,
"A Session Initiation Protocol (SIP) Response Code for Rejected Calls".

--------------------------------------
You may review the report below and at:
https://www.rfc-editor.org/errata/eid6586

--------------------------------------
Type: Technical
Reported by: Amrita Bhatt <amrita_ch@yahoo.com>

Section: 3

Original Text
-------------
                         +--------+         +-----------+
                         | Called |         |   Call    |
        +-----+          | Party  |         | Analytics |   +-----+
        | UAC |          | Proxy  |         |  Engine   |   | UAS |
        +-----+          +--------+         +-----------+   +-----+
           |  INVITE         |                    |            |
           | --------------> |  Is call OK?       |            |
           |                 |------------------->|            |
           |                 |                    |            |
           |                 |               Yes  |            |
           |                 |<-------------------|            |
           |                 |                    |            |
           |                 | INVITE             |            |
           |                 | ------------------------------> |
           |                 |                    |            |
           |                 |                    |       607  |
           |                 | <------------------------------ |
           |                 |                    |            |
           |                 |  Unwanted call     |            |
           |            607  | -----------------> |            |
           | <-------------- |  indicators        |            |
           |                 |                    |            |


Corrected Text
--------------
                         +--------+         +-----------+
                         | Called |         |   Call    |
        +-----+          | Party  |         | Analytics |   +-----+
        | UAC |          | Proxy  |         |  Engine   |   | UAS |
        +-----+          +--------+         +-----------+   +-----+
           |  INVITE         |                    |            |
           | --------------> |  Is call OK?       |            |
           |                 |------------------->|            |
           |                 |                    |            |
           |                 |               No   |            |
           |                 |<-------------------|            |
           |                 |                    |            |
           |                 |              	  |            |
           |                 |                    |            |
           |                 |                    |            |
           |            608  |                    |            |
           | <-------------- |                    |            |
           |                 |                    |            |


Notes
-----
"Figure 4: Rejected (608) Ladder Diagram" does not depict correct signalling flow.

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. 

--------------------------------------
RFC8688 (draft-ietf-sipcore-rejected-09)
--------------------------------------
Title               : A Session Initiation Protocol (SIP) Response Code for Rejected Calls
Publication Date    : December 2019
Author(s)           : E.W. Burger, B. Nagda
Category            : PROPOSED STANDARD
Source              : Session Initiation Protocol Core
Area                : Applications and Real-Time
Stream              : IETF
Verifying Party     : IESG