Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (1)
Mpierce1@aol.com Tue, 16 November 2004 17:41 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 MAA23085 for <sip-web-archive@ietf.org>; Tue, 16 Nov 2004 12:41:40 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU7N3-00030Y-6m for sip-web-archive@ietf.org; Tue, 16 Nov 2004 12:44:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU75F-0006x0-CO; Tue, 16 Nov 2004 12:25:37 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CU6xv-0004IC-PQ; Tue, 16 Nov 2004 12:18:04 -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 MAA20991; Tue, 16 Nov 2004 12:18:01 -0500 (EST)
From: Mpierce1@aol.com
Received: from imo-d06.mx.aol.com ([205.188.157.38]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CU709-0002Oq-TL; Tue, 16 Nov 2004 12:20:23 -0500
Received: from Mpierce1@aol.com by imo-d06.mx.aol.com (mail_out_v37_r3.8.) id c.1e6.2ef6420a (3924); Tue, 16 Nov 2004 12:17:19 -0500 (EST)
Message-ID: <1e6.2ef6420a.2ecb901f@aol.com>
Date: Tue, 16 Nov 2004 12:17:19 -0500
Subject: Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (1)
To: jmpolk@cisco.com, jgunn6@csc.com, oran@cisco.com
MIME-Version: 1.0
X-Mailer: 6.0 for Windows XP sub 10500
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: An.Nguyen@ncs.gov, sip@ietf.org, sip-bounces@ietf.org
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="===============1307579861=="
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 68ba2b07ef271dba6ee42a93832cfa4c
In a message dated 11/15/2004 11:39:06 PM W. Europe Standard Time, jmpolk@cisco.com writes: > >The .03 draft (and I think also the .04 draft) had a paragraph that said > > "Namespaces do not describe how they relate to other existing > > namespaces, as each namespace is independent of other registrations." > > > >It doesn't seem to be in .05 > > see (the new) section 7.1 about the warnings of multiple namespaces > I don't read anything in 7.1 as saying what the previous versions said. What I think is needed is a very clear statement something like "neither this document nor namespaces specify the interrelationship or interworking between namespaces, such as mapping from one namespace to another at domain boundaries". That was my understanding of the previous agreement. As a result, the first bullet in Section 7.1, which states "There MUST be one order of priorities a SIP element has to process to", while talking about multiple namespaces in a message, seems to be wrong (or misunderstood), since it seems to require something about the relationship. In fact the example following this bullet list is trying to say something about the "acceptable" ways that the SIP element may process multiple namespaces. The part about what is "not acceptable" is not needed. The examples of incorrect order within each individual namespace are not allowed even without multiple namespaces. Since the document should say that it does not address interworking between namespaces, it should not contain this material. I don't know what the second bullet is trying to say. The third bullet is obvious, I thought, according to the rules of SIP. If not, this statement could be worded better. Section 7.1 should be deleted completely and replaced with a single statement something like I proposed above. ( I guess this will start a long series of e-mails on what I find wrong in -05.) Mike Pierce
_______________________________________________ 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] -resource-priority-05.txt: Comments and… Mpierce1
- Re: [Sip] -resource-priority-05.txt: Comments and… Janet P Gunn
- Re: [Sip] -resource-priority-05.txt: Comments and… Mpierce1
- Re: [Sip] -resource-priority-05.txt: Comments and… James M. Polk
- Re: [Sip] -resource-priority-05.txt: Comments and… David R Oran
- Re: [Sip] -resource-priority-05.txt: Comments and… Janet P Gunn
- Re: [Sip] -resource-priority-05.txt: Comments and… James M. Polk
- Re: [Sip] -resource-priority-05.txt: Comments and… Janet P Gunn
- Re: [Sip] -resource-priority-05.txt: Comments and… Mpierce1
- Re: [Sip] -resource-priority-05.txt: Comments and… Janet P Gunn
- Re: [Sip] -resource-priority-05.txt: Comments and… James M. Polk
- RE: [Sip] -resource-priority-05.txt: Comments and… Nguyen, An
- Re: [Sip] -resource-priority-05.txt: Comments and… Mpierce1
- Re: [Sip] -RP-05.txt: section 7.1 and (rough) con… James M. Polk