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

David R Oran <oran@cisco.com> Mon, 15 November 2004 19:54 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 OAA25543 for <sip-web-archive@ietf.org>; Mon, 15 Nov 2004 14:54:44 -0500 (EST)
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CTmy4-0006cs-Eu for sip-web-archive@ietf.org; Mon, 15 Nov 2004 14:56:53 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTmq4-0004lR-9Z; Mon, 15 Nov 2004 14:48:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CTmly-0003ka-3N for sip@megatron.ietf.org; Mon, 15 Nov 2004 14:44:22 -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 OAA24846 for <sip@ietf.org>; Mon, 15 Nov 2004 14:44:20 -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 1CTmnx-0006Os-Bh for sip@ietf.org; Mon, 15 Nov 2004 14:46:30 -0500
Received: from sj-core-5.cisco.com (171.71.177.238) by sj-iport-1.cisco.com with ESMTP; 15 Nov 2004 11:58:33 -0800
X-BrightmailFiltered: true
Received: from imail.cisco.com (imail.cisco.com [128.107.200.91]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id iAFJhcOx017098; Mon, 15 Nov 2004 11:43:39 -0800 (PST)
Received: from [10.32.245.156] (stealth-10-32-245-156.cisco.com [10.32.245.156]) by imail.cisco.com (8.12.11/8.12.10) with SMTP id iAFJi3ip002639; Mon, 15 Nov 2004 11:44:04 -0800
In-Reply-To: <4.3.2.7.2.20041115125332.03798ee8@localhost>
References: <4.3.2.7.2.20041115125332.03798ee8@localhost>
Mime-Version: 1.0 (Apple Message framework v619)
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Message-Id: <A2F773DC-373E-11D9-97C5-000A95C73842@cisco.com>
Content-Transfer-Encoding: 7bit
From: David R Oran <oran@cisco.com>
Subject: Re: [Sip] -resource-priority-05.txt: Comments and Recommendations (1)
Date: Mon, 15 Nov 2004 14:43:34 -0500
To: "James M. Polk" <jmpolk@cisco.com>
X-Mailer: Apple Mail (2.619)
IIM-SIG: v:"1"; h:"imail.cisco.com"; d:"cisco.com"; z:"home"; m:"krs"; t:"1100547844.763217"; x:"432200"; a:"rsa-sha1"; b:"nofws:2233"; e:"Iw=="; n:"sQYarK2E51MdcTiUqeif3F7cWdxIfoCiXhdfb9vD5ee/j0jXL15gbFxF2pXIw" "eAblu0N6XAgK7k+wrbr7bQDJaCDqOmzqpRUBjIRQAXQ7NzadpmR3pUL6wxaRU" "tW+c43sl9jC50Qg1sXHpPjt8Y+Y16ioyQAQAdSunM4YhevURc="; s:"YmlDSla9F6H+1XCIjXofKsKCDnZM6BCpYjnDHmR8CS9D6ecpyIihrZhUeIPFu" "HrT6aFRFz7gpdzJZ9VJGtbRp95JJ6Zv7+AQFhkdH7u4Lc3pW7oIKkdUOIH57H" "1p47rmsN4mys9Mhb9kVTHoFAigkajzVtAkkwZx8hHPRSRox3w="; c:"From: David R Oran <oran@cisco.com>"; c:"Subject: Re: [Sip] -resource-priority-05.txt: Comments and Recommendat" "ions (1)"; c:"Date: Mon, 15 Nov 2004 14:43:34 -0500"
IIM-VERIFY: s:"y"; v:"y"; r:"60"; h:"imail.cisco.com"; c:"message from imail.cisco.com verified; "
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e8a67952aa972b528dd04570d58ad8fe
Content-Transfer-Encoding: 7bit
Cc: An.Nguyen@ncs.gov, sip@ietf.org, Mpierce1@aol.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: 41c17b4b16d1eedaa8395c26e9a251c4
Content-Transfer-Encoding: 7bit

On Nov 15, 2004, at 2:01 PM, James M. Polk wrote:

> 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?
>
If somebody reads the doc expecting to see something and it isn't 
there, two possibilities obtain:
(a) they don't "get it"
(b) a reasonable person might think that function a natural one to be 
handled, but that's not the approach we took in designing this beastie.

The case at hand seems closer to (b) than (a), so I see no harm in 
saying that namespaces are orthogonal as far as the specification is 
concerned, and while it may be possible to map behavior between 
namespaces, this document doesn't tell you how, and that's intentional.

Dave.

> 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
>
David R. Oran
Cisco Fellow
Cisco Systems
7 Ladyslipper Lane
Acton, MA 01720 USA
Tel: +1 978 264 2048
Email: oran@cisco.com


_______________________________________________
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