RFC Errata
Found 1 record.
Status: Held for Document Update (1)
RFC 5850, "A Call Control and Multi-Party Usage Framework for the Session Initiation Protocol (SIP)", May 2010
Source of RFC: sipping (rai)
Errata ID: 3662
Status: Held for Document Update
Type: Editorial
Publication Format(s) : TEXT
Reported By: Joël Repiquet
Date Reported: 2013-06-17
Held for Document Update by: Gonzalo Camarillo
Section 2.5 says:
The multi-party architecture may also need to provide a mechanism to get information about the status/handling of a dialog (for example, information about the history of other contacts attempted prior to the current contact). Finally, the architecture should provide ample opportunities to present informational URIs that relate to calls, conversations, or dialogs in some way. For example, consider the SIP Call-Info header or Contact header fields returned in a 300-class response. Frequently, additional information about a call or dialog can be fetched via non-SIP URIs. For example, consider a web page for package tracking when calling a delivery company or a web page with related documentation when joining a dial-in conference. The use of URIs in the multi-party framework is discussed in more detail in Section 3.7.
It should say:
The multi-party architecture may also need to provide a mechanism to get information about the status/handling of a dialog (for example, information about the history of other contacts attempted prior to the current contact). Finally, the architecture should provide ample opportunities to present informational URIs that relate to calls, conversations, or dialogs in some way. For example, consider the SIP Call-Info header or Contact header fields returned in a 300-class response. Frequently, additional information about a call or dialog can be fetched via non-SIP URIs. For example, consider a web page for package tracking when calling a delivery company or a web page with related documentation when joining a dial-in conference. The use of URIs in the multi-party framework is discussed in more detail in Section 2.7.