Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (1)

"James M. Polk" <jmpolk@cisco.com> Mon, 15 November 2004 19:10 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 OAA21874 for <sip-web-archive@ietf.org>; Mon, 15 Nov 2004 14:10:35 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTmHK-0005Zm-NC for sip-web-archive@ietf.org; Mon, 15 Nov 2004 14:12:43 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTmD4-0006WP-As; Mon, 15 Nov 2004 14:08:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTm70-00054T-Qi for sip@megatron.ietf.org; Mon, 15 Nov 2004 14:02:06 -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 OAA20952 for <sip@ietf.org>; Mon, 15 Nov 2004 14:02:01 -0500 (EST)
Received: from sj-iport-1-in.cisco.com ([171.71.176.70] helo=sj-iport-1.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTm92-0005L6-R6 for sip@ietf.org; Mon, 15 Nov 2004 14:04:10 -0500
Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-1.cisco.com with ESMTP; 15 Nov 2004 11:16:18 -0800
X-BrightmailFiltered: true
Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id iAFJ1Iw0027660; Mon, 15 Nov 2004 11:01:19 -0800 (PST)
Received: from jmpolk-w2k01.diablo.cisco.com (ssh-sjc-1.cisco.com [171.68.225.134]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA07200; Mon, 15 Nov 2004 11:01:19 -0800 (PST)
Message-Id: <4.3.2.7.2.20041115125332.03798ee8@localhost>
X-Sender: jmpolk@localhost
X-Mailer: QUALCOMM Windows Eudora Version 4.3.2
Date: Mon, 15 Nov 2004 13:01:25 -0600
To: Mpierce1@aol.com, An.Nguyen@ncs.gov, coreya@nortelnetworks.com, sip@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
Subject: Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (1)
In-Reply-To: <1ca.2ca0df9e.2ec67586@aol.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 1.1 (+)
X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228
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: 1.1 (+)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f

Where is "mapping between namespaces" specified in the document now?

I do not believe there is such a sentence/comment/statement, and there 
should not be one, so why was this brought up?

At 03:22 PM 11/12/2004 -0500, Mpierce1@aol.com wrote:
>In a message dated 11/12/2004 11:58:14 AM Eastern Standard Time, 
>An.Nguyen@ncs.gov writes:
>
>
>>Can we just add a sentence to the draft saying mapping between namespaces 
>>is out of scope and it should be addressed separately?
>
>
>Yes, such a statement would be fine, but it should be along with a 
>statement that all interrelationship between namespaces is out of scope.
>
>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


cheers,
James

                                *******************
                 Truth is not to be argued... it is to be presented


_______________________________________________
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