[regext] Mirja Kühlewind's Discuss on draft-ietf-regext-bundling-registration-11: (with DISCUSS)

Mirja Kühlewind via Datatracker <noreply@ietf.org> Tue, 15 October 2019 23:29 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DD3612080E; Tue, 15 Oct 2019 16:29:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Mirja Kühlewind via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-regext-bundling-registration@ietf.org, Joseph Yee <jyee@afilias.info>, regext-chairs@ietf.org, jyee@afilias.info, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.105.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Mirja Kühlewind <ietf@kuehlewind.net>
Message-ID: <157118218724.28032.11960770549771220835.idtracker@ietfa.amsl.com>
Date: Tue, 15 Oct 2019 16:29:47 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/VvUehRG_wg9tKzaqaO5illumAUw>
Subject: [regext] Mirja Kühlewind's Discuss on draft-ietf-regext-bundling-registration-11: (with DISCUSS)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 15 Oct 2019 23:29:47 -0000

Mirja Kühlewind has entered the following ballot position for
draft-ietf-regext-bundling-registration-11: Discuss

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/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


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



----------------------------------------------------------------------
DISCUSS:
----------------------------------------------------------------------

I’m not certain about the intended status of this document. I understand that
this was discussed in the group but this document does specify a protocol
extension and as such Proposed Standard or Experimental would be the two usual
choices. The shepherd write-up mentions that this extension only has a limited
scope, however, not sure what that is supposed to mean and it also doesn’t
seems a good reason for informational (but experimental maybe). There are
informational RFCs that document protocols of existing deployments for
informational purposed only, meaning that there is a good reason to have a
description of an existing protocol in a stable reference while the process of
publishing the RFC would not change any technical means of that protocol but
only document what’s out there. Usually these kind of RFC have a title like
“Campany’s X protocol for something”. However, this seems not to be the case
here or at least it's not clear from the content of the document.