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

"James M. Polk" <jmpolk@cisco.com> Tue, 26 February 2008 18:46 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 218E83A6D81; Tue, 26 Feb 2008 10:46:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.071
X-Spam-Level:
X-Spam-Status: No, score=-1.071 tagged_above=-999 required=5 tests=[AWL=-0.634, 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 MVClaC7IY1iJ; Tue, 26 Feb 2008 10:46:35 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF41C28C27F; Tue, 26 Feb 2008 10:46:34 -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 9756A28C2A8 for <sip@core3.amsl.com>; Tue, 26 Feb 2008 10:46:33 -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 OxQSf1se2S+h for <sip@core3.amsl.com>; Tue, 26 Feb 2008 10:46:32 -0800 (PST)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id C953D28C1FC for <sip@ietf.org>; Tue, 26 Feb 2008 10:46:32 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-1.cisco.com with ESMTP; 26 Feb 2008 10:46:27 -0800
Received: from sj-core-2.cisco.com (sj-core-2.cisco.com [171.71.177.254]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1QIkQYR014906; Tue, 26 Feb 2008 10:46:26 -0800
Received: from xbh-sjc-211.amer.cisco.com (xbh-sjc-211.cisco.com [171.70.151.144]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id m1QIk7RW018422; Tue, 26 Feb 2008 18:46:26 GMT
Received: from xfe-sjc-211.amer.cisco.com ([171.70.151.174]) by xbh-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Feb 2008 10:46:21 -0800
Received: from jmpolk-wxp.cisco.com ([171.70.229.148]) by xfe-sjc-211.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Tue, 26 Feb 2008 10:46:20 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Tue, 26 Feb 2008 12:46:18 -0600
To: Dale.Worley@comcast.net, sip@ietf.org
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <200802252311.m1PNBxuu007876@dragon.ariadne.com>
References: <20080224054501.90B6A3A6A07@core3.amsl.com> <200802250404.m1P44eZm023626@dragon.ariadne.com> <XFE-SJC-212GpaoG1VR00004ef4@xfe-sjc-212.amer.cisco.com> <200802252311.m1PNBxuu007876@dragon.ariadne.com>
Mime-Version: 1.0
Message-ID: <XFE-SJC-2113zrwz4kg000054c9@xfe-sjc-211.amer.cisco.com>
X-OriginalArrivalTime: 26 Feb 2008 18:46:20.0645 (UTC) FILETIME=[E0CCD150:01C878A7]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2062; t=1204051586; x=1204915586; c=relaxed/simple; s=sjdkim2002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=jmpolk@cisco.com; z=From:=20=22James=20M.=20Polk=22=20<jmpolk@cisco.com> |Subject:=20Re=3A=20[Sip]=20I-D=20Action=3Adraft-ietf-sip-r ph-new-namespaces-02.txt |Sender:=20; bh=jm1RHv5jZzvyxXRPRkBCXaqSNik+jPJoNkQooicxB+4=; b=qCexFw4Ttp39KM1K6KSN+Ayv4OM/vpTvqamo+Nj53FO+/UvwUgHWNkcHJi 5Sqw+ZLC91YfPgaQZJNbPLt1NEGbtasxeYTKe0QGRGQZup3agCFu4G77C6yH hU9+1dB3aL;
Authentication-Results: sj-dkim-2; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
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: <http://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: <http://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

At 05:11 PM 2/25/2008, Dale.Worley@comcast.net wrote:
>    From: "James M. Polk" <jmpolk@cisco.com>
>
>    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
>
>I've been sick and perhaps my message was a little short.  But when I
>read the abstract, I realized that if I didn't already know what the
>I-D was about, the abstract really wouldn't tell me.  It would be even
>clearer to say something like "This document creates 40 additional SIP
>... for the use of DISA."  But that might sound snarky, as people have
>wondered what so many namespaces are needed for.

Well... I can easily put the purpose of the namespaces in, to 
differentiated it from future IANA registrations of RP 
namespaces.  I'll submit this in two weeks, when we're out of the 
blackout period. This is easy.

James


>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