Re: [apps-discuss] APPSDIR review of draft-ietf-appswg-xdash-03
Pete Resnick <presnick@qualcomm.com> Sun, 11 March 2012 04:00 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 A625321F8607; Sat, 10 Mar 2012 20:00:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.568
X-Spam-Level:
X-Spam-Status: No, score=-106.568 tagged_above=-999 required=5 tests=[AWL=0.031, 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 BOd7LF+7SwQg; Sat, 10 Mar 2012 20:00:53 -0800 (PST)
Received: from wolverine01.qualcomm.com (wolverine01.qualcomm.com [199.106.114.254]) by ietfa.amsl.com (Postfix) with ESMTP id 0923B21F8604; Sat, 10 Mar 2012 20:00:52 -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=1331438453; x=1362974453; 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<4F5C236F.40003@qualcomm.com>|Date:=20Sat, =2010=20Mar=202012=2022:00:47=20-0600|From:=20Pete=20Resn ick=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:=20<dcrocker@bbiw.net>|CC:=20Dave =20Crocker=20<dhc@dcrocker.net>,=20John=20C=20Klensin=20< klensin@jck.com>,=0D=0A=09<draft-ietf-appsawg-xdash.all@t ools.ietf.org>,=20Peter=20Saint-Andre=0D=0A=09<stpeter@st peter.im>,=20<apps-discuss@ietf.org>,=20The=20IESG=20<ies g@ietf.org>|Subject:=20Re:=20[apps-discuss]=20APPSDIR=20r eview=20of=20draft-ietf-appswg-xdash-03|References:=20<62 FF481C5AD21C3F683CD2B9@PST.JCK.COM>=09<4F5B9FF5.7040209@d crocker.net>=20<4F5BA20D.30304@qualcomm.com>=09<B47E8B2B6 E9CA7E84099E605@PST.JCK.COM>=20<4F5C1CCE.6020706@dcrocker .net>=20<4F5C1E10.6000909@qualcomm.com>=20<4F5C1EFE.40703 01@dcrocker.net>|In-Reply-To:=20<4F5C1EFE.4070301@dcrocke r.net>|Content-Type:=20text/plain=3B=20charset=3D"ISO-885 9-1"=3B=20format=3Dflowed|Content-Transfer-Encoding:=207b it|X-Originating-IP:=20[172.30.48.1]; bh=1rsws8XXu4CQUZOlwcaU0RBq0Mf1/l1ixFc7DbmQbV0=; b=hGFF4jzYt7Xid7vgWKdSvmWcqgj8b1rZL51Sn+1zDlNd5+jS1Z4cGHNS 2628meinhZlijnQ1yoWxrNjkqoWt+XJ620oPe/Wf1dLj2ZvlSKudPAPcL ew3j2WiboYgXsHGdZsnrci63FGcJd9NYeMZRLDc/KGDwToOGhOM5hhXfE 0=;
X-IronPort-AV: E=McAfee;i="5400,1158,6645"; a="171413194"
Received: from ironmsg02-l.qualcomm.com ([172.30.48.16]) by wolverine01.qualcomm.com with ESMTP; 10 Mar 2012 20:00:52 -0800
X-IronPort-AV: E=Sophos;i="4.73,565,1325491200"; d="scan'208";a="119654336"
Received: from nasanexhc04.na.qualcomm.com ([172.30.48.17]) by ironmsg02-L.qualcomm.com with ESMTP/TLS/AES128-SHA; 10 Mar 2012 20:00:52 -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 20:00:52 -0800
Message-ID: <4F5C236F.40003@qualcomm.com>
Date: Sat, 10 Mar 2012 22:00:47 -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: dcrocker@bbiw.net
References: <62FF481C5AD21C3F683CD2B9@PST.JCK.COM> <4F5B9FF5.7040209@dcrocker.net> <4F5BA20D.30304@qualcomm.com> <B47E8B2B6E9CA7E84099E605@PST.JCK.COM> <4F5C1CCE.6020706@dcrocker.net> <4F5C1E10.6000909@qualcomm.com> <4F5C1EFE.4070301@dcrocker.net>
In-Reply-To: <4F5C1EFE.4070301@dcrocker.net>
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, John C Klensin <klensin@jck.com>, 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 04:00:53 -0000
Presenting my still purple face, and this time intentionally replying to all... On 3/10/12 9:41 PM, Dave Crocker wrote: > for the life of me, I can't figure out what John's substantive concern > is with the document being considered. As I said before, I think making the "status vs. type" distinction is worth doing, though apparently even I was unable to do it the first shot to make it clear to John, though apparently I did on the second go-round. An attempt at text: To the first paragraph of the intro: Many application protocols use parameters with textual names to identify data (media types, header fields in Internet mail messages and HTTP requests, vCard parameters and properties, etc.). Historically, designers and implementers of application protocols have often distinguished between "standard" and "non-standard" parameters by prefixing the latter with the string "X-" or similar constructions (e.g., "x."), where the "X" is commonly understood to stand for "eXperimental" or "eXtension". Add: "That is, instead of just identifying the data, the name also embedded the status of the name as "non-standard" into the name itself." Does that help? Do we need more elsewhere in the intro. pr -- Pete Resnick<http://www.qualcomm.com/~presnick/> Qualcomm Incorporated - Direct phone: (858)651-4478, Fax: (858)651-1102
- [apps-discuss] APPSDIR review of draft-ietf-appsw… William Mills
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Martin Thomson
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Martin Thomson
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Pete Resnick
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Pete Resnick
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Pete Resnick
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Pete Resnick
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Pete Resnick
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Bill McQuillan
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Pete Resnick
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Bill McQuillan
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Ned Freed
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Dave Crocker
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… Peter Saint-Andre
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin
- Re: [apps-discuss] APPSDIR review of draft-ietf-a… John C Klensin