[ire] Response From ICANN About Host Info

"liushuo@knet" <liushuo@knet.cn> Wed, 29 May 2013 01:52 UTC

Return-Path: <liushuo@knet.cn>
X-Original-To: ire@ietfa.amsl.com
Delivered-To: ire@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 3BAB321E804B for <ire@ietfa.amsl.com>; Tue, 28 May 2013 18:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.306
X-Spam-Level: ***
X-Spam-Status: No, score=3.306 tagged_above=-999 required=5 tests=[BAYES_50=0.001, FH_RELAY_NODNS=1.451, HTML_MESSAGE=0.001, MIME_BASE64_TEXT=1.753, RDNS_NONE=0.1]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id HM1PGhSrVpEV for <ire@ietfa.amsl.com>; Tue, 28 May 2013 18:52:43 -0700 (PDT)
Received: from cnnic.cn (unknown []) by ietfa.amsl.com (Postfix) with SMTP id 039B811E80A2 for <ire@ietf.org>; Tue, 28 May 2013 18:52:41 -0700 (PDT)
X-EYOUMAIL-SMTPAUTH: liushuo@knet.cn
Received: from unknown203.119.80.47 (HELO stuart-knet) ( by with SMTP; Wed, 29 May 2013 09:52:38 +0800
Date: Wed, 29 May 2013 09:52:34 +0800
From: "liushuo@knet" <liushuo@knet.cn>
To: ire <ire@ietf.org>
X-Priority: 3
X-Has-Attach: no
X-Mailer: Foxmail[cn]
Mime-Version: 1.0
Message-ID: <2013052909523452915715@knet.cn>
Content-Type: multipart/alternative; boundary="----=_001_NextPart875878617776_=----"
Subject: [ire] Response From ICANN About Host Info
X-BeenThere: ire@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: liushuo <liushuo@knet.cn>
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: Wed, 29 May 2013 01:52:49 -0000


I have submited the same question to ICANN regarding the external and internal host isssue in escrow file, and I got the following answer:

The draft-arias-noguchi-dnrd-objects-mapping (http://tools.ietf.org/html/draft-arias-noguchi-dnrd-objects-mapping-03#section-1) supports two ways of escrowing host information: host objects and host attributes (see section 1.1 of RFC 5731 at http://tools.ietf.org/html/rfc5731). 
If you are escrowing using host attributes, there is no need to use host objects in the escrow deposit. If you are escrowing using host objects, both internal and external hosts must be escrowed. 
This serves as a resolution to your inquiry. Please submit a new comment within seven days to reopen this case. 

So I think in case of the existing host attribute in domain objects, there is no need to use host objects at all.

What do you say?