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

Thomas Corte <Thomas.Corte@knipp.de> Mon, 16 July 2018 15:07 UTC

Return-Path: <Thomas.Corte@knipp.de>
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 16406130E66 for <regext@ietfa.amsl.com>; Mon, 16 Jul 2018 08:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, URIBL_BLOCKED=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 luP-fun2m-ZL for <regext@ietfa.amsl.com>; Mon, 16 Jul 2018 08:07:54 -0700 (PDT)
Received: from kmx5b.knipp.de (s671.bbone.dtm.knipp.de [195.253.6.105]) (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 B0DF612426A for <regext@ietf.org>; Mon, 16 Jul 2018 08:07:53 -0700 (PDT)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx5b.knipp.de (Postfix) with ESMTP id 228123007D5 for <regext@ietf.org>; Mon, 16 Jul 2018 15:07:51 +0000 (UTC)
Received: from flexo.fritz.box (fw.do.knipp.de [195.253.2.17]) by hp9000.do.knipp.de (Postfix) with ESMTP id 09E98CF9D9 for <regext@ietf.org>; Mon, 16 Jul 2018 17:07:21 +0200 (MESZ)
To: regext@ietf.org
References: <3266784A-E663-4465-8ABF-A3305B83C253@verisign.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> <1527135820.1779071.1382936736.3093914E@webmail.messagingengine.com> <2c568201-aa94-3c74-a708-33f3b97bc4f3@switch.ch> <da81c99b-a578-2c63-e383-a94edb66f991@switch.ch> <B34D3782-8922-404D-AE53-52F6C97B5D19@verisign.com> <1531714837.3402881.1441792896.31139F66@webmail.messagingengine.com> <D3A1BF68-4CB5-4AB1-A448-81672BBBAECB@verisign.com> <76E9BFB72652A04F93B1151E087E53380262AA8E@MBX117.d.ethz.ch>
From: Thomas Corte <Thomas.Corte@knipp.de>
Openpgp: preference=signencrypt
Autocrypt: addr=Thomas.Corte@knipp.de; prefer-encrypt=mutual; keydata= xsDiBDtvzjIRBAD2csyfVM8EPe+Pd/iYhwDP7fHAMCoZNsPBId4UrOQraKflyVCq2aOMVofw G2ayL377DewD+Va2GYgNes7a1bVLc0KxUCfvCKm3mLcBd8ScWaPurWMinTFHMBDm0CVIbIM6 P22HEqQ5w38W/yaisitIstU4MV9MLYttbUIZg75MvQCg/xNEFuhmmmp9hYnopxoyniDkovUD /iv7jhPtn4M/bOxCcSBYE1lJ6kILe1Z3rc5N9Ymr7uzUOffTt9JDqq9/2MujKODo5KosNC+m r6F1XC1a7KvhhjBofGHxQt9YZtCmHmdgumg5XoKwuujYG9BT1oKxj5/rnRHwT8GzxLL0YyAp Sbu6UfpAjhHAFtiL5Bg9fpDA2OAHA/9P/aSSE/FG0Rh7i6t+jZe/BCX5i4rns3UmjW7pzj/e wZENsKST72x5YVvbtXzYw620v7EFmZB99+UftXg6ggZUHkaDllR9lN75s9ih8cWI5zhj6OA8 LGsc4CqudNa0TSFdHTaHOT8QJtfP8UFJYcJd2ahOPXDIcqGd2JdGPHXO4c0kVGhvbWFzIENv cnRlIDxUaG9tYXMuQ29ydGVAa25pcHAuZGU+wksEEBECAAsFAjtvzjIECwMBAgAKCRDz5VkQ Ov//nJKaAJ4h/hksIIt3Zmkmwt7IT8VtwyYkcQCcDvapUlelcVQRKDB9cwPkZkwmQXPOwU0E O2/OMhAIAPZCV7cIfwgXcqK61qlC8wXo+VMROU+28W65Szgg2gGnVqMU6Y9AVfPQB8bLQ6mU rfdMZIZJ+AyDvWXpF9Sh01D49Vlf3HZSTz09jdvOmeFXklnN/biudE/F/Ha8g8VHMGHOfMlm /xX5u/2RXscBqtNbno2gpXI61Brwv0YAWCvl9Ij9WE5J280gtJ3kkQc2azNsOA1FHQ98iLMc fFstjvbzySPAQ/ClWxiNjrtVjLhdONM0/XwXV0OjHRhs3jMhLLUq/zzhsSlAGBGNfISnCnLW hsQDGcgHKXrKlQzZlp+r0ApQmwJG0wg9ZqRdQZ+cfL2JSyIZJrqrol7DVekyCzsAAgIIAKOz DOAHt4rHGwJbacsUbB0O4Y7Wm5f1dEyMeh2IKWZB557W90PPMaJlKqc5BRImOgY6/mCaGY3i bn0axP/2zQe0yX1NCudPXLFzazztSBsaQeQGZ8fBo3RHMdG9QgI39KHvHRuyTJ2qiiUkB43R 5JP9uJcQ/ca9COBpFR6L05YMleh9du1EVKPoKUFjjIFrS8DTN3RuCMTvmey6U6NRyg6O6/4x VpNBZTrn4i9r3oZ0drd1UpdEuFvMpfKgch08W3EUfGQaqasrja77rwGWG1CIJfQrtgkfNiHj kX9uJRDGmKln8Q7xntQPFAx7kDId4ZcaWruEoK916HJbrmIWmWvCPwMFGDtvzjLz5VkQOv// nBECnWYAoIfyMQI8fKTCMc0pdvycfsbwCYA9AKCFE9M915HNchKGzKCxIQQbnLNXSA==
Organization: Knipp Medien und Kommunikation GmbH
Message-ID: <90ca0e84-7c73-1756-e096-88f07f48f758@knipp.de>
Date: Mon, 16 Jul 2018 17:07:20 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <76E9BFB72652A04F93B1151E087E53380262AA8E@MBX117.d.ethz.ch>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Spamd-Bar: /
Authentication-Results: kmx5b.knipp.de
X-Rspamd-Server: s671
X-Rspamd-Queue-Id: 228123007D5
X-Spamd-Result: default: False [0.00 / 15.00]; ASN(0.00)[asn:8391, ipnet:195.253.0.0/16, country:DE]; IP_WHITELIST(0.00)[195.253.2.54]
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/eRt_1zm8ifXP6xg9g0iqkfbf0Ks>
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.27
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: Mon, 16 Jul 2018 15:07:57 -0000

Hello,

On 7/16/18 16:46, Martin Casanova wrote:

> ... The precondition of this approach is, that we actually can ask all
> registrars to prepare their clients to at least tolerate new poll
> messages and to update their business logic in order to process the
> newly given information properly if they wish to do so. I think this
> should be the case and no problem for most registrars already.

There is a problem with this approach if the EPP client (like ours) uses
an XML parser that validates against the configured XML schema
definitions. Such a client will inevitably choke on any unknown
namespaces, since reading the message will fail on the parsing layer
already (without the business logic even getting a chance to look at the
message).
Note by the way that using a schema-validating EPP client is actually
beneficial since it allows the code consuming data from the registry's
responses to simply assume that certain data must be present and/or
follow a certain format, without the need for additional checks; i.e.
it's not just a case of being particularly pedantic.

To "tolerate new poll messages" in such a scenario would require
disabling the schema validation altogether, which would reintroduce the
need for addition checks in code that were previously handled by the
parsing layer.

I'm therefore much in favor of the previously discussed solution
involving the <extValue> element. It's not perfect, but it allows
schema-validating EPP clients to read and acknowledge unknown poll
messages which would otherwise block the queue.

Best regards,

Thomas

-- 
____________________________________________________________________
     |       |
     | knipp |            Knipp  Medien und Kommunikation GmbH
      -------                    Technologiepark
                                 Martin-Schmeißer-Weg 9
                                 44227 Dortmund
                                 Deutschland

     Dipl.-Informatiker          Tel:    +49 231 9703-0
     Thomas Corte                Fax:    +49 231 9703-200
     Stellvertretender Leiter    SIP:    Thomas.Corte@knipp.de
     Software-Entwicklung        E-Mail: Thomas.Corte@knipp.de

                                 Registereintrag:
                                 Amtsgericht Dortmund, HRB 13728

                                 Geschäftsführer:
                                 Dietmar Knipp, Elmar Knipp