Re: [Gen-art] [regext] Genart telechat review of draft-ietf-regext-bundling-registration-11

Barry Leiba <barryleiba@computer.org> Tue, 15 October 2019 18:19 UTC

Return-Path: <barryleiba@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69737120805; Tue, 15 Oct 2019 11:19:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.478
X-Spam-Level:
X-Spam-Status: No, score=-1.478 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.172, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 c3voPGTQU5bM; Tue, 15 Oct 2019 11:19:25 -0700 (PDT)
Received: from mail-io1-f49.google.com (mail-io1-f49.google.com [209.85.166.49]) (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 562751207FC; Tue, 15 Oct 2019 11:19:25 -0700 (PDT)
Received: by mail-io1-f49.google.com with SMTP id h144so48151982iof.7; Tue, 15 Oct 2019 11:19:25 -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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=9ow0ZOB5b5wtQvgHb7O9Q9rbpN6i+t943h+4qOc3Qmw=; b=TrZ4JbzzdB7c2I1mLst3qpYPlKTG7E4jh94s7l90KDCMseX7wyOgwgz/B1gHx20aSR yieW8yfg8xhtN4qm9Woa41pKFg8Zez0guWVwVZSt7A8BzPXM7uuHCjvZmwCkzWyB7Nrk OZZsnTxZR3RDisnH5To9EAlE2X5kjOIiqM2QsW2wJLq2IetU129+CFKSM3l1hoOCNm6y D19pjvx+tj+ej5TvF47MSva2z05kcSxuAUG+tati5UlZKZWeGRUUGCh5XAo2AWFB/dKh fPMW5OncTmRIHLjQ5/RCQ9wXPpAvTDA9mfsYoyJjpxODJsjjAvVU8Uxtw8eYmTTkL5F/ ZdUQ==
X-Gm-Message-State: APjAAAWC9Yp6nUJij8vqTRm22fd/leZDmO4T9/DZ0LqWmkCK1UITd42Z E47ujTWfYvp4rScgTupilGtQdX9WleP1T8CSf/ZmX5vO
X-Google-Smtp-Source: APXvYqwcdBHekq8EKlEA7Y+jF7vJ90kDlAbjjSuj7CP/fQeFW+dVhkOneW4WXteIdxyYxlsAvkMHsZVAZFqmmw3f0X8=
X-Received: by 2002:a02:69cd:: with SMTP id e196mr23119341jac.88.1571163564325; Tue, 15 Oct 2019 11:19:24 -0700 (PDT)
MIME-Version: 1.0
References: <157074817849.20459.11318968277639852496@ietfa.amsl.com> <754e85cd.1470.16dce6a353a.Coremail.yaojk@cnnic.cn> <cffa265b-5df3-fdea-f57a-7af30880a154@joelhalpern.com> <5D394E0244700A5D092F1181@PSB> <c32157cf-3b18-fd01-9f0d-29bd6f4d4645@joelhalpern.com>
In-Reply-To: <c32157cf-3b18-fd01-9f0d-29bd6f4d4645@joelhalpern.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Tue, 15 Oct 2019 14:19:12 -0400
Message-ID: <CALaySJLpf63gG811=az6oEfSV4hu20KDJn_rSXJ=gZQQ+OKsZw@mail.gmail.com>
To: Joel Halpern Direct <jmh.direct@joelhalpern.com>
Cc: John C Klensin <john-ietf@jck.com>, Jiankang Yao <yaojk@cnnic.cn>, General Area Review Team <gen-art@ietf.org>, "draft-ietf-regext-bundling-registration.all" <draft-ietf-regext-bundling-registration.all@ietf.org>, IETF discussion list <ietf@ietf.org>, regext <regext@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/KOjfI-icf0hDZN3ekLucjSyCy7I>
Subject: Re: [Gen-art] [regext] Genart telechat review of draft-ietf-regext-bundling-registration-11
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 18:19:27 -0000

> If we do not have agreement on what the meaning is for the relevant
> terms, then either
> 1) The document should not be an IETF consensus document (which even
> Informational publication is)

Just a point on this: it's not true.

We have a "consensus" flag in the datatracker, which triggers a
boilerplate change.  It's always set to "yes" for Standards Track or
BCP, but for Informational and Experimental it can be set either way.
If it's set to "no", the boilerplate says that the document does not
have IETF consensus.  It's possible that when we're done with this
document it could settle into that.

It's also possible that we might convince the regext working group to
stop processing this document and suggest to the authors to go to the
ISE.  I don't think we're there yet, and at the moment the working
group has consensus to publish it as a working group product

Barry