Browse Prior Art Database

Clarifications for the Use of REFER with RFC 6665 (RFC7647)

IP.com Disclosure Number: IPCOM000244988D
Original Publication Date: 2015-Sep-01
Included in the Prior Art Database: 2016-Feb-05
Document File: 12 page(s) / 13K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Sparks: AUTHOR [+2]

Abstract

The SIP REFER method relies on the SIP-Specific Event Notification framework. That framework was revised by [RFC6665]. This document highlights the implications of the requirement changes in RFC 6665, and updates [RFC3515] to clarify and disambiguate the impact of those changes.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 22% of the total text.

Internet Engineering Task Force (IETF)                         R. Sparks Request for Comments: 7647                                        Oracle Updates: 3515                                                 A.B. Roach Category: Standards Track                                        Mozilla ISSN: 2070-1721                                           September 2015

            Clarifications for the Use of REFER with RFC 6665

Abstract

   The SIP REFER method relies on the SIP-Specific Event Notification    framework.  That framework was revised by RFC 6665.  This document    highlights the implications of the requirement changes in RFC 6665,    and updates the definition of the REFER method described in RFC 3515    to clarify and disambiguate the impact of those changes.

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by the    Internet Engineering Steering Group (IESG).  Further information on    Internet Standards is available in Section 2 of RFC 5741.

   Information about the current status of this document, any errata,    and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc7647.

Copyright Notice

   Copyright (c) 2015 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    (http://trustee.ietf.org/license-info) in effect on the date of    publication of this document.  Please review these documents    carefully, as they describe your rights and restrictions with respect    to this document.  Code Components extracted from this document must    include Simplified BSD License text as described in Section 4.e of    the Trust Legal Provisions and are provided without warranty as    described in the Simplified BSD License.

 Sparks & Roach               Standards Track                    [Page 1]
 RFC 7647                  Refer Clarifications            September 2015

 Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2    2.  Conventions Used in This Document . . . . . . . . . . . . . .   2    3.  Use of GRUU Is Mandatory  . . . . . . . . . . . . . . . . . .   3    4.  Dialog Reuse Is Prohibited  . . . . . . . . . . . . . . . . .   3    5.  The 202 Response Code Is Deprecated . . . . . . . . . . . . .   4    6.  Security Considerations . ....