[Sipping] [Technical Errata Reported] RFC3665 (5294)
RFC Errata System <rfc-editor@rfc-editor.org> Thu, 22 March 2018 15:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: sipping@ietfa.amsl.com
Delivered-To: sipping@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BFD33124B18 for <sipping@ietfa.amsl.com>; Thu, 22 Mar 2018 08:56:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Cq50vRTL6GF5 for <sipping@ietfa.amsl.com>; Thu, 22 Mar 2018 08:56:36 -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 CFF8E1242F5 for <sipping@ietf.org>; Thu, 22 Mar 2018 08:56:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9C3BEB80C45; Thu, 22 Mar 2018 08:56:25 -0700 (PDT)
To: alan.johnston@mci.com, sdonovan@dynamicsoft.com, rsparks@dynamicsoft.com, ccunningham@dynamicsoft.com, kevin.summers@sonusnet.com, ben@nostrum.com, aamelnikov@fastmail.fm, adam@nostrum.com, gonzalo.camarillo@ericsson.com, mary.ietf.barnes@gmail.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: yoshigev@gmail.com, sipping@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20180322155625.9C3BEB80C45@rfc-editor.org>
Date: Thu, 22 Mar 2018 08:56:25 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipping/KEDnQqZEkJBTpEVGFMfe1m4LdMU>
X-Mailman-Approved-At: Mon, 26 Mar 2018 09:04:13 -0700
Subject: [Sipping] [Technical Errata Reported] RFC3665 (5294)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "SIPPING Working Group \(applications of SIP\)" <sipping.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipping>, <mailto:sipping-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sipping/>
List-Post: <mailto:sipping@ietf.org>
List-Help: <mailto:sipping-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipping>, <mailto:sipping-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 15:56:39 -0000
The following errata report has been submitted for RFC3665, "Session Initiation Protocol (SIP) Basic Call Flow Examples". -------------------------------------- You may review the report below and at: http://www.rfc-editor.org/errata/eid5294 -------------------------------------- Type: Technical Reported by: Yehoshua Gev <yoshigev@gmail.com> Section: 3.1 Original Text ------------- BYE sip:alice@client.atlanta.example.com SIP/2.0 Corrected Text -------------- BYE sip:alice@client.atlanta.example.com;transport=tcp SIP/2.0 Notes ----- In Example 3.1, the URI of the Contact header field of the INVITE request (F1) containes a parameter "transport=tcp". According to section 12.2.1.1 of RFC 3261, this URI should be used as the Request-URI for Bob sending requests within this dialog. As there is no explicit text about omitting parameters from the URI, the Request-URI should contain the "transport=tcp" parameter. Hence, the Request-URI of the BYE request (F5) should contain the parameter. It seems that the this problem was reported some years ago in the sip-implementors list: https://lists.cs.columbia.edu/pipermail/sip-implementors/2006-July/013507.html The same problem appear in other examples, specifically 3.2 and 3.6. 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. -------------------------------------- RFC3665 (draft-ietf-sipping-basic-call-flows-02) -------------------------------------- Title : Session Initiation Protocol (SIP) Basic Call Flow Examples Publication Date : December 2003 Author(s) : A. Johnston, S. Donovan, R. Sparks, C. Cunningham, K. Summers Category : BEST CURRENT PRACTICE Source : Session Initiation Proposal Investigation Area : Real-time Applications and Infrastructure Stream : IETF Verifying Party : IESG
- [Sipping] [Technical Errata Reported] RFC3665 (52… RFC Errata System