[JMAP] Re: WGLC: please review the final state of the JSCalendar/JMAP Calendars drafts

[Lisa Dusseault <[e-mail]>]

I reviewed draft-ietf-calext-icalendar-jscalendar-extensions.  I'm in
favour of its publication.

I noticed a missing word in the introduction sentence "To achieve this,
this document
defines new elements iCalendar and extends existing definitions.
The security considerations reference RFC5545 but that document itself has
very light security considerations.
* At the very least, this document introduces a new OWNER role which in
many systems implies access privileges, and there are surely new security
considerations around that. (Should a system let me, if I have write access
to an event, make myself the owner?)
* perhaps this document should fill in some things that RFC5545 c*ould* have
included, notably that location information can be a privacy and safety
concern.

Lisa

On Wed, Sep 16, 2026 at 11:06 AM Mauro De Gennaro <mauro=
[e-mail]> wrote:

>
> I have reviewed draft-ietf-jmap-calendars-29 together with
> draft-ietf-calext-jscalendarbis-20,
> draft-ietf-calext-jscalendar-icalendar-28 and
> draft-ietf-calext-icalendar-jscalendar-extensions-07. The only issue I
> found is an inconsistency around the "attendee" participant role.
>
> draft-ietf-calext-jscalendarbis-20 removes the "attendee" role (Appendix
> A.2.3) and marks it obsolete in the IANA registry (Section 7.6.15).
> However, draft-ietf-jmap-calendars-29 still relies on it without defining
> it:
>
> - Section 3 (permission rules) requires participants added via
> mayInviteSelf or mayInviteOthers to have "roles" containing only "attendee".
> - Sections 5.1.1 and 5.1.2 define mayInviteSelf and mayInviteOthers in
> terms of the "attendee" role.
> - The "attendee" filter condition of CalendarEvent/query matches
> participants with a role of "attendee".
> - The examples use "roles": { "attendee": true }.
>
> Otherwise the document looks good to me.
>
>
> Best,
> Mauro
>
>
>
> > On 16 Sep 2026, at 19:42, Bron Gondwana <brong=
> [e-mail]> wrote:
> >
> > Hello JMAP and CALEXT working groups,
> >
> > Our AD has asked us to please do one final pass over the combined set of
> documents in the Calendaring cluster, as they have has some late normative
> changes due to WGLC feedback.  In order no to hold things up too long, it
> would be great to have feedback by the end of next week, Friday September
> 25th.
> >
> > The set of documents is:
> >
> > CALEXT:
> >     • draft-ietf-calext-icalendar-jscalendar-extensions-07
> >     • draft-ietf-calext-jscalendar-icalendar-28
> >     • draft-ietf-calext-jscalendarbis-20
> > JMAP:
> >     • draft-ietf-jmap-calendars-29
> >
> > Our area director and the IESG would like to see that people have read
> the documents (or at least the most recent set of changes) and agree with
> them, so please reply to this message, not only with disagreement but also
> with support for this set of documents going forwards.
> >
> > Thanks,
> >
> > Bron.
> >
> >
> > --
> >   Bron Gondwana, CEO, Fastmail Pty Ltd / Fastmail US LLC
> >   [e-mail]
> >
> > _______________________________________________
> > JMAP mailing list -- [e-mail]
> > To unsubscribe send an email to [e-mail]
>
> _______________________________________________
> JMAP mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
>