Re: [regext] [Gen-art] Genart last call review of draft-ietf-regext-bundling-registration-09

Antoin Verschuren <ietf@antoin.nl> Fri, 15 March 2019 14:13 UTC

Return-Path: <ietf@antoin.nl>
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 6B1A9130E5A; Fri, 15 Mar 2019 07:13:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=antoin.nl
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 juo_kHiFYAsi; Fri, 15 Mar 2019 07:13:13 -0700 (PDT)
Received: from walhalla.antoin.nl (walhalla.antoin.nl [IPv6:2001:985:b3c0:1:e2cb:4eff:fe5e:3096]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4006130E7F; Fri, 15 Mar 2019 07:13:12 -0700 (PDT)
Received: by walhalla.antoin.nl (Postfix, from userid 5001) id 220782804C4; Fri, 15 Mar 2019 15:13:10 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=antoin.nl; s=walhalla; t=1552659190; bh=9tG+tLrZEJsuJZjsGa8kBMXsq6Ty9+EG5/OXbqgDK0U=; h=From:Subject:Date:In-Reply-To:Cc:To:References:From; b=buJ9eOktGQj84qRRWhs80hVirqCsFQP0fjxmFNXHsBzi9qfiJfLYczUjGiCMG+T2h gyz6LiISq0QrEQ8UP+OYsHA7J/rFGpI6AgSw/WW1EnkVNktNYP/Ya6R3N5CzgScBIW 825+Z6IWBbj1kzQKdd5kfL+Tsxq/ERvROy3Y1WKM=
Received: from [IPv6:2001:985:b3c0:1:7018:41f0:aa2b:35f3] (unknown [IPv6:2001:985:b3c0:1:7018:41f0:aa2b:35f3]) by walhalla.antoin.nl (Postfix) with ESMTPSA id 4A83C28024D; Fri, 15 Mar 2019 15:13:08 +0100 (CET)
From: Antoin Verschuren <ietf@antoin.nl>
Message-Id: <9441F8B1-AD27-4B2B-A296-AC118A741A5A@antoin.nl>
Content-Type: multipart/alternative; boundary="Apple-Mail=_4BA1ED50-338B-49BA-9036-71B5B0C844E1"
Mime-Version: 1.0 (Mac OS X Mail 12.2 \(3445.102.3\))
Date: Fri, 15 Mar 2019 15:13:07 +0100
In-Reply-To: <57d81b46-5d94-6044-7ab1-d7763997d63e@joelhalpern.com>
Cc: Jiankang Yao <yaojk@cnnic.cn>, gen-art@ietf.org, draft-ietf-regext-bundling-registration.all@ietf.org, ietf@ietf.org, regext@ietf.org
To: "Joel M. Halpern" <jmh@joelhalpern.com>
References: <155200161246.5468.7896585235201756105@ietfa.amsl.com> <2a26b767.b09.1697f5a3e96.Coremail.yaojk@cnnic.cn> <57d81b46-5d94-6044-7ab1-d7763997d63e@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.102.3)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/wPQdna8E6eHkF4co4XDxrNzHPls>
Subject: Re: [regext] [Gen-art] Genart last call review of draft-ietf-regext-bundling-registration-09
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: Fri, 15 Mar 2019 14:13:21 -0000

- -- 
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392






> Op 15 mrt. 2019, om 04:27 heeft Joel M. Halpern <jmh@joelhalpern.com>; het volgende geschreven:
> 
> While the status is between you and the IESG, in my experience it is very unusual for the IETF to define a protocol in an Informational RFC. (I presume there are some exceptions.)  The obvious move if the WG does not want to publish it as standards track is to publish as an experimental RFC.
> 
> Failing that, I hope that you have provided more justification than "this is what the WG chose" to your area director.

I think there is a slight misunderstanding here about the document status and IANA registration.
The EPP extension registry has 2 types of registrations:
(see https://datatracker.ietf.org/doc/rfc7451/ <https://datatracker.ietf.org/doc/rfc7451/>)

1. EPP standard track registrations:
These extensions have had thorough review and have consensus that these are standard extensions.
These EPP extensions will point to the IESG in the IANA registry (RFC 7451 section 2.2.1)

2. Proprietary EPP extensions
Extensions that seek registration in the IANA EPP extensions registry, but are only supported by one or few registries.
These extensions should be documented and one way of documenting them is to write an informational RFC describing how the proprietary extension works.
These EPP extensions will have the Registrant information in the IANA registry, which is NOT the IESG!

draft-ietf-regext-bundling-registration is of type 2 since the REGEXT WG could not reach consensus that this extension should become the standard way of bundling. Hence the informational status of the document and the Registrant should be in the IANA registration as mandated by RFC 7451.

- -- 
Antoin Verschuren

Tweevoren 6, 5672 SB Nuenen, NL
M: +31 6 37682392