[secdir] Secdir last call review of draft-ietf-calext-eventpub-extensions-12

Rich Salz via Datatracker <noreply@ietf.org> Mon, 22 April 2019 18:14 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D3901120128; Mon, 22 Apr 2019 11:14:21 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Rich Salz via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: draft-ietf-calext-eventpub-extensions.all@ietf.org, ietf@ietf.org, calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.95.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Rich Salz <rsalz@akamai.com>
Message-ID: <155595686177.21216.4076761255030943970@ietfa.amsl.com>
Date: Mon, 22 Apr 2019 11:14:21 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/LCUzii013Yq3CLCjYUxhQ7y_rtM>
Subject: [secdir] Secdir last call review of draft-ietf-calext-eventpub-extensions-12
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Apr 2019 18:14:22 -0000

Reviewer: Rich Salz
Review result: Has Nits

This is the SECDIR last-call review, intended to be input to the Security AD's.

Ready with nits.

The Security Considerations and Privacy Considerations are short, but they seem
to reasonably refer to already-published documents.

Following are nits I noticed.

Abstract "a number of new iCalendar properties and components" -> "a new
iCalendar component and a number of properties"  Maybe stike "iCalendar"

Sec 1, STRUCTURED-DATA. In my opinion the confirmation code would be the most
useful new info :)

Sec 1, SOURCE Is it redefined or extended?

Sec 2, para 2.  "In a break with this 'tradition' ..." --> "Breaking with this
practice, ..."

Sec 3, "When a calendar client receives a calendar component" Should the second
calendar be CALENDAR? Should the first be "iCalendar"?

Sec 3.1.1, uppercase "vcard"?

Sec "non of which" --> "none of which"

Sec 4 Perhaps add a sentence saying where this syntax is defined. Is this the
complete iCalendar spec or is it just changing a few things?

Sec 5.1, etc "as laid down in" Is kind of informal wording.

Sec 6, the notation has "value=URI" but the example has "URL" (Sec 7.3, etc.,
uses URI in both parts)

Sec 10, "applications using" Is "acting on" better?