--- 1/draft-ietf-bliss-problem-statement-03.txt 2009-03-09 23:12:05.000000000 +0100 +++ 2/draft-ietf-bliss-problem-statement-04.txt 2009-03-09 23:12:05.000000000 +0100 @@ -1,87 +1,101 @@ BLISS J. Rosenberg Internet-Draft Cisco -Intended status: Informational November 3, 2008 -Expires: May 7, 2009 +Intended status: Informational March 9, 2009 +Expires: September 10, 2009 Basic Level of Interoperability for Session Initiation Protocol (SIP) Services (BLISS) Problem Statement - draft-ietf-bliss-problem-statement-03 + draft-ietf-bliss-problem-statement-04 Status of this Memo - By submitting this Internet-Draft, each author represents that any - applicable patent or other IPR claims of which he or she is aware - have been or will be disclosed, and any of which he or she becomes - aware will be disclosed, in accordance with Section 6 of BCP 79. + This Internet-Draft is submitted to IETF in full conformance with the + provisions of BCP 78 and BCP 79. This document may contain material + from IETF Documents or IETF Contributions published or made publicly + available before November 10, 2008. The person(s) controlling the + copyright in some of this material may not have granted the IETF + Trust the right to allow modifications of such material outside the + IETF Standards Process. Without obtaining an adequate license from + the person(s) controlling the copyright in such materials, this + document may not be modified outside the IETF Standards Process, and + derivative works of it may not be created outside the IETF Standards + Process, except to format it for publication as an RFC or to + translate it into languages other than English. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. - This Internet-Draft will expire on May 7, 2009. + This Internet-Draft will expire on September 10, 2009. Copyright Notice - Copyright (C) The IETF Trust (2008). + Copyright (c) 2009 IETF Trust and the persons identified as the + document authors. All rights reserved. + + This document is subject to BCP 78 and the IETF Trust's Legal + Provisions Relating to IETF Documents in effect on the date of + publication of this document (http://trustee.ietf.org/license-info). + Please review these documents carefully, as they describe your rights + and restrictions with respect to this document. Abstract The Session Initiation Protocol (SIP) has been designed as a general purpose protocol for establishing and managing multimedia sessions. It provides many core functions and extensions in support of features such as transferring of calls, parking calls, and so on. However, interoperability of more advanced features between different vendors has been poor. This document describes the reason behind these interoperability problems, and presents a framework for addressing them. Table of Contents - 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 - 2. The Confusion of Tongues . . . . . . . . . . . . . . . . . . . 4 - 3. Concrete Examples . . . . . . . . . . . . . . . . . . . . . . 5 - 3.1. Call Forward No Answer . . . . . . . . . . . . . . . . . . 5 - 3.1.1. Approach 1: UA Redirects . . . . . . . . . . . . . . . 6 - 3.1.2. Approach II: Proxy Forwards . . . . . . . . . . . . . 7 - 3.1.3. Approach III: UA Proxies . . . . . . . . . . . . . . . 8 - 3.1.4. Approach IV: Call Processing Language . . . . . . . . 9 - 3.1.5. Failure Cases . . . . . . . . . . . . . . . . . . . . 10 - 3.1.5.1. No One Implements . . . . . . . . . . . . . . . . 11 - 3.1.5.2. Both Implement . . . . . . . . . . . . . . . . . . 11 - 3.1.5.3. Missing Half . . . . . . . . . . . . . . . . . . . 11 - 4. Solution Considerations . . . . . . . . . . . . . . . . . . . 11 - 5. BLISS Solution Framework . . . . . . . . . . . . . . . . . . . 13 - 5.1. Phase I - Identify a Feature Group . . . . . . . . . . . . 13 - 5.2. Phase II - Gather Data . . . . . . . . . . . . . . . . . . 15 - 5.3. BLISS Phase III - Problem Definition . . . . . . . . . . . 15 - 5.4. BLISS Phase 4 - Minimum Interop Definition . . . . . . . . 16 - 6. Structure of the BLISS Final Deliverable . . . . . . . . . . . 17 - 7. Security Considerations . . . . . . . . . . . . . . . . . . . 18 - 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 18 - 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 18 - 10. Informative References . . . . . . . . . . . . . . . . . . . . 18 - Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 19 - Intellectual Property and Copyright Statements . . . . . . . . . . 20 + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 + 2. The Confusion of Tongues . . . . . . . . . . . . . . . . . . . 5 + 3. Concrete Examples . . . . . . . . . . . . . . . . . . . . . . 6 + 3.1. Call Forward No Answer . . . . . . . . . . . . . . . . . . 6 + 3.1.1. Approach 1: UA Redirects . . . . . . . . . . . . . . . 7 + 3.1.2. Approach II: Proxy Forwards . . . . . . . . . . . . . 8 + 3.1.3. Approach III: UA Proxies . . . . . . . . . . . . . . . 9 + 3.1.4. Approach IV: Call Processing Language . . . . . . . . 10 + 3.1.5. Failure Cases . . . . . . . . . . . . . . . . . . . . 11 + 3.1.5.1. No One Implements . . . . . . . . . . . . . . . . 12 + 3.1.5.2. Both Implement . . . . . . . . . . . . . . . . . . 12 + 3.1.5.3. Missing Half . . . . . . . . . . . . . . . . . . . 12 + 4. Solution Considerations . . . . . . . . . . . . . . . . . . . 12 + 5. BLISS Solution Framework . . . . . . . . . . . . . . . . . . . 14 + 5.1. Phase I - Identify a Feature Group . . . . . . . . . . . . 14 + 5.2. Phase II - Gather Data . . . . . . . . . . . . . . . . . . 16 + 5.3. BLISS Phase III - Problem Definition . . . . . . . . . . . 16 + 5.4. BLISS Phase 4 - Minimum Interop Definition . . . . . . . . 17 + 6. Structure of the BLISS Final Deliverable . . . . . . . . . . . 18 + 7. Security Considerations . . . . . . . . . . . . . . . . . . . 19 + 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 19 + 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 19 + 10. Informative References . . . . . . . . . . . . . . . . . . . . 19 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 20 1. Introduction The Session Initiation Protocol (SIP) [RFC3261] has been designed as a general purpose protocol for establishing and managing multimedia sessions. In this role, it provides many core functions and extensions to support "session management features". In this context, session management features (or just features in this specification) are operations, typically invoked by the user, that provide some form value-added functionality within the context of a @@ -805,55 +819,10 @@ Author's Address Jonathan Rosenberg Cisco Iselin, NJ US Email: jdrosen@cisco.com URI: http://www.jdrosen.net - -Full Copyright Statement - - Copyright (C) The IETF Trust (2008). - - This document is subject to the rights, licenses and restrictions - contained in BCP 78, and except as set forth therein, the authors - retain all their rights. - - This document and the information contained herein are provided on an - "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS - OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND - THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS - OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF - THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED - WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. - -Intellectual Property - - The IETF takes no position regarding the validity or scope of any - Intellectual Property Rights or other rights that might be claimed to - pertain to the implementation or use of the technology described in - this document or the extent to which any license under such rights - might or might not be available; nor does it represent that it has - made any independent effort to identify any such rights. Information - on the procedures with respect to rights in RFC documents can be - found in BCP 78 and BCP 79. - - Copies of IPR disclosures made to the IETF Secretariat and any - assurances of licenses to be made available, or the result of an - attempt made to obtain a general license or permission for the use of - such proprietary rights by implementers or users of this - specification can be obtained from the IETF on-line IPR repository at - http://www.ietf.org/ipr. - - The IETF invites any interested party to bring to its attention any - copyrights, patents or patent applications, or other proprietary - rights that may cover technology that may be required to implement - this standard. Please address the information to the IETF at - ietf-ipr@ietf.org. - -Acknowledgment - - Funding for the RFC Editor function is provided by the IETF - Administrative Support Activity (IASA).