[calsify] Roman Danyliw's No Objection on draft-ietf-calext-ical-relations-09: (with COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 16 February 2022 16:14 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: calsify@ietf.org
Delivered-To: calsify@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D66F73A0D3F; Wed, 16 Feb 2022 08:14:58 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-calext-ical-relations@ietf.org, calext-chairs@ietf.org, calsify@ietf.org, Bron Gondwana <brong@fastmailteam.com>, brong@fastmailteam.com
X-Test-IDTracker: no
X-IETF-IDTracker: 7.45.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <164502809874.9967.1926820506987867104@ietfa.amsl.com>
Date: Wed, 16 Feb 2022 08:14:58 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/vzw0Wcttv4vynHXS8DipE1Rhn8Q>
Subject: [calsify] Roman Danyliw's No Objection on draft-ietf-calext-ical-relations-09: (with COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Calendaring and Scheduling Standards Simplification <calsify.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/calsify>, <mailto:calsify-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/calsify/>
List-Post: <mailto:calsify@ietf.org>
List-Help: <mailto:calsify-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/calsify>, <mailto:calsify-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Feb 2022 16:14:59 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-calext-ical-relations-09: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/blog/handling-iesg-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-calext-ical-relations/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Thank you to Catherine Meadows for the SECDIR review. ** Abstract. The abstract text needs to mention that it is updating RFC5545. ** Section 6.2. Typo. s/temporaly/temporarily/ ** Section 8.1. Per the example, “CONCEPT:http://example.com/event-types/arts/music” should this use https? ** Section 10. Thanks for noting the RFC3986 considerations on using URIs. Digging a bit more into the implementation approaches of the CONCEPT parameter, would clients be expected dereference the taxonomy URI in real-time? I’m wondering if there would be a chance for tracking mechanism akin to a “web bug” on a web page or in HTML email. For example, an .ics file is sent via an asynchronous mechanism (email) with a CONCEPT URI to something unique/unknown to the end-client and to a destination controlled by the sender or even a third party. Could it function as a read-receipt or to harvest an identifier for the system the client is on (IP address)?
- [calsify] Roman Danyliw's No Objection on draft-i… Roman Danyliw via Datatracker
- Re: [calsify] Roman Danyliw's No Objection on dra… Michael Douglass