Re: [Sip] namespaces in RFC 4411, 4412 and draft-ietf-sip-rph-new-namespaces-00

Dale.Worley@comcast.net Mon, 05 November 2007 22:04 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 1IpA3L-0007LL-CD; Mon, 05 Nov 2007 17:04:15 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1IpA3J-0007KF-FK for sip-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 17:04:13 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IpA3J-0007K7-3x for sip@ietf.org; Mon, 05 Nov 2007 17:04:13 -0500
Received: from qmta05.westchester.pa.mail.comcast.net ([76.96.62.48]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IpA3I-0005w9-Lk for sip@ietf.org; Mon, 05 Nov 2007 17:04:12 -0500
Received: from OMTA01.westchester.pa.mail.comcast.net ([76.96.62.11]) by QMTA05.westchester.pa.mail.comcast.net with smtp id 99L71Y0080EZKEL0004J00; Mon, 05 Nov 2007 22:04:12 +0000
Received: from dragon.ariadne.com ([24.34.79.42]) by OMTA01.westchester.pa.mail.comcast.net with comcast id 9A4B1Y00K0umElk0000000; Mon, 05 Nov 2007 22:04:12 +0000
X-Authority-Analysis: v=1.0 c=1 a=mLbkgN8gmkxEsmXQtfYA:9 a=fimCFBeWoCRH2b9VFyoA:7 a=LsxlQw_QxqmMMc8l_XYZYS61i0AA:4 a=0a1BeuFvlBEA:10 a=tlK-OJsYmR4A:10 a=lNxDZue6IIMA:10 a=CDGxlOTZlHAA:10 a=GDpXhxC-ij4A:10 a=8y7tGHue6YMA:10
Received: from dragon.ariadne.com (dragon.ariadne.com [127.0.0.1]) by dragon.ariadne.com (8.12.8/8.12.8) with ESMTP id lA5M4BSV023216 for <sip@ietf.org>; Mon, 5 Nov 2007 17:04:11 -0500
Received: (from worley@localhost) by dragon.ariadne.com (8.12.8/8.12.8/Submit) id lA5M4Bta023212; Mon, 5 Nov 2007 17:04:11 -0500
Date: Mon, 05 Nov 2007 17:04:11 -0500
Message-Id: <200711052204.lA5M4Bta023212@dragon.ariadne.com>
To: sip@ietf.org
From: Dale.Worley@comcast.net
In-reply-to: <680808427CF931459462C3D78CB5EC607C6863@EXVS02.nasstar-t1.net> (attila.sipos@vegastream.com)
Subject: Re: [Sip] namespaces in RFC 4411, 4412 and draft-ietf-sip-rph-new-namespaces-00
References: <680808427CF931459462C3D78CB5EC607C6863@EXVS02.nasstar-t1.net>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
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

   From: "Attila Sipos" <attila.sipos@vegastream.com>

   Are namespaces just a way to group together different users across
   different DNS domains?

   What if a.com is using namespaces "dsn-000000" to "dsn-000009"
   and b.com is using the same namespaces?
   Then if A@a.com calls B@b.com, wouldn't the namespaces interfere?

   What looks after or checks the namespaces?
   Is it that a proxy knows what everyone's namespace should be?
   So if someone wants to do "UA Preemption" and tries to use a resource
   priority level higher than they should have, then will the domain's
   proxy downgrade it back to the correct permitted level?

The primary thing is that resource-priority namespaces are registered
with IANA (RFC 4412, section 3.1).

Within any administrative domain, if it processes resource-priorities
at all, it will generally sanitize any incoming SIP messages to match
the policy of the domain.  As a default, this means that it is going
to strip any resource-priority identification.  Above that, it may
respect resource-priority identification if the domain has a suitable
working relationsip with the terminal or domain from which the message
is entering -- but that relationship will explicitly or implicitly
define how the resource-priority identifications will be preserved or
transformed at the boundary.

This is pretty much how *any* priority-identification system has to be
operated.

Dale


_______________________________________________
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