IETF Logo Mail Archive

[sipcore] Proxy-feature use-case: forking capability [was: Draft new version: draft-holmberg-sipcore-proxy-feature]

Christer Holmberg <christer.holmberg@ericsson.com> Thu, 27 January 2011 16:04 UTC

Return-Path: <christer.holmberg@ericsson.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4415D3A682A for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 08:04:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.466
X-Spam-Level:
X-Spam-Status: No, score=-6.466 tagged_above=-999 required=5 tests=[AWL=0.133, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mCxHDUVJqa1m for <sipcore@core3.amsl.com>; Thu, 27 Jan 2011 08:04:50 -0800 (PST)
Received: from mailgw10.se.ericsson.net (mailgw10.se.ericsson.net [193.180.251.61]) by core3.amsl.com (Postfix) with ESMTP id 373593A63CB for <sipcore@ietf.org>; Thu, 27 Jan 2011 08:04:50 -0800 (PST)
X-AuditID: c1b4fb3d-b7b89ae0000036a3-d2-4d419859d34b
Received: from esessmw0184.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw10.se.ericsson.net (Symantec Mail Security) with SMTP id 21.EE.13987.958914D4; Thu, 27 Jan 2011 17:07:53 +0100 (CET)
Received: from ESESSCMS0356.eemea.ericsson.se ([169.254.1.59]) by esessmw0184.eemea.ericsson.se ([153.88.115.81]) with mapi; Thu, 27 Jan 2011 17:07:53 +0100
From: Christer Holmberg <christer.holmberg@ericsson.com>
To: "sipcore@ietf.org" <sipcore@ietf.org>
Date: Thu, 27 Jan 2011 17:07:48 +0100
Thread-Topic: Proxy-feature use-case: forking capability [was: Draft new version: draft-holmberg-sipcore-proxy-feature]
Thread-Index: Acu+O5nBl5aHToRzQN6gM0EPa6zplAAAGg0g
Message-ID: <7F2072F1E0DE894DA4B517B93C6A0585194427B18D@ESESSCMS0356.eemea.ericsson.se>
References: <7F2072F1E0DE894DA4B517B93C6A058502B84084@ESESSCMS0356.eemea.ericsson.se> <BDBFB6CE314EDF4CB80404CACAEFF5DE07C6C68C@XCH02DFW.rim.net>, <4D3A2C3D.10508@cisco.com> <7F2072F1E0DE894DA4B517B93C6A0585194414F717@ESESSCMS0356.eemea.ericsson.se> <4D3EEC64.2080302@nostrum.com> <7F2072F1E0DE894DA4B517B93C6A05851944155A13@ESESSCMS0356.eemea.ericsson.se> <4D3F2365.2070504@nostrum.com> <7F2072F1E0DE894DA4B517B93C6A0585194427B044@ESESSCMS0356.eemea.ericsson.se> <4D419713.7030000@nostrum.com>
In-Reply-To: <4D419713.7030000@nostrum.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: AAAAAA==
Subject: [sipcore] Proxy-feature use-case: forking capability [was: Draft new version: draft-holmberg-sipcore-proxy-feature]
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 27 Jan 2011 16:04:51 -0000

Hi,

One general use-case that I have been thinking about is a feature tag indicating 
forking capability.

Now, such indicator as such might not be very useful, but the feature 
tag could also have values indicating what kind of forking has taken 
place. I think that could be useful information in issues related to 
forking, e.g. decissions regarding early media etc.

For example:

Record-Route: sip:myProxy.com;forking-para=4 

(4 here indicates how many parallel forks have been created)

Regards,

Christer

v2.23.0 | Report a Bug | By Email