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

Alvaro Retana via Datatracker <noreply@ietf.org> Tue, 18 January 2022 13:32 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 881623A118D; Tue, 18 Jan 2022 05:32:04 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alvaro Retana via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: calext-chairs@ietf.org, calsify@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alvaro Retana <aretana.ietf@gmail.com>
Message-ID: <164251272447.25883.1640740546329924573@ietfa.amsl.com>
Date: Tue, 18 Jan 2022 05:32:04 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/calsify/DAcikhHXSymD2VfFZkuiFSLY3LI>
Subject: [calsify] Alvaro Retana's Block on charter-ietf-calext-01-00: (with BLOCK and COMMENT)
X-BeenThere: calsify@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Calendaring and Scheduling Standards Simplification <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, 18 Jan 2022 13:32:05 -0000

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.


----------------------------------------------------------------------
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.