[regext] AD review of draft-ietf-regext-tmch-func-spec-08

Barry Leiba <barryleiba@computer.org> Thu, 23 July 2020 20:45 UTC

Return-Path: <barryleiba@gmail.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 CD0593A0DE2; Thu, 23 Jul 2020 13:45:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 MItf5zfuCqf2; Thu, 23 Jul 2020 13:45:02 -0700 (PDT)
Received: from mail-io1-f41.google.com (mail-io1-f41.google.com [209.85.166.41]) (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 B1B0D3A0DA4; Thu, 23 Jul 2020 13:44:59 -0700 (PDT)
Received: by mail-io1-f41.google.com with SMTP id q74so7722015iod.1; Thu, 23 Jul 2020 13:44:59 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=uCacmAps5fOkpQIHcBNx+Qlkc/S/fdtYD9boE9qMptw=; b=LqqVOilnl28ds84m6Q+6ol8ukxz1udsKp9yGl2FspnCcTC+1haX/5hcVJPf0Ir6nDR a37u8x9FWJIfEtpE619yd0aYiO8gTOP5Zu5JjsyF4+iqAj1ftlzf+SiKb0DdhqiZu8dY E+tZFmdWBWU6uAvkJ5Wi6wPgkILwOISi4wGZc6CnApmn8ecKZ2O/kWSDw93WHIneV+L6 xL2dd7Pfcwh8lnz5XzCGQuBSQdXdxzxrcqu3hKmgnILmnLhr/I4OOixv3IZ9k5jGvMk+ ZvgpPt9/3O839lnuUTocsJVRdHStwz3Jdg58uUAemAeWpHI7rm6zpqNOWGFkPRVZ/9Hv xh8g==
X-Gm-Message-State: AOAM531PaTy7y9DbfiRve5+W3r1v3HByCa3TsReDMjUqiCwm3tAZ5GVK DkAO2JvJ2iymDpxkl4HHva2NGlNuHwytwF72XVrWsw==
X-Google-Smtp-Source: ABdhPJwZ7/DroZCzIxuGfURDkz1HGrEZe0NLPDg9KUrFf6ZFPwk1yzQ2RL+MPfqKoG8gjlEywxvETYLugTaVcQa3DWY=
X-Received: by 2002:a02:7419:: with SMTP id o25mr6747199jac.46.1595537098508; Thu, 23 Jul 2020 13:44:58 -0700 (PDT)
MIME-Version: 1.0
From: Barry Leiba <barryleiba@computer.org>
Date: Thu, 23 Jul 2020 16:44:47 -0400
Message-ID: <CALaySJKMQ9Ktg-voR-WDjRU+QvdSCS0GZ1C78+maMsYuWo4vbQ@mail.gmail.com>
To: draft-ietf-regext-tmch-func-spec.all@ietf.org
Cc: regext <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/uj2RlaJNXPEeSFuAthr2g2sKlM8>
Subject: [regext] AD review of draft-ietf-regext-tmch-func-spec-08
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: Thu, 23 Jul 2020 20:45:09 -0000

First: Please accept my apology for the delay in handling this
document.  It's been a particularly busy time for the ADs, and I've
let this slip for a lot longer than I'd thought it would.

My main comment about this document is that I find it odd as a working
group document: it strikes me as something that ought to be published
by ICANN as a policy document, not as something that should come out
of an IETF working group.  An alternative path in the RFC series would
be through the Independent Stream, which allows publication of
Informational documents without getting IETF consensus.

What, exactly, would IETF consensus mean for this document.  As it's
describing an operational external system, we don't really have the
ability to change it.  All we can do is decide to publish it... or
not, yes?

I think it will be very hard to sell this to the IESG.  Will the
working group consider an alternative path for publishing this (ICANN
or the ISE, or something else)?

Barry