Re: [calsify] Roman Danyliw's Discuss on draft-ietf-calext-eventpub-extensions-13: (with DISCUSS and COMMENT)
Michael Douglass <mikeadouglass@gmail.com> Tue, 08 October 2019 18:44 UTC
Return-Path: <mikeadouglass@gmail.com>
X-Original-To: calsify@ietfa.amsl.com
Delivered-To: calsify@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A92F1200B9; Tue, 8 Oct 2019 11:44:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bRS-eGy3orUb; Tue, 8 Oct 2019 11:44:12 -0700 (PDT)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AACCA120071; Tue, 8 Oct 2019 11:44:12 -0700 (PDT)
Received: by mail-qt1-x832.google.com with SMTP id u22so26711187qtq.13; Tue, 08 Oct 2019 11:44:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=7fA1G5lD3GYbh1vePGMURqb7BXEiKo/XtVoOltqR+F0=; b=t3LT5AJTe/Eg9gojF7+QM7GatCPd7ms012zbURsWq1//WrjO/ytCb9J9wh5d6sCWIV citX60QTHvAj0qz7MLMeprrJmhbY4TQr0ga7sZ6EsEOqg0z2HYZfBCRpGV95ertu6pee f0O87KNe9jaR94k9XYmclPV/b/FRg1bRNtoyDSYU0y/fGTmMw7P8faPo6E3Hcop6bQ3f DTdaK7eJyUE3GObmtil6OVO9w68ge3p8L3qGIM9cWuMn6dp17iZWNRx9UDxkIOM5p/ll WGaYjp9lYv8Xh7PTw2/r1MW1fMRdqnZ3S6TklHP4xX55ZHj1dnvtTE9Zp6IuZpWMaOll o+Rw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=7fA1G5lD3GYbh1vePGMURqb7BXEiKo/XtVoOltqR+F0=; b=TuY2yA3KNPGip+sfEhlOwgw4EExogg4yZYyy72Ns61G6L55kXsvDnoNy7T+YrOIgKY 97isksjjZe7bkvqpRrL37uYcRXP+Z5+XiepEsSgCdB4Tk9hoPduuMMLeNj2XFolWIDal 0Gdpxf4JA699fe4YREM+GrnRRs/Td/ktLzH/RozVbKJPA6l2Y5JYrA1sZ3WnO4sRP+RO j6rQmCTsqxNDSIFGhdcQGzoGaQyEdRjJIVTcZq0oCVo7BPB6T9CoFwpd1nJS6q3I+G+Y it3ArR7wiJ4NlZKZ8N61jVRneSYvGOJ81/YWKmrAt667hH+WmP8CoijRLQVkxKvDpYfw 0Byg==
X-Gm-Message-State: APjAAAX4MUhvMUBgr/6+Yb88ndlbpz+CBHQN4FRSEIKNu20PEPNauP8+ TzcYAsQKSVSz/HNaeK6l9gaFOCid
X-Google-Smtp-Source: APXvYqyN/FIXIiDIiFxqU7S0B1sY9Gj+bPhPvwDgL0x6lrryl3AwlTDR6ACe9QEJ7G+V/oW9p926DA==
X-Received: by 2002:a0c:8828:: with SMTP id 37mr4791637qvl.44.1570560251465; Tue, 08 Oct 2019 11:44:11 -0700 (PDT)
Received: from Michaels-MacBook-Pro.local (pool-100-19-39-104.phlapa.fios.verizon.net. [100.19.39.104]) by smtp.googlemail.com with ESMTPSA id c6sm81713qtc.83.2019.10.08.11.44.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 08 Oct 2019 11:44:10 -0700 (PDT)
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
Cc: draft-ietf-calext-eventpub-extensions@ietf.org, calext-chairs@ietf.org, calsify@ietf.org
References: <155915671351.5441.17788073160352746190.idtracker@ietfa.amsl.com>
From: Michael Douglass <mikeadouglass@gmail.com>
Message-ID: <5e020a9c-103f-9df2-45b7-d9f1d31edf36@gmail.com>
Date: Tue, 08 Oct 2019 14:44:09 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <155915671351.5441.17788073160352746190.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/0X1-Huv2U4uthG0efGih7b59hJs>
Subject: Re: [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
Precedence: list
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: Tue, 08 Oct 2019 18:44:16 -0000
Thank you. Updates will appear in version 15 On 5/29/19 15:05, Roman Danyliw via Datatracker wrote: > 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. Not sure what I was looking at there. I have found some managed attachments text which I have modified and added > > > ---------------------------------------------------------------------- > 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. Done > > (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? We're no longer updating that property > > (3) Editorial nits: > > Global. “vcard” and “VCARD” is used interchangeably. Recommend choosing one > and being consistent Used vCard throughout > > 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/ All done. > > > _______________________________________________ > calsify mailing list > calsify@ietf.org > https://www.ietf.org/mailman/listinfo/calsify
- [calsify] Roman Danyliw's Discuss on draft-ietf-c… Roman Danyliw via Datatracker
- Re: [calsify] Roman Danyliw's Discuss on draft-ie… Michael Douglass