User-Agent: Cyrus-JMAP/3.1.7-694-gd5bab98-fmstable-20191218v1
Mime-Version: 1.0
Message-Id: <185b57cd-984c-4167-8e62-fc37dcf46fdf@www.fastmail.com>
In-Reply-To: <4bbb8a33bee54a8797fc75a1cf532899@switch.ch>
References: <d17d88d0-e9db-9416-1917-dc992fcd2d3a@switch.ch>
 <35BAECA0-9B4A-4C1F-9EEF-BA9C4BE2E325@verisign.com>
 <4bbb8a33bee54a8797fc75a1cf532899@switch.ch>
Date: Fri, 20 Dec 2019 04:06:06 -0500
From: "Patrick Mevzek" <pm@dotandco.com>
To: regext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/cn6eeSizf9ga0GL6vnUImCbbUPc>
Subject: Re: [regext] 
 =?utf-8?q?How_to_handle_Domain_Info_Command_with_empty_?=
 =?utf-8?q?authinfo/pw_tag_in_command=3F?=
Precedence: list



On Fri, Dec 20, 2019, at 03:50, Martin Casanova wrote:
> I agree that hashing an empty String to match a not set authinfo is not 
> the way to go. We are using [null] values in the db for a not set 
> authinfo field. However I think you could argue that semantically and 
> empty XML tag is somewhat similar to a not filled db field being [null] 

I strongly disagree.
It is the same thing as the difference in an RDBMS when you store "" (the empty string)
or NULL (the undefined value). Those are two different things, and for good reason.

<pw/> or <pw></pw> means an empty password, the empty string.
No XML pw node means an undefined password, as the data is just not there, so unknown.

Like said in other threads, this all shows to me that efforts should be put
into finding now new ways to operate, without domain passwords as they became
useless, instead of trying to fix with various warts the current situation.

-- 
  Patrick Mevzek
  pm@dotandco.com