Re: [sipcore] New ID posted asking for two more RPH namespaces

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Wed, 13 July 2011 16:22 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: sipcore@ietfa.amsl.com
Delivered-To: sipcore@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C903021F8753 for <sipcore@ietfa.amsl.com>; Wed, 13 Jul 2011 09:22:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.216
X-Spam-Level:
X-Spam-Status: No, score=-106.216 tagged_above=-999 required=5 tests=[AWL=0.033, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aqaTpgNRMKBh for <sipcore@ietfa.amsl.com>; Wed, 13 Jul 2011 09:22:05 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [62.23.212.56]) by ietfa.amsl.com (Postfix) with ESMTP id C982721F8752 for <sipcore@ietf.org>; Wed, 13 Jul 2011 09:22:04 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p6DGLuhw006339 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Wed, 13 Jul 2011 18:21:56 +0200
Received: from FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com ([135.120.45.47]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Wed, 13 Jul 2011 18:21:57 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: "James M. Polk" <jmpolk@cisco.com>, "sipcore@ietf.org" <sipcore@ietf.org>
Date: Wed, 13 Jul 2011 18:21:54 +0200
Thread-Topic: [sipcore] New ID posted asking for two more RPH namespaces
Thread-Index: Acw9stoS8qDG1cuvTdeT0bBkuy8pEADxZKkA
Message-ID: <EDC0A1AE77C57744B664A310A0B23AE21FC9342C@FRMRSSXCHMBSC3.dc-m.alcatel-lucent.com>
References: <201107082105.p68L5pfh032286@mtv-core-2.cisco.com>
In-Reply-To: <201107082105.p68L5pfh032286@mtv-core-2.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Cc: "Adarsh Kaithal (akaithal)" <akaithal@cisco.com>, Jack Klecha <jaklecha@cisco.com>
Subject: Re: [sipcore] New ID posted asking for two more RPH namespaces
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Jul 2011 16:22:05 -0000

The way this reads it gives the impression that these are not defined for priority purposes but for creating closed user groups. Assuming this is not the case, maybe you can add some text that these are used only for priority (and preemption) of individual groups within that group.

Also, given that it appears that the intent is for all these namespaces to coexist, maybe you need a few words on that and how that is handled. Can one namespace, defined by this document, preempt another, defined by this document, or is that precluded?

Regards

Keith


> -----Original Message-----
> From: sipcore-bounces@ietf.org [mailto:sipcore-bounces@ietf.org] On Behalf
> Of James M. Polk
> Sent: 08 July 2011 22:06
> To: sipcore@ietf.org
> Cc: Adarsh Kaithal (akaithal); Jack Klecha
> Subject: [sipcore] New ID posted asking for two more RPH namespaces
> 
> SIPCORE
> 
> A New Internet-Draft is available from the on-line Internet-Drafts
> directories.
> 
> 	Title           : IANA Registration of the UC and CUC Session
> Initiation Protocol (SIP) Resource-Priority Namespaces
> 	Author(s)       : Adarsh Kaithal
>                           James Polk
>                           Jack Klecha
> 	Filename        : draft-kaithal-sipcore-rph-cuc-uc-namespaces-00.txt
> 	Pages           : 5
> 	Date            : 2011-07-04
> 
>     This document creates two new Session Initiation Protocol (SIP)
>     Resource-Priority namespaces, and places these namespaces in the
>     IANA registry.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-kaithal-sipcore-rph-cuc-uc-
> namespaces-00.txt
> 
> This is a simple 5 page draft requesting two new RPH namespaces be
> IANA registered. There are no new semantics involved, and uses RFC
> 5478 as a template for much of the text and all of the security
> considerations.
> 
> Comments are appreciated
> 
> James, Adarsh and Jack
> 
> _______________________________________________
> sipcore mailing list
> sipcore@ietf.org
> https://www.ietf.org/mailman/listinfo/sipcore