--- 1/draft-ietf-sipcore-rfc4244bis-callflows-05.txt 2013-07-15 05:14:22.150331649 -0700 +++ 2/draft-ietf-sipcore-rfc4244bis-callflows-06.txt 2013-07-15 05:14:22.234333866 -0700 @@ -5,21 +5,21 @@ Expires: January 2, 2014 Skype S. Schubert NTT H. van Elburg Detecon International Gmbh C. Holmberg Ericsson Jul 2013 Session Initiation Protocol (SIP) History-Info Header Call Flow Examples - draft-ietf-sipcore-rfc4244bis-callflows-05.txt + draft-ietf-sipcore-rfc4244bis-callflows-06.txt Abstract 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. Status of this Memo @@ -1569,22 +1571,22 @@ SIP/2.0 200 OK Via: SIP/2.0/TCP 192.0.2.1;branch=z9hG4bKnashds7 From: John ;tag=a73kszlfl To: John ;tag=b88sn Call-ID: 1j9FpLxk3uxtm8tn@192.0.2.1 CSeq: 1 REGISTER Contact: ;\ pub-gruu="sip:john@example.com;\ gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6";\ temp-gruu=\ - "sip:tgruu.7hs==jd7vnzga5w7fajsc7-ajd6fabz0f8g5@example.com;gr";\ - +sip.instance=\ + "sip:tgruu.7hs==jd7vnzga5w7fajsc7-ajd6fabz0f8g5@example.com;\ + gr";+sip.instance=\ "";\ expires=3600 Content-Length: 0 [SDP Not Shown] Assuming Alice has a knowledge of a gruu either through prior communication or through other means such as presence places a call to John's gruu. @@ -1783,21 +1785,21 @@ States, are telephone numbers that are free for users to call. In the telephone network, toll free numbers are just aliases to actual numbers which are used for routing of the call. In order to process the call in the PSTN, a switch will perform a query (using a protocol called TCAP), which will return either a phone number or the identity of a carrier which can handle the call. There has been recent work on allowing such PSTN translation services to be accessed by SIP proxy servers through IP querying mechanisms. - ENUM, for example [RFC3761] has already been proposed as a mechanism + ENUM, for example [RFC6117] has already been proposed as a mechanism for performing Local Number Portability (LNP) queries [RFC4769], and recently been proposed for performing calling name queries [I-D.ietf-enum-cnam]. Using it for 8xx number translations is a logical next-step. Once such a translation has been performed, the call needs to be routed towards the target of the request. Normally, this would happen by selecting a PSTN gateway which is a good route towards the translated number. However, one can imagine all-IP systems where the 8xx numbers are SIP endpoints on an IP network, in which case the @@ -1921,71 +1923,46 @@ Marianne Mohali provided extensive review and comments on call-flow, message examples and text. 6. Informative References [RFC3261] Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston, A., Peterson, J., Sparks, R., Handley, M., and E. Schooler, "SIP: Session Initiation Protocol", RFC 3261, June 2002. - [RFC3326] Schulzrinne, H., Oran, D., and G. Camarillo, "The Reason - Header Field for the Session Initiation Protocol (SIP)", - RFC 3326, December 2002. - - [RFC3323] Peterson, J., "A Privacy Mechanism for the Session - Initiation Protocol (SIP)", RFC 3323, November 2002. - - [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate - Requirement Levels", BCP 14, RFC 2119, March 1997. - - [RFC5246] Dierks, T. and E. Rescorla, "The Transport Layer Security - (TLS) Protocol Version 1.2", RFC 5246, August 2008. - - [RFC4244] Barnes, M., "An Extension to the Session Initiation - Protocol (SIP) for Request History Information", RFC 4244, - November 2005. - [RFC5627] Rosenberg, J., "Obtaining and Using Globally Routable User Agent URIs (GRUUs) in the Session Initiation Protocol (SIP)", RFC 5627, October 2009. - [RFC5630] Audet, F., "The Use of the SIPS URI Scheme in the Session - Initiation Protocol (SIP)", RFC 5630, October 2009. - [RFC3087] Campbell, B. and R. Sparks, "Control of Service Context using SIP Request-URI", RFC 3087, April 2001. [RFC4240] Burger, E., Van Dyke, J., and A. Spitzer, "Basic Network Media Services with SIP", RFC 4240, December 2005. [RFC5039] Rosenberg, J. and C. Jennings, "The Session Initiation Protocol (SIP) and Spam", RFC 5039, January 2008. [RFC4458] Jennings, C., Audet, F., and J. Elwell, "Session Initiation Protocol (SIP) URIs for Applications such as Voicemail and Interactive Voice Response (IVR)", RFC 4458, April 2006. - [RFC3761] Faltstrom, P. and M. Mealling, "The E.164 to Uniform - Resource Identifiers (URI) Dynamic Delegation Discovery - System (DDDS) Application (ENUM)", RFC 3761, April 2004. + [RFC6117] Hoeneisen, B., Mayrhofer, A., and J. Livingood, "IANA + Registration of Enumservices: Guide, Template, and IANA + Considerations", RFC 6117, March 2011. [RFC4769] Livingood, J. and R. Shockey, "IANA Registration for an Enumservice Containing Public Switched Telephone Network (PSTN) Signaling Information", RFC 4769, November 2006. - [RFC3969] Camarillo, G., "The Internet Assigned Number Authority - (IANA) Uniform Resource Identifier (URI) Parameter - Registry for the Session Initiation Protocol (SIP)", - BCP 99, RFC 3969, December 2004. - [I-D.ietf-enum-cnam] Shockey, R., "IANA Registration for an Enumservice Calling Name Delivery (CNAM) Information and IANA Registration for URI type 'pstndata'", draft-ietf-enum-cnam-08 (work in progress), September 2008. [I-D.ietf-sipcore-rfc4244bis] Barnes, M., Audet, F., Schubert, S., Elburg, H., and C. Holmberg, "An Extension to the Session Initiation Protocol (SIP) for Request History Information",