Found 1 record.
Status: Rejected (1)
RFC 7332, "Loop Detection Mechanisms for Session Initiation Protocol (SIP) Back-to-Back User Agents (B2BUAs)", August 2014Source of RFC: straw (rai)
Errata ID: 4108
Publication Format(s) : TEXT
Reported By: Chozhan A
Date Reported: 2014-09-11
Rejected by: Ben Campbell
Date Rejected: 2017-03-15
Section 5 says:
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].
It should say:
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].
Max-Forward is mandatory for Request as per RFC 3261. So this case is possible only on response processing.
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.