Re: [Sip] More general question on S-S-L mode in RPH
Mpierce1@aol.com Wed, 10 November 2004 18:47 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 NAA11867 for <sip-web-archive@ietf.org>; Wed, 10 Nov 2004 13:47:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRxWJ-0001YS-WF for sip-web-archive@ietf.org; Wed, 10 Nov 2004 13:48:40 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxPK-0004dX-LK; Wed, 10 Nov 2004 13:41:26 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CRxKh-0003lC-Rw; Wed, 10 Nov 2004 13:36:41 -0500
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 NAA10716; Wed, 10 Nov 2004 13:36:36 -0500 (EST)
From: Mpierce1@aol.com
Received: from imo-d20.mx.aol.com ([205.188.139.136]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CRxLh-0001Iw-DO; Wed, 10 Nov 2004 13:37:42 -0500
Received: from Mpierce1@aol.com by imo-d20.mx.aol.com (mail_out_v37_r3.8.) id t.be.1b89d95a (3924); Wed, 10 Nov 2004 13:36:00 -0500 (EST)
Message-ID: <be.1b89d95a.2ec3b990@aol.com>
Date: Wed, 10 Nov 2004 13:36:00 -0500
Subject: Re: [Sip] More general question on S-S-L mode in RPH
To: jgunn6@csc.com, jmpolk@cisco.com
MIME-Version: 1.0
X-Mailer: 6.0 for Windows XP sub 10500
X-Spam-Score: 0.8 (/)
X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8
Cc: rkaczmarek@csc.com, dpado@csc.com, snegash@csc.com, sip@ietf.org, sip-bounces@ietf.org, nyquetek@msn.com, dberg3@csc.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>
Content-Type: multipart/mixed; boundary="===============1527209579=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: b7b9551d71acde901886cc48bfc088a6
In a message dated 11/10/2004 11:00:13 AM Eastern Standard Time, jgunn6@csc.com writes: > For instance a SIP element could be "strict" for namespace A and > "semi-strict" for namespace B. > This doesn't make sense. Part of the use of the mode still is to determine what to do when the receiving element does not understand the namespace, that is, it thinks it needs a namespace but doesn't see one it understands. (This was the only use of the mode in version -04.) Becasue of this, the mode must be a function of the domain, or rather, of every element in the domain. It is not associated with a namespace. Each element must know what mode it is supposed to operate in independent of what namespace is being used. Version -04 was based on an element or UAS operating in a specific mode and did not try to associate the mode with the namespace. This technical change is another reason why I believe that version -05 should be rejected. Mike
_______________________________________________ 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] More general question on S-S-L mode in RPH Janet P Gunn
- Re: [Sip] More general question on S-S-L mode in … James M. Polk
- Re: [Sip] More general question on S-S-L mode in … Mpierce1