[Sipping] [Errata Rejected] RFC3665 (4723)

RFC Errata System <rfc-editor@rfc-editor.org> Thu, 30 June 2016 16:27 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 B4AEC12DABD; Thu, 30 Jun 2016 09:27:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.048
X-Spam-Level:
X-Spam-Status: No, score=-104.048 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] 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 r5uGZntb2VJ5; Thu, 30 Jun 2016 09:27:43 -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 EE3CF12D113; Thu, 30 Jun 2016 09:27:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D9CC5B802FE; Thu, 30 Jun 2016 09:27:42 -0700 (PDT)
To: benoitentzmann@hotmail.com, alan.johnston@mci.com, sdonovan@dynamicsoft.com, rsparks@dynamicsoft.com, ccunningham@dynamicsoft.com, kevin.summers@sonusnet.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Message-Id: <20160630162742.D9CC5B802FE@rfc-editor.org>
Date: Thu, 30 Jun 2016 09:27:42 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/sipping/oTdGOBu10ngMupXZxtsRtRSbZR4>
X-Mailman-Approved-At: Thu, 30 Jun 2016 09:29:39 -0700
Cc: ben@nostrum.com, sipping@ietf.org, iesg@ietf.org, rfc-editor@rfc-editor.org
Subject: [Sipping] [Errata Rejected] RFC3665 (4723)
X-BeenThere: sipping@ietf.org
X-Mailman-Version: 2.1.17
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, 30 Jun 2016 16:27:44 -0000

The following errata report has been rejected for RFC3665,
"Session Initiation Protocol (SIP) Basic Call Flow Examples".

--------------------------------------
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=3665&eid=4723

--------------------------------------
Status: Rejected
Type: Technical

Reported by: Benoit Entzmann <benoitentzmann@hotmail.com>
Date Reported: 2016-06-30
Rejected by: Ben Campbell (IESG)

Section: GLOBAL

Original Text
-------------
CSeq: 1 BYE

Corrected Text
--------------
CSeq: 2 BYE

Notes
-----
RFC 3261:
Section 15.1.1 UAC Behavior
   A BYE request is constructed as would any other request within a
   dialog, as described in Section 12.

Section 12.2.1.1 Generating the Request
   A request within a dialog is constructed by using many of the
   components of the state stored as part of the dialog...
    ... Requests within a dialog MUST contain strictly monotonically
   increasing and contiguous CSeq sequence numbers (increasing-by-one)
   in each direction 

Each direction of the dialog shows CSeq: 1 so whatever is the direction that generates the BYE it must increase the value to 2
 --VERIFIER NOTES-- 
   The CSeq numbering space is independent for each peer. Alice's CSeq values do not affect Bob's. The intent of the phrase "in each direction" in the quote is to say that each "direction" has increments independently of the other.

--------------------------------------
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