[apps-discuss] APPSDIR review of draft-daboo-ical-vcard-parameter-encoding-02
Tim Bray <tbray@textuality.com> Fri, 28 December 2012 16:51 UTC
Return-Path: <tbray@textuality.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 ADC4F21F8D32 for <apps-discuss@ietfa.amsl.com>; Fri, 28 Dec 2012 08:51:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level:
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id mWD8zJZ7lJqY for <apps-discuss@ietfa.amsl.com>; Fri, 28 Dec 2012 08:51:17 -0800 (PST)
Received: from mail-oa0-f48.google.com (mail-oa0-f48.google.com [209.85.219.48]) by ietfa.amsl.com (Postfix) with ESMTP id 92CFE21F8C54 for <apps-discuss@ietf.org>; Fri, 28 Dec 2012 08:50:59 -0800 (PST)
Received: by mail-oa0-f48.google.com with SMTP id h2so9994848oag.35 for <apps-discuss@ietf.org>; Fri, 28 Dec 2012 08:50:59 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:content-transfer-encoding:x-gm-message-state; bh=MMsc92Aw5QL2GWQdtY/pfAYmK4zoTxf1O2rPLR8ZJEg=; b=oDsK1NCjhl3Td2JHdSInlhP6PnsQSN4pZksg8+EqG27O1Qa2C1TgCQM/OHGnp3dwqM tHcuVG2SdstWGVdYjLu3ZQ2k4W9jQ3DYIA6DWb6vDwl84S/2W2SrhxtCMK0xWemF79g5 TVSniDKvvKYVyyozkF13lLC9Hy1waU2yWZfMX06pTMQxnmSD3QODGTszn06cYo035JUa fNyupkvvcU7nhSZhwBccKnvV8mXO3WENB4bVVCjBceqxjmP0NZknGY+Z4/VC7r4gOYg7 BalSeiTDpZDeLEDHw1bEYk1/CcgfwU9nUmtVCbm3J1rInOpP8FzHVN/3fhPIb7y93EI9 q32w==
MIME-Version: 1.0
Received: by 10.182.228.69 with SMTP id sg5mr28291950obc.2.1356713459011; Fri, 28 Dec 2012 08:50:59 -0800 (PST)
Received: by 10.76.152.198 with HTTP; Fri, 28 Dec 2012 08:50:58 -0800 (PST)
X-Originating-IP: [204.83.73.92]
Date: Fri, 28 Dec 2012 08:50:58 -0800
Message-ID: <CAHBU6iu719WYW0x6RccpR2xgV3JrMjMuWt8AsMrec6unLWCwqA@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: draft-daboo-ical-vcard-parameter-encoding.all@tools.ietf.org, "apps-discuss@ietf.org" <apps-discuss@ietf.org>, The IESG <iesg@ietf.org>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQl4thKdnu444LHTDc95sFBs07TFXefDab3hFGS4r2RYLXC+q/F+on0knFHOf/IcIugOY1OQ
Subject: [apps-discuss] APPSDIR review of draft-daboo-ical-vcard-parameter-encoding-02
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: Fri, 28 Dec 2012 16:51:18 -0000
I have been selected as the Apps Area Directorate reviewer for this draft (for background on appsdir, please see http://trac.tools.ietf.org/area/app/trac/wiki/ApplicationsAreaDirectorate ). Please resolve these comments along with any other Last Call comments you may receive. Please wait for direction from your document shepherd or AD before posting a new version of the draft. Document: draft-daboo-ical-vcard-parameter-encoding-02 Title: Parameter Value Encoding in iCalendar and vCard Reviewer: Tim Bray Review Date: Dec 28th 2012 Summary: This draft is ready for publication, after fixing one error Major issues: None Minor issues: Section 3, second para. Text reads “If a ^ (U+005E) character is followed by any other character than the ones above, parsers SHOULD leave the ^ character in place.” - This should read “SHOULD leave both the ^ and the following character in place”. - Shouldn’t this be a MUST? The whole escaping scheme is going to blow up if software starts doing this wrong, or am I missing something? - You might want to consider putting this rule in the table, “^ followed by any other character|left unchanged”. Might be simpler. Nits: Appendix A. Did the discussion also consider the very successful and generalized character escaping system, as used in HTML & XML, of " or " for U+0022? If you did that, you’d never have to revisit this again, when (as seems likely) the need for other character-escaping functions arises in the future?