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

"James M. Polk" <jmpolk@cisco.com> Fri, 29 February 2008 00:51 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 DCE9328C161; Thu, 28 Feb 2008 16:51:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.004
X-Spam-Level:
X-Spam-Status: No, score=-1.004 tagged_above=-999 required=5 tests=[AWL=-0.567, 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 8I7Ps0twbXmw; Thu, 28 Feb 2008 16:51:53 -0800 (PST)
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id E690A3A6C2C; Thu, 28 Feb 2008 16:51:52 -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 C23533A6C2C for <sip@core3.amsl.com>; Thu, 28 Feb 2008 16:51:51 -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 DshLerz56GKF for <sip@core3.amsl.com>; Thu, 28 Feb 2008 16:51:50 -0800 (PST)
Received: from sj-iport-3.cisco.com (sj-iport-3.cisco.com [171.71.176.72]) by core3.amsl.com (Postfix) with ESMTP id E28613A6BF6 for <sip@ietf.org>; Thu, 28 Feb 2008 16:51:50 -0800 (PST)
Received: from sj-dkim-2.cisco.com ([171.71.179.186]) by sj-iport-3.cisco.com with ESMTP; 28 Feb 2008 16:51:44 -0800
Received: from sj-core-5.cisco.com (sj-core-5.cisco.com [171.71.177.238]) by sj-dkim-2.cisco.com (8.12.11/8.12.11) with ESMTP id m1T0phLG015761; Thu, 28 Feb 2008 16:51:43 -0800
Received: from xbh-sjc-221.amer.cisco.com (xbh-sjc-221.cisco.com [128.107.191.63]) by sj-core-5.cisco.com (8.12.10/8.12.6) with ESMTP id m1T0phbd013728; Fri, 29 Feb 2008 00:51:43 GMT
Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-221.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Feb 2008 16:51:41 -0800
Received: from jmpolk-wxp.cisco.com ([171.70.229.148]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Thu, 28 Feb 2008 16:51:41 -0800
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Thu, 28 Feb 2008 18:51:50 -0600
To: Dean Willis <dean.willis@softarmor.com>
From: "James M. Polk" <jmpolk@cisco.com>
In-Reply-To: <47C6FB5F.8090209@softarmor.com>
References: <20080224054501.90B6A3A6A07@core3.amsl.com> <200802250404.m1P44eZm023626@dragon.ariadne.com> <XFE-SJC-212GpaoG1VR00004ef4@xfe-sjc-212.amer.cisco.com> <47C6FB5F.8090209@softarmor.com>
Mime-Version: 1.0
Message-ID: <XFE-SJC-2128aVKUJfh00005709@xfe-sjc-212.amer.cisco.com>
X-OriginalArrivalTime: 29 Feb 2008 00:51:41.0115 (UTC) FILETIME=[3F3E98B0:01C87A6D]
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=1667; t=1204246303; x=1205110303; 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=+PETuQE5qaxQE/etmuILcoNnus0JM9lEMqR+cb5BpXY=; b=HJkSP/WjI+EYHu/xnAjni0kSeuB3uGLNXl6deUtjjIxE7rWj1cRvMPMYwF Ki9n7/rwd7egecQjvXHpmDwhlSswV95fh3bexJwarZUAjqlw3nW7SABjQ2vK Fc5LEydDli;
Authentication-Results: sj-dkim-2; header.From=jmpolk@cisco.com; dkim=pass ( sig from cisco.com/sjdkim2002 verified; );
Cc: sip@ietf.org
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

At 12:20 PM 2/28/2008, Dean Willis wrote:
>James M. Polk wrote:
> >
> >>    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
>
>Since I personally only read the abstract of new drafts and extrapolate
>all further content (including any errors) by intuitive deduction, I'm
>sure that a more detailed abstract would be helpful. ;-)

no problem... the next version will be done and submitted the week of 
the meeting


>Seriously, a well-written abstract is a big help for people who haven't
>been reading along with the development. Many students I've talked to
>start with the abstract, and then use that to decide how the RFC fits
>into the mental framework they're building as they try to come to grips
>with the documentation-kraken that SIP has become.
>
>We should be careful to make our abstracts as useful for this sort of
>thing as we can. That means that the abstract needs to tell us what the
>draft is about well enough to fit it into a framework, but not tell us
>much about the implementation detail. Admittedly, it is a fine balancing
>act -- but I'm afraid the abstract for the draft in question hasn't even
>stepped up to the high-wire, much less maintained its balance.
>
>--
>dean

_______________________________________________
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