The IESG has approved the following document: - 'Session Initiation Protocol (SIP) History-Info Header Call Flow Examples' (draft-ietf-sipcore-rfc4244bis-callflows-08.txt) as Informational RFC This document is the product of the Session Initiation Protocol Core Working Group. The IESG contact persons are Richard Barnes and Gonzalo Camarillo. A URL of this Internet Draft is: http://datatracker.ietf.org/doc/draft-ietf-sipcore-rfc4244bis-callflows/ Technical Summary This document describes use cases and documents call flows which require the History-Info header field to capture the Request-URIs as a Session Initiation Protocol (SIP) Request is retargeted. The use cases are described along with the corresponding call flow diagrams and messaging details. Working Group Summary There was considerable debate about the placement of these call flows: all within the bis draft, all in a separate draft, or some in the bis and some in this separate draft. This is largely a matter of taste. Ultimately the WG decided that a separate draft for all the call flows was preferred. It took an exceedingly long time to get this document adequately reviewed and to resolve issues with rfc4244bis that the reviews resolved. It has been hard to get attention on this because rfc4244bis has been considered "done" for a long time by those who care. Document Quality Are there existing implementations of the protocol? NA. See the writeup for 4244bis. Have a significant number of vendors indicated their plan to implement the specification? NA. See the writeup for 4244bis. Are there any reviewers that merit special mention as having done a thorough review, e.g., one that resulted in important changes or a conclusion that the document had no substantive issues? Dale Worley did very heavy lifting reviewing all of these call flows, checking all the details. He deserves five gold stars. Roland Jesske, Laura Liess, and Marianne Mohali also did careful reviews that led to fixes. If there was a MIB Doctor, Media Type or other expert review, what was its course (briefly)? In the case of a Media Type review, on what date was the request posted? There is nothing in this document that calls for an expert review. Personnel Who is the Document Shepherd? Paul Kyzivat Who is the Responsible Area Director? Richard Barnes
