IETF Logo Mail Archive

Re: [regext] Poll messages with unhandled namespaces (was Re: I-D Action: draft-ietf-regext-change-poll-07.txt)

Patrick Mevzek <pm@dotandco.com> Thu, 24 May 2018 04:23 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 87AD712D941 for <regext@ietfa.amsl.com>; Wed, 23 May 2018 21:23:43 -0700 (PDT)
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=F7lORps0; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=FwO2rDts
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 6bBmP3x8-ufd for <regext@ietfa.amsl.com>; Wed, 23 May 2018 21:23:42 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F04D7127275 for <regext@ietf.org>; Wed, 23 May 2018 21:23:41 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0A59321DFB for <regext@ietf.org>; Thu, 24 May 2018 00:23:41 -0400 (EDT)
Received: from web3 ([10.202.2.213]) by compute3.internal (MEProxy); Thu, 24 May 2018 00:23:41 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dotandco.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm3; bh=1LSo2AI3aI++DYRFO8mbdmsl9GBoo kbGA5bBH5b9Ss0=; b=F7lORps08I4ue2PxsICyBKDBcKXLGmAbxS72i3P90vcYo w109OPoH6I/kINRG5jnx3vKbqBwIdCC39VYgkca+aS4EGl80gKSWyfOkbsHr3eJQ nHh+qp/IFfArJpuJAqBIwz+Ce+8yWOtALnKsZ5tRAH/Yg7M63SagS5dwMoxDiIgn 8e6GfDkiR2tmYGNYgUYlJy71UgFfWmNx//jiS3TjZxLmxu0xdE1UteqtExeVXg+E BnByStx5Au1FS+s2+H/yeCc1UhcmG8pGjMtk64vL20BrMCp9HbWlSAy1LT2noV3H AKNyWgIaX/0eiPiaUzhzZEvJs8Huj5uxgrCRLHkNQ==
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-sender:x-me-sender:x-sasl-enc; s=fm2; bh=1LSo2A I3aI++DYRFO8mbdmsl9GBookbGA5bBH5b9Ss0=; b=FwO2rDtsBEVUaDO6YH2toR i43AC64daHHGUzPpNMTy6fQGQwKVzU/9CKKkKMnHZpWi5t4VwDGHp//HAuwrkAjb BRRx/xH1BO993+hPvI61zwFS/6eXp064u9FaDkYw67LBq0CCELdUKhMAQ8n3C+Uc OuffqNQ2A8goTV51bSGTm7n+r2H6jVDG5WJsHWZWQe69A4uDGCIvehKnq+B/cIJA mEpjyu5ZtjhKQPehfJh7X+/Gq+/LkKMit9sgx5NZ40R/EUuT3ynOnoLHVYD5X76C mWSiAlmQxcRrsoCMwy63tOvVe6ZXyfQoFG3A1B0cUj8vgzfYLtFGdR03ycsLDakg ==
X-ME-Proxy: <xmx:TD4GW93bQGbA1CsdGh37PpTNITOZ5hxGczDqE7QR-x1G9XFHqaWTPQ>
X-ME-Proxy: <xmx:TD4GW0QhK1lNDfpMCgDy-WFV05eaFcKnjwcZIz5liUmer9RDg8xToA>
X-ME-Proxy: <xmx:TD4GW_uKyoFLK1cJ_dX1zm1jdf4iRUqXBzudjLrdkORSzmWPcL2jsw>
X-ME-Proxy: <xmx:TD4GW5YsRe806tzhd5te6LuWz2FzKn0uLu7KB1a3Brd9v0aGXEpHBw>
X-ME-Proxy: <xmx:TD4GW0urYtLdeIwr_G_ajGdLIYqgbEoeqZhc8FhH-RtTB88SA4GCKw>
X-ME-Proxy: <xmx:TD4GW6i-gGJz0Ew4LfHWKg-kc6A8UjZKBaDZP8Chmdz2Iy5D27eDkw>
X-ME-Sender: <xms:TD4GW3g2SmjTFvINuiKmtWoNm9PvqnKB5EXb85EONucJWp2BU6RSUpq3pwk>
Received: by mailuser.nyi.internal (Postfix, from userid 99) id BE9E19E196; Thu, 24 May 2018 00:23:40 -0400 (EDT)
Message-Id: <1527135820.1779071.1382936736.3093914E@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-a224ff37
References: <3266784A-E663-4465-8ABF-A3305B83C253@verisign.com> <e7916b75-1555-14e3-43bc-644059cd68f0@switch.ch> <605AC23F-D7B3-4A37-876E-45EC8E6BEEB8@verisign.com> <84309e91-dbe9-8865-fd06-528266aa93e7@switch.ch> <FAFB62AE-C0D1-4D74-888C-00C632D73211@verisign.com> <1522912361.3587146.1327243736.6AB5A07D@webmail.messagingengine.com> <58605AC6-A8B3-4428-A71E-580E6BC01EFF@verisign.com> <1524032366.3941888.1341940112.7D43F230@webmail.messagingengine.com> <BEC1040F-25C7-4F52-BB94-1F55BFA4C1C7@verisign.com> <1524203922.4022062.1344535160.39F0C10F@webmail.messagingengine.com> <83479150-4E98-452F-B27B-BD286AA18C1B@verisign.com> <1524425212.2370983.1346768616.2A2DE208@webmail.messagingengine.com> <48889EC8-FF2C-4CF3-B5E1-9DC5482E06E9@verisign.com> <CF701CA2-F63A-4573-AB87-68E3AB30C635@elistx.com> <5743B914-A1C7-426C-B0AA-515A3AEB5C72@verisign.com> <CY4PR02MB254962B12D6D196EACE492AEB1860@CY4PR02MB2549.namprd02.prod.outlook.com> <8A5C829F-BB67-4BA2-8E3E-5A4002D7D2CA@dnsbelgium.be> <1526875928.815044.1378899224.71EFB177@webmail.messagingengine.com> <F9BD7DC9-8472-438E-BDDD-8658A0D0A841@verisign.com> <1526973885.2320203.1380323248.3A725D0E@webmail.messagingengine.com> <96AC029A-47E4-4729-8297-571F9A34FE6C@verisign.com>
Date: Thu, 24 May 2018 06:23:40 +0200
In-Reply-To: <96AC029A-47E4-4729-8297-571F9A34FE6C@verisign.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/XVsVRIlXK9tH1y_iduDseNpEdFA>
Subject: Re: [regext] Poll messages with unhandled namespaces (was Re: I-D Action: draft-ietf-regext-change-poll-07.txt)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.22
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: Thu, 24 May 2018 04:23:44 -0000


On Tue, May 22, 2018, at 14:23, Gould, James wrote:
> Referring to the language in the RFC is the starting point in the 
> discussion related to defining the problem that may or may not require a 
> solution. 

If everything is already crystal clear  from the existing documents I do not know why you even presented 4 different options at the beginning of the thread.
So if everything is clear, there are no options, and no problem to solve either.
I can hence leave this conversation where it is.

> I disagree that we should look at the various implementation 
> policies implemented in the wild by registries and registrars to develop 
> the appropriate interpretation of the RFC.

Which is absolutely not what I said.

So I will stop here, as I may be doing more harm than benefits to the WG by continuing.

Regards,

-- 
  Patrick Mevzek

v2.23.0 | Report a Bug | By Email