[Sip] Join header (draft-ietf-sip-join-03.txt) unnecessary?
"Christian Jansson" <christian.jansson@hotsip.com> Thu, 21 October 2004 14:25 UTC
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA05037 for <sip-web-archive@ietf.org>; Thu, 21 Oct 2004 10:25:13 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKe55-0004HN-8m for sip-web-archive@ietf.org; Thu, 21 Oct 2004 10:38:19 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKdkF-0005cj-NC; Thu, 21 Oct 2004 10:16:47 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CKdZg-0002Dx-Jl for sip@megatron.ietf.org; Thu, 21 Oct 2004 10:05:52 -0400
Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA01430 for <sip@ietf.org>; Thu, 21 Oct 2004 10:05:50 -0400 (EDT)
Received: from [62.119.82.41] (helo=mailserver.hotsip.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CKdm8-0003bQ-Qf for sip@ietf.org; Thu, 21 Oct 2004 10:18:55 -0400
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Date: Thu, 21 Oct 2004 16:05:07 +0200
Message-ID: <B7192C0D8D60754DADA9E22294C57369528E43@mailserver.hotsip.com>
Thread-Topic: Join header (draft-ietf-sip-join-03.txt) unnecessary?
Thread-Index: AcS3dqfKJkX6MDJCQd6VWtE6hauJPw==
From: Christian Jansson <christian.jansson@hotsip.com>
To: sip@ietf.org
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 932cba6e0228cc603da43d861a7e09d8
Subject: [Sip] Join header (draft-ietf-sip-join-03.txt) unnecessary?
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============2030059498=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56
Why do we need a Join header to be able to indicate that we want to join an ongoing session? Wouldn't it be enough to, for the party that wants to join, actually use the call-id for the session when sending the join-INVITE? Suppose A and B are in a session with the dialog identified by call-id=12345;tag=A;tag=B. If C now wants to join the session he sends an INVITE to A or B with call-id=12345, from-tag=C, and an empty to-tag. Wouldn't it make more sense that the 2 dialog-ids had some parts in common, that is the call-id, and something that distinguished them, that is the to and from tags? It would be much easier to find the session related messages as they would share the same call-id. Have I missed some essential part of the Join header, or are we just adding something that we could already express easily with what we already have? / Christian Jansson, Hotsip
_______________________________________________ Sip mailing list https://www1.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip
- [Sip] Join header (draft-ietf-sip-join-03.txt) un… Christian Jansson