[Jmap] Roman Danyliw's No Objection on draft-ietf-jmap-contacts-09: (with COMMENT)

Roman Danyliw via Datatracker <noreply@ietf.org> Tue, 28 May 2024 15:41 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: jmap@ietf.org
Delivered-To: jmap@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 65A60C18DBB7; Tue, 28 May 2024 08:41:41 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Roman Danyliw via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 12.13.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <171691090140.41173.12674049038070402991@ietfa.amsl.com>
Date: Tue, 28 May 2024 08:41:41 -0700
Message-ID-Hash: D7ASXQQRSDQ23HS7UR2NOJYV2E2GVYGZ
X-Message-ID-Hash: D7ASXQQRSDQ23HS7UR2NOJYV2E2GVYGZ
X-MailFrom: noreply@ietf.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-jmap.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: draft-ietf-jmap-contacts@ietf.org, jmap-chairs@ietf.org, jmap@ietf.org, fenton@bluepopcorn.net
X-Mailman-Version: 3.3.9rc4
Reply-To: Roman Danyliw <rdd@cert.org>
Subject: [Jmap] Roman Danyliw's No Objection on draft-ietf-jmap-contacts-09: (with COMMENT)
List-Id: JSON Message Access Protocol <jmap.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/coAWV-hDnHaHX0qMaLI-hpiJMwE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/jmap>
List-Help: <mailto:jmap-request@ietf.org?subject=help>
List-Owner: <mailto:jmap-owner@ietf.org>
List-Post: <mailto:jmap@ietf.org>
List-Subscribe: <mailto:jmap-join@ietf.org>
List-Unsubscribe: <mailto:jmap-leave@ietf.org>

Roman Danyliw has entered the following ballot position for
draft-ietf-jmap-contacts-09: No Objection

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/about/groups/iesg/statements/handling-ballot-positions/ 
for more information about how to handle DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-jmap-contacts/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thank you to Meral Shirazipour for the GENART review.

** Section 7.  Section 7.1, 7.2 and 7.3 don’t explicitly name the registry. 
However, Section 7.4, does.  For clarity, I would recommend:

OLD #1
   IANA will register the "contacts" JMAP Capability as follows:
NEW
IANA will register "contacts" in the “JMAP Capabilities” registry as follows:

OLD #2
   IANA will register the "AddressBook" JMAP Data Type as follows:
NEW
IANA will register "AddressBook" in the “JMAP Data Types” registry as follows:

OLD #3
   IANA will register the "ContactCard" JMAP Data Type as follows:
NEW
IANA will register “ContactCard" in the “JMAP Data Types” registry as follows: