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

"Attila Sipos" <attila.sipos@vegastream.com> Mon, 05 November 2007 15:15 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 1Ip3fx-00030P-95; Mon, 05 Nov 2007 10:15:41 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Ip3fw-0002zF-24 for sip-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 10:15:40 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip3fv-0002z1-Og for sip@ietf.org; Mon, 05 Nov 2007 10:15:39 -0500
Received: from cluster-f.mailcontrol.com ([85.119.2.190]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ip3ft-0000vS-TQ for sip@ietf.org; Mon, 05 Nov 2007 10:15:39 -0500
Received: from exsmtp01.nasstar-t1.net (exsmtp01.nasstar-t1.net [89.28.233.12]) by rly27f.srv.mailcontrol.com (MailControl) with ESMTP id lA5FFalq011765 for <sip@ietf.org>; Mon, 5 Nov 2007 15:15:36 GMT
Received: from EXVS02.nasstar-t1.net ([10.2.10.105]) by exsmtp01.nasstar-t1.net with Microsoft SMTPSVC(6.0.3790.1830); Mon, 5 Nov 2007 15:14:20 +0000
x-mimeole: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [Sip] namespaces in RFC 4411, 4412 and draft-ietf-sip-rph-new-namespaces-00
Date: Mon, 05 Nov 2007 15:13:44 -0000
Message-ID: <680808427CF931459462C3D78CB5EC607C6863@EXVS02.nasstar-t1.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] namespaces in RFC 4411, 4412 and draft-ietf-sip-rph-new-namespaces-00
Thread-Index: Acge/eqrZJnyHBzIRGCduFxXB59HMQAwCWGw
From: Attila Sipos <attila.sipos@vegastream.com>
To: sip@ietf.org
X-OriginalArrivalTime: 05 Nov 2007 15:14:20.0890 (UTC) FILETIME=[8A8E7BA0:01C81FBE]
X-Scanned-By: MailControl A-08-00-00 (www.mailcontrol.com) on 10.70.0.137
X-Spam-Score: -0.0 (/)
X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002
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

Hi,

I have tried asking these questions on SIP-implementors
but not getting any responses.  Are these silly questions...?




-----Original Message-----
From: sip-implementors-bounces@lists.cs.columbia.edu
[mailto:sip-implementors-bounces@lists.cs.columbia.edu] On Behalf Of
Attila Sipos
Sent: 01 November 2007 08:52
To: sip-implementors@lists.cs.columbia.edu
Subject: [Sip-implementors] namespaces in RFC 4411,4412 and
draft-ietf-sip-rph-new-namespaces-00



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?


Regards,

Attila


_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors

_______________________________________________
Sip-implementors mailing list
Sip-implementors@lists.cs.columbia.edu
https://lists.cs.columbia.edu/cucslists/listinfo/sip-implementors


_______________________________________________
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