Re: [weirds] [eppext] Adding missing RDAP event action types for gTLDs

Roger D Carney <rcarney@godaddy.com> Tue, 15 December 2015 18:44 UTC

Return-Path: <rcarney@godaddy.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 280071A8A45; Tue, 15 Dec 2015 10:44:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.654
X-Spam-Level:
X-Spam-Status: No, score=0.654 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FRT_PROFILE1=2.555, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] 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 aqWHJdXF5Puh; Tue, 15 Dec 2015 10:44:39 -0800 (PST)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0115.outbound.protection.outlook.com [65.55.169.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B95E1AC3D0; Tue, 15 Dec 2015 10:44:39 -0800 (PST)
Received: from BY2PR0201MB0773.namprd02.prod.outlook.com (10.160.125.139) by BY2PR0201MB0776.namprd02.prod.outlook.com (10.160.125.141) with Microsoft SMTP Server (TLS) id 15.1.337.19; Tue, 15 Dec 2015 18:44:37 +0000
Received: from BY2PR0201MB0773.namprd02.prod.outlook.com ([10.160.125.139]) by BY2PR0201MB0773.namprd02.prod.outlook.com ([10.160.125.139]) with mapi id 15.01.0337.024; Tue, 15 Dec 2015 18:44:37 +0000
From: Roger D Carney <rcarney@godaddy.com>
To: "eppext@ietf.org" <eppext@ietf.org>, "weirds@ietf.org" <weirds@ietf.org>
Thread-Topic: [eppext] Adding missing RDAP event action types for gTLDs
Thread-Index: AQHRMiB7vJAHZ7R4aEujObDC1dr/wp7LDteg
Date: Tue, 15 Dec 2015 18:44:36 +0000
Message-ID: <BY2PR0201MB0773607DE53F284796AB2E2FB1EE0@BY2PR0201MB0773.namprd02.prod.outlook.com>
References: <D28CC239.D42D7%gustavo.lozano@icann.org>
In-Reply-To: <D28CC239.D42D7%gustavo.lozano@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=rcarney@godaddy.com;
x-originating-ip: [64.202.161.57]
x-microsoft-exchange-diagnostics: 1; BY2PR0201MB0776; 5:Pk1ZVs9QKkCCYe0UfZU/w13OtcH5Re1LWEcrU9mwWDmgsaZhUJ5lLWGPalPEWPDtVa3ZKVyN615YwX5c/ZAjUksOY3PQR0FoIE7aVaQPsUj9UNVGd4gwjulTF6NSTCDaPtWjOVy8eoxGmkE0D7xtoQ==; 24:K+Yc7jl5zSmJYkFtFUjF3ara3aNOoIqUjhaFaNjJ+hOOSsXzu+cD4IDl25aE4H1K0AMSt9ou5h21f8q0JsvlbiZRLjdIIAbQKV0FK6tq89o=
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BY2PR0201MB0776;
x-microsoft-antispam-prvs: <BY2PR0201MB0776E8EB38BBEF7BB037F269B1EE0@BY2PR0201MB0776.namprd02.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(246761809553906);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(2401047)(5005006)(8121501046)(520078)(3002001)(10201501046); SRVR:BY2PR0201MB0776; BCL:0; PCL:0; RULEID:; SRVR:BY2PR0201MB0776;
x-forefront-prvs: 07915F544A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(52014003)(51694002)(199003)(36944003)(13464003)(51914003)(189002)(377454003)(76176999)(50986999)(5004730100002)(122556002)(107886002)(33656002)(74316001)(189998001)(81156007)(2900100001)(5001770100001)(105586002)(5002640100001)(11100500001)(106116001)(40100003)(450100001)(19580395003)(54356999)(77096005)(92566002)(97736004)(15975445007)(76576001)(10400500002)(99286002)(2950100001)(66066001)(1720100001)(86362001)(19580405001)(2501003)(5003600100002)(87936001)(5890100001)(561944003)(5001960100002)(5008740100001)(101416001)(106356001)(6116002)(1096002)(102836003)(3846002)(1220700001)(586003)(17423001); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR0201MB0776; H:BY2PR0201MB0773.namprd02.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; A:1; MX:1; LANG:en;
received-spf: None (protection.outlook.com: godaddy.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: godaddy.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Dec 2015 18:44:36.9226 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: d5f1622b-14a3-45a6-b069-003f8dc4851f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR0201MB0776
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/z9QEpW97ZMsn4vT91F40q_oBm50>
Subject: Re: [weirds] [eppext] Adding missing RDAP event action types for gTLDs
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Dec 2015 18:44:48 -0000

Thanks for the reference Gustavo.

Just for clarity the suggestion is to make a new RDAP event for Last update of RDAP database as defined as "the last date and time the database used by the RDAP service was updated from the Registry or Registrar database". I don't think this definition of "Last update" matches the definition of an event as defined in Appendix B of RFC 7483: "actions that have taken place against a registered object at a certain date and time". A small nit, but I just wanted to make sure that I understand the proposal and the components involved.


Thanks
Roger

-----Original Message-----
From: Gustavo Lozano [mailto:gustavo.lozano@icann.org] 
Sent: Tuesday, December 08, 2015 7:25 PM
To: Roger D Carney; eppext@ietf.org; weirds@ietf.org
Subject: Re: [eppext] Adding missing RDAP event action types for gTLDs

Thank you for the feedback Roger,

 
This email slipped through the cracks, apologies for the
late response. 

Comments inline.

Regards,
Gustavo


From:  EppExt <eppext-bounces@ietf.org> on behalf of Roger D Carney
<rcarney@godaddy.com>
Date:  Tuesday, November 10, 2015 at 13:19
To:  "eppext@ietf.org" <eppext@ietf.org>rg>, "weirds@ietf.org"
<weirds@ietf.org>
Subject:  Re: [eppext] Adding missing RDAP event action types for gTLDs


>Thanks Gustavo.
> 
>I agree with Scott, from what I recall this is just a proposed timeline.
> 
>As for this I-D, one comment, one clarification:
>·        
>Comment: in reading Appendix B of RFC 7483 it states that events
>represent actions that have taken place against a registered object
> at a certain date and time. I don¹t see that Last Update of RDAP
>Database is an action against a registered object, against the
>³container² of these registered objects but not against a registered
>object. This may be just a definition issue, I don¹t recall
> reading a definition of Last Update of RDAP Database so it could be
>defined as: the date/time of the last change to a registration object
>(domain, host, contact) in the RDAP database. Lacking a definition I
>would have defined Last Update of RDAP Database literally,
> so any maintenance including restoration, reference table updates,
>etc I would say changes the Last Update of RDAP Database. Again maybe
>just a definition issue.
>
>
>

The draft provides a definition for "last update of RDAP database" in
section 2. The definition is: An action noting when the information in the
object instance in the RDAP database was last synchronized from the
authoritative database (e.g. registry database).

The RDAP profile published for public comments (i.e.
https://whois.icann.org/sites/default/files/files/gtld-rdap-operational-pro
file-draft-03dec15-en.pdf) uses this event action, you may want to take a
look at this document to have a better idea of the intended use.


>
>·        
>Clarification: this I-D tries to address the lack of some RDAP data
>modeling in regards to Registrar Expiration Date but there still
> is work needed to address getting this data from registrar to registry,
>correct? I am not aware of a way to do this currently or of work to make
>this happen.
> 
>
>
>

Correct, I am working on an I-D (EPP extension) to fill this gap.

> 
>Thanks
>Roger
> 
> 
>From:
> EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck, Scott
>Sent: Tuesday, November 10, 2015 12:48 PM
>To: Gustavo Lozano; eppext@ietf.org
>Cc: weirds@ietf.org
>Subject: Re: [eppext] Adding missing RDAP event action types for gTLDs
>
>
> 
>From: weirds [mailto:weirds-bounces@ietf.org]
>On Behalf Of Gustavo Lozano
>Sent: Tuesday, November 10, 2015 1:29 PM
>To: eppext@ietf.org
>Cc: weirds@ietf.org
>Subject: [weirds] Adding missing RDAP event action types for gTLDs
> 
>Hello colleagues,
>
> 
>
>As you may know, two of the open issues in the RDAP profile for gTLDs
>(http://mm.icann.org/pipermail/gtld-tech/attachments/20150928/35901409/gTL
>DRDAPOperationalProfile-v06-0001.pdf)
> are missing event action types in the base RDAP specification for:
>
>* Last update time of the RDAP database
>
>* Registrar registration expiration date
>
> 
>
>You may find the details in the following I-D:
>
>https://www.ietf.org/id/draft-lozano-rdap-gtld-whois-additional-events-00.
>txt 
><https://www.ietf.org/id/draft-lozano-rdap-gtld-whois-additional-events-00
>.txt>
>
> 
>
>It's important to promptly add these two event action types based on the
>timeline for deployment of RDAP in the gTLDs.
>
> 
>
>[snip]
> 
>If a recall what I heard in Dublin and Yokohama, the timeline is
>*proposed* and subject to a community review process that is supposed to
>start later this month ­ correct?
> 
>Scott