Re: [regext] review of draft-ietf-regext-login-security-03

"Patrick Mevzek" <pm@dotandco.com> Tue, 09 April 2019 21:26 UTC

Return-Path: <pm@dotandco.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 9440C120357 for <regext@ietfa.amsl.com>; Tue, 9 Apr 2019 14:26:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=u1HBA0dv; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=1ykUJtyg
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 k1iRz0UV6tF2 for <regext@ietfa.amsl.com>; Tue, 9 Apr 2019 14:26:52 -0700 (PDT)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61079120342 for <regext@ietf.org>; Tue, 9 Apr 2019 14:26:52 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 17ACF2563B for <regext@ietf.org>; Tue, 9 Apr 2019 17:26:51 -0400 (EDT)
Received: from imap1 ([10.202.2.51]) by compute3.internal (MEProxy); Tue, 09 Apr 2019 17:26:51 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm2; bh=BjzU92ImcHHX6RE+TO0XezIzh1UgBq/ SbZ+Ez5Wcs5A=; b=u1HBA0dv3TCaLXWmqsiVRu69Tysd3w6751Oruh/1FF5/k7M 0C+TlByuqRg5MsGeIwMw3wF2/SMf3fMCO0FpYLswzNeS629kZGZPjVR4VNALxmn6 yIoRC3szcEAyIIdKVZZ9rqHEdfLjbjZeOEG85yvirl4ifxgXaPkHHa1LuSIW2spK zBvP+VuHnaYWFhZBX4uXOD7GPAt17MeP49ZMwLFTtwyABT5LiLlXktfciRrm9l2N ezm1rziKPKsbG04ZQZr919vAjWHoJI6cMk4j3Bl3B5zzZqYZMgOghpi+0vZ/vEi9 S34LPX5Cj9IFlgrwi4dQPFog6quD3yegg3OF2Wg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=BjzU92 ImcHHX6RE+TO0XezIzh1UgBq/SbZ+Ez5Wcs5A=; b=1ykUJtyg9FfKqVWNJR+2Ex ABKAzY5q/I3erJdYySe27gXc7j/sZMGTBarlOActEe3DLaw6xUqKzOVuEirEcFoT s9FxCEP3kYg1v6f+8gF9hieEXdRLBFHfkNtpcMk1ddjxOkpcUXnv+JG3tai4at3b YMePeh9AjXQgQfYqxxecfDqE7Vj/wiTKG1D99i3E5MvZTl1WNvt6sb81xvrB5IBw sfDsRDkeDzTw2gT93kdnr+a6YIFn5lf8YFkuSC2Iw0+CQlw9wfE2BcsOlyy+9OfO Ijcpfqp9BgOqB0EPsHtpv8wxBop5irjCgLaTjRiAEAc2TiTA8i+wlwNXf/7SA1tg ==
X-ME-Sender: <xms:Gg6tXJX7-MYWkvwXRbDbkGzDUwYCurBtOWdNw75z0S5zFR8PauZhIGkIddU>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudehgdduiedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfrfgrthhrihgtkhcuofgvvhiivghkfdcuoehpmhesugho thgrnhgutghordgtohhmqeenucfrrghrrghmpehmrghilhhfrhhomhepphhmseguohhtrg hnuggtohdrtghomhenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:Gg6tXHKR7IAreepvM3RBtmPBpWaukUd1TB7ARnzBYIT_wbL1BwJHnw> <xmx:Gg6tXOZR4C2tb9PrINdr8zWqBBbYTXLiwBa0eUEsomyZTm3IPPfang> <xmx:Gg6tXHNfQopex9UKZckpjf4iabN5iYpmU6L1OrSv7eSeig_PboPNBA> <xmx:Gw6tXFjfb9unOHu2fGbzrWIoTlqKFyKEUrHRmoXI_pmG0gZV767lNw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7CF87D48AB; Tue, 9 Apr 2019 17:26:50 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-329-gf4aae99-fmstable-20190329v1
Mime-Version: 1.0
X-Me-Personality: 66173168
Message-Id: <5701cfe6-ef44-4a6f-a1fa-74530aada875@www.fastmail.com>
In-Reply-To: <F66B4693-C2BF-4E5A-B360-6433C5026EDF@verisign.com>
References: <afac0d26-e054-54a3-306b-5ec5a49fd489@switch.ch> <7597ff38-29ba-77e3-e093-524c5cb7123a@switch.ch> <878793C3-AE5B-4364-AA0A-572467EDB0D6@verisign.com> <fa8f12c3-851b-d29a-969d-605120704ed6@switch.ch> <BE4C3FDB-0A1D-4C6F-87C7-6D9CDDB09E10@verisign.com> <b692be9f-6123-42f5-b8a8-a4bbfb986e73@www.fastmail.com> <F66B4693-C2BF-4E5A-B360-6433C5026EDF@verisign.com>
Date: Tue, 09 Apr 2019 17:26:50 -0400
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/hJ16C56oAjyfTn9TbTlW5JKUU4c>
Subject: Re: [regext] review of draft-ietf-regext-login-security-03
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: Tue, 09 Apr 2019 21:26:55 -0000


On Tue, Apr 9, 2019, at 16:19, Gould, James wrote:
> I believe the most important aspect is that there are three separate 
> sub-elements to make the <loginSec:userAgent> element structured.

If you just want to record a structure with 3 elements, a sequence is enough,
you do not need explicit naming of each item.

> There will not be any confusion with "tech" contact attribute value and 
> the draft describes the meaning of each of the sub-elements.

You could have then arrived to the exact same conclusion with this reasoning for the "lang" attribute, yet you changed it. So we could as well go back to "lang" now.

For the record, I am against both "lang" and "tech", but those are minor points, like expressed previously I think there are other problems more important but I won't reiterate and I would be happy to see other registries implementing it, simply as there is no other option on the table anyway.
But again if we go the whole standardization process for an extension used only by a few players, I am not sure how much of the "E" in "EPP" we do leverage. Or if we leverage it too much in fact.

As in other cases, it would be good to see other registries/registrars voice their opinion, or even better implement it or something else or explicitely not for some reasons, etc.

-- 
  Patrick Mevzek
  pm@dotandco.com