IETF Logo Mail Archive

Re: [eppext] I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt

Gustavo Lozano <gustavo.lozano@icann.org> Sat, 23 January 2016 01:46 UTC

Return-Path: <gustavo.lozano@icann.org>
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 647E21B2ECB for <eppext@ietfa.amsl.com>; Fri, 22 Jan 2016 17:46:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] 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 J7Ofyke3AOST for <eppext@ietfa.amsl.com>; Fri, 22 Jan 2016 17:46:32 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03DEE1B2ECA for <eppext@ietf.org>; Fri, 22 Jan 2016 17:46:32 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Fri, 22 Jan 2016 17:46:29 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Fri, 22 Jan 2016 17:46:28 -0800
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt
Thread-Index: AQHRVX/gAP8gVO3Bp0qp3Ahdr6ABkg==
Date: Sat, 23 Jan 2016 01:46:28 +0000
Message-ID: <D2C81A2C.F052E%gustavo.lozano@icann.org>
References: <20160121193028.13313.82104.idtracker@ietfa.amsl.com> <831693C2CDA2E849A7D7A712B24E257F4A133A9D@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <D2C6A87C.F0080%gustavo.lozano@icann.org> <831693C2CDA2E849A7D7A712B24E257F4A13DDF0@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4A13DE97@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A13DE97@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.0.151221
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3536329579_8341038"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/IWO4toJR9Vt-gq_GhbPmbf4weC8>
Subject: Re: [eppext] I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt
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: <https://mailarchive.ietf.org/arch/browse/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, 23 Jan 2016 01:46:33 -0000

Thank you Scott, 

@All: An interesting conversation about the registrar registration
expiration date is taking place in gtld-tech, you may find it here:
http://mm.icann.org/pipermail/gtld-tech/2016-January/000605.html. As
Francisco mentioned in the gtld-tech thread:

"The ³Registrar Registration Expiration Date² is **not** being proposed in
draft-lozano-ietf-eppext-registrar-expiration-date. The field is already
in gTLD Registrar's Whois and has been there for more than two years and
registrars use it as described by Pat, Thomas and others in this thread.
Please see the 2013 RAA RDDS spec at
https://www.icann.org/resources/pages/approved-with-specs-2013-09-17-en#who
is. The draft is simply a proposal to fill the vacuum to pass this field
from registrars to registries per the Thick Whois policy recommendation
that is in the process to finalize its policy language."

I will add text in the draft mentioning the origin (RAA2013) of the
registrar expiration date, and that registrars use this field to signal
the expiration date within the Registrar.


Regards,
Gustavo


On 1/22/16, 06:30, "Hollenbeck, Scott" <shollenbeck@verisign.com> wrote:

>> -----Original Message-----
>> From: EppExt [mailto:eppext-bounces@ietf.org] On Behalf Of Hollenbeck,
>> Scott
>> Sent: Friday, January 22, 2016 9:09 AM
>> To: Gustavo Lozano; eppext@ietf.org
>> Subject: Re: [eppext] I-D Action: draft-lozano-ietf-eppext-registrar-
>> expiration-date-00.txt
>> 
>
>[snip]
>
>> I will not support publication of an EPP extension RFC that is unclear
>> about
>> the purpose of the extension or the fields that are being added.
>> Something
>> needs to be added to the draft to make that purpose crystal clear. If
>> that
>> means adding text to an external document, fine. However, you do need
>> to
>> answer the questions I asked in my last note.
>
>Sorry, there's a word missing in the text above. What it should say:
>
>"means adding text to *describe* an external document"
>
>Scott

v2.23.0 | Report a Bug | By Email