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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 25 January 2016 14:29 UTC

Return-Path: <shollenbeck@verisign.com>
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 E0FBD1ACEFD for <eppext@ietfa.amsl.com>; Mon, 25 Jan 2016 06:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] 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 Y0EyP_662OqB for <eppext@ietfa.amsl.com>; Mon, 25 Jan 2016 06:29:54 -0800 (PST)
Received: from mail-oi0-x264.google.com (mail-oi0-x264.google.com [IPv6:2607:f8b0:4003:c06::264]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5D7791ACEFA for <eppext@ietf.org>; Mon, 25 Jan 2016 06:29:54 -0800 (PST)
Received: by mail-oi0-x264.google.com with SMTP id y145so7881462oif.1 for <eppext@ietf.org>; Mon, 25 Jan 2016 06:29:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=XlulIflqHZKPk8/xMEzP1QZvFtm4GhMt0I8WLmqZtiI=; b=vafBPWgOQBZBqtLccXXU2KQhcdkk3o7Tabr4TTE4sg6pGlRRSUQSxNAkXfQMoBJdb3 eMrfvteT5fEvkvzX8s9IGCwwlm8WDtOaavlXhuqQ31wpDarO+lH/b9Vc0GmhXgtDHEWO hfdZ2AAvUcj95f/cNy4IiUFS/I/CUVTMmCg2o4Sp5b4ktbnUm8W1Hrx3GiX3e4cVCnV6 rpWtp+0g8Lb6dHLsWHhge7wQ357CTRlxuimtdt7xlpA8c5uK8/dYPEjohPJP+gURdafq nRwKQC9SkcseReRjsvgbCwWkRSIt1KwZ199Iur05brgu+sR9LfC+AaSeqZtop3Vt8URI GFig==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :content-type:mime-version; bh=XlulIflqHZKPk8/xMEzP1QZvFtm4GhMt0I8WLmqZtiI=; b=KQlYL07OX3USjHYfTiHjYYAaJ89C3eXjbLCV96zl1XjTzxirlnLtaBQIe9bfi/TPmV fVVOBXpEPlcj8xOX62G81xIP7UDyCDqIU59FUm1Ajt09SN6ORUFb0dhIlrq4U7GMtE1u aRRkQWea9llyqzC4i2FPOiL0b9KPcMrX1YpXVMmhlVlF2aq4bJU9HkZjEhqvAlgFX6lZ B+0xtDHZDkSKtniXQERyKZu1RBvl+BehCgwFypVv1OP1pYjTMaO0OIak2bzXg+Jn+cRc mdhwxKMEpLd9fjXY/krhjD8PIbsae2E5AJYZE3LZC7ucxGHR9vewNurq/6ZxcpepBeUu I8rg==
X-Gm-Message-State: AG10YOSrlQ1ubLo7sWsNq7FhQsuTV4TZf4JatXDBDP4O6wz46YMTMAUEcXGHCuEvodfA/kvRiaHOmN7Zircg4+eua8J3s9bs
X-Received: by 10.140.239.79 with SMTP id k76mr23015235qhc.87.1453732191768; Mon, 25 Jan 2016 06:29:51 -0800 (PST)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id z142sm3013338qka.11.2016.01.25.06.29.51 (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 25 Jan 2016 06:29:51 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id u0PETpiH028969 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 25 Jan 2016 09:29:51 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 25 Jan 2016 09:29:50 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Gustavo Lozano <gustavo.lozano@icann.org>, "eppext@ietf.org" <eppext@ietf.org>
Thread-Topic: I-D Action: draft-lozano-ietf-eppext-registrar-expiration-date-00.txt
Thread-Index: AQHRVII5CddH1x7oPEyvfpfQ7AYzkZ8GX2rQgACTRACAAJ8ckIAAB4PQgAERQACAA6RVYA==
Date: Mon, 25 Jan 2016 14:29:49 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A141B86@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
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> <D2C81A2C.F052E%gustavo.lozano@icann.org>
In-Reply-To: <D2C81A2C.F052E%gustavo.lozano@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0008_01D15752.EE1DCC00"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/OVDGQvxTQwQnsE6rbr4YJ0JPVEw>
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: Mon, 25 Jan 2016 14:29:56 -0000

> -----Original Message-----
> From: Gustavo Lozano [mailto:gustavo.lozano@icann.org]
> Sent: Friday, January 22, 2016 8:46 PM
> To: Hollenbeck, Scott; eppext@ietf.org
> Subject: Re: I-D Action: draft-lozano-ietf-eppext-registrar-expiration-
> date-00.txt
> 
> Thank you Scott,
> 
> @All: An interesting conversation about the registrar registration
> expiration date is taking place in gtld-tech, you may find it here:

[snip]

> 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.

Adding the reference would be good, but please keep in mind that more than a
reference may be needed. Something somewhere needs to explain what this
information means and how it relates to other information that is already
being exchanged or produced.

I still don't know what "expiration date within the Registrar" means when
the registrar isn't the authoritative source for the registration period. If
it has something to do with the registrar-registrant service relationship
perhaps it should be named something else to make sure there is no confusion
between this value and the expiration date managed by the registry.

Scott