Re: [regext] Fwd: Datatracker State Update Notice: <draft-ietf-regext-bundling-registration-11.txt>

"Patrick Mevzek" <pm@dotandco.com> Mon, 21 October 2019 05:24 UTC

Return-Path: <pm@dotandco.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 D82751200C3 for <regext@ietfa.amsl.com>; Sun, 20 Oct 2019 22:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=lTrkMXuk; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=bryp/RgJ
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 2XRRKtIfQKvx for <regext@ietfa.amsl.com>; Sun, 20 Oct 2019 22:24:32 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 903D21200B8 for <regext@ietf.org>; Sun, 20 Oct 2019 22:24:32 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id BF462361 for <regext@ietf.org>; Mon, 21 Oct 2019 01:24:31 -0400 (EDT)
Received: from imap1 ([10.202.2.51]) by compute3.internal (MEProxy); Mon, 21 Oct 2019 01:24:31 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=kYY72Z11JXRNb9NDJ90YmTHoKoNU5wH 3iN9wKk+Ghpk=; b=lTrkMXukZ4NTUoL/5k+6bczR/qXhKKOtyxrrk6fGUBUOCDK 175wASTXPKuTuYgUfP1jZKU9TCYvC3qlgZLF5d+WE9pVpey1sR76c0NrhTAJDf8K 5igzEL4qOaQriNrOd4YYCm/P3Lxq0P1ODklYof6EgC9vXhSHV4vj9x7T1pJTAS5x nL/uejPV2abpCbC3C/X9wJfQHx6uw0/c8/rK8ZboqPDBWAv60eTR0SWj+E8y8vji fNBmzA9sjM6E8zEzigvGRbZn+x4byckcoqYTZf0YnQTL16+oeHr/HoDhm2yF8F/L j4KZavpnCCND34JatHztRKI4LwXPL3L+RF4+OuQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=kYY72Z 11JXRNb9NDJ90YmTHoKoNU5wH3iN9wKk+Ghpk=; b=bryp/RgJcSkRdDa3xdr9mn Nx2j2h5Kab8K6/N0CURMeQTO9qg5HJpat8XhgkxTjAPPlBuFvDAFTGayYXn1bRSF f6MB03PVTPGju7UvYWNX/Uf26TrxKLzo1BwOxaVGDEOfdw7sTPOrAL+aJRegt7Xh TOIP5Px2q0xWhP2P3SpG/DFJKnpBSdbaBNP816ZnltVfq8jn+VCVFO/xi3yKjO7L ApKXvb3zumf7XJz6wihDnGGiJ2wuZMOhUn0qy+XGlftClMjvuwnFHdCajJBc5NJr zO4sflvosQ+5dXXnfl+Uri8brSpJglBoWIYfnNq0NCBqybq781l6/0lHT60Rdvfw ==
X-ME-Sender: <xms:DkGtXdFPFz8BSa8ILckZVwrcHVtS9IuewgIRsSJxSEUAEvvdPTJ9pd6yQKs>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrkeeggdelfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreerjeenucfhrhhomhepfdfrrghtrhhitghkucfovghviigvkhdfuceophhmseguohht rghnuggtohdrtghomheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpmhesughothgrnh gutghordgtohhmnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:D0GtXZ86BplZdhpkqsDUAnspEpC8l1PAoPxYIFNUPsnitQdZmP88Cg> <xmx:D0GtXfXWrsLizdgqJdaWYnJcuSY0x291bpSN6Z0jUOk49jEgFqGlOQ> <xmx:D0GtXbGJLwAhEyWadHYef-xH3e6QNpRn_11Y1Nfh3KhLHyzhrp-roQ> <xmx:D0GtXTQzRHsJWGAfFlYpkVPXgGFxSYSLj8ZpeWgOTSsbGt2zyGL9sA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DF3F9C200A4; Mon, 21 Oct 2019 01:24:30 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-469-gd84f3d2-fmstable-20191021v3
Mime-Version: 1.0
Message-Id: <3979793f-e2c3-4ef9-9a4d-f7024bef713c@www.fastmail.com>
In-Reply-To: <CALaySJK-CtWonECFWWc0v+cTGFBv-JgbHLk=SSoQAegfTos=xg@mail.gmail.com>
References: <157116559901.28061.1061398353565107916.idtracker@ietfa.amsl.com> <CALaySJK-CtWonECFWWc0v+cTGFBv-JgbHLk=SSoQAegfTos=xg@mail.gmail.com>
Date: Mon, 21 Oct 2019 00:24:09 -0500
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/MZfdCNVhIpaZRzoXhPp43xTm94U>
Subject: Re: [regext] Fwd: Datatracker State Update Notice: <draft-ietf-regext-bundling-registration-11.txt>
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, 21 Oct 2019 05:24:34 -0000

On Tue, Oct 15, 2019, at 14:15, Barry Leiba wrote:
> I have taking this document out of IESG Evaluation state and put it
> back into Waiting for AD Go-Ahead.
> 
> Regext working group, please look at the reviews and decide how you
> want to handle this.  The document clearly needs some updates to
> address the comments we have, but in addition the WG needs to decide
> to...
> 1. ...continue processing this as an Informational document (in which
> case it needs to be made very clear why this is being handled by the
> working group and not in the Independent stream, or...
> 2. ...change the intended status to Standards Track and resume
> processing it as a working group document that way, or...
> 3. ...stop processing this document (change the WG status to "dead")
> and recommend to the authors that they take it to the Independent
> stream.

I am not sure I want to express my views on this because I am probably quite extreme and often not in the consensus (but my opinion could probably be summarized as: interoperability in this WG for EPP should probably have a minimum bar of 2 registries and 2 registrars, each one connecting to the 2 registries, and with every entity independent technically and administratively)

However, whatever comes out of this would be useful to capture into some generic
explanations so that the WG has (soft) rules, even maybe embodied in its charter,
or as an ID/RFC surely tied to RFC 7451, to be able to easily determine if a given submitted ID:
- should be considered as a WG document and the minimum set of criteria for that
- should be Standards, Informational or Experimental, and the criteria for each case.

I think by being clearer on this, it makes less confusion and future questions,
and enables one to make sure that the IETF is not just rubber stamping work being
done in reality outside it.

I quite remember having touched this subject in the past, already feeling the
split in views that may happen, as we see it now for that case.
If that path (working on defining some criteria to help in future cases) is of interest
to anybody and some work is started on it, I would be interested to join this effort.

-- 
  Patrick Mevzek
  pm@dotandco.com