Re: [regext] EXTENDED: Re: CALL FOR ADOPTION: draft-loffredo-regext-rdap-jcard-deprecation-03

Gavin Brown <gavin.brown@centralnic.com> Mon, 15 February 2021 10:38 UTC

Return-Path: <gavin.brown@centralnic.com>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A3F03A1106 for <regext@ietfa.amsl.com>; Mon, 15 Feb 2021 02:38:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.001
X-Spam-Level:
X-Spam-Status: No, score=0.001 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=centralnic-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id toWZPoK2Q4GM for <regext@ietfa.amsl.com>; Mon, 15 Feb 2021 02:38:08 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABD6D3A1104 for <regext@ietf.org>; Mon, 15 Feb 2021 02:38:08 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id b3so8267369wrj.5 for <regext@ietf.org>; Mon, 15 Feb 2021 02:38:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=centralnic-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7wL+mG9C7u9LNv4ZNRrHgmYtBhYqBpUhznaQ3zywFNg=; b=iJy9afdhPVBhdXF5PqbbXp8wNEVwNxdqYUnGBhryBLztBPp/qrFrDgcKIZvuLEIJGb RD4YJm2c0SlY4+DQuGTf78EhDdvztNT7CfJeXD0JvATfpPfCvYd9z79KctDi6NHyZ9PS Xd0G+FpZkO9/WFRB+PpHfXttZKGJtC1++agwb1uLryle3wZJ8TXzhQG/nWdwyq7XpcfR kmvOrRgCZoJkjySuSk2/Am394Zb/VprIR1A8/83e71aarmcT2AvehkG7ap2HVwTjtBNu J0hqdy3RuPi3xwZLIMiIBEKum+nXWRAdbaBrTEwrhjWX9odinwccB4Sqjnp7+HYeyBcJ k8uA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=7wL+mG9C7u9LNv4ZNRrHgmYtBhYqBpUhznaQ3zywFNg=; b=rMy4qwsPacMl6DY7H4qD7rip31ILzWkQtp8yAwssVKoBYP5FjuCxiKF0uQN+nrQUaY I67N+fg80rG2nGOQ0CPKlSOFeo1DsYGZwSZ2DJnQi6LACQ0TM4TU9okOZzpatvKo4b+S 8YYkBQ0BbRIvxEf/lJmNRcF15ays6zhYy4FLt00xzpN6J7SAJez/Y7X8poH88Wu0N+GS SI3aa+MOOx1amQVM+N3FCT/eRka3oizkpA5LjchUtd1w0ZnofOUxyTeRIMfDY2vHNc4B pGRGvKQUTTvG93N36bmkU9tRVSPyVuaW6o5bvuc3OADMSY34BC5wPM45pO+Os5I1B/00 QGPA==
X-Gm-Message-State: AOAM5337piW511am9ersMLrCvdLWv/JREzyX8nzu1JNmXDRX5VjZWSCP 3MRE/S9ih5ycHgH7lQad8mVkzg==
X-Google-Smtp-Source: ABdhPJzbKkQDkVcKMeU/2CVYn6OpiXK5P4zUFQ90XoQjkQS0JgOPi0DCHhhf8vJgfiqilTWLpSwa3g==
X-Received: by 2002:a5d:5910:: with SMTP id v16mr7521009wrd.304.1613385486842; Mon, 15 Feb 2021 02:38:06 -0800 (PST)
Received: from broadband.bt.com ([2a00:23c7:d708:bd01:3c87:c330:9330:1a20]) by smtp.gmail.com with ESMTPSA id j125sm24818787wmb.44.2021.02.15.02.38.06 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Feb 2021 02:38:06 -0800 (PST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Gavin Brown <gavin.brown@centralnic.com>
In-Reply-To: <04ED2EFE-3F91-4357-B2B5-4D2B18DFBAC5@elistx.com>
Date: Mon, 15 Feb 2021 10:38:05 +0000
Cc: REGEXT WG <regext@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFB6463B-135B-4713-B7D8-17D69C58DAB7@centralnic.com>
References: <3163EFC6-C1B4-43E4-A24D-BF3F8410FE2A@elistx.com> <04ED2EFE-3F91-4357-B2B5-4D2B18DFBAC5@elistx.com>
To: James Galvin <galvin@elistx.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/Ij79pIfAlJRPhxyeqzUmse5z9zM>
Subject: Re: [regext] EXTENDED: Re: CALL FOR ADOPTION: draft-loffredo-regext-rdap-jcard-deprecation-03
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Feb 2021 10:38:11 -0000

Hi,

I support adoption of this document and will continue to contribute to it.

G.

> On 10 Feb 2021, at 19:33, James Galvin <galvin@elistx.com> wrote:
> 
> The Chairs would like to extend this CALL FOR ADOPTION because we’d like to separate out an issue that has come up in the discussion of this adoption.  We are hoping that this clarity will address the concern that has been raised.
> 
> This document actually covers two distinct issues.
> 
> 1. A specification for jsContact.
> 2. A proposal for migrating to jsContact from jCard.
> 
> There are words suggesting that jCard would be deprecated as part of this and the question has been raised on the list as to whether or not this is actually a reality.
> 
> The Chairs would like to propose that we separate out the question of whether or not jCard will be deprecated.  That is better considered as a separate question.
> 
> Since there is precedent in the IETF for documenting alternate ways of meeting a requirement, here is what we propose.
> 
> This CALL FOR ADOPTION is to commit to a specification of jsContact.  The specification would be permitted to document how one could migrate from jCard to jsContact.  The starting point for this work is draft-loffredo-regext-rdap-jcard-deprecation-03.
> 
> If this document is adopted, then we will need to consider the relationship between the use of jsContact and jCard.  The IESG will ask us this question as part of considering the publication of any document we develop.  This will effect the potential status of the document, e.g., Proposed Standard vs Experimental.  More specifically, we will need to consider whether there is support to migrate to something new given the legacy deployment.  It is appropriate to have this discussion within the working group.
> 
> With all that in mind, here is the revised, extended CALL FOR ADOPTION:
> 
> 
> This is a formal adoption request for “Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses”:
> 
> https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-jcard-deprecation/
> 
> This document will serve as the starting point for documenting jsContact.  It may also document how to migrate from jCard to jsContact, depending on the consensus of the working group.
> 
> Please review this draft to see if you think it is suitable for adoption by REGEXT for the stated purpose, and comment to the list, clearly stating your view.
> 
> If adopted, the document will be renamed as follows: draft-ietf-regext-rdap-jscontact.
> 
> Please indicate if you are willing to contribute text, review text, or be a document shepherd.
> 
> Please also indicate any preference you have for a proposed milestone date.
> 
> This call for adoption ends Monday, 22 February 2021.
> 
> If there are no objections, and we receive enough consensus for adoption, the chairs will consider this document adopted.
> 
> Thanks,
> 
> Your REGEXT co-chairs Antoin and Jim
> 
> 
> 
> 
> On 18 Jan 2021, at 9:29, James Galvin wrote:
> 
>> This is a formal adoption request for “Using JSContact in Registration Data Access Protocol (RDAP) JSON Responses”:
>> 
>> https://datatracker.ietf.org/doc/draft-loffredo-regext-rdap-jcard-deprecation/
>> 
>> Please review this draft to see if you think it is suitable for adoption by REGEXT, and comment to the list, clearly stating your view.
>> 
>> Please indicate if you are willing to contribute text, review text, or be a document shepherd.
>> 
>> Please also indicate any preference you have for a proposed milestone date.
>> 
>> This call for adoption ends Monday, 1 February 2021.
>> 
>> If there are no objections, and we receive enough consensus for adoption, the chairs will consider this document adopted.
>> 
>> Thanks,
>> 
>> Your REGEXT co-chairs Antoin and Jim
> 

--
Gavin Brown
Head of Registry Services
CentralNic Group plc (LSE:CNIC)
https://centralnicregistry.com

Cal: https://cnic.link/gbcalendar

CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: Saddlers House, Gutter Lane, London EC2V 6BR.

https://www.centralnic.com