Re: [DNSOP] pushing updates to the parent

Tony Finch <dot@dotat.at> Fri, 07 March 2014 10:49 UTC

Return-Path: <fanf2@hermes.cam.ac.uk>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BD94D1A012B for <dnsop@ietfa.amsl.com>; Fri, 7 Mar 2014 02:49:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 eBBqwd9u559C for <dnsop@ietfa.amsl.com>; Fri, 7 Mar 2014 02:49:56 -0800 (PST)
Received: from ppsw-41.csi.cam.ac.uk (ppsw-41-v6.csi.cam.ac.uk [IPv6:2001:630:212:8::e:f41]) by ietfa.amsl.com (Postfix) with ESMTP id C070D1A006F for <dnsop@ietf.org>; Fri, 7 Mar 2014 02:49:56 -0800 (PST)
X-Cam-AntiVirus: no malware found
X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/
Received: from hermes-1.csi.cam.ac.uk ([131.111.8.51]:39724) by ppsw-41.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:25) with esmtpa (EXTERNAL:fanf2) id 1WLsLe-00037x-Sj (Exim 4.82_3-c0e5623) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 07 Mar 2014 10:49:50 +0000
Received: from fanf2 by hermes-1.csi.cam.ac.uk (hermes.cam.ac.uk) with local id 1WLsLe-0001PY-QW (Exim 4.72) (return-path <fanf2@hermes.cam.ac.uk>); Fri, 07 Mar 2014 10:49:50 +0000
Date: Fri, 7 Mar 2014 10:49:50 +0000
From: Tony Finch <dot@dotat.at>
X-X-Sender: fanf2@hermes-1.csi.cam.ac.uk
To: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <3E0DC692-7BA0-4672-BB10-82B854BB69CE@hopcount.ca>
Message-ID: <alpine.LSU.2.00.1403071025270.19416@hermes-1.csi.cam.ac.uk>
References: <20140307100524.2F42810CD58F@rock.dv.isc.org> <3E0DC692-7BA0-4672-BB10-82B854BB69CE@hopcount.ca>
User-Agent: Alpine 2.00 (LSU 1167 2008-08-23)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Tony Finch <fanf2@hermes.cam.ac.uk>
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/tMhMzKWCyWndDqG3wmz5lX3W-n4
Cc: dnsop@ietf.org
Subject: Re: [DNSOP] pushing updates to the parent
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 07 Mar 2014 10:49:59 -0000

Joe Abley <jabley@hopcount.ca> wrote:
>
> https://xkcd.com/927/

So from the standards development point of view, I think what this is
saying is that success is more likely to come from building on what people
are already doing and nudging more of them to do it more similarly.

The problem with the parent update process is that there's a hopeless zoo
of more-or-less crappy APIs almost none of which are good foundations.

For a push-style protocol there are two parts: finding out where to push
the update; and how to push the update.

The where question ought to be answered by whois or weirds or _update SRV
records.

The how question ought to be answered by EPP (from registrant to
registrar) or DNS UPDATE. It would be nice if there were software to
gateway between one and the other.

Tony.
-- 
f.anthony.n.finch  <dot@dotat.at>  http://dotat.at/
Humber: Southwest 6 to gale 8, becoming variable 4, then southeast 5 later.
Slight or moderate. Rain, becoming fair. Moderate becoming good.