[sipcore] [Technical Errata Reported] RFC8599 (7136)
RFC Errata System <rfc-editor@rfc-editor.org> Sun, 18 September 2022 02:14 UTC
Return-Path: <wwwrun@rfcpa.amsl.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 2E238C1522C0 for <sipcore@ietfa.amsl.com>; Sat, 17 Sep 2022 19:14:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.659
X-Spam-Level:
X-Spam-Status: No, score=-1.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_PASS=-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=no autolearn_force=no
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 l4HZuyiMFzhM for <sipcore@ietfa.amsl.com>; Sat, 17 Sep 2022 19:14:36 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 09FDAC1522AB for <sipcore@ietf.org>; Sat, 17 Sep 2022 19:14:36 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id BA536877C8; Sat, 17 Sep 2022 19:14:35 -0700 (PDT)
To: christer.holmberg@ericsson.com, michael.arnold@metaswitch.com, superuser@gmail.com, francesca.palombini@ericsson.com, br@brianrosen.net, mahoney@nostrum.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: alex@au.voipcloud.online, sipcore@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220918021435.BA536877C8@rfcpa.amsl.com>
Date: Sat, 17 Sep 2022 19:14:35 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipcore/B760OV9-D5bVm8ncZ-Rgzf1ARqU>
Subject: [sipcore] [Technical Errata Reported] RFC8599 (7136)
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 18 Sep 2022 02:14:40 -0000
The following errata report has been submitted for RFC8599, "Push Notification with the Session Initiation Protocol (SIP)". -------------------------------------- You may review the report below and at: https://www.rfc-editor.org/errata/eid7136 -------------------------------------- Type: Technical Reported by: Alex Vasilchenko <alex@au.voipcloud.online> Section: 1; 4.1.3 Original Text ------------- In section 1. Introduction it says: Example of a SIP REGISTER request in the flow above: REGISTER sip:alice@example.com SIP/2.0 (the rest part of the message is omitted) In section 4.1.4. Sending Binding-Refresh Requests Using Non-push Mechanism it says: Example of a SIP REGISTER request including a 'sip.pnsreg' media feature tag: REGISTER sip:alice@example.com SIP/2.0 (the rest part of the message is omitted) Corrected Text -------------- In section 1. Introduction it should be: Example of a SIP REGISTER request in the flow above: REGISTER sip:example.com SIP/2.0 (the rest part of the message is omitted) In section 4.1.4. Sending Binding-Refresh Requests Using Non-push Mechanism it should be: Example of a SIP REGISTER request including a 'sip.pnsreg' media feature tag: REGISTER sip:example.com SIP/2.0 (the rest part of the message is omitted) Notes ----- The error is in R-URI: REGISTER sip:alice@example.com SIP/2.0 It should be: REGISTER sip:example.com SIP/2.0 According to RFC3261 - 10.2 Constructing the REGISTER Request - Request-URI: The Request-URI names the domain of the location service for which the registration is meant (for example, "sip:chicago.com"). The "userinfo" and "@" components of the SIP URI MUST NOT be present. 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. -------------------------------------- RFC8599 (draft-ietf-sipcore-sip-push-29) -------------------------------------- Title : Push Notification with the Session Initiation Protocol (SIP) Publication Date : May 2019 Author(s) : C. Holmberg, M. Arnold Category : PROPOSED STANDARD Source : Session Initiation Protocol Core Area : Applications and Real-Time Stream : IETF Verifying Party : IESG
- [sipcore] [Technical Errata Reported] RFC8599 (71… RFC Errata System