Re: [apps-discuss] APPSDIR review of draft-ietf-appswg-xdash-03

Pete Resnick <presnick@qualcomm.com> Sun, 11 March 2012 03:33 UTC

Return-Path: <presnick@qualcomm.com>
X-Original-To: apps-discuss@ietfa.amsl.com
Delivered-To: apps-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F0E6521F8467; Sat, 10 Mar 2012 19:33:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.567
X-Spam-Level:
X-Spam-Status: No, score=-106.567 tagged_above=-999 required=5 tests=[AWL=0.032, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OSJ7ASErtsg8; Sat, 10 Mar 2012 19:33:40 -0800 (PST)
Received: from wolverine02.qualcomm.com (wolverine02.qualcomm.com [199.106.114.251]) by ietfa.amsl.com (Postfix) with ESMTP id 3038621F844A; Sat, 10 Mar 2012 19:33:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=presnick@qualcomm.com; q=dns/txt; s=qcdkim; t=1331436820; x=1362972820; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-originating-ip; z=Message-ID:=20<4F5C1D10.8050305@qualcomm.com>|Date:=20Sa t,=2010=20Mar=202012=2021:33:36=20-0600|From:=20Pete=20Re snick=20<presnick@qualcomm.com>|User-Agent:=20Mozilla/5.0 =20(Macintosh=3B=20U=3B=20Intel=20Mac=20OS=20X=2010.6=3B =20en-US=3B=20rv:1.9.1.9)=20Gecko/20100630=20Eudora/3.0.4 |MIME-Version:=201.0|To:=20John=20C=20Klensin=20<klensin@ jck.com>|CC:=20<dcrocker@bbiw.net>,=20Dave=20Crocker=20<d hc@dcrocker.net>,=0D=0A=09<apps-discuss@ietf.org>,=20<dra ft-ietf-appsawg-xdash.all@tools.ietf.org>,=20The=0D=0A=20 IESG=20<iesg@ietf.org>,=20Peter=20Saint-Andre=20<stpeter@ stpeter.im>,=20Martin=20Thomson=0D=0A=09<martin.thomson@g mail.com>|Subject:=20Re:=20[apps-discuss]=20APPSDIR=20rev iew=20of=20draft-ietf-appswg-xdash-03|References:=20<62FF 481C5AD21C3F683CD2B9@PST.JCK.COM>=09<4F5B9FF5.7040209@dcr ocker.net>=20<4F5BA20D.30304@qualcomm.com>=20<B47E8B2B6E9 CA7E84099E605@PST.JCK.COM>|In-Reply-To:=20<B47E8B2B6E9CA7 E84099E605@PST.JCK.COM>|Content-Type:=20text/plain=3B=20c harset=3D"ISO-8859-1"=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-Originating-IP:=20[1 72.30.48.1]; bh=5vw5hDQS6JX2mh9JJajNHBDnXU6TeQj8NvA/6cOYgHY=; b=oItPr4hPFWpJ/JJZMa3SMqBAfv7bww2E398SQyiA7qZ5Gq5LxpPlvN/I hsZIc6yTKClXHC5JIyjYaJqhGyjoBP482KXJzRsKfegwp4fI1CKYocI6n r4wUqTiY/cg/AjfwYTEhiTQUpcS+a/IhKhpJGNM7XzJPXulr8MH75nTp9 Q=;
X-IronPort-AV: E=McAfee;i="5400,1158,6645"; a="169097976"
Received: from ironmsg04-r.qualcomm.com ([172.30.46.18]) by wolverine02.qualcomm.com with ESMTP; 10 Mar 2012 19:33:39 -0800
X-IronPort-AV: E=Sophos;i="4.73,563,1325491200"; d="scan'208";a="281614491"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by Ironmsg04-R.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Mar 2012 19:33:39 -0800
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.17) with Microsoft SMTP Server (TLS) id 14.1.339.1; Sat, 10 Mar 2012 19:33:39 -0800
Message-ID: <4F5C1D10.8050305@qualcomm.com>
Date: Sat, 10 Mar 2012 21:33:36 -0600
From: Pete Resnick <presnick@qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: John C Klensin <klensin@jck.com>
References: <62FF481C5AD21C3F683CD2B9@PST.JCK.COM> <4F5B9FF5.7040209@dcrocker.net> <4F5BA20D.30304@qualcomm.com> <B47E8B2B6E9CA7E84099E605@PST.JCK.COM>
In-Reply-To: <B47E8B2B6E9CA7E84099E605@PST.JCK.COM>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Cc: apps-discuss@ietf.org, draft-ietf-appsawg-xdash.all@tools.ietf.org, dcrocker@bbiw.net, The IESG <iesg@ietf.org>
Subject: Re: [apps-discuss] APPSDIR review of draft-ietf-appswg-xdash-03
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 11 Mar 2012 03:33:41 -0000

On 3/10/12 9:23 PM, John C Klensin wrote:
>
> --On Saturday, March 10, 2012 12:48 -0600 Pete Resnick
> <presnick@qualcomm.com>  wrote:
>
>    
>> On 3/10/12 12:39 PM, Dave Crocker wrote:
>>
>>      
>>> On 3/10/2012 10:35 AM, John C Klensin wrote:
>>>        
>>>> However, an
>>>> interpretation of Dave's statement could extend to a
>>>> prohibition, not only on faceted or hierarchical names but on
>>>> the "+xml" arrangements and the like that we've used in media
>>>> types.
>>>>          
>>> Unless I've entirely misunderstood the use of that qualifier,
>>> it  indicates an encoding framework for the labeled data, not
>>> it's 'status'.
>>>        
>> Ah! That would be a lovely distinction to make in the
>> introduction in so many words: It's when a piece of the name
>> is used to indicate a *status* rather than a *type* that
>> presents the problem. That would be a great clarification.
>>      
> Sure.  Except that, while "experimental" or "private use" are
> examples of "status", "extension" is a type.  And that, I
> believe, takes us back to square one.
>    

No, you've misunderstood my distinction, which means we haven't gotten 
the wording quite right. When I said "type", I meant "type of *content* 
being named". So, "+xml" is indicating a "type" of data or content. 
"Extension" is a status. It's how the *name* is being used, not what the 
*content* is.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102