IETF Logo Mail Archive

Re: [ire] EBERO and host attributes

Klaus Malorny <Klaus.Malorny@knipp.de> Fri, 18 October 2013 08:09 UTC

Return-Path: <Klaus.Malorny@knipp.de>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46A3511E810C for <ire@ietfa.amsl.com>; Fri, 18 Oct 2013 01:09:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.249
X-Spam-Level:
X-Spam-Status: No, score=-3.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id GczJpTzgHOtW for <ire@ietfa.amsl.com>; Fri, 18 Oct 2013 01:08:52 -0700 (PDT)
Received: from kmx10a.knipp.de (clust3c.bbone.knipp.de [195.253.6.130]) by ietfa.amsl.com (Postfix) with ESMTP id 4206611E8128 for <ire@ietf.org>; Fri, 18 Oct 2013 01:08:47 -0700 (PDT)
Received: from localhost (localhost.bbone.knipp.de [127.0.0.1]) by kmx10a.knipp.de (Postfix) with ESMTP id 7DF7D45; Fri, 18 Oct 2013 10:08:46 +0200 (MESZ)
X-Knipp-VirusScanned: Yes
Received: from kmx10a.knipp.de ([127.0.0.1]) by localhost (kmx10a.knipp.de [127.0.0.1]) (amavisd-new, port 10004) with ESMTP id amO7os3E4Yca; Fri, 18 Oct 2013 10:08:39 +0200 (MESZ)
Received: from hp9000.do.knipp.de (hp9000.do.knipp.de [195.253.2.54]) by kmx10a.knipp.de (Postfix) with ESMTP id 02B9144; Fri, 18 Oct 2013 10:08:39 +0200 (MESZ)
Received: from [195.253.2.27] (mclane.do.knipp.de [195.253.2.27]) by hp9000.do.knipp.de (@(#)Sendmail version 8.13.3 - Revision 1.000 - 1st August,2006/8.13.3) with ESMTP id r9I88Z6f003193; Fri, 18 Oct 2013 10:08:35 +0200 (MESZ)
Message-ID: <5260EC8A.9090202@knipp.de>
Date: Fri, 18 Oct 2013 10:08:42 +0200
From: Klaus Malorny <Klaus.Malorny@knipp.de>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:27.0) Gecko/20100101 Thunderbird/27.0a1
MIME-Version: 1.0
To: Rubens Kuhl <rubensk@nic.br>, ire@ietf.org
References: <CE851019.5035D%jgould@verisign.com> <525FBF0B.9010607@knipp.de> <DD3FE9E9-9A09-4CD8-990E-1E262E9864E1@nic.br>
In-Reply-To: <DD3FE9E9-9A09-4CD8-990E-1E262E9864E1@nic.br>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [ire] EBERO and host attributes
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Internet Registration Escrow discussion list." <ire.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ire>, <mailto:ire-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ire>
List-Post: <mailto:ire@ietf.org>
List-Help: <mailto:ire-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ire>, <mailto:ire-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 Oct 2013 08:09:07 -0000

On 17.10.2013 23:01, Rubens Kuhl wrote:
>>
>
> Klaus question suggested me another point that I'm curious about: are all
> EBEROs providing capability for doing emergency failover of registries
> running host attributes instead of host records ? Although host records are
> the most usual solution among gTLD registries, not all new gTLD registries
> will use host records. As a matter of fact I know of at least 5 TLDs running
> on host attributes, could be more among the 1345 new gTLDs.
>
>
> Rubens
>

Hi Rubens,

I think the two ways of representing hosts are rather exchangeable, so you can 
create host objects on the fly from host attributes and vice versa. In-zone 
hosts are then associated with the same sponsor as the containing domain, 
external hosts are associated with a default sponsor. In our system, we will 
definitely handle it this way in order to limit the changes to our registry 
software.

Regards,

Klaus

v2.23.0 | Report a Bug | By Email