[Sip] Contradictory Semantics header againest Join header in SIP
"suryakanta mandal" <suryakanta.mandal@gmail.com> Mon, 28 January 2008 21:11 UTC
Return-path: <sip-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1JJbGp-0005dQ-Bx; Mon, 28 Jan 2008 16:11:59 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JHvwd-00070Y-N2 for sip-confirm+ok@megatron.ietf.org; Thu, 24 Jan 2008 01:52:15 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1JHvwd-00070O-DB for sip@ietf.org; Thu, 24 Jan 2008 01:52:15 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1JHuvP-0007XW-Mx for sip@ietf.org; Thu, 24 Jan 2008 00:46:55 -0500
Received: from an-out-0708.google.com ([209.85.132.247]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1JHuvP-00079q-Aw for sip@ietf.org; Thu, 24 Jan 2008 00:46:55 -0500
Received: by an-out-0708.google.com with SMTP id d11so44756and.122 for <sip@ietf.org>; Wed, 23 Jan 2008 21:46:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=NQLbHsiIM473KrIBlEfQa19P45NRDj4rtZ1U85HtrV8=; b=c5fZSx5Nwd+g3dQQmX3fWPhYQkhoMdp3f0iukOmv98dEmfNh6DgzR3kWKGoWEGM8ClvC9aoRCEC9Jt3cvx426K0qsXXG0TS2rJ3Bom7NW6doJO0uLRyodxmJlt2z9zA5U8ai8uzos61/LObtS8hR7MDYg2gGlltOCjMIjhKj3eA=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=xoojGA9S/Y+96GN3uq6UzapMTnHHBZkY74qrBL4XTyW/pC33AN/IJ5uYspP0UPKLEan+4q3O/VWaV1iGDRi6BVK+/ml2RuPTIHpU7fRKOgO3uLcGl9OS5Gd5/Lqk3udcOeAWF2CRfj/GVjlmPeSj+ukZtysnSDsi4NZf8acrzfM=
Received: by 10.100.216.3 with SMTP id o3mr596827ang.28.1201153614995; Wed, 23 Jan 2008 21:46:54 -0800 (PST)
Received: by 10.100.9.5 with HTTP; Wed, 23 Jan 2008 21:46:54 -0800 (PST)
Message-ID: <24e80f870801232146v69f42461sbcdeef6787f4ae3b@mail.gmail.com>
Date: Thu, 24 Jan 2008 11:16:54 +0530
From: suryakanta mandal <suryakanta.mandal@gmail.com>
To: sip@ietf.org, Sip-implementors@lists.cs.columbia.edu
MIME-Version: 1.0
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199
X-TMDA-Confirmed: Thu, 24 Jan 2008 01:52:15 -0500
X-Mailman-Approved-At: Mon, 28 Jan 2008 16:11:57 -0500
Cc:
Subject: [Sip] Contradictory Semantics header againest Join header in SIP
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>
Errors-To: sip-bounces@ietf.org
Hi, I have a query about the contradictory semantics header againest Join header. In RFC 3911 it's saying the following "The Join header has specific call control semantics. If both a Join header field and another header field with contradictory semantics (for example a Replaces [8] header field) are present in a request, the request MUST be rejected with a 400 "Bad Request" response. " here it specifies that Replace is the one Contradictory header for join but I seek to know that who else header has the contradictory semantics againest Join header for an INVITE _______________________________________________ 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] Contradictory Semantics header againest Joi… suryakanta mandal