[regext] [check] <reason> always prohibited when avail="1" ?
Stephane Bortzmeyer <bortzmeyer@nic.fr> Wed, 29 September 2021 11:01 UTC
Return-Path: <bortzmeyer@nic.fr>
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 5E0383A0DA5 for <regext@ietfa.amsl.com>; Wed, 29 Sep 2021 04:01:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 I0jkY2WkuWpg for <regext@ietfa.amsl.com>; Wed, 29 Sep 2021 04:01:40 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 125173A0DA3 for <regext@ietf.org>; Wed, 29 Sep 2021 04:01:39 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id B7BD6280BCB for <regext@ietf.org>; Wed, 29 Sep 2021 13:01:36 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id B2B34281169; Wed, 29 Sep 2021 13:01:36 +0200 (CEST)
Received: from relay01.prive.nic.fr (relay01.prive.nic.fr [IPv6:2001:67c:2218:15::11]) by mx4.nic.fr (Postfix) with ESMTP id AB6A1280BCB for <regext@ietf.org>; Wed, 29 Sep 2021 13:01:36 +0200 (CEST)
Received: from b12.nic.fr (b12.users.prive.nic.fr [10.10.86.133]) by relay01.prive.nic.fr (Postfix) with ESMTP id A8330601C000 for <regext@ietf.org>; Wed, 29 Sep 2021 13:01:36 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 992A6400A8; Wed, 29 Sep 2021 13:01:11 +0200 (CEST)
Date: Wed, 29 Sep 2021 13:01:11 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: regext@ietf.org
Message-ID: <YVRHd64Ec8ZyOH+x@nic.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
X-Operating-System: Debian GNU/Linux 11.0
X-Kernel: Linux 5.10.0-8-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
X-Bogosity: No, tests=bogofilter, spamicity=0.008128, version=1.2.2
X-PMX-Version: 6.4.9.2830568, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2021.9.29.102715, AntiVirus-Engine: 5.86.0, AntiVirus-Data: 2021.9.29.5860000
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/t-v1MjzKLPI6ZoQZMCj3jdb2tFA>
Subject: [regext] [check] <reason> always prohibited when avail="1" ?
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: Wed, 29 Sep 2021 11:01:43 -0000
RFC 5731 3.1.1 seems to clearly prevent a <reason> to be sent when avail="1". But RFC 9095 6.1.1 has an example with a <reason> for avail="1". So, is it really forbidden to send a <reason> to the client when the domain is available but you want to send some extra conditions?
- [regext] [check] <reason> always prohibited when … Stephane Bortzmeyer
- Re: [regext] [check] <reason> always prohibited w… Thomas Corte (TANGO support)
- Re: [regext] [check] <reason> always prohibited w… Gould, James