IETF Logo Mail Archive

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

Eric Burger <eburger@standardstrack.com> Wed, 26 May 2021 00:32 UTC

Return-Path: <eburger@standardstrack.com>
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 441373A1589 for <sipcore@ietfa.amsl.com>; Tue, 25 May 2021 17:32:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.088
X-Spam-Level:
X-Spam-Status: No, score=-1.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_SBL=0.5, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=standardstrack.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 v5XRm0wI7vLl for <sipcore@ietfa.amsl.com>; Tue, 25 May 2021 17:32:06 -0700 (PDT)
Received: from se4o-iad1.servconfig.com (se4o-iad1.servconfig.com [199.250.217.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4249E3A1583 for <sipcore@ietf.org>; Tue, 25 May 2021 17:32:06 -0700 (PDT)
Received: from biz221.inmotionhosting.com ([192.145.239.201]) by se4-iad1.servconfig.com with esmtps (TLSv1.2:AES128-GCM-SHA256:128) (Exim 4.92) (envelope-from <eburger@standardstrack.com>) id 1llhSg-000Oq9-4m; Tue, 25 May 2021 20:32:02 -0400
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=standardstrack.com; s=default; h=References:To:Cc:In-Reply-To:Date:Subject: Mime-Version:Content-Type:Message-Id:From:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=u+Yh+OIIcoTs4OR3NxSq2PCMvS79je21iifZdAsUp3g=; b=f+2AvyyVSYzknFUYGRIXHQTJov +zOqA+qj33iZZ0IVCcqVIVJN3UOZB6sybCvxqoezBK4arMWxsjgbrEdr3kr4fRFoGQa8Z6LPOuqXZ PxPl2YjIQSDa5lu9SYU7P3yhSQML7e8e6Vo/nYZXSuOUXVTiFfv+KqJHMHUneY1b7M70=;
Received: from [68.100.100.136] (port=51613 helo=smtpclient.apple) by biz221.inmotionhosting.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <eburger@standardstrack.com>) id 1llhSb-00GT3T-KE; Tue, 25 May 2021 17:31:45 -0700
From: Eric Burger <eburger@standardstrack.com>
Message-Id: <22296D26-7DB4-4354-9F7D-3B66ACF302C8@standardstrack.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_8CC44EBC-E3C2-4FCB-A459-068DBAE2A987"; protocol="application/pkcs7-signature"; micalg="sha-256"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.100.0.2.22\))
Date: Tue, 25 May 2021 20:31:44 -0400
In-Reply-To: <20210518094837.CF8E0F407BA@rfc-editor.org>
Cc: Bhavik V Nagda <nagdab@gmail.com>, superuser@gmail.com, francesca.palombini@ericsson.com, Brian Rosen <br@brianrosen.net>, mahoney@nostrum.com, amrita_ch@yahoo.com, sipcore@ietf.org
To: RFC Errata System <rfc-editor@rfc-editor.org>
References: <20210518094837.CF8E0F407BA@rfc-editor.org>
X-Mailer: Apple Mail (2.3654.100.0.2.22)
X-Get-Message-Sender-Via: biz221.inmotionhosting.com: authenticated_id: eburger+standardstrack.com/only user confirmed/virtual account not confirmed
X-Authenticated-Sender: biz221.inmotionhosting.com: eburger@standardstrack.com
X-Originating-IP: 192.145.239.201
X-SpamExperts-Domain: biz221.inmotionhosting.com
X-SpamExperts-Username: 192.145.239.201
Authentication-Results: servconfig.com; auth=pass smtp.auth=192.145.239.201@biz221.inmotionhosting.com
X-SpamExperts-Outgoing-Class: ham
X-SpamExperts-Outgoing-Evidence: Combined (0.17)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT+RGAL+R4Qs0xlVN+ILfIcVPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5y1JMu9hk2W5e6SrIZvOH6vvVm4UDG4QGnnBexGYm3sWKBN e+0GLpPD/lei3mxuh/p02x+raDr28ND8nMrWCyczRF0UPH+c6TbuUqma5R7QOgPmI6JFCLKlvlNz VD4KX6sPKYMfE+V8uoWTTKbjYP+NDThzgMU94s37iQD4iRCUNolFbCszT3E3kdogf/OMyfuj8Amy CX6o5rVm0m4xVtZWHPdj4ZVtaA1ZzJ8YHqJCcr/GW1QOymN5zwCUbhFYnK5JJrEdbXjD+gyEEGSr 8l3jsMbsfPCbm49L3aSnN7qTZyTg127TqHZDxA/kZB41Rh/tZAm5CxZFJFmMJYowSgzgztdnziQq PRIzHM0xZsO3LKGYxI6eAT7BbzeYmkjqtHcKpj5lm4TlcuWQipsxoh6kO4I9/VzTYT7ojR51RkeG yuoo5keMxDDDmZL9OAzJml0F1vLM9cIybVokPLVwNGeGe/AqQm64UwYpIc8nFV5EcoDKd/XBM6Ee MCpZHojmAc8tUSl2WmT0XVwpr4noM18+7rSFKsvvEVZNOj9CknkFzlWgpiRfGOSpo4szFlf4Gpig 4iObGNKAIfyAxmFNRoYowxHqOeBT4r+LJYtXxWC01IjN1dJNyD7+sHaao9ZdwPBUvSqV1F5i8Viy 1vLMOMM2Dzn23lmbQ455+TwtsPDDuZQG7dYoWs1E//3c9tLxiFNewhCVhTPXHcTOo3QHXSGeZw4l bURmFp+QdNYfiyRLYBqZR3KVQgqF/fPYYAfEfsgoE9MMuhnhumpdqkJVxSZqX90QJPyDvvcxEEW2 UWB5dx9biWDiGjilhb5LmNIn2Om7emgr5XPyJxOmzYBSuLMzfzCNg5m9qaFCFMpwiEn7rTRJXT5B R761T1iPG2gBXJ3TPpuFqUUQz+mM8JAD4ECWdyEwLsGpJ0QVlXZ2XSz9LZyLwkuKI51yRR7AImuZ BFyiCb2MlFyJDbr15votsPUsiQHL3fBQQfCPJP/nl3LCdwDm3IkHus1KJdLlVEWX6971R4V/glmb eUNP/Dj/GUP5crDpQppZkgV1Qhx7bWVCV0cuOs2OpHbEsl81ku0Z0CrZBGK35FebR+5cfOOxWc5q jO0zpoeEbpMqYY9OJ1qM0elZegsYJRxHb8DZzi4G5qFoMMMh30z0ou3Uma6ICBqooWDkfaAACQiW MyAesX7/7H247ivQrwCcKDGaVzoLWnJWBRU3XZvUK1+KHvj8p2fa2TUkgk57eJPLGNtJ+TMPvA==
X-Report-Abuse-To: spam@se1-lax1.servconfig.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/T2hIqEcuFaXEwb0Aiwt90xyu_Yk>
Subject: Re: [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: Wed, 26 May 2021 00:32:11 -0000

Good catch! Yet another reason why people need to code to the text and not the examples. This is laughably wrong. [I can laugh at myself and the entire IESG for not noticing this error.]

Verified.

> On May 18, 2021, at 5:48 AM, RFC Errata System <rfc-editor@rfc-editor.org> wrote:
> 
> 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

v2.23.0 | Report a Bug | By Email