Re: [Sip] I-D Action:draft-ietf-sip-rph-new-namespaces-02.txt

"DRAGE, Keith \(Keith\)" <drage@alcatel-lucent.com> Wed, 27 February 2008 19:05 UTC

Return-Path: <sip-bounces@ietf.org>
X-Original-To: ietfarch-sip-archive@core3.amsl.com
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 7F9A228C92A; Wed, 27 Feb 2008 11:05:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.027
X-Spam-Level:
X-Spam-Status: No, score=-1.027 tagged_above=-999 required=5 tests=[AWL=-0.590, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_ORG=0.611, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gl93iGBVw1o8; Wed, 27 Feb 2008 11:05:42 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id B23BB28C395; Wed, 27 Feb 2008 11:05:20 -0800 (PST)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 470F428C32B for <sip@core3.amsl.com>; Wed, 27 Feb 2008 11:05:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KzsfwFA7lk6E for <sip@core3.amsl.com>; Wed, 27 Feb 2008 11:05:18 -0800 (PST)
Received: from ihemail1.lucent.com (ihemail1.lucent.com [135.245.0.33]) by core3.amsl.com (Postfix) with ESMTP id 5DD8D28C323 for <sip@ietf.org>; Wed, 27 Feb 2008 11:02:20 -0800 (PST)
Received: from ilexp03.ndc.lucent.com (h135-3-39-50.lucent.com [135.3.39.50]) by ihemail1.lucent.com (8.13.8/IER-o) with ESMTP id m1RJ1vFs025673; Wed, 27 Feb 2008 13:01:58 -0600 (CST)
Received: from DEEXP01.de.lucent.com ([135.248.187.65]) by ilexp03.ndc.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 27 Feb 2008 13:01:57 -0600
Received: from DEEXC1U01.de.lucent.com ([135.248.187.20]) by DEEXP01.de.lucent.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 27 Feb 2008 20:01:54 +0100
X-MIMEOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Date: Wed, 27 Feb 2008 20:01:53 +0100
Message-ID: <5D1A7985295922448D5550C94DE2918001CB019C@DEEXC1U01.de.lucent.com>
In-Reply-To: <XFE-SJC-212GpaoG1VR00004ef4@xfe-sjc-212.amer.cisco.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Sip] I-D Action:draft-ietf-sip-rph-new-namespaces-02.txt
Thread-index: Ach3c2lnw7o0pmZSQ6+083GFB/sVNAB/4bGQ
References: <20080224054501.90B6A3A6A07@core3.amsl.com><200802250404.m1P44eZm023626@dragon.ariadne.com> <XFE-SJC-212GpaoG1VR00004ef4@xfe-sjc-212.amer.cisco.com>
From: "DRAGE, Keith (Keith)" <drage@alcatel-lucent.com>
To: "James M. Polk" <jmpolk@cisco.com>, Dale.Worley@comcast.net, sip@ietf.org
X-OriginalArrivalTime: 27 Feb 2008 19:01:54.0936 (UTC) FILETIME=[38180F80:01C87973]
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.33
Subject: Re: [Sip] I-D Action:draft-ietf-sip-rph-new-namespaces-02.txt
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.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://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org

Rather than "for the use of" I would prefer "to meet the requirements
of".

The usage of any namespace is a private matter between the operator of
the SIP entities, and the user. The fact that DISA requested such a set
of namespaces does not reserve usage to that particular organisation.
Rather it defines a particular set of priority and preemption schemes
that anyone can use.

Regards

Keith 

> -----Original Message-----
> From: sip-bounces@ietf.org [mailto:sip-bounces@ietf.org] On 
> Behalf Of James M. Polk
> Sent: Monday, February 25, 2008 5:57 AM
> To: Dale.Worley@comcast.net; sip@ietf.org
> Subject: Re: [Sip] I-D Action:draft-ietf-sip-rph-new-namespaces-02.txt
> 
> At 10:04 PM 2/24/2008, Dale.Worley@comcast.net wrote:
> >            Title           : IANA Registration of New Session
> >                              Initiation Protocol (SIP)
> >                              Resource-Priority Namespaces
> >            Author(s)       : J. Polk
> >            Filename        : 
> draft-ietf-sip-rph-new-namespaces-02.txt
> >            Pages           : 7
> >            Date            : 2008-02-23
> >
> >    Abstract:
> >
> >    This document creates additional Session Initiation Protocol
> >    Resource-Priority namespaces, and places these namespaces in the
> >    IANA register.
> >
> >As an editorial matter, can the abstract be made less vague? 
>  Such as 
> >mentioning that it creates a set of namespaces for the use of the US 
> >Defense Information Systems Agency...
> 
> well, at least I didn't overstate things...  ;-)
> 
> I can change this if you want me to
> 
> 
> >Dale
> >_______________________________________________
> >Sip mailing list  http://www.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  http://www.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://www.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