[calsify] Roman Danyliw's Discuss on draft-ietf-calext-eventpub-extensions-13: (with DISCUSS and COMMENT)
Roman Danyliw via Datatracker <noreply@ietf.org> Wed, 29 May 2019 19:05 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 934D41201B3; Wed, 29 May 2019 12:05:13 -0700 (PDT)
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-eventpub-extensions@ietf.org, Daniel Migault <daniel.migault@ericsson.com>, calext-chairs@ietf.org, daniel.migault@ericsson.com, calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.97.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Roman Danyliw <rdd@cert.org>
Message-ID: <155915671351.5441.17788073160352746190.idtracker@ietfa.amsl.com>
Date: Wed, 29 May 2019 12:05:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/sLRH17Ft3F-w54P6k5e3pUBNGWw>
Subject: [calsify] Roman Danyliw's Discuss on draft-ietf-calext-eventpub-extensions-13: (with DISCUSS and COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: <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, 29 May 2019 19:05:18 -0000
Roman Danyliw has entered the following ballot position for draft-ietf-calext-eventpub-extensions-13: Discuss 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/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-calext-eventpub-extensions/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- Per the Security Considerations section, [RFC3986] and [W3C.REC-html51-20171003] were helpful. I was hoping to see cautionary text for the potentially danger of handling/parsing arbitrary binaries as allowed by STRUCTURED DATA. I didn’t see it in downstream references. I also tried to find the referenced section suggested by “Security considerations relating to the ‘ATTACH’ property, as described in [RFC5545]” but could not. It’s not the explicit Security Considerations (Section 7 of [RFC5545) or in the definition of Attachment (Section 3.8.1.1 of [RFC5545]). Do you mean Section 3.1.3, Binary Content? Could you please make it clear which section you meant. ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- (1) Sections 5.1. and 5.2 state “New resource types SHOULD be registered in the manner laid down in this specification.” It would be cleared if you explicitly referenced the relevant IANA section. (2) Section 6. Doesn't the sentence “[t]he SOURCE property defined in [RFC7986] is redefined …” suggests that this document should also officially update RFC7986? (3) Editorial nits: Global. “vcard” and “VCARD” is used interchangeably. Recommend choosing one and being consistent Section 2. Misplaced comma?. s/JSON, [RFC8259]/JSON [RFC8259] Section 3. Typo. s/informations/information/ Section 3.1.2. Typo. s/traveller/traveler/ Section 3.1.2.1. Typo. s/non/none/ Section 7.5. Typo. s/sevices/services/ Section 9.2. Typo. s/plaaning/planning/
- [calsify] Roman Danyliw's Discuss on draft-ietf-c… Roman Danyliw via Datatracker
- Re: [calsify] Roman Danyliw's Discuss on draft-ie… Michael Douglass