Re: [calsify] Barry Leiba's Discuss on draft-ietf-calext-eventpub-extensions-12: (with DISCUSS and COMMENT)

[Barry Leiba <[e-mail]>]

Hiya,

>> — Section 10 —
>> It’s good to refer to RFC 3986 for URI-related security considerations, and all
>> of them do apply here.
>>
>> Something else that comes to mind that comes along with a set of new URIs is
>> whether they actually point to what they say they do.  I don’t see that there’s
>> any way to verify that they do, and I’m very skeptical about the effectiveness
>> of warning an end user about this sort of thing, for many reasons.  I can see
>> why allowing URIs is convenient and compelling, but I’m very heavily concerned
>> about tracking and other privacy leaks, malicious and deceptive content, and
>> other such problems, especially considering the prevalence of abusive calendar
>> invitations these days.
>>
>> I’m not sure what the answer is here, but let’s have a discussion about it and
>> see where we can go with it.
>
> Maybe a brief discussion at CalConect/IETF meeting?

Yes, that sounds like a good idea.  We'll hold this until then.

>> — Section 6 —
>>
>>    Purpose:  This property provides a reference to information about a
>>       component such as a participant possibly as a vcard or optionally
>>       a plain text typed value.
>>
>> This sentence needs some punctuation or rephrasing in order to make sense.  Can
>> you try?
>
> Is this better?
>
> This property provides a reference to information
> about a component such as a participant. For example, that
> information may be a vcard or a plain text typed value.

Ah, yes, OK: now I get what you're saying.  Thanks.

Barry