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

"DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com> Mon, 05 November 2007 16:36 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 1Ip4vo-00017o-Af; Mon, 05 Nov 2007 11:36:08 -0500
Received: from sip by megatron.ietf.org with local (Exim 4.43) id 1Ip4vm-00014i-Km for sip-confirm+ok@megatron.ietf.org; Mon, 05 Nov 2007 11:36:06 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Ip4vm-00013k-AZ for sip@ietf.org; Mon, 05 Nov 2007 11:36:06 -0500
Received: from ihemail3.lucent.com ([135.245.0.37]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Ip4vl-0002cG-1m for sip@ietf.org; Mon, 05 Nov 2007 11:36:06 -0500
Received: from ilexp02.ndc.lucent.com (h135-3-39-2.lucent.com [135.3.39.2]) by ihemail3.lucent.com (8.13.8/IER-o) with ESMTP id lA5GZYqm018866; Mon, 5 Nov 2007 10:36:04 -0600 (CST)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp02.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 5 Nov 2007 10:36:03 -0600
Received: from DEEXC1U01.de.lucent.com ([135.248.187.26]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 5 Nov 2007 17:36:00 +0100
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 17:36:00 +0100
Message-ID: <5D1A7985295922448D5550C94DE2918001886FC0@DEEXC1U01.de.lucent.com>
In-Reply-To: <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/eqrZJnyHBzIRGCduFxXB59HMQAwCWGwAAGfeGA=
References: <680808427CF931459462C3D78CB5EC607C6863@EXVS02.nasstar-t1.net>
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: Attila Sipos <attila.sipos@vegastream.com>, sip@ietf.org
X-OriginalArrivalTime: 05 Nov 2007 16:36:00.0668 (UTC) FILETIME=[F30D45C0:01C81FC9]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.37
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1
Cc:
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

I don't think it is explicitly covered in the RFC 4412, but there are
clear pointers to what needs to be done.

There needs to be agreement between the administrative domains as to
what is passed across the boundaries between the adminstrative domains.
This could take a number of forms:

-	the header is not passed at all because there is no agreement
between the administrations. Any priority handling only exists in the
source domain.
-	the header is passed and the two administrations agree to use
the same namespace in a compatible fashion.
-	by agreement, different namespaces are conveyed by the two
adminstrations, and two Resource-Priority headers are included that are
each used by the owning administration. 

Regards

Keith

> -----Original Message-----
> From: Attila Sipos [mailto:attila.sipos@vegastream.com] 
> Sent: Monday, November 05, 2007 3:14 PM
> To: sip@ietf.org
> Subject: RE: [Sip] namespaces in RFC 4411,4412 and 
> draft-ietf-sip-rph-new-namespaces-00
> 
> 
> 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
> 


_______________________________________________
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