Re: [regext] Picking XML namespaces

Patrick Mevzek <pm@dotandco.com> Tue, 06 November 2018 06:52 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 E92EC1277C8 for <regext@ietfa.amsl.com>; Mon, 5 Nov 2018 22:52:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dotandco.com header.b=P9LaWj19; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dfPt0Uxo
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 eoI3Gmmk5w3U for <regext@ietfa.amsl.com>; Mon, 5 Nov 2018 22:52:20 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D20D112777C for <regext@ietf.org>; Mon, 5 Nov 2018 22:52:19 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 183F9225B7 for <regext@ietf.org>; Tue, 6 Nov 2018 01:52:19 -0500 (EST)
Received: from web6 ([10.202.2.216]) by compute3.internal (MEProxy); Tue, 06 Nov 2018 01:52:19 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= message-id:from:to:mime-version:content-transfer-encoding :content-type:references:in-reply-to:date:subject; s=fm1; bh=Y6/ JlBMVQrXnuSU3sXeIBZDnsVYl7Wr9EW+Gd/cvmq4=; b=P9LaWj190LhPjQx+ifM IpFmTbqISeCdiwuFL38hQpU0NbQpGGJ8xXRHsFVO5OVoRCrPFhJ3bzcPf6m3h9b5 BuvBVVxojSzRChqEGYeAJKhshZhzOkVKFKURAy8TPevEN7/l7k1zCxU+2FaJQf8g +5zQ5x78EBXlQNkSNLamOax4IFLfRK052RkNIAZjEXKzjoeR3aCxPcBGbNQqWQPk /YnUxZpkxCn3mKQ9q6/kFgh6s8A+AQA7tEoAP2ZSdJJtltojSDvKMoBqyUTxGN0r oz3KXLlZc/oCLUYm3JsTGnxc04m+Sr0bgGiYwHscd54wEZIh7s/rKazUeBF7RUOn tVA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding: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=fm1; bh=Y6/JlBMVQrXnuSU3sXeIBZDnsVYl7Wr9EW+Gd/cvm q4=; b=dfPt0UxoLeNtUHsAqwl3JaI9ayDaLugUZ7KtSV2obgNAN6yHS0F7WHBKK mz5QSo4Ap3q5II6qeA3E1dOuMuUTqe61U+EkubZ3Lc84vHfjzcu/L68VH29zQkz+ Me5lrqyzeYJWJWyu/CdeeLS2MMW/uYKd6+aj4+HgLZdqoDQHgt1vdWyW8nTjBwUT 2iEcpqCLk8LDTgNYHp6kQwtnN94wE5vLuKJH8DkFez99A7IsXjxc/fXWUNcsi9Rf k53HI01vPaMIzlGMeCikOJeV0SX6YToXQs8QXe6KLFX9O7WnIZRcm7OhlkBaRCri H3HxhsawriT5ifvMTnXoZzW7qJnvA==
X-ME-Sender: <xms:IjrhWxjI02cpU3t6j81DAqYXYQNDvwAv0HfX_dr8Gip3SEfcCX8FbrgBRgE>
X-ME-Proxy: <xmx:IjrhW5d7zEdv4GMXkwYAT_SmEsQLRiE07vjVoNllWnqXm4k_FfMVRw> <xmx:IjrhW4ngaIwGS5EcwASJNECdP2hHqaoa-C2W0yw9Ls5xNQlOje4M6w> <xmx:IjrhW7xvZWqIeH8DU5J_GSeG3kHGtHA0vfP1Ov2tffoofpOs8ZRglQ> <xmx:IjrhW7Mx2nxsyoGYxP_YBv2LjfCPxssxKL5Mo9NnpIwTftns1ViLvg> <xmx:IjrhW8gEOFKRgxkUK5kuP6BS2oHkq52IUu6DOxiIFvHgmBp_rzATJA> <xmx:IzrhW0iDWvG9VAUjlbCBuuqVJfvmvsDO2X_n_zvfnCchl2N0OUH5lg>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id AAD2C4250; Tue, 6 Nov 2018 01:52:18 -0500 (EST)
Message-Id: <1541487138.3877532.1567053496.6E846CD0@webmail.messagingengine.com>
From: Patrick Mevzek <pm@dotandco.com>
To: regext@ietf.org
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="utf-8"
X-Mailer: MessagingEngine.com Webmail Interface - ajax-d469da0c
References: <CABkgnnVALJ7kB-LpUFq3BtmMfNtVHbxfOaiQceKjN4gRZ3NRYw@mail.gmail.com> <6B4DDD24-06C8-4EFF-A844-57D2F8B60F72@verisign.com> <CABkgnnVrqQRGS8PsQiHxuCrZy91pMzBeOTScDAbZUu9g2Be7Sg@mail.gmail.com> <EA0B408F-B4F6-4A80-99D2-F2A7C5295F82@verisign.com> <1541481433.3854216.1566997696.4FD35EED@webmail.messagingengine.com> <AA77079B-3291-43B5-BCBC-EC82A472FCC2@verisign.com>
In-Reply-To: <AA77079B-3291-43B5-BCBC-EC82A472FCC2@verisign.com>
Date: Tue, 06 Nov 2018 07:52:18 +0100
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/cUc0tkfu5upN7kogYzggqLM5YWc>
Subject: Re: [regext] Picking XML namespaces
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, 06 Nov 2018 06:52:22 -0000

On Tue, Nov 6, 2018, at 07:08, Gould, James wrote:
>
> I believe that there needs to 
> be a compelling reason to make the change, such as an IANA namespace 
> conflict, to justify making the namespace change on extensions that will 
> have operational impact. 

As far as I know there is no real conflict whatsoever for any of the current XML namespaces used by every draft on EPP extensions, so by this same argument
(since multiple other documents could be said as already implemented "somewhere"
and hence having an operational impact for at least one actor)
you could arrive at the conclusion that not a single document we have on the table should be updated regarding the namespace it uses.

Also by the same single argument, any draft that kind of have an Implementation Status may be said to be operational in some way by some actor and hence any single change in it could be rebuffed by saying "We can not change it, it is operational already".

And I would still disagree.

Like I said, I believe that most arguments there could be used in the same way for any
of the documents, so they should apply uniformly. Either no document is updated in that regard or all are, whether they are already implemented somewhere or not.

But after having expressed my concerns, I will not push further on this and just remain in agreement with Martin's first message on the issue.

-- 
  Patrick Mevzek
  pm@dotandco.com