RFC Errata


Errata Search

 
Source of RFC  
Summary Table Full Records

RFC 6044, "Mapping and Interworking of Diversion Information between Diversion and History-Info Headers in the Session Initiation Protocol (SIP)", October 2010

Note: This RFC has been obsoleted by RFC 7544

Source of RFC: INDEPENDENT

Errata ID: 2607
Status: Rejected
Type: Editorial

Reported By: Hadriel Kaplan
Date Reported: 2010-11-04
Rejected by: Nevil Brownlee
Date Rejected: 2014-03-06

Section 7 says:

   History-Info:
   <sip: diverting_user1_address; privacy=none >; index=1,
   <sip: diverting_user2_address; cause=408?privacy=history>;index=1.1,
   <sip: diverting_user3_address; cause=486?privacy=none>;index=1.1.1,
   <sip: last_diverting_target; cause=302>;index=1.1.1.1

7.2.  Example with History-Info Header Changed into Diversion Header

   History-Info:
   <sip: diverting_user1_address?privacy=history >; index=1,
   <sip: diverting_user2_address; cause=302? privacy=none>;index=1.1,
   <sip: last_diverting_target; cause=486>;index=1.1.1

It should say:

   History-Info:
   <sip:diverting_user1_address?Privacy=none>;index=1,
   <sip:diverting_user2_address?Reason=SIP%3Bcause%3D408?privacy=
      history>; index=1.1,
   <sip:diverting_user3_address?Reason=SIP%3Bcause%3D486?privacy=none>;
     index=1.1.1,
   <sip:last_diverting_target?Reason=SIP%3Bcause%3D302>;index=1.1.1.1

7.2.  Example with History-Info Header Changed into Diversion Header

   History-Info:
   <sip: diverting_user1_address?privacy=history >; index=1,
   <sip: diverting_user2_address?Reason=SIP%3Bcause%3D302&Privacy=none>;
     index=1.1,
   <sip: last_diverting_target?Reason=SIP%3Bcause%3D486>;index=1.1.1

Notes:

I know RFC 4244 makes this error all over the place, but the "cause" field is not a URI parameter. It is a header parameter of the Reason header field, and per the ABNF of RFC4244 Hist-Info, the Reason header is embedded into the URI, including its cause parameter - in other words, the cause field is a parameter of an embedded header inside a URI, as shown in the correction.

This error is made in section 2.2.1, 3.1, 5, 7.1, 7.2, and 7.3 of this RFC 6044.
--VERIFIER NOTES--
RFC author considers this erratum to be incorrect.

Report New Errata