[Sipping] [Technical Errata Reported] RFC3665 (6984)
RFC Errata System <rfc-editor@rfc-editor.org> Tue, 31 May 2022 06:34 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
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 4167CC15AAE9 for <sipping@ietfa.amsl.com>; Mon, 30 May 2022 23:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.654
X-Spam-Level:
X-Spam-Status: No, score=-1.654 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 9gTL5YIm-Vhw for <sipping@ietfa.amsl.com>; Mon, 30 May 2022 23:33:56 -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 78760C15AAD4 for <sipping@ietf.org>; Mon, 30 May 2022 23:33:56 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5D4A73510C; Mon, 30 May 2022 23:33:56 -0700 (PDT)
To: alan.johnston@mci.com, sdonovan@dynamicsoft.com, rsparks@dynamicsoft.com, ccunningham@dynamicsoft.com, kevin.summers@sonusnet.com, superuser@gmail.com, francesca.palombini@ericsson.com, gonzalo.camarillo@ericsson.com, mary.ietf.barnes@gmail.com
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: xiaoxi.li@vodafone.com.au, sipping@ietf.org, rfc-editor@rfc-editor.org
Content-Type: text/plain; charset="UTF-8"
Message-Id: <20220531063356.5D4A73510C@rfcpa.amsl.com>
Date: Mon, 30 May 2022 23:33:56 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipping/knihHXxJ7cULT3u-5GipW6ob6hY>
X-Mailman-Approved-At: Tue, 31 May 2022 06:20:05 -0700
Subject: [Sipping] [Technical Errata Reported] RFC3665 (6984)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.34
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: Tue, 31 May 2022 06:34:00 -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: https://www.rfc-editor.org/errata/eid6984 -------------------------------------- Type: Technical Reported by: Xiaoxi Li <xiaoxi.li@vodafone.com.au> Section: 3.2 Original Text ------------- F5 INVITE Proxy 1 -> Proxy 2 INVITE sip:bob@biloxi.example.com SIP/2.0 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74bf9 ;received=192.0.2.101 Max-Forwards: 69 F7 INVITE Proxy 2 -> Bob INVITE sip:bob@client.biloxi.example.com SIP/2.0 Via: SIP/2.0/TCP ss2.biloxi.example.com:5060;branch=z9hG4bK721e4.1 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 ;received=192.0.2.111 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74bf9 ;received=192.0.2.101 Max-Forwards: 68 F16 ACK Proxy 1 -> Proxy 2 ACK sip:bob@client.biloxi.example.com SIP/2.0 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b76 ;received=192.0.2.101 Max-Forwards: 69 F17 ACK Proxy 2 -> Bob ACK sip:bob@client.biloxi.example.com SIP/2.0 Via: SIP/2.0/TCP ss2.biloxi.example.com:5060;branch=z9hG4bK721e4.1 Via: SIP/2.0/TCP ss1.atlanta.example.com:5060;branch=z9hG4bK2d4790.1 ;received=192.0.2.111 Via: SIP/2.0/TCP client.atlanta.example.com:5060;branch=z9hG4bK74b76 ;received=192.0.2.101 Max-Forwards: 68 From: Alice <sip:alice@atlanta.example.com>;tag=9fxced76sl Corrected Text -------------- the branch id in the topmost Via header(s) in the F16 F17 messages shouldn't be the same as the via headers added in F5 F7 messages. the ACK message shall only copy the same branch id in Via if it's for non-200 ok responses. this example deviates from the description in RFC 3261 chapter 16.6 Notes ----- the branch id in the topmost Via header(s) in the F16 F17 messages shouldn't be the same as the via headers added in F5 F7 messages. the ACK message shall only copy the same branch id in Via if it's for non-200 ok responses. this example deviates from the description in RFC 3261 chapter 16.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 (69… RFC Errata System