Re: [calsify] Alvaro Retana's Block on charter-ietf-calext-01-00: (with BLOCK and COMMENT)

[Bron Gondwana <[e-mail]>]

On Wed, Jan 19, 2022, at 00:32, Alvaro Retana via Datatracker wrote:
> Alvaro Retana has entered the following ballot position for
> charter-ietf-calext-01-00: Block
> 
> 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.)
> 
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/charter-ietf-calext/
> 
> 
> 
> ----------------------------------------------------------------------
> BLOCK:
> ----------------------------------------------------------------------
> 
>    - publish informative documents describing existing vendor extensions
>      which did not come through the IETF consensus process, but are
>      nonetheless in common usage and likely to be encountered in the wild.
> 
> I understand the intent, but all IETF documents require consensus (rfc8789).
> Publishing a vendor extension without consensus should be done through the ISE.

The idea is to publish as informative - with consensus that this matches what IETF members have seen in the wild.  Even if they wound up published via ISE, the working group would work with them, since we have to work around them because that's what's actually out there.

> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Please help me understand how JSContact fits into this charter.  It confuses me
> because it is a draft that belongs to a different WG, which also contradicts
> the statement that "work which is in scope for any other ART area working
> group" is out of scope.  It may be premature to list draft-ietf-jmap-jscontact
> as part of the base documents.
> 

This is based on taking on VCARD into this group, which brings jscontact into scope as well.  We decided to put jscontact in JMAP despite having done jscalendar (which is the related format for calendar events) here in CALEXT.  I'm a co-chair on both working groups, and have discussed this move with the chairs of both working groups as well as the authors - and it was discussed at last IETF in both groups as well.

Cheers,

Bron.


--
  Bron Gondwana, CEO, Fastmail Pty Ltd
  [e-mail]