[straw] [Errata Rejected] RFC7332 (4108)

RFC Errata System <rfc-editor@rfc-editor.org> Wed, 15 March 2017 14:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: straw@ietfa.amsl.com
Delivered-To: straw@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 47AE01315CA; Wed, 15 Mar 2017 07:56:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] 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 eL272JdJfQXH; Wed, 15 Mar 2017 07:56:18 -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 01D3F1315C7; Wed, 15 Mar 2017 07:56:18 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id B106FB81736; Wed, 15 Mar 2017 07:56:06 -0700 (PDT)
To: chozhan.a@huawei.com, hadrielk@yahoo.com, victor.pascual@quobis.com
X-PHP-Originating-Script: 30:errata_mail_lib.php
From: RFC Errata System <rfc-editor@rfc-editor.org>
Cc: ben@nostrum.com, iesg@ietf.org, straw@ietf.org, rfc-editor@rfc-editor.org, charset=UTF-8@rfc-editor.org
Message-Id: <20170315145606.B106FB81736@rfc-editor.org>
Date: Wed, 15 Mar 2017 07:56:06 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/straw/56akRfYzpwZWcWbEnY4EQYobu84>
Subject: [straw] [Errata Rejected] RFC7332 (4108)
X-BeenThere: straw@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Sip Traversal Required for Applications to Work \(STRAW\) working group discussion list" <straw.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/straw>, <mailto:straw-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/straw/>
List-Post: <mailto:straw@ietf.org>
List-Help: <mailto:straw-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/straw>, <mailto:straw-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2017 14:56:19 -0000

The following errata report has been rejected for RFC7332,
"Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)".

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

--------------------------------------
Status: Rejected
Type: Editorial

Reported by: Chozhan A <chozhan.a@huawei.com>
Date Reported: 2014-09-11
Rejected by: Ben Campbell (IESG)

Section: 5

Original Text
-------------
If the received request did not contain a Max-Forwards header field,
one MUST be created in any request generated in the UAC side, as
described for proxies in Section 16.6, Step 3 of [RFC3261].

Corrected Text
--------------
If B2BUA creates a request as a result of processing a
incoming response, Max-Forwards MUST be added in any request
generated in the UAC side, as described for proxies in
Section 16.6, Step 3 of [RFC3261].

Notes
-----
Max-Forward is mandatory for Request as per RFC 3261. So this case is possible only on response processing.
 --VERIFIER NOTES-- 
   The existing text is correct. The fact that Max-Forwards is required to be present in a request does not invalidate text that says what to do if it is not.

--------------------------------------
RFC7332 (draft-ietf-straw-b2bua-loop-detection-04)
--------------------------------------
Title               : Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)
Publication Date    : August 2014
Author(s)           : H. Kaplan, V. Pascual
Category            : PROPOSED STANDARD
Source              : Sip Traversal Required for Applications to Work RAI
Area                : Real-time Applications and Infrastructure
Stream              : IETF
Verifying Party     : IESG