Protocol Action: 'The SIP Referred-By Mechanism' to Proposed Standard

The IESG <iesg-secretary@ietf.org> Tue, 23 March 2004 22:04 UTC

Received: from asgard.ietf.org (asgard.ietf.org [10.27.6.40]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06079 for <ietf-announce-archive@odin.ietf.org>; Tue, 23 Mar 2004 17:04:48 -0500 (EST)
Received: from majordomo by asgard.ietf.org with local (Exim 4.14) id 1B5tpz-0000jT-7R for ietf-announce-list@asgard.ietf.org; Tue, 23 Mar 2004 16:53:31 -0500
Received: from ietf.org ([10.27.2.28]) by asgard.ietf.org with esmtp (Exim 4.14) id 1B5tm8-0000Ih-WB for all-ietf@asgard.ietf.org; Tue, 23 Mar 2004 16:49:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA04616 for <all-ietf@ietf.org>; Tue, 23 Mar 2004 16:49:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 1B5tm7-00075Q-00 for all-ietf@ietf.org; Tue, 23 Mar 2004 16:49:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1B5tlC-00071L-00 for all-ietf@ietf.org; Tue, 23 Mar 2004 16:48:34 -0500
Received: from optimus.ietf.org ([132.151.1.19]) by ietf-mx with esmtp (Exim 4.12) id 1B5tkH-0006wo-00; Tue, 23 Mar 2004 16:47:37 -0500
Received: from nobody by optimus.ietf.org with local (Exim 4.20) id 1B5tkI-0001zO-Ub; Tue, 23 Mar 2004 16:47:38 -0500
X-test-idtracker: no
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce:;
Cc: Internet Architecture Board <iab@iab.org>, RFC Editor <rfc-editor@rfc-editor.org>, sip mailing list <sip@ietf.org>, sip chair <dean.willis@softarmor.com>, sip chair <rohan@cisco.com>
Subject: Protocol Action: 'The SIP Referred-By Mechanism' to Proposed Standard
Message-Id: <E1B5tkI-0001zO-Ub@optimus.ietf.org>
Date: Tue, 23 Mar 2004 16:47:38 -0500
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=0.2 required=5.0 tests=AWL autolearn=no version=2.60
Sender: owner-ietf-announce@ietf.org
Precedence: bulk

The IESG has approved the following document:

- 'The SIP Referred-By Mechanism '
   <draft-ietf-sip-referredby-05.txt> as a Proposed Standard

This document is the product of the Session Initiation Protocol Working 
Group. 

The IESG contact persons are Allison Mankin and Jon Peterson.

Technical Summary

   The 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.

   The REFER method is specified in RFC 3515, which describes a general
    set of security considerations in addition to those particular to 
   Referred-By.

 
Working Group Summary

   The Working Group strongly supported the advancement of Referred-By,
    once it was split out of the REFER document into the present design.
 
 
 
Protocol Quality
 
  There was a large amount of working group review of Referred-by, which
   resulted in its being split out of the original REFER method document
   and the development of this mechanism and the Authentication ID Body
   (under review at the same time) on which it depends.  There were no 
   dissenting comments during WG Last Call or IETF Last Call.  The
  document was reviewed for the IESG by Allison Mankin.