Browse Prior Art Database

The Session Initiation Protocol (SIP) Referred-By Mechanism (RFC3892)

IP.com Disclosure Number: IPCOM000031542D
Original Publication Date: 2004-Sep-01
Included in the Prior Art Database: 2004-Sep-29
Document File: 26 page(s) / 53K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Sparks: AUTHOR

Abstract

The Session Initiation Protocol (SIP) REFER method provides a mechanism where one party (the referrer) gives a second party (the referee) an arbitrary URI to reference. If that URI is a SIP URI, the referee will send a SIP request, often an INVITE, to that URI (the refer target). This document extends the REFER method, allowing the referrer to provide information about the REFER request to the refer target using the referee as an intermediary. This information includes the identity of the referrer and the URI to which the referrer referred. The mechanism utilizes S/MIME to help protect this information from a malicious intermediary. This protection is optional, but a recipient may refuse to accept a request unless it is present.

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

Network Working Group                                          R. Sparks

Request for Comments: 3892                                          Xten

Category: Standards Track                                 September 2004

      The Session Initiation Protocol (SIP) Referred-By Mechanism

Status of this Memo

   This document specifies an Internet standards track protocol for the

   Internet community, and requests discussion and suggestions for

   improvements.  Please refer to the current edition of the "Internet

   Official Protocol Standards" (STD 1) for the standardization state

   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).

Abstract

   The Session Initiation Protocol (SIP) REFER method provides a

   mechanism where one party (the referrer) gives a second party (the

   referee) an arbitrary URI to reference.  If that URI is a SIP URI,

   the referee will send a SIP request, often an INVITE, to that URI

   (the refer target).  This document extends the REFER method, allowing

   the referrer to provide information about the REFER request to the

   refer target using the referee as an intermediary.  This information

   includes the identity of the referrer and the URI to which the

   referrer referred.  The mechanism utilizes S/MIME to help protect

   this information from a malicious intermediary.  This protection is

   optional, but a recipient may refuse to accept a request unless it is

   present.

Sparks                      Standards Track                     [Page 1]

RFC 3892             The SIP Referred-By Mechanism        September 2004

Table of Contents

   1.  Overview . . . . . . . . . . . . . . . . . . . . . . . . . . .  2

       1.1.  Requirements Notation  . . . . . . . . . . . . . . . . .  3

   2.  The Referred-By Mechanism  . . . . . . . . . . . . . . . . . .  3

       2.1.  Referrer Behavior  . . . . . . . . . . . . . . . . . . .  4

       2.2.  Referee Behavior . . . . . . . . . . . . . . . . . . . .  4

       2.3.  Refer Target Behavior  . . . . . . . . . . . . . . . . .  5

   3.  The Referred-By Header Field . . . . . . . . . . . . . . . . .  6

   4.  The Referred-By Token  . . . . . . . . . . . . . . . . . . . .  7

       4.1.  Refer Target Inspection of a Referred-By Token . . . . .  8

   5.  The 429 Provide Referrer Identity Error Response . . . . . . .  8

   6.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8

       6.1.  Identifying the Referee in the Referred-by Token . . . . 10

   7.  Examples . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

       7.1.  Basic REFER  . . . . . . . . . . . . . . . . . . ....