Re: [eppext] [provreg] Publishing of the Change Poll EPP Extension IETF Draft

Patrick Mevzek <Patrick.Mevzek@afnic.fr> Sat, 25 April 2015 14:27 UTC

Return-Path: <Patrick.Mevzek@afnic.fr>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 021501ACD40 for <eppext@ietfa.amsl.com>; Sat, 25 Apr 2015 07:27:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.349
X-Spam-Level:
X-Spam-Status: No, score=0.349 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, HELO_EQ_FR=0.35] autolearn=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 9mJBNq-bxYgo for <eppext@ietfa.amsl.com>; Sat, 25 Apr 2015 07:27:17 -0700 (PDT)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 5A5F91ACD27 for <eppext@ietf.org>; Sat, 25 Apr 2015 07:27:17 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id 9A68B2802BF; Sat, 25 Apr 2015 16:27:15 +0200 (CEST)
Received: from relay1.nic.fr (relay1.nic.fr [192.134.4.162]) by mx4.nic.fr (Postfix) with ESMTP id 9473B2802B2; Sat, 25 Apr 2015 16:27:15 +0200 (CEST)
Received: from [IPv6:::1] (citrine.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:96]) by relay1.nic.fr (Postfix) with ESMTP id 4C5DA4C0053; Sat, 25 Apr 2015 16:26:45 +0200 (CEST)
Message-ID: <1429972004.16625.6.camel@citrine-mobile>
From: Patrick Mevzek <Patrick.Mevzek@afnic.fr>
To: Rubens Kuhl <rubensk@nic.br>
Date: Sat, 25 Apr 2015 16:26:44 +0200
In-Reply-To: <4D5E61F9-D8ED-48A1-BF40-6CE42B09601B@nic.br>
References: <211D0420-18A3-43D7-9A3D-553B34C6DF43@verisign.com> <CAJ9-zoVSoY=g+70ZfYFkYG7KEFM88x0BxVRH5jUxNYqMsMt+8A@mail.gmail.com> <77F1013C-BF41-4982-9845-C1F87F69B5F5@verisign.com> <4D5E61F9-D8ED-48A1-BF40-6CE42B09601B@nic.br>
Organization: AFNIC
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.5-2+b1
Mime-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/Pav-YIyzmuHoK9n5XVD530J04P0>
Cc: gtld-tech@icann.org, "eppext@ietf.org" <eppext@ietf.org>, "Gould, James" <JGould@verisign.com>
Subject: Re: [eppext] [provreg] Publishing of the Change Poll EPP Extension IETF Draft
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 25 Apr 2015 14:27:19 -0000

Le jeudi 05 mars 2015 à 21:07 -0300, Rubens Kuhl a écrit :

> Has the use case of DNS publishing been considered for the changepoll
> extension ? Some registries defer publication of a domain to the
> registry zone until DNS servers respond correctly (authoritative,
> DNSKEY matches DS etc.), and a poll message could signal that to the
> sponsoring client. I couldn't find an appropriate operation in
> changepoll-02... what are your and the group's thoughts on this ? 

I agree that could be very useful, especially if the polling message can
carry some information on what tests have been done, which have failed,
and courses of action for the registrar (including info to know if the
failure is temporary or definitive).

However it could be using the operation name "update". But I would
recommend to define some kind of extensibility into the list of
operation names, making registry able to add some new ones.

When AFNIC did include a message for registrars after a DNS check in the
the past, here was how the polling message looked like :
<msgQ count="1" id="50001">
 <qDate>2008-12-25T00:01:00.0Z</qDate>
 <msg>
  <resZC type="plain-text">
ZONE : ndd-de-test-0001.fr.
NS    : ns1.nic.fr.
NS    : ns2.nic.fr.
NS    : ns.ndd-de-test-0001.fr. [192.93.0.1, 2001:660:3005:1::1:1]

==> SUCCESS
  </resZC>
 </msg>
</msgQ>


It was using at the time the pure text result of the Zonecheck tool.
Today, this tool has been replaced by ZoneMaster.

-- 
Patrick Mevzek