Re: [sip]Join header syntax related to RFC2543
Dean Willis <dean.willis@softarmor.com> Thu, 23 September 2004 15:21 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 LAA22295 for <sip-web-archive@ietf.org>; Thu, 23 Sep 2004 11:21:06 -0400 (EDT)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVVv-0001rf-M6 for sip-web-archive@ietf.org; Thu, 23 Sep 2004 11:28:11 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAV9x-0004Vi-9v; Thu, 23 Sep 2004 11:05:25 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CAV9B-00049N-1K for sip@megatron.ietf.org; Thu, 23 Sep 2004 11:04:38 -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 LAA20775 for <sip@ietf.org>; Thu, 23 Sep 2004 11:04:34 -0400 (EDT)
Received: from [206.176.144.210] (helo=kevlar.softarmor.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CAVFo-0001Sz-SL for sip@ietf.org; Thu, 23 Sep 2004 11:11:39 -0400
Received: from [127.0.0.1] (kevlar.softarmor.com [127.0.0.1]) (authenticated bits=0) by kevlar.softarmor.com (8.12.11/8.12.11) with ESMTP id i8NF3Y8u021630 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Sep 2004 10:03:40 -0500
Message-ID: <4152E5C6.4020905@softarmor.com>
Date: Thu, 23 Sep 2004 10:03:34 -0500
From: Dean Willis <dean.willis@softarmor.com>
User-Agent: Mozilla Thunderbird 0.8 (X11/20040913)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: 石川 愛 <ishikame@alpha.co.jp>
Subject: Re: [sip]Join header syntax related to RFC2543
References: <20040902001944.8D2B93D0FB@ms2.alpha.co.jp>
In-Reply-To: <20040902001944.8D2B93D0FB@ms2.alpha.co.jp>
Content-Type: text/plain; charset="ISO-2022-JP"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b
Content-Transfer-Encoding: 7bit
Cc: sip@ietf.org, rohan@ekabal.com, dpetrie@pingtel.com
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>
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa
Content-Transfer-Encoding: 7bit
石川 愛 wrote: > Hi, > > I have a question associated with draft-ietf-sip-join-03.txt > and draft-ietf-sip-replaces-05.txt. > > > Join document at the tail of Section 7.1 saids: > > For compatibility with dialogs initiated by RFC2543 [11] > compliant UAs, a tag of zero matches both tags of zero and null tags > > Examples: > Join: 87134@192.0.2.23;to-tag=24796;from-tag=0 > > and also said at section 6.1 in Replaces document. > > > > In inverse case, i.e., there is a dialog initiated by RFC3261 > compliant UAs to RFC2543 compliant UAs, is the same? > In other words, there is a possibility that there is > no to-tag in this case. So we can as below? > > For example, > Join: 12345@192.1.2.3;to-tag=0;from-tag=56789 > > > In this example, does tag of zero matches both tags of zero > and null tags? And also for Replaces? That's my reading of the doc, although in retrospect the wording at the end of joing-7.1 is particularly clumsy, and I wish somebody had noticed sooner. I'd like to ask the authors to clarify here, and perhaps we can get an errata entry with that clarification. -- Dean _______________________________________________ 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
- Re: [sip]Join header syntax related to RFC2543 Dean Willis
- Re: [sip]Join header syntax related to RFC2543 Rohan Mahy